image attribution

i should have captioned this on the last PR...

Oh I forgot about this.
The image attribution looks a bit wonky – I wasn't sure if links could be included in the caption that's written on  {% include screen_image_with_caption.html org="moms-rising" caption="Help end the tampon tax" %} and if so, if it needs to be written in some other way or if I can use normal html there too. I was going to test but then didn't come back to it. I can update it it in a bit :)

No hurry! I just wanted to make sure this wasn't held up by a lack of clarity on engineering review.


StudioRack

It's an open-source plugin manager called StudioRack:
https://github.com/studiorack
The aim of the project is to provide a free open-source way to manage plugin dependencies and their versions. It would involve the following steps:
Publish a Github release containing the plugin source along with metadata plugins.json
Tag your Github repository with studiorack-plugin so it can be discovered
Wait for the studiorack-registry to index your plugin (every 24 hours)
Check the registry feed for your plugin to appear

I'm currently can't see any benefit from using StudioRack.
Ready to use binaries been provided on the release page for Linux/windows already here. They comes with the benefit of no external dependency (using PawPaw). Looking at the workflow files from StudioRack it looks that binaries build with them are only usable on up to date distributions and comes with external dependencies to special versions of the used libraries (ubuntu-latest).
While the idea of having a single plugin manager tool online available is nice, it seems that the build system it use didn't cover this idea in regards to Linux. It may work better for Windows and Mac, but still there dependencies needs to be covered by the user.

I'm currently can't see any benefit from using StudioRack. Ready to use binaries been provided on the release page for Linux/windows already here. They comes with the benefit of no external dependency (using PawPaw). Looking at the workflow files from StudioRack it looks that binaries build with them are only usable on up to date distributions and comes with external dependencies to special versions of the used libraries (ubuntu-latest). While the idea of having a single plugin manager tool online available is nice, it seems that the build system it use didn't cover this idea in regards to Linux. It may work better for Windows and Mac, but still there dependencies needs to be covered by the user.

any issues like this should be made as issues on the github repo, the main dev is working hard to get out of alpha and feedback like this is massively helpful.

Sorry, that isn't my part in this game. If you would help to support StudioRack and make it better, you could forward my response from here. I'm myself already have more projects running I could handle. So, for example, if you wish to see support for StudioRack in Ratatouille, fork Ratatoille, add support and make a pull request. I'm not against that, just, I wouldn't spend any time to figure out how it works, test it and implement support for it, as I said, I didn't see any benefit, not for me, nor for users of Ratatouille.


⚠ Samsung has degraded performance

In 7de8957, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2472 ms

Resolved: Samsung performance has improved in 89b2c8b.


Svix Helm Chart

Goal
Deploy Svix with a helm chart.

https://github.com/holaplex/helm-charts/tree/main/charts/svix-server


[Event Request] page 9657 "Customer Report Selections" - OnMapTableUsageValueToPageValueOnCaseElse

Could you please add the following event?
local procedure MapTableUsageValueToPageValue()
var
    CustomReportSelection: Record "Custom Report Selection";
begin
    case Usage of
        CustomReportSelection.Usage::"P.Order":
            Usage2 := Usage2::"Purchase Order";
        CustomReportSelection.Usage::"V.Remittance":
            Usage2 := Usage2::"Vendor Remittance";
        CustomReportSelection.Usage::"P.V.Remit.":
            Usage2 := Usage2::"Vendor Remittance - Posted Entries";
        CustomReportSelection.Usage::"P.Ret.Shpt.":
            Usage2 := Usage2::"Posted Return Shipment";
//+EVENT
        else
            OnMapTableUsageValueToPageValueOnCaseElse(Rec, Usage2);
//-EVENT
    end;
end;

[IntegrationEvent(false, false)]
local procedure OnMapTableUsageValueToPageValueOnCaseElse(Rec: Record "Custom Report Selection"; var CustomReportSelectionSales: Enum "Custom Report Selection Sales")
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


doc: update Effective Go with 1.14 language changes

Fixes #37560
This PR will be imported into Gerrit with the title and first
comment (this text) used to generate the subject and body of
the Gerrit change.

@googlebot I signed it!


Is it possible use FB.ui function?

I'm using the angular-facebook for login, but now I also want to share links. So as the doc says:
FB.ui({
  method: 'share',
  href: 'https://developers.facebook.com/docs/',
}, function(response){});

... I'm wondering how to use the package to share.

Never mind, just use:
Facebook.ui({
      method: 'share',
      quote: '',
      href: ''
    }, function(response) {
      console.log(response);
    });


Bug: Remove same timestamp dependency

Problem
When we compute the blobs related to a given eid to be synced, we relay on the fact that reference blobs and change blobs have the same timestamp to group them together and sync them. In the future this may not be the case and will cause the system to fail
Steps to Reproduce

Expected Behavior
Also, it's going to do a full scan of the table for each row to join, because column is not indexed. And because timestamps are not unique, there can be all sorts of other problems.
See this query for inspiration: https://github.com/seed-hypermedia/seed/blob/48a4bed2a3e789b5c1ab905b17ac1ac591269623/backend/index/index.go#L169
It takes the refs first. And then it follows blob links from refs to changes, and then deps links from changes to other changes.
Debug Info

done c9e8a3b0c4c9f05b33e3ea121b92d442128d3afe


Module

Hi
I saw you are using the detect-node module.
Actually this module is about to be depreciated so I would suggest moving to the nodejs-detector module instead. No API changes needed!

Thanks for opening the issue but we don’t use the mentioned package directly.


Modify applying security to proxy service, API docs

Purpose
Modify applying security to proxy service, API docs

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Chanika Geeganage seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


net/http: serveContent should 500 instead of 404 on error

http's fs.go contains:
        f, err := fs.Open(name)
        if err != nil {
                // TODO expose actual error?
                NotFound(w, r)
                return
        }
        defer f.Close()

        d, err1 := f.Stat()
        if err1 != nil {
                // TODO expose actual error?
                NotFound(w, r)
                return
        }

This bug is about those TODOs.
We should send a 500 instead of a 404. Sending the actual error text is probably too risky (might contain sensitive information). Instead, we could just log it.

Brad it's not quite correct, if error is permission-related, the web-servers normally give 403. Non-existing files return 404.
I can imagine there should be errors that should result in 500 but normally two above should handle most of the cases (*CGI, proxying and SSI are usual suspects for 500)

Sent https://go-review.googlesource.com/9200


Ambiguous spec expressions

In the joint tour frequency and composition component, we have (for example):
https://github.com/ActivitySim/sandag-abm3-example/blob/85c1ecb4e17ad63a87e84aadf56a26d28e1c1488/configs/resident/joint_tour_frequency_composition.csv#L56
This expression is summarized as (bool * bool) + (bool * bool).  The two parenthetical terms each neatly and correctly resolves to a binary value regardless of whether the operands are treated as literal boolean values or their (0,1) numerical equivalent.  However, + operator is not so clean; if both operands are True, we could arrive at different results:

Interpret as numeric, so1 + 1 = 2, or
Interpret as boolean, so True + True = True.

The numexpr engine of pandas.eval will (with arguably good reason) punt on solving this, throwing a NotImplementedError.  Pandas can fall back to numpy logic, which will solve the expression based on the logic (2) and get True.  Sharrow converts the booleans to numbers, using logic (1).
It would be better to write expressions so they are less ambiguous, and (obviously) so they resolve the same with or without sharrow.  Based on context clues from the rest of the spec, it appears the intention of these expressions is following logic (1).  @dhensle can you (or whomever at RSG crafted this spec) confirm the preferred interpretation?

I can answer this since I worked on the initial conversion of joint tour frequency composition model.
This is what's coded in the BayDAG CT-RAMP UEC for the joint tour frequency composition model:

In CT-RAMP, expressions are returned in numeric. A==B returns either numeric 1 or 0, which means this expression should return 0, 1, or 2.
So this expression should be rewritten to follow logic (1).
@dhensle do you agree? If we correct the expressions, it will cause abm3 results to change in the sharrow off mode, perhaps slightly, depending on how many 2+ joint tour households are there.

Yes, agreed.  We should be replicating the original CT-RAMP logic/results.
cc: @aletzdy


Healthcare smart contract

Smart contract for issuing and filing of medical prescriptions.

This is not related to TDLib.


chaosblade-operator  panic because of runtime error: slice bounds out of range [:12] with length 0

Issue Description
Type: bug report or feature request
bug report
Describe what happened (or what feature you want)
When executing jvm process experiment, panic occurred.
errors:
：time="2022-03-17T13:21:30Z" level=info msg="get pods by names prod-docker-a-dep1-55f4f6597f-jtx8s, len is 1" experiment=h-hs-sirius-01b1647522974062nweewgovov-prod-docker-a-dep1-55f4f6597f-jtx8s
E0317 13:21:30.399143 7 runtime.go:78] Observed a panic: runtime.boundsError{x:12, y:0, signed:true, code:0x1} (runtime error: slice bounds out of range [:12] with length 0)
goroutine 659 [running]:
k8s.io/apimachinery/pkg/util/runtime.logPanic({0x14707c0, 0xc01901f5a8})
/Users/wufan/go/pkg/mod/k8s.io/apimachinery@v0.17.4/pkg/util/runtime/runtime.go:74 +0x99
k8s.io/apimachinery/pkg/util/runtime.HandleCrash({0x0, 0x0, 0xc009718400})
Describe what you expected to happen
   no panic occurs. the containerStatus.ContainerID field should not be empty

How to reproduce it (as minimally and precisely as possible)
This doesn't happen every time, just random occurs.

Tell us your environment
k8s: 1.18.9
container runtime: docker
run jvm process experiment
Anything else we need to know?
 When running experiment, pod is in ready state, no restart.

This happens when triggering rate limit, the default qps and burst setting is small


ubuntu-cx11-02: Am 12.10.21 um 08:01: Transport endpoint is not connected

●<EMAIL_ADDRESS>loaded failed failed Syncthing - Open Source Continuous File Synchronization for root

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

Due to #417


Resolved issue #173 - preventing AIA upload as media asset

Resolved issue detailed at https://github.com/mit-cml/appinventor-sources/issues/173 and replaced window.alerts with gwt dialog boxes.
@afmckinney @jisqyv

@varunm22 See line note above.

Hi @jisqyv, I fixed up the code with your suggestions, please let me know if there's anything else I can improve!

