Error when connecting via wss

My site uses SSL locally, and when I try to connect via wss I get the following:
WebSocket error
goog.net.WebSocket.ErrorEvent {type: "error_1", target: goog.net.WebSocket, currentTarget: goog.net.WebSocket, propagationStopped_: false, defaultPrevented: false…}
currentTarget: goog.net.WebSocket
data: undefined
defaultPrevented: false
propagationStopped_: false
returnValue_: true
target: goog.net.WebSocket
type: "error_1"
__proto__: tempCtor

Here's the command: (ws-repl/connect "wss://localhost:9001" :verbose true)

In case it's useful to anyone, here's an nginx config that fronts two Weasel brepls ("content" and "background") and a regular web app. It forwards the two WSS connections on 9003 and 9004 to my repl running on 9001 and 9002, respectively. I'm an nginx noob, so it might not be optimal, but it works.
nginx.conf:
events {
  worker_connections  4096;
}

http {
    upstream clojure_web {
        server clojure:3000;
        keepalive 32;
    }

    upstream clojure_brepl_content {
        server clojure:9001;
        keepalive 32;
    }

    upstream clojure_brepl_background {
        server clojure:9002;
        keepalive 32;
    }

    server {
        listen 443 ssl;

        include ssl.conf;

         location / {
            proxy_pass http://clojure_web;
            proxy_set_header Host $http_host;
            proxy_set_header X-Forwarded-Proto $scheme;
        }
     }

    server {
        listen 9003 ssl;
        include ssl.conf;

        location / {
          include brepl.conf;
          proxy_pass http://clojure_brepl_content;
        }
    }

    server {
        listen 9004 ssl;
        include ssl.conf;

        location / {
          include brepl.conf;
          proxy_pass http://clojure_brepl_background;
      }
  }
}

ssl.conf:
ssl on;
ssl_certificate /etc/nginx/ssl/server.crt;
ssl_certificate_key /etc/nginx/ssl/server.key.nopass;

brepl.conf
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_read_timeout 86400;


Rule 110 Celluar Automation test

A test case to ensure that Rule 110 Cellular Automation can be completed correctly in salient.
This cannot be actually implemented untill certain features have been implemented:

[ ] Linear (inline array)
[ ] Basic for loops
[ ] Variable iteration (_++, --_, etc)

#9 should really be implemented before any of the requirements for this PR


GitHub action documentation

please commit with git cz - (you need to npm i -g commitizen beforehand)


Fix the Spinner

The spinner in the application does not function correctly and needs to be fixed.

This should be good enough for now.


Feat slider added component

name: 'Pull request'
about: A new pull request
New Pull Request
Checklist

[x] I am not disclosing a vulnerability.
[x] My code is conform the code style
[x] I have made corresponding changes to the documentation
[x] I have updated Typescript definitions when needed

Issue Description

Related issue: #715
Solution Description

Adding a screenshot of final work
Another small addition was done for IPFSInput where the storybook did not have savetoIPFS boolean set

Hey @3scava1i3r
The slider component works but sorry I have added some comments to make the component code similar to rest of the components 😅
Feel free to ping me on discord or slack if you need me to explain anything again 🙌🏻
Also I have deleted the changeset file and created a new one.. since we are doing patch release instead of minor.

Closing this and creating a new PR since the git history is completely messed up now 😅


