Symbol not found: _clock_gettime when using kqueue native transport on MacOS 10.11.6

Tried  to use netty-transport-native-kqueue on MacOS 10.11.6 and got the following:
dyld: lazy symbol binding failed: Symbol not found: _clock_gettime
  Referenced from: /private/var/folders/y3/8mx9s87n01942z74s5wjsxjw0000hb/T/libnetty-transport-native-kqueue8841250350785055197.dylib (which was built for Mac OS X 10.12)
  Expected in: /usr/lib/libSystem.B.dylib

Netty version
4.1.12.Final
JVM version (e.g. java -version)
java version "1.7.0_80"
OS version (e.g. uname -a)
MacOS 10.11.6 (El Capitan)

Yes the transport only works on MacOS Sierra+

Am 09.06.2017 um 22:26 schrieb marcuslinke<EMAIL_ADDRESS>Tried to use netty-transport-native-kqueue on MacOS 10.11.6 and got the following:
dyld: lazy symbol binding failed: Symbol not found: _clock_gettime
Referenced from: /private/var/folders/y3/8mx9s87n01942z74s5wjsxjw0000hb/T/libnetty-transport-native-kqueue8841250350785055197.dylib (which was built for Mac OS X 10.12)
Expected in: /usr/lib/libSystem.B.dylib
Netty version
4.1.12.Final
JVM version (e.g. java -version)
java version "1.7.0_80"
OS version (e.g. uname -a)
MacOS 10.11.6 (El Capitan)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@normanmaurer Is there any chance to get this compatible with El Capitan?

I'm not a C developer but maybe this could be fixed by a simmilar workaround as described in https://github.com/pocoproject/poco/issues/1453?

Also found this: https://github.com/jordansissel/xdotool/commit/9bc31403b95826d9fd8d6540c459ee862b2ac127
@normanmaurer @Scottmitch Would it be an accepted workaraound?

@marcuslinke I will check next week when I have a few cycles. Stay tuned

Note that this is a duplicate of https://github.com/Scottmitch/netty/pull/1#issuecomment-290704233 and there is additional context explained there.
TLDR - transport-native-kqueue should compile against 10.11 but the artifacts we publish are built on 10.12 and we do not support linking to older macOS versions.

[ This comment was originally on the other issue, but as this is the actual project, I'll comment here ]
This is quite frustrating -- a developer brought in testcontainers, which brings in netty, which exposes this issue and he broke the build on some of our developers' machines. We're now forced to choose between upgrading our hardware or using Netty...
I will echo the request that publishing an artifact to Maven Central which does not work on ~ 1/3 the Mac install base (roughly guessing based on the link above) is not very nice, and "just build your own" isn't really a solution when you bring in a third party project that depends on Netty.

Ah, in case anyone else gets frustrated by this -- the problem is that the docker-java library is inappropriately pulling in this kqueue transport, when it really doesn't need to.  So I'll work with the library maintainers to fix that...


Where to find the dataset?

Hi Cody!
Can you please help me find the data set on which you worked?

https://www.kaggle.com/mlg-ulb/creditcardfraud

Thanks a lot


Add profile visibility and not found page for missing profiles

Description
This PR adds the following features:

Displays a "not found" page if the requested profile does not exist.
Allows authorized users to view their own profile.
Enables users to view another user's profile if it has been created.

Type of Change

[x] New feature
[ ] Bug fix
[ ] Refactor
[ ] Documentation update
[ ] Other (please describe):

Checklist

[x] My code follows the project’s coding style
[x] I have performed a self-review of my code
[x] I have added tests that prove my fix is effective or that my feature works
[ ] I have updated the documentation as necessary
[x] My changes generate no new warnings or errors
[x] I have checked my code and corrected any misspellings
[ ] Any dependent changes have been merged and published in downstream modules

Related Issues
None.
Additional Information
None.

:tada: This PR is included in version 1.20.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Periodically clean leftover files

With ideascube/ideascube#704 we now have a new command:
$ ideascube clean leftover-files

Running this will remove all the stale mediacenter files which were associated to medias, but aren't any more. (either because the media was removed, or updated to a new file)
We probably want to set up a systemd timer or something to run this command periodically and reclaim disk space.
It will be available in ideascube 0.20.0.

PR #76 has been open for review

Fixed 1b8c043


Any open source make shift simulator to run Apollo AV stack?

Hi All,
As LGSVL going to be sunset, any make shift open source simulator to run Apollo AV stack?
Can we run the SVL itself in any of the offline mode, which could help for faster development?
Help suggest some inputs. Appreciate your guidance.

lgsvl just doesn't develop new features anymore, you can keep using it.
At present, the mainstream simulators are carla and lgsvl. By the way, apollo has a lightweight simulator called sim control in dreamview.
At present, the mainstream simulators are carla and lgsvl. By the way, apollo has a lightweight simulator called sim control in dreamview. I'm afraid I can't make it clear in a few words.

Closed due to inactivity. If the problem persists, pls feel free to reopen it or create a new one and refer to it.


PHOENIX-5221 Phoenix Kerberos Integration tests failure on Redhat Linux

Closing since this JIRA was resolved elsewhere.


Remove hardcoded auth header

Let through a few leftover lines. Tested and working against localhost (no auth), plus instances with Aerie native auth and CAM auth.

@Mythicaeda Yes, that's correct


oauth callback raise an error while use gitea with woodpecker

Component
server
Describe the bug
see also https://github.com/go-gitea/gitea/issues/17969
Even the woodpeckerci/woodpecker-server:latest raise this error, too.
System Info
{"source":"https://github.com/woodpecker-ci/woodpecker","version":"next-9e8d1a92"}

Additional context
No response
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A join our Discord Chat Server.

from https://github.com/woodpecker-ci/woodpecker/issues/605#issuecomment-992854121
new error:
time="2021-12-13T20:15:27Z" level=error msg="cannot authenticate user. oauth2: cannot fetch token: 405 Method Not Allowed\nResponse: "

It happened when I confirm the oauth request in gitea
There is also an error report in Gitea log
Completed GET /login/oauth/access_token 405 Method Not Allowed in 204.447µs

@zxcvbnm3057 can you paste your woodpecker server config?
(replace passwds with xxxxx or so)

version: "3"

services:
  woodpecker-server:
    image: woodpeckerci/woodpecker-server:latest
    container_name: woodpecker-server
    volumes:
      - /root/woodpecker:/var/lib/woodpecker/
    networks:
      - web-bridge
    restart: always
    environment:
      # This is for nginx-proxy
      - VIRTUAL_HOST=drone.example.com
      - VIRTUAL_PORT=8000

      - WOODPECKER_OPEN=true
      - WOODPECKER_HOST=https://drone.example.com
      - WOODPECKER_GITEA=true
      - WOODPECKER_GITEA_URL=http://code.example.com
      - WOODPECKER_GITEA_CLIENT=xxxxxxxxxxxxx
      - WOODPECKER_GITEA_SECRET=xxxxxxxxxxxxxxx
      - WOODPECKER_AGENT_SECRET="xxxxxxxxxxx"
      # - WOODPECKER_GITEA_PRIVATE_MODE=true
      - WOODPECKER_ADMIN=Admin

@zxcvbnm3057 what do you mean with nginx-proxy that there is no nginx in woodpeckerci/woodpecker-server

well, that was a plugin for nginx.
PS:The bugs I got this week even more than during the whole past year....

the config seems right - can you test with a secound account to log-in?

No, but I had reset the oauth token and clean the woodpecker-server data folder many times. But still got nothing.

So this works fine in your test environment?

# docker-compose.yml
version: '3'

services:
  woodpecker-server:
    image: woodpeckerci/woodpecker-server:latest-alpine
    networks:
      - intern
    ports:
      - 8000:8000
    volumes:
      - ./data/woodpecker:/var/lib/woodpecker/
    environment:
      - WOODPECKER_OPEN=true
      - WOODPECKER_HOST=http://woodpecker-server:8000
      - WOODPECKER_GITEA=true
      - WOODPECKER_GITEA_URL=http://gitea-server:3000
      - WOODPECKER_GITEA_CLIENT=0a40a3d2-adf3-4b27-9d30-64c6a10b94fd
      - WOODPECKER_GITEA_SECRET=gf5XKtr8tlrlUZlnsRgww3i8cvGVokkoIJ4KVKAC1KG4
      - WOODPECKER_AGENT_SECRET=1234512345123451234512345

  woodpecker-agent:
    image: woodpeckerci/woodpecker-agent:latest-alpine
    command: agent
    restart: always
    networks:
      - intern
    depends_on:
      - woodpecker-server
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    environment:
      - WOODPECKER_SERVER=woodpecker-server:9000
      - WOODPECKER_AGENT_SECRET=1234512345123451234512345

  gitea-server:
    image: gitea/gitea:dev
    environment:
      - USER_UID=1000
      - USER_GID=1000
    restart: always
    networks:
      - intern
    volumes:
      - ./data/gitea:/data
      - /etc/timezone:/etc/timezone:ro
      - /etc/localtime:/etc/localtime:ro
    ports:
      - "3000:3000"
      - "2222:22"

networks:
  intern:
    driver: bridge

that one works

OK, I'll give it a shoot...

I try to shutdown the nginx and export ports directly, then the problem is solved. It looks like nginx changed the method as the same time do redirect.

Thank you for all of your help!! That really help me a lot!
one more little thing, I can't downgrade my gitea from dev to latest.....But at least there is no more errors, for now.

@zxcvbnm3057 downgrading gitea is ... a bad idear - if you have no backup, you dont have to worry - gitea is on the way to deliver a new release soon too - so if released just switch there back to latest :)

haha yeah, I don't worry about it actually. Thank you once again and then I will close this issus. So see you later XD.


/sourceDependencies (+ etc) behavior with directory mode unclear

/sourceDependencies, /scanDependencies, /sourceDependencies:directives all can output to a directory, but the documentation about how to use that is slightly wrong.
First off, https://docs.microsoft.com/en-us/cpp/build/reference/sourcedependencies-directives?view=msvc-170 and https://docs.microsoft.com/en-us/cpp/build/reference/scandependencies?view=msvc-170 show the syntax as <cmd> directory\ whereas the trailing slash is not required.
Instead (and this behavior should be listed on all 3 pages), the compiler checks the given argument exists and is a directory (in other words, the directory must be pre-created before running the compiler) in order to enable "directory output mode". If the path does not exist or is a file, "file output mode" is used.
directory\ (with the trailing slash) is confusing because if the path does not exist OR is an existing file instead of a directory, you get the same error: fatal error C1083: Cannot open compiler generated file: 'directory\': Invalid argument.

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

ID: 8697ff9c-9a88-50ff-9b23-a85cdbee123a
Version Independent ID: be639a51-dc95-429f-ad7c-141c0717340c
Content: /sourceDependencies (Report source-level dependencies)
Content Source: docs/build/reference/sourcedependencies.md
Product: visual-cpp
Technology: cpp-tools
GitHub Login: @TylerMSFT
Microsoft Alias: twhitney

