pushing updates live

Docs Build status updates of commit 51e515a:
:clock10: Full build: the average full build time is 15 min(s) 56 sec(s), this is based on the last 8 build(s) for this repository.
:warning: This is a FULL build due to a configuration change (usually in .openpublishing.publish.config.json and/or docfx.json). It is strongly suggested to merge this configuration change after the business hours, as it could impact the overall build performance of other PRs on the 'live' branch. For more detailed info, please click here.

Docs Build status updates of commit 51e515a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 690079d:
:clock10: Full build: the average full build time is 15 min(s) 57 sec(s), this is based on the last 9 build(s) for this repository.
:warning: This is a FULL build due to a configuration change (usually in .openpublishing.publish.config.json and/or docfx.json). It is strongly suggested to merge this configuration change after the business hours, as it could impact the overall build performance of other PRs on the 'live' branch. For more detailed info, please click here.

Docs Build status updates of commit 690079d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Deleted dependency detected

I'm a Cyber Security researcher and developer of PackjGuard [1] to address open-source software supply chain attacks.
Issue
During my research, I found that this repo is vulnerable to attack due to deleted dependency from the public PyPI registry.
Details
Specifically, file https://github.com/PSLmodels/OG-USA/blob/9da4947cacf412e4930d17365e5419bed5d17df6/setup.py lists xcalc as one of the dependencies. However, it has been deleted from public PyPI. As such, an external bad actor can claim that name and register a malicious package, which will be then installed with pip install command, resulting in arbitrary remote code execution.
Impact
Not only your apps/services using https://github.com/PSLmodels/OG-USA repo code are vulnerable to this attack, but the users of your open-source Github repo could also fall victim.
You could read more about such attacks here<EMAIL_ADDRESS>Remediation
Please manually register a placeholder xcalc package on PyPI immediately or remove xcalc dependency from https://github.com/PSLmodels/OG-USA/blob/9da4947cacf412e4930d17365e5419bed5d17df6/setup.py to fix this vulnerability.
To automatically fix such issues in future, please install PackjGuard Github app [1].
Thanks!

PackjGuard is a Github app that monitors your repos 24x7, detects vulnerable/malicious/risky open-source dependencies, and creates pull requests for auto remediation: https://github.com/marketplace/packjguard

Sorry about this false positive.


Sections inside table

Hello.
Is it possible to make headers inside table?
I mean create space between rows and put there a header. Not sticky, just header for full width of a table. Like sections, ect

Hi @Slavcheg2107
Nope! Sorry
You can also check #18 issue.


Don't stub the inject method when running on Node

Karma actually uses the $inject method and this was causing problems. It was difficult to
determine where to fix this, but settled on here.
Also removed glob dependency and improve unit test cleanup, added multiple override tests,
ensured that bundler based compile overrides work without messing up this patch
@cj - I could understand if you think this doesn't belong here. I would definitely agree only 1 or 2 of these 'exceptions' for other pieces of software at most.

@wied03 I'm fine with merging this in as in most cases you'll be using some node package with webpack.


Toggle layer visibility no longer working

Hi,
In the last few days, the plugin has stopped working. The shortcut to view or hide layers no longer works. I'm running Sketch Version 3.4.2 (15857). Any ideas what could be causing this ?
Thanks / Lucie