@varunm22 Looks good... except... If you look at other components, you will see we use ALL UPPER CASE for enum values. Can you make that change?

@jisqyv I fixed it, thanks!

Thanks. I'll do my final testing this evening and if all goes well I'll
merge it into the master branch.
-Jeff
On Sat, Apr 30, 2016, 11:55 PM Varun Mangalick<EMAIL_ADDRESS>wrote:

@jisqyv https://github.com/jisqyv I fixed it, thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/mit-cml/appinventor-sources/pull/747#issuecomment-216014580

@varunm22 LGTM
There are some whitespace errors, but I'll take care of these when I squash things down for Gerrit

@varunm22 MERGED


Account forms slight refactor

Use new form helpers

Coverage: 93.521% (+0.008%) from 93.512% when pulling 233c6fdb58e06fe3613aa60da1a6aff660697477 on nimmo-account-forms-slight-refactor into d83cbab5933f7bae63e234c00b7932e03b428b97 on main.


Add cache use examples

Is your feature request related to a problem? Please describe.
Understand how and when to use the different cache implementations available in the framework
Describe the solution you'd like
Showcase the different memory strategies in action with examples

Done: https://github.com/i-am-bee/bee-agent-framework/blob/main/docs/cache.md


Jcaccamo/update closest faclilty name

@ldanzinger Ready for review. Just updating the name of the samples.
Also came across some inconsistencies in the comments at the top of the file. Does the value for "WriteFile Name=" matter? I updated them for consistency. Let me know if I need to revert it back.

looks good. Let's hold still until after the release to merge

@jared-esri I believe those tags no longer matter. They used to be used for the doc build for pulling snippets. I'm not sure that they are any longer.

@ldanzinger I'll leave the change in then. 👍

@jared-esri this one can be merged now that the code base is open


Windows commands inside WSL hang forever