@shuffle2
Thanks for the report. There was a typo in the formatting for the syntax sections that unfortunately left a trailing \ visible in these articles. I've fixed it so it shouldn't show up anymore. I've also clarified the language around the directory and filename behavior to indicate the directory must exist.


Code Style

Great! Thank you very much.

Link to #3

For the redundant import java.util.Objects and the java.util.Objects is added since JDK 1.7, we should release a new version later.

Merged. BTW, maybe we can turn to use the https://github.com/novoda/gradle-static-analysis-plugin for the checkstyle and findbugs.

Another awesome plugin. But I think if we need PWD and findbugs too, we can add them by ourselves because gradle-static-analysis-plugin itself maybe have issue.

Well. We are already using findbugs and Idea Analyze, but do not use PWD. And we can apply findbugs through gradle plugin as well next time.


SMCP for OpenCL?

I found there olny SSCP for OpenCL, Is it possible to implement OpenCL SMCP compilation flow in the future? I found it difficult to embed OpenCL into Cpp like CUDA

It is not planned to implement SMCP for OpenCL, and there is also no reason or use case to do so. The SSCP compiler is superior in every way to the SMCP approach: It compiles faster, generates faster binaries, is more portable and extensible, an is a more elegant design.
Why do you want an SMCP compiler?
The only thing that the SMCP compilers give you is that they allow to mix-and-match CUDA/HIP source code with SYCL. This can be useful when migrating code. For OpenCL, this is irrelevant because OpenCL has a separate source compilation models, so wouldn't get the same benefits from an SMCP compiler either.

Because on my device there is only OpenCL. So I hope there is a SMCP compiler to compile directly. I think SSCP is too troublesome by saving LLVM IR. With SSCP, additional transcoding work has to be done at runtime.

It has a persistent on-disk kernel cache that negates pretty much all of those effects after the first application run. And even in plain OpenCL with ahead of time code generation, the driver would still need to lower SPIR-V at runtime to OpenCL, because this is how OpenCL works.
Please try SSCP first before asking for someone else. Again, it is superior to SMCP compilers in every way.


Node resolution on darwin does not seem to pick up the interface info correctly

Problem
When trying to commission an m5stack with a Mac laptop, if the address it advertises via mdns is its ipv6 link-local address then attempts to actually send commands to it end up with "no route to host".
Proposed Solution
I can ping the link-local ipv6 if I specify the right interface to use (which makes sense; you can't decide on the right interface from just the IP for a link-local address).
This suggests that we need to either send out messages on all interfaces or store the interface that the resolve was done on or something.
@woody-apple @andy31415 @pan-apple

Fixed by https://github.com/project-chip/connectedhomeip/pull/7388


Fix the case that labels are all ignored

An error occurred in line 177 ( C = probas.size(1) ) when input labels are all ignored, because labels got empty.
This PR deal with such problems.
One thing I concerned about is the difference between the lines I added and below lines
        if len(labels) == 0:
            # only void pixels, the gradients should be 0
            return logits.sum() * 0.

Above is a part of the original implementation of lovasz_flat. This doesn't exclude void labels for calculation the loss. Is it excepted behavior?

Hi,
Thanks for the PR. However, I think it is better to use logits.sum() * 0. rather than NaN since you want the loss to be 0..
Since the gradient of logits w.r.t. logits.sum() * 0. is 0. it doesn't matter if you exclude void labels or not. Said differently, I needed something that gave the 0. value and had gradient 0.. (I could also have simply created a new 0. tensor for that on the right device).
I would rather change line 177 into
if probas.numel() == 0:
    return probas * 0.
C = probas.size(1)

If you agree and make these changes I will merge.

Thank you for the explanation. I updated code as you said.


Use ruff instead of black, isort, and flake8

This PR replaces black, isort, and flake8 with ruff. Ruff does a great job removing unused imports in our opsets. There are some other minor formatting changes that I think are not worth the trouble of diverging from the default settings.
Supersedes #133

Looks good 🚀
However, I'm not super familiar with the ruff configuration details, maybe someone else can take a look to approve.

@adityagoel4512 Would you like to do the honors unless you see something amiss? Given that the config is quite defaulty and the diff is reasonably small I'd be happy to just see how it works out.

The attribute references are still private which is the reason why they are not in the public interface. On the other hand, maybe it is time to stabilize ONNX functions in Spox now that their support in the onnxruntime seems to have matured (even though I consider them pretty broken and useless in the standard).


DefineConstants not worked in compilation

Environment

dotnet sdk 2.1.402
Buildalyzer: 2.1.0
windows8.1 x64

Steps to reproduce

unpack buildalyzertest.constants.zip
move "buildalyzertest.constants/buildalyzertest.constants"
run dotnet run

"buildalyzertest.constants/buildalyzertest.constants" does

get project instance of sandboxproject
get workspace by ProjectAnalyzerExtensions.GetWorkspace()
enumerate class names

Expected Result
ns=sandboxproject.X1, X1
ns=sandboxproject.X3, X3
ns=sandboxproject.Program, Program
Hello World!

it means sandboxproject.X1(surrounded by DEF1 symbol) is included in Compilation.Assembly.
Actual Result
ns=sandboxproject.X3, X3
ns=sandboxproject.Program, Program
Hello World!

sandboxproject.X1 is not included in Compilation.Assembly.
DEF1 seems to be not defined in compilation.
Additionally, do dotnet build in sandboxproject by hand and analyze output assembly by dnSpy,
sandboxproject.X1 is included in symbols.

I can see where the problem is here. The constant will get defined correctly during the MSBuild pass when we build the project(s) and get the resulting project files, but then in .GetWorkspace() it passes those project files along with some other rudimentary information to Roslyn but doesn't pass the defined constants.
To get this to work I'll need to make sure any build constants get passed to Roslyn. This is tricky because I can't just pull those right out of the project file - they've got to come from the result of the build since they could get redefined or even based on other constants. I'll start looking into this.

This is now resolved and will ship with the next release.


Can "Hal" be compiled on "CentOS"?

Hello, is there a more specific source code compilation method?
I want to compile on X86 or CentOS or arm systems，
Please give guidance。

Sadly we support only Ubuntu 20.04, as we don't have the time to maintain more Unix flavours.


Unset git author/committer variables when running integration tests

TestAPIGitTag (and likely others) will fail if the running environment contains
GIT_AUTHOR_NAME and other env variables like it.
This PR simply unsets these when running the integration tests.
Fix #14247
Close #19509
Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>

Please send backport :)


[W5.7][W10-1] Way Tan

Edit find function to be non-case sensitive. Update tests and User Guide accordingly.

Hi Prof, noted on the PR. I may have branched at the wrong place, so wasn't sure how to rectify it. (the commit for the earlier LO was also captured)

Hi Prof, noted on the PR. I may have branched at the wrong place, so wasn't sure how to rectify it. (the commit for the earlier LO was also captured)

One way to fix it:

close this PR
create a new branch at the right place
cherry-pick the relevant commits from this branch to the new branch
open a new PR with the new branch


install board, if the setup time is long, need restart proxy

In GitLab by @luotian-github on Jul 18, 2018, 10:25
If you are reporting a problem, please make sure the following information are provided:

Version of board (last git commit number) , docker engine and docker-compose.
Config files of board, you can get them by packaging "board.cfg" and files in the same directory, including subdirectory.
Log files, you can get them by package the /var/log/board/.
Other necessery information.

In GitLab by @wknet123 on Nov 8, 2019, 07:55
Duplicate #1389

In GitLab by @sokril on Nov 8, 2019, 08:25
closed

In GitLab by @sokril on Nov 8, 2019, 08:25
assigned to @guyingyan


Safari v11+ not working with blueimp/jQuery-File-Upload plugin

I am stumped at the moment as to why I am unable to get the blueimp/jQuery-file-upload plugin to work with the desktop Safari browser v11+. My QA tested with v11.2 (MacOS El Capitan) and I've tested on v13.0.3 (macOS Mojave 10.14.6). Safari doesn't appear to be calling the .fileupload() function. However, the plugin works as expected in both Chrome and Firefox.
Here's the bare bones code I've been using for testing.
Html
<input class="upload" type="file" name="FileData" id="fileupload-remove-items" data-url="/analysis/upload"/>
JS:
  $('#fileupload-remove-items').fileupload({
        dataType: 'json',
        start: function (e, data){
            console.log('start'); // fires in Chrome & Firefox browsers, but *not* Safari
        },
        progress: function (e, data){
            console.log('progress');  // fires in Chrome & Firefox browsers, but *not* Safari
        },
        done: function (e, data) {
            console.log('done');
        }
    });

In both Firefox & Chrome the console.log() fires as expected. But nothing happens at all in Safari. I haven't been able to find any related SO posts or bug reports in this repo that answer this question so I'm now reaching out here. Can anyone else replicate this issue? Interestingly, I am able to upload a file from the demo page using Safari but looking through the demo code thus far has not made it clear how/why the simple above use case consistently fails with Safari.
Any help would be most welcome. Thanks ahead of time!
I have also asked this question on S.O.: https://stackoverflow.com/questions/58896103/safari-v11-not-working-with-blueimp-jquery-file-upload-plugin

Howdy!  I figured it out finally... it was the version of jQuery that my legacy website is using - namely, 1.7.3 which does not work with newer versions of Safari.  When I upped my jQuery to 1.8 Safari finally stepped in line like the other browsers.  I'd love to know what is specifically breaking it from that version, but need to move on and get this feature set out the door.  Hopefully this is useful info for you and others.  My answer is also on S.O.: https://stackoverflow.com/questions/58896103/safari-v11-not-working-with-blueimp-jquery-file-upload-plugin/58961924#58961924

Thanks a lot for coming back and posting your solution @afenix !
I've labeled this as a combined jQuery/browser bug and will leave the issue open for others to find your solution.
As far as I know, it's safe to upgrade to jQuery 1.9, which is the last version which supports IE 6-9.
I'll leave the minimal dependency version as jQuery 1.6 as it's still true for the project, despite the issues with Safari.

This was the same as my issue https://github.com/blueimp/jQuery-File-Upload/issues/3536.
I narrowed it down to being the change from jQuery 1.7.x -> 1.8.0; where the lower version didn't play well with newer Safari.

I've removed the browser/jquery bug labels, since #3536 points to this issue being fixable in this library (thanks @RobAndersson).

Turns out this was a regression introduced in #3435, which replaced promise.pipe() with promise.then().
When reviewing this I didn't test with jQuery versions lower than 1.8 anymore and unfortunately the behavior of promise.then() only matched that of promise.pipe() from jQuery 1.8 and higher.
But it should finally be fixed now for old (< 1.8) jQuery versions with the latest release:
<EMAIL_ADDRESS>


Out of date dependency causes breaking changes

