Make Paket compile on systems with only F# 4.0 installed

Make Paket compile on systems with only F# 4.0 installed

thx buddy


bind mirror sockets to <IP_ADDRESS> to workaround localhost restrictions in firefox

Tested with uProxy, one peer running Chrome and the other Firefox.

Isn't this unsafe, without any source filtering?

Just doing one thing at a time.

Introducing a known security-ish issue into a point release, with the intention of fixing it in the following one, makes me very uncomfortable.  I would prefer to do these changes in the other order.

This was a lot easier than I expected!
PTAL. Tested with uProxy between Chrome and Firefox and Simple SOCKS on both Chrome and Firefox and manually sending packets to a mirror socket with ncat.

:+1:


Unable to find the updated device-list after realignment process

It would be helpful when MWDI showing the updated device-list after re-alignment process.
Also, if it is showing for deleted device list, new devices planning to add list in log, it would be better.

Looks good to me. Maybe for debugging purposes we can also keep older versions of the file (configurable). Just like with logfiles like logfile.1, logfile.2 etc.; but that would depend on if this would be useful for TechM.
As for the files getting lost when the docker container is destroyed... if I remember correctly, it's possible to configure file locations outside the docker container, we the files could be written to. So we could go with that approach.

We provided MWDI a new feature that each time the realignment event occurs
creates a new log file named as:
date_time.log   (for example: 2024.05.06_13.20.19.log)
The log file prints both the device list and the sliding window before and
after the realignment event. In addition both the added and the dropped
elements are listed.
All these files are saved to the "realignment_logs" external volume.
The procedure checks for the volume before saving the log file. If the
volume doesn't exist the procedure doesn't save any file.
Following the options to add to docker run command for mapping the volume
that must be created with:
docker run --mount source=realignment_logs,target=/realignment_logs
The above command mounts the volume on the root of the container.

Tested okay with 1.1.2d.
Re-aligment logs are collected in docker path /var/lib/docker/volumes/realignment_logs/_data

realignment_logs.txt


[BUG] Upgrade from v1.5.2 to v1.5.3-rc1 failed if there's an attached v1 volume and a detached v2 volume

Describe the bug (🐛 if you encounter this issue)
Upgrade from v1.5.2 to v1.5.3-rc1 failed if there's an attached v1 volume and a detached v2 volume
instance-managers get stuck in Pending -> OutOfhugepages-2Mi -> Terminating loop forever and not possible to become Running:
According to v1.5.3 website, attached v1 volume should not impact the upgrade process.
longhorn-system   instance-manager-749a0b6289a7dcd13969be2694fa32e3   0/1     OutOfhugepages-2Mi   0          0s
longhorn-system   instance-manager-381b3cd27f3e4a0e4b02d634f29a503e   0/1     OutOfhugepages-2Mi   0          0s
longhorn-system   instance-manager-249758cbabcbc1f2d148a6d98bc97030   0/1     Terminating          0          0s
longhorn-system   instance-manager-249758cbabcbc1f2d148a6d98bc97030   0/1     Terminating          0          0s
longhorn-system   instance-manager-249758cbabcbc1f2d148a6d98bc97030   0/1     Pending              0          0s
longhorn-system   instance-manager-249758cbabcbc1f2d148a6d98bc97030   0/1     OutOfhugepages-2Mi   0          0s

To Reproduce

Setup v2 engine environment with https://longhorn.io/docs/1.5.3/spdk/quick-start/
Install longhorn v1.5.2 by kubectl apply -f https://raw.githubusercontent.com/longhorn/longhorn/v1.5.2/deploy/longhorn.yaml
Create a v1 volume and PVC1, apply workload1 with the PVC1, write data into mount point
Create a v2 volume and PVC2, apply workload2 with the PVC2, write data into mount point
Scale down the workload2,  make sure v2 volume detached.
Upgrade longhorn to kubectl apply -f https://raw.githubusercontent.com/longhorn/longhorn/v1.5.3-rc1/deploy/longhorn.yaml
instance-managers get stuck in Pending -> OutOfhugepages-2Mi -> Terminating loop

Expected behavior
Upgrade success when v2 volume detached
Support bundle for troubleshooting
supportbundle_374b780d-fb7a-46a8-a30e-ef04354a62e6_2023-11-14T04-09-22Z.zip
Environment

Longhorn version: v1.5.3-rc1
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): kubectl and helm
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version:  v1.28.2+k3s1
Impacted Longhorn resources:

Volume names: vol2

Additional context
Upgrade form v1.5.2 to v1.5.3-rc1 success if there only had a detached v2 volume.
https://github.com/longhorn/longhorn/issues/7025

Ah, we should update the document. All v1 and v2 volumes should be detached.

Confirmed that the upgrade from v1.5.2 to v1.5.3-rc1 success when all v1 and v2 volumes were detached.
Waiting doc PR merged to close this ticket.

Close this ticket as the doc PR merged,  thanks


User Story: Search Bar

As as user, I should be able to use the search bar to find items by name so that I can quickly find the product I'm looking for

Completed by #77


Allow highlighting drag to start from the border

This is sort of a papercut type issue, often when I go to highlight some text in the window especially when it's maximized and against the left edge of my screen I can't start the drag without moving a couple of pixels to the right which appears to be the width of the border of the window. It usually means I end up having to attempt to drag more than once to get it right or start from the other end. I think this would improve the ergonomics of alacritty.
Which operating system does the issue occur on?
Linux
If on linux, are you using X11 or Wayland?
Wayland, though it appears alacritty runs in XWayland as it shows up in xwininfo.

I've noticed this too and I think this is a great suggestion!
It also shouldn't be super complex to do, so if someone is interested this might be a fun thing to play around with. All relevant code should be in the mouse_moved method in src/input.rs.

Was interested to learn some Rust and took a look at this.
Seems to be a limitation of glutin::GlWindow, see here https://docs.rs/glutin/0.19.0/glutin/enum.WindowEvent.html#variant.CursorMoved
The event loop does not receive any events while the cursor is moving on the border, which exists even when the app is maximized. There is an undocumented "MouseMotion" WindowEvent that occurs (on Linux X11) but it only provides motion delta, so it would require tracking outside the app.

This is about the padding that is created by Alacritty, so it is not relevant if we can get window events outside of Alacritty or not.

Thanks for the clarification, FWIW, on x11 I don't have any issues drag selecting from the left side of a maximized screen except for on the ~2 pixel window border.

@chrisduerr Thanks for the clarification, I misunderstood the issue.


Is there a way to use this wrapper with Xcode toolchain?

I wonder if there is way to link to libclang that comes with Xcode.app? I want to make a small tool based on this library and I wish I can avoid forcing users to install llvm via brew on their systems, because it takes a lot of time.

I don’t think the headers get shipped with the toolchain’s copy of libClang so unfortunately that’s not going to work.  The brew installation process for LLVM only takes a while until they get the bottles built, then it’s usually a breeze.


Thirty Minute Interval Not Supported

Is there any particular reason that you are replacing 30m with 15m on all calls?
	// Add the interval based on Interval property.
	var interval = YUtils.GetInterval(Interval == Interval.ThirtyMinutes ? Interval.FifteenMinutes : Interval);

Please, open a pull request to fix it.


nginx as backend sometimes doesnt display content with multiple new loads / reloads or just new page

Describe the bug
nginx as backend sometimes doesnt display content with multiple new loads / reloads or just new page
in a separate issue, this error appears too
2022/12/21 14:49:47.349734 client.go:1840: [Info] http2: Transport readFrame error on conn 0xc00006cd00: (*errors.errorString) EOF
2022/12/21 14:49:47.988014 client.go:1840: [Info] http2: Transport readFrame error on conn 0xc00006d1e0: (*errors.errorString) EOF
2022/12/21 14:49:47.988062 client.go:1840: [Info] http2: Transport readFrame error on conn 0xc0004b0000: (*errors.errorString) EOF
2022/12/21 14:49:47.992292 client.go:1840: [Info] http2: Transport readFrame error on conn 0xc0004b01a0: (*errors.errorString) EOF