Version
WSL <IP_ADDRESS>
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
Ubuntu 20.04.3 LTS
Other Software
No response
Repro Steps
I'm not sure what went wrong nor how to debug this. It was working fine before but all of a sudden I stopped being able to use windows commands from inside WSL. notepad.exe, wsl.exe, etc they all just hang forever and not even Ctrl+C is able to kill them and I'm forced to close the terminal.
Expected Behavior
Can use windows commands from inside WSL (e.g. wsl.exe --version)
Actual Behavior
Windows commands (e.g. wsl.exe --version) hang forever and not even Ctrl+C is able to kill them and I'm forced to close the terminal.
Diagnostic Logs
nodepad.exe
$ strace notepad.exe
execve("/mnt/c/Windows/system32/notepad.exe", ["notepad.exe"], 0x7fff357161e0 /* 37 vars */) = 0
arch_prctl(ARCH_SET_FS, 0x378290)       = 0
set_tid_address(0x3782c8)               = 400
brk(NULL)                               = 0xf79000
brk(0xf7a000)                           = 0xf7a000
brk(0xf7b000)                           = 0xf7b000
gettid()                                = 400
gettid()                                = 400
gettid()                                = 400
gettid()                                = 400
brk(0xf7c000)                           = 0xf7c000
brk(0xf7d000)                           = 0xf7d000
brk(0xf7e000)                           = 0xf7e000
sched_getaffinity(0, 128, [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11]) = 32
getpid()                                = 400
getcwd("/home/tiago", 4096)             = 12
uname({sysname="Linux", nodename="DESKTOP-VN589IP", ...}) = 0
getcwd("/home/tiago", 4096)             = 12
open("/mnt/c/Windows/system32/notepad.exe", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_PATH) = 3
readlink("/proc/self/fd/3", "/mnt/c/Windows/system32/notepad."..., 4095) = 35
fstat(3, {st_mode=S_IFREG|0555, st_size=348160, ...}) = 0
stat("/mnt/c/Windows/system32/notepad.exe", {st_mode=S_IFREG|0555, st_size=348160, ...}) = 0
close(3)                                = 0
open("/proc/self/mountinfo", O_RDONLY)  = 3
readv(3, [{iov_base="", iov_len=0}, {iov_base="68 72 0:26 / /mnt/wsl rw,relatim"..., iov_len=1024}], 2) = 1024
readv(3, [{iov_base="", iov_len=0}, {iov_base="- tmpfs none rw,mode=755\n96 95 0"..., iov_len=1024}], 2) = 1024
readv(3, [{iov_base="", iov_len=0}, {iov_base="ev,noexec,relatime - cgroup cgro"..., iov_len=1024}], 2) = 1024
readv(3, [{iov_base="", iov_len=0}, {iov_base="66 / /mnt/c rw,noatime - 9p drvf"..., iov_len=1024}], 2) = 270
readv(3, [{iov_base="", iov_len=0}, {iov_base="", iov_len=1024}], 2) = 0
close(3)                                = 0
getcwd("/home/tiago", 4096)             = 12
open("/proc/self/mountinfo", O_RDONLY)  = 3
readv(3, [{iov_base="", iov_len=0}, {iov_base="68 72 0:26 / /mnt/wsl rw,relatim"..., iov_len=1024}], 2) = 1024
readv(3, [{iov_base="", iov_len=0}, {iov_base="- tmpfs none rw,mode=755\n96 95 0"..., iov_len=1024}], 2) = 1024
readv(3, [{iov_base="", iov_len=0}, {iov_base="ev,noexec,relatime - cgroup cgro"..., iov_len=1024}], 2) = 1024
readv(3, [{iov_base="", iov_len=0}, {iov_base="66 / /mnt/c rw,noatime - 9p drvf"..., iov_len=1024}], 2) = 270
readv(3, [{iov_base="", iov_len=0}, {iov_base="", iov_len=1024}], 2) = 0
close(3)                                = 0
ioctl(0, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(1, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(2, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(0, TIOCGPGRP, [397])              = 0
getpgid(0)                              = 397
fstat(0, {st_mode=S_IFCHR|0620, st_rdev=makedev(0x88, 0), ...}) = 0
fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(0x88, 0), ...}) = 0
fstat(2, {st_mode=S_IFCHR|0620, st_rdev=makedev(0x88, 0), ...}) = 0
ioctl(0, TIOCGWINSZ, {ws_row=39, ws_col=166, ws_xpixel=0, ws_ypixel=0}) = 0
ioctl(0, SNDCTL_TMR_START or TCSETS, {B38400 -opost -isig -icanon -echo ...}) = 0
                                                                                dup(0)                                  = 3
                                                                                socket(AF_VSOCK, SOCK_STREAM|SOCK_CLOEXEC, 0) = 4
       bind(4, {sa_family=AF_VSOCK, sa_data="\0\0\377\377\377\377\377\377\377\377\0\0\0\0"}, 16) = 0
                                                                                getsockname(4, {sa_family=AF_VSOCK, sa_data="\0\0\343\221\264\332\377\377\377\377\0\0\0\0"}, [16]) = 0
                                    listen(4, 4)                            = 0
                                                                               socket(AF_UNIX, SOCK_SEQPACKET|SOCK_CLOEXEC, 0) = 5
                                                                                connect(5, {sa_family=AF_UNIX, sun_path="/run/WSL/350_interop"}, 110) = 0
                                     write(5, "\6\0\0\0006\1\0\0\343\221\264\332\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 310) = 310
                                                                                poll([{fd=4, events=POLLIN}], 1, 10000) = 1 ([{fd=4, revents=POLLIN}])
                                        accept4(4, {sa_family=AF_VSOCK, sa_data="\0\0]c\317O\2\0\0\0\0\0\0\0"}, [16], SOCK_CLOEXEC) = 6
                                                                                poll([{fd=4, events=POLLIN}], 1, 10000) = 1 ([{fd=4, revents=POLLIN}])
                                       accept4(4, {sa_family=AF_VSOCK, sa_data="\0\0^c\317O\2\0\0\0\0\0\0\0"}, [16], SOCK_CLOEXEC) = 7
                                                                                poll([{fd=4, events=POLLIN}], 1, 10000) = 1 ([{fd=4, revents=POLLIN}])
                                      accept4(4, {sa_family=AF_VSOCK, sa_data="\0\0_c\317O\2\0\0\0\0\0\0\0"}, [16], SOCK_CLOEXEC) = 8
                                                                                poll([{fd=4, events=POLLIN}], 1, 10000) = 1 ([{fd=4, revents=POLLIN}])
                                     accept4(4, {sa_family=AF_VSOCK, sa_data="\0\0`c\317O\2\0\0\0\0\0\0\0"}, [16], SOCK_CLOEXEC) = 9
                                                                                close(4)
      = 0
         rt_sigprocmask(SIG_BLOCK, [INT WINCH], NULL, 8) = 0
                                                            signalfd4(-1, [INT WINCH], 8, 0)        = 4
                                                                                poll([{fd=0, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8, events=POLLIN}, {fd=9, events=POLLIN}, {fd=4, events=POLLIN}], 5, -1

wsl.exe --version
$ strace wsl.exe --version
execve("/mnt/c/Windows/system32/wsl.exe", ["wsl.exe", "--version"], 0x7fff7408be88 /* 37 vars */) = 0
arch_prctl(ARCH_SET_FS, 0x378290)       = 0
set_tid_address(0x3782c8)               = 282
brk(NULL)                               = 0x2100000
brk(0x2101000)                          = 0x2101000
brk(0x2102000)                          = 0x2102000
gettid()                                = 282
gettid()                                = 282
gettid()                                = 282
gettid()                                = 282
brk(0x2103000)                          = 0x2103000
brk(0x2104000)                          = 0x2104000
brk(0x2105000)                          = 0x2105000
sched_getaffinity(0, 128, [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11]) = 32
getpid()                                = 282
getcwd("/home/tiago", 4096)             = 12
uname({sysname="Linux", nodename="DESKTOP-VN589IP", ...}) = 0
getcwd("/home/tiago", 4096)             = 12
open("/mnt/c/Windows/system32/wsl.exe", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_PATH) = 3
readlink("/proc/self/fd/3", "/mnt/c/Windows/system32/wsl.exe", 4095) = 31
fstat(3, {st_mode=S_IFREG|0555, st_size=172032, ...}) = 0
stat("/mnt/c/Windows/system32/wsl.exe", {st_mode=S_IFREG|0555, st_size=172032, ...}) = 0
close(3)                                = 0
open("/proc/self/mountinfo", O_RDONLY)  = 3
readv(3, [{iov_base="", iov_len=0}, {iov_base="68 72 0:26 / /mnt/wsl rw,relatim"..., iov_len=1024}], 2) = 1024
readv(3, [{iov_base="", iov_len=0}, {iov_base="- tmpfs none rw,mode=755\n96 95 0"..., iov_len=1024}], 2) = 1024
readv(3, [{iov_base="", iov_len=0}, {iov_base="ev,noexec,relatime - cgroup cgro"..., iov_len=1024}], 2) = 1024
readv(3, [{iov_base="", iov_len=0}, {iov_base="66 / /mnt/c rw,noatime - 9p drvf"..., iov_len=1024}], 2) = 270
readv(3, [{iov_base="", iov_len=0}, {iov_base="", iov_len=1024}], 2) = 0
close(3)                                = 0
getcwd("/home/tiago", 4096)             = 12
open("/proc/self/mountinfo", O_RDONLY)  = 3
readv(3, [{iov_base="", iov_len=0}, {iov_base="68 72 0:26 / /mnt/wsl rw,relatim"..., iov_len=1024}], 2) = 1024
readv(3, [{iov_base="", iov_len=0}, {iov_base="- tmpfs none rw,mode=755\n96 95 0"..., iov_len=1024}], 2) = 1024
readv(3, [{iov_base="", iov_len=0}, {iov_base="ev,noexec,relatime - cgroup cgro"..., iov_len=1024}], 2) = 1024
readv(3, [{iov_base="", iov_len=0}, {iov_base="66 / /mnt/c rw,noatime - 9p drvf"..., iov_len=1024}], 2) = 270
readv(3, [{iov_base="", iov_len=0}, {iov_base="", iov_len=1024}], 2) = 0
close(3)                                = 0
ioctl(0, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(1, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(2, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(0, TIOCGPGRP, [279])              = 0
getpgid(0)                              = 279
fstat(0, {st_mode=S_IFCHR|0620, st_rdev=makedev(0x88, 0x1), ...}) = 0
fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(0x88, 0x1), ...}) = 0
fstat(2, {st_mode=S_IFCHR|0620, st_rdev=makedev(0x88, 0x1), ...}) = 0
ioctl(0, TIOCGWINSZ, {ws_row=39, ws_col=166, ws_xpixel=0, ws_ypixel=0}) = 0
ioctl(0, SNDCTL_TMR_START or TCSETS, {B38400 -opost -isig -icanon -echo ...}) = 0
                                                                                dup(0)                                  = 3
                                                                                socket(AF_VSOCK, SOCK_STREAM|SOCK_CLOEXEC, 0) = 4
       bind(4, {sa_family=AF_VSOCK, sa_data="\0\0\377\377\377\377\377\377\377\377\0\0\0\0"}, 16) = 0
                                                                                getsockname(4, {sa_family=AF_VSOCK, sa_data="\0\0\333\221\264\332\377\377\377\377\0\0\0\0"}, [16]) = 0
                                    listen(4, 4)                            = 0
                                                                               socket(AF_UNIX, SOCK_SEQPACKET|SOCK_CLOEXEC, 0) = 5
                                                                                connect(5, {sa_family=AF_UNIX, sun_path="/run/WSL/244_interop"}, 110) = 0
                                     write(5, "\6\0\0\08\1\0\0\333\221\264\332\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 312) = 312
                                                                                poll([{fd=4, events=POLLIN}], 1, 10000) = 1 ([{fd=4, revents=POLLIN}])
                                      accept4(4, {sa_family=AF_VSOCK, sa_data="\0\0\32c\317O\2\0\0\0\0\0\0\0"}, [16], SOCK_CLOEXEC) = 6
                                                                                poll([{fd=4, events=POLLIN}], 1, 10000) = 1 ([{fd=4, revents=POLLIN}])
                                       accept4(4, {sa_family=AF_VSOCK, sa_data="\0\0\33c\317O\2\0\0\0\0\0\0\0"}, [16], SOCK_CLOEXEC) = 7
                                                                                poll([{fd=4, events=POLLIN}], 1, 10000) = 1 ([{fd=4, revents=POLLIN}])
                                        accept4(4, {sa_family=AF_VSOCK, sa_data="\0\0\34c\317O\2\0\0\0\0\0\0\0"}, [16], SOCK_CLOEXEC) = 8
                                                                                poll([{fd=4, events=POLLIN}], 1, 10000) = 1 ([{fd=4, revents=POLLIN}])
                                         accept4(4, {sa_family=AF_VSOCK, sa_data="\0\0\35c\317O\2\0\0\0\0\0\0\0"}, [16], SOCK_CLOEXEC) = 9
                                                                                close(4)
            = 0
               rt_sigprocmask(SIG_BLOCK, [INT WINCH], NULL, 8) = 0
                                                                  signalfd4(-1, [INT WINCH], 8, 0)        = 4
                                                                                poll([{fd=0, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8, events=POLLIN}, {fd=9, events=POLLIN}, {fd=4, events=POLLIN}], 5, -1

This seems to happen most frequently after using vscode -- maybe something related to the WSL remote extension?

Interesting, we will probably need the /logs from the Windows side. Coud you please share those?

I can confirm that I noticed the same issue. Quiet strange behavior, the first one or two times calling and windows executable works like a charm. Afterwards the behavior described by @siferati kicks in and only rebooting the system fixes it for now (did not try to dig deeper).
@benhillis if you could provide an email where I could send the logs (recorded with: wpr -start wsl.wprp -filemode) to I would happily contribute the file. But I would rather not share this openly on GitHub.

The logs can be attached here or in Feedback Hub as explained here https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs

The logs can be attached here or in Feedback Hub as explained here master/CONTRIBUTING.md#8-collect-wsl-logs

I've read that but did recorded it manually. Therefore I ask for an email as @craigloewen-msft  did provide such email earlier on in some networking related issue.

windows logs: logs.zip
Sorry they're so long... I still haven't found a way to reliably trigger the issue, so I had to do random stuff for 10min until it eventually happened. I stopped recording once the problem occurred, so the relevant logs should be the most recent ones.

Some more info I found about the issue:
When this issue happens, if I run windows commands (e.g. wsl.exe --version) in a linux path (e.g. /home/username) it will hang forever like I described above. But if I run the command inside /mnt/c then it will work as expected.

@siferati by any chance you're using wsl2-ssh-pageant, npipe or similar tools automated at launch in combination with socat? I'm currently suspecting this as the root cause of breaking it, I've removed it for now and try to replicate the issue.

I'm not using any of those tools AFAIK. The only thing I changed about launching wsl is running the docker daemon as described in https://docs.microsoft.com/en-us/windows/wsl/wsl-config#boot-settings

I've found #7754 which sounds exactly like this issue. Maybe it's a good idea to mark this as duplicate.

This happens to me daily when I try to launch VS Code using code . from WSL. It also happens with one of my VS Code extensions that shells out to Powershell to do manipulate the Windows clipboard. From the linked #7754 thread, this seems to only be happening with the store installed version. Is there a recommended way to revert from the store version to the inbox version? Or should I just uninstall the store version?

Thanks for the logs, I'll start looking at this.

For me the loss of interoperability happened for both the non-store and the latest store version. What happens is that my PHPStorm loses all Git functionality. The file I/O then stays ok, so PHPStorm still alows me to make edits. Restarting PHPStorm to see if Git interactions becomes available then crashes the entire IDE.
When I/O interoperability is lost, I am unable to navigate to the mount from Explorer, nor am I able to start a new terminal and log into wsl by running the wsl command.
Interesting here is that the terminal session that I have open in PHPStorm at that moment keeps open, and still allows me to run commands.
Found out that non-store wsl versions can solely update the kernel from the command line without upgrading to the store version by running wsl --update --inbox

Hitting this one daily running code ./blah and with Git credential manager, the later I can mostly mitigate by using SSH for Git but it's still a huge pain

The work-around is to uninstall the store-version of WSL and revert to the "system" version.

This workaround is not confirmed to work for everyone, myself included.

@dhowett this is the one

Thanks to everyone who submitted logs.
We've made some progress on the issue, but we need more diagnostics to root cause it.
Instructions once you have a repro (elevated command prompt):
curl.exe https://raw.githubusercontent.com/microsoft/terminal/main/src/Terminal.wprp > Terminal.wpr
wpr.exe -start Terminal.wprp!DefTerm  -filemode

[Start a windows process from wsl, make sure it hangs, then wait a couple seconds]

wpr.exe -stop logs.etl

Then using the task manager, check if the process is actually running on the Windows side, if it is, dump it (under the 'details tab', right click, then 'create dump file'). Do the same for all conhost.exe processes running on the machine.
Then reply to this issue with logs.etl and the dumps of all the above processes, if any. Please also include your Windows build number, and the output of wsl --version

@OneBlue your command has a typo: the curl should be done to a file named Terminal.wprp
I wasn't able to record the logs, when I run the command I get error code: 0xc00ce56f switch from current encoding to specified encoding not supported
I was trying to run notepad.exe but it did not show in the task manager. I uploaded the dumps from conhost to gdrive (too big to upload here).
WSL: <IP_ADDRESS>
kernel: <IP_ADDRESS>
WSLg: 1.0.30
Windows: 10.0.22000.434

Thanks @siferati. Fixed the typo :).
Interesting, did Terminal.wprp get downloaded correctly ? If the process isn't created at all the logs would be what we need.
Maybe you have another trace running ? What if you try to run wpr.exe -stop logs.etl to stop any pre-existing tracing ?

Managed to fix the encoding error by replacing UTF-8 with UTF-16.
logs.zip

I've also started experiencing this issue in the last week. Seems to also be related to web servers running in WSL not responding to requests.
logs.zip
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.30
Windows version: 10.0.22000.376

New WSL version was released! https://github.com/microsoft/WSL2-Linux-Kernel/releases/tag/linux-msft-wsl-<IP_ADDRESS>
Would the following release notes that were included possibly relate to fixes for this bug?

Switched Dxgkrnl Version to 2111
Removed the limit of existing and total sysmem allocations
Properly flush the device for termination during process cleanup
Fixed SPDX-License-Identifier for d3dkmthk.h

Update: we're still actively investigating this issue.
We know that the problem is between the Plan9 client on the host and the server that runs in WSL2, but we don't know what triggers this 'stuck' state yet. I'll update this issue when we'll have more info.

Here are my logs just in case they could help. These were dumped with three windows processes in the blocked state: 1 x docker.exe (via docker desktop for windows), 2 x cmd.exe, all started from my WSL home directory.
logs.zip
wsl --status
Default Distribution: ubu2004
Default Version: 2
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.30
Windows version: 10.0.22000.526

Thanks a lot to everyone who posted logs and helped with this investigation.
We have found the root cause: A bug in p9rdr.sys (the plan 9 redirector driver), which handles the \\wsl$\<distro> file accesses.
The bug causes a transaction to be left in a pending state forever, which is why this only happens to Windows commands running inside the wsl filesystem (since the programs try to access their current directories, which would in this case be under \\wsl$\<distro>).
The fix has been checked in to the Windows codebase, and will work its way through Windows release pipeline.
I'll update the issue when I'll have the Windows build numbers with the fix.

@OneBlue will the fix coming also in the Insider Dev channel? Can we expect it in the next week build?

@maicol07 are you sure that it's not just a placebo?

@Ansuel I've tried it for a few hours and processes aren't stuck. For this reason I've written "it seems". We need some other confirms to declare this issue permanently (I hope) fixed!

The thing is that it's strange that a fix of 9 days ago has already been merged. Let's hope you are right!

Dev builds are based on mainstream Windows, so they should include all the changes done from the current one to the next one

@OneBlue will the fix also come in the Insider Dev channel? Can we expect it in the next week build?

The fix hasn't shipped yet. I'll update this thread with the build numbers when it will be in the Dev channel.

OK, this is really strange, as I've had the same problems as other people have reported here - code . from WSL would hang, accessing \\wsl$\Ubuntu\home\myuser would hand, etc.
I went to the Security and Maintenance control panel, and Maintenance told me I needed to install a device driver. Didn't mention which driver, but I allowed it to, restarted my machine, and now everything is working?

Cause probably the bug was triggered every time after the reboot. Again it's random, now we just have to wait as this has been fixed.

Question - Is the bug fix mentioned above being distributed via the store "windows subsystem for linux preview" app on non-insider win11 installs or via an update to the "turn windows features on or off" | "windows subsystem for linux" option for those on dev, beta or release train insider installs?

@myusrn: The fix is in a Windows driver that's part of Windows (p9rdr.sys) and so doesn't ship with the WSL app. The only way to get it is via Windows update.

If I have all of the current microsoft update offered updates installed on my win11 enterprise release [ 22000.556 ] install.
The $env:windir/system32/drivers/p9rdr.sys | alt+enter | details shows version 10.0.22000.1 and digital signature tab shows Friday June 4, 2021 7:51:52 PM.
Will i only receive the p9rdr.sys driver update with proposed fix for this matter if i'm configured for dev or beta or release preview insider track updates?

Any update on when the Plan 9 redirector driver fix will get shiped via Windows Update? Can we manually already install the fix?

. . . and is there a way to restart the driver without a full reboot before the fix is available?

Considering you guys can just use the wsl from the system instead (to workaround the regression) of the store version is it that hard to wait? o.o
I mean you can also workaround this by simply using vscode remote extension

@Ansuel somewhere earlier in this thread it was suggested that reverting to the turn windows features on and off | windows subsystem for linux = checked installation option wasn't a guaranteed fix for the issue.
If it is do you know if you also have to remove the microsoft store | windows subsystem for linux preview app install after enabling that OS feature, followed by a reboot, in order for the system32/p9np.dll+p9rdrservice.dll+drivers/p9rdr.sys stability fix to take effect?
What does "workaround this by simply using vscode remote extension" mean?  When my p9 functionality breaks attempting to execute "code ." from wsl distro cli is also broken.

Given that the fix is unrelated to wsl, that means the earlier confirmations that rolling back to the non-store version did not work are valid.

Given that the fix is unrelated to wsl, that means the earlier confirmations that rolling back to the non-store version did not work are valid.

I have to say it did work for me 🤷🏻♂ I was hitting this (or some similar) issue daily. Multiple times. An hour or two (at most) of using some JetBrains IDE or VS Code accessing files via the Plan 9 FS was enough for the \wsl$ mount to become completely unresponsive and unfixable any other way than rebooting.
After I removed the WSL Preview from MS Store altogether and re-installed the Windows Subsystem for Linux "Windows feature", I haven't hit the issue once for more than a month now. I'm running a non-insider Windows 11 build (22000.556) though.

What does "workaround this by simply using vscode remote extension" mean? When my p9 functionality breaks attempting to execute "code ." from wsl distro cli is also broken.

@myusrn If you use the Remote - WSL extension, code . runs a local vscode-server instance on the WSL distro and doesn't use Plan 9 for file access. Used it all the time when I was hitting this bug...

@Ansuel somewhere earlier in this thread it was suggested that reverting to the turn windows features on and off | windows subsystem for linux = checked installation option wasn't a guaranteed fix for the issue.
If it is do you know if you also have to remove the microsoft store | windows subsystem for linux preview app install after enabling that OS feature, followed by a reboot, in order for the $env:windir/system32/p9np.dll, p9rdrservice.dll and drivers/p9rdr.sys stability fix to take effect?
What does "workaround this by simply using vscode remote extension" mean? When my p9 functionality breaks attempting to execute "code ." from wsl distro cli is also broken.

yes you need to obviously remove the wsl store app.............

1 month this was fixed in Windows code but it hasn't been shipped yet...

Waiting for this one so long!

same, I had this issue for many months, it made me dualboot linux again

Don't mind me. I'm just one more guy telling Microsoft that there are thousands of developers desperately waiting for the rollout of this fix...

Don't mind me. I'm just one more guy telling Microsoft that there are thousands of developers desperately waiting for the rollout of this fix...
https://youtrack.jetbrains.com/issue/IDEA-276250

@kohlerdominik I believe the issue you reference is a different one, namely wsl.exe runs leaving behind stale interop sockets in /run/WSL. That can be worked around rather easily by periodically pruning sockets whose matching processes aren't around anymore. No reboot of host is necessary to make the distro work smoothly again.
Reading the comments (and workarounds) posted there suggest some people are actually hitting this issue, instead of the one they're commenting under, though. As mentioned earlier, removing the preview version of WSL and re-installing the bundled version (along with a kernel update) is worth trying, though YMMV...

Update on this issue:
It turns out that this problem is actually composed of 3 bugs:
1) The p9rdr.sys bug I mentioned earlier
2) A bug in WSL's linux plan9 server that would cause sockets to sometimes be dropped when a new client connects
3) A bug in WSL's init process that causes error logs from the plan9 server to go to /dev/null instead of dmesg.
Explanation:
1) is what causes the actual 'hang', but it can only be triggered if the server closes the socket right after the connection is established (so only happens when 2) happens). And because of 3), there were no records of 2) happening, which 'hid' where the issue actually came from.
While 1) is part of the Windows image (and the fix hasn't shipped to insider builds yet), 2) an 3) have been fixed in the latest store WSL release that we just published today (0.58.0). With those fixes, the code path that triggers 1) shouldn't be reached anymore, so the issue should go away.
Note that 2) is also present is the inbox version of WSL (although it appears to hit less frequently than with the store version). We have also checked-in fix to the Windows image, but it hasn't shipped yet.
TL; DR: The fix is available in the latest Store WSL (0.58.0)