Hi @lucielca, which version of the plugin are you using? The latest?
Also, if you have several sketch documents opened while using the plugin: try closing all except one and try the plugin again (there's a known quite nasty issue where plugin commands fired in document A might take action in document B.)

Hi Christophe,
Thanks for your quick reply. I’m not sure which version I’m using, but it was downloaded sometime in the last few months. I see you have a more recent version, I’ll try with that one. I’ll also try your tip about keeping only one sketch document open.

On Nov 18, 2015, at 14:04, Christophe Stoll<EMAIL_ADDRESS>wrote:
Hi @lucielca https://github.com/lucielca, which version of the plugin are you using? The latest?
Also, if you have several sketch documents opened while using the plugin: try closing all except one and try the plugin again (there's a known quite nasty issue where plugin commands fired in document A might take action in document B.)
—
Reply to this email directly or view it on GitHub https://github.com/preciousforever/sketch-layer-visibility/issues/5#issuecomment-157824099.

It’s the jan 28 2015 version.

On Nov 18, 2015, at 14:04, Christophe Stoll<EMAIL_ADDRESS>wrote:
Hi @lucielca https://github.com/lucielca, which version of the plugin are you using? The latest?
Also, if you have several sketch documents opened while using the plugin: try closing all except one and try the plugin again (there's a known quite nasty issue where plugin commands fired in document A might take action in document B.)
—
Reply to this email directly or view it on GitHub https://github.com/preciousforever/sketch-layer-visibility/issues/5#issuecomment-157824099.

Hi,
It’s now working again with the latest version. However, the shortcut to toggle the visibility isn’t Command + L anymore, but Ctrl + Shift + R.

On Nov 18, 2015, at 14:04, Christophe Stoll<EMAIL_ADDRESS>wrote:
Hi @lucielca https://github.com/lucielca, which version of the plugin are you using? The latest?
Also, if you have several sketch documents opened while using the plugin: try closing all except one and try the plugin again (there's a known quite nasty issue where plugin commands fired in document A might take action in document B.)
—
Reply to this email directly or view it on GitHub https://github.com/preciousforever/sketch-layer-visibility/issues/5#issuecomment-157824099.

@lucielca the plugin does not have a default shortcut assigned actually! But you can set up whatever you like…

Ok thanks. Would it be possible for you to explain how to do that ?

@lucielca sure! This is what I did,
In Sketch, navigate to:

Plugins --> Manage Plugins
Select Sketch Layer Visibility --> Show Plugin Folder (in the gear dropdown)
Open sketchlayervisibility.sketchplugin in an editor like Sublime
In Sublime, avigate to manifest.json
In the "shortcut" parameter of each action enter the combination that you would like for that shortcut, for example "cmd shift x" or "ctrl shift 1", etc.

Thank you very much for the excellent instructions ! I was able to create a new shortcut.

sorry @lucielca for not getting back and thanks @yosyp for jumping in! :)


Sequence widget unavailable in v0.17.6

Error: module has no .Sequence field or method
The Sequence widget isn't making into the module exports. From debug:
[onebusaway2.star] ["Animation", "Box", "Circle", "Column", "Image", "Marquee", "Padding", "Plot", "Root", "Row", "Stack", "Text", "WrappedText", "fonts"]
2022/05/19 13:56:14 error loading applet: error running script: Traceback (most recent call last):
  onebusaway2.star:39:22: in main
Error: module has no .Sequence field or method
^C
$ pixlet version
Pixlet version: v0.17.6

You can clone the full repo and build there and it is useable that way.
I suspect they'll build it into the next release though.
But that's what you can do if you don't want to wait.

It did that when it was merged since the changes to the docs and the inclusion of the code to perform it was part of the same PR.
I can say though if you just build it from the source and not just unpack the binary it does work.

Looks like they update the release build so 'render.Sequence` should be available!!


Update cats-effect and Cats

Codecov Report

Merging #243 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master    #243   +/-   ##
======================================
  Coverage    97.2%   97.2%
======================================
  Files          23      23
  Lines         786     786
  Branches       58      58
======================================
  Hits          764     764
  Misses         22      22

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 6bdee37...1d815b1. Read the comment docs.


:sparkles: feat: Add ts-plugins etting to .vscode

Description
Removes the evmts.config in favor of only using ts-config to reduce amount of configuration.
This is because the ts-plugin cannot load async configs atm.
Until fixed this is better dx.
Testing
Explain the quality checks that have been done on the code changes
Additional Information

[ ] I read the contributing docs (if this is your first contribution)

Your ENS/address:

Current dependencies on/for this PR:

main

PR #250

PR #251

PR #252   👈

This comment was auto-generated by Graphite.


cmd/compile: differences in assembly between new(T) and &T{}

Go version
go version devel go1.24-d36353499f Sat Aug 10 12:39:48 2024 +0000 linux/amd64
What did you do?
I compiled the following program to check if there were any differences between new(T) and &T{}.
package test

type T struct {
    x string
}

func f1() *T {
    return new(T)
}

func f2() *T {
    return &T{}
}

What did you see happen?
In the case of &T{}, I noticed an extra instruction MOVQ    $0, (AX).
When the struct is
type T struct {
	x string
	y string
}

there is even another instruction MOVQ	$0, 16(AX).
But when the struct is
type T struct {
	x string
	y string
	z string
}

the differences go away.
Also, I noticed the two functions have a different cost to inline.
f1: can inline f1 with cost 2 as: func() *T { return new(T) }
f2: can inline f2 with cost 3 as: func() *T { return &T{} }
Lastly, both functions have stack handling code and I'm probably missing something, but from the assembly they don't seem to use the stack.

As an extra point of reference, the following functions produce different, but equivalent, assembly. The stack usage seems like it could be optimized, but that is another issue:
package test

type T struct {
	x string
	y string
	z string
}

func f1() T {
	return *new(T)
}

func f2() T {
	return T{}
}

f1
MOVUPS	X15, command-line-arguments.~r0(SP)
MOVUPS	X15, command-line-arguments.~r0+16(SP)
MOVUPS	X15, command-line-arguments.~r0+32(SP)
MOVQ	command-line-arguments.~r0(SP), AX
MOVQ	command-line-arguments.~r0+16(SP), CX
MOVQ	command-line-arguments.~r0+32(SP), SI
XORL	BX, BX
MOVQ	BX, DI
MOVQ	BX, R8

f2
MOVUPS	X15, command-line-arguments.~r0(SP)
MOVUPS	X15, command-line-arguments.~r0+16(SP)
MOVUPS	X15, command-line-arguments.~r0+32(SP)
MOVQ	command-line-arguments.~r0(SP), AX
MOVQ	command-line-arguments.~r0+8(SP), BX
MOVQ	command-line-arguments.~r0+16(SP), CX
MOVQ	command-line-arguments.~r0+24(SP), DI
MOVQ	command-line-arguments.~r0+32(SP), SI
MOVQ	command-line-arguments.~r0+40(SP), R8

What did you expect to see?
I expected both functions to be equivalent.

Related Issues and Documentation

cmd/compile: &T{} generates different assembly than new(T) #16494 (closed)
cmd/compile: small struct initialization code is suboptimal because of redundant zeroing #59021 (closed)
cmd/compile: strange performance difference between two implementations #49785

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

I have a fix for the unnecessary zeroing.

Also, I noticed the two functions have a different cost to inline.

This is because at inlining time, f1 has just NEW whereas f2 has PTRLIT + STRUCTLIT, each of which has a cost of 1. Probably not worth fixing.

Lastly, both functions have stack handling code and I'm probably missing something, but from the assembly they don't seem to use the stack.

They need stack handling because they call out to runtime.newobject, and thus need a full frame.

Thank you for the quick reply and the explanation on inlining/stack handling.

This is because at inlining time, f1 has just NEW whereas f2 has PTRLIT + STRUCTLIT, each of which has a cost of 1. Probably not worth fixing.

IMHO, this should be fixed for the sake of consistency. People expect that new(T) and &T{} generate identical assembly code with identical inlining costs. If these statements generate different assembly code and/or have different inlining costs, then people start wasting their time on figuring out the most optimal statement. This isn't very productive task.


WSL2 cannot SSH to any servers

Version
Microsoft Windows [Version 10.0.19043.1466]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
5.10.16
Distro Version
Ubuntu 20.04
Other Software
No response
Repro Steps
ssh userid@IPaddress
OpenSSH_8.2p1 Ubuntu-4, OpenSSL 1.1.1f  31 Mar 2020
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug1: Connecting to xx.xxx.xx.220 [xx.xxx.xx.220] port 22.
debug1: connect to address xx.xxx.xx.220 port 22: Connection timed out
ssh: connect to host xx.xxx.xx.220 port 22: Connection timed out
I can ssh from a VirutalBox VM running CentOS, and I can ssh from a simple command line (cmd) with this command. I expect if I installed any other ssh client it would work. It just doesn't work in WSL2.
After reading many pages of forums, I added a rule for incoming port 22 connections to the windows firewall. That didn't work so I just turned the whole firewall off and the ssh command still doesn't work. I don't think it's windows firewall preventing this. I do have Sophos Safeguard on this machine but am not able to detect if it has another layer of network protection. I will ask my company about this.
Expected Behavior
I am expecting a successful ssh connection.
Actual Behavior
ssh: connect to host xx.xxx.xx.220 port 22: Connection timed out
Diagnostic Logs
No response

same here

I had the same problem and it was because of the network, I solved it by following this solution :
Open Command Prompt as an Administrator and type these
netsh winsock reset
netsh int ip reset all
netsh winhttp reset proxy
ipconfig /flushdns
Reboot your machine.

Thanks for reporting this @hockeybrad. Does the command also time out if use ssh.exe on Windows ?
Are you trying to connect to a local ip address ?


Include missing cluster and index privileges

Relates: https://github.com/elastic/elasticsearch-specification/pull/2491#pullrequestreview-1993988824

@pquentin thanks for the review!

I assume this can be fully backported 8.13?

Indeed, though we'd have to sanity check if any of the privileges were added in 8.14. I'm wrapping up a couple of things before going on PTO so might not get to it for ~2 weeks.
Is it all good to merge now, and backport later, once I'm back?

Sounds good! Actually I found https://github.com/elastic/elasticsearch/commits/f5c7938ab8043383aebeac0998a40967da55f924/docs/reference/rest-api/security/get-builtin-privileges.asciidoc which proves that manage_inference, monitor_inference, manage_data_stream_global_retention and monitor_data_stream_global_retention are 8.14 only. I can manage the backport when you're away.


Parsing issues with MetaCoq

At the moment, basically all the files in https://github.com/thomas-lamiaux/generating_recursors creates parsing issue.
I can not exactly isolate a file as it happens from time to time when I open files.
You can check out the issue by cloning the repo, doing make, and trying to check the files in the folder recursors_api.
I am using coq 8.19.2, the associated version of Equations and MetaCoq and vscoq 2.1.7.

Not sure if it is the same, but for my project, the parsing is messed up almost each time I edit something containing utf8 characters like 𝓘 or 𝒯.  The only fix is to reopen vscode, which gets annoying very quickly.

@terencode can you please tell us which version are you on?

@terencode can you please tell us which version are you on?

vscoq 2.2.1

see https://coq.zulipchat.com/#narrow/channel/237662-VsCoq-devs-.26-users/topic/VsCoq.20randomly.20crashes.20when.20opening.20a.20file/near/481334265 for a minimal example.
Basically it happens as soon as there is a file doing
From MetaCoq Require Import Template.All

can you try with https://github.com/coq/coq/pull/19864 ?

It doesn't even work, set_option_value ~stage:Interp (fun _ v -> v) key i sets the option to the current value

Thanks for investigating @SkySkimmer . Should we open an issue in metacoq?

https://github.com/MetaCoq/metacoq/pull/1123

Thomas can you confirm the issue is no more present?

I don't work with the master right now, but I have been confirmed by @MathisBD that it is so I think it is fine closing

Yes the issue is solved in MetaCoq's main branch, you can close

Solved by Gaetan's PR


Caching results to limit requests to APIs

A lot of API guidelines have one thing in common; they either limit the number of requests made per day, or throttle requests, especially in case of free APIs.
In such a case, eventually, users will be unable to avail these services even if they are repeating a query.
For API's where real-time results are not required (eg: movies, books, jokes, wiki) and where caching is not against the policy of using the API, we could maintain a server-side cache of the results.
For queries with randomized results (like jokes, quotes), we could enter a small probability that the joke is picked up from the cache, rather than a new request (of course, this is just an example.. If we use our own joke/quote list, this won't be required, but the principle applies to most other API's we'll use eventually)
Use cases:

I'm trying to decide which book to buy. I ask JARVIS for the rating of Throne of Glass. Then I ask it for Lady Midnight. But being my absent minded self, I forget the rating Throne of Glass had, and so I query it again. But alas, the query limit has been exceeded, and I can't see the rating anymore :disappointed: Must wait till tomorrow to decide.
I have an upcoming math test :scream: I ask JARVIS to tell me about the Pythagoras theorem, but eventually, because of exam stress :books: I forget it. So I ask it again, but alas, Wikipedia has crashed because it's exam time everywhere, and now I'm going to fail :sob:

Hey @havanagrawal, this will actually be quite useful (or more appropriately, required as we expand).
I'll take a look on how to do this, keeping in mind that not all responses can be cached (as you correctly pointed out). Meanwhile, if you get any ideas (approaches), do share on this page.
P.S. Do you use an extension for using those emojis or do you know 'em all? :stuck_out_tongue_winking_eye:

The way I see it, there are two scenarios

Keyword-less queries: Jokes, quotes, etc do not need entities, only intents, so we could maintain a simple dictionary-like cache, with key as (say) "joke", and the value being a queue of the least-recently-shown jokes
Keyword queries: Books, movies, etc have an entity associated with them, and so we'd somehow need to maintain a dictionary-like structure of "book" to entity to actual result. This could quickly get too complex if not designed well.

Not sure how practical this approach would be. Let's see if someone else has any ideas.

I tried using requests-cache , it works perfectly fine!! Can I create a pull request ?


⚠ Bofrost.lu has degraded performance

In ae14c12, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1797 ms

Resolved: Bofrost.lu performance has improved in 4f41b5f after 44 minutes.