To Reproduce
use the code here
https://github.com/cloudwego/hertz/issues/481
Steps to reproduce the behavior:
same as mentioned in issue
Expected behavior
nginx not showing error but hertz showing blank
Screenshots

cc @Duslia

Does this question come up every time？

I cannot understand multiple new loads / reloads.
And hertz showing blank is the expected behavior?

@Duslia , when first time visit the url, hertz showing blank. this is not expected. expected behaviour is showing nginx default html page.
if you reload the browser multiple times, u'll sometimes get a blank screen too as attached in the image above.
expected behaviour is showing nginx default html page.

@Duslia they are two issues (i think same problems), can you look into it?

reverse proxy doesnt work well with nginx backend, shows blank page sometimes (check the video)
error message after waiting for some time.

https://github.com/cloudwego/hertz/issues/481


SPICE Mnemonic & S3 position

Fixed SPICE mnemonic and finished modifications I started to S3 positions, now mnemonic is used to set positions in TS3Hit correctly for all bambino and SPICE configurations automatically.

Added in an earlier correction to the waveform fitting I lost in a merge.
Tiny change that makes a big difference.

This looks okay to me, I've removed one statement in TMnemonic.cxx that had no effect (strol used without using the return value or the end pointer), the other changes in this are okay.
As far as I can see you've changed the way the S3 segments are handled (using the TGRSIDetectorHit::GetSegment instead), changed some of the GetPosition functions to get around signature clashes I assume, removed the option to use waveform fitting with S3, and replaced the copy-constructor with an explicit call to TS3Hit::Copy (which isn't in the copy-constructor why?).
And in the PulseAnalyzer you've decided to prefix some of the class members with a lower-case c (why not use the standard lower-case f?).
So unless I missed something important this looks okay to me (as far as functionality goes).

Good catch on the pointless strol, that was an example line I'd had while working that should have been deleted.
I only removed the S3 sector waveform fitting, which was sat next to the comment "Only fit waveforms for rings".
The Copy was there to make it explicit what operation was being performed as there was some redundancy there before.
As for PulseAnalyzer prefix ... comparing to someone else's code looking for a mistake got messy. I could tidy it up, but its no worse than it was before.

Looking again at the S3 stuff I was wrong.
The assignment stuff wasn't redundant, although some becomes redundant by removing the segment fitting. So perhaps all that should have been removed was "Only fit waveforms for rings" comment that has got left in.
I blame Sunday night coding, I suggest banning it from the collaboration.

... actually maybe I was right the first time about the redundancy. I give up.

I just intended to point out that the waveform fitting had been removed completely. If that is what was causing issues for you, remove it.
The bigger question is the Copy vs copy-constructor thing. It's fine to use the Copy explicitly, though at least for me ROOTs Copy function is always confusing because it works backward to what I expect reading the code. But the point I wanted to make was that there is actually a difference in the code between using Copy or the copy-constructor. The latter does not copy all the TTigressHit specific class members because it is missing the call to Copy. All (I hope) other copy-constructors call the copy-constructor of the TGRSIDetectorHit base-class and then use Copy within the constructor to do all the rest. This is not the case for the TTigressHit (which I think should be fixed).

The TS3Hit copy-constructor does call the Copy operator, I would think this should be standard as then we define copying all class members in one place.
I see your point about the confusion of the root style Copy operator. TS3Hit copy-constructor does not call the TGRSIDetectorHit copy-constructor but instead calls Copy which contains TGRSIDetectorHit::Copy(rhs); which I may be reading wrong, but that seems to be copying the wrong way.

Sorry, that was actually me reading the wrong constructor. You are right, the copy-constructor does use Copy and it is using it the right way. Meaning that a.copy(b) (reading a copy b) actually copies a to b.
Anyway, I've merged your changes, Ryan has tagged everything, and I've now merged the parallel_queues branch back into master.


在初始化过程中，显存爆了

更换了更大一点的向量化模型bge-m3，在初始化比较大文件的时候会爆显存，导致无法继续进行初始化，请问有什么办法分批或者量化模型的方式来解决？
报错内容：
”CUDA out of memory. Tried to allocate 128.00 GiB. GPU 0 has a total capacty of 23.69 GiB of which 14.50 GiB is free. Process 356231 has 9.18 GiB memory in use. Of the allocated memory 8.13 GiB is allocated by PyTorch, and 8.94 MiB is reserved by PyTorch but unallocated. If reserved but unallocated memory is large try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF
Exception in thread Thread-1:“

更换了更大一点的向量化模型bge-m3，在初始化比较大文件的时候会爆显存，导致无法继续进行初始化，请问有什么办法分批或者量化模型的方式来解决？ 报错内容： ”CUDA out of memory. Tried to allocate 128.00 GiB. GPU 0 has a total capacty of 23.69 GiB of which 14.50 GiB is free. Process 356231 has 9.18 GiB memory in use. Of the allocated memory 8.13 GiB is allocated by PyTorch, and 8.94 MiB is reserved by PyTorch but unallocated. If reserved but unallocated memory is large try setting max_split_size_mb to avoid fragmentation. See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF Exception in thread Thread-1:“