Well done @OneBlue debugging this to completion, this was definitely a tricky one.

How we can update if we are not insider
Is this one: Kernel version: <IP_ADDRESS> ?

You need to install https://www.microsoft.com/store/productId/9P9TQF7MRM4R which will then install the version, @OneBlue mentioned. Been running for a couple of hours now and I had no issues so far.

Hi All! Thanks a lot for the fixes landed. With the new released version, would there be a preferred way to access the distros filesystems between \\wsl.localhost and \\wsl$ ?

Fyi, i had the windows wsl feature enabled as work around until fix came out.  After announcement above i installed the windows store preview mentioned above and then unchecked/removed the windows wsl feature and then rebooted.  After that the wsl --version command produces the following output confirming install of the wsl preview store app that have the fixes in place.  So for file explorer access to \\wsl.localhost and \\wsl$ paths has been working without any hangs eventually showing up.
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.32
MSRDC version: 1.2.2924
Direct3D version: 1.601.0
Windows version: 10.0.22000.593

Update on this issue:
It turns out that this problem is actually composed of 3 bugs:

The p9rdr.sys bug I mentioned earlier 2) A bug in WSL's linux plan9 server that would cause sockets to sometimes be dropped when a new client connects 3) A bug in WSL's init process that causes error logs from the plan9 server to go to /dev/null instead of dmesg.

Explanation:

is what causes the actual 'hang', but it can only be triggered if the server closes the socket right after the connection is established (so only happens when 2) happens). And because of 3), there were no records of 2) happening, which 'hid' where the issue actually came from.

While 1) is part of the Windows image (and the fix hasn't shipped to insider builds yet), 2) an 3) have been fixed in the latest store WSL release that we just published today (0.58.0). With those fixes, the code path that triggers 1) shouldn't be reached anymore, so the issue should go away.
Note that 2) is also present is the inbox version of WSL (although it appears to hit less frequently than with the store version). We have also checked-in fix to the Windows image, but it hasn't shipped yet.
TL; DR: The fix is available in the latest Store WSL (0.58.0)

@OneBlue
When the p9rdr.sys bug‘s fix ship to windows update? The bug still reproduce but very few times after I upgrade WSL from msstore.

I updated to the latest version but it stills hangs every time I open a 2nd big project in PHPStorm with both project files located in \wsl$\Ubuntu\home\alex.... I am not trying to disable phpcs Inspection, which also located inside \wsl$. I think that it created numerous temporary files and seems better. I don't know if this is a wsl, jetbrains or a phpcs bug.
It's not even possible to do wsl --shutdown now. My windows hang for minutes and new ubuntu cli don't respond.

@alexbogias Why do you think it's related to this issue? I don't see any indication in your posts that it is. Have you tried reaching out to JetBrains support? I see you commented under https://youtrack.jetbrains.com/issue/IDEA-276250, but hadn't even said if you did try the workaround mentioned there or not... And that issue seems to be an altogether different one than this one, despite some people mixing the two together in the comments...

Phpstorm acts differently now with the latest wsl update, thats why.

@alexbogias Doesn't that, on the contrary, mean, that your problems are no longer related to this issue?