In knex v11.5 we had to take advantage of the fact that conn.client.pool was an event emitter. However, in knex v12.6 uses an out of date verison of node-pool which is not an event emitter. The new version of node-pool is implemented as an event emitter. I realize that node-pool is, for the most part, an undocumented part of the knex API but that package should be upgraded since it can cause breaking changes in an application.

Closing since generic-pool is no longer used in this lib.


nixos/networking: set broadcast address

Motivation for this change
This allows the broadcast address to be specified in networking.interfaces.*.ipv[46].broadcast defaulting to "+" (which per ip-address(8) sets all the bits after the prefix). This does change the default broadcast address for anyone who has set static addresses - from <IP_ADDRESS> to the highest address on the specified network.
This fixes #34026 and (already closed) #26196.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

I would make this nullOr and use optionalString there. This way nothing changes unless you will it to.
I wonder what @wkennington @tstrobel @rnhmjoj from git blame think.

@oxij One thing I found when poking at the networkd version of this is that currently the default broadcast address changes when you toggle networking.useNetworkd - it's "<IP_ADDRESS>" under scripts and the highest address under networkd. That inconsistency seems undesirable.

FYI I have a partial version (still with a bug in the networkd version - not clear on how to add fields to that generated file) that drops the "-" option and just gives empty (corresponding to "+") and a full IP address as options to better match up with networkd.

You can make - an error when networkd is enabled.

Figured out the systemd/networkd stuff. How does this look?

I do agree that we should try to homogenize things between scripted and networkd services. Would networkd still work fine if we were to set this option to "+" by default?
As it is:

I feel like ip.broadcast != ""s are begging for that option to become nullOr.

Broadcast = optional, I would think this should be mkIf or something.

Any updates on this pull request, please?

I have not tested this post conflict-resolution, though if I understand the change of forEach = flip map correctly it should work.

Looks good except for the extra checks if broadcast exists. Thanks!

That check is necessary for manual IPv6 setup, as IPv6 does not have broadcast addresses.

This seems to be a useful thing to be able to set. I've got wifi and lan(cabled) connected at the same time.
Wifi has this:
inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global dynamic noprefixroute wlan0
lan only has this:
inet <IP_ADDRESS>/24 scope global eth0
so its missing the brd address. How does everyone else deal with this ?


Frozen players in replay mods

I was setting up the server side replay mod and I got it to work where it will record all players all the time but the issue is when I view the replays after they were recorded I noticed no players move in the replays I am guessing this is because of a Mod incompatibility to do with networking but I have no Idea what mod it might be. It is very odd I was moving around in the replay but it isn't captured but particles appear beneath me at certain points. I have tried making many replay mods and keep having the same issue and yes both the server and the client replay mod are in the same version 1.20.4. Here is a list of the Mods.

I must add that I did get these files off the server and upload them to drive to use them on my main PC I don't think that would be a problem unless I am not aware of drive messing with the replay mod files and breaking them.

Could you please uninstall all unnecessary mods and add them back one by one to see which is the one causing issues?
I would think it's likely ViaFabric or the other Via mods, badpackets, or very many players. So you can try these first.
Also ServerReplay 1.0.8 is released. Please also update to this version.

For me this behavior occurs when using https://modrinth.com/mod/vmp-fabric but I don't think that can be fixed easily.


Plugin switches temp units to C

Seems when sending a temp change to the AC (when units are set to F, of course), it automatically switches the AC's units to C. Recommend a config setting to ID desired units for those of us still stuck in the past ;)

knowing problem. Hope to fix it in the next Update.

The plugin won't support Fahrenheit for now.


Widget is closing automatically when user clicks on proceed button after choosing chain and wallet

Steps to reproduce:
1.Open keyless demo app
2.click on connect
3.Choose wallet and chain
4.Then click on proceed button
Actual result:
Widget is closing automatically when user clicks on proceed button after choosing chain and wallet
https://github.com/getsafle/safle-keyless-js/assets/149378074/25f584ab-c4f2-45b1-afe3-7b7afb98c417
Expected result:
Widget should not be closing when user clicks on proceed button

https://github.com/getsafle/safle-keyless-js/assets/149378074/78a65368-2db1-4e4a-b775-fa3ed9a80b84
Issue still exists

https://github.com/getsafle/safle-keyless-js/assets/149378074/a6ef3572-9dbb-4c10-82ca-c632c637b64d
Fixed


Support/RFC: Generic CI/CD integration

Is there an existing issue for this?

[X] I have searched the existing issues

Maybe extending ddev's providers.
Is your feature request related to a problem?
I've started using ddev recently and found it awesomely useful. Thanks for putting up such a great tool!
As an experienced DevOps and Docker practitioner, what I'm currently missing is come build/deploy workflow. Before the needs, some considerations:

I'm aware that ddev is mainly intended as a local development tool, so I understand it not being strong in this regard, but I think it would be in scope to add the extensibility to do some CI/CD. Not sure, thou. Let me know if not.
Aside of being in scope or not, I've found ddev's extensibility and customization very powerful and worth exploring. Awesome work in this space!
I'm still getting used to it and not too deep in ddev, so maybe there is some functionality I haven't discovered yet.
However, I've already read about hosting provider extensibility and I think it might suit my needs. I have to go deeper, yet, but just dumping my needs in case anyone else finds them useful and worth giving feedback, and hopefully, attracting more eyeballs and brains to it.

Describe your solution
As for my requirements, we're currently using ddev as our local development tool of choice for Drupal 7 & 8+ sites. Nothing fancy, just check out some repo, load some db dump, do some composer/drush make commands and start working locally on the contrib/custom modules. What we'd like to accomplish is some CI/CD tooling to allow us to:

Run some sort of ddev build command which would ideally run some basic "it works" tests and build a deployable artifact to test locally. Build artifact should include all necessary code, but repos contain only composer.*/*.make files, custom code and not much else. So build would do at the very least some composer or drush make steps.
For the above, we would have to use a custom Dockerfile (most probably based on some official php-fpm image), as ddev's web image is not suitable for production because of complexity (although I'd like it to be, for consistency). It hosts several services (fpm and webserver, at the least), which is a Docker antipattern and also I guess it might contain development & debugging functionality not suitable for production (xdebug & others). Even if it could be disabled, I guess it would be more work and having to track ddev's image. But having to create some custom Dockerfile it's not the end of the world, so I can bear with it.
(Maybe) After building and testing OK, some kind of ddev push for the built artifact to be pushed and deployed to QA/test/staging environments by the developers themselves. Production will be deployed by manually triggering some pipeline (at least for now).

Additional context
As we're still exploring ddev's abilities in this space, requirements might change/adapt/extend to fit or take advantage of ddev's features. I'm just putting up this write-up to gather feedback on ideas, suggestions and even maybe how people are currently addressing this. With my current knowledge of ddev, I'd bet that the missing stage to deployment to QA (and even production) in the development workflow would fit nicely, with the proper tooling and I think it could be useful for others even under different workflows and CI/CD scenarios, if done properly.

You'll want to take a look at https://ddev.readthedocs.io/en/latest/users/details/alternate-uses/#continuous-integration-ci

DDEV's focus is on local development. Specific idea you have can be implemented as DDEV Add-ons pretty easily. But since this is actually out of scope for the primary focus of the tool, I'm going to close for now, but happy to continue the discussion here or elsewhere.

Turns out that, while delving into the docs familiarizing with ddev, the link you gave me above was not among my reading :facepalm:. Much appreciated.
I agree it's out of scope. I was thinking more in some opportunistic (and generic enough) way of extending ddev right into production. I'm OK with closing this, since there is a valuable link and also can attract eyeballs. I will keep it handy while progressing with our production dockerization and hopefully I'll be able to come back with more input. Anyway, the initiative has been shelved, by now.
Thanks for your feedback, @rfay.

Unfortunately, with one dedicated developer and a significant (and great) community, it's not possible to expand scope very much. Thanks for your understanding!

new link to docs is here: https://ddev.readthedocs.io/en/latest/users/topics/remote-docker/#integration-of-ddev-docker-images-into-other-projects


#52 issues fix.

After looking into the code, I found out that the "type": "module" option in node_modules/mui-chips-input/package.json forces mui-chips-input to input the .js extension when using the import statement.
I have identified this issue and will request a PR as soon as possible. However, since I am not a contributor to the initial development of the module, I do not know the reason behind setting the "type": "module" option.
However, I don't know the exact reason why this option is set, so please judge whether it is right or wrong and merge or close this PR.
Revision history
"type": "module" option deleted.
Reference
#52

After reading the patch notes for version 3.1.0, I realized that the "type": "module" option in the package.json was an intentional setting by the developer.
I will submit a new pull request to modify the build options so that the extension names are specified in the import statements of the built mui-chips-input.es.js.


Update index.md

minor tweak - only to test the PR WORKFLOW

=> great, I can now see the change (submitted by PR) in the artifact file (see link above). I will now try to add one more commit to this PR and check it gets triggered again!

=> that works (artifact gets updated to reflect latest change)

Coool!!
@niconoe does the artikfact-website render well on your PC? I believe its hyperlinks are hardcoded relative to root? With hugo one can pass -b to change base directory, but not clear to me how to make it work in a directory-independent (relative?) way.

indeed, I can see the issue too! Will revisit soon, then :)


[Gaprindashvili] Fix DB loading strategy

Fix DB loading strategy. This was fixed in master, by refactoring
the DB loading indexes. We need this change for backported Azure
refresh. What this allows is using both find and lazy_find on
InventoryCollection and have all references loaded correctly from
the DB.
Right now, only the find was loaded and the lazy_find edges
were not loaded.
Partially fixes:
https://bugzilla.redhat.com/show_bug.cgi?id=1558078

@miq-bot assign @simaishi
@miq-bot add_label bug

@simaishi before/after we backport everything in https://bugzilla.redhat.com/show_bug.cgi?id=1487602#c18
we will need this to pass the Azure CI specs for targeted refresh
cc @bronaghs @djberg96 @agrare

@Ladas Is there an associated PR to master

@bdunne it was part of a big stream of refactorings in upstream only. In this PR https://github.com/ManageIQ/manageiq/pull/16659


added contributors.json file

added contributors.json file as per the issue #58
The file has the format as there was shown in the issue.

@devvsakib
Please review this


enhance card component layout

[x] position / order of buttons
[x] enhance text component (currently text area)

done


fraction of my custom stuff rebased onto #21

I think this is good enough
should merge this after #21

As I see, most of the changes in this PR are either already integrated or obsolete. Feel free to open a new PRs for each change that is still relevant.


Gulp?

In guh, gulp is being used for just a few things:

global command (gulp)
filesystem watching
vinyl-fs piping

Is it necessary? It add a lot of bloat to the console's output, and the useful features, like task orchestration and argument parsing are going totally unused.

So I guess it's possible to just bypass Gulp's CLI and output while still using all the nice things about Gulp.
With a couple line addition in a recent commit, just using node gulpfile.js is totally functional -- I changed app/build/main.js to automatically load the default task if not spawned via the Gulp CLI.
It'd be nice to have a short command for building, like "guh build" that is practically an alias here. We'll see.

Pushed up.


Puppet helper slaveagentport

add get_slaveagent_port()/set_slaveagent_port() methods to puppet_helper
add slaveagentport param to jenkins class

You'd also want to add this to the documentation- at the very least to the init.pp documentation. All parameters need to be declared, and explained at the top of init.p

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests


Avoid using addGenConstrLogistic when doing classification with Logistic Regression

Currently to do classification we round the output of logistic regression:
$\frac{1}{1 - e^{-f(x)}}$
where f(x) is the affine transformation defined by the trained logistic regression model.

For classification it seems it would be enough to use indicator constraints on the result of f(x), i.e. whether affinevars are negative or positive, and then we don't need to introduce non-linearity via addGenConstrLogistic.
Does this seem right?
- Riley

Hi Riley,
Yes, you are completely right. We could (and should) save adding the nonlinear constraint by using indicator variables.

No issues (excuse the pun) with me having a go at a PR?

Not at all. On the contrary, more than happy if you can do it. And if you need any help let me know.

FIxed by #318


[Windows] make setMinimum/MaximumSize() dpi change awareable

Current implemention of setMinimum/MaximumSize() on Windows platform only get device pixel ratio once at the functions called.  When user has multiple monitors with different dpi, this implementation will cause window size issue (too big / small) after drag the window to another monitor.
This PR implements dpi change awareness feature for setMinimum/MaximumSize().

LGTM


add min / max directives

@rkingon Thanks for this!  Do you find it's too complicated to use the jquery ui date options directly to the directive?
<input ui-date="{minDate: -20}"/>

I'm wondering if adding documentation or adding a link to documentation might serve us better than adding a new directive altogether to control something that can be done through the options.

Honestly, if it can be done via the options I'd be super down with that. Will passing an options minDate actually follow an object an listen for changes? IE: in the new directive it'll dynamically keep the min or max date consistent with the model passed to it.
That's my only goal, so if we can achieve that natively then having it in the docs would defiantly be beneficial

Thanks for the feedback, there was an issue raised similar to this so it definitely could use some clarification and probably an update of the example as well. There is a watcher on the options so that should update when the options change.

Confirmed that it works using a model in the options param. Pretty cool.
I left an example in the demo folder, feel free to either close this out or leave the example in -- might be helpful to others.
thanks man, sweet plugin.

Readme has been updated with link to jquery ui

will the min- and max-date options also used in the validation of the field?

@Devqon rather than allowing an incorrect date, ui-date will "disable" dates that do not validate per the min/max. Works very well, actually

Yes I understand, that works perfectly. But still the user can manually type in a date before the min, which won't be picked up by angular's form validation.


404 at /reference/run/

I found a broken link : https://docs.docker.com/reference/run/#mode-host
I arrived on this page through: https://github.com/RattyDAVE/alpine-vpn-pptp

Thanks for reporting, looks like that is an old URL; the new URL is https://docs.docker.com/engine/reference/run/#network-host
I opened a pull request to add a redirect; https://github.com/docker/cli/pull/2942, and a pull request to fix the readme where you found the broken link; https://github.com/RattyDAVE/alpine-vpn-pptp/pull/2

Thanks for reporting, looks like that is an old URL; the new URL is https://docs.docker.com/engine/reference/run/#network-host
I opened a pull request to add a redirect; https://github.com/docker/cli/pull/2942, and a pull request to fix the readme where you found the broken link; https://github.com/RattyDAVE/alpine-vpn-pptp/pull/2

Thank you very much!
在 2021年1月21日，22:45，Sebastiaan van Stijn<EMAIL_ADDRESS>写道：

Thanks for reporting, looks like that is an old URL; the new URL is https://docs.docker.com/engine/reference/run/#network-host
I opened a pull request to add a redirect; docker/cli#2942https://github.com/docker/cli/pull/2942, and a pull request to fix the readme where you found the broken link; RattyDAVE/alpine-vpn-pptp#2https://github.com/RattyDAVE/alpine-vpn-pptp/pull/2
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/docker/docker.github.io/issues/12151#issuecomment-764691923, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALWYYYJXPXELGJSF3DESYQDS3A4W5ANCNFSM4WMMO4PQ.

Thank you very much!
在 2021年1月21日，22:45，Sebastiaan van Stijn<EMAIL_ADDRESS>写道：

Thanks for reporting, looks like that is an old URL; the new URL is https://docs.docker.com/engine/reference/run/#network-host
I opened a pull request to add a redirect; docker/cli#2942https://github.com/docker/cli/pull/2942, and a pull request to fix the readme where you found the broken link; RattyDAVE/alpine-vpn-pptp#2https://github.com/RattyDAVE/alpine-vpn-pptp/pull/2
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/docker/docker.github.io/issues/12151#issuecomment-764691923, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALWYYYJXPXELGJSF3DESYQDS3A4W5ANCNFSM4WMMO4PQ.


Update Readme to include DB Context configuration via user secrets

Use dotnet user-secrets set key value to save the connection string to your database as an environment variable on your machine as opposed to storing it in a appsettings.json file.
Store the connection string using the CLI tool. Note: you will have to include your actual username and password.
dotnet user-secrets set "connectionString" "Server=MYAPPNAME.database.windows.net,1433;Initial Catalog=MYCATALOG;Persist Security Info=False;User ID={plaintext user};Password={plaintext pass};MultipleActiveResultSets=False;Encrypt=True;TrustServerCertificate=False;Connection Timeout=30;"
Reference the Configuration API with the key you defined, and your environment variable will be referenced.
It should look something like this:
            string connection = _configuration["connectionString"];
            services.AddDbContext<JabbrContext>(options => options.UseSqlServer(connection));

Updated the readme on PR #206, closing this


Is this possible to hover on x y Point by using realHover

I want to perform hover on XY point on the element.
Can we hover on XY Point passing by using realHover?

Yes the type of position property is
export type Position =
  | "topLeft"
  | "top"
  | "topRight"
  | "left"
  | "center"
  | "right"
  | "bottomLeft"
  | "bottom"
  | "bottomRight"
  | { x: number; y: number };

So if you will pass cy.realHover({ position: { x: 10, y: 10 }}) it will hover at x:10;y:10 coordinate relative to the element


Failed make tests

I was able to complete the install but here is the output running this on my server:
php: symbol lookup error: /usr/lib/php/20170718/phpiredis.so: undefined symbol: redisReplyReaderCreate

I closed this originally as I thought it had been caused by an old version of this lib but it seems this is different.

phpiredis
enabled

phpiredis version
1.0.0

hiredis version
0.13.3

make test
Build complete.
Don't forget to run 'make test'.
=====================================================================
PHP         : /usr/bin/php7.2
PHP_SAPI    : cli
PHP_VERSION : 7.2.9-1+ubuntu18.04.1+deb.sury.org+1
ZEND_VERSION: 3.2.0
PHP_OS      : Linux - Linux  -Q1 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 x86_64
INI actual  :  /phpiredis/tmp-php.ini
More .INIs  :
PHP         : /usr/bin/phpdbg7.2
PHP_SAPI    : phpdbg
PHP_VERSION : 7.2.9-1+ubuntu18.04.1+deb.sury.org+1
ZEND_VERSION: 3.2.0
PHP_OS      : Linux - Linux  -Q1 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 x86_64
INI actual  :  /phpiredis/tmp-php.ini
More .INIs  :
CWD         :  /phpiredis
Extra dirs  :
VALGRIND    : Not used
TIME START 2018-09-13 10:34:53
PASS [CLIENT] Connect to Redis [tests/client_001.phpt]
PASS [CLIENT] Persistent and non-persistent connections [tests/client_002.phpt]
SKIP [CLIENT] Persistent and non-persistent connections (UNIX socket) [tests/client_003.phpt] reason: Cannot find UNIX domain socket file at /tmp/redis.sock
PASS [CLIENT] Execute commands [tests/client_004.phpt]
PASS [CLIENT] Execute pipelined commands [tests/client_005.phpt]
PASS [CLIENT] Execute pipelined commands returning nested multibulk responses [tests/client_006.phpt]
PASS [CLIENT] Execute commands (binary-safe) [tests/client_007.phpt]
PASS [CLIENT] Execute commands with binary data (binary-safe) [tests/client_008.phpt]
PASS [CLIENT] Execute pipelined commands (binary safe) [tests/client_009.phpt]
PASS [CLIENT] Do not attempt to reconnect upon disconnection [tests/client_010.phpt]
PASS [CLIENT] Do not attempt to reconnect upon disconnection (pipeline) [tests/client_011.phpt]
FAIL [READER] Create reader resource [tests/reader_001.phpt]
FAIL [READER] Feed reader and parse responses [tests/reader_002.phpt]
FAIL [READER] Check reader state [tests/reader_003.phpt]
FAIL [READER] Reset reader [tests/reader_004.phpt]
FAIL [READER] Response types [tests/reader_005.phpt]
FAIL [READER] Set custom error handler [tests/reader_006.phpt]
FAIL [READER] Set custom status handler [tests/reader_007.phpt]
FAIL [READER] Custom error handler throwing exceptions or returning objects [tests/reader_008.phpt]
FAIL [READER] Properly handle NULL responses [tests/reader_009.phpt]
FAIL [READER] Keep multibulk responses types [tests/reader_010.phpt]
FAIL [READER] Test regression for segfaults [tests/reader_011.phpt]
PASS [READER] Parameters formatting should not modify input argument. [tests/reader_012.phpt]
PASS [READER] Parameters formatting should not break on many arguments [tests/reader_013.phpt]
PASS [SERIALIZER] Command serialization [tests/serializer_001.phpt]
PASS [SERIALIZER] Command serialization with non-string arguments [tests/serializer_002.phpt]
PASS [UTILS] Calculate the CRC16 of strings [tests/utils_001.phpt]
TIME END 2018-09-13 10:34:55
=====================================================================
TEST RESULT SUMMARY
Exts skipped    :    0
Exts tested     :   15
Number of tests :   27                26
Tests skipped   :    1 (  3.7%) --------
Tests warned    :    0 (  0.0%) (  0.0%)
Tests failed    :   11 ( 40.7%) ( 42.3%)
Expected fail   :    0 (  0.0%) (  0.0%)
Tests passed    :   15 ( 55.6%) ( 57.7%)
Time taken      :    2 seconds
=====================================================================
FAILED TEST SUMMARY
[READER] Create reader resource [tests/reader_001.phpt]
[READER] Feed reader and parse responses [tests/reader_002.phpt]
[READER] Check reader state [tests/reader_003.phpt]
[READER] Reset reader [tests/reader_004.phpt]
[READER] Response types [tests/reader_005.phpt]
[READER] Set custom error handler [tests/reader_006.phpt]
[READER] Set custom status handler [tests/reader_007.phpt]
[READER] Custom error handler throwing exceptions or returning objects [tests/reader_008.phpt]
[READER] Properly handle NULL responses [tests/reader_009.phpt]
[READER] Keep multibulk responses types [tests/reader_010.phpt]
[READER] Test regression for segfaults [tests/reader_011.phpt]

php: symbol lookup error: /usr/lib/php/20170718/phpiredis.so: undefined symbol: redisReplyReaderCreate
Does this still happen with this version? I'm confused here :)

'Note': Installing the phpiredis extension requires php to install both the APC and APCU extensions in addition to Hiredis, otherwise the dynamic library cannot be loaded.

Changes to support Hiredis >= 0.14, >= 1.0 have been merged in the v1.1 branch, the new minor release will be shipped in a few days is everything is fine. Thank you.


kafka: use error_reason dimension

This PR aligns kafka package to use error_reason dimension instead of the more generic error.
It also changes the other error reason to unknown, which better represent the reason.
Requires https://github.com/elastic/apm-queue/pull/289

@endorama is there anything holding back from merging this in?


[BREAKING] Change launchTask to Task.launch

Another option is launch(task: Task, standardInput: SignalProducer<Data, NoError>? = nil) related to Swift 3 API Design Guidelines.
Diff ignoring whitespace: https://github.com/Carthage/ReactiveTask/pull/76/files?w=1

Thanks! ✨


Boolean wrapped values don't refine that value to not be undefined

Suggestion
🔍 Search Terms
Boolean refine wrapped
✅ Viability Checklist
My suggestion meets these guidelines:

[ ] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion
if you wrap a value in Boolean() and use it in a conditional, it should still refine it to be not null or undefined.
📃 Motivating Example
In JSX its common to do the following
x && <Component x={x} />

but we have issues where if x is falsy but not accepted as a non value in jsx it can leak the type, so there is a lint rule to protected against it
https://github.com/jsx-eslint/eslint-plugin-react/blob/master/docs/rules/jsx-no-leaked-render.md
the least invasive fix of the lint rule is to wrap x in Boolean
Boolean(x) && <Component x={x} />

but that breaks typescripts ability to refine x.
example:
function a(x: undefined|null|{a: boolean}) {
    Boolean(x) && b(x);
}

function b(x: {a: boolean}) {

}

It is possible to fix this with something like this
interface BooleanConstructor {
    <T extends {} | string | number | boolean | Array<any>>(
        value?: T | undefined | null | '' | false,
    ): value is T;
}

playground link
Is there a reason to not have the above in the library - does it make typescript slower?

Another duplicate of #16655.

Thanks, I did search and didn't find that one.


drivers: nrf: Fix UARTE interrupt driven operation.

Bad order of interrupt calls made it unable to transmitt data
using interrupt driven API.
Signed-off-by: Mieszko Mierunski<EMAIL_ADDRESS>

@Mierunski @jarz-nordic can you please open a GitHub issue that is a bug and set this PR to fix that bug?

@carlescufi Mieszko is already working on it.

@anangl could you review this one please?


neuron: 8.2.3 -> 8.2.4; fixup

Description of changes

Version bump which fixes use of distutils removed in Python 3.12.
Pins Cython to the 0.x series since the version in Nixpkgs is newer than the maximum allowed by the package.
Removes unused patch for *-darwin.
Makes use of cmakeBool.
Switched to fetchFromGitHub.
Switched to finalAttrs instead of using rec.
Switched to substituteInPlace instead of a call to sed.

Hydra failures:

https://hydra.nixos.org/build/260854610

Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[x] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

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

4 packages built:

neuron
neuron-full (python311Packages.neuronpy)
neuron-mpi
python312Packages.neuronpy

Result of nixpkgs-review pr 317310 run on aarch64-darwin 1

4 packages built:

neuron
neuron-full (python311Packages.neuronpy)
neuron-mpi
python312Packages.neuronpy

Result of nixpkgs-review pr 317310 run on aarch64-linux 1

4 packages built:

neuron
neuron-full (python311Packages.neuronpy)
neuron-mpi
python312Packages.neuronpy

Result of nixpkgs-review pr 317310 run on x86_64-darwin 1

4 packages built:

neuron
neuron-full (python311Packages.neuronpy)
neuron-mpi
python312Packages.neuronpy

Merging without neuron, neuron.passthru.tests on aarch64-darwin as it started 18h ago and seems stuck. Per nixpkgs-review it should be fine.


not able to download some docx or doc files

Provide environment information
Python 3.10.10
gdown 4.6.4
What OS are you using?
macOs  12.6.3
Describe the Bug
i am trying to download a doc file
https://docs.google.com/document/d/17r06adjf3VBTJ57FQ4gw_T6JSVKWA_0I_1QPzAikSds/edit?usp=sharing
i used  gdown.download() with url option and with id  , but its not working
using id option is working for some doc files , but it's particularly not working for some files like the above one
with id option for the above file , i am getting this:
Access denied with the following error:
 	Cannot retrieve the public link of the file. You may need to change
	the permission to 'Anyone with the link', or have had many accesses.
You may still be able to access the file from the browser:
	 https://drive.google.com/uc?id=17r06adjf3VBTJ57FQ4gw_T6JSVKWA_0I_1QPzAikSds

if i use the url option ,  i am getting this:
Downloading...
From: https://docs.google.com/document/d/17r06adjf3VBTJ57FQ4gw_T6JSVKWA_0I_1QPzAikSds/edit?usp=sharing
To: /content/edit?usp=sharing
its saving html code to above sharing file and if i pass a file name as output , its storing only html code
i tried all the options(restart,use_cookies= False , fuzzy=True) as suggested in the other issues , but its not working
i tried to see what is the reason using the code in this repo , for res = sess.get(url, stream=True, verify=verify)
i see resp.text as Internal Server Error and
We're sorry...</h1><p>... but your computer or network may be sending automated queries. To protect our users, we can't process your request right now.
please let me know how to fix it
Thanks..
Expected Behavior
No response
To Reproduce
id = '17r06adjf3VBTJ57FQ4gw_T6JSVKWA_0I_1QPzAikSds'
gdown.download( id = id ,fuzzy = True , output='/content/')

Closed via https://github.com/wkentaro/gdown/releases/tag/v4.7.1


Simplify Scss

Simplify Scss to clearly separate content from theme

Done: cae9ebb78ffd0469c48cd920378571b07cf2baea

Last update: https://github.com/pierrick-marie/yummy-yam/commit/b11fe6c324d3a1521b8b409abc22ba416d7b8936


chore: add link checking in CI

This adds a link-checking action run on a weekly basis (Mondays) using lychee:
The check can also be triggered manually using the Github CLI or the 'Actions' tab interface for contributors of the repo.
This does not act on PRs but rather publishes / updates an issue on the repo with the link check report.
Demo run:
https://github.com/huitseeker/sui/runs/6282514162?check_suite_focus=true
Demo resulting issue:
https://github.com/huitseeker/sui/issues/4
We should also include a configuration file ./lychee.toml with possible excludes and other details, see documentation. This is a first stab, though.

Adding here since we never created an issue for this change:
Me: May I ask to be made the default assignee on these reports? FWIW, I
Francois: You can do that yourself by a PR against the GH action.
here's the doc:
https://github.com/peter-evans/create-issue-from-file#action-inputs
here's the line that needs changing:
https://github.com/MystenLabs/sui/blob/9eb55f8ba434bbb954a781ab9ea5d7660b33a12a/.github/workflows/links_checker.yml#L56-L62
Done:
https://github.com/MystenLabs/sui/pull/1961
https://github.com/MystenLabs/narwhal/pull/242


[2.2] Update dotnet-ef.csproj to correct shim generation

This should fix installations of dotnet-ef as a package which are broken due to https://github.com/dotnet/sdk/issues/2698
Description
Fixes https://github.com/aspnet/EntityFrameworkCore/issues/15448.  Due to https://github.com/dotnet/sdk/issues/2698, dotnet-ef does not work when installed as a package.
Customer Impact
This fixes a broken experience with dotnet ef typically encountered by .NET Core 3.0 users and anyone using a source-built SDK (like RedHat devs)
Regression?
No. This package never worked.
Risk
Low. Does not impact in-the-box version of dotnet-ef.

/azp run all

/azp run

Approved for 2.2.6
Wait for branch to open.

Discussed in shiproom. Does not meet the bar for customer impact.


Generate copy/copyWith methods

Hi,
I was wondering what would be the best way to define copy/copyWith methods on the models generated from swagger.
Ideally, they would be generated but it may be out of scope of this library. Maybe you have some pointers on how to use something like copy_with_extension together with swagger-dart-code-generator.
Thanks for the amazing work!

I think we can add it.
Actually good idea

@RomainFranceschini Please check this feature in latest version 1.4.6. We did not used external lib and implemented copyWith manually to not have external dependencies.

@Vovanella95 fantastic ! Already bumped the version and it works like a charm. Thank you for the responsiveness.


Path Validation Error on Cleanup

Description:
Getting Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
on cleanup for action
Action version:
3.7.0
Platform:

[x] Ubuntu
[x] macOS
[x] Windows

Runner type:

[x] Hosted
[ ] Self-hosted

Tools version:
Node 18, pnpm 7.12.1

Repro steps:
Example run
Expected behavior:
Clean up with no errors.
Actual behavior:
Path validation error on clean up.
This appears to be new to 3.7.0, because when we pinned the version to 3.6.0, it went away.

Hello, @NicholasLYang ! Thank you for creating the issue, we will take a closer look into it and see what can be done :)

Hello @NicholasLYang. We've merged the pull request with possible fix. Could you please try to use actions/setup-node@main to confirm that it works as expected.
For now I'm going to reopen the issue.

Hello @NicholasLYang. Thank you for your response. Could you please enable debug for you job and add this step after integration tests:
      - run: |
          cachedPath=$(pnpm store path --silent)
          echo "cached path is $cachedPath"
          [ -d "$cachedPath" ] && echo "Directory $cachedPath exists."

Hello @NicholasLYang, just a gentle ping.

I'm getting the same error Error: Cache folder paths are not retrieved for npm with cache-dependency-path =  but using this setup: (no cached-dependency-path and using npm`)
runs:
  using: 'composite'
  steps:
    - uses: actions/checkout@v3
    - uses: actions/setup-node@v3
      with:
        node-version: 18
        registry-url: https://npm.pkg.github.com/
        cache: ${{ hashFiles('**/package-lock.json') && 'npm' || null }}
    - run: npm install --ignore-scripts
      shell: bash
    - run: npm rebuild && npm run prepare --if-present
      shell: bash