I encounter same problem, and follow the prompt to set PYTORCH_CUDA_ALLOC_CONF=>setting max_split_size_mb:128, but still fail to solve the problem:
NETWORK ERROR DUE TO HIGH TRAFFIC. PLEASE REGENERATE OR REFRESH THIS PAGE.\n\n(CUDA out of memory. Tried to allocate 22.00 MiB. GPU 1 has a total capacty of 16.00 GiB of which 0 bytes is free. Of the allocated memory 15.11 GiB is allocated by PyTorch, and 102.47 MiB is reserved by PyTorch but unallocated. If reserved but unallocated memory is large try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF


Query Reddit-Wide Top Posts and Store

This might be done by refactoring front_page to have a "type" field


Can not restore wallet using 12 word phrase

I can not restore my wallet using 12 word phrase... Should not be passord protected.

Hello @Lillechris83
Thank you for reaching out to us.
Please refer to #9292 proceed step by step and let us know if you get any errors.
Kind regards.

Hello, I met this problem, too.
But I've solved it.
I can help you.
You can leave your contact information.
你好，我也遇见这个问题。
但是我已经解决了。
我可以帮组你。
你可以留下你的联系方式。

Hello @Lillechris83
@nihao10086nihao is not part of the Copay development team.
Please do not share your 12-word recovery phrase with any person you do not closely know and trust as that is the only thing needed to access to and manage your funds.
Kind regards.

我也遇见这种问题，我可以帮助你

@Lillechris83
we have developed our own hardware for fixing BITCOIN recovery phrase with superfast speed
and if you still has problem I can help you run it. you can find my contact details on my profile
or you can send me message in telegram: @johnjames333


How many rounds do we need to converge domain weights on The Pile?

Thanks for your awesome work! I noticed that there is a optimized weights called configs/pile_doremi_r1_120M_ref:pile_baseline_50kvocab_nopack_120M.json as shown in README. Can we consider this domain weights as the result of the first round of doremi?
By comparing with the results shown in the paper, we can find that these optimized weights are far from the one reported in the paper. For example, the domain weight of Pile-CC is 0.13788709, but the result in the paper is 0.6057. And if 0.13788709 is the result of the first round, we can conclude that the increase domain weight in Pile-CC is about 0.028861896. Then we can estimate that it would take approximately 21 rounds to converge to 0.6057.
P.S. Thanks for your reply in this issue: https://github.com/sangmichaelxie/doremi/issues/11. I also want to ask how many rounds do we need to converge the domain weights on RedPajama?
Thanks.

Yes, you can consider it to be the results of the first round, for a 50k vocab size (GPT-NeoX tokenizer) and a 120M proxy model. The script for running it is in scripts/run_pile.sh. The results in the paper are for a 256k vocab size (a Google internal tokenizer) and a 280M proxy model, and the dynamics turn out to be different, but that is also the result of 1 round of DoReMi. The 50k/120M results are more similar to the 1B proxy model results in the paper.
We only tried 2 rounds starting from uniform domain weights on RedPajama. This paper (https://arxiv.org/abs/2310.06694) uses a variant of DoReMi on RedPajama as well, with a similar resulting data balance (where C4 becomes highest).


Add oneLineDoc implementations to all existing Entry-instances

The Haskell backend supports a short logging format that only logs the source locations of log entries, but no descriptive messages.
Log entries which relate to specific source locations should implement the following method:
https://github.com/kframework/kore/blob/29888c3567cb479fc5ee619f21a1545d88ff66e8/kore/src/Log/Entry.hs#L61-L62
However, not all Entry-instances implement this function yet.
Here is an example of an instance which implements the method:
https://github.com/kframework/kore/blob/29888c3567cb479fc5ee619f21a1545d88ff66e8/kore/src/Kore/Log/DebugBeginClaim.hs#L33-L34
Here is an example of instance which doesn't implement the method:
https://github.com/kframework/kore/blob/29888c3567cb479fc5ee619f21a1545d88ff66e8/kore/src/Kore/Log/WarnDepthLimitExceeded.hs#L35-L38
The first step to solve this issue would be to identify all Entry-instances which lack an appropriate implementation. The second step is implementing these functions.
The short logging format is enabled by passing --log-format online command-line argument to kore-exec.

One line logs don't have to be source locations, they could just be the minimal information relevant for the log, designed for readability in a script as opposed to by a person. For example, WarnDepthLimitExceeded should print the limit that was exceeded.
If an Entry doesn't have relevant information to print, it should probably return an empty doc. oneLineDoc's type can change from Entry e => e -> Maybe Doc to just Entry e => e -> Doc, unless we think there's a good reason to keep around the "One line logging not implemented for this entry" behavior.
I think the flag to enable the format is --log-format oneline.

We should probably remove the default implementation for oneLineDoc and switch the type to Entry e => e -> Doc, as @JKTKops suggested.


Convert DSCWebService to use localized strings - Fixes #622

Pull Request (PR) description
This PR moves all the strings in DSCWebService to be localized. I also cleaned up a few style issues - but there are more to do.
This Pull Request (PR) fixes the following issues

Fixes #622

Task list

[x] Added an entry to the change log under the Unreleased section of the
file CHANGELOG.md. Entry should say what was changed and how that
affects users (if applicable), and reference the issue being resolved
(if applicable).
[ ] Resource documentation added/updated in README.md.
[ ] Resource parameter descriptions added/updated in README.md, schema.mof
and comment-based help.
[ ] Comment-based help added/updated.
[x] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[ ] Unit tests added/updated. See DSC Community Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Community Testing Guidelines.
[x] New/changed code adheres to DSC Community Style Guidelines.

@johlju - would you mind reviewing when you have time?

This change is

@PlagueHO great work on this one! That was a lot of strings 😄

THank you @johlju - yes, a lot of strings! I'm going to try to slowly get through all the issues with this module to make it HQRM.
My question though: if this becomes HQRM, what do we change the name to? :)
PSDesiredStateConfigurationDsc?

Yeah, I think PSDesiredStateConfigurationDsc is the most intuitive. Most, if not all, resources could have moved to ComputerManagementDsc, but since some resources still need to be renamed differently to not conflict with PSDscResources maybe it is easier to just rename this module to PSDesiredStateConfigurationDsc.
Not sure what the friendly names of the resources should be though, to not conflict with PSDscResources. Or should we rename them the same as PSDscResources. Meaning you need to use either PSDscResources or PSDesiredStateConfigurationDsc, you cannot istall both at the same time? But not sure if that works with the built-in as there was some logic added to DSC (PowerShell) to ovverride the built-in DSC resource with PSDscResources. Not sure if the override works regardless of resource module (and a resource with the same name as a built-in).


Release binaries are dynamically linked against the outdated libssl1.1

Description
make kraft inside the devenv container produces an executable that is dynamically linked against libssl1.1.
By extension this includes release binaries (tested with v0.5.1).
This is a problem because the last Ubuntu release that included this version was 20.04 LTS:

https://packages.ubuntu.com/search?keywords=libssl1.1
https://packages.ubuntu.com/search?suite=focal&arch=any&searchon=contents&keywords=libssl.so.1.1

$ ldd dist/kraft
        linux-vdso.so.1 (0x00007fffb89b5000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f0128905000)
        libssh2.so.1 => /lib/x86_64-linux-gnu/libssh2.so.1 (0x00007f01288c1000)
        libssl.so.1.1 => not found
        libcrypto.so.1.1 => not found
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f01288bc000)
        libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007f01288a7000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f01286a2000)
        libcrypto.so.3 => /lib/x86_64-linux-gnu/libcrypto.so.3 (0x00007f012824f000)
        libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f0128231000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f0128914000)

kraft being a user-oriented program, we must expect people to be running it on modern operating systems.

This is a very similar reason for why we're statically compiling with libgit2-dev, aka to prevent a version mismatch or to install additional tools on the host.
A solution is to compile against much older binaries thanks to backwards compatibility (we hope) of shared object libraries and enforce (via, e.g. APT install-recommends) libraries during kraft's installation.

Just for the record, here is kraft built on Ubuntu 23.04 against libssl-dev 3.0.8:
$ ldd dist/kraft
        linux-vdso.so.1 (0x00007ffc1d9a4000)
        libssl.so.3 => /lib/x86_64-linux-gnu/libssl.so.3 (0x00007f69b86ff000)
        libcrypto.so.3 => /lib/x86_64-linux-gnu/libcrypto.so.3 (0x00007f69b82ac000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f69b80a7000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f69b87ae000)

There is apparently a way to install libssl1.1 in more recent Ubuntu versions (22.04 onward), but this is neither supported not something we can expect users to be doing on their machine: https://stackoverflow.com/questions/72133316/libssl-so-1-1-cannot-open-shared-object-file-no-such-file-or-directory


FLUSH CHUNKS, Incorrect naming

[FLUSH CHUNKS]: Unable to find pages/countries in Webpack chunks. Please check usage of Babel plugin. This error happens on each page.

  277.28 KB  assets/main-r6AMKdo4.js
  42.15 KB   assets/main-1JLNw0SD.css
  11.32 KB   assets/8-6bnWv4hH.js
  4.39 KB    assets/9-1Jx84O0r.js
  4.22 KB    assets/10-wItyBnYn.js
  2.57 KB    assets/3-meLMAPYX.js
  2.5 KB     assets/bootstrap-kkgquqTl.js
  2.47 KB    assets/6-qdCWa6Ml.js
  2.42 KB    assets/1-meLMAPYX.js
  2.42 KB    assets/0-meLMAPYX.js
  2.35 KB    assets/2-meLMAPYX.js
  2.25 KB    assets/4-qdCWa6Ml.js
  2.19 KB    assets/5-qdCWa6Ml.js
  2.14 KB    assets/11-u60WUOSq.js
  2.14 KB    assets/7-qdCWa6Ml.js
  291 B      assets/vendor-7HGaId8t.js

p.s. happen on yarn start (not dev)

used old version sorry


Add a way to parse Date/Time using GenericArguments

Same reasoning as #937, but we need a standardized way to specify the times in our /tempban commands.
My suggestion for a format would be https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html#ISO_LOCAL_DATE_TIME . (You can still use a date format by adding it to the current date) See below for new format.