I think its more than one bug to be honest. And yes it looks like there are also jetbrains bug related :(

Yes, your problems are/were likely caused by multiple bugs jumbled together. But have you actually read through the whole https://youtrack.jetbrains.com/issue/IDEA-276250 issue and its comments where you posted? There are clear workarounds mentioned that most likely work for your problems too. And even though there probably is another WSL issue involved, it's not related to this particular WSL issue, but something along the lines of https://github.com/microsoft/WSL/issues/7252...

One day, I hope the projects that first instigated users to just use the issue tracker in place of a regular user group will go down in history books for the slippery slope they put all of us on...

I am not really sure if that matters, but after uninstalling both WSL preview and WSLg preview from "add & remove programs (settings)" and did a wsl --update again, everything works more stable :S

默认分发: Ubuntu
默认版本: 2
WSL 版本： <IP_ADDRESS>
内核版本： <IP_ADDRESS>
WSLg 版本： 1.0.39
MSRDC 版本： 1.2.3213
Direct3D 版本： 1.601.0
DXCore 版本： 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows版本： 10.0.22000.739
@OneBlue I reproduced this problem on a new version, is it only fixed on 0.58.0

When is this going to be fixed? There's a lot of pain in the Jetbrains community, it's horror to have to reboot Windows a couple of time each day when the WSL freeze happens.

@schiorean the issue has been fixed some months ago in WSL v0.58.0.
Can you check if your WSL installation is more recent than 0.58.0?

Looks like it's not fixed, I'm running 0.66.2. Or it's another related bug, but the symptom is the same: WSL (and WSL commands) freezes and the only way to make it work again is to restart the computer.

Looks like it's not fixed, I'm running 0.66.2. Or it's another related bug, but the symptom is the same: WSL (and WSL commands) freezes and the only way to make it work again is to restart the computer.

It's another bug and probably not even related to this one. The symptoms are not the same: WSL itself never froze due to this bug, the distro itself was running just fine, only the interoperability with Windows was lost.
This bug has been fixed. I haven't had it occur once since 0.58.0.

Same here running <IP_ADDRESS> and have to reboot mostly after my Suface Book was in standby. @schiorean have you found or created an issue for that?

@cubic3d no I didn't find or add a new issue. I added the issue on the Jetbrains side.

@cubic3d Created a new issue on Github with complete WSL logs https://github.com/microsoft/WSL/issues/8824.

for me the problem was solved, just by adding the .gradle folder to the ignore/exclude list of the windows defender security setting:

for me the problem was solved, just by adding the .gradle folder to the ignore/exclude list of the windows defender security setting:

@sufius now that it's been a couple of weeks - was that the root cause for you? Did excluding from windows defender make the difference?

@nrclark Yes, my problem was solved by this exclusion.


How to: Is there a way to display and sort query_result with several data

My query_result is
{family="Chrome"}<PHONE_NUMBER>36294<PHONE_NUMBER>000
{family="GoogleBot"}<PHONE_NUMBER>327997<PHONE_NUMBER>000
{family="BingBot"}<PHONE_NUMBER>8313124<PHONE_NUMBER>000

I would like to see something like this:
Top - 10
Chrome = 57%
GoogleBot =  30%
BingBot = 12%

@rmalenko I believe you can do it using Data Source and Transformations to get percentage for each and sort by to get Top 10. Then display results using Dynamic Text Panel.
Will it work for you?

@rmalenko Please let us know if there is anything else.
We are wrapping up a new version of the Dynamic Text Panel and planning to release over the weekend.


Feature Request: Rename assist for modules

It would be nice, If we could rename a module through assist, For example:
// src/foo.rs
mod foo; // renamed with `bar`

Would transform into.
// src/foo.rs -> src/bar.rs   |   src/foo/mod.rs -> src/bar/mod.rs
mod bar;

Although, renaming module  feature is supported,
But there should be a assist for that.

Renaming the foo symbol using f2 or "rename symbol" will rename the file too.

Thanks @bjorn3, I didn't know that, So closing...


Mastodon support

Seeing as so many people are frequenting mastodon now it would be really nice to have a mastodon button as well. I've yet to see a single library add support since a mastodon share button would require a modal or something to enter your instance address, which tends to upset the simple "click and go" flow.

Hey! I'll take a look at the issue soon. I think the interface should look like this:
interface IMastodonShareOptions {
  domain?: string
  text?: string;
  url?: string;
}

Leave the modal window to users, as the design may not be suitable.

Seems great :) would love to see this get added for sure. Thanks for the quick response.

Available in v2.0.0 for vue 3
<template>
  <s-mastodon
    :window-features="windowFeatures"
    :share-options="shareOptions"
    :use-native-behavior="useNativeBehavior"
    @popup-close="onClose"
    @popup-open="onOpen"
    @popup-block="onBlock"
    @popup-focus="onFocus"
  ></s-mastodon>
</template>

<script>
  import { SMastodon } from 'vue-socials'

  export default {
    name: 'SSMastodonSharing',

    components: { SMastodon },

    data() {
      return {
        windowFeatures: {},
        shareOptions: {
          domain: 'https://mas.to',
          url: 'https://github.com',
          text: 'Hello, world!',
        },
        useNativeBehavior: false,
      }
    },

    methods: {
      onClose() {},
      onOpen() {},
      onBlock() {},
      onFocus() {},
    }
  };
</script>

My dude. Absolute legend. Thanks!

How would you recommend allowing the user to provide a domain before launching the window? I'd like to have it so that clicking the button launches a modal that asks for the mastodon domain, and then clicking Ok on the modal triggers the click event on the vue-social button, passing in the user's provided domain.

Ahhhh smart. Thanks again!


S2U-42 <IP_ADDRESS> Roster: The Card Game!

https://sakaiproject.atlassian.net/browse/S2U-42

Thanks @jesusmmp!


References to “font-family: "curier-new"” in demo

Assuming this is a typo and should be Courier New, but I wanted to check in before making any changes (making sure it isn’t testing an intentional failure state or anything).