Hello @eddiemonge. Could you please attach a failed build? I think you can have the same issue as this.

I was getting similar errors. Started with v3 and cache: yarn (using yarn 3), got:
Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.

https://github.com/movehq/Hub/actions/runs/5728412193
Which led me to #803 so I tried @main. (ca2d4e0cdd8c63d9ebfedc3d16d450a870caf31c) which then errored:
Cache folder paths are not retrieved for yarn with cache-dependency-path =

https://github.com/movehq/Hub/actions/runs/5728573485/job/15523437090

I'm also running into the problem of
Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved

on Cleanup.
Running on @main does not seem to do anything. Has there been any development on new ideas on this topic?

Whenever I tried pinning to v3.6.0, I got a similar but different error:
Post job cleanup.
/home/runner/setup-pnpm/node_modules/.bin/pnpm store path --silent
/home/runner/setup-pnpm/node_modules/.bin/store/v[3](https://github.com/meese-os/meeseOS/actions/runs/6292934770/job/17082829140?pr=156#step:12:3)
Error: Cache folder path is retrieved for pnpm but doesn't exist on disk: /home/runner/setup-pnpm/node_modules/.bin/store/v3

Any ideas on how to proceed from here?

Getting this after upgrading from yarn 1 to 3. Any solutions?

Fyi I had this error when using node v16 and when I changed to v18 it now works with pnpm cache!
Note the other thing I noticed is that it was failing in a workflow of mine that I actually did not run pnpm install with so potentially the issue was that there was no cache created and that is why I was getting this error 🤷♂  ... in case someone else runs into the same scenario.
Anyways, below is working for me now:
name: Test pnpm install and cache

on:
  workflow_dispatch:

jobs:
  test-pnpm-install-and-cache:
    runs-on: ${{ matrix.os }}
    strategy:
      matrix:
        os: [windows-latest, macos-latest]

    steps:
      - name: Checkout the code
        uses: actions/checkout@v3
      - name: Setup pnpm
        uses: pnpm/action-setup@v2
        with:
          version: 8
      - name: Setup Node.js
        uses: actions/setup-node@v3
        with:
          node-version: 18
          cache: 'pnpm'
      - name: Install dependencies
        run: pnpm install --frozen-lockfile
      - name: Test pnpm list
        run: pnpm list
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

Hope this helps someone!

I am running into this issue with node 18.17 + yarn 4 once a while. Any debugging I can do to help resolve this issue?

any updates on this one? (using node 18 + pnpm inside a composite action)

Post Use Node.js 18
    Post job cleanup.
    Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.

name: Workflow

on:
  push:
    branches:
      - staging

jobs:
  install_dependencies:
    runs-on: ubuntu-22.04

    steps:
      - name: Checkout
        uses: actions/checkout@v3

      - name: Install Node.js
        uses: actions/setup-node@v3
        with:
          node-version: 18

      - uses: pnpm/action-setup@v2
        name: Install pnpm
        with:
          version: 8
          run_install: false

      - name: Get pnpm store directory
        shell: bash
        run: |
          echo "STORE_PATH=$(pnpm store path --silent)" >> $GITHUB_ENV

      - uses: actions/cache@v3
        name: Setup pnpm cache
        with:
          path: ${{ env.STORE_PATH }}
          key: ${{ runner.os }}-pnpm-store-${{ hashFiles('**/pnpm-lock.yaml') }}
          restore-keys: |
            ${{ runner.os }}-pnpm-store-

      - uses: actions/cache@v3
        name: Cache node_modules
        id: cache-nodemodules
        with:
          path: node_modules
          key: ${{ runner.os }}-pnpm-store-${{ hashFiles('**/pnpm-lock.yaml') }}
          restore-keys: |
            ${{ runner.os }}-build-${{ env.cache-name }}-
            ${{ runner.os }}-build-
            ${{ runner.os }}-

      - name: Install dependencies
        if: steps.cache-nodemodules.outputs.cache-hit != 'true'
        run: pnpm install

  build:
    runs-on: ubuntu-22.04
    needs: install_dependencies
    steps:
      - uses: actions/checkout@v3
      - uses: pnpm/action-setup@v2
        with:
          version: 8
      - name: Use Node.js 18
        uses: actions/setup-node@v3
        with:
          node-version: 18.x
          cache: 'pnpm'
      - uses: actions/cache@v3
        name: Restore node_modules
        with:
          path: node_modules
          key: ${{ runner.os }}-pnpm-store-${{ hashFiles('**/pnpm-lock.yaml') }}
      - run: pnpm build

What's wrong here?

The error is related to the caching layer, not setup-node itself.
As it's a post-setup step, it should just show a warning instead of throwing an error, as this breaks actions that use multiple jobs.
This error can occur if there's an apparently valid cache entry stored for the action and the repo suffered some change after the cache was made, like a folder rename.
Workaround
Running gh cache delete -a, or manually deleting node-cache- cache entries should fix the issue.
Also, editing package-lock.json, yarn.lock or pnpm-lock.yaml by just updating some package will create a new cache key and ignore the older one.
Important
Do not try to be clever and cache node_modules. It uses symlinks/hard links to save space, but caching it can make debugging your actions a living hell, whence setup-node just don't cache it. Node will show weird errors that are hard to make sense, and the action can fail sometimes, but not always (depending on cache invalidation).
Simply configure cache and cache-dependency-path on setup-node and let it cache the global packages that it'll just work.

Workaround
Running gh cache delete -a, or manually deleting node-cache- cache entries should fix the issue.

How to do this inside an action? 🤔
gh: command not found
Does this need to be installed explicitly?

gh cache

This is the github cli. You run it locally on your machine.
cd to a local copy of the repository and use the gh command.
This specific command will interact with stored workflow caches, like the ones shown on this page. gh cache delete -a is the same thing to access this tab on the browser and click delete (for a repo you have permissions) on each cache.
You shouldn't run this from the action. If you really think clearing the cache all the time is the solution, it's much simpler to just disable the caching entirely by removing cache and cache-dependency-path from the setup-node action.

I was having this issue when upgrading from v2 to v4
What helped me was to move actions/checkout step to the top
Previously I would only do actions/checkout on a hit miss, so that I can use gh to automatically open issue. This doesn't seem to work with v4 and seemed like it worked with v2.
Here's my action with v2:
# inspired by https://ben.balter.com/2021/12/15/github-actions-website-api-change-notification/

name: Some Check

on:
  schedule:
    - cron: "0 0 * * *" # Runs at 00:00 UTC daily.
  workflow_dispatch: # for manual testing

permissions: write-all

jobs:
  check:
    runs-on: ubuntu-latest
    steps:
      # Use cURL to fetch the given URL, saving the response to `some-data.html`
      - name: Fetch data
        run: curl "https://some-url.com" -o some-data.html

      # Optionally, use `jq` to pull one or more fields from the JSON to include in the SMS message
      - name: Parse data
        id: parse_data
        run: echo '::set-output name=someDateHtml::'$(echo some-data.html)

      # Compare the response to the previous run, using a hash of the response as the cache key
      - name: Fetch Cache
        id: cache
        uses: actions/cache@v2
        with:
          path: some-data.html
          key: ${{ hashFiles('some-data.html') }}

      # If there was not a cache hit (meaning the response changed), create issue
      - uses: actions/checkout@v4 # otherwise can't use `gh` command
      - name: Open an Issue
        env:
          GH_TOKEN: ${{ github.token }}
        if: steps.cache.outputs.cache-hit != 'true'
        run: |
          echo "The some data has changed. Please review." > issue-body.txt
          gh issue create --title "some data has changed" --body-file issue-body.txt

Here's my action with v4:
name: Some Check

on:
  schedule:
    - cron: "0 0 * * *" # Runs at 00:00 UTC daily.
  workflow_dispatch: # for manual testing

permissions: write-all

jobs:
  check:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4 # otherwise can't use `gh` command

      # Fetch the data
      - name: Fetch data
        run: curl "https://some-url.com" -o some-data.html

      # Ensure the file exists and has content before proceeding
      - name: Check file existence
        run: |
          if [ ! -s some-data.html ]; then
            echo "Error: File does not exist or is empty."
            exit 1
          fi

      # Attempt to fetch cache
      - name: Fetch Cache
        id: cache
        uses: actions/cache@v4
        with:
          path: some-data.html
          key: ${{ hashFiles('some-data.html') }}

      # Conditional logic for issue creation
      - name: Open an Issue if data changed
        if: steps.cache.outputs.cache-hit != 'true'
        run: |
          echo "The some data has changed. Please review." > issue-body.txt
          gh issue create --title "some data has changed" --body-file issue-body.txt
        env:
          GH_TOKEN: ${{ github.token }}

Hope this helps someone, cheers!

Please validate my account

Our solution (TLDR): remove the .yarnrc.yml file when using pnpm package manager and cache.
We were having the exact same error with pnpm, but in our case there was a .yarnrc.yml file left at the root of the repository that we forgot to remove during the migration from yarn to pnpm. It appears that automated stuffs related to yarn were done during the setup phase that somehow brought confusion related to pnpm cache.

I'm getting this error using v4 with yarn. As someone else mentioned, can this be a warning and not an error? Pretty annoying to have to wait on an entire action to run just to have it fail on a cache cleanup task at the very end.

In my project, I forgot to add a step to run pnpm install and it caused this error. Making sure I install dependencies fixed the issues.

I'm getting this with yarn.  If I run the action in debug mode, I see during the cache restore step
##[debug]yarn's cache folder "/home/runner/.cache/yarn/v6" configured for the directory "/home/runner/work/my-repo/my-repo"

but then during the cache save I see
'/home/runner/work/my-repo/my-repo//home/runner/.cache/yarn/v6'

So, something isn't properly detecting that the path is absolute, and is inappropriately prepending the working directory.  That seems to maybe be a bug in @actions/cache?

Hi @NicholasLYang, The "Path Validation Error" occurs because the specified path for caching does not exist, so no cache is being saved. This is expected behavior when the action has nothing to restore. To reslove this issue, ensure that dependencies are installed before the cleanup step by including an additional step to install them.
- name: Install dependencies
  run: pnpm install

Adding this step to your workflow ensures that there is something to cache, which prevents the path validation error.  Attached is a screenshot of the sucessful workflow after installing the dependencies. If you have any other issues or questions, please let us know.

Hi @NicholasLYang, Just a gentle reminder regarding this issue, If you have any updates or need further assistance, Please let us know.

Hi @NicholasLYang, Just a gentle reminder regarding this issue, If you have any updates or need further assistance, Please let us know.

Hi @NicholasLYang, Due to inactivity, I'm going to close this issue for now. Please feel free to reopen this issue or create a new one if necessary. Thank you.


Found conflicts between different versions of "System.Net.Http" that could not be resolved - in Xamarin Android

Hi Guys
I am having issues with seq sing in Xamarin Android project. After adding serilog sink nuget package I get following warning in logs:
Found conflicts between different versions of "System.Net.Http" that could not be resolved.
There is no way to solve it by using binding redirects as far as I can tell.

Project:
Visual Studio 2017 15.9.7
Xamarin <IP_ADDRESS>
Serilog.Sinks.Seq 4.0.0
Targetting Android 8.1 Oreo
Repro:
Create new project using default Xamarin Android template, select empty project.
Build -> no warnings, add seq sink -> build -> warning
I have tried:

Adding app.config and remapping system.net.http to <IP_ADDRESS> in binding redirect
Adding separate system.net.http nuget package and forcing binding redirect to the newest version

Thanks!

Hi @jmalczak - it seems like this might be a spurious warning, there has historically been some confusion about how/where this occurs and whether it is correct: https://bugzilla.xamarin.com/show_bug.cgi?id=22670
Does the app still run, and log events to Seq? Thanks!

Hi @nblumhardt - the problem is that we want to treat warnings as errors and this one issue prevent us from doing that. I have seen bug that you have provided. It looks like was closed in 2017 and I am using latest version of both Visual Studio and Xamarin. App still run and send events to Seq.
Thanks

👍 makes sense. You should be able to achieve this using <NoWarn> in the CSPROJ, but I can't spot the warning code in the screenshot. Worth a try.
I have no idea how we can tackle this at the package level, but if there's some way for us to avoid it without breaking other targets I can help with the change. Zero Xamarin knowledge here, though, except for the memory of some bad experiences using early versions of the tooling :-)

I'll close this one as stale, as I still don't know of any course we could take to fix this from our side, but let me know if you still need some help with this, @jmalczak. Cheers!


not working with VC/Save

Hi,
File format look like you describe but update dosen't work.
(size is 128k instead of 256k on Virtual consol)
And data seems to be use from backup part and not for the first section part.
(Checksum is bad ?)
(I can send you a sample file)

File size of any flash RAM for the Nintendo 64 should always be 128k.
I do not imagine that 256k would be correct in any case.

And data seems to be use from backup part and not for the first section part.

Can you describe what you mean here?  How are you invoking zs.exe, e.g. with what command or batch file?  Yes, if it would help you are welcome to send me a sample file.

Hi,
I'm using virtualconsol and SaveManager to get an un-encrypted save file, obviously no warning when i'm using 128k file. (The file is padded with "0xAA" to 256k when I extract it)
ex:
"zc file -I i" give me right information.
"./zs EEP_NZSP -I i 4 0 0x04" without error
Checksum is at 0x100A as expected.

When I upload the save file to VC, game keeps the old paramaters.
I'm supecting that VC use "backup save" from 0x2000 to 0x3FFF.
When I manually change values and checksum between 0x2000 and 0x3FFF.
(The savegame is corrupt )

I'm on linux (no Mswindows @home )
file is available here pastefile 25b0d4166bf2a76bbb7cf207bf73af60

Dominique

Yes, the "backup save" from 0x2000 to 0x3FFF is what the game reverts to if it considers the blocks between 0x0000 to 0x1FFF to be invalid.  I have no idea what VirtualConsole or Save Manager are, but the game itself is designed to do that.  (Of course, if both the backup and actual saves are invalid, the file is just reset as empty/unused.)
What version of the game are you playing?  Is it NTSC USA?  What's VirtualConsole?  Does that mean you're running it on an actual Nintendo 64 or some emulator?
The only way the game will determine a save to be corrupt is if the checksum is wrong (or stored at the wrong location) or the "ZELDA3" string from 0x0024:29 isn't set.

Hi,
I'm running ZeldaMM on my Wii  (with the NARP channel).
As you said, the checksum position/value shouln'd be correct.
I'll read you source code to find the way to calculate it, and verify with a fresh savefile.

I would propose, take the Wii/VC original save file before my zs command executes any changes on that, have some backup of that, then run my zs command on it making one single minimalist change, then see if it works on VC.  If not, send me both files, and I can do a binary comparison on them to see what is being done unusually.

Hi,
I found a fix, to get the right checksum based on the 0x2000 first bytes (and not 0x4000)
I know that is quit dirty and should'nt write like that.
Obviously with my trick, the checksum is not the same but WII/VC works with it.
The generated file is 128k, instead of 256k from the WII/VC, but it works.
WII/VC add automagically extra information (padding with 0xAA)
--- a/zs_data.c
+++ b/zs_data.c
@@ -694,6 +694,7 @@ u16 fix_checksum(unsigned int section_ID)

     format = (read16(&section[0x100A]) != read16(&section[0x300A])) ? 1 : 0;
     limit = (FILE_SIZE / 2) << format;
+    limit = (FILE_SIZE / 2) << 0;

I've just attach a savefile without modification.

I've got a bottle in place of bombchu < I 'used the bottle duplication glitch )
EEP_NZSP.zip