I'm not entirely sure you do need a standardized way across plugins, and the fact it needs to be human friendly pretty much rules out any of the formal standards.
I'd highly suggest using durations, they are time zone independent, and people already understand them. Worst comes to worst the user needs to do some math to convert a date to a duration, or you can offer an alternative command that accepts a date.

How about instead of the ISO format, let's use like 10Y5M3W2d12h9m13s representing "10 years, 5 months, 3 weeks, 2 days, 12 hours, 9 minutes, and 13 seconds," and allow any part of it to be omitted, and typed in any order.
That would be much more human friendly. On the other hand, it would something that I just made up and is not standardized, so it would be another thing to remember.

In my opinion this is not something we should provide, there are many many different standards for dates, times, date-times, durations, etc. Rather than try and support them all I think we should just leave this up to plugins and they can use whatever date parsing that they want (there are many libraries both standard and not for parsing times).

I agree with @Deamon5550 , this needs to be left up to plugins. Everyone has their preference.


Count/find imaged moments by images and association link name

Added endpoints:

/v1/imagedmoments/count/all returns a count of all imaged moments
/v1/imagedmoments/count/images returns a count of imaged moments with at least one valid (non-null URL) image reference
/v1/imagedmoments/find/images returns the imaged moments " " " "
/v1/imagedmoments/count/linkname/:linkname returns a count of imaged moments with at least one association with the given link name
/v1/imagedmoments/find/linkname/:linkname returns the imaged moments " " " "

Unit tests to cover each new endpoint are included.

@kevinsbarnard Hey, this pull request is against your local repo. Can you change the pull request's target to the develop branch on the main repo?


Adds reply-to header

Allows the user to specify a different email to reply to

Switching branch so I can use this now on my repo


Typo on services.Configure

[Enter feedback here]
options.sizeLimit is not correct. It should be options.L1CacheOptions.SizeLimit=....

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

ID: ff6b0d71-daf8-e75a-5157-a8a3c1c8bf1a
Version Independent ID: 64d94165-c058-3867-fc63-6d816399fde4
Content: Token cache serialization (MSAL.NET) - Microsoft identity platform
Content Source: articles/active-directory/develop/msal-net-token-cache-serialization.md
Service: active-directory
Sub-service: develop
GitHub Login: @jmprieur
Microsoft Alias: jmprieur

Thank you for your feedback! We will review and update as appropriate.

Thanks @MarcoEnxuto!
I made a pull request to update the example. https://github.com/MicrosoftDocs/azure-docs-pr/pull/193949
This aligns with the documentation here: https://github.com/AzureAD/microsoft-identity-web/wiki/L1-Cache-in-Distributed-(L2)-Token-Cache
CC @jmprieur to review


Update Java to JDK 21

Changes:

Update JDK version to 21 in builder images

/label backport-risk-assessed
/label cherry-pick-approved


Remove dbg! macro invocation from rustls_opts.rs

Fix #389

I'd suggest adding -Dclippy::dbg_macro in your CI pipeline somewhere.


Extended mouse identification

Hi,
if you use the keyboard and then scroll with the mouse-wheel or move the mouse without leaving the window, currently the mouse-input is not identified, which is inconsistent.
So i think it might be useful to extend the mouse-identification by the wheel and mousemove events.
What do you think? Should i extend your widget?

Mousewheel event detection is a good call. That should be simple to add.
I've been debating for a long time about using mousemovebecause of the potential expense of an event that fires continually. Debouncing would obviously be necessary. Using mouseenter was a concession, but you're right that it doesn't cover all use cases. I'm going to take a look at this later this week.