Looks like this was a typo in the [toolbar config] (https://github.com/vistaprint/ArteJS/blob/master/src/toolbar/Configuration.js#L177) that just got referenced in the demo. It should be Courier New

Fixed.


[Storage] Setup datalake test proxy and migrate first two files

This change sets up conftest in datalake for test proxy as well as migrates test_cpk and test_datalake_service_client to use test proxy.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-storage-file-datalake

/azp run python - storage - ci

/azp run python - storage - ci


constrain norm after learning rate scaling

that way constrain_norm doesn't need to know the learning rate

Actually I have a question about this. Will this result in the "prev_grad" in the next iteration being the grad BEFORE the scaling or AFTER the scaling? I guess it depends on whether it's saved in .update() or.apply_updates().
Can you check on this to make sure it's doing the right thing before merging?


Next available IP range calculator only considers active workspaces

Fixes #1845
What is being addressed
Change to getting all workspaces when calculating allocated IP addresses.

/test

/test-extended

/test-extended

/test-extended

/test-force-approve


MTU option for macvlan driver

"docker network create -d macvlan -o com.docker.network.driver.mtu=1450 " is not honored.
The option to change MTU for macvlan is implemented with a different option (if so, what is it?) or is this feature not available?

Same problem here, i took a quick look at the source and sadly it is not implemented for macvlan.
My workaround is to give the container cap net_admin and set the mtu inside of the container.

Another workaround might be manually setting the MTU on the sub-interface
sudo ip link set dev ens4.40 mtu 1500

I understand that this is bridge driver option not macvlan driver option.
https://docs.docker.com/engine/reference/commandline/network_create/#bridge-driver-options
For my testing, every option described in here only worked for bridge.

Any update on this?


facebook and Google both ads are not load and show when ad id is real.

#0   EasyLogger._onAdFailedToLoad (package:easy_ads_flutter/src/utils/easy_logger.dart:43:13)<…>
#1   EasyLogger._onAdEvent (package:easy_ads_flutter/src/utils/easy_logger.dart:83:9)<…>
banner ads for facebook could not be loaded.<…>
ERROR: Error occurred while loading 1001 No fill ad<…>
banner ads for admob could not be loaded.<…>
ERROR: LoadAdError(code: 1, domain: com.google.admob, message: Request Error: No ad to show., responseInfo: ResponseInfo(responseId: null, mediationAdapterClassName: null, adapterResponses: [], loadedAdapterResponseInfo: AdapterResponseInfo(adapterClassName: , latencyMillis: 0, description: , adUnitMapping: {}, adError: null, adSourceName: , adSourceId: , adSourceInstanceName: , adSourceInstanceId: )), responseExtras: {})<…>

This is not a package issue, clearly you can see from logs that there is no ad fill


Add information on the dashboard and on the gamepage so the user is informed about what the game is

I will create a page, where the user is shown a type of tutorial.

https://github.com/sopra-fs23-group-20/client/commit/acd91cbb9939b473e95ec1c286521b71501d99b0


Finetuning

Hello, I wish to fine-tune your model using my own dataset.
I am running an experiment to see if fine-tuning on a pre-trained model can offer performance improvements over training an nnUNet from scratch (which I have already done).
The folks at the nnUNet repo have told me that in order to fine-tune your models I need the plans for the dataset you trained your data on.
Is it possible for you to upload this information?
Thank you!

Thanks, for others wondering the steps to solve are:

create dummy Dataset in the preprocessed folder which the environment variable nnUNet_preprocessed points to
run command where i is the dummy dataset id and j is the dataset you're transferring plans to with

from nnunetv2.experiment_planning.plans_for_pretraining.move_plans_between_datasets import move_plans_between_datasets

move_plans_between_datasets(source_dataset_name_or_id=i
                                    , target_dataset_name_or_id=j
                                    , source_plans_identifier='nnUNetPlans'
                                    , target_plans_identifier=f'totseg_nnUNetPlans' # can rename original plans.json to something more discernable
        )

Alternatively just copy the json to each dataset... thats all it really does
3. I preferred to use the original entry function in the nnUNet to finetune, so the whole argv hack can be avoided if you're confident your parameters are correct:
from nnunetv2.experiment_planning.plan_and_preprocess_entrypoints import preprocess_entry
import sys

original_sys_argv = sys.argv
sys.argv = [original_sys_argv[0],
                    '-d', str(j),
                    '-plans_name', 'totseg_nnUNetPlans',
                    '-c', '3d_fullres',
                    '--verbose',
                    '-np', '4']
preprocess_entry()
sys.argv = original_sys_argv


(WIP)Fix load not required plugins

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.高博文 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Store history of last N errors and api to get last error or all history

We want to use circuit breaker instance in our healthcheck reporting. Would be nice if cb instance was able to report which errors triggered it to fail.
If that's something you consider useful for this library we can send a PR.

That sounds cool, I'd definitely take a PR for it. 👍

so we envision a couple of additional api methods, it will stay compatible:
FailWithError(error)
Error() error - return last error
Errors() []error  - return history of errors
I'm not sure yet how we configure history depth. Do you have any suggestions?

@rubyist I've submitted PR, let me know what you think. Thanks!


Added solution to remove-whitespace-from-start-and-end.english.md

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

@Hiyorimi You must paste a full solution which includes all of the original challenge seed code plus the additions/changes which allow the solution to pass.  You only added a single line of code.  There should be a total of 3 lines of code.

Updated the code, thank you for the comments!

Congrats @Hiyorimi on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝

Thank you! Glad to make small contribution for such a great project!


Added a basic terminal with one terminal command (message) for testing

Added one API view to respond to message and created one template for terminal.

The text box's position is still not correct in the terminal. Please fix it, I'll merge it after that and extend on the logic.

* I ran the terminal locally, and the positioning of the text box is a bit off for me. Please fix that.


Refactor asymmetric crypto API further and add examples

This PR adds virtual interfaces to the current API, moves the specification of the hash function from the paddings to the contexts (and does some adaptions that are required with to the API). Additionally a (doxygen) example page for the asymmetric crypto interface is added.

I have two major complains:
* declaration of implemented interface methods in a declaration of the classes which implement those interfaces. It does not add any value but makes code harder to read.

* Tests files are too big to reason about them.  Single test file includes several god-classes, some test methods checks several things. We can do a better job making them more focused and concise.

Hey,
i've changed a few things:

I hope the tests are a bit cleaner now...
Regarding your first point: As stated in the comments i don't think it is possible. And even if, I'd argue against that. Because from only reading the header you couldn't really tell if the class is abstract or if all virtual methods have been implemented.


Feature async wasm call

Added web worker to make WASM calls async. Fixed issue with calMinMax.  I will add @neurolabusc WASM changes in another branch.

@cdrake, is this PR ready to be merged?

@hanayik - Yes, this is ready to be merged.


release of other controlnets such as canny or depth?

would you be open to releasing other controlnets such as canny or depth?

The subsequent open source program has been terminated by the Company. I'm sorry about the company's attitude towards open source, but SDXS probably won't be updated again.

thx for updating the readme !


Feedback for Get tenant status notifications

Next release of our environment (Online) will add in notification to partner apps when a tenant is moved to a new endpoint.
• CustomerStateChangeNotificationType must be extended with type Move (change public endpoint)
• Everywhere we change public end-point, the event must be raised with partners
• NotificationMessage must include new public endpoint for the customer
We need to update the docs with this change. DevOps ID 52259

Document Details
⚠ Do not edit this section. It is required for docs.superOffice.com ➟ Docs Team processing.

Content Source: notify-customer-state-change

{"ChangeType":5,"ContextIdentifier":"Cust36660","VersionName":"Release_10.3.8_2024.08.30-01","FileVersion":"<IP_ADDRESS>4","Token":"eyJ....","PublicEndpoint":"sod3.superoffice.com"}


[Bug Report] wrong of fn write in the TcpSocketState

I think there are something wrong within the  fn write in the TcpSocketState, Code below:
fn write(&self, data: &[u8], _sendto_endpoint: Option<Endpoint>) -> SysResult {
        // get the lock and handle of the global SOCKETS
        let mut sockets = SOCKETS.lock();
        let mut socket = sockets.get::<TcpSocket>(self.handle.0);

        if socket.is_open() {
            if socket.can_send() {
                match socket.send_slice(&data) {
                    Ok(size) => {
                        // avoid deadlock
                        drop(socket);
                        drop(sockets);

                        poll_ifaces();
                        Ok(size)
                    }
                    Err(_) => Err(SysError::ENOBUFS),
                }
            } else {
                Err(SysError::ENOBUFS)
            }
        } else {
            Err(SysError::ENOTCONN)
        }
    }

Withourt using the second parameter  _sendto_endpoint
I'm considering that  there maybe some problems ,  the parameter is not necessary ,  tcp first bind and connect  with a endpoint which ensure the data transfer to the endpoint

I'm considering that there maybe some problems , the parameter is not necessary , tcp first bind and connect with a endpoint which ensure the data transfer to the endpoint

That's why the endpoint parameter is not used. It is saved in socket.

Thank you , I understand it !!


How to synchronize cache of server components to the client?

server component
const client = getClient()
client.query({
   ...
})

And then, when I checked the cache in the browser, the result did not get synchronized, which may cause the cache to not get updated after using useMutation.

I found the answer, When should you use Client Components vs Server Components?

On top of that, I'm gonna quote the README for this package as a TLDR of that article:

❗ We do handle "RSC" and "SSR" use cases as completely separate.
You should generally try not to have overlapping queries between the two, as all queries made in SSR can dynamically update in the browser as the cache updates (e.g. from a mutation or another query), but queries made in RSC will not be updated in the browser - for that purpose, the full page would need to rerender. As a result, any overlapping data would result in inconsistencies in your UI.
So decide for yourself, which queries you want to make in RSC and which in SSR, and don't have them overlap.


investigate the impact of changing account_id in targetAccountMappings

With the addition of https://github.com/awslabs/seed-farmer/pull/204 - if you did change the account_id in the target mappings and tried to deploy, seedfarmer will stop as it triggers a destroy of modules that have dependencies (assuming the new target account has been bootstrapped).  You would have to explicitly delete all dependency modules.  This would mitigate an inadvertent change in mappings.


Double tap zoom option

Describe your suggested feature
Add the option to make the "zoom wide images automatically" feature use the double tap zoom size.
Other details
Could be located on the reader section of the settings.
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an official extension, I should be opening an issue in the extensions repository.
[X] I have updated the app to version 1.11.2.
[X] I will fill out all of the requested information in this form.

could you explain more on this? what is current behavior, what is exactly expected?


HIVE-26174 disable rename table across dbs when on different filesystem

What changes were proposed in this pull request?

Disable rename table across dbs when dbs on different filesystem.
Adjust the place of comment so it matches code better.

Why are the changes needed?
Currently, if we run ALTER TABLE db1.table1 RENAME TO db2.table2; with db1 and db2 on different filesystem, for example db1 as "hdfs:/user/hive/warehouse/db1.db", and db2 as "s3://bucket/s3warehouse/db2.db", the new db2.table2 will be under location hdfs:/s3warehouse/db2.db/table2, which looks quite strange.
Does this PR introduce any user-facing change?
Yes.
Before this patch, if we run
CREATE DATABASE db1 LOCATION '/user/hive/warehouse/db1.db';
CREATE DATABASE db2 LOCATION 's3://bucket/s3warehouse/db2.db';
CREATE TABLE db1.table1 (...);
-- write some data to db1.table1
ALTER TABLE db1.table1 RENAME TO db2.table2;

The ALTER TABLE RENAME TO command will success and, table location is under /s3warehouse/db2.db/table2(s3), which is like undefined behavior of the language manual.
After this fix, the ALTER TABLE RENAME TO command will fail with message telling user that Hive cannot rename tables because they are on different filesystem.
How was this patch tested?
Manually tested.

Hi @ayushtkn , In our customers' scenario, they want to put table data in HDFS, while some stale tables will be archived to cloud store. They were using this command and thought that data should be placed in cloud store, but after a while they found it is still in HDFS. Besides, currently if we have two dbs located on two different HDFS services, the command would fail, Hence I think we should not allow rename when two dbs are on different storages.


(Capacitor 3) Plugin.swift -> downloadFile() has no implementation for iOS

Describe the bug
A clear and concise description of what the bug is.
In the capacitor 3 branch of this project, when files are downloaded, the request is made, but file is never saved to disk.
See diff here of missing implementation in Plugin.swift:
https://github.com/lincolnthree/capacitor-community-http/commit/c693de967ddff9ccb4a38e6dfa16e94a02de214e
To Reproduce
Steps to reproduce the behavior:

Try to download a file. Nothing saved :)

Expected behavior
Files should be saved to disk just like on master branch.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: iOS
Browser: Native

Smartphone (please complete the following information):
iOS real and simulated devices
Additional context
Add any other context about the problem here.

I think https://github.com/capacitor-community/http/blob/capacitor-v3/ios/Plugin/Plugin.swift#L42 should be changed
Now, it just call request (not download method)
Expectation.

    @objc func downloadFile(_ call: CAPPluginCall) {
        // Protect against bad values from JS before calling request
        guard let u = call.getString("url") else { return call.reject("Must provide a URL") }
        guard let _ = call.getString("filePath") else { return call.reject("Must provide a file path to download the file to") }
        guard let _ = URL(string: u) else { return call.reject("Invalid URL") }

        do {
            try HttpRequestHandler.download(call)
        } catch let e {
            call.reject(e.localizedDescription)
        }
    }

That makes sense! I didn't dig too deep to see where this function had moved. Looks like you found it :)

@leo6104 I think that method may not be working as intended. I still don't get files downloaded when calling it. Is it working for you?

I just published 1.0.0-alpha.1 on npm. Can you let me know if that fixes your issue? If it does not, can you provide a reproducible example? I'm not able to reproduce your issue

The new Alpha.1 seems to be unusable without modification, as it targets iOS 11:

@capacitor-community/http/ios/Plugin/Plugin.swift:3:8: Compiling for iOS 11.0, but module 'Capacitor' has a minimum deployment target of iOS 12.0: /Library/Developer/Xcode/DerivedData/App-ewnizagrywofygemcnpulcdczdjo/Build/Products/Debug-iphonesimulator/Capacitor/Capacitor.framework/Modules/Capacitor.swiftmodule/x86_64-apple-ios-simulator.swiftmodule

Wait, I may have misinstalled. Ugh. Sorry.

@thomasvidas Confirmed! The latest alpha.1 fixes the issue (along with a few other warnings about incorrect method configuration.) Thank you!

Perfect. Glad it was just me calling the wrong function 😅


Add missing spaces in concatenated strings

Mostly changing code like this
"expected: " + currentFullFlushDelQueue + "but was: "
to
"expected: " + currentFullFlushDelQueue + " but was: "
But also fixing bugs like "" + i + numDocs => "" + (i + numDocs).
I took the liberty to also do some minor housekeeping in the affected files:

corrected grammar and spelling mistakes
removed unnecessary type parameters
optimized API usage (e.g. "UTF-8" => UTF_8, assertThat() => assertEquals(), etc.)