The format assignment was put there to determine whether the ROM version in use is saving the Pictograph Box snapshots into an extra 4k of the same save slot section (making 8k total), or it is just 4k behind another backup 4k copying the same thing.
There may be some reason the VC output is making the check-sums inconsistent.  I will take a look.

Thanks very much for reporting this.
Try again please.
I see what went wrong.  The code you pinpointed had been designed to try to detect whether the save data was written by the Japanese release of Zelda Majora's Mask or not, which uses a slightly different file format.  It operated off the assumption that your usage of the utility did not fix the checksum in advance before all operations completed, because it was comparing the two potential checksum addresses (for both formats) to tell if it was one format or the other, was which indeterminate.

Thanks !
It perfectly Works with your update.


[Bug]: KDE.Kate wrong download URL

Is there an existing issue for this?

[X] I have searched the existing issues

Project Name
WinGet Automation
What happened?
Latest release of KDE.Kate has a non working download URL in the winget-pkgs manifest
https://github.com/microsoft/winget-pkgs/tree/master/manifests/k/KDE/Kate/23.04.3

Updated in: https://github.com/microsoft/winget-pkgs/pull/115670


[stdlib] prevent MutableCollections from inappropriately inheriting a Slice subscript

adds a conditional protocol extension that defines MutableCollection.MutableCollection.subscript(bounds: Range<_>) -> Slice<Self> only when SubSequence == Slice<Self>.