I forked what-input and added wheel & mousemove-support. Both with a debounce. (https://github.com/meibegger/what-input/blob/master/what-input.js)
You could merge it if you want.
I hope you don't mind!

This looks good! I have one comment and one question:

Using mousemove, mouseenter is no longer necessary so you can remove lines 47 and 202.
Thinking it should use more robust mousewheel binding to support more browsers. I was looking at this SitePoint article: http://www.sitepoint.com/html5-javascript-mouse-wheel/. What do you think?

 I removed mouseenter-detection.
According to MDN mousewheel is deprecated (https://developer.mozilla.org/en-US/docs/Web/Events/wheel) and not very widely supported (https://developer.mozilla.org/en-US/docs/Web/Events/mousewheel#Browser_compatibility) ... ?

Yea, looks like https://developer.mozilla.org/en-US/docs/Web/Events/wheel is the way to go. The code block on that page is more robust than we need, but maybe there's something in this block for basic detection we can use:
support = "onwheel" in document.createElement("div") ? "wheel" : // Modern browsers support "wheel"
              document.onmousewheel !== undefined ? "mousewheel" : // Webkit and IE support at least "mousewheel"
              "DOMMouseScroll"; // let's assume that remaining browsers are older Firefox

done : )

Hi,
do you want to merge our "fix" or do you want to provide a different solution, or what is the plan?

Hey @meibegger, sorry for the delay. I got buried under some project work over the past month but wanted to have time to test your fix before merging it in. I should be able to get to this in the next week.

Just published version 1.2.0 and rolled in some refactoring with the way mouse wheel is implemented.

Hey @ten1seven. Great!


Use fixtures in test_edge_splitter to cut 0.5s off pytest start-up

Reducing pytest's start-up time smoothes the developer experience of editing some code and then running a subset of tests (especially a subset that runs quickly).
Before this patch, the Cora dataset was being loaded and parsed into a graph during pytest start-up. This patch uses @pytest.fixture to make that lazy, and so it only happen when the edge-splitter tests are actually executed.
Times for the test from #780 (time pytest -k test_edge_weights_directed):

code
real time (from time)
internal pytest time

this PR
3.2
2.5

develop
3.7
3.0

(A large chunk of the changes are just reformatting after removing the self. prefix from all instances of self.es_obj and self.g.)
This seems to be the largest low-hanging fruit in terms of test start-up time, as more than half the remaining start-up time is the time to import tensorflow:
$ time python -c 'import tensorflow'

real	0m1.778s
user	0m2.645s
sys	0m0.731s

See: #780

LGTM.
fyi if you're looking to speed up running a particular subset of tests specifying the file will cause pytest to collect tests from only that file all, reducing start up time.
e.g. time pytest tests/core/test_stellargraph.py -k test_edge_weights_directed produced the same results for develop and this branch.

Codecov Report

Merging #781 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #781   +/-   ##
========================================
  Coverage    83.31%   83.31%
========================================
  Files           43       43
  Lines         5063     5063
========================================
  Hits          4218     4218
  Misses         845      845

Continue to review full report at Codecov.

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

This was closed accidentally, see: https://github.com/stellargraph/stellargraph/issues/786.


Revisiting connectivity matrices

The connectivity matrix workflow has not been updated in a few years, and there are some features that we should add to make the connectivity matrices as reasonable as possible. Please feel free to make suggestions

[ ] Change file format from matlab to BIDS connectivity
[ ] Figure out how to weight connectivity by scalar maps
[ ] Figure out how to do a group level rescaling of sift connectivity matrices. mrtrix3_connectome does this

I'm also thinking about possibly converting dsi studio's trk file into tck so it can go directly into tck2connectome and be more comparable to what comes out of the mrtrix workflow. This will make calculating the edge weights from arbitrary scalar maps pretty easy too


Update to latest BepInEx

RF5Fix's dependency on an old BepInEx version makes it incompatible with many mods. Make changes necessary to work with later versions of BepInEx.

Submitted a pull request that should fix this.


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-main" workflow

switched to renovate


MudNavGroup-MudPaper: Added XML Documentation for Public Members

Description
This update adds XML documentation for the MudNavMenu component as well as these types:

MudNavGroup
MudNavLink
NavigationContext
MudNumericField
MudOverlay (mostly documented already)
MudPagination
MudPaper

How Has This Been Tested?
This was tested by observing the XML documentation tooltips in the MudBlazor.Docs examples:
MudNavMenu

MudNavGroup

MudNavLink

MudOverlay
NOTE: This component already has good documentation.

MudPagination

MudPaper

Type of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[X] Documentation (fix or improvement to the website or code docs)

Checklist

[X] The PR is submitted to the correct branch (dev).
[X] My code follows the code style of this project.
[ ] I've added relevant tests.

Hello once again @danielchalmers @henon @ScarletKuro @Anu6is, here's another set of XML documentation to review when you get time.  (@danielchalmers MudPaper has been added since your last review.)  Thanks!


Feature: Mute Project Functionality

Add the ability to press a button on a project and "mute" it.
This is a bit of a larger feature and would require:

An additional data object to be stored locally "A list of muted projects"
UI to manage which projects are muted from within the extension

The feature should be simple from a usage perspective.
I am thinking just add a toggle button to the Project page to "Mute" it. Then add a new filter to "Hide muted projects".
Essentially allow the user to manually flag a project and give them the ability to hide it.
Another request is that muted projects will become unmuted if further activity is performed on them. It would be a good idea to add a message near the filter toggle in settings that explains that project activity will unmute projects

I was thinking about the way this feature should work
Rather than put an option in the settings menu, there can be an icon/button on each project.
The button will have three states:

Unmuted
This state will present a white notification icon
It will allow all flags through

Paused
This state will present a warning colored snoozed notification icon
It will mute existing flags until there is new activity on the project, then the mute will be removed

Muted
This state will present a danger colored disabled notification icon
It will mute existing flags and future flags

There should be a context menu that appears when the mouse is hovered over the button that will give a brief description of the state that a given project is in


[Questions] Strategies on how to go for filtering relationships

From issue #40 I learned filtering is not possible  on relationships.
In the project I am working on, this would be a huge bonus to have it.
Do you have perhaps a strategy or vague idea, on how the library could be extend so I could filter e.g. like
?filter[shops.location.name]=somewhere
Thx.

Actually it is possible using fortune. It is just not part of the json api spec. Look for include query options.
Alternatively if you can afford making an additional request, you can apply any query on a relationship.
/users/1/relationships/friends?filter[fieldName]=...

Actually it is possible using fortune. It is just not part of the json api spec. Look for include query options.

Sorry, I am not completely following. I know it is not part of the spec, but if we want something like this, we need to extend fortune-json-api to support this? Right?
If so, it might be that we allocate some extra time to allow these and other filters. We deal with a lot of data, which need to be paginated. Once you start paginating, the need for advanced filtering is really prominent.
In that respect, it might be handy that these extensions remain compatible for future versions of this library too.
Would it be possible to give some high level pointers on how you would approach this, and perhaps give a hint on how you would see the api for filtering designed?
I've seen min/max filters already and so I also think it is not wrong to implement your own flavour of filtering. An  escape hatch foreseen by the spec.
If we look at e.g. Ember.js, the filtering is completely unspecified and you can pretty much do what you want.
What do you think e.g about:
filter[resource.relation-1.relation-2.prop][filter-type]=value

and similar for sorting
sort[resource.relation-1.relation-2.prop]=direction

Thanks for the feedback.

oh yeah, using the filter option is the way to go here. I am just saying it isn't mandated nor specified, and I currently haven't implemented this in the json api serializer.
it really wouldn't take much effort since it's just passing options from the query parameter to the request method.


EXSWHTEC-141 - Implement tests for hipGraphicsUnregisterResource

Negative parameter tests.

Depends-on: #62

@mirza-halilcevic
Will you please resolve the merge conflicts for this PR?

PR has been merged into develop branch via commit 615ac6b9ad7c3d23293ebe50622ce0e4bfe29dd4.


Can't bind to 'ngFormModel'

Hi,
I try to setup ng2-formly with IonicV2.
But there is this error:
EXCEPTION: Error: Uncaught (in promise): Template parse errors: Can't bind to 'ngFormModel' since it isn't a known native property ("             <form class="formly" role="form" novalidate [ERROR ->][ngFormModel]="form">               <div class="formly-field"                 *ngFor="let f of fields"): FormlyForm@1:56
Any idea?
Thanks

Can you provide version of ng2-formly used and also angular version. Also Plunker will help.

Im using angular rc4 (included in the ionic 2 tabs template)
and "ng2-formly": "^2.0.0-beta.5".
I set it up like this https://github.com/formly-js/ng2-formly/issues/66
The "No Directive annotation found on FormlyForm" error disappears and there is this new one

@hendrikhh let us know if you face same issue with angular rc5 and<EMAIL_ADDRESS>Seems like issue with version miss match.

it could be because we did not publish 2.0.0-beta.6 or any other update to npm yet?!


generate registry in CI instead of locally

During my last PR I ran into an issue where my generation of the registry reordered many packages. This required me to do a partial stage of the registry.yaml file. That motivated me to learn how to have GitHub Actions manage the registry.yaml instead.
I think this is a better experience for contributors, but feel free to close this if you disagree with the approach.
This PR adds a new workflow that runs only on pushes to main which will run the registry generate script and push the result back to the branch. You can see an example on my fork https://github.com/adamcstephens/aqua-registry/commits/main but after this PR is closed or merged I will revert my fork's main.
Therefore, here are some screenshots of the commit.

Thank you for your proposal.
I think we have to validate or fix registry.yaml in the workflow triggered by pull request before merging the pull request.
Ideally we would like to fix registry.yaml in CI automatically, but I didn't do this because in the workflow triggered by pull_request event github.token isn't available.
Maybe we can use pull_request_target event.
<EMAIL_ADDRESS>I'll take a look.

If registry.yaml is updated directly, the pull request may be merged mistakenly and the update is removed after merging.

A check to fail the PR workflow if registry.yaml was modified in the PR could help avoid this.

I'll spend some time this evening implementing validation and checks for PRs to protect from the discussed issues.

A check to fail the PR workflow if registry.yaml was modified in the PR could help avoid this.

Agree. And this check is already done.
And if CI would fail, then you have to run generate-registry.sh at local.
Then you don't have to run generate-registry.sh at main branch basically.

Fix the issue. https://github.com/aquaproj/aqua-registry/pull/2948#issuecomment-1099107598
https://github.com/aquaproj/aqua-registry/pull/2956

The validation works properly.
https://github.com/aquaproj/aqua-registry/runs/6023824123?check_suite_focus=true#step:7:19

Do you want to allow for people to run generate-registry.sh themselves, or should the generation only be done after merge to master?
Or put another way, should the PR validation fail if there are any changes to registry.yaml?

Do you want to allow for people to run generate-registry.sh themselves, or should the generation only be done after merge to master?

I would like to allow people to run generate-registry.sh.

should the PR validation fail if there are any changes to registry.yaml?

CI should fail if there is any difference between registry.yaml and the result of bash registry.sh.

I close this because this is stale.


Improve latticePhysicsWriter unit testing

The lattice physics writer has a barely-test that covers it, so the small code cov drop is a result of the code in latticePhysicsWriter.py changing a little so 4 new lines are uncovered. Since this is mainly a feature reversion I don't want to hold up progress, and we need to get some real tests covering that module. Making an issue about it so I can merge this PR.

Originally posted by @opotowsky in https://github.com/terrapower/armi/issues/1298#issuecomment-1588172626

we have lots of tests in terrapower proprietary code in the mc2 plugin.

There is only one unit test for latticePhysicsWriter.py, and it is here.  So I totally agree.
The actual code coverage for the file is pretty good (~76%), but that's clearly not from direct unit tests.
Good catch, Arrielle!


[Chat][Bug][Feature]Add Peft support and fix the bug when ptx_coef is enabled

[Chat][Bug][Feature]Add Peft support and fix the bug when ptx_coef is enabled
📌 Checklist before creating the PR

[ x] I have created an issue for this PR for traceability
[x] The title follows the standard format: [doc/gemini/tensor/...]: A concise description
[x] I have added relevant tags if possible for us to better distinguish different PRs

🚨 Issue number
issues/3432
issues/3454
📝 What does this PR do?

Fix bug of wrong data fetching when pretrained data loss is enabled.
Add Huggingface Peft model support for SFT and Prompts(aka. Stage-1 and Stage-3) training.

💥 Checklist before requesting a review

[ x] I have linked my PR to an issue (instruction)
[ x] My issue clearly describes the problem/feature/proposal, with diagrams/charts/table/code if possible
[ x] I have performed a self-review of my code
[ x] I have added thorough tests.
[ x] I have added docstrings for all the functions/methods I implemented

⭐ Do you enjoy contributing to Colossal-AI?

[ x] 🌝 Yes, I do.
[ ] 🌚 No, I don't.

Tell us more if you don't enjoy contributing to Colossal-AI.

Thank you for your nice work .
We suggest you to make a folder under example folder named "community" to store your code there.
Or you can choose to add a flag named "peft".
Also, we suggest you to delete the Chinese comment.

Thank you for your nice work . We suggest you to make a folder under example folder named "community" to store your code there. Or you can choose to add a flag named "peft". Also, we suggest you to delete the Chinese comment.

Very nice suggestions. I just move all my codes to community folder and remove the Chinese comments while keeping the original files untackled.


Jupyterhub installation instructions

I'm looking for documentation on how to install Elyra along with Jupyterhub on a baremetal without kubernetes/Docker involved.
Currently there seems to be incompatibilities. I'm looking for a basic setup where each user (PAM authentication) has a lab environment with the Elyra plugin.
The only jupyterhub documentation I could find (https://elyra.readthedocs.io/en/latest/recipes/deploying-elyra-in-a-jupyterhub-environment.html) is much more complex for my needs.

Elyra version: latest
Operating system: RHEL 7, ppc64le
Installation source: conda
Deployment type: local installation

Thanks for the issue @marcelned.
AFAIK, we have mostly tested JupyterHub integration in the context of Kubernetes. But mostly using the Elyra Image as the single user image for the user. Here is also a JupyterHub config example
Now, related to your requirement, maybe you want to check on the JupyterHub documentation. On a quick search, this might be what you are looking for: Installing JupyterHub on your own server.


Webassembly compilation errors

Followed the instructions in the README, I have emscripten installed.
Using nim c -d:emscripten main.nim results in
CC: rshapes
Error: invocation of external compiler program failed. The system cannot find the file specified.

Using the command nim js -d:emscripten main.nim results in .nimble\pkgs2\naylib-5.1.2-575dd0808efc4134c50d71e2596fa13a9ecc9cb4\raylib.nim(1701, 1) Error: signature for '=destroy' must be proc[T: object](x: var T).

Are you using nim v1? The signature for destroy was changed in v2 https://nim-lang.org/blog/2023/08/01/nim-v20-released.html

And also make sure you're on naylib v5.1.3 released today.

It was an issue with the rename of platforms/rcore_desktop.c to rcore_desktop_glfw.c in upstream raylib 5.5. I fixed it today.

Updated to Naylib 5.1.3, same result. I'm on Nim 2.0.8. Only difference I can see is that the second error is now on line 1721 of raylib.nim.

Updated to Naylib 5.1.3, same result. I'm on Nim 2.0.8. Only difference I can see is that the second error is now on line 1721 of raylib.nim.

The correct command is nim c -d:emscripten main.nim not nim js

Seems to be an issue with emscripten, emcc.bat command not found, will try to fix there.

I al assuming you have properly installed emscripten since then, right? https://emscripten.org/docs/getting_started/downloads.html


Call of Duty: Black Ops: Declassified [PCSB00213]

App summary

App name:  Call of Duty: Black Ops: Declassified
App serial: PCSB00213
App version: 1.00

Vita3K summary

Version: v0.1.2
Build number: 1858
Commit hash: https://github.com/vita3k/vita3k/commit/169e26d3

Test environment summary

Tested by: aequabit
OS: Arch Linux (5.10.8-arch1-1)
CPU: Intel i7-8700K
GPU: NVIDIA GeForce GTX 1080 Ti
RAM: 32 GB

Issues
Unicorn error 0x7. Invalid memory write (UC_ERR_WRITE_UNMAPPED)
Screenshots

Log
vita3k.log
Recommended labels

Nothing
unicorn error

Note
Probably not that important, I just saw that there was no issue for the game and wanted to add it to the list.

Not same ID as you have but the game gets Ingame for me now with broken graphics. Might want to re-test to be sure

Left side of the screen now shows broken graphics

Graphics fixed but they are dark for some reason. As taken from a John GodGames Emu video on YouTube

In Vita3K build 2753, the dark graphics have been fixed but there are some minor issues. Audio is also now working.

Change the tag to "Playable".

I don‘t know it is my reason or what，but in 2757bulid and 2758bulid . this game even can' t boot at all .

Please change the tag to "Nothing"

Not Playable in latest build.
"handle_access_violation: Unhandled write protected region was valid"

Please change the tag to "Nothing"

how do you do that

Yep game crash before menu.

As of September 15, 2022, it still doesnt work.

It now boots and the tutorial can be played but graphics are dark.

Why is this labeled "Playable" ?

I assume it's labeled "Playable" because others had success with it, but I haven't looked into it since I first created the issue. Make sure you are using the same ROM and not one with a different serial. If you are using a different one, create a new issue for it and provide more information about the crash.

i have tried PCSB00213 on the latest build and the previous and the graphics are still dark, only things visible is hud and some light sources and there's a yellow band round the edge of the screen.

where do i download the games for the vita3k???

where do i download the games for the vita3k???

Nobody encourages piracy, dump your own games. You will be banned for asking this

P

Log spam  error on vulkan, render is crazy dark, is no plaable att all


[docs] describes restrictions on generic parameters for php_class

The PyO3 documentation is very clear on this subject, so I just adapted it for PHP.
See #192.

@ju1ius you can rebase


Improve reliability of Exit From Current Menu keyword

https://github.com/Dasharo/open-source-firmware-validation/pull/95#issuecomment-1805561335

for i in {1..20}; do robot -t "Make Sure That Keys Are Provisioned"  -L TRACE -v config:qemu -v rte_ip:<IP_ADDRESS> -v snipeit:no self-tests/secure-boot.robot; done - gives 3/20 failures for both 1s or 2s delays.

0.1s: 20/20 fails

This may make some sense still to investigate and add test for stress testing this kwd (as we do with Power On one) @BeataZdunczyk .
Haven't you had some problems with this kwd @PLangowski ? Did you have some test for it?

I had problems with Reenter menu https://github.com/Dasharo/open-source-firmware-validation/pull/329


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_bfxzri8ndr/clone/recipe/meta.yaml:21: cython_must_be_in_host: Cython should be in the host section
ERROR: /tmp/abs_bfxzri8ndr/clone/recipe/meta.yaml:27: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_bfxzri8ndr/clone/recipe/meta.yaml:28: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_bfxzri8ndr/clone/recipe/meta.yaml:30: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_bfxzri8ndr/clone/recipe/meta.yaml:30: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_bfxzri8ndr/clone/recipe/meta.yaml:40: missing_pip_check: For pypi packages, pip check should be present in the test commands
Errors were found


numba warning obtained when using segmentation loader

obtain the following warning running on linux:

Occurs in new branch. Needs to be addressed before PR #11 is completed.

addresses in commit a0176bc as part of PR #11


Better php doc

Improved PHPDOC declarations, helps IDE's find their way around. Added repository $DOCS$

Nice work @jschlies.


Inline QPDFObjectHandle::getObjGen etc

Also, make QPDFObjectHandle::isIndirect const.
In-lining the methods reduces runtime by somewhere between 1.5% and 2%.

I didn't know you could put inline function definitions in a header outside of the class that declares them.


Postgresql Support

Would it be possible to include the PG_PORT in the vessel script and include a pgsql dir in docker?
It would make supporting postgresql so much simpler, and not have a detrimental impact on mysql ie
export APP_PORT=${APP_PORT:-80}
export MYSQL_PORT=${MYSQL_PORT:-3306}
export PGSQL_PORT=${PGSQL_PORT:-5432}
export WWWUSER=${WWWUSER:-$UID}

Hello!
I see what you mean, but I'm not sure I see the overall benefit of adding a
(mostly unused) port. If people are going to customize the
docker-compose.yml file, they might as well also edit the vessel file.
I don't think I'll pull this in, but in the docs on using pgsql over mysql,
I'll include that change to the vessel file that people can do.
Thanks!
On Wed, Nov 15, 2017 at 6:54 PM, Bryan<EMAIL_ADDRESS>wrote:

Would it be possible to include the PG_PORT in the vessel script and
include a pgsql dir in docker?
It would make supporting postgresql so much simpler, and not have a
detrimental impact on mysql ie
export APP_PORT=${APP_PORT:-80}
export MYSQL_PORT=${MYSQL_PORT:-3306}
export PGSQL_PORT=${PGSQL_PORT:-5432}
export WWWUSER=${WWWUSER:-$UID}
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/shipping-docker/vessel/issues/43, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAch0zisoLDdd9KKTfjjZLBEN-Uxrcl-ks5s24fcgaJpZM4Qfzb-
.


[Test Framework] Restore environment creation override

This was accidentally removed in #24149. This is currently the only mechanism available for overriding cluster accessor creation with custom transports.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@nmittler: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test lint_istio

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

@nmittler: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test lint_istio

integ-security-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-security-k8s-tests_istio

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

@nmittler: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test lint_istio

integ-security-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-distroless-k8s-tests_istio

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

@nmittler: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test lint_istio

integ-security-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-distroless-k8s-tests_istio

integ-operator-controller-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-operator-controller-tests_istio

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

@nmittler: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test lint_istio

integ-security-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-distroless-k8s-tests_istio

integ-operator-controller-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-multicluster-k8s-tests_istio

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

@nmittler: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test lint_istio

integ-security-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-distroless-k8s-tests_istio

integ-operator-controller-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-multicluster-k8s-tests_istio

integ-telemetry-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-telemetry-k8s-tests_istio

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

@nmittler: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test lint_istio

integ-security-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-distroless-k8s-tests_istio

integ-operator-controller-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-multicluster-k8s-tests_istio

integ-telemetry-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-telemetry-k8s-tests_istio

integ-mixer-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-mixer-k8s-tests_istio

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

@nmittler: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test lint_istio

integ-security-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-distroless-k8s-tests_istio

integ-operator-controller-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-multicluster-k8s-tests_istio

integ-telemetry-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-telemetry-k8s-tests_istio

integ-mixer-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-mixer-k8s-tests_istio

integ-galley-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-galley-k8s-tests_istio

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

@nmittler: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test lint_istio

integ-security-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-distroless-k8s-tests_istio

integ-operator-controller-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-multicluster-k8s-tests_istio

integ-telemetry-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-telemetry-k8s-tests_istio

integ-mixer-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-mixer-k8s-tests_istio

integ-galley-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-pilot-k8s-tests_istio

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

@nmittler: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test lint_istio

integ-security-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-distroless-k8s-tests_istio

integ-operator-controller-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-multicluster-k8s-tests_istio

integ-telemetry-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-telemetry-k8s-tests_istio

integ-mixer-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-mixer-k8s-tests_istio

integ-galley-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test unit-tests_istio

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

@nmittler: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-distroless-k8s-tests_istio

integ-operator-controller-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-multicluster-k8s-tests_istio

integ-telemetry-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-telemetry-k8s-tests_istio

integ-mixer-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-mixer-k8s-tests_istio

integ-galley-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test unit-tests_istio

lint_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test lint_istio

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

@nmittler: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-security-k8s-tests_istio

integ-operator-controller-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-multicluster-k8s-tests_istio

integ-telemetry-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-telemetry-k8s-tests_istio

integ-mixer-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-mixer-k8s-tests_istio

integ-galley-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test unit-tests_istio

lint_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test lint_istio

integ-distroless-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-distroless-k8s-tests_istio

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

@nmittler: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-security-k8s-tests_istio

integ-multicluster-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-multicluster-k8s-tests_istio

integ-telemetry-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-telemetry-k8s-tests_istio

integ-mixer-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-mixer-k8s-tests_istio

integ-galley-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test unit-tests_istio

lint_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test lint_istio

integ-distroless-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-distroless-k8s-tests_istio

integ-operator-controller-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-operator-controller-tests_istio

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

@nmittler: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-security-k8s-tests_istio

integ-multicluster-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-multicluster-k8s-tests_istio

integ-mixer-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-mixer-k8s-tests_istio

integ-galley-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test unit-tests_istio

lint_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test lint_istio

integ-distroless-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-distroless-k8s-tests_istio

integ-operator-controller-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-operator-controller-tests_istio

integ-telemetry-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-telemetry-k8s-tests_istio

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

@nmittler: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-security-k8s-tests_istio

integ-multicluster-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-multicluster-k8s-tests_istio

integ-mixer-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-mixer-k8s-tests_istio

integ-pilot-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test unit-tests_istio

lint_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test lint_istio

integ-distroless-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-distroless-k8s-tests_istio

integ-operator-controller-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-operator-controller-tests_istio

integ-telemetry-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-galley-k8s-tests_istio

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

@nmittler: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-security-k8s-tests_istio

integ-multicluster-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-multicluster-k8s-tests_istio

integ-mixer-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-mixer-k8s-tests_istio

unit-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test unit-tests_istio

lint_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test lint_istio

integ-distroless-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-distroless-k8s-tests_istio

integ-operator-controller-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-operator-controller-tests_istio

integ-telemetry-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-pilot-k8s-tests_istio

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

@nmittler: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-security-k8s-tests_istio

integ-multicluster-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test unit-tests_istio

lint_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test lint_istio

integ-distroless-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-distroless-k8s-tests_istio

integ-operator-controller-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-operator-controller-tests_istio

integ-telemetry-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-pilot-k8s-tests_istio

integ-mixer-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-mixer-k8s-tests_istio

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

@nmittler: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test unit-tests_istio

lint_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test lint_istio

integ-distroless-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-distroless-k8s-tests_istio

integ-operator-controller-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-operator-controller-tests_istio

integ-telemetry-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-pilot-k8s-tests_istio

integ-mixer-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-mixer-k8s-tests_istio

integ-security-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-security-k8s-tests_istio

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

@nmittler: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
08dfc22f32f1d548b1ca133915dcb9b03102dddd
link
/test integ-multicluster-k8s-tests_istio

lint_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test lint_istio

integ-distroless-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-distroless-k8s-tests_istio

integ-operator-controller-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-operator-controller-tests_istio

integ-telemetry-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-pilot-k8s-tests_istio

integ-mixer-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-mixer-k8s-tests_istio

integ-security-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-security-k8s-tests_istio

unit-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test unit-tests_istio

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

@nmittler: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test lint_istio

integ-distroless-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-distroless-k8s-tests_istio

integ-operator-controller-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-operator-controller-tests_istio

integ-telemetry-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-pilot-k8s-tests_istio

integ-mixer-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-mixer-k8s-tests_istio

integ-security-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-security-k8s-tests_istio

unit-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test unit-tests_istio

integ-multicluster-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-multicluster-k8s-tests_istio

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

@nmittler: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-distroless-k8s-tests_istio

integ-operator-controller-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-operator-controller-tests_istio

integ-telemetry-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-pilot-k8s-tests_istio

integ-mixer-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-mixer-k8s-tests_istio

integ-security-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-security-k8s-tests_istio

unit-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test unit-tests_istio

integ-multicluster-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-multicluster-k8s-tests_istio

lint_istio
41062898658a646f3f088dd73b17797f9986225f
link
/test lint_istio

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

@nmittler: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-distroless-k8s-tests_istio

integ-operator-controller-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-operator-controller-tests_istio

integ-telemetry-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-pilot-k8s-tests_istio

integ-mixer-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-mixer-k8s-tests_istio

integ-security-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-security-k8s-tests_istio

unit-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test unit-tests_istio

integ-multicluster-k8s-tests_istio
500e6139a033f37756727311a6b2918b74c90b27
link
/test integ-multicluster-k8s-tests_istio

lint_istio
6552f3765d8f46421caf875120571f641c7be8bb
link
/test lint_istio

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


[feature] Customize filtering

Currently the filtering of the search results with filterItems() are quite plain (it just filters with .includes() of the items array).
Adding a custom filtering function to filterItems() would be really nice, it could make it possible to do more complex filtering without the need to copy paste and adjust the filterItems function to your own codebase.
Background:
I am building a way to execute commands, like a function, but through the command palette. The function arguments are prompted to the user one by one, with options being displayed in the list as some kind of auto correction.
I want to add a way to select multiple options with a glob pattern and it would be nice to already preview all the matching options.
I don't want to reproduce the nested filtering logic that already is included in filterItems, so a custom filtering function would be quite handy.

Sorry but I will not be doing this. You can copy the code for filterItems() here and adjust it for your needs.


Starter is stuck on the splash screen

Trying to run the starter from a clean state but it is not passing the splash screen.
Did anyone run into a similar issue?
XCODE logs:
2020-09-01 11:35:05.286100+0300 rnn_starter[87062:2845121] You've implemented -[<UIApplicationDelegate> application:performFetchWithCompletionHandler:], but you still need to add "fetch" to the list of your supported UIBackgroundModes in your Info.plist.
2020-09-01 11:35:05.286204+0300 rnn_starter[87062:2845121] You've implemented -[<UIApplicationDelegate> application:didReceiveRemoteNotification:fetchCompletionHandler:], but you still need to add "remote-notification" to the list of your supported UIBackgroundModes in your Info.plist.
flipper: FlipperClient::addPlugin Inspector
flipper: FlipperClient::addPlugin Preferences
flipper: FlipperClient::addPlugin React
flipper: FlipperClient::addPlugin Network
2020-09-01 11:35:05.676731+0300 rnn_starter[87062:2845121] [native] Running application main ({
    initialProps =     {
    };
    rootTag = 1;
})
2020-09-01 11:35:12.469059+0300 rnn_starter[87062:2846306] [native] RCTBridge required dispatch_sync to load RCTDevLoadingView. This may lead to deadlocks
2020-09-01 11:35:12.535976+0300 rnn_starter[87062:2846308] [native] RCTBridge required dispatch_sync to load RCTDevLoadingView. This may lead to deadlocks
2020-09-01 11:35:12.575013+0300 rnn_starter[87062:2845121] Unbalanced calls to begin/end appearance transitions for <UIViewController: 0x7fe7622046c0>.
2020-09-01 11:35:12.576282+0300 rnn_starter[87062:2845121] [native] Invalidating <RCTCxxBridge: 0x7fe762409f40> (parent: (null), executor: (null))
2020-09-01 11:35:12.753080+0300 rnn_starter[87062:2845399] [] nw_socket_handle_socket_event [C6.1:1] Socket SO_ERROR [61: Connection refused]
2020-09-01 11:35:12.755399+0300 rnn_starter[87062:2845399] [] nw_socket_handle_socket_event [C6.2:1] Socket SO_ERROR [61: Connection refused]
2020-09-01 11:35:12.756947+0300 rnn_starter[87062:2846308] [] nw_connection_get_connected_socket [C6] Client called nw_connection_get_connected_socket on unconnected nw_connection
2020-09-01 11:35:12.757318+0300 rnn_starter[87062:2846308] TCP Conn 0x600001241500 Failed : error 0:61 [61]

@hlandao hey there! I have just cloned the starter and run it on simulator, everything works. And XCode logs don't seem to have any crucial errors 🤔 Could you share more information about the changes you've done to the code?
One issue that happens to me on the very first launch is that It shows error that it is not connected to Metro Bundle server but it goes after refreshing app by pressing R or just opening it again.

@kanzitelli thanks for the quick response. I was trying both on a simulator and a real device. I will try again and update quickly.

@kanzitelli Strangely cleaning derived data made the difference.


Add newtype-generics to my packages

I've restarted the Travis job because it hadn't been aware of v<IP_ADDRESS> which I had published only minutes before opening the PR.

Thanks!


Should be limited to 14kb by default

why though

I think more details are required. Another issue or a PR is welcome. Closing due to inactivity.


Add a Run button to every example

We used to have one but it didn't work: https://github.com/brson/rust-cookbook/issues/32.
We could use an approach more like https://serde.rs where it links to a playground rather than running the code inline. See this page for example. This is nice because you get to modify the code if you want.

As discussed on Use the crates from the libz blitz? integer32llc/rust-playground#168 the integer32 rust playground team is willing to coordinate with us on the list of preloaded crates.
Cookbook would be also interested on a json  list of supported crates that we could consume in runtime to (re)enable play buttons for given examples.
As suggested by @kodraus one or both parties might expose static json lists via raw github content.
What is left is to discuss the details.
cc @shepmaster

The static lists I could go either way on. That is, if we want to say that the cookbook libs should be in the playground, I'm cool with that. We can add a whitelist easily. Then we could just accept a PR every time a library goes though the blitz. I don't know if we want to start with worrying about if this crate available or not - just assume all are. A thing that would change my mind would be if we know there are incompatibilities.

I guess that I would prefer to treat the playpen as semi volatile remote resource as we might add some non blitz crates to cookbook examples and We might want to query the playpen for supported crates prior to enabling play buttons on per example basis.
Having a whitelist would be awesome as we would be able to setup a curation process for the crate list. And we would just push a PR once crate is within the Libz Blitz. Could you specify the form (and possibly create a whitelist stub where you'd like to have it located)
Unfortunately I'll not be able to followup on this for the next two weeks due to holidays but someone from blitz might take it up in the meantime

fixed by update of mdbook


F/home page

Redesigning the existing home page to include a better UI and a "Recent Pages" section.

Also we need to gate the changes with an experiment (You can name it whatever you want but following what I had done in the past it would be called BetterHomePage)
I should write a wiki page for this, but you could look like the code in AppExperiment and core/experiments.ts to get started


[Branch-2.7] Fixed deadlock on metadata cache missing while doing checkReplication

Motivation
The origin PR #12484 is merged into branch 2.7, but reverted in #16882 because Unit test BrokerBookieIsolationTest#testBookieIsilationWithSecondaryGroup fails.
The root cause is that policies and localPolicies are not updated after they are read from async process.
Modifications

Cherry-pick PR #12484
Change optPolicies, optLocalPolicies to policies, localPolicies in
https://github.com/merlimat/pulsar/blob/f53ddc13d7fb28f4c1bd73b23e7f3d8b7fc35591/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/BrokerService.java#L1209

Verifying this change

[ ] Make sure that the change passes the CI checks.

This change is already covered by existing tests, such as BrokerBookieIsolationTest#testBookieIsilationWithSecondaryGroup
Documentation
Check the box below or label this PR directly.
Need to update docs?

[x] doc-not-needed
bug fix.

/pulsarbot run-failure-checks