[FEATURE] Offline mode

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when trying to use it for CTFs.
Describe the solution you'd like
Use it without the internet.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Sorry, but I don't see how an offline mode makes sense for Beacon. It is specifically meant to allow less technically inclined users to open ports to the internet for the purposes of hosting game servers. Nothing more, nothing less.
It really isn't suited for any sort of pentesting or similar activities and frankly will never serve those kinds of purposes. It's simply designed for a different audience. There are more than likely already CLI tools that do a much better job at providing direct access to the protocol (and they're probably already part of the usual suites).


mimalloc does not free memory to OS

On Windows, mimalloc does not free memory to OS,  my program is multiple threads (in the memory pool) to allocate memory, then there is a dedicated thread to free memory. But I found that the memory kept increasing fast. What should I do about this situation? When I replace it by tcmalloc, the memory increase is significantly improved, slowly increasing within a certain peak range.

runtime stats
【program start】
heap stats:     peak      total      freed    current       unit      count
reserved:   312.1 mb   312.1 mb       0 b    312.1 mb       1 b              not all freed!
committed:   197.8 mb   202.8 mb     5.0 mb   197.8 mb       1 b              not all freed!
reset:       0 b        0 b        0 b        0 b        1 b              ok
touched:     1.3 mb     1.4 mb    47.1 kb     1.3 mb       1 b              not all freed!
segments:      23         23          0         23                           not all freed!
-abandoned:       0          0          0          0                           ok
-cached:       0          0          0          0                           ok
pages:     2.2 k      2.2 k        6        2.2 k                         not all freed!
-abandoned:       0          0          0          0                           ok
-extended:       0
-noretire:       0
mmaps:       0
commits:     198
threads:      16         16          0         16                           not all freed!
searches:     0.0 avg
numa nodes:       1
elapsed:      54.019 s
process: user: 0.187 s, system: 0.484 s, faults: 53836, rss: 205.0 mb, commit: 207.4 mb
【50min later】
heap stats:     peak      total      freed    current       unit      count
reserved:   384.1 mb   384.3 mb   184.7 kb   384.1 mb       1 b              not all freed!
committed:   212.6 mb   221.2 mb     8.5 mb   212.6 mb       1 b              not all freed!
reset:       0 b        0 b        0 b        0 b        1 b              ok
touched:     2.4 mb     2.5 mb     5.7 mb    -3.2 mb       1 b              ok
segments:      50         50         23         27                           not all freed!
-abandoned:       5         11         10          1                           not all freed!
-cached:       0          0          0          0                           ok
pages:     2.3 k      2.4 k      169        2.2 k                         not all freed!
-abandoned:      34         61         60          1                           not all freed!
-extended:       0
-noretire:       0
mmaps:       0
commits:     319
threads:      21         44         33         11                           not all freed!
searches:     0.0 avg
numa nodes:       1
elapsed:    3267.039 s
process: user: 0.671 s, system: 1.546 s, faults: 58922, rss: 208.2 mb, commit: 222.5 mb
【80min later】
heap stats:     peak      total      freed    current       unit      count
reserved:   416.1 mb   416.4 mb   297.1 kb   416.1 mb       1 b              not all freed!
committed:   217.0 mb   297.0 mb    80.9 mb   216.1 mb       1 b              not all freed!
reset:       0 b        0 b        0 b        0 b        1 b              ok
touched:     3.0 mb     3.1 mb    22.7 mb   -19.5 mb       1 b              ok
segments:      66         67         38         29                           not all freed!
-abandoned:       8         17         16          1                           not all freed!
-cached:       0          0          0          0                           ok
pages:     2.4 k      2.8 k      537        2.2 k                         not all freed!
-abandoned:      57         87         86          1                           not all freed!
-extended:       0
-noretire:       0
mmaps:       0
commits:     924
threads:      21         59         47         12                           not all freed!
searches:     0.0 avg
numa nodes:       1
elapsed:    5054.574 s
process: user: 0.890 s, system: 2.109 s, faults: 75092, rss: 215.6 mb, commit: 227.0 mb
Memory is growing all the time，what the faults count mean,from 53836 to 75092

heap stats:     peak      total      freed    current       unit      count
reserved:   672.1 mb   673.4 mb     1.2 mb   672.1 mb       1 b              not all freed!
committed:   275.3 mb   462.6 mb   188.7 mb   273.9 mb       1 b              not all freed!
reset:       0 b        0 b        0 b        0 b        1 b              ok
touched:     9.8 mb     9.9 mb   357.2 mb  -347.3 mb       1 b              ok
segments:     226        227        165         62                           not all freed!
-abandoned:      41         69         68          1                           not all freed!
-cached:       0          0          0          0                           ok
pages:     3.4 k     10.1 k      7.5 k      2.6 k                         not all freed!
-abandoned:     498        688        675         13                           not all freed!
-extended:       0
-noretire:       0
mmaps:       0
commits:     1.9 k
threads:      21        185        174         11                           not all freed!
searches:     0.0 avg
numa nodes:       1
elapsed:   20273.464 s
process: user: 4.359 s, system: 8.390 s, faults: 98956, rss: 239.9 mb, commit: 287.0 mb
【20273 s later 】
Is there something wrong with my program？

heap stats:     peak      total      freed    current       unit      count
reserved:   944.2 mb   946.7 mb     2.5 mb   944.1 mb       1 b              not all freed!
committed:   339.4 mb   697.2 mb   357.7 mb   339.4 mb       1 b              not all freed!
reset:       0 b        0 b        0 b        0 b        1 b              ok
touched:    15.8 mb    16.0 mb   651.0 mb  -635.0 mb       1 b              ok
segments:     420        421        326         95                           not all freed!
-abandoned:      76        168        165          3                           not all freed!
-cached:       0          0          0          0                           ok
pages:     4.6 k     17.0 k     14.0 k      2.9 k                         not all freed!
-abandoned:     995        1.8 k      1.8 k       33                           not all freed!
-extended:       0
-noretire:       0
mmaps:       0
commits:     3.3 k
threads:      21        346        335         11                           not all freed!
searches:     0.0 avg
numa nodes:       1
elapsed:   39371.755 s
process: user: 9.406 s, system: 18.890 s, faults: 134639, rss: 274.3 mb, commit: 352.0 mb


AttributeError: 'SequenceWrapperMapDataPipe' object has no attribute 'prefetch . when using MultiProcessingReadingService

🐛 Describe the bug
from torchdata.datapipes.map import SequenceWrapper
from torchdata.dataloader2 import DataLoader2
from torchdata.dataloader2 import MultiProcessingReadingService

class SimpleDataset:
    def __len__(self):
        return 1000

    def __getitem__(self, i):
        if i >= len(self): raise StopIteration()
        return i

if __name__ == '__main__':
    ds = SimpleDataset()
    warp_ds = SequenceWrapper(ds)

    rs = MultiProcessingReadingService(num_workers=2)
    # no error
    # dl = DataLoader2(warp_ds)
    # raise error
    dl = DataLoader2(warp_ds, reading_service=rs)

    for x in dl:
        print(x)

Versions
torchdata nightly

@NivekT Thank you reply. I have successfully used it.
If the error message is more easier to understand, or if it is automatically converted to IterDataPipe, it would be even better.


Amazon: Fix failing to obtain game library (#401)

Fixes failing to obtain games during library update. (#401)
While not needed, I added two missing parameters in the request body and updated the user agent for good measure.

https://github.com/JosefNemec/PlayniteExtensions/blob/d59a97d5bce1c35a55c7dc01000684169b76fd96/source/Libraries/AmazonGamesLibrary/Models/EntitlementsRequest.cs#L11
The official clients send "GetEntitlements" on "Operation" propery.

Parece un error de amazon ya que launchbox, otro lanzador de juegos, tiene el mismo problema.

It was my first time do that. Maybe my method is not the best one.
I used mitmproxy.
I installed mitmproxy to my Raspberry Pi. And started it according to this documentation: https://docs.mitmproxy.org/stable/mitmproxytutorial-interceptrequests/
Then I started a clean Windows virtual machine by Hyper-V.
On network settings set the proxy to the IP of the Raspberry Pi.
Installed certificates according to this document:
https://docs.mitmproxy.org/stable/concepts-certificates/
Now all network request send from the Windows virtual machine will appear on the console of the Raspberry Pi.
The reason why I used Windows virtual machine is, installing third party root certificates are dangerous. It gives too much power to the issuer of the certificate.


Use Custom HTML Templates

Right now, the user gets a generic html file output, with their custom projects specification.
It would be neat to be able to provide a custom template through the command line, by specifying the location of the the HTML file to use as a template. The file would require a predefined portfolioBuilder class tag and a projects id tag so that the program would know where to place the portfolio items. If those don't exist, it should throw.

Feature added as of this commit:
https://github.com/ajshiff/portfolio-builder/commit/a57bb9041540d5503db2f412f9993d15868d2cb7
Issue closed.


Sign assemblies

The goal is to create signed assemblies.
Original conversation : https://github.com/mathieumack/HockeySDK-Windows/commit/8d72d2b62c95d302c36c0567e9b232296bbee039#commitcomment-22579134

Closed as HockeyApp is replaced by AppCenter.


Fixed the broken link to the examples directory

The pull request covers issue #170

@nlchar/z this pull request is too small, just 2 lines changed (less than 10), there will be no formal code review, see §53 and §28; in the future, try to make sure your pull requests are not too small; @yegor256/z please review this and merge or reject

@nlchar/z this pull request is too small, just 2 lines changed (less than 10), there will be no formal code review, see §53 and §28; in the future, try to make sure your pull requests are not too small; @yegor256/z please review this and merge or reject

@nlchar thanks!

@nlchar thanks!

Job gh:yegor256/eo#172 is not assigned, can't get performer

Job gh:yegor256/eo#172 is not assigned, can't get performer


Security fix for Cross-Site Scripting Vulnerability in frappe-charts

:bar_chart: Metadata *
frappe-charts is vulnerable to Cross-Site Scripting (XSS).
Bounty URL: https://www.huntr.dev/bounties/1-npm-frappe-charts
:gear: Description *
Cross-Site Scripting (XSS) attacks are a type of injection, in which malicious scripts are injected into otherwise benign and trusted websites. XSS attacks occur when an attacker uses a web application to send malicious code, generally in the form of a browser side script, to a different end user.
:computer: Technical Description *
While rendering charts, the package is validating all object fields except name in datasets array, this allows malicious code execution. The fix is implemented by properly validating name field to escape malicious characters.
:bug: Proof of Concept (PoC) *
Steps To Reproduce

Open NPM repo https://www.npmjs.com/package/frappe-charts
Open the Explore demos https://frappe.io/charts
At the bottom find the sandbox Ref: https://codesandbox.io/s/frappe-charts-demo-viqud?from-embed=&file=/src/index.js
Use the payload ><img/
 src=~ onerror=alert('XSS')> and place it in name.
XSS payload will get executed.

References

:fire: Proof of Fix (PoF) *

Before fix

After fix, Cross-Site Scripting is prevented.

+1 User Acceptance Testing (UAT)

I've executed unit tests.
After fix the functionality is unaffected.

Congratulations arjunshibu - your fix has been selected! 🎉
Thanks for being part of the community & helping secure the world's open source code.
If you have any questions, please respond in the comments section, or hit us up on Discord. Your bounty is on its way - keep hunting!
Come join us on Discord


Support publish of content and contentFiles with NuGet PackageReference format

For Sitecore 9.1 and beyond, it's recommended to convert the ASP.NET Web Application projects in your solution to use the NuGet PackageReference format for reasons I won't expound here. After you convert an ASP.NET Web Application project to use the PackageReference format, config files in NuGet packages (e.g., Unicorn, Synthesis, Glass Mapper) will no longer be automatically added in to your project when those NuGet packages are installed or updated. Instead, you have to track down the configs in the %USERPROFILE%\.nuget\packages folder and manually copy them in to your project. This makes it easy to miss critical config changes when upgrading NuGet packages.
The ASP.NET Core Web Application project type does not suffer from this problem. When an ASP.NET Core Web Application project is published, all assets in the contentFiles directory of the NuGet packages that the project references are automatically published to the publish target. Due to this mechanism, it is not necessary for assets in contentFiles to be added to ASP.NET Core Web Application project types.
It would be awesome if HPP handled publishing of assets in the content and contentFiles folders of referenced NuGet packages when using the PackageReference format with the ASP.NET Web Application similar to the way they are handled for ASP.NET Core Web Application projects. This feature should not be enabled for ASP.NET Web Application projects still using the packages.config format. I think there should be some intelligence for packages with configs/assets duplicated in both the content and contentFiles folders for backwards compatibility (e.g., Synthesis) so that a double publish doesn't occur, if possible.

Great idea. I propose the following rules:

Only run when the website project contains PackageReferences
Prefer contentFiles/ over content/
Prefer a project file to a package file (to allow overrides)
Allow .Helix transform files to transform package config files

Sound good?

Sounds great.

hey guys, the solution I'm working with right now is configured with PackageReferences and I've hit the same problem @coreyasmith described above. I'm wondering if this feature request is already being worked on as it sounds so much better than building my own custom build steps. If not, I'd be happy to take a stab at it

@ezlateva just to clarify, if the PackageReference with the content a reference of Website or one of the modules?

in my case, both actually

Interesting. Looking the NuGet.targets, the content files should get published. I wonder if it doesn't follow that path when running via a legacy (non-SDK) csproj

Yes I think that's the case @richardszalay.

Which which case, solving it for Website should be simple enough as we can trigger the same target and/or Task that gets used by sdk projects.
Modules will be more difficult. Need to think it through a little more.

I'll look into it again as soon as I can. If either of you want to do the same, to figure it what's executing I recommend the MSBuild binary log viewer.

I've had a little time to investigate this further:
Files in content/ are not supported at all in the PackageReference model. Since the're used by Unicorn and pretty much every other legacy-supporting package, we should definitely support this.
Files in contentFiles/ are explicitly skipped by both Visual Studio and NuGet CLI restores when a legacy project is using PackageReference`. I propose we do not support contentFiles due to:

It's clearly intended only for .NET Core projects
It supports additional complexities like language specific transforms

If/when Sitecore supports .NET Core, we can review the above.
Thoughts?
In both cases, adding support for content/ in PackageReferences on the Website project is on the lower end of effort but supporting PackageReferences of referenced modules is a bit more complex.
NB. We should definitely use the project lock file rather than the PackageReference items, since the former includes downstream references and the latter does not.

I think that by the time all of Sitecore is running on .NET Core, we'll be using project formats that support all of the Package Reference features natively and HPP won't need to support contentFiles.
Focusing on publishing only files in the content folder will definitely be a big win. However, it'd still be nice to support publishing from the contentFiles folder just because I think it promotes better development habits.

My only issue is that supporting it properly (ie. without breaking a bunch of packages), we'd have to reimplement all of the tokenisation transform support. content/ is much easier to support since it only supports a bunch of files. It does support config transforms, but we can leave for a future release.

Here's my plan for the implementation:

Create a custom task that:
Parses the lock file (from $(ProjectLockFile))
Finds packages that haven't been excluded (possibly via a custom ExcludeAssets metadata value?)
Outputs a list of items as long as they don't exist in the current project
Create a target that uses the new task to add the located content files into FilesForPackagingFromProject
Create another target (in it's own file) that runs the task and adds the content files to Content, and configure this target with BeforeTargets="ContentFilesProjectOutputGroup"
Update CollectFilesFromHelixModulesContent to inject the new targets file into the ContentFilesProjectOutputGroup invocation by using CustomBeforeMicrosoftCommonTargets

There will be no support for prioritising content from multiple projects that both include the same package. As with regular content files, this will generate a publish-time warning via WPP.


fix: Fixed IllegalStateException: Already resumed on cancelConnection

Check if coroutine has been not be resumed before resume it
Fix: #21

Thank you for the PR. However, it seems this is a fix for the 'symptom', rather than the root cause. I still don't get why this is happening in the first place....it seems like onDisconnected is called more than once which I don't understand


problem while running compiled app

$ cargo run
    Finished dev [unoptimized + debuginfo] target(s) in 0.15s
     Running `target/debug/counter`
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', ~/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-native-0.4.3/src/instance.rs:474:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

This issue is caused by wgpu not being able to find a suitable graphics adapter. Similar issues have been reported in #182, #72 and/or https://github.com/hecrj/iced/issues/69#issuecomment-559673451.
wgpu has some issues running on old hardware. We will eventually implement an OpenGL/software renderer as a fallback. In the meantime, some users have been able to fix the issue by updating graphics drivers.

See also https://github.com/gfx-rs/wgpu-rs/issues/226 - in my case it was a graphics driver upgrade that apparently broke vulkan. vkcube reveled the culprit, and a reboot fixed it.

D:


Fix issue #4809: [Bug]: Model does not support image upload when usin…

…g litellm_proxy/
End-user friendly description of the problem this fixes or functionality that this introduces

[ ] Include this change in the Release Notes. If checked, you must provide an end-user friendly description for your change below

Give a summary of what the PR does, explaining any non-trivial design decisions
Fix issue https://github.com/All-Hands-AI/OpenHands/issues/4809.

Link of any specific issues this addresses

To run this PR locally, use the following command:
docker run -it --rm   -p 3000:3000   -v /var/run/docker.sock:/var/run/docker.sock   --add-host host.docker.internal:host-gateway   -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:de7977a-nikolaik   --name openhands-app-de7977a   docker.all-hands.dev/all-hands-ai/openhands:de7977a

@enyst I'll dig more into the model_info passing back by the litellm (this was supposed to fix issue like this :(


Update README.md to remove theupdateframework from URLs

Updates URLs, where possible, to use new GitHub project (notaryproject) instead of theupdateframework .
FOSSA project hasn't been created for the new GitHub project namespace yet, so those remain pointing at the older URL.
This fixes CircleCI badge display

@justincormack did the signoff for DCO


Symbols view doesn't update when renaming a function with an existing symbol.

Rename a function with the name of an existing symbol.
Select "Yes" when asked if you want to override the existing symbol.
The function is renamed, but the function whose symbol was taken is not updated in the symbols view.  Whereas, the linear view correctly reverts to "sub_HEXADDR".

I think this was fixed with the recent support for duplicate symbols


Suggestion for adding an autocomplete text field

WHY
BEFORE - What was wrong? What was happening before this PR?
There were no text type fields with autocomplete.

AFTER - What is happening after this PR?
Added an autocomplete-text field which allows you to enter text and have autocompletion suggested.
HOW
How did you achieve that, in technical terms?
I took the text field and added the jquery ui load already present in the project to allow autocomplete.
I did not modify the text field because I do not think that this is a behavior that should be able to be activated on a text field. This is a very specific use in my opinion which is only used when needed.
Is it a breaking change?
No, just a suggestion for an addition.
CRUD::field('sound')
             ->type('autocomplete-text')
             ->options(["pushover", "bike", "bugle", "cashregister", "classical", "cosmic", "falling", "gamelan", "incoming", "intermission", "magic", " mechanical", "pianobar", "siren", "spacealarm", "tugboat", "alien", "climb", "persistent", "echo", "updown", "vibrate", "none"]);

How can we test the before & after?
Get the field code and use the autocomplete-text type in its crud, remembering to add a table in the options option.

Hello @dimer47 , thank you very much for this contribution, one of our members will review this suggestion to evaluate if it meets standards to add it to our main.
Thanks again.

I like this idea and the concept of a searchable text field thanks @dimer47 🙏
The code is very clean and it seems to work properly on simpler use cases.
I think this may need a little bit more work to fix edge cases like repeatable such so I don't think we can merge it as is.
I don't want to ask you to work more on this without being 100% sure we are going to do something with it in future. So allow me a few more time when we pick feature to build, to bring this to the team and decide on how to go about this.
For now it's just a file you can place in your /resources/vendor/backpack/crud/fields and use in your projects when you need it.
Will keep this open and re-evaluate in future if we want to spend time doing this as proposed, or we incorporate it as a component later.
Thanks again for the contribution @dimer47 🙏
If anyone feels this is a wanted feature please leave a comment or a thumbs up so that we can prioritize it if more people want it 🙏
Cheers

Hey @dimer47, @pxpm!
Thank you for the PR, I took a quick check on your code and it looks nice, but it uses jQuery 😅
We're trying to avoid using libraries when they're not needed, and this is a good example.
For this purpose we can use <datalist>, it's vanilla HTML, no javascript needed, and it works just as good, and it's fully supported (https://caniuse.com/?search=datalist).


eo-maven-plugin:print fails with java.lang.NoSuchMethodError: java.nio.ByteBuffer.position(I)Ljava/nio/ByteBuffer;

One of the recent builds failed with the following exception:
[ERROR] Failed to execute goal org.eolang:eo-maven-plugin:0.44.0:print (convert-xmir-to-eo) on project jeo-it: 'PrintMojo' execution failed: java.io.UncheckedIOException: java.io.IOException: java.util.concurrent.ExecutionException: java.lang.NoSuchMethodError: java.nio.ByteBuffer.position(I)Ljava/nio/ByteBuffer; -> [Help 1]

You can find full logs here:
build.log.txt
It's not a bug in jeo-maven-plugin, but influence it significantly.

eo-maven-plugin states that I need Java 8 installed:
You will need [Maven 3.3+](https://maven.apache.org/) and Java 8+ installed.

But the goal fails exactly on Java 8. Maybe there are some inconsistencies between real code and the documentation.

@yegor256 Could you take a look, please? It blocks entire development process in the jeo-maven-plugin.

@volodya-lombrozo we support Java 11, I made the changes to the doc and our pom: https://github.com/objectionary/eo/issues/3589

@yegor256 Thank you for the clarification and the fix


ghcr.io image tag for v7.1.7 missing

Can you please add a tag to the v7.1.7 release? It's currently not possible to pull by tag (only via :latest):
LAST SEEN   TYPE      REASON     OBJECT                           MESSAGE
59s         Warning   Failed     pod/fedifetcher-28755945-d6ptd   Failed to pull image "ghcr.io/nanos/fedifetcher:v7.1.7": reading manifest v7.1.7 in ghcr.io/nanos/fedifetcher: manifest unknown

Thanks!

ok, this was annoying. Think it's fixed now, and hopefully it will survive the next releases.
You can get v7.1.12 (which is identical to 7.1.7 except for a bit of tidy up and removing unnecessary files)

Thanks for the quick fix!

Thanks for the quick fix!


ring_size listed as input to wallet RPC transfer method

I thought the ring_size in Monero can no longer be changed.  Does it still belong as an input to transfer in the RPC documentation?
https://github.com/monero-project/monero-site/blame/28cfcdb38e735f5c35b83c067d8410ff4dc81ad4/resources/developer-guides/wallet-rpc.md#L659

On mainnet yes, but devs are still able to perform tests on older versions of the blockchain. so perhaps just a few words to clarify this e.g. "Not adjustable on mainnet" or something to that effect

Instead of "not adjustable on mainnet", I think the phrase "the field is completely ignored on mainnet" would be more helpful. Seeing that description, client developers of libraries not intended for testing older versions will just omit the field entirely. Developers won't waste time trying to figure out if they need to set it to exactly 16 or if setting it to an arbitrary number like 13 will generate an error.

moneromoo - "It is not ignored if sending pre rct outputs."

@plowsof Did moneromoo give any advice on how the ring_size field should set for the standard use case of transferring Monero on the current mainnet? The transfer method only takes an amount.  You don't specify or easily know which outputs get used and if they are pre rct or not. I've just been leaving it unset or with a value of zero and it seems to be working.

I will ask, i share the same feelings, for now i'm using "(Unless dealing with pre rct outputs, this field is ignored on mainnet)."


Create a website

There should be a website and documentation.
This is time-consuming, but I think it will be a good first issue.

Hi! I'd like to work on this issue. Could you provide more details on what content you would like for the website and documentation? Thanks!

You can propose something. I would like to have:

Welcome page with explanation of what Wayne is with a logo and maybe a genesis of the name (you can find it in README).
Documentation also from README, each section can be a different page.
Links to demos, the links can be inside documentation, or it can be a different page.

Right now, I'm thinking maybe using Docusaurus is a good idea. I use it in one project, and it's a fast way to create documentation written in Markdown file. The tool use React to build a website.


Rustup

@bors r+

:pushpin: Commit d248397e3c06a2ed26318e29e019f082b3f1bb29 has been approved by RalfJung
It is now in the queue for this repository.

:hourglass: Testing commit d248397e3c06a2ed26318e29e019f082b3f1bb29 with merge a38997cdd63223580e95d5f3b403622e7d0cba7b...

:broken_heart: Test failed - checks-actions

@bors r+

:pushpin: Commit e47904fc5da3f274f4fec3c6b91354edac3ebf78 has been approved by RalfJung
It is now in the queue for this repository.

:hourglass: Testing commit e47904fc5da3f274f4fec3c6b91354edac3ebf78 with merge d06a41b778005eac2ac0047f5d11975874046fcd...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing d06a41b778005eac2ac0047f5d11975874046fcd to master...


WIP: Add Path alias to -FilePath parameters and others for several commands

PR Summary

Add alias Path to the -FilePath parameter of Start-Process, Set-TraceSource, Tee-Object, Trace-Command,Register-ScheduledJob, Set-ScheduledJob,Invoke-WSManAction, Set-WSManInstance,New-WSManInstance
Add alias Path to the -BinaryPathName parameter of New-Service
Add alias Path to the -DestinationPath parameter of Save-Help
Add alias Path to the -SourcePath parameter of Update-Help

PR Checklist
Note: Please mark anything not applicable to this PR NA.

[x] PR has a meaningful title

[x] Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[X] User facing Documentation needed: https://github.com/PowerShell/PowerShell-Docs/pull/2148

[X] Issue filed - Issue link: https://github.com/PowerShell/PowerShell-Docs/issues/2147

[X] Change is not breaking
[NA] Make sure you've added a new test if existing tests do not effectively test the code changed

[NA] Add [feature] if the change is significant or affects feature tests

[X] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

@PowerShell/powershell-committee reviewed this.  We would be concerned about making any general rules here, but reviewing the specific cmdlets listed we are ok with the proposed change.

I added tests where the cmdlets already had some tests. Several of those cmdlets have no tests at all. I would like to work on some of those as a separate work effort.
I have a pull request out for the documentation of these changes.


Dockerize app

This PR covers:

refactor the Dockerfile to actually do something
add needed requirements
change how the app is initally run (migrate instead of syncdb)
add all configurable ENV variables to the dockerfile so a user knows what he can tune

:+1:


Creation of additional file types

Description of the new feature / enhancement
Allow creation of files of type
text (.txt)
generic (.)
PowerShell (.ps1)
batch commands (.cmd) <= perhaps not anymore
or customizing this be bespoke types and content
Additional creation of symlinks (for folders or files) would be neat. After adding the user group to the proper list.
Scenario when this would be used?
From the file explorer new files are restricted to folders, shortcuts and office documents. Adding new file types is not possible.
Supporting information
I believe this used to be possible in windows 7

In fact this was still possible in Windows 10

Just to be sure you're talking about this menu, right? :

Yeah! but I only see:


Fixing flaky tests in DateTest4_indian and DateTest5_iso8601

test_date in DateTest4_indian and DateTest5_iso8601 has a test-order dependency and it fails when they are run by themselves.
test_date can be fixed by running a setup to change the time and locale to "Asia/Shanghai" and "China" (respectively). This setup is the same as the one in the DateTest class that these tests were depending on. The fix will enable test_date in the two classes to now pass in any test run order and by itself. Without the fix, the tests will get the following error. Let me know if you want to discuss more.
junit.framework.AssertionFailedError:
Expected :83419000
Actual   :29419000
	at junit.framework.Assert.fail(Assert.java:57)
	at junit.framework.Assert.failNotEquals(Assert.java:329)
	at junit.framework.Assert.assertEquals(Assert.java:78)
	at junit.framework.Assert.assertEquals(Assert.java:159)
	at junit.framework.Assert.assertEquals(Assert.java:166)
	at junit.framework.TestCase.assertEquals(TestCase.java:324)
	at com.alibaba.json.bvt.serializer.date.DateTest5_iso8601.test_date(DateTest5_iso8601.java:27)

Codecov Report

Merging #2148 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #2148      +/-   ##
============================================
- Coverage     81.67%   81.66%   -0.02%
+ Complexity     6784     6780       -4
============================================
  Files           140      140
  Lines         25360    25360
  Branches       6055     6055
============================================
- Hits          20713    20709       -4
- Misses         2930     2931       +1
- Partials       1717     1720       +3

Impacted Files
Coverage Δ
Complexity Δ

...com/alibaba/fastjson/parser/JSONReaderScanner.java
72.61% <0%> (-1.28%)
44% <0%> (-1%)

...n/java/com/alibaba/fastjson/util/JavaBeanInfo.java
87.5% <0%> (-0.19%)
191% <0%> (-1%)

...java/com/alibaba/fastjson/parser/ParserConfig.java
82.38% <0%> (-0.19%)
185% <0%> (-1%)

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 6a5adc9...1fb1f23. Read the comment docs.


Quote every String variable

To prevent unwanted shell word splitting, it is a best practice to literally quote every String variable.
Source: http://wiki.bash-hackers.org/scripting/style#parameter_expansion

I just read through install-template.sh and couldn't find any instances of this problem. If you see instances of this in the code let me know.

Oh, on second review I did find that PATH, LD_LIBRARY_PATH and DYLD_LIBRARY_PATH were unquoted.

every variable and assignment should be quoted, except for maybe internal bash variables such as $? which are always integers. Example: https://github.com/brson/rust-installer/blob/296f7adc495baf6c45dadcddb84f2c76f4799feb/install-template.sh#L49

What about a case like
for available_component in $COMPONENTS; do
    ...
done

If I quote $COMPONENTS won't for then only iterate over one thing?

Depends whether $COMPONENTS is a String or an Array. If it's a String, then you probably want implicit shell word splitting. If it's an Array, use "${COMPONENTS[@]}". Quoting Array expansions prevents the shell from implicitly shellword splitting each element.


BUG: Potential Hang Issue When Importing scipy.spatial.distance

Describe your issue.
I've encountered a peculiar issue with scipy.spatial.distance where it seems to freeze under specific circumstances. The problem arises when I use import scipy.spatial.distance. Here's the traceback I received:
python
Copy code
Traceback (most recent call last):
File "E:\buyi_work\MMC5\Login_test.py", line 147, in
import scipy.spatial.distance
File "E:\buyi_work\MMC5\venv\lib\site-packages\scipy_init_.py", line 136, in
from . import distributor_init
File "E:\buyi_work\MMC5\venv\lib\site-packages\scipy_distributor_init.py", line 61, in
WinDLL(os.path.abspath(filename))
File "D:\Python3.6.6\lib\ctypes_init.py", line 348, in init
self._handle = _dlopen(self._name, mode)
After this point, the program stops executing further. Upon initial investigation, this freeze seems to occur when I have already imported the pyminitouch library and scipy.spatial.distance is being imported in a script (for instance, in script b.py with import scipy.spatial.distance, and a importing b). However, if I import scipy.spatial.distance directly in script a, the issue does not arise. This bug is quite intriguing and seems to be dependent on the order and context of imports.
Reproducing Code Example
will jam
a.py
from pyminitouch import MNTDevice
device = MNTDevice("<IP_ADDRESS>:5555")
import b

b.py
import scipy.spatial.distance

no jam
a.py
from pyminitouch import MNTDevice
device = MNTDevice("<IP_ADDRESS>:5555")
import scipy.spatial.distance
import b

b.py
import scipy.spatial.distance

Error message
Traceback (most recent call last):
  File "E:\buyi_work\MMC5\Login_test.py", line 147, in <module>
    import scipy.spatial.distance
  File "E:\buyi_work\MMC5\venv\lib\site-packages\scipy\__init__.py", line 136, in <module>
    from . import _distributor_init
  File "E:\buyi_work\MMC5\venv\lib\site-packages\scipy\_distributor_init.py", line 61, in <module>
    WinDLL(os.path.abspath(filename))
  File "D:\Python3.6.6\lib\ctypes\__init__.py", line 348, in __init__
    self._handle = _dlopen(self._name, mode)
KeyboardInterrupt

SciPy/NumPy/Python version and system information
scipy 1.5.4
numpy 1.19.5
python 3.6

Hi @134820134820 , your SciPy version (1.5.4) is very old (NumPy and Python too) - would it be possible for you to try with a more recent version?


A11y_AzureToolsStorageExplorer_BlobContainer_BlobContainerAcquireLease_ScreenReader: Title is not provided to the Acquire Lease dialog.

“Check out Accessibility Insights! Identify accessibility bugs before check-in and make bug fixing faster and easier.”
GitHubTags: #A11y_AzureToolsStorageExplorer; #A11yMAS; #A11YTCS; #DesktopApp; #WCAG1.3.1;#WCAG2.4.2 #VoiceOver; #Mac;
Environment Details:
Application Name: Azure Tools Storage Explorer
Application Version: 1.10.0
MAC Version 10.14.6 Beta(18G29g)
Repro Steps:

Launch Storage Explorer
Navigate to "Open Connect dialog" pane and Sign in to Azure.
Go to "Manage Accounts" pane and Select the subscriptions you will use. Once selected, click on "Apply" button.
Navigate to "Blob Containers" of the selected subscription, right click and hit enter on "Create Blob container" to Create a new Blob container.
Right click on created blob container and select "Acquire Lease" control and hit enter.
Start VoiceOver and check whether the Voiceover reads the title of the dialog as Acquire Lease when opened.
Actual:
Voiceover does not read the title of the dialog as Acquire Lease dialog is opened after click on Acquire lease menu.
Expected:
VoiceOver should read the title as Acquire Lease dialog opened.
UserImpact:
Screen reader users unable to know the which dialog opened if it will not read the title.

Attachment for Reference:
1976_A11y_AzureToolsStorageExplorer_BlobContainer_BlobContainerAcquireLease_ScreenReader.pptx

Fix checking into master.

@MRayermannMSFT Verified on version 1.12.0 and MAC 10.15.3.The issue is no longer reproduced.Hence close this bug.

GithubTags:#Closed;

GitHubTags:#BM-TCS-StorageExplorer-Mac-Sep2019;


Add GlitchTip to list

Hello. I was hoping to add the open-source project I work on to this list. Normally we mention Sentry as our primary competitor, but I wanted to ask if this is alright since they also seem to be on this list. Thanks for your time.

Hey, thanks for your PR!
We are open for all projects, but we decided to put a lower bound on number of stars (100 GitHub / GitLab stars).
I will make a note and add your repo as soon as you reach 100 stars. Hope it makes sense :)


Freeze after starting

Hello, I have problem with goad application. I have created new amazon account, setuped IAM user and builded last version of goad.  I am trying to run goad and it's freeze.
goad -u http://srelease.hgstudio.ru
http://take.ms/XhgOK - here what I see
Environment data:
goad version 1.2.0
go version 1.7.3 darwin/amd64
macos 10.12.2 (16C67)
Can anybody help? I wanna debug goad application, but doesn't know where is start. Thanks for help and sorry for stupid question.

Same problem happens my environment and resolve with https://github.com/goadapp/goad/pull/95 .

Thanks that really help. I think that core team should approve Guido PR

So, 95 issue merged I close this issue


Error at startup on a local build

I just tried compiling fstar from source this morning, and here's what I'm getting.
protz@Joprotze-Z420:~/Code/FStar (master) $ fstar

Unexpected error; please file a bug report, ideally with a minimized version of the source program that triggered the error.
The type initializer for '<StartupCode$FSharp-PowerPack-Compatibility>.$Microsoft.FSharp.Compatibility.OCaml.Sys' threw an exception.

Would be happy to help debugging if there's anything I can do.

Salut Jonathan,
Can you give us some platform details?

Right, that would be Windows 8. Here's a more meaningful stack trace and some version numbers.
D:\cygwin\home\protz\Code\FStar\bin>fstar

Unexpected error; please file a bug report, ideally with a minimized version of
the source program that triggered the error.
The type initializer for '<StartupCode$FSharp-PowerPack-Compatibility>.$Microsof
t.FSharp.Compatibility.OCaml.Sys' threw an exception.

Unhandled Exception: System.TypeInitializationException: The type initializer fo
r '<StartupCode$tosmt>.$Microsoft.FStar.ToSMT.Z3' threw an exception. ---> Syste
m.ComponentModel.Win32Exception: The system cannot find the file specified
   at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startIn
fo)
   at Microsoft.FStar.Util.run_proc(String name, String args, String stdin) in D
:\cygwin\home\protz\Code\FStar\src\basic\util.fs:line 141
   at Microsoft.FStar.ToSMT.Z3.get_z3version$cont@52(Unit unitVar) in D:\cygwin\
home\protz\Code\FStar\src\tosmt\z3.fs:line 52
   at <StartupCode$tosmt>.$Microsoft.FStar.ToSMT.Z3..cctor() in D:\cygwin\home\p
rotz\Code\FStar\src\tosmt\z3.fs:line 68
   --- End of inner exception stack trace ---
   at Microsoft.FStar.ToSMT.Z3.get_z3proc()
   at Microsoft.FStar.ToSMT.Z3.cleanup() in D:\cygwin\home\protz\Code\FStar\src\
tosmt\z3.fs:line 131
   at <StartupCode$fstar>.$Microsoft.FStar.FStar.main@() in D:\cygwin\home\protz
\Code\FStar\src\fstar.fs:line 107

Also:
protz@Joprotze-Z420:~/Code/FStar (master) $ fsc --help | head -n 2
Microsoft (R) F# Compiler version 12.0.21005.1
Copyright (c) Microsoft Corporation. All Rights Reserved.

protz@Joprotze-Z420:~ $ z3 --version
Z3 version 4.3.2

Obviously looks like a Z3 issue. Try with the --smt /path/to/z3 option and with the z3 binaries copied to FStar/bin (also make sure your FSTAR_HOME variable is set (e.g. with source setenv.sh), or set the --fstar_home option

Sorry about the terrible delay.
Here's more attempts at getting fstar to work.
protz@Joprotze-Z420:~/Code/FStar (master) $ echo $FSTAR_HOME
/home/protz/Code/FStar
protz@Joprotze-Z420:~/Code/FStar (master) $ echo $PATH
/home/protz/Code/FStar/bin:(more stuff)
protz@Joprotze-Z420:~/Code/FStar (master) $ ls bin/z3.exe
bin/z3.exe
protz@Joprotze-Z420:~/Code/FStar (master) $ bin/z3.exe
Error: input file was not specified.
For usage information: z3 -h
protz@Joprotze-Z420:~/Code/FStar (master) $ bin/fstar.exe

Unexpected error; please file a bug report, ideally with a minimized version of the source program that triggered the error.
The type initializer for '<StartupCode$FSharp-PowerPack-Compatibility>.$Microsoft.FSharp.Compatibility.OCaml.Sys' threw an exception.
protz@Joprotze-Z420:~/Code/FStar (master) $ bin/fstar.exe --smt bin/z3.exe

Unexpected error; please file a bug report, ideally with a minimized version of the source program that triggered the error.
The type initializer for '<StartupCode$FSharp-PowerPack-Compatibility>.$Microsoft.FSharp.Compatibility.OCaml.Sys' threw an exception.

I'm using cygwin, if that matters.

(I should also mention that this attempt to compile from source was just out of curiosity, and that the binary build works fine on my machine.)

Unfortunately I can now reproduce this ... when trying to get an F* release out. Painful, I'll let you know if I discover anything.

FWIW, I'm unable to reproduce this on my machine. Although I have Z3 4.3.0 ...

I think it's more of an F# thing than a Z3 thing.


Feature Request: Check URLs against Content-Security-Policy header

The Content-Security-Policy header controls which domains the browser is allowed to access in various contexts. For example, if a website contains an image that is hosted at a domain that the Content-Security-Policy header doesn't allow images to be loaded from, then this image won't be loaded by a complying browser.
This can be quite painful. I've noticed today that the newsletter signup form on my website had been broken in Chrome for months, because Chrome and Firefox seem to interpret the Content-Security-Policy slightly differently (Chrome didn't pick up a wildcard in a URL). It would be great to have a tool that can check all images, form actions, etc. against Content-Security-Policy, to make sure nothing on the site is broken.
Note: I'm not a user of Lychee (although I might become one, after this experience :smile:), but @mre requested that I submit this issue.

There is https://github.com/rust-ammonia/rust-content-security-policy, which we might use for that.
So the idea would be:

Parse the header from the page with the crate above
Test sub-requests that should get restricted by the CSP and report them as unreachable by a compliant browser.


Does it support subquery and table alias?

Does it support sub query and table alias?
select f.col1 A, f.col2 B, s.colx C
from foo f, ( select colx from bar where colx=123) s
where f.colx=s.colx

Alias should not be a problem, since the from method only stores a string,
I imagine this should work:
...
  .from("foo f")
...

About sub queries, this is one of the reasons I'm still thinking about using this lib.

If aliases work because the from is stored as a string, then I feel like subqueries should work too.
.from("("+subquery.str()+") sub")


Fix Google lighthouse score

https://pagespeed.web.dev/analysis/https-jackbailey-dev/ytsy2auf54?form_factor=mobile
Seems to no longer be perfect on mobile

Works fine on homepage, but fix the score for blog pages too (if possible)


Fan Oscillation Doesn't Work

Pushing in the stick thingy at the back of the fan case doesn't make the fan oscillate. It's not clear why.

[x] Figure out how to open fan casing.
[x] Figure out what's wrong.
[x] Fix it.

Arm connecting the oscillation gears to the frame of the fan had become detached from the gear for unclear reasons.
There's a small crack on its far side, but at no point in the oscillation cycle does this appear to be stressed enough to open far enough for the arm to slip off.
In any case, I reattached the arm and everything works fine now.


prodlem has raise

Shell showoff? Mine is prettier.

(by the way, I don't know how to debug your issue)


Add progressDeadlineSeconds

To make sure the operator doesn't get stuck in an infinite loop, we need a safeguard mechanism. We want this to be eventual consistent, because there might be a delay in ArgoCD (it might be down, or unable to sync for a time window).
We can use the progressDeadlineSeconds concept as seen in https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.19/#deploymentspec-v1-apps and https://docs.flagger.app/usage/how-it-works

Considering how ArgoCD support retries with backoff, as per https://argo-cd.readthedocs.io/en/stable/operator-manual/application.yaml
    # The retry feature is available since v1.7
    retry:
      limit: 5 # number of failed sync attempt retries; unlimited number of attempts if less than 0
      backoff:
        duration: 5s # the amount to back off. Default unit is seconds, but could also be a duration (e.g. "2m", "1h")
        factor: 2 # a factor to multiply the base duration after each failed retry
        maxDuration: 3m # the maximum amount of time allowed for the backoff strategy

we can tune ArgoCD to retry how many times we need with the appropriate backoff.
This behavior makes the ProgressDeadline feature less urgent.


rpi-imager: 1.7.2 -> 1.7.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/raspberrypi/rpi-imager/releases.
meta.description for rpi-imager is: "Raspberry Pi Imaging Utility"
meta.homepage for rpi-imager is: "https://www.raspberrypi.org/software/"
meta.changelog for rpi-imager is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.7.3 with grep in /nix/store/kgnc2sb4yi6986lsf1bkb0z086r4yq0i-rpi-imager-1.7.3
found 1.7.3 in filename of file in /nix/store/kgnc2sb4yi6986lsf1bkb0z086r4yq0i-rpi-imager-1.7.3

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
rpi-imager

Instructions to test this update (click to expand)

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

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

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

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

1 package built:

rpi-imager

Maintainer pings
cc @ymarkus for testing.

Result of nixpkgs-review pr 190636 run on x86_64-linux 1

1 package built:

rpi-imager


[Feature]: JUnit:  Allow the user to control the Browser object's lifecycle

🚀 Feature Request
Add an option that will reset the Browser object after each test so cloud services that use BrowserType.connect can work properly. Example: https://www.browserstack.com/docs/automate/playwright/playwright-capabilities#Java
Example
public class Options {
  // existing options

  public Boolean closeBrowserAfterEachTest;

  public Options setCloseBrowserAfterEachTest(Boolean closeBrowser) {
    this.closeBrowserAfterEachTest = closeBrowser;
    return this;
  }

}

Inside of the existing TestWatcher methods, we can check if the user wants to close the browser after each test and do so.  Once the next test starts, the Browser will be re-created by the fixture using the existing options.  This will allow a new test session to start in BrowserStack.
  @Override
  public void testSuccessful(ExtensionContext extensionContext) {
    saveTraceWhenOn(extensionContext);
    closeBrowserContext();
    Options options = OptionsExtension.getOptions(extensionContext);
    if(options.closeBrowserAfterEachTest) {
      BrowserExtension.closeBrowser();
    }
  }

Motivation
Cloud testing services like BrowserStack launch new sessions using BrowserType.connect.  Each call to connect starts a new test session.
This doesn't work properly with current JUnit fixtures because the Browser object is re-used per thread and so all tests that run on the same thread use the same test session in BrowserStack.  This becomes one giant test according to BrowserStack.
My suggestion would allow the user to decide when to re-use the browser, which works great locally, but not so well when using cloud testing services.

Not to say that I'm completely against the idea, but it sounds like a workaround for a limitation of a particular cloud service. Do you know why they require resetting the connection for each test rather than reusing the connection and creating BrowserContext per test as we do? Is it because there is no separate API to mark test begin/end?

I'm not sure what their reasoning is.  My guess is that it's a carry-over from how they implemented their selenium tests.

I see, thanks for providing more context. I commented on the PR. My preference would be to allow calling browser.close() on the browsers provided by @Playwright fixture and let the clients call that method from their own fixtures if needed. But I'm not strongly opposed to having the option either if there is a good rationale for that.

@yury-s I'll test out your proposed solution tomorrow and see how it works out.

@yury-s using onDisconnected works but there are a couple drawbacks:

The user cannot call browser.close() from within a normal JUnit AfterEach hook.  If they do, all of the trace recording that happens in the test watcher methods will not work because the BrowserContext will be closed.  So instead the user has to create their own TestWatcher and call BrowserExtension.getOrCreateBrowser(extensionContext).close().  This works fine.
The order of the extension registration will matter if we go this route.  We need to have the trace-related methods execute first before the browser is closed.  So the user must be careful how they apply the annotations:

works:
@ExtendWith(BrowserStackTestWatcher.class)
@UsePlaywright(SomeOptions.class)
public class MyTests {
}

doesn't work:
@UsePlaywright(SomeOptions.class)
@ExtendWith(BrowserStackTestWatcher.class)
public class MyTests {
}

I think this trade-off is acceptable for nowbecause this is a one off thing for services like BrowserStack. If you agree I can make the changes in my branch.

The user cannot call browser.close() from within a normal JUnit AfterEach hook.  If they do, all of the trace recording that happens in the test watcher methods will not work because the BrowserContext will be closed.  So instead the user has to create their own TestWatcher and call BrowserExtension.getOrCreateBrowser(extensionContext).close().  This works fine.

I believe we should address this. I hope the traces can be saved when BrowserContext.onClose is emitted, that would work for the cases when the context is closed, browser is closed or just test fails/ends (triggering context close). Would that work? At least this is how it is done in Node.

The order of the extension registration will matter if we go this route.  We need to have the trace-related methods execute first before the browser is closed.  So the user must be careful how they apply the annotations:

This is counter intuitive and it'd be nice if we could avoid that. I hope we can save traces on context close and avoid this problem, but if we don't, this ordering constrain should be a minor limitation.

I hope the traces can be saved when BrowserContext.onClose is emitted, that would work for the cases when the context is closed

@yury-s I really like this idea but there is one drawback that I think can be worked around but before I implement I wanted to get your thoughts:
In JUnit, we don't know whether a test passed or failed until the TestWatcher method execute.  In the case of a RETAIN_ON_FAILURE trace setting, we will still have to wait for the TestWatcher methods to execute to know whether to save the trace or not, however if the Browser is closed at that point by the user in their AfterEach hook, we won't be able to save the trace.
The workaround I can think of is to save the trace always, and then delete the trace if the trace setting is RETAIN_ON_FAILURE.  The flow would be:

Start trace as we currently do
Configure BrowserContext.onClose to save the trace file if trace setting is ON or RETAIN_ON_FAILURE
In the TestWatcher.testPassed method, if the trace setting is RETAIN_ON_FAILURE, delete the saved trace.

This would allow us to avoid having the user register their own TestWatcher to close the browser and would remove the Extension registration order issue.  Does this sound like a good compromise?

Yes, this sounds good to me. In Node.js we also record the trace if it might be needed when the test is done and then delete it if according to the setting and the test's outcome it should not be preserved. I think it'd be nice if we followed the same logic in the Java por.


Clarifying scheduling settings

Added some detail that makes it clearer what this does.

@altendky glad to contribute! This is such a useful tool and I really enjoy documentation :D


How to assign a mac Address to a vm using python

Hi i Have an envy where i have to assign the mac address to a vm by giving a 2 digit number to it do you have any script for that?

@sanjay1839 Take a look at the create_exhaustive_vm.py. You should be able to create or update vm nic with specific mac type.
https://github.com/vmware/vsphere-automation-sdk-python/blob/master/samples/vsphere/vcenter/vm/create/create_exhaustive_vm.py#L169

@tianhao64  its little confusing do you have any script to just change the mac address of a vm which is already cloned from a template

I found https://github.com/StackStorm-Exchange/stackstorm-vsphere/blob/master/actions/stasis/new_networkadapter.py helpful.


is.safari() return true in MS Edge browser

is.safari() return true in MS Edge browser and is.not.edge() return true in MS edge as well. :/

the problem occurs also with is.chrome()

can you try with https://github.com/evdama/is-it-check and let me know please


keras layers LSTM uses inconsistent dropout approach

System information

TensorFlow version (use command below): 2.2

Describe the current behavior
The input dropout mask is the same for the respective input, forget, update, and output computation.
from the call method in the LSTM class in recurrent_v2.py
    dropout_mask = self.get_dropout_mask_for_cell(inputs, training, count=4)
    if dropout_mask is not None:
        inputs = inputs * dropout_mask[0]

However, the recurrent dropout mask is unique for the input, forget, update, and output computation
        h_tm1_i = h_tm1 * rec_dp_mask[0]
        h_tm1_f = h_tm1 * rec_dp_mask[1]
        h_tm1_c = h_tm1 * rec_dp_mask[2]
        h_tm1_o = h_tm1 * rec_dp_mask[3]

If the input dropout mask approach was the intended behavior can someone link me a reference paper that explains why and shouldn't we at least set the count=1. To me it seems like we are attempting to follow the approach from "A Theoretically Grounded Application of Dropout in Recurrent Neural Networks"
Describe the expected behavior
I'd have thought the input dropout mask would be unique to the input, forget, update, and output computation

@zacwellmer
Please share a simple stand alone code such that we can replicate the issue faced, or is possible share a colab gist for us to analyse the error faced.

I don't think stand alone code would help to describe this issue since the issue is heavily embedded into the LSTM implementation. I'll write the equations which are being performed and what I expect to occur.
Current Behavior
for each sequence the masks $\mathbf{m}_{x}$, $\mathbf{m}_{hi}$, $\mathbf{m}_{hf}$, $\mathbf{m}_{ha}$, and $\mathbf{m}_{ho}$ are sampled then used in the following LSTM update

Expected Behavior
I would expect $\mathbf{m}_{xi}$, $\mathbf{m}_{xf}$, $\mathbf{m}_{xa}$, and $\mathbf{m}_{xo}$ to be different for each gate

I'm guessing this is not currently being done b/c there is a desire to use the gpu implementation and that doesn't seem to allow 4 different masked inputs values

@qlzh727 is there any updates on this? If there's a paper that the current convention was modeled after I'd love to check it out. If not, I'm happy to help out with a PR, though it seems like this would change _could_use_gpu_kernel to False for input dropout.
Would it be possible to just mask the kernel (could be done to have the same effect as masking the input for forward prop)? I think this would mean we need to mask gradients as well though. If this is possible, we could use the same solution for recurrent dropout to enable _could_use_gpu_kernel

@qlzh727 @haozha111 do you folks have any thoughts on this? I'm open to make the PR to fix this but would prefer to know if it's a bad idea before spending time on it

Thanks for reporting the issue. Let me check the change history and related paper/math, and I will post some updates.

@qlzh727 is there any updates on this? I'm still open to helping

@qlzh727 FYI looks there is also discrepancies in how the input mask is handled between when _could_use_gpu_kernel is True and False. When it is True it looks as though we properly apply dropout (uniquely to i, f, a, and o) (here).
        inputs_i = inputs * dp_mask[0]
        inputs_f = inputs * dp_mask[1]
        inputs_c = inputs * dp_mask[2]
        inputs_o = inputs * dp_mask[3]

Seems like the simplest fix for this is to add an extra condition on self._could_use_gpu_kernel requiring that dropout==0.0. Then the following lines could be dropped (here)
self.reset_dropout_mask()
      dropout_mask = self.get_dropout_mask_for_cell(inputs, training, count=4)
      if dropout_mask is not None:
        inputs = inputs * dropout_mask[0]

Very sorry for the long wait.
I checked RNN code history in recurrent.py. Historically we have 2 implementation, which is branched by flag "implementation" in https://github.com/tensorflow/tensorflow/blob/8c80b0433f6f09a720a4fc2fbe55b64b4948965c/tensorflow/python/keras/layers/recurrent.py#L2429.
In the implementation 1, the input/recurrent input to IFCO gates are dropout via different mask, whereas in implementation 2, they are dropout via same mask. See https://github.com/tensorflow/tensorflow/blob/8c80b0433f6f09a720a4fc2fbe55b64b4948965c/tensorflow/python/keras/layers/recurrent.py#L2468. The recurrent_v2 is using implementation 2 as the basic and mimic it behavior. Historically, we create 4 dropout mask so that both implementation can use the same field, rather than branching the mask creation logic based on "implementation" version.
Hope this answers your question.

No worries and thanks for circling back!
I understand what it is doing but I don't understand why this would be the desired behavior. I don't understand why a different variant of input dropout would silently be used from an arbitrary combination of flags (ex: dropout>0 and recurrent_dropout=0 vs. dropout>0 and recurrent_dropout>0 ).
The only case I could see for sharing the IFCO dropout masks is if the user preferred the code to be faster (using the cudnn implementation) at the cost of questionable performance (I'm not aware of any works studying the impact of fixing a mask for all gates). But even still why would we only offer this speed/performance trade-off for the input mask but not the hidden state mask?

The reason we split the logic between dropout = 0 and recurrent_dropout = 0 in recurrent_v2 implementation is that cudnn kernel is a fused op and we can't inject the recurrent dropout for hidden state in each timestep. On the other hand, the input dropout can be done by dropping out the overall input sequence before feeding the input to the cudnn kernel.
Note that in the implementation 2, the behavior between recurrent.py and recurrent_v2.py should be the same. The same dropout mask is used for all 4 gates, and I think that's intended. We could certainly change recurrent_v2.py to use 4 different mask for input IFCO, but I am not sure if that's intended behavior. I would expect the mask to randomly drop the same feature for all IFCO, which mimic the behavior that some certain feature is totally hide from the network within the batch. This is aligned with the concept of the variational dropout, which use the same mask for all timesteps.
It seems to me that using different mask for 4 gates will introduce noise to the network, but I don't have the math proof for it.

ah gotcha, thanks for the explanation. I'm not sure how the cudnn implementation works but the reasoning sounds like it makes sense

I would expect the mask to randomly drop the same feature for all IFCO, which mimic the behavior that some certain feature is totally hide from the network within the batch. This is aligned with the concept of the variational dropout, which use the same mask for all timesteps.

This approach is called "tied-weights LSTM". I agree that the tied-weights approach seems to closely follow traditional uses of dropout (dropping a specific subset of units). However, dropout can also be interpreted as dropping rows of the weight matrix. Through the lens of the second approach it seems intuitive that the mask should differ between gates.
It turns out the untied-weights LSTM performs better. From section 4.1 and referring to the trade-off from tied-weights

With the second parametrisations we would place a distribution over the single matrix W. This leads to a faster forward-pass, but with slightly diminished results as we will see in the experiments section

From Table 1

It seems to me that using different mask for 4 gates will introduce noise to the network

yeah, the entropy of q(ω) would be larger in the un-tied weights approach

Thanks for the detailed reference.
If I understand the "MC" correctly, I don't think keras is currently using MC dropout at test time. Basically dropout is disabled at eval/predict time. And if we remove the item with MC, then the tied weights are actually out performing the untied weights (lower error and higher WPS).

that's a great point, thanks for taking a closer look at that table than I did. On second thought I'm not sure how helpful that table is for us since it doesn't tell us which performs better when dropout is only applied to the input gates (implementation=1).
Still seems odd to me that we follow the tied weights approach when dropout>0 and recurrent_dropout=0 but follow the untied approach when dropout>0 and recurrent_dropout>0. But if this is the desired behavior, I guess I could at least update the docs

I don't think we perform differently between recurrent_dropout=0 and recurrent_dropout>0, since the default implementation in TF2 is implementation=2, which only use the first mask out of 4 to mask the input. The implementation=1 is only used in TF1 and we can't change its behavior since it is suppose to be frozen.
https://github.com/tensorflow/tensorflow/blob/8c80b0433f6f09a720a4fc2fbe55b64b4948965c/tensorflow/python/keras/layers/recurrent.py#L2469
If there is no other questions, I will close this bug as working as intended. Feel free to reopen it if there is any other issue.
Sorry again for the long wait and thank you the bring up this question to us.

I don't think we perform differently between recurrent_dropout=0 and recurrent_dropout>0, since the default implementation in TF2 is implementation=2, which only use the first mask out of 4 to mask the input.

I don't think this is true. implementation=1 is still used when dropout>0 and recurrent_dropout=0. I couldn't figure out a good way to fix the generated dropout masks (fixing the random seed doesn't work) between both approaches. You will need to follow this hacky approach with pdb. In short, the old approach is still used in recurrent_v2.py
Here's a colab notebook to demonstrate

I don't think we perform differently between recurrent_dropout=0 and recurrent_dropout>0, since the default implementation in TF2 is implementation=2, which only use the first mask out of 4 to mask the input.

I don't think this is true. implementation=1 is still used when dropout>0 and recurrent_dropout=0. I couldn't figure out a good way to fix the generated dropout masks (fixing the random seed doesn't work) between both approaches. You will need to follow this hacky approach with pdb. In short, the old approach is still used in recurrent_v2.py
Here's a colab notebook to demonstrate

I don't think so.. when dropout>0 and recurrent_dropout=0, it will fallback to recurrent.py, but both LSTM and LSTM Cell are created with implementation=2 (you can verify that by print out the layer.implementation). When implementation=2, it will use tied dropout, whereas implementation=1 will use untied dropout.

Regardless of what the user passes input for implementation, if self._could_use_gpu_kernel is true, then the tied weights approach is used for inputs.
https://github.com/tensorflow/tensorflow/blob/2b96f3662bd776e277f86997659e61046b56c315/tensorflow/python/keras/layers/recurrent_v2.py#L1091-L1095
https://github.com/tensorflow/tensorflow/blob/2b96f3662bd776e277f86997659e61046b56c315/tensorflow/python/keras/layers/recurrent_v2.py#L1120-L1149

it will fallback to recurrent.py

Maybe I'm misunderstanding something. By "fallback to recurrent.py" do you mean that recurrent_v2.py is not used? b/c that example in the colab notebook shows the tied weights approach being used (unless the output is thrown-away after?)

Correct, when self._could_use_gpu_kernel is True, then the tied dropout approach is used and all the logic is in recurrent_v2.py. When self._could_use_gpu_kernel is False, it will fallback to https://github.com/tensorflow/tensorflow/blob/2b96f3662bd776e277f86997659e61046b56c315/tensorflow/python/keras/layers/recurrent_v2.py#L1120-L114, and the logic of self.cell.call() is the actual logic gets triggered which lives in recurrent.py. When implementation=2, then the tied dropout will be used in that case.

The user provided input of the implementation flag doesn't seem to matter since it's overridden anytime the recurrent dropout rate is greater than 0.
https://github.com/tensorflow/tensorflow/blob/2b96f3662bd776e277f86997659e61046b56c315/tensorflow/python/keras/layers/recurrent.py#L2300-L2302
The tied weights dropout looks like it is only used when implementation=2, dropout>0, and recurrent_dropout=0.
Why wouldn’t we just offer a tied weights approach and an untied weights approach instead of silently changing based on an arbitrary set of parameters which the user is unaware of?


First run at M1 support

@grendello should we pull in the libMonoPosixHelper code for this PR or wait for Mono.Posix to support M1?

@grendello should we pull in the libMonoPosixHelper code for this PR or wait for Mono.Posix to support M1?

The new Mono.Posix repo already supports that, but it will be a while before it produces a nuget. I guess pulling in libMonoPosixHelper code would be fine if you want to get this PR in ASAP

closing in favour of #87


Django 1.9 fix: apps.get_model

if you want to support django 1.7 and below, you need something like this:
try:
    from django.apps import apps
except ImportError:  # django < 1.7
    from django.db import models as apps


Add MIT License and code of conduct markdown files

Kindly assign me this under JWOC'24

@manyaa1  you can only be assigned one issue at a time.

Kindly assign me this under JWOC'24

@Priyanshi662 assign me this issue as I'm now done with previous issue


pghoard: bump version to 2.1.1

Apparently small formatting fix required

@rikonen , I'm not familiar with the process, but could you please tell when this new 2.1.1. version will appear in pypi repository?


Fix YAML validation + prepare for patch release

This PR contains a fix for the YAML validation skip reported in #121 and the preparation for a patch release

Error seems to be related to the validation of YAML files that have no header. I'll try and fix this first

I think that part of the issue was that no tests really checked we performed the validation. Should we add some new tests to ensure this doesn't creep in again somehow?
(I think it might just be a case of having a test that we actually intend to fail validation - that can only happen if content is actually passed)

Good point! I'll add a failing test :)


Only using CPU in Jupyter Notebook

Hi,
How do I set the library to only use CPU when I run it in Jupyter Notebook I can only found instructions for the command line

@nilsstre I am sorry for the late reply. As shown in the testing code, by changing the setting of cuda as None.
{
cuda = None				# the gpu id, e.g., 0 or 1, otherwise, set it as None indicating to use cpu
}


Use semantic versioning/tags on the image

Can you tag images with a version in addition to applying the latest tag? Makes it easier to consume these fantastic images :-)
See also<EMAIL_ADDRESS>for how convoluted docker tags are...

Sure! Do you have a suggestion for how you'd version them?
Most of the images that I've seen on Docker Hub tend to follow the underlying version of a framework or major software release. In this case, I'm already doing that with Python 2 vs Python 3 and I'd certainly be open to doing that with the JS images.
Any ideas are very much welcome!

I wouldn't mind if you just bumped a minor (e.g. 1.x) on each revision that doesn't contain breaking changes).  The problem with this (and many other docker images) is that it's not 100% reproducible, e.g. the -js version installs node 6.x
RUN curl -sL https://deb.nodesource.com/setup_6.x | bash -
RUN apt-get install -y nodejs && npm install -g npm@latest

So the version on Docker Hub depends on the time the image was built.
On the other hand, just monotonically increasing the version would be fine with me as well. It's just meant to ensure people can pull an immutable image version from docker hub by tag.

Just found the image and it works great for JS tests. This versioning scheme would be great. Otherwise, to have reproducible builds we need to build the image on our own. What can we do to help you on this?

I started some work on this over the past few days: https://hub.docker.com/r/markadams/chromium-xvfb-js/tags/
The JS image now contains tags for 6.x and 7.x versions of Node and the exact versions are pinned in the Dockerfiles. Next, I'll probably create some tags for the minor versions as well.


feat: Extended trusted_entities variable to support multiple types

Description
This change allows a better customization for the trusted entities used in the assume role policy
For example :
trusted_entities = [
    {
      type = "AWS",
      identifiers = ["arn:aws:sts::XXXXXXXXXXXX:assumed-role/OktaRoleForXXX/xxxx@xxxx"]
    }
]

Motivation and Context
Currently, trusted_entities input variable only accepts a list of strings which is added to the type Service of the assume role Principal.
For example:
trusted_entities = ["service.amazonaws.com"]

Will be interpreted as :
Principal = {
   ~ Service = "lambda.amazonaws.com" -> [
      + "lambda.amazonaws.com",
      + "service.amazonaws.com",
    ]
}

In the issue https://github.com/terraform-aws-modules/terraform-aws-lambda/issues/138 I explain that we need a AWS Principal in our assume role (the goal is to execute lambda in local using its assume role).
Breaking Changes
This first version overwrites trusted_entities input variable. It was previously a list of (service only) strings, and now becomes a list of objects consisting of a type string (like Service or AWS) and an identifiers array of strings (like an array of services URL as before or a list of ARNs), which will break previous usages of this variable as a list of strings.
But It could also be moved to another input variable so it doesn’t break the current trusted_entities input variable. The only thing that is missing is a good variable name which reflects the openness of the input variable compared to the current trusted_entities, which actually seems to be a trusted_services_entities.
How Has This Been Tested?

[ ] I have tested and validated these changes using one or more of the provided examples/* projects

[x] I have executed the code in our project and it results in a good terraform plan :

module.lambda.aws_iam_role.lambda[0] will be updated in-place
  ~ resource "aws_iam_role" "lambda" {
      ~ assume_role_policy    = jsonencode(
          ~ {
              ~ Statement = [
                  ~ {
                      ~ Principal = {
                          + AWS     = [
                              + "arn:aws:sts::XXXXXXXXXXX:assumed-role/OktaRoleForXXX/xxx@xxx",
                            ]
                            # (1 unchanged element hidden)
                        }
                        # (3 unchanged elements hidden)
                    },
                ]
                # (1 unchanged element hidden)
            }
        )
        # (7 unchanged attributes hidden)

        # (1 unchanged block hidden)
    }

Thank you for your help and your fantastic work on this module 👏

I’ve updated the pull request using try but I’m not very familiar with it so don’t hesitate to give me your feedback/modifications
Thank you !

Thanks @flibustier !
I have updated the code and examples.
v1.47.0 has been just released.

Great job! I successfully tested it in our project!
Thanks so much!! 🎉


added henanigans theme

I’m making a consistent theme across multiple dev applications.  I
would like to include it in your project.
Other henanigans supported things include:

Jupyter (i.e. iPython) notebooks
Sublimetext
Matplotlib
Snakeviz (via stylish)
iTerm
Terminal
Konsole
Zsh
Gmail (via stylish)
Google (via stylish)

Thanks


Morph relations fields are undefined

Hi,
Those relations which are not morphed works perfectly but, what about morph relations?
/**
     * @Relations
     * @return \Illuminate\Database\Eloquent\Relations\MorphTo
     */
    public function requestable(): MorphTo {

        return $this->morphTo();
    }

this packages creates following doc
/**
 * @property-read \Illuminate\Database\Eloquent\Model|\Eloquent $requestable
/*

And I'm using like this $this->request->requestable->project->id but project->id is undefined.

Any progress on reading morphed relations?

Workaround.
Define your relation manually on phpdoc.
/**
 *
 * Class description
 * @property Post|Video|OtherClass $commentable
 */
class comment .....

My morphTo relation produces the same model as return type for the property:
/**
 * Website.
 * [...]
 * @property-read \App\Entities\Website $owner
 */
class Website extends EntityBase
{

    /**
     *
     * @return MorphTo
     */
    public function owner(): MorphTo
    {
        return $this->morphTo();
    }
}

Is there a way to ignore these relations in order to not been overridden by ide-helper:models command? Or set them default to be mixed type?

I'm having the same issue. What's the recommendation?

@barryvdh Can you please re-open this issue? It's still relevant


Add seldon deployment predictor parameters and resource requirements

Describe changes
I implemented passing optional list of parameters to predictors in Seldon Deployments (within Seldon integration).
Add parameters to SeldonDeploymentPredictiveUnit and SeldonDeploymentConfig, and pass these parameters all the way to the seldon deployment manifest.
Add resource requirements to SeldonDeploymentPredictors and SeldonDeploymentConfig, and pass these parameters all the way to the seldon deployment manifest.
Document usage.
Pre-requisites
Please ensure you have done the following:

[x] I have read the CONTRIBUTING.md document.
[x] If my change requires a change to docs, I have updated the documentation accordingly.
[ ] If I have added an integration, I have updated the integrations table and the corresponding website section.
[ ] I have added tests to cover my changes. not applicable, no test suite

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Other (add details above)

A feature request has been made earlier today https://zenml.hellonext.co/p/in-seldon-integration-allow-for-predictor-parameters-to-be-passed

@d-lowl can you please add the word engineResources to the .pyspelling-ignore-words file to fix check spelling error.

Thanks for the review comments, they've been addressed now. Good to merge when you are ready


option to not show things that unity auto upgrade

a button to exclude from the list all the things that unity auto upgrade
For example

I'm pretty sure those are handled automatically. Or maybe that's wishful thinking, I'd like to know that.

The tool warns you about items marked with [Obsolete].
I don't make any assumption and show you everything.
Because I can't tell what is the [Obsolete] about, I can't not easily discard them.
That is particularly subjective.


[MSBuild] PathTooLongException

I got an issue in msbuild. While NSwag searchs for assemblies the PathTooLongException appears. It's happening only in specific situation but still..
System.AggregateException: One or more errors occurred. ---> System.IO.FileLoadException: Could not load file or assembly 'myassembly' or one of its dependencies. The filename or extension is too long. ---> System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
5>     at System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths)
5>     at System.IO.Path.GetDirectoryName(String path)
5>     at System.IO.FileSystemEnumerableIterator`1..ctor(String path, String originalUserPath, String searchPattern, SearchOption searchOption, SearchResultHandler`1 resultHandler, Boolean checkHost)
5>     at System.IO.Directory.GetFiles(String path, String searchPattern, SearchOption searchOption)
5>     at NSwag.CodeGeneration.SwaggerGenerators.AssemblyLoader.<>c__DisplayClass0_0.<RegisterReferencePaths>b__1(Object sender, ResolveEventArgs args)
5>     at System.AppDomain.OnAssemblyResolveEvent(RuntimeAssembly assembly, String assemblyFullName)
5>     --- End of inner exception stack trace ---

I googled it and found this post.
Is it possible to consider external libs like Delimon.Win32.IO to avoid this problem?

Maybe .NET 4.6.2 solves this problem: http://stackoverflow.com/a/38889598/876814

Well after changes in .net framework versions:
4.6.2 NSwag && NSwagStudio - DirectoryNotFoundException
System.AggregateException: One or more errors occurred. ---> System.IO.FileNotFoundException: Could not load file or assembly 'MyAssembly, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=485d6168b1ae96cc' or one of its dependencies. The system cannot find the path specified. ---> System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\gitrepo\mfxi\External Tools\swagger-merger\node_modules\swagger-merge\node_modules\swagger2-utils\node_modules\z-schema\node_modules\request\node_modules\har-validator\node_modules\is-my-json-valid\node_modules\generate-object-property\node_modules'.
5>     at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
5>     at System.IO.FileSystemEnumerableIterator`1.CommonInit()
5>     at System.IO.Directory.GetFiles(String path, String searchPattern, SearchOption searchOption)
5>     at NSwag.CodeGeneration.SwaggerGenerators.AssemblyLoader.<>c__DisplayClass0_0.<RegisterReferencePaths>b__1(Object sender, ResolveEventArgs args) in C:\Users\piotrku\Documents\tmp\Nswagv5\NSwag-master\src\NSwag.AssemblyLoader\SwaggerGenerators\AssemblyLoader.cs:line 35
5>     at System.AppDomain.OnAssemblyResolveEvent(RuntimeAssembly assembly, String assemblyFullName)
5>     --- End of inner exception stack trace ---

4.6 NSwag && NSwagStudio - PathTooLongException
System.AggregateException: One or more errors occurred. ---> System.IO.FileLoadException: Could not load file or assembly 'MyAssembly, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=485d6168b1ae96cc' or one of its dependencies. The filename or extension is too long. ---> System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
5>     at System.IO.Path.LegacyNormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths)
5>     at System.IO.Path.InternalGetDirectoryName(String path)
5>     at System.IO.FileSystemEnumerableIterator`1..ctor(String path, String originalUserPath, String searchPattern, SearchOption searchOption, SearchResultHandler`1 resultHandler, Boolean checkHost)
5>     at System.IO.Directory.GetFiles(String path, String searchPattern, SearchOption searchOption)
5>     at NSwag.CodeGeneration.SwaggerGenerators.AssemblyLoader.<>c__DisplayClass0_0.<RegisterReferencePaths>b__1(Object sender, ResolveEventArgs args) in C:\Users\piotrku\Documents\tmp\Nswagv5\NSwag-master\src\NSwag.AssemblyLoader\SwaggerGenerators\AssemblyLoader.cs:line 35
5>     at System.AppDomain.OnAssemblyResolveEvent(RuntimeAssembly assembly, String assemblyFullName)
5>     --- End of inner exception stack trace ---

Are you sure MSBuild and VS are supported with this MAX_PATH change?
According to your source (comments).

Petr Vones
After many years the legacy MAX_PATH limitation is gone. Thanks ! Will also MSBuild and Visual Studio take advantage of it ?

JeremyKuhne
Not yet. Getting the blocks removed from .NET is the first step to making MAX_PATH a thing of the past.

Immo Landwerth [MSFT]
We haven’t yet updated the VM to support loading DLLs on long paths. So take this feature in .NET Framework 4.6.2 as a large step in the right direction, but don’t expect that Long Path issues are completely gone yet.

Are you using the recently released .net v4.6.2?

It's working now with v5 due to changes in #242.

Really? Why did this solve this issue here? The paths are still too long, or not?

After changes in #242 I don't use @referencepaths so NSwag doesn't need to look through whole solution because paths to dlls are already known (NSwag doesn't get into this unfortunate folder).

I think this is just "luck", the problem itself is not solved... But i dont know how easy it is to fix...

Long Path tool can resolve error messages like: path too long, cannot delete file, too long path, destination path is too long, etc.

Closing as not seen for a long time...


C# System.DllNotFoundException (k4a.dll)

Describe the bug
On some PC's the .dll refuses to load.
Exact same program works on most of our pc's but once in a while we will encounter a machine where it just doesn't work.
So far we have just changed the PC when it for some reason refuses to work.
But now we have experienced the program working before a windows update, and then refusing to load the dll after a successful windows update.
To Reproduce

Create a new C# console application.
Add Microsoft.Azure.Kinect.Sensor nuget package v1.4.1
Change platform to x64
Add code:

static void Main(string[] args)
{
      Microsoft.Azure.Kinect.Sensor.Device.GetInstalledCount();
      Console.WriteLine("Press any key to exit...");
      Console.ReadKey();
}

Run compiled program.

Expected behavior
A console window with the message "Press any key to exit..."
Actual behavior
Unhandled Exception: System.DllNotFoundException: Unable to load DLL 'k4a': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
at Microsoft.Azure.Kinect.Sensor.NativeMethods.k4a_device_get_installed_count()
at AzureKinectMissingExample.Program.Main(String[] args)
Logs
Application: AzureKinectMissingExample.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.DllNotFoundException
at Microsoft.Azure.Kinect.Sensor.NativeMethods.k4a_device_get_installed_count()
at AzureKinectMissingExample.Program.Main(System.String[])
Desktop (please complete the following information):

OS with Version:
Edition	Windows 10 Pro
Version	20H2
Installed on	3/16/2021
OS build	19042.868
Experience	Windows Feature Experience Pack 120.2212.551.0

SDK Version:  1.4.1

Firmware version:  No kinect needed to provoke the error.

Additional context
So far we have just changed the PC when it for some reason refuses to work.
But now we have experienced the program working before a windows update, and then refusing to load the dll after a successful windows update.

This code produces the exact same error.
Works on same pc that the other code works on and fails on the same pc's that the other code fails on.
class Program
    {
        static void Main(string[] args)
        {
            k4a_device_get_installed_count();
            Console.WriteLine("Press any key to exit...");
            Console.ReadKey();
        }

        [DllImport("k4a.dll", CharSet = CharSet.Auto)]
        public static extern int k4a_device_get_installed_count();
    }

Could it be that the k4a.dll is trying to load some .dll that is delivered with windows but is somehow damaged on a few PC's?
And how could I identify the faulty dll in that case?

Using this lovely tool: http://www.dependencywalker.com/
And running it on faulty machine and a healthy machine and comparing the results I have found, that the faulty machine is missing:
MSVCP140.dll and VCRUNTIME140.dll
Downloading and installing the following package resolved the issue.
https://www.microsoft.com/en-us/download/confirmation.aspx?id=48145
I do however feel that the error message could have been a little clearer.

For anyone stumbling upon this ticket.
I ended up getting the issue resolved on troublesome systems by installing:
c++ redistributable 2015
And
c++ redistributable 2019
Both seems to be needed, and sometimes included on PC's and sometimes not... I guess it depends on the vendor supplying the machines.


Make JHipster, Micronaut and spring-boot workflows fail if not fully cacheable

Looks good to me to make the builds fail if not fully cacheable. The other changes don't seem to be related and it isn't clear if the JDK upgrade is to be on the latest version or to match what the projects are using.

I upgraded JDK when it was required


'Smarties' object has no attribute 'get_params'

If I am grid searching over a pipeline that uses Smarties, how might I set or skip over the 'get_params'?

Closing this for now.


docs: translate responding-to-events

docs

translate responding-to-events

Apologies for the delay in addressing your comments. I've completed the revisions.

Apologies for the delay in addressing your comments. I've completed the revisions.

Hi @yishuolin , no worries. Appreciate your contribution and don't feel sorry😄


Integration Test - Release - 2021/09/28 19:38:00

Auto create for integration test. IssueCommandFlow

#pri1


Kerning options gives error with AAT font

Hi,
now I’m using the current version (v2.6a) and run in the problem that the option Kerning now throws an error for an AAT rendered font, which wasn't the case in the previous version (don’t know the exact version number). The following example using Proza Libre only works with an explizit selection of the rendering mechanism.
% !TeX program = xelatex
\documentclass{article}

\usepackage{fontspec}
\setsansfont[
%   Renderer = OpenType
]{Proza Libre}

\begin{document}
\sffamily
TEST

\addfontfeatures{Kerning=Uppercase}
TEST
\end{document}

file list
 *File List*
 article.cls    2014/09/29 v1.4h Standard LaTeX document class
  size10.clo    2014/09/29 v1.4h Standard LaTeX file (size option)
fontspec.sty    2017/03/31 v2.6a Font selection for XeLaTeX and LuaLaTeX
   expl3.sty    2017/03/18 v7019 L3 programming layer (loader)
expl3-code.tex    2017/03/18 v7019 L3 programming layer
l3xdvipdfmx.def
  xparse.sty    2017/03/18 v7019 L3 Experimental document command parser
fontspec-xetex.sty    2017/03/31 v2.6a Font selection for XeLaTeX and LuaLaTeX
 fontenc.sty
   tuenc.def    2017/02/22 v2.0g Standard LaTeX file
fontspec.cfg
 ***********

Sorry for the slow reply — can't promise a quick fix but I'll look into this as a first priority for the next round of fontspec updates.

Thanks. I’m not in a hurry, I finished the project with a previous version and a the moment don’t use an AAT font …

I finally dived back through the code to look into this, and it turns out there were never any AAT Kerning features — although it might not have given an error, as far as I know it couldn't have been doing anything :)

Thanks! So, can I assume, that manually selecting the Renderer is the proper way to go in this case?

Yes, if you want to use the Uppercase kerning option.
I didn’t realise that XeTeX defaulted to using the AAT renderer; if so that might be something that fontspec needs to provide an interface for.
Moreover, it doesn’t look like Proza Libre has AAT features available — is that actually the font you had the trouble with?

Yes it is. However, actually I have only a slight guess about the AAT features and don’t need them. But Proze was the font where I discovered the “bug” …