I'll backport for 9.10 soon.

Thank you for checking this so quickly!
I started with a "Whitespace may be missing in string concatenation" inspection in IntelliJ IDEA.
After applying those fixes I went through the changed files again fixing file-level problems reported by the default inspections profile.

I started with a "Whitespace may be missing in string concatenation" inspection in IntelliJ IDEA.  After applying those fixes I went through the changed files again fixing file-level problems reported by the default inspections profile.

Cool!  Thanks for your attention to detail.  I wish we could somehow fold these checks into Lucene's static code analysis tooling...

https://www.jetbrains.com/qodana/
Open source projects can get a free license for any JetBrains products:
https://www.jetbrains.com/community/opensource/#support


Error: Error Parsing XML:

After installing 1.0.0 beta 1, I'm receiving the following error when running any recipe.
The following recipes failed:
Google Chrome.jss.recipe
Error in local.jss.Google Chrome: Processor: JSSImporter: Error: Error Parsing XML:
Not seeing anything else in the logs which would be of much help. I'm using 1.0.0 because 0.5.1 was failing when I tried logging in via the failover link since we have SSO enabled on our JSS.
Allen

Hey @golbiga. So you're not getting any more detail if you do an autopkg run -vvvv.
My guess is that your SSO setup is causing the API requests to fail so the response doesn't include XML, which JSSImporter is expecting.
I would probably figure out which request is failing (probably the very first one, which is a GET request to https://yourjss.com:8443/api/distributionpoints. I bet if we just do that with curl, we'll see an auth error and non-XML response body.

I was using the ?failover link and since removed it. The GET request is going through now, but I'm still receiving an error.
The following recipes failed:
Google Chrome.jss.recipe
Error in local.jss.Google Chrome: Processor: JSSImporter: Error: Error Parsing XML:
{"distribution_points":[{"id":2,"name":"XXX Distribution Point"}]}
I fully disabled SSO and receive the same error.

Here is the output after the change to curl_adapter.py
Error in local.jss.yo: Processor: JSSImporter: Error: Response Code: 409 Response: Conflict. API file upload exception:org.apache.commons.fileupload.FileUploadBase$InvalidContentTypeException: the request doesn't contain a multipart/form-data or multipart/mixed stream, content type header is text/xml; boundary=------------------------8929592e5972f4d8 https://server.com:8443/JSSResource/fileuploads/policies/id/282.

I should have added to the above comment:
JSSImporter: Found file: /Users/user/Library/AutoPkg/RecipeRepos/com.github.autopkg.jss-recipes/yo/yo.png
I definitely think its the icon upload.
Here is the full output. output.txt

So it looks like the Icon, which is uploaded through the /fileuploads endpoint (we need better icon management in the API btw) is not setting the correct header.
Hopefully that's not too big of a deal to fix.

@golbiga I notice this was run on Jamf Pro 9.101, so many updates since then - did you solve this problem? Did you try changing yo.png to a different icon, and/or did you experience the problem with any other recipes?


DSA <IP_ADDRESS> Stacks: Infix to Prefix - Audio/Video

Description
How to convert infix expressions to prefix? Show examples and implementation.
Two contributors may take up this issue depending on Audio or Video format.
Task

[ ] Audio
[x] Video

Note

Do not use assign command for this issue.
While requesting the issue to be assigned, please mention your NAME & BATCH NUMBER.
Kindly refer to Issue Guidelines.
Changes should be made inside the DSA/directory & DSA branch.

@nimisha-yadav
I would like to work on this issue in video format. Please assign me this issue.
Thankyou!
Name : Harshitha
Batch: DSA batch-3

Name- Priyasha Jain
Batch - DSA-7
I would like to work on this issue in audio format. Please assign this issue to me.
Thank you!

Hi! Can u please open this issue again? I had prepared material but I contributed in the wrong method before.

Thank you so much!!


prisma asks to authenticate when running prisma deploy command

Hi,
I have my prisma service running into a Docker container locally.
I want to have my API (built on top of prisma service) running through a container too.
prisma.yml:
endpoint: ${env:PRISMA_ENDPOINT}
datamodel: datamodel.prisma
generate:
  - generator: typescript-client
    output: ../src/generated/prisma-client/
hooks:
  post-deploy:
    - prisma generate --env-file ../.env
secret: ${env:PRISMA_SECRET}

docker-compose.yml to start the prisma service and the data base:
version: '3.7'
services:
  prisma:
    container_name: pwa-prisma
    image: prismagraphql/prisma:1.34
    restart: always
    ports:
    - 4469:4469
    environment:
      PRISMA_CONFIG: |
        port: 4469
        databases:
          default:
            connector: postgres
            host: postgres
            port: 5432
            user: prisma
            password: prisma
    networks:
      - prisma

  postgres:
    container_name: pwa-db
    image: postgres:10.3
    restart: always
    ports:
    - 5432:5432
    environment:
      POSTGRES_USER: prisma
      POSTGRES_PASSWORD: prisma
    volumes:
      - pwa-volume:/var/lib/postgresql/data2
    networks:
      - prisma

volumes:
  pwa-volume: ~

networks:
  prisma:
    name: prisma
    driver: bridge

Note that the two services are under the same network named prisma.
Ok now here is the  Dockerfile of my API:
FROM node:latest

WORKDIR /usr/src/app

COPY package*.json ./
COPY deploy/.env ./
COPY src src/
COPY prisma prisma/
COPY tsconfig.json ./

RUN npm i
RUN cd prisma && npx prisma deploy --env-file ../.env
RUN npm run build

EXPOSE 4001

ENV NODE_ENV production

CMD [ "node", "dist/index.js" ]

and finally the docker-compose.yml to build it:
version: '3.7'

services:
  api:
    container_name: api
    build:
      context: ../
      dockerfile: deploy/Dockerfile
    restart: always
    ports:
      - 4001:4001
    networks:
      - prisma

networks:
  prisma:
    external: true

Note that I put the api service under the same network of the prisma service to allow them to communicate.
My .env looks like:
PRISMA_SECRET=xxx
PRISMA_ENDPOINT=http://<prisma_service_container_name>:4469
API_SECRET=xxx

When I run my docker-compose.yml to build the API, It fails:
Step 9/13 : RUN cd prisma && npx prisma deploy --env-file ../.env
 ---> Running in 8f9e5a9fd919
npx: installed 593 in 55.357s

Authenticating...
Opening https://app.prisma.io/cli-auth?secret=xxx in the browser

Could not open the authentication link, maybe this is an environment without a browser. Please open this url in your browser to authenticate: https://app.prisma.io/cli-auth?secret=xxx

We can see for some weird reason Prisma needs to authenticate when the command prisma deploy --env-file ../.env is run.
But if I run the exact same commands (cd prisma && npx prisma depoy ..) directly into the container (through docker exec -it api /bin/bash), the command succeds.

even I get the same problem...

After some digging into Docker I think this is not a Prisma cli problem:
The prisma deploy command will make calls to the running container of the Prisma service. For me on localhost:4469.
In my Dockerfile I try to run prisma deploy. And this is the problem: Dockerfiles can't make external callouts to other containers or to the host system during their build.
Initially I misunderstood this and I naively thought it was possible.
Back to my problem, during the build time of my Dockerfile, a step runs prisma deploy and this command will try to call the container of Prisma service on http://<prisma_service_container_name>:4469. These calls will fail as explained above. At this time I think the command fall into a default case and assumes that this endpoint is a cloud one. And this is what happens, prisma deploy finally asks the user to authenticate against this endpoint.
But because it's not, this fail.


Change title in taskbar

On XFCE at least, the title is still __main__.py. Related, the icon shows up in XFCE, but I don't think it does in Gnome.

Icon shows up fine in Gnome, but when I right click on it to see a window list it shows up as __main__.


Item Display: add new styles

Issue Description

Need to add two new textStyles to Item Display:
1a. that makes text bold but keeps current text color (not red).
1b. an inactive version, superlight text
Change the Item Comment icon color to use transparency (looks better when row is selected).

Issue Type

[ ] New Feature
[X] Enhancement
[ ] Bug
[ ] Other

Expected Behavior
Add two new options to the textStyle prop: 'bold'/'strong', and 'inactive'/'disabled' or similar wording for the props.
Current Behavior
Item Display currently has {default}, 'secondary', 'attention', 'strikeThrough'.

Will provide colors for styles needed.

@neilpfeiffer I'm happy to take this on if you're able to provide the color values.


[Bugfix] Sticky element losing its height. Fixes #8435

Anchored element is losing its original height after being stuck.
Fixes https://github.com/zurb/foundation-sites/issues/8435

This one looks good to me. @zurb/yetinauts please have a look when you get a minute, the sticky visual test for callouts really demonstrates this problem.

Discovered something worth noting for you guys to take into consideration when checking this out.
If I make the div with the Sticky class as the parent of the callout div the height issue goes away (before merging the fix from this PR). The same thing applies to menus. This syntax works as is:

      Go to Sticky Docs

This syntax has the issue:

    Go to Sticky Docs

I have a little more to on add on to my previous post. If you use the following syntax...

      Go to Sticky Docs

...the callout has a bottom margin, so the sticky container includes that in its height and the anchoring is off by that much. I changed all of the Sticky element's to use that syntax. See here:

My questions for the @zurb/yetinauts, @gehasia, and anybody else that wants to give feedback:

Should we direct users in the docs to put the .sticky div as a parent of the element they want to sticky? This would essentially make you use 2 container divs for Sticky, one for [data-sticky-container] and one for [data-sticky] / .sticky.

^^^ If we did it this way then:
2. How should we then handle margins like in the example I gave above with the callout bottom margin?
3. it would prevent potential collision between having 2 Foundation plugins initialized on the same element. I'm not sure if advising against that (2 plugins on same element) is clearly stated in the docs, and it probably should be, right?
4. Do we still implement the fix in this PR?
Sorry for the barrage of info/questions, I need some good feedback to make sure that Sticky is headed in the right direction. Thanks!

re point 3, we pretty definitely state A single element can only have one Foundation plugin on it at a time. However, most plugins can be nested inside other ones.  Perhaps could be louder/repeat more often, but that is clearly in the docs

Re point 1, my inclination would be only if absolutely necessary.  The more we can avoid requiring extremely bulky HTML to accomplish goals, the better.  The amount of containerization/bolierplate to handle off canvas still irks me. :P


symfony 2.7 deprecated syntax in installRequirementsFile()

https://github.com/sensiolabs/SensioDistributionBundle/blob/master/Composer/ScriptHandler.php#L210
uses a deprecated syntax for chmod-ing the dumped file. Which in turn for symfony 2.7 throws an exception during composer update:
[ErrorException]
Support for modifying file permissions is deprecated since version 2.3.12 and will be removed in 3.0.

Can you submit a pull request to fix that?


Support connect() usage

Had a good brief chat about downsides with @ian-craig, who brought up the good point that only targeted hook usage leaves out all applications that use connect().
In theory it should be possible to support connect(). Let's do it!

I investigated a little bit and this seems like it should be doable. Yay!
However, it's going to rely on #6. mapStateToProps calls inline functions and so can't have selectors mapped out nicely the way useSelector does.
Here's a bit of somewhat-working code for just mapStateToProps:
import * as React from "react";

export const mockConnect = (mockSelector) => {
  const mockConnect = (mapStateToProps) => {
    return function createMockConnectedComponent<Props>(Component: React.ComponentType<Props>) {
      return function MockConnectedComponent(props: Props) {
        const stateProps = Object.entries(mapStateToProps?.() ?? {}).reduce(
          (accumulated, [key, selector]) => {
            accumulated[key] = mockSelector(selector);
            return accumulated;
          },
          {},
        );

        return <Component {...stateProps} {...props} />;
      };
    };
  };

  return mockConnect;
};


Homekit: Hide All by default

Home Assistant release with the issue:

0.66.0.b2
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):