attempts to mark the unconditional extension method MutableCollection.subscript(bounds: Range<_>) -> Slice<Self> as unavailable

MutableCollections where SubSequence == Slice<Self> still get the expected default implementation.

adds a default implementation of MutableCollection.subscript(bounds: Range<_>) -> SubSequence, marked unavailable, in order to prevent invalid conformances from compiling when SubSequence is not Slice<Self>.

Resolves SR-14850 (and completes the fix to SR-14848).

Is there a wizard of availability annotations to help figure out what's needed in the last of these commits?

@swift-ci please smoke test

@slavapestov I'd like your opinion on availability and ABI impact of these changes.

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test macOS platform

As it is, this change is tripping up the api-digester test. I believe that's the not-breaking-things test, so an adjustment is clearly needed.

The source/abi compatibility tests aren't perfect -- they sometimes report false positives. We also know that this is technically a source breaking change, so I'd expect we'll need to add at least a couple new expected differences.
Source compat diff
--- /Users/buildnode/jenkins/workspace/swift-PR-macos-smoke-test/branch-main/buildbot_incremental/swift-macosx-x86_64/test-macosx-x86_64/api-digester/Output/stability-stdlib-source.swift.tmp.tmp/stability-stdlib-source.swift.expected	2021-07-23 13:23:30.000000000 -0700
+++ /Users/buildnode/jenkins/workspace/swift-PR-macos-smoke-test/branch-main/buildbot_incremental/swift-macosx-x86_64/test-macosx-x86_64/api-digester/Output/stability-stdlib-source.swift.tmp.tmp/changes.txt.tmp	2021-07-23 13:23:30.000000000 -0700
@@ -1,4 +1,7 @@
+Accessor MutableCollection.subscript(_:).Get() has generic signature change from <Self where Self : Swift.MutableCollection> to <Self where Self : Swift.MutableCollection, Self.SubSequence == Swift.Slice<Self>>
+Accessor MutableCollection.subscript(_:).Set() has generic signature change from <Self where Self : Swift.MutableCollection> to <Self where Self : Swift.MutableCollection, Self.SubSequence == Swift.Slice<Self>>
+Subscript MutableCollection.subscript(_:) has generic signature change from <Self where Self : Swift.MutableCollection> to <Self where Self : Swift.MutableCollection, Self.SubSequence == Swift.Slice<Self>>

These are good -- the test correctly caught that we added an extra constraint on the Slice-returning subscript.
ABI diffs
--- /Users/buildnode/jenkins/workspace/swift-PR-macos-smoke-test/branch-main/buildbot_incremental/swift-macosx-x86_64/test-macosx-x86_64/api-digester/Output/stability-stdlib-abi-with-asserts.test.tmp.tmp/stability-stdlib-abi.swift.expected.sorted	2021-07-23 13:23:31.000000000 -0700
+++ /Users/buildnode/jenkins/workspace/swift-PR-macos-smoke-test/branch-main/buildbot_incremental/swift-macosx-x86_64/test-macosx-x86_64/api-digester/Output/stability-stdlib-abi-with-asserts.test.tmp.tmp/changes.txt.tmp	2021-07-23 13:23:31.000000000 -0700
@@ -1,3 +1,4 @@
+Accessor _SmallString.subscript(_:).Modify() is a new API without @available attribute

This one is interesting -- it looks like the compiler generated an implicit _modify accessor for the smol string subscript. I did not know the compiler did that!
If true, then this is indeed an ABI break that needs to be fixed. A quick patch is to add an explicit _modify with an @_alwaysEmitIntoClient attribute.

@swift-ci please smoke test macOS platform

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test macOS platform

@swift-ci please smoke test Linux platform

@lorentey Thanks for confirming I wasn't breaking anything I shouldn't break!


APIM Notification Templates: Definition of well-formed HTML document missing

Dear Documentation team,
I was trying to update the "Developer welcome letter" notification template and kept coming accross the following error:

It took me some time, but I managed to figure out some non-obvious "rules" as to what makes up a well-formed HTML document:

All tags must have closing tags including tags such as  and
 although the shortcut
 is allowed
  is not allowed
Surprisingly, comments are allowed

Would be great if you could include this in the documentation, as well as any other rules that I have not yet stumbled across.
I write the templates in visual studio code before I copy them into the notification templates. It would be great if you could provide a linter or extension that I can use to make sure that the html is well-formed in the context of these notification templates.
Thanks

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

ID: a55c0a23-de53-df95-fcc9-70cebebf3d0c
Version Independent ID: 51f1b3fc-aa47-110b-6de9-e4fec8c5b269
Content: Configure notifications and email templates - Azure API Management
Content Source: articles/api-management/api-management-howto-configure-notifications.md
Service: api-management
GitHub Login: @dlepow
Microsoft Alias: danlep

@rsch136  - Thanks for pointing out this issue and providing detailed examples. I've captured a work item for our doc backlog to provide some specifics on "well-formed HTML document" in the context of these templates. We'll plan work in an upcoming sprint. According to our usual process, I'll now close this issue. If you'd like to continue the discussion, feel free to comment in this issue or open another.
cc/ @mikebudzynski
#please-close


[6/x][programmable transactions] Calculate effects

Adds the final bit of execution for determining the object changes and collecting the user events

Description
This replicates the work currently done by the Move adapter, but will apply to all commands. Which in the future might call for a cleanup of the TemporaryAuthorityStore
Test Plan
Not yet visible or usable