Hassbian
Component/platform:

ecobee and other
Description of problem:
The new update is great, however, it ends up duplicating most of my devices on homekit.
A hidden or visible option like the one for homebridge would work well. Having to figure out each device id to add to exclude takes longer than just adding the ones that are not.
Luckly my lutron and hue were commented :)
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:

For the duplicated entries: Read the section about breaking changes here #12997.
You can use the include_entities filter. Than only the entities defined there will be displayed https://rc.home-assistant.io/components/homekit/#filter

Sorry, should have paid more attention. Keep the good work 👍

All good. Just wanted to close this, so I can focus on the open ones. I hope it wasn't to offensive


Fix regression after #5661

Thanks a lot for the PR! Somehow I saw this one after merging #5731 which does exactly the same change, sorry for that :(


Added Repetier-Server platform

Description:
Adds sensors for each devices in your Repetier-Server installation.
Currently pulls status including start time, job name, done percentage and more.
Example entry for configuration.yaml:
sensor:
  - platform: repetier
    url: http://server-ip
    port: 3344
    api_key: api-key-from-server
    state_percent: true
    decimals: 1

state_percent is optional and defaults to false (showing on, idle, off as state)
decimals is optional and defaults to 1, only used when state_percent is true
Checklist:

[ x ] The code change is tested and works locally.
[ x ] Local tests pass with tox. Your PR cannot be merged unless tests pass
[ x ] There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

[ x ] Documentation added/updated in home-assistant.io

Hello @MTrab,
When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).
The commits that are missing a linked GitHub account are the following:

ea7fcfcaf9794655613d4d20002ce2090e4172fd - This commit has something that looks like an email address (morten@ha-dev.trab.local). Maybe try linking that to GitHub?.

Unfortunately, we are unable to accept this pull request until this situation is corrected.
Here are your options:

If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.

If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.

If you only made a single commit you should be able to rungit commit --amend --author="Author Name<EMAIL_ADDRESS>
(substituting Author Name and<EMAIL_ADDRESS>for your actual information) to set the authorship information.
If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:

You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.

Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.

We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.
Thanks, I look forward to checking this PR again soon! :heart:


Handle the first version of translation as missing if auto-saved

Motivation

If there is no translation yet and an user starts an first translation and it gets auto-saved, ✅ appears as translation status in the page tree. This is but not completely so correct, because the saved translation is just auto-save and still in progress. In this case ❎ should be shown.
Proposed Solution

Handle the first version of the translation as missing and show ❎ in the tree, if it is not a manaual save.
Alternatives

Leave it as it is.
User Story

Additional Context

TBD:

Whether this behaviour should be applied for the route lanuage too.
Whether ❎ should be shown until the first manual save, even if there are multiple of auto save versions. Related to #2067

Design Requirements

This issue may bring a kind of contradiction to #2389
We will not show translation status of the root language anymore because it's always up-to-date. However this issue breaks such an assumption, creating cases that translation status of the root language is "missing" with no manual save yet.
Of course we can apply this issue only for non-root languages, though the behaviour is then not consistent between the root and other languages (users recognise by icons whether there is a manually saved version for translations in non-root languages whereare there is no indication about the root language) and probably causes confusion to users.

I'm in favor of closing this issue since it also contradicts #1889.
In my opinion, the current separation of translation status and publication status makes a lot of sense, and if we create one exception now, it will become messy and even more complicated.

We decided to close this, see https://chat.tuerantuer.org/digitalfabrik/pl/cnopratp1pn8z8yysrj3atoj4h


Packaged for NixOS

Hi, not really a question, but I figured you'd like to know that I've packaged tuifeed for NixOS
Thank you for tuifeed! Ciao!

Thank you very much 🙂


this.source.getFilteredAndSorted Not Working

Unable to get FilteredAndSorted...
let testfilter = this.source.getFilteredAndSorted().then(data => {
        return data;
 });

Returns no data.

Any Ideas?

For me is returning in 'data' parameter the items in the table after applying the filter. So it works ok. Add a log on 'data' on your example

In my case it does not work.
this.source.getFilteredAndSorted().then(data => {
console.log(data);
});
returns to me the getAll() before filter which is 448 objects in my case, and my ui only has 4 records after filter


APNs multi staging fixes

This PR addresses two things:

when network options of a iOS variant change from DEV->PROD (or vice versa), the cached connection is incorrect, since we only use the Variant_ID as the key. We need to a add a new identified to the VARIANT_ID, like -prod or -dev

adding Default Topic for APNs (bundle ID)
When an application/bundle_ID (inside of Apple's UI) is configured for multiple stages (e.g. DEV/PROD), we do need to provide a (default) topic, which matches the Apple bundle ID. We read that from the given .p12 file, if present. Otherwise, null is used - which is fine for single topic certificats (e.g. Only one, DEV or PROD is enabled), and on DEVELOPMENT APNS - unfortunately the PRODUCTION endpoint is a bit inconsistent...

Besides that, removing a dependency, which is automatically get from Pushy 0.9.3 and some simple LOGGER format changes.

@ziccardi Can you review this ?

Added a few comments

LGTM


Adding linters and aligning code

Closes #166.

These changes could affect the work in progress by @PaoloCarta: thanks to the additional linters I discovered the (obvious) duplication of code for the StorageClass, IngressClass, and Registry allowed lists with exact and regex matching.
So I decided to perform refactoring of this to avoid the duplication of code, and the result seems neat to me but I could expect some pain performing a rebase of your work on #162: so, if this is going to happen, we can delay this PR after yours.
Just let me know!


why VisibilityNotifier2D emit signal exit_screen when freed?

Operating system or device, Godot version, GPU Model and driver (if graphics related):
MAC
2.1.4 beta
Issue description:

when the position of the VisibilityNotifier2D node is out of the screen, the exit_screen is emitted, that's OK.
However when queue_free is called on the VisibilityNotifier2D, the exit_screen is also emitted, How to distinguish these two situations in the exit_screen callback?
Steps to reproduce:
Link to minimal example project:

Can you check if NOTIFICATION_PREDELETE and/or NOTIFICATION_EXIT_TREE happen before the signal?
If these do happen before, you can use that as a workaround to remove connections or ignore the signal in the target.
Maybe VisibilityNotifier could have an optional check to not emit signals when queued for deletion.

Same here, I thought when freeing an object all the signals were disconnected before. Is not really a problems since you could always disconnect manually the signals, like I did:
$body/LeftVisibilityNotifier.disconnect("screen_exited", self, "_on_VisibilityNotifier_screen_exited") $body/RightVisibilityNotifier.disconnect("screen_exited", self, "_on_VisibilityNotifier_screen_exited") queue_free()
But I read somewhere all signals were automatically disconnected when freeing and that is not consistent. I agree having an option for visibility notifiers to notify or not when being destroyed might be usefull but I'd leave this as not emitting anything by default.
Regards

Now that I think of, may be better that queue_free gets an option to "disconnect all signals before freeing".

I can confirm that issue is still parent in 3.2.
My biggest problem is that when closing a game while object with visibility notifier is present it's queued free before my autoloads and it causes errors
So I have a simple ball scene in breakout game it has a VisibilityNotifier2D that send a signal to destroy the ball and update player lives
Ball has this callback
    func _on_VisibilityNotifier2D_screen_exited() -> void:
		print("emited")
		emit_signal("destroyed",self)
		queue_free()

My GameControler then checks if there are any other balls left as sometimes player has more than one ball at a time. If there isn't any balls I reduce player lives. It works spot on

	func _on_Ball_destroyed(ball)-> void:
	        yield(ball,"tree_exited")
		if not are_balls_left():
			GameData.player_lives -= 1

	func are_balls_left() -> bool:
		var balls_left = get_tree().get_nodes_in_group("Ball")
		if balls_left == []:
			return false
		else:
			return true

My problem is when I close a game while ball is still in playVisibilityNotifier2d emits a signal screen_exited (I know this because my print("emited") is activated) which causes my GameControler to attempt to look for balls in a tree but as there is no tree any more and whole thing breaks.
Message I am getting is "Attempt to call function get_notes_in_group" in base "null instance" on a null instance?
This is strange is VisibilityNotifier2dmeant to emit signal when I close the game? Am I doing something wrong here or should I be reporting it as a bug?
Link to github page with a whole project https://github.com/Feniks-Gaming/Breakout-Clone all you have to do to replicate is play a game press space to create a ball and close the game while ball is still on the screen

I don't see any error on 3.4b4 trying the snippet that is in one of the posts here (that also pass around a reference of a node that will be in queue for deletion and may produce another error).
The OP could have been a logic error as well.

Still emit screen_exited signal when freed in 3.3.3.
Archive.zip

Ah, ok, yes, it emits screen exited (because it technically exits the screen?) so needs to be decided if is the desired behavior or not.
Something similar happened with Area nodes when removed or added and emitted (or not) their enter/exit signals, so maybe the same behavior applies for visibility nodes (that should be also consistent to what is expected on the visibility enabler nodes).