If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process.
Type of Change (Check all that apply)

[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes

I added some extra doc comments. As we are approaching the end of the programmable transaction core implementation, let me know if there are spots you think need extra documentation!


ServiceMonitor serverName filed incorrectly set by OLM

Bug Report
What did you do?
When deploying a ServiceMonitor object the serverName field should be updated to reflect the namespace in which the operator in begin deployed.
What did you expect to see?
so foir exmaple if this is the ServiceMonitor in the bundle:
apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
  labels:
    operator: volume-expander-operator
  name: volume-expander-operator-controller-manager-metrics-monitor
spec:
  endpoints:
  - bearerTokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token
    interval: 30s
    port: https
    scheme: https
    tlsConfig:
      caFile: /etc/prometheus/configmaps/serving-certs-ca-bundle/service-ca.crt
      serverName: volume-expander-operator-controller-manager-metrics.volume-expander-operator.svc
  selector:
    matchLabels:
      operator: volume-expander-operator

and the operator is being deployed to the aaabbb namespace then OLM should change this to be

apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
labels:
operator: volume-expander-operator
name: volume-expander-operator-controller-manager-metrics-monitor
spec:
endpoints:

bearerTokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token
interval: 30s
port: https
scheme: https
tlsConfig:
caFile: /etc/prometheus/configmaps/serving-certs-ca-bundle/service-ca.crt
serverName: volume-expander-operator-controller-manager-metrics.aaabbb.svc
selector:
matchLabels:
operator: volume-expander-operator

**What did you see instead? Under which circumstances?**
A clear and concise description of what you expected to happen (or insert a code snippet).

**Environment**
* operator-lifecycle-manager version:

quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:4b14ffcea52f9eb5952546634cb26bfb1d523a4dd81382021c71673fed91efa2

* Kubernetes version information:

kubectl version
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.0", GitCommit:"cb303e613a121a29364f75cc67d3d580833a7479", GitTreeState:"archive", BuildDate:"2021-07-22T00:00:00Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.3+e790d7f", GitCommit:"3a0f2c90b43e6cffd07f57b5b78dd9f083e47ee2", GitTreeState:"clean", BuildDate:"2021-12-14T02:10:38Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind:
OCP 4.9

Possible Solution
OLM should scan and fix that field, or even better just support deploying via an helm chart and let the operator packager worry about these kinds of things.
Additional context
Add any other context about the problem here.

Hi @raffaelespazzoli, thank you for opening this issue. This issue has gone undetected because most operators leveraging the ServiceMonitor object in the bundle are installed in a specific predefined namespace and do not need to update the serverName field dynamically at install-time.
This definitely feels like a valid bug and is worth continuing to triage.


Add Widget additional information link

Add a link to widget developer recipe at the end of Widget section.
I think it is import to point developer where to find information about customizing and overriding widgets.
Thanks @tiberiuichim  for the tip
https://community.plone.org/t/using-react-currency-selector/14737

@arky you need to sign the Plone Contributor Agreement in order to merge this pull request.
Learn about the Plone Contributor Agreement: http://docs.plone.org/develop/coredev/docs/contributors_agreement_explained.html

I have signed and submitted my Plone Contributor Agreement.

@ableeb has @arky proper permissions and everything is ok with his PCA?

@arky It's better to create the branch in the main repo then create the PR, if not, the actions do not run properly. Could you do that? Thanks!

@arky for next one, that small thing in docs it's not worth the effort.

Sure @sneridagh this was minor fix. Next time I'll create a branch for more significant contribution.

Hi @arky I couldn't find your Plone Contributor's Agreement in our archives and without that we can't accept your PR. Please fill out https://plone.org/foundation/contributors-agreement/agreement.pdf and send to<EMAIL_ADDRESS>Once that's in hand, we can assign the necessary permissions so that we can accept your PRs. Thank you!

@ableeb I had sent my contributor agreement on 6/26/21. I have resent to<EMAIL_ADDRESS>again. Please let me know should you need any further changes.

@ableeb I had sent my contributor agreement on 6/26/21. I have resent it to<EMAIL_ADDRESS>again. Please let me know should you need any further changes.

Please close and reopen this PR for so our robot can detect your signed contributor agreement. Thank you!

Merging then, since it's resolved and it's a single line of docs.

This needs to be backported to plone6-docs with a git cherrypick.


Sub-directories use fallback_page

Say I have "fallback_page" : "/index.html" defined in dat.json. When going to the url /content, I’d like to see my fallback_page if there isn’t an index.html file present within that directory. It’s also worth noting that the directory listing is currently displayed regardless of if the directory exists or not.
This is super useful for creating pseudo-static sites which reads content from files within sub-directories and displays it through a webapp.


StableCode Fails During Inference (stabilityai/stablecode-completion-alpha-3b-4k)

stabilityai/stablecode-completion-alpha-3b-4k fails at the assert here but converts successfully using:
python -m exporters.coreml --model=stabilityai/stablecode-completion-alpha-3b-4k exported/

It's a gpt_neox model with GPTNeoXForCausalLM architecture.
When removing the assert and re-running, the SwiftChat app is able to load and run the model, but generates gibberish.

I have the converted model currently uploading to HF but it's going to take a bit to complete.

Closing for now, feel free to reopen if appropriate!


fix cacert() to work with openssl's defaults

The existing cacert() implementation builds the single bundle of certs in
/etc/ssl/certs/ca-certifates.crt. This isn't read by default, and results in
a verification error:
r00t@9c80da3575a7:~# echo | openssl s_client -connect www.google.com:443 2>&1 | grep Verify
Verify return code: 20 (unable to get local issuer certificate)

The default path for the single cert bundle is /usr/lib/ssl/cert.pem
r00t@9c80da3575a7:~# ln -sf /etc/ssl/certs/ca-certificates.crt /usr/lib/ssl/cert.pem
r00t@9c80da3575a7:~# echo | openssl s_client -connect www.google.com:443 2>&1 | grep Verify
Verify return code: 0 (ok)

So ship that symlink as part of cacert()

@loosebazooka is the expert, wdyt?

ping @loosebazooka

Oh I assume it's a Debian thing. Lemme do a little reading but this looks fine

Yah, it's unfortunate that the default is compiled into openssl and it
seems like everybody picks a different value.
In my use cases, Ubuntu's openssl uses /usr/lib/ssl, and the indygreg
standalone python binaries that I'm bundling from rules_python use
/etc/ssl. I'm shipping another symlink for the latter when I bundle it up
for the container.
They all seem to work out of the box with the individual cert+fingerprint
symlink tree in /etc/ssl/certs
On Wed, Aug 21, 2024 at 2:56 AM Appu @.***> wrote:

Oh I assume it's a Debian thing. Lemme do a little reading but this looks
fine
—
Reply to this email directly, view it on GitHub
https://github.com/GoogleContainerTools/rules_distroless/pull/71#issuecomment-2299428347,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWXYTGNOT4M5BDZCPANYFETZSN7OBAVCNFSM6AAAAABMHWDXASVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJZGQZDQMZUG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

@thesayyn I think we have to revert this. It looks to be creating some issues downstream on various distroless containers: https://github.com/GoogleContainerTools/distroless/issues/1679, https://github.com/GoogleContainerTools/distroless/issues/1676

GoogleContainerTools/distroless#1679
I think just making the parent directory might fix this one?

    mtree.add_parents("/usr/lib/ssl", mode = "0755", time = ctx.attr.time, skip = [1])

GoogleContainerTools/distroless#1676

this one doesn't seem related to the new symlink?
% docker run --rm -it gcr.io/distroless/base-debian12:debug
/ # mv /usr/lib/ssl/cert.pem /usr/lib/ssl/oldcert.pem
/ # wget -S https://sts.nih.gov/.well-known/openid-configuration -O -
Connecting to sts.nih.gov (<IP_ADDRESS>:443)
wget: note: TLS certificate validation not implemented
wget: got bad TLS record (len:0) while expecting handshake record
wget: error getting response: Connection reset by peer

There's also SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crt set in the environment on that container ... so why would the symlink matter?
It'd be useful to know what old container it worked on to be able to bisect the breakage. My docker repository-fu isn't good enough to find old releases of the distroless base-debian12 debug image, and the image metadata setting timestamps to 1970 makes a simple timestamp sort not a viable strategy.

Either way, I think something like this should be an additional function
(exposed via explicit configuration).

At the risk of re-stating the obvious: without the symlink created by
cacerts(), SSL cert verification is broken by default.
The distroless container images that are distributed configure around this
breakage by setting an env variable:
https://github.com/GoogleContainerTools/distroless/blob/f2714a06a32d11aa3c7ad16ab2a1fe81548d0bc0/base/base.bzl#L79
An alternative to the symlink would be to document the incomplete nature of
cacerts(), and call out the need for the environment variable to be set
on every container to get SSL to work properly?

I don't mind including this -- but I have to ensure distroless works
first and always (as my primary concern) -- where we only need to be debian
compliant.

I would hope that "debian compliant" means having openssl or curl .debs
that do SSL securely.
On Mon, Sep 23, 2024 at 11:28 PM Appu @.***> wrote:

Either way, I think something like this should be an additional function
(exposed via explicit configuration).
I don't mind including this -- but I have to ensure distroless works first
and always (as my primary concern) -- where we only need to be debian
compliant.
—
Reply to this email directly, view it on GitHub
https://github.com/GoogleContainerTools/rules_distroless/pull/71#issuecomment-2368456390,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWXYTGLZ4XNDBQIHTW4NKCTZYAQSNAVCNFSM6AAAAABMHWDXASVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRYGQ2TMMZZGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Yeah those are fair clarifications. The intent is not that this feature was wrong, but that we don't know what's wrong yet and we need to revert while we figure it out.


Mod user's wires look weird when in a session with multiple users

Not sure if there's a good way to fix this, I may have to do something funky

Fixed by https://github.com/Nytra/ResoniteLeftHandedProtoFlux/commit/6ad1a9a9ccb4b60cdd1c09277779e59a5ea937dd


I can't send the ada anywhere else.

I'm trying to send the ada I have, but I can't choose.If you select another coin, the send is displayed and you can send it, but only the ada is not selected.
Please let me know what the problem is.
"ada" doesn't show the send button.
Swap is normal with the ada you own, but if you select ada, the send button should appear below, but there is no response.Help me.
my wallet address
addr1qxajmmrps5w3hen0wzfnh4z5rdc40apmyhzgqq65uqvjyw9anp7trcxu7ns2c8pll5nfyyyfcuqarkskcd7mxvge2zys3zptkt

Having the same issue - please help

If you select another coin, the send is displayed and you can send it, but only the ada is not selected. Please let me know what the problem is. "ada" doesn't show the send button.

Can you send ADA with the big yellow “Send” button next to “Receive” in the upper row?
In contrast to the other assets, it just does not seem to have a detail view (because it is just the main currency of the network?).