BUG: Fix BLEU calculation

Mirroring https://github.com/d2l-ai/d2l-en/pull/1981.
Question: I'm not sure why d2l-zh has no saved bleu function in the d2l package even though we have added #@save in the notebook. Any ideas @goldmermaid? Hence I only fixed the notebook code for this, but in the English version the libraries were also updated.

Job d2l-zh/PR-1032/1 is complete.
Check the results at http://preview.d2l.ai/d2l-zh/PR-1032/

Great question. d2l-zh's CI is fixed to d2l==0.17.0.post0 (https://github.com/d2l-ai/d2l-zh/blob/master/static/build.yml), would that be the potential causes @AnirudhDagar ?

d2l-zh's CI is fixed to d2l==0.17.0.post0 (https://github.com/d2l-ai/d2l-zh/blob/master/static/build.yml), would that be the potential causes @AnirudhDagar ?

Yes, that is true, but when adding the function and saving it with #@save in that notebook, did we not run d2lbook build lib? I'm confused because obviously, we are not installing d2l from the source here. But then what's the purpose of those library .py files. They are not even used to build the d2l API section in the book.
I'm probably missing something and it seems like a temporary thing, maybe @astonzhang knows better?
Seems like the library was update here for chapter RNN but for Modern RNN nobody updated the lib, even thought the notebooks were added here.

d2l-zh's CI is fixed to d2l==0.17.0.post0 (https://github.com/d2l-ai/d2l-zh/blob/master/static/build.yml), would that be the potential causes @AnirudhDagar ?

Yes, that is true, but when adding the function and saving it with #@save in that notebook, did we not run d2lbook build lib? I'm confused because obviously, we are not installing d2l from the source here. But then what's the purpose of those library .py files. They are not even used to build the d2l API section in the book.
I'm probably missing something and it seems like a temporary thing, maybe @astonzhang knows better? Seems like the library was update here for chapter RNN but for Modern RNN nobody updated the lib, even thought the notebooks were added here.

I may add them back later.


Occurs when the model is loaded for the first time. orbit will not work

chrome 100
windows 11
react 17

Could you post your scene URL?

Could not reproduce, closing. Feel free to reopen when you have a reproducible example.


[WIP] /features/: Redesign of the features landing page.

This is a redesign of the features landing page from the current
style that just includes the new sections in a grid format.
Warning: This has a bunch of unfilled descriptions. Do NOT deploy
with them in place.

Automated message from Dropbox CLA bot
@brockwhittaker, it looks like you've already signed the Dropbox CLA. Thanks!

This looks good modulo the text needing work and the small linter error (we should add this to the relevant linter exclude list until #5863 is resolved).  @rishig do you have time to do a pass on the text or should I take that project?

I can do a pass, though we should discuss a bit first.

This has a few updates. The linter is tripping over the webpack output however now and giving hundreds of errors.

updated.

The image looks kind of strange on screens with weird dimensions (about 12 x 8 inches but rotated 90 degrees in tablet mode), screnshot attached

Again in the rotated-window view, the keyboard shortcuts stuff also goes off the left side of the page without giving me a scrollbar at the bottom/the ability to scroll left.

I may need to do some responsive polishing since I added these new
features. Will do. Thanks James!
On Fri, Jul 28, 2017 at 13:02 James Rowan<EMAIL_ADDRESS>wrote:

Again in the rotated-window view, the keyboard shortcuts stuff also goes
off the left side of the page without giving me a scrollbar at the
bottom/the ability to scroll left.
[image: screenshot 3]
https://user-images.githubusercontent.com/5571464/28734259-15624d12-73ae-11e7-8f93-73621b969c75.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zulip/zulip/pull/5864#issuecomment-318748956, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJ19960IoMphDNmzFNeGFcR27zNgunsKks5sSj5sgaJpZM4OdFZW
.

@brockwhittaker can you fix the lint errors?

I went ahead and fixed the lint issue, edited the copy some, and merged this.  Thanks @brockwhittaker!  @rishig I think we should do another pass on the content (we need a better screenshot is probably the top priority, etc.), but this is clearly better than we had before and I'd like to make it easy to improve iteratively from here.
@brockwhittaker let's chat tomorrow about next steps for this.


Player not creating the proper game.data and game.js file

I am done publishining a game as a html 5 game using
python C:\Users\pc\love.js\emscripten\tools\file_packager.py game.data --preload C:\Users\pc\Desktop\Example_Game_1\ExampleGame.exe@/ --js-output=game.js
but for my second try, it doesn't output the correct file. What is worng?

You should be packaging either your game folder or the .love file, not the
.exe file.
On Monday, 26 September 2016, bonez001<EMAIL_ADDRESS>wrote:

I am done publishining a game as a html 5 game using
python C:\Users\pc\love.js\emscripten\tools\file_packager.py game.data
--preload C:\Users\pc\Desktop\Example_Game_1\ExampleGame.exe@/
--js-output=game.js
but for my second try, it doesn't output the correct file. What is worng?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/TannerRogalsky/love.js/issues/40, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAn-U0lQgbexFZWaNUcxArkyNtyijcunks5qt59WgaJpZM4KGXpK
.

Thanks for the reply.  I tried to do it but it outputs files that hvae very little data 10-500 kb. When I put the game.data and game.js to the debug folder, it always outputs the sound and the screen of one previous game. I dunno what is wrong. Thank you.

I type this one
python C:\Users\pc\love.js\emscripten\tools\file_packager.py game.data --preload C:\Users\pc\game_cards@/ --js-output=game.js.
I dunno what is wrong. Maybe it has something to do with the conf.lua of previous game? I will try it on other pc.

That looks right to me. What is the structure of the game_cards directory?

Hello. I made it again. I dunoo what is wrong last time.


Maintenance: add biome to project (logger)

Summary
With #2791 being merged, we can now migrate the packages/logger workspace to use Biome.
As part of the migration I will fix any issue/inconsistency that arises. I'll do my best to minimize changes and leave the logic untouched.
Why is this needed?
So that we can gradually replace eslint, prettier, and all their dependencies with a single one, @biomejs/biome.
Which area does this relate to?
Other
Solution
No response
Acknowledgment

[X] This request meets Powertools for AWS Lambda (TypeScript) Tenets
[ ] Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers
Please react with 👍 and your use case to help us understand customer demand.

@daschaa - could you pls leave a comment here so I can assign the issue? thx

Can you assign this issue to me? ❤


[BUG] "My mags" link missing when inside of a thread's comments page

Enable "Add subs to navbar"
Navigate inside a thread

Resolved by 628a114bcebdd0ebc42614e172dd3057b7d115e7


Traducción

wow but why

wow but why

There are some pull requests that I'm like "so right".

There are some pull requests that I'm like "so right".

Okay boomer

Okay boomer

After what I've seen, I don't want to live anymore

After what I've seen, I don't want to live anymore

Its for his spanish brothers prob

Its for his spanish brothers prob

lmao

lmao


Bug 1727042: feat(operatorstatus): report packageserver as upgradeable

The PR that added Upgradeable for olm and catalog missed packageserver.

/retest

/lgtm

/lgtm cancel
Didn't know that would actually add the label :)

/retest


FAILED_TO_LOAD_NATIVE_LIBRARY for Solaris 11 Sparc server

I have an error while running Apache Spark on Solaris 11 sparc server, error caused by :
org.xerial.snappy.SnappyError: [FAILED_TO_LOAD_NATIVE_LIBRARY] no native library is found for os.name=SunOS and os.arch=sparcv9

It seems current version only support SunOS(solaris) 32-bit  sparc:
"org/xerial/snappy/native/SunOS/sparc/libsnappyjava.so;osname=sunos;processor=sparc"
But not support for 64-bit sparcv9 system. Please add this support, thanks.

@evan912 We don't have portable way to build Solaris library (e.g., using a cross compiler, etc.) If you have a Soralis 11 with 64-bit spark, please build the native library with make native test and send a PR.

Thanks @xerial , I will try to build with solaris 11 64-bit sparc. Current solution for running Apache Spark is to change to other Compressor in configuration temporarily.

@evan912  I have a similar problem,I want to run Apache spark on Linux-sw, error caused by
org.xerial.snappy.SnappyError: [FAILED_TO_LOAD_NATIVE_LIBRARY] no native library is found for os.name=Linux and os.arch=sw
ok, I would like to ask you, how did you modify it, and what modifications have you made? thanks!
@xerial hi, Do you have some specific implementations or ideas? I want snappy-java to support Linux-sw. thanks!

@amateur-RD   You can change setting of spark.io.compression.codec to lzf.  The default setting of Spark is using snappy as compressor, but it not supported some platform.

Thank you very much! @evan912 It has been successfully modified and running successfully. thanks!

Added pure-java snappy implementation in <IP_ADDRESS>. I think it will support Sparc as well.


Change the picker text style

Is there way to change the picker container text styles like change the text color and size etc.?

Hey @hasithaWalpola , please see https://github.com/mmazzarolo/react-native-modal-datetime-picker/issues/366

Hey @mmazzarolo  not the button text color, I need to change the picker container text color, Is there any solution for that?

AFAIK it's not possible, because they're native components. You should head to https://github.com/react-native-community/datetimepicker for more info


add 0.58.5 and 0.58.6 pre/post

Propagates the pre/post hooks that already existed for 0.58.4 for 0.58.5 and 0.58.6.
Also fixes the dependency issue mentioned in facebook/react-native#23390.

👍 +1 We have been waiting for a month for my fix to reach a production version. Help us @orta, you're our only hope!

Oh, damn, I missed this!


M3-1658

Purpose

https://github.com/linode/manager/pull/4083

Coverage decreased (-0.02%) to 28.885% when pulling 57e4930cf52d0392a6b5114c34235afb1f3bd2c6 on rjstires:M3-1658 into 69c46e82c104d2f69807c15723da0d7d07a847ba on linode:develop.


[MM-35138] Avoid autofill on apps forms

Summary
When a secret field (type=password) field is used in a form, the browser treats the whole form as a login form, and tries to autofill the credentials for the current site into the form fields. This PR makes it so the apps form does not allow for autofill.
Ticket Link
Fixes https://mattermost.atlassian.net/browse/MM-35138

@mickmister In which release should this go?

@mickmister In which release should this go?

@hanzei I'd say it can wait for the next cloud release. @DHaussermann What are your thoughts on this?
Should this fix also be applied to interactive dialogs?

Cherry pick is scheduled.

/cherry-pick cloud

Cherry pick is scheduled.


amd-llama-135M

https://huggingface.co/amd/AMD-Llama-135m
Fully open source with opensource licence and open source data set

I am one of the contributors for the Nexa SDK, and it supports amd-llama-135M.
If you want to quickly try the model, install the SDK from here.
Then, simply run nexa run AMD-Llama-135m:fp16
You can also pull and run gguf version of this model directly from HuggingFace with nexa run -hf QuantFactory/AMD-Llama-135m-GGUF.


Grammatical mistake in libuv documentation on page 8

On page no. 8, in section 3.1.3 File I/O, last line says "libuv currently uses a global thread pool on which all loops can queue work on". According to me it should be "libuv currently uses a global thread pool on which all loops queue can work on."

I believe the original phrasing is correct. Queue in that sentence is a verb not a noun. The loops are queuing work on different thread pools.

@crazymerlyn is correct, though the original phrasing could be improved to
"libuv currently uses a global thread pool on which all loops can queue work on."

Would someone like to open a PR dropping the trailing "on"?

I'm... wait for it... on it! #2010


Error: lookup thenaritiv.lcl.host: no such host

Are there any additional details you would like to share?

Command: anchor lcl
Executable: C:\Program Files\Anchor CLI\anchor.exe
Version: 0.1.6 (windows/amd64) Commit: 3d6f32576ae7aaf17172ec968bb44012aa0d4753 BuildDate: 2024-10-30T16:24:30Z
Arguments: []
Flags: []
Timestamp: 2024-11-05T22:59:32.6464627Z
Stdout:

# Signin to Anchor.dev `anchor auth signin`
    | Please sign up or sign in with your Anchor account.
    |
    | Once authenticated, we can provision your personalized Anchor resources to
    | power HTTPS in your local development environment.
    - Copied your user code LHPW-CTLZ to your clipboard.
    - Opened https://anchor.dev/users/sign_in/cli?signup_src=lclhost in your browser.
    - Signed in as<EMAIL_ADDRESS>| Let's set up fast and totally free lcl.host HTTPS!

# Setup lcl.host HTTPS Local Development Environment `anchor lcl`
    | We'll set you up to use HTTPS locally in your browsers and other programs.

# Audit lcl.host HTTPS Local Development Environment `anchor lcl audit`
    | We'll compare your local development CA certificates from Anchor and your local trust stores.
    - Compared local and expected CA certificates: need to install 2 missing certificates.

# Initial System Configuration for lcl.host Local HTTPS Development `anchor lcl bootstrap`
    | We'll configure your browsers and OS to trust your local development certificates.
    - Checked diagnostic service on Anchor.dev: need to provision service.
    - Entered hi-moraar222.lcl.host domain for lcl.host diagnostic certificate.
    - Resolved hi-moraar222.lcl.host domain: failed!
    | The entered domain name is either invalid or cannot be resolved from
    | your machine, possibly due to rebinding protection on your DNS server.
    | Learn more here: https://lcl.host/dns-rebinding

# Setup lcl.host Application `anchor lcl setup`
    | We'll integrate your application and system for HTTPS local development.
    - Using moraar222, the only available organization. You can also use `--org moraar222`.
    - Using localhost, the only available realm. You can also use `--realm localhost`.
    - No services found, so we'll create one.
    - Scanned current directory.
    - Entered javascript application server type.
    - Entered thenaritiv application name.
    - Entered thenaritiv.lcl.host domain for local application development.
    - Resolved thenaritiv.lcl.host domain: failed!
    | The entered domain name is either invalid or cannot be resolved from
    | your machine, possibly due to rebinding protection on your DNS server.
    | Learn more here: https://lcl.host/dns-rebinding

Sorry to hear you are having issues here.
Failing to resolve lcl.host domains is usually caused by DNS rebinding protection. You should be able to find more information on how to work around that here: https://lcl.host/dns-rebinding
If that doesn't get you what you need or you have other questions, please let us know.


This commit performs minor maintenance and a bug fix

updating minSDK to 24
updating gradle
updating AGP
removing overidesLibrary
DragAndDropRichContentReceiverFragment is marked as requiresApi 31

@yrezgui I've reverted the minSDK update and fixed the build. Turns out AGP changed behavior and the problem was in our manifest.  Please re-review.


fix: Remove deleted segments from ingestDataCache

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Cleans up segments from ingestDataCache when dataSegmentDelete is recieved.

What is the current behavior? (You can also link to an open issue here)
The cached ingest data for a segment remains after a segment is deleted from the NRCS.

What is the new behavior (if this is a feature change)?
The ingest data will be cleaned up.

Status

[X] Code documentation for the relevant parts in the code have been added/updated by the PR author
[X] The functionality has been tested by the PR author
[ ] The functionality has been tested by NRK

I'm not sure that is better, in handleRemovedSegment it would only make sense to do this operation around this line, and it feels like it would be conditional on this statement being true? https://github.com/nrkno/tv-automation-server-core/blob/9f350055865ffd27ebcc6ecda69860cf4bc605c8/meteor/server/api/ingest/rundownInput.ts#L1048
So it would make sense to bundle removing cached data in with removing the segment itself? Potentially it would be better to remove to afterRemoveSegments?


Integrate development workflow with Prettier

I think integrating Prettier to the repository (particularly to the devDependencies in package.json) will be useful, because:

Contributors who use "Format on save" in their IDE (in my case, Visual Studio Code) will be able to "delegate" the formatting concerns to the machine.
In case if a contributor's IDE is not integrated with Prettier, then we can have a GitHub Actions as a "guard". We can do so with prettier --check (--check flag docs). We will also provide a script, such as below, so that if the GitHub Action fails, they can run this script (so they don't have to update the files manually):

{
  "scripts": {
    "format": "prettier --write src"
  }
}

This will enforce a soft consistency on code formatting for all contributors. I usually use this as my default config, but I'm open for changes:
{
  "trailingComma": "none",
  "printWidth": 80,
  "tabWidth": 2,
  "semi": true,
  "singleQuote": true
}

Possible tasks

[ ] Arrive at a decision on which Prettier rules we want to use
[ ] Add Prettier
[ ] Add Prettier script to package.json
[ ] Format all files under src
[ ] [Optional] Add GitHub action for formatting check

Nice addition for consistencies, I think prettier on github actions would be good.
Regarding rules, any guidelines or standard? Usually I look for GoogleStandard
But yours rules seems same "style" with me too.

I assigned this to you @imballinst , maybe you could start "claimed" with draft PR

Regarding rules, any guidelines or standard? Usually I look for GoogleStandard

@ans-4175 yes, that seems like a very comprehensive guide. For React codebases, I think it's a bit more lenient. Some React codebases use all lowercase for files/folders, e.g. Chakra UI https://github.com/chakra-ui/chakra-ui/tree/main/packages/accordion/src, but PascalCase in Material UI https://github.com/mui-org/material-ui/tree/master/packages/mui-material/src/Accordion, so I don't have a strong opinion about it.


Different behavior between Firefox and Chrome

Describe the bug
Different behavior between firefox and chrome. Setting the height to a fixed value solves the issue with firefox but I can't really do it. Using Angular 7

Software
Version(s)

SimpleBar
4.0.0

Browser
firefox

npm/Yarn
npm

Operating System
any

You would need to provide an example because this can be happening cause of your CSS code.
Obviously we have tested the plugin in both Chrome and Firefox and they behave the same on our examples page.

Closing this as it's pretty old. Please re-open a new issue related to the latest version if needed! Thanks.


TypeError: super() takes at least 1 argument (0 given)

Hi jarekwg,
When i try to follow the steps test the code encounter this issue, I am using python 2.7:
Can you help me take a look?
In [7]: scheduler.add_jobstore(DjangoJobStore(), 'djangojobstore')
TypeError Traceback (most recent call last)
in ()
----> 1 scheduler.add_jobstore(DjangoJobStore(), 'djangojobstore')
/home/sunjiali/workspace1/Timer/Timer/django_apscheduler/jobstores.pyc in init(self, pickle_protocol)
17
18 def init(self, pickle_protocol=pickle.HIGHEST_PROTOCOL):
---> 19 super().init()
20 self.pickle_protocol = pickle_protocol
21
TypeError: super() takes at least 1 argument (0 given)
In [8]:

Hi sunjiali, are you running on Python 2?
This repo is currently python 3 only.
I'm happy to merge PRs that add python2 compatibility.
In this case all that's missing is arguments to the super() call:
super() -> super(classname, self)

Hi, jarekwg
I just changed super().init()-> super(DjangoJobStore,self).init() still have error.
In [14]: scheduler.add_jobstore(DjangoJobStore(), 'djangojobstore')
TypeError                                 Traceback (most recent call last)
 in ()
----> 1 scheduler.add_jobstore(DjangoJobStore(), 'djangojobstore')
/home/sunjiali/workspace1/Timer/Timer/django_apscheduler/jobstores.pyc in init(self, pickle_protocol)
17     def init(self, pickle_protocol=pickle.HIGHEST_PROTOCOL):
18         super(DjangoJobStore,self).init()
---> 19         self.pickle_protocol = pickle_protocol
20
21     def lookup_job(self, job_id):
TypeError: super() takes at least 1 argument (0 given)
In [15]:
Am I missing something?

Jarekwg,
Many thanks for your qucik response. It' working now.


50% of loaded map in fullscreenmode

Hi!
In fullscreen mode all time I have only 50% loaded maps

Leaflet.fullscreen 1.5.1
Leaflet 1.5.1

Have anyone same error?

In mobile it also show not all map:

I see the same issue. This plugin does not seem to work very well.

yes, it doesn't load all the additional tiles automagically.

this now seems browser specific to me. there's a problem in safari, but not in firefox. haven't yet tried others.


Start async request for UnaryStream endpoints

This is to fix https://github.com/grpc/grpc/issues/9581.
I'll admit I don't know much about the inner workings of this code, so there's a very large chance that I did something wrong. But this code change is sufficient to initiate the underlying http request as soon as the the UnaryStreamMultiCallable is called.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

I signed it!

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

As per #9581, async requests for UnaryStream endpoints are already working correctly. This PR doesn't fix anything, and indeed creates unintended side effects.


Fix error handling in SSL_new

Prevent a crash in SSL_free when refcount underflows

1.1.0 needs a new PR
1.0.2 is not affected

Err... 1.1.0 is OK, and does not need any patch.

merged to master, thanks!


Separate UI from service layer

I've had a fork on the go (samscam/ios_google_places_autocomplete) for a while where I've done quite a bit of work on it. Using it in production on Knocker.
I'll clean up what I've done and submit a bunch of pull requests for you for the smaller things, but the big one is that I needed to separate out the UI from the service layer so it can be used in programatic contexts. I've tried to do it in as non-breaking a way I could but would love to go a bit deeper. Would you be game for that?

Thanks for taking the time to think about contributing this back, and yes this sounds entirely sensible.  I'm sure there are others with a similar use case.


hashCode fails in DDC for frozen JS objects

With dart 2.2.0 and DDC, a JS object which has had Object.freeze() called upon it in JS will cause the following error: Uncaught TypeError: Cannot add property Symbol(_identityHashCode), object is not extensible. It will return 0 in dart2js. A set of files for minimal repro follows:
main.dart:
@JS()
library foo;

import 'package:js/js.dart';

@JS()
@anonymous
class Foo {}

@JS()
abstract class Fooinator {
  external static Foo fooFactory();
}

void main() {
  var foo = Fooinator.fooFactory();
  print(foo.hashCode);
}

foo.js:
var Foo = function() {
    return Object.freeze({});
};

var Fooinator = {
    fooFactory: function fooFactory() {
        return new Foo();
    },
};

index.html:
<!DOCTYPE html>

    <title>Foo</title>

I can't imagine this is something that is easy to change, as DDC (and even Dart2JS, under some circumstances) relies on being able to modify itself in order to implement some semantics (for example, this is how Expando works on platforms without WeakMap).
/cc @jmesserly, tho.

This is a question of how Dart Object members (toString, ==, hashCode, runtimeType, noSuchMethod) should work for non-Dart JS objects (e.g. here's the issue for toString: https://github.com/dart-lang/sdk/issues/35951). For hashCode, dart2js defines hashCode as 0 for JS interop objects. Needless to say, this will make these objects very slow if many of them are used as keys in a HashMap. DDC uses the normal identityHashCode behavior of Dart objects.
dart2js does have a similar bug, but it shows up differently. If you call identityHashCode(foo) you get a different answer each time. dart2js and DDC use almost identical code here, both storing a property on foo (DDC uses a JS Symbol, dart2js uses "$identityHash"). The reason it fails in DDC and not in dart2js is because DDC uses "strict mode" and dart2js does not (more info). But both of them fail to set the property.
WeakMap might be a better approach here. But we'll need some performance testing, because it might have an adverse effects on identityHashCode. Perhaps we can implement it only for get hashCode on JS interop objects, and leave identityHashCode failing on these objects. Not sure.

Just in case it provides useful context, in our particular case we're running into it as a result of using the collection package, which uses hashCode to check equality. If we happen to have a map in which a value is one of these frozen objects, we get a failure in DDC where we don't in dart2js.

Perhaps we can implement it only for get hashCode on JS interop objects, and leave identityHashCode failing on these objects.

I think that would be fine to this case; I don't believe we need identityHashCode for anything.


Persist Login

If I login with OneGraph, the auth token should be stored in localstorage so that if I refresh the page, I don't have to login again.

Made some progress. Looks like it's persisting, I just need to check if they're logged in already.
Posted a question on Spectrum: https://spectrum.chat/onegraph?tab=posts

This is basically done.
TODOs

[ ] Respond to OneGraph folks
[ ] Design loading screen
[ ] Implement loading screen


#1 - refactoring .goreleaser.yml Slack message

The changes will be included in a future PR with the complete documentation.


Mistake in "Add Editable table" page under "Step 5: Set up edit and cancel options" on the 6th point. 2369466

[in "Add Editable table" page under "Step 5: Set up edit and cancel options" on the 6th point.
For Cancel Icon, "Visibility" is set to "galleryDisplayMode = DisplayMode.Disabled".
Cancel icon should be visible when Gallery is editable but here we are saying it should be visible when Gallery Display mode is disabled. Hope this is a mistake.]

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

ID: a5761783-eeb8-2a47-bd89-7add589cf4b2
Version Independent ID: 3f1a4081-70ff-83d9-4f58-87721272986c
Content: Add editable tables in canvas apps - Power Apps
Content Source: powerapps-docs/maker/canvas-apps/add-editable-tables.md
Service: powerapps
Sub-service: canvas-maker
GitHub Login: @denisem-msft
Microsoft Alias: denisem

Thank you for reaching out. Documentation has been fixed and the change will be visible soon.


[Nightly] Strange Menu Display Corruption

So this happens every now and then. It comes and goes by itself.

Weird, I've never seen this in Grabber, though I saw it happen in Firefox a few times 🤔
Do you use any particular Windows theme?
Or any special Grabber theme? (Options > Interface > Theme)
The randomness makes me feel it's more likely a bug in Qt/Windows rather than Grabber itself (especially since the way this menu is created is the "official" one).
How often would you say it occurs?

I don't use any themes whatsoever for grabber nor windows.
I think its more or less an issue due to GPU state change. As it happens when I am rendering videos in some video editor (filmora/da vinci) or have a game paused in background.

No it is an old bug, I guess started from v7.


Opening empty file error dialog is empty

Hint: Dialog#showDialog called with wrong arguments.

Closed via #1303


KA-547 Use notifier to notify about successful run of service

I refactored configuration and fixed exceptions.


In search view, most recent should be on right, oldest on left.

(reverse current)

Fixed in 1dac982


scload("myData.json") returns null

I was trying to load some JSON-Data from a file. That didnt work because scload kept returning null.
Then i tried replicating the situation in the API-Reference: I made a file called myData.json with the example JSON data for scload in it in the plugins folder, made a new script in the same folder and put the following code in it:
var myData = scload("myData.json");
console.log(myData)

And yeah, it still logs [scriptcrafdt] null in the console. w h y  t h o

// Sidequestion: Can you log stuff to the console without the [scriptcraft] in front?

// Sideanswer: try  /js server.consoleSender.sendMessage("something")

Also scload with a relative path will start looking in the server's root directory, e.g. scload("ops.json") should return something. Try using the full path to your JSON file.


Add auto backport functionality for SQL

Description
Adds auto-backporting functionality for SQL plugin
Issues Resolved
#310
Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[x] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #445 (c27e55c) into main (8ad144e) will increase coverage by 3.40%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main     #445      +/-   ##
============================================
+ Coverage     96.51%   99.92%   +3.40%
  Complexity     2698     2698
============================================
  Files           267      257      -10
  Lines          7149     6491     -658
  Branches        520      402     -118
============================================
- Hits           6900     6486     -414
+ Misses          196        5     -191
+ Partials         53        0      -53

Flag
Coverage Δ

query-workbench
?

sql-engine
99.92% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

workbench/public/components/SQLPage/SQLPage.tsx

...ublic/components/QueryResults/QueryResultsBody.tsx

workbench/public/components/Main/main.tsx

...h/public/components/QueryLanguageSwitch/Switch.tsx

...ch/public/components/QueryResults/QueryResults.tsx

workbench/public/application.tsx

workbench/public/components/app.tsx

workbench/public/components/PPLPage/PPLPage.tsx

workbench/public/components/Header/Header.tsx

workbench/public/utils/PanelWrapper.tsx

Continue to review full report at Codecov.

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

Hi @davidcui1225 , this is an old version of the backport, can you please update it and also add auto delete workflow. The details are in issue #310 .


Removed extra square bracket at top.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

biztalk/core/delimiter-preservation-and-suppression.md
:white_check_mark:Succeeded
View

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


Release 0.13

What's up?
I think we should release this — it's been a while, we have some great PRs.
Call for any changelog entries! @aljazerzen et al! :)
I'll try and release soon. We still haven't sorted out the PyPI issues — and have no responses to our questions.

I see that I'm now late to read this comment :D


Different error message than expected

While using your plugin, I noticed that two error messages pop up when I choose a commit message that does not respect the "conventional commit" standard.
These messages are not what I expected, because I was looking for a message like Commit message does not meet Conventional Commit standards....
What I got instead are the two messages below:
.git/hooks/commit-msg: line 17: unexpected EOF while looking for matching `''
.git/hooks/commit-msg: line 19: syntax error: unexpected end of file

The commit message I used was "add histogram for flow analysis". When I used it, the plugin correctly blocked me from committing, and when I added "feat:" in front of it, the commit was rightly made.

My .git/hooks/commit-msg looks like this
#!/usr/bin/env bash

# Create a regex for a conventional commit.
conventional_commit_regex="^(build|chore|ci|docs|feat|fix|perf|refactor|revert|style|test)(\([a-z \-]+\))?!?: .+$"

# Get the commit message (the parameter we're given is just the path to the
# temporary file which holds the message).
commit_message=$(cat "$1")

# Check the message, if we match, all good baby.
if [[ "$commit_message" =~ $conventional_commit_regex ]]; then
   echo -e '\e[32mCommit message meets Conventional Commit standards...\e[0m'
   exit 0
fi

# Uh-oh, this is not a conventional commit, show an example and link to the spec.
echo -e '\e[31mThe commit message does not meet the Conventional Commit standard\e[0m\nAn example of a valid message is: \n  feat(login): add the \'remember me\' button\nMore details at: https://www.conventionalcommits.org/en/v1.0.0/#summary'
exit 1

The sbt setting keys that concern the plugin are
lazy val startupTransition: State => State = { s: State =>
  "conventionalCommits" :: s
}

lazy val root = project
  .in(file("."))
  .settings(
      Global / onLoad := {
          startupTransition compose (Global / onLoad).value
      }
  )

I hope I have not forgotten anything!

:tada: This issue has been resolved in version 2.2.2 :tada:
The release is available on:

2.2.2
GitHub release

Your semantic-release bot :package::rocket:


Add stress test for EventHubBufferedProducer and update options for existing test

Description

Add stress test for EventHubBufferedProducer
Add more logs for EventProcessorWithOptions as reference to long running test
Update scenario options and default values
Move stress test log output to fileshares (working on evaluate SDK info log size, can print info log to console after tune SDK logs)
Upgrde addons to 0.2.0
Enable sdk client metrics
Add checkstyle and spotbugs check

All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

@conniey since @liukun-msft's earlier change to the SDK to use debug logs over info logs in some places, I haven't seen any notable data ingestion costs from the java stress tests.

@conniey @benbp yes, I changed the logs to info level and output them to fileshare, so it won't create much logs on container.
But when I enable the debug level log, I do see lots of applicationinsights logs for EventHubBufferProducer test. (I don
t see massive logs in other tests, such as Processor or Sender). I'll take some time to check the reason, it might be some applicationinsights configuration in SDK itself.

But when I enable the debug level log, I do see lots of applicationinsights logs for EventHubBufferProducer test. (I don t see massive logs in other tests, such as Processor or Sender). I'll take some time to check the reason, it might be some applicationinsights configuration in SDK itself.

Ah yes, sorry I had forgotten that you had changed the log output source entirely, not just that the logs were less verbose than before.


redirect to welcome from base and /multicloud

Signed-off-by: Will Kutler<EMAIL_ADDRESS>needed now that header charts have been removed

Would it be a good to add some quick tests to check the URL in the welcome page tests to make sure these redirects are working or is that overkill?

sure, i'll add one


WEB-78: Backend cleanup

Changes informed by the most-recent use of this boilerplate.
Note
The FE will need to be updated to handle the new API endpoint(s), but the relevant code has not yet been merged into master.

Updates look good :)
I know there was something else @gyanesh-mishra wanted to see cleaned up in the model, but I'm not sure what it was. Something about simplifying the code there? Maybe that's a different ticket, or is it pretty small?


Resolve warning about undefined behavior

This bug is very similar to another issue I reported, that was fixed
in patch 7.4.1819.
The error message is:
term.c:2877:2: warning: embedding a directive within macro arguments has undefined behavior [-Wembedded-directive]
\#if defined(FEAT_VTP) && defined(FEAT_TERMGUICOLORS)
 ^
1 warning generated.

The issue is caused because sprintf() is implemented as a macro on some
systems.
Therefore, this sprintf() call has its parameters conditionally modified
by the preprocessor, and embedding a preprocessor directive within macro
arguments causes undefined behavior.
My proposed fix would be to move the preprocessor check outside the call
to sprintf().

Codecov Report

Merging #2946 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #2946      +/-   ##
==========================================
+ Coverage   75.73%   75.74%   +<.01%
==========================================
  Files          92       92
  Lines      135077   135077
==========================================
+ Hits       102303   102311       +8
+ Misses      32774    32766       -8

Impacted Files
Coverage Δ

src/term.c
59.72% <100%> (+0.15%)
:arrow_up:

src/os_unix.c
54.35% <0%> (-0.19%)
:arrow_down:

src/if_xcmdsrv.c
84.17% <0%> (-0.18%)
:arrow_down:

src/gui.c
49.3% <0%> (ø)
:arrow_up:

src/channel.c
83.11% <0%> (+0.03%)
:arrow_up:

src/ex_cmds2.c
80.29% <0%> (+0.09%)
:arrow_up:

src/gui_gtk_x11.c
48.03% <0%> (+0.09%)
:arrow_up:

src/message.c
74.83% <0%> (+0.24%)
:arrow_up:

Continue to review full report at Codecov.

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

isn't that fixed by d315cf551f1d15609c4d7cf724 ?

Yes, I just need to close this merge request.
It was created before @brammool created https://github.com/vim/vim/commit/d315cf551f1d15609c4d7cf724e471de55f5cdac.
(Closing now...)

It looks Bram wrote a wrong issue number in the commit message.

okay, so reopening #2956


Run ESLint for .tsx files & Use it to spot variables without inferred types

Run ESLint for .jsx and .tsx files too (was missing in package.json and .eslintrc.cjs).
Also includes fixes for most of these new linter warnings (except any type in catch clauses).
Enable warnings for variable declarations without initialisation. This makes it easier to ensure they have type annotations (to prevent them from being any type) before disabling the warning locally.

Awesome, thanks!
I'll see what I can do about the remaining warnings


updating README.md, include onStart method

I am excited to use this module, and I hope I can contribute more in the near future 👍

Coverage remained the same at 100.0% when pulling bc97118e53dd360db7287fa199e1a78eb66e2b7b on chrischang:master into abdb9153cff64150d3a976ad2c58e5aa4a064190 on Accenture:master.

Thank you for your pull request. See my minor comment attached

Great to know, Thanks!

Coverage remained the same at 100.0% when pulling d84c2916fd66b65b9a416e2a66fb8ae891dc8ab5 on chrischang:master into abdb9153cff64150d3a976ad2c58e5aa4a064190 on Accenture:master.

Coverage remained the same at 100.0% when pulling d84c2916fd66b65b9a416e2a66fb8ae891dc8ab5 on chrischang:master into abdb9153cff64150d3a976ad2c58e5aa4a064190 on Accenture:master.

I pushed one small update adding missing code block ending and semicolons (I noticed it just after merging)
https://github.com/Accenture/alexia/commit/b544ea2668cfa6a69008b4922c46b03fc517cb42


Bump rufus scheduler version number.

3.1.7 includes bug fix for scheduler not running during hour long transition on DST.

want to include this fix: https://github.com/jmettraux/rufus-scheduler/commit/3b52ee2e7148d0da98ea4ee53f38f6df9481396d

Merged


Issue with /docs/tutorials/kubernetes-basics/explore-interactive/

This is a...

[ ] Feature Request
[x] Bug Report

Problem:
Kubernetes basics - Chapter 3 mentions :
Again, worth mentioning that the name of the container itself can be omitted in this case because we have only one running in the Pod.```

But it seems that omitting the container name is not supported:

kubectl exec env
error: expected 'exec POD_NAME COMMAND [ARG1] [ARG2] ... [ARGN]'.
POD_NAME and COMMAND are required arguments for the exec command
See 'kubectl exec -h' for help and examples.

**Proposed Solution:**
Remove that piece of advice?

**Page to Update:**
https://kubernetes.io/docs/tutorials/kubernetes-basics/explore-interactive/

<!--Optional Information (remove the comment tags around information you would like to include)-->
<!--Kubernetes Version:-->

<!--Additional Information:-->

@fuho kubectl exec defaults to the single/first container by default given the argument followed by kubectl exec is a valid pod name. You will get the error you pasted if the pod name is invalid, (in your case env).
You will not get this error if you specified a valid pod name followed by kubectl exec.
Here's an example:
$ kubectl run web --image nginx --port 80
deployment "web" created

$ kubectl get pod
NAME                   READY     STATUS    RESTARTS   AGE
web-4291803130-472lw   1/1       Running   0          5s

$ kubectl exec web-4291803130-472lw env
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOSTNAME=web-4291803130-472lw
KUBERNETES_SERVICE_PORT=443
...

$ kubectl exec invalid
error: expected 'exec POD_NAME COMMAND [ARG1] [ARG2] ... [ARGN]'.
POD_NAME and COMMAND are required arguments for the exec command
See 'kubectl exec -h' for help and examples.

In the interactive tutorial, in step 2 of 4 you need to execute this:
export POD_NAME=$(kubectl get pods -o go-template --template '{{range .items}}{{.metadata.name}}{{"\n"}}{{end}}')

echo Name of the Pod: $POD_NAME
and in Step 4 of 4, it makes you execute kubectl exec $POD_NAME env so this is valid advice.
If this makes sense, let's close the issue. The advice given in the tutorial  If not, please feel free to ask your question if it is still confusing.

@fuho Thanks for opening this issue. Given @ahmetb's response, I'm closing this issue.
Help is also available in the #kubernetes-users channel in Kubernetes slack.


[harfbuzz] Build error on x64-windows

I am not sure if this is related to https://github.com/microsoft/vcpkg/pull/36151, but when I try to build my project from visual studio using manifest mode I see the following error output:
1> [CMake] Building<EMAIL_ADDRESS>1> [CMake] -- Installing port from location: C:\Users\geiseri\AppData\Local\vcpkg\registries\git-trees\1526ee7fd00ec5ec6eac90cc5c8b0c007d25f0f4
1> [CMake] -- Found Python version '3.11.5 at C:/Users/geiseri/AppData/Local/vcpkg/downloads/tools/python/python-3.11.5-x64/python.exe'
1> [CMake] -- Using meson: C:/Users/geiseri/AppData/Local/vcpkg/downloads/tools/meson-1.3.2-20de00/meson.py
1> [CMake] -- Using cached harfbuzz-harfbuzz-8.3.1.tar.gz.
1> [CMake] -- Extracting source C:/Users/geiseri/AppData/Local/vcpkg/downloads/harfbuzz-harfbuzz-8.3.1.tar.gz
1> [CMake] -- Applying patch fix-win32-build.patch
1> [CMake] -- Using source at C:/src/out/build/x64-debug-blh/vcpkg_installed/vcpkg/blds/harfbuzz/src/8.3.1-472e934e2c.clean
1> [CMake] -- Found external ninja('1.11.0').
1> [CMake] -- Getting CMake variables for x64-windows
1> [CMake] -- Configuring x64-windows-dbg
1> [CMake] CMake Error at scripts/cmake/z_vcpkg_setup_pkgconfig_path.cmake:5 (message):
1> [CMake]   BASE_DIRS is required.
1> [CMake] Call Stack (most recent call first):
1> [CMake]   C:/src/out/build/x64-debug-blh/vcpkg_installed/x64-windows/share/vcpkg-tool-meson/vcpkg_configure_meson.cmake:430 (z_vcpkg_setup_pkgconfig_path)
1> [CMake]   C:/Users/geiseri/AppData/Local/vcpkg/registries/git-trees/1526ee7fd00ec5ec6eac90cc5c8b0c007d25f0f4/portfile.cmake:67 (vcpkg_configure_meson)
1> [CMake]   scripts/ports.cmake:170 (include)
1> [CMake] error: building harfbuzz:x64-windows failed with: BUILD_FAILED
1> [CMake] Elapsed time to handle harfbuzz:x64-windows: 6.4 s
1> [CMake] Please ensure you're using the latest port files with `git pull` and `vcpkg update`.
1> [CMake] Then check for known issues at:
1> [CMake]   https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+harfbuzz
1> [CMake] You can submit a new issue at:
1> [CMake]   https://github.com/microsoft/vcpkg/issues/new?title=[harfbuzz]+Build+error+on+x64-windows&body=Copy+issue+body+from+C%3A%2Fsrc%2Fout%2Fbuild%2Fx64-debug-blh%2Fvcpkg_installed%2Fvcpkg%2Fissue_body.md
1> [CMake]
1> [CMake] -- Running vcpkg install - failed
1> [CMake] CMake Error at C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/vcpkg/scripts/buildsystems/vcpkg.cmake:899 (message):
1> [CMake]   vcpkg install failed.  See logs for more information:
1> [CMake]   C:\src\out\build\x64-debug-blh\vcpkg-manifest-install.log
1> [CMake] Call Stack (most recent call first):
1> [CMake]   C:/Program Files/Microsoft Visual Studio/2022/Professional/Common7/IDE/CommonExtensions/Microsoft/CMake/CMake/share/cmake-3.28/Modules/CMakeDetermineSystem.cmake:170 (include)
1> [CMake]   CMakeLists.txt:26 (project)
1> [CMake] CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage
1> [CMake] CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage
1> [CMake] -- Configuring incomplete, errors occurred!
1> 'C:\Windows\system32\cmd.exe' '/c "%SYSTEMROOT%\System32\chcp.com 65001 >NUL && "C:\PROGRAM FILES\MICROSOFT VISUAL STUDIO\2022\PROFESSIONAL\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\CMAKE\CMake\bin\cmake.exe"  -G "Ninja"  -DX_VCPKG_APPLOCAL_DEPS_INSTALL:STRING="ON" -DCMAKE_BUILD_TYPE:STRING="RelWithDebInfo" -DENABLE_GAVS_BRANDING:STRING="ON" -DENABLE_BLH_PASSWORD:STRING="ON" -DCMAKE_INSTALL_PREFIX:PATH="C:/src/out/install/x64-debug-blh" -DCMAKE_TOOLCHAIN_FILE:FILEPATH="C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\vcpkg/scripts/buildsystems/vcpkg.cmake"   -DCMAKE_MAKE_PROGRAM="C:\PROGRAM FILES\MICROSOFT VISUAL STUDIO\2022\PROFESSIONAL\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\CMAKE\Ninja\ninja.exe" "C:\src" 2>&1"' execution failed with error: ''C:\Windows\system32\cmd.exe' '/c "%SYSTEMROOT%\System32\chcp.com 65001 >NUL && "C:\PROGRAM FILES\MICROSOFT VISUAL STUDIO\2022\PROFESSIONAL\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\CMAKE\CMake\bin\cmake.exe"  -G "Ninja"  -DX_VCPKG_APPLOCAL_DEPS_INSTALL:STRING="ON" -DCMAKE_BUILD_TYPE:STRING="RelWithDebInfo" -DENABLE_GAVS_BRANDING:STRING="ON" -DENABLE_BLH_PASSWORD:STRING="ON" -DCMAKE_INSTALL_PREFIX:PATH="C:/src/out/install/x64-debug-blh" -DCMAKE_TOOLCHAIN_FILE:FILEPATH="C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\vcpkg/scripts/buildsystems/vcpkg.cmake"   -DCMAKE_MAKE_PROGRAM="C:\PROGRAM FILES\MICROSOFT VISUAL STUDIO\2022\PROFESSIONAL\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\CMAKE\Ninja\ninja.exe" "C:\src" 2>&1"' returned with exit code: 1'.

I do know that the last working baseline in my manifest was 215a2535590f1f63788ac9bd2ed58ad15e6afdff so before that pull.
What confuses me is that if I run vcpkg install  from the project directory it will run to completion.  I am wondering if it could also be related to https://github.com/microsoft/vcpkg/issues/37615 then.  I do have a python that is different installed in my path.

Do a git pull. I think the problem is that you are using a baseline which is newer than your vcpkg checkout and thus the scripts are outdated compared to the baseline.

I can confirm failure with baseline at be9eb6694585a8db137872b29fcad3619a5f893a and vcpkg checkout at 3c76dc55f8bd2b7f4824bcd860055094bfbbb9ea  having the baseline back at 3c76dc55f8bd2b7f4824bcd860055094bfbbb9ea causes the build to complete.  Between all changes I did a git clean -Xdf . in both my project directory and vcpkg as well as deleting %HOMEPATH%\AppData\Local\vcpkg.  Are there other values I should check too?

What confuses me is that if I run vcpkg install  from the project directory it will run to completion. I am wondering if it could also be related to #37615 then. I do have a python that is different installed in my path.

I just noticed this: 1> [CMake] CMake Error at C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/vcpkg/scripts/buildsystems/vcpkg.cmake:899 (message):. I did confirm my environment though: PS C:\src> echo $env:VCPKG_ROOT C:\Users\geiseri\vcpkg.    Maybe visual studio is being helpful?

@Neumann-A  It was because I had vcpkg installed from Visual Studio.  Once I uninstalled the feature eveerything worked again.  Is there a reccomendation to not use that feature in Visual Studio?

This is still blocking on #38151 passing tests for qcoro.


Issue with missing dependencies for the "stillat-blade-parser" package

Description
I have installed stillat-blade-parser and I'm using it for parsing purposes.
I believe there are missing dependencies in the stillat-blade-parser package.
To execute the sample code in the README, you will need to install additional packages such as prettier, php-parser, @prettier/plugin-php, @stedi/prettier-plugin-jsonata and jsonata in addition to the stillat-blade-parser package.
Repro
1. Prepare
mkdir -p /tmp/blade-parser-check
cd /tmp/blade-parser-check
npm init -y
npm i stillat-blade-parser
npm i -D typescript
npx tsc --init
touch sample.ts

2. Code
The following is an example code of using a simple parser described in the README.
sample.ts:
import { BladeDocument } from "stillat-blade-parser/out/document/bladeDocument";

const document = BladeDocument.fromText(`<html>
    <head>
        <title>{{ $title }}</title>
    </head>
</html>`);

3.  When transpiling and running, I encounter an error.
npx tsc

node sample.js

To resolve this, you need to install packages such as prettier, php-parser, @prettier/plugin-php, @stedi/prettier-plugin-jsonata and jsonata...

Error:
$ node sample.js
node:internal/modules/cjs/loader:1078
  throw err;
  ^

Error: Cannot find module 'prettier'
Require stack:
- /private/tmp/blade-parser-check/node_modules/stillat-blade-parser/out/formatting/prettier/utils.js
- /private/tmp/blade-parser-check/node_modules/stillat-blade-parser/out/document/printers/directivePrinter.js
- /private/tmp/blade-parser-check/node_modules/stillat-blade-parser/out/document/transformer.js
- /private/tmp/blade-parser-check/node_modules/stillat-blade-parser/out/document/bladeDocument.js
- /private/tmp/blade-parser-check/sample.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:1075:15)
    at Module._load (node:internal/modules/cjs/loader:920:27)
    at Module.require (node:internal/modules/cjs/loader:1141:19)
    at require (node:internal/modules/cjs/helpers:110:18)
    at Object.<anonymous> (/private/tmp/blade-parser-check/node_modules/stillat-blade-parser/out/formatting/prettier/utils.js:30:36)
    at Module._compile (node:internal/modules/cjs/loader:1254:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
    at Module._load (node:internal/modules/cjs/loader:958:12)
    at Module.require (node:internal/modules/cjs/loader:1141:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/private/tmp/blade-parser-check/node_modules/stillat-blade-parser/out/formatting/prettier/utils.js',
    '/private/tmp/blade-parser-check/node_modules/stillat-blade-parser/out/document/printers/directivePrinter.js',
    '/private/tmp/blade-parser-check/node_modules/stillat-blade-parser/out/document/transformer.js',
    '/private/tmp/blade-parser-check/node_modules/stillat-blade-parser/out/document/bladeDocument.js',
    '/private/tmp/blade-parser-check/sample.js'
  ]
}

Node.js v18.16.0

Sorry about that! I've pushed a 1.1.9 release with the update dependencies list 🙌

Thanks 🙇 @JohnathonKoster

Your active development on the blade parser (typescript and php) is truly remarkable. Thanks. 🙇
This is unrelated to the issue at hand, but are you familiar with something called tree-sitter?
There are tree-sitters available for Twig and Django HTML (Python related), but unfortunately, there is currently no tree-sitter specifically designed for Blade...

https://github.com/gbprod/tree-sitter-twig
https://github.com/interdependence/tree-sitter-htmldjango

If you were to develop tree-sitter-blade, I believe it would become something truly remarkable. If you're interested, I suggest looking into tree-sitter.


Organize Python tests in tests

Pytest or unittest

https://stackoverflow.com/questions/644821/python-how-to-run-unittest-main-for-all-source-files-in-a-subdirectory
Make test_forward test_backward unittest


[GHSA-97m3-52wr-xvv2] Dompdf's usage of vulnerable version of phenx/php-svg-lib leads to restriction bypass and potential RCE

Updates

Affected products
CWEs

Comments
Restoring CWEs that were accidentally removed with the previous suggestion.

Hi there @Blaklis and @bsweeney! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository.
This change will be reviewed by our Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory


Flickering Issue

Hello @Thundermaker300,
Not sure how to describe this but if having ScriptedEvents in the server and having plugin(s) showing hints on the screen, the ScriptedEvents makes them flicker and disappear almost instantly.
Having ScriptedEvents disabled fixes that issue.
The only script that I have on the server is Auto Nuke:
!-- AUTORUN
# Wait until the round has started
WAITUNTIL {ROUNDSTARTED}

# Wait for the amount of seconds
WAITSEC 1200

# Do not activate the warhead again if it's already detonated or counting down
STOPIF {WARHEADDETONATED}

# Activate warhead
WARHEAD START

# Lock the warhead so its setting can't be changed
WARHEAD LOCK

# Broadcast that the warhead has been automatically started and cannot be cancelled.
BROADCAST 10 <color=#FF0000>WARNING: WARHEAD HAS BEEN AUTOMATICALLY ACTIVATED AND CANNOT BE STOPPED. PLEASE ESCAPE THE FACILITY!

Do you have RueI installed? There have been known issues with SE's implementation of RueI, which could've lead to this behavior.

afaik scripted events is not doing anything with hints by itself, it uses the exileds implementation for showing hints
only explanation for that behavior would be that se is trying to display hints all the time, but no hint action is used in your script
maybe @Thundermaker300 would know more about it

Has this been resolved at all yet @Elektryk-Andrzej @Thundermaker300?


Polish cloud controller

https://github.com/fluxninja/aperture/issues/2308 implemented basic support for configuring connection to cloud controller, but there are a few things that can be improved:

[x] #2372
[x] #2371
[x] #2368
[x] #2369
[x] #2370
[x] #2373
[x] #2388
[x] #2402
[x] #2420

@krdln @kklimonda-fn can this one be closed?


Error running xfuse

When I run the xfuse run my-config.toml --save-path my-run line, I ran into an error:
[2022-10-07 21:59:44,127] ℹ : Running xfuse version 0.2.1
[2022-10-07 21:59:44,146] ℹ : Using the following design table:
[2022-10-07 21:59:44,146] ℹ :
[2022-10-07 21:59:44,147] ℹ : |          |   section {1,2,3,4} |
[2022-10-07 21:59:44,147] ℹ : |----------+---------------------|
[2022-10-07 21:59:44,147] ℹ : | section1 |                   1 |
[2022-10-07 21:59:44,147] ℹ : | section2 |                   2 |
[2022-10-07 21:59:44,147] ℹ : | section3 |                   3 |
[2022-10-07 21:59:44,147] ℹ : | section4 |                   4 |
[2022-10-07 21:59:44,147] ℹ :
[2022-10-07 21:59:44,149] 🚨 ERROR : AttributeError: module 'os' has no attribute 'sched_getaffinity'
Traceback (most recent call last):
File "/Users/name/xfusestuff/xfusevenv/lib/python3.8/site-packages/xfuse/main.py", line 585, in run
_run(
File "/Users/name/xfusestuff/xfusevenv/lib/python3.8/site-packages/xfuse/run.py", line 64, in run
if (available_cores := len(os.sched_getaffinity(0))) < num_data_workers:
AttributeError: module 'os' has no attribute 'sched_getaffinity'
I searched this problem on stack overflow but it I didn't find a solution to it. Is there an alternative function to use in place of os.sched_getaffinity. I am using an M1 Macbook Air 2020, 16GB Ram.

Hi, Can you try the fixes proposed in #51?


calling searchIndex twice causes the process to hang, so check to see if the index has already been "opened" before opening it again.

This is a PR addressing the above comment that is under the TODOs. I've attached a field to blockstore-level that allows access to the instance db status, and a simple check on that status to determine open() logic. Please let me know if adjustments are needed!

From the looks of it, two database's are opened, a BLOCKSTORE and an INDEX levelDB, looking at the file changes it looks like your checking if the BLOCKSTORE database is open/opening to then decide to open the INDEX db. Should it not check if the index db is open already to decide whether to open it?

From the looks of it, two database's are opened, a BLOCKSTORE and an INDEX levelDB, looking at the file changes it looks like your checking if the BLOCKSTORE database is open/opening to then decide to open the INDEX db. Should it not check if the index db is open already to decide whether to open it?

This was my original approach but I wasn't sure if I was reading the comment correct. I can modify the logic to follow more along what you're saying. If I'm understanding right.
I'll revise the PR with the following changes:

Revert changes to BlockStoreLevel class
Add status field to MessageStoreLevel
Flip status field and add checks on calls to MessageStoreLevel.open() / close()

Does that sounds more in line with what you had in mind?

agreed with the approach that @NWylynko laid out and that's currently how the code on the main branch behaves. BlockstoreLevel#open already has logic in place to prevent from calling open if the Blockstore is already open.
I think the way i wrote the TODOs made it seem as if calling searchIndex twice was causing the process to hang as something that needed to be addressed. This wasn't actually a TODO, it's just a comment explaining the conditional. The actual TODO is to parameterize name.
code snippet
// TODO: look into using the same level we're using for blockstore
// TODO: parameterize `name`
// calling `searchIndex` twice causes the process to hang, so check to see if the index
// has already been "opened" before opening it again.
if (!this.index) {
  this.index = await searchIndex({ name: this.config.indexLocation });
}

i forgot to add a period here: // TODO: parameterize name which probably made it seem like the comment right below it was a part of the TODO. many apologies 😅


Auto Synthesis

AutoSynthesis doesn't work with XIVAlexander?

should not effecting. That program is just like a macro recorder

AutoSynthesis is incompatible with XivAlexander. It explicitly states that in the main page.

"WARNING: This application is not compatible with current versions of XIV Alexander. Will be looking into this. For now if you want to use autosynth, please disable XIV Alexander or use the NoClippy plugin"

I feel that warning is more a "political" stance of the program author to the XIVAlexander than "not working because something".
Logically, that program at current state is just a "autohotkey" script put as a fancy standalone program. And if you check their issue, there's no issue about XIVAlexander.


add more options to install

-y, --yaml-file <path-to-yaml-file> - Path to a YAML file, default ./package.yaml
-r, --repos-dir <path-to-repos-dir> - Path to the installed repositories dir, default ./repositories

added:


Docker Stack api

I read the v1.25 document, but I can't find any related information.  I was wondering if "docker stack deploy" api was the on roadmap.

docker stack is a client-side implementation currently.
Closing since it's not really an issue, but feel free to discuss.
🙇


E0419 14:04:33.137997       1 reflector.go:315] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to watch *v3.PodSecurityPolicyTemplate: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/watch/podsecuritypolicytemplates?resourceVersion=47896&timeoutSeconds=387: net/http: TLS handshake timeout
E0419 14:04:33.138063       1 reflector.go:315] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to watch *v1.Namespace: Get https://<IP_ADDRESS>:6443/api/v1/watch/namespaces?resourceVersion=47890&timeoutSeconds=330: net/http: TLS handshake timeout
E0419 14:05:13.093881       1 reflector.go:315] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to watch *v3.RoleTemplate: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/watch/roletemplates?resourceVersion=47896&timeoutSeconds=541: net/http: TLS handshake timeout
E0419 14:05:13.103318       1 reflector.go:315] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to watch *v3.PodSecurityPolicyTemplate: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/watch/podsecuritypolicytemplates?resourceVersion=47896&timeoutSeconds=357: net/http: TLS handshake timeout
E0419 14:05:13.103338       1 reflector.go:315] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to watch *v3.Node: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/watch/nodes?resourceVersion=47892&timeoutSeconds=513: net/http: TLS handshake timeout
E0419 14:05:13.103344       1 reflector.go:315] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to watch *v3.NodeDriver: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/watch/nodedrivers?resourceVersion=47892&timeoutSeconds=327: net/http: TLS handshake timeout
E0419 14:05:13.103349       1 reflector.go:315] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to watch *v3.Project: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/watch/projects?resourceVersion=47892&timeoutSeconds=387: net/http: TLS handshake timeout
E0419 14:04:46.192021       1 reflector.go:315] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to watch *v3.ProjectLogging: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/watch/projectloggings?resourceVersion=47924&timeoutSeconds=380: net/http: TLS handshake timeout
E0419 14:05:28.079836       1 reflector.go:315] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to watch *v1.ClusterRoleBinding: Get https://<IP_ADDRESS>:6443/apis/rbac.authorization.k8s.io/v1/watch/clusterrolebindings?resourceVersion=47890&timeoutSeconds=516: net/http: TLS handshake timeout
E0419 14:05:40.117086       1 reflector.go:315] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to watch *v1.Role: Get https://<IP_ADDRESS>:6443/apis/rbac.authorization.k8s.io/v1/watch/roles?resourceVersion=47890&timeoutSeconds=503: net/http: TLS handshake timeout
E0419 14:06:27.047563       1 reflector.go:315] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to watch *v3.App: Get https://<IP_ADDRESS>:6443/apis/project.cattle.io/v3/watch/apps?resourceVersion=47924&timeoutSeconds=428: net/http: TLS handshake timeout
E0419 14:06:27.033061       1 reflector.go:315] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to watch *v3.Project: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/watch/projects?resourceVersion=47892&timeoutSeconds=442: net/http: TLS handshake timeout
E0419 14:06:44.092375       1 wrap.go:34] APIServer panic'd on POST /apis/management.cattle.io/v3/templateversions: kill connection/stream
goroutine 45537 [running]:
runtime/debug.Stack(0xa52a440, 0xc4457b44d0, 0x4d4f4c4)
	/usr/local/go/src/runtime/debug/stack.go:24 +0xa7
github.com/rancher/rancher/vendor/k8s.io/apiserver/pkg/server/filters.WithPanicRecovery.func1.1(0x41c8e20, 0xc420565cb0)
	/go/src/github.com/rancher/rancher/vendor/k8s.io/apiserver/pkg/server/filters/wrap.go:34 +0x74
github.com/rancher/rancher/vendor/k8s.io/apimachinery/pkg/util/runtime.HandleCrash(0xc435493c90, 0x1, 0x1)
	/go/src/github.com/rancher/rancher/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:54 +0xc8
panic(0x41c8e20, 0xc420565cb0)
	/usr/local/go/src/runtime/panic.go:491 +0x283
github.com/rancher/rancher/vendor/k8s.io/apiserver/pkg/server/filters.(*baseTimeoutWriter).timeout(0xc42c3909e0, 0xc44e25a480)
	/go/src/github.com/rancher/rancher/vendor/k8s.io/apiserver/pkg/server/filters/timeout.go:230 +0x190
github.com/rancher/rancher/vendor/k8s.io/apiserver/pkg/server/filters.(*timeoutHandler).ServeHTTP(0xc42a819260, 0xa52a440, 0xc4457b44d0, 0xc44df9d500)
	/go/src/github.com/rancher/rancher/vendor/k8s.io/apiserver/pkg/server/filters/timeout.go:114 +0x292
github.com/rancher/rancher/vendor/k8s.io/apiserver/pkg/endpoints/filters.WithRequestInfo.func1(0xa52a440, 0xc4457b44d0, 0xc44df9d500)
	/go/src/github.com/rancher/rancher/vendor/k8s.io/apiserver/pkg/endpoints/filters/requestinfo.go:45 +0x20f
net/http.HandlerFunc.ServeHTTP(0xc42a7ab500, 0xa52a440, 0xc4457b44d0, 0xc44df9d500)
	/usr/local/go/src/net/http/server.go:1918 +0x44
github.com/rancher/rancher/vendor/k8s.io/apiserver/pkg/endpoints/request.WithRequestContext.func1(0xa52a440, 0xc4457b44d0, 0xc44df9d500)
	/go/src/github.com/rancher/rancher/vendor/k8s.io/apiserver/pkg/endpoints/request/requestcontext.go:110 +0xcb
net/http.HandlerFunc.ServeHTTP(0xc42a819280, 0xa52a440, 0xc4457b44d0, 0xc44df9d500)
	/usr/local/go/src/net/http/server.go:1918 +0x44
github.com/rancher/rancher/vendor/k8s.io/apiserver/pkg/server/filters.WithPanicRecovery.func1(0xa52a440, 0xc4457b44d0, 0xc44df9d500)
	/go/src/github.com/rancher/rancher/vendor/k8s.io/apiserver/pkg/server/filters/wrap.go:41 +0x108
net/http.HandlerFunc.ServeHTTP(0xc42a8192a0, 0xa52e680, 0xc434585500, 0xc44df9d500)
	/usr/local/go/src/net/http/server.go:1918 +0x44
github.com/rancher/rancher/vendor/k8s.io/apiserver/pkg/server.(*APIServerHandler).ServeHTTP(0xc424352cc0, 0xa52e680, 0xc434585500, 0xc44df9d500)
	/go/src/github.com/rancher/rancher/vendor/k8s.io/apiserver/pkg/server/handler.go:198 +0x51
net/http.serverHandler.ServeHTTP(0xc42b6e4a90, 0xa52e680, 0xc434585500, 0xc44df9d500)
	/usr/local/go/src/net/http/server.go:2619 +0xb4
net/http.(*conn).serve(0xc4411e5ae0, 0xa532100, 0xc441827ac0)
	/usr/local/go/src/net/http/server.go:1801 +0x71d
created by net/http.(*Server).Serve
	/usr/local/go/src/net/http/server.go:2720 +0x288

E0419 14:07:09.108007       1 streamwatcher.go:109] Unable to decode an event from the watch stream: tunnel disconnect
E0419 14:07:51.038143       1 status.go:62] apiserver received an error that is not an metav1.Status: http: Handler timeout
E0419 14:07:50.159456       1 reflector.go:315] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to watch *v1.Namespace: Get https://<IP_ADDRESS>:6443/api/v1/watch/namespaces?resourceVersion=47890&timeoutSeconds=322: net/http: TLS handshake timeout
E0419 14:10:25.130228       1 reflector.go:315] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to watch *v1.RoleBinding: Get https://<IP_ADDRESS>:6443/apis/rbac.authorization.k8s.io/v1/watch/rolebindings?resourceVersion=47897&timeoutSeconds=407: net/http: TLS handshake timeout
E0419 14:09:06.120238       1 reflector.go:315] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to watch *v1.Role: Get https://<IP_ADDRESS>:6443/apis/rbac.authorization.k8s.io/v1/watch/roles?resourceVersion=47890&timeoutSeconds=498: net/http: TLS handshake timeout
E0419 14:07:08.032994       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: the server was unable to return a response in the time allotted, but may still be processing the request (get endpoints kube-controller-manager)
E0419 14:10:28.039734       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v3.Catalog: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/catalogs?resourceVersion=0: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
E0419 14:10:28.039812       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v3.Node: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/namespaces/cluster-9phkq/nodes?resourceVersion=0: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
E0419 14:10:28.059064       1 streamwatcher.go:109] Unable to decode an event from the watch stream: tunnel disconnect
E0419 14:10:29.002929       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v3.Notifier: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/namespaces/cluster-9phkq/notifiers?resourceVersion=0: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
E0419 14:10:29.039329       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v3.PodSecurityPolicyTemplate: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/podsecuritypolicytemplates?resourceVersion=0: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
E0419 14:10:29.175999       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v1.ClusterRoleBinding: Get https://<IP_ADDRESS>:6443/apis/rbac.authorization.k8s.io/v1/clusterrolebindings?resourceVersion=0: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
E0419 14:10:30.018164       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v3.ProjectAlert: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/projectalerts?resourceVersion=0: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
E0419 14:10:30.050583       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v3.ClusterLogging: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/namespaces/cluster-9phkq/clusterloggings?resourceVersion=0: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
E0419 14:10:30.149320       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v3.ClusterRegistrationToken: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/clusterregistrationtokens?resourceVersion=0: dial tcp <IP_ADDRESS>:6443: i/o timeout
E0419 14:10:30.149398       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v3.ClusterPipeline: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/clusterpipelines?resourceVersion=0: dial tcp <IP_ADDRESS>:6443: i/o timeout
E0419 14:10:31.022135       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v3.Node: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/nodes?resourceVersion=0: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
E0419 14:10:23.218745       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-scheduler: the server was unable to return a response in the time allotted, but may still be processing the request (get endpoints kube-scheduler)
E0419 14:11:28.089944       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v3.Project: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/projects?resourceVersion=0: net/http: TLS handshake timeout
E0419 14:11:33.017120       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v3.Node: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/namespaces/local/nodes?resourceVersion=0: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
E0419 14:11:33.017215       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v1.Role: Get https://<IP_ADDRESS>:6443/apis/rbac.authorization.k8s.io/v1/roles?resourceVersion=0: net/http: TLS handshake timeout
E0419 14:11:33.051586       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v3.NodePool: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/nodepools?resourceVersion=0: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
E0419 14:11:33.080714       1 streamwatcher.go:109] Unable to decode an event from the watch stream: tunnel disconnect
E0419 14:11:33.087808       1 streamwatcher.go:109] Unable to decode an event from the watch stream: tunnel disconnect
E0419 14:11:33.088355       1 streamwatcher.go:109] Unable to decode an event from the watch stream: tunnel disconnect
E0419 14:11:33.088778       1 streamwatcher.go:109] Unable to decode an event from the watch stream: tunnel disconnect
E0419 14:11:33.089422       1 streamwatcher.go:109] Unable to decode an event from the watch stream: tunnel disconnect
E0419 14:11:33.089860       1 streamwatcher.go:109] Unable to decode an event from the watch stream: tunnel disconnect
E0419 14:11:33.090347       1 streamwatcher.go:109] Unable to decode an event from the watch stream: tunnel disconnect
E0419 14:11:33.090989       1 streamwatcher.go:109] Unable to decode an event from the watch stream: tunnel disconnect
E0419 14:11:33.091599       1 streamwatcher.go:109] Unable to decode an event from the watch stream: tunnel disconnect
E0419 14:11:33.092188       1 streamwatcher.go:109] Unable to decode an event from the watch stream: tunnel disconnect
E0419 14:11:33.099392       1 streamwatcher.go:109] Unable to decode an event from the watch stream: tunnel disconnect
E0419 14:11:33.100012       1 streamwatcher.go:109] Unable to decode an event from the watch stream: tunnel disconnect
E0419 14:11:33.100599       1 streamwatcher.go:109] Unable to decode an event from the watch stream: tunnel disconnect
E0419 14:11:33.101020       1 streamwatcher.go:109] Unable to decode an event from the watch stream: tunnel disconnect
E0419 14:11:33.102005       1 streamwatcher.go:109] Unable to decode an event from the watch stream: tunnel disconnect
E0419 14:11:33.102473       1 streamwatcher.go:109] Unable to decode an event from the watch stream: tunnel disconnect
E0419 14:11:33.111750       1 streamwatcher.go:109] Unable to decode an event from the watch stream: tunnel disconnect
E0419 14:11:33.112386       1 streamwatcher.go:109] Unable to decode an event from the watch stream: tunnel disconnect
E0419 14:11:33.112810       1 streamwatcher.go:109] Unable to decode an event from the watch stream: tunnel disconnect
E0419 14:10:31.085322       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v3.NodeDriver: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/nodedrivers?resourceVersion=0: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
E0419 14:10:34.161897       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v3.Token: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/tokens?resourceVersion=0: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
E0419 14:10:36.160573       1 reflector.go:315] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to watch *v1.Secret: Get https://<IP_ADDRESS>:6443/api/v1/watch/secrets?resourceVersion=47890&timeoutSeconds=572: net/http: TLS handshake timeout
E0419 14:09:33.098482       1 reflector.go:315] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to watch *v3.ProjectNetworkPolicy: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/watch/projectnetworkpolicies?resourceVersion=47924&timeoutSeconds=467: net/http: TLS handshake timeout
E0419 14:10:52.056735       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v3.NodeDriver: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/nodedrivers?resourceVersion=0: net/http: TLS handshake timeout
E0419 14:10:54.095557       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v3.ProjectRoleTemplateBinding: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/projectroletemplatebindings?resourceVersion=0: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
E0419 14:11:07.017621       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v1.Secret: Get https://<IP_ADDRESS>:6443/api/v1/secrets?resourceVersion=0: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
E0419 14:11:07.030619       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v3.PodSecurityPolicyTemplate: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/podsecuritypolicytemplates?resourceVersion=0: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
E0419 14:11:07.030695       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v1.Namespace: Get https://<IP_ADDRESS>:6443/api/v1/namespaces?resourceVersion=0: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
E0419 14:11:07.035449       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v3.RoleTemplate: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/roletemplates?resourceVersion=0: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
E0419 14:11:07.057597       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v3.ProjectLogging: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/projectloggings?resourceVersion=0: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
E0419 14:11:07.057646       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v3.Setting: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/settings?resourceVersion=0: net/http: TLS handshake timeout
E0419 14:10:52.042001       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v3.Node: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/nodes?resourceVersion=0: net/http: TLS handshake timeout
E0419 14:10:59.132252       1 leaderelection.go:224] error retrieving resource lock kube-system/cattle-controllers: Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-system/configmaps/cattle-controllers: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
E0419 14:11:19.002527       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v3.GlobalRoleBinding: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/globalrolebindings?resourceVersion=0: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
E0419 14:11:19.106346       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v3.App: Get https://<IP_ADDRESS>:6443/apis/project.cattle.io/v3/apps?resourceVersion=0: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
E0419 14:11:19.106368       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v3.GlobalRole: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/globalroles?resourceVersion=0: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
E0419 14:11:28.195781       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v3.Project: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/projects?resourceVersion=0: net/http: TLS handshake timeout
E0419 14:11:33.266059       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v3.DynamicSchema: Get https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/dynamicschemas?resourceVersion=0: net/http: TLS handshake timeout
2018/04/19 14:11:31 [INFO] Handling backend connection request.
E0419 14:11:30.165130       1 streamwatcher.go:109] Unable to decode an event from the watch stream: tunnel disconnect
2018/04/19 14:11:42 [ERROR] failed to rollback and delete templateVersion helm-kubernetes-traefik-1.28.1: Delete https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/templateversions/helm-kubernetes-traefik-1.28.1: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
2018/04/19 14:11:42 [INFO] Creating template helm-kubernetes-uchiwa
E0419 14:11:40.100152       1 cronjob_controller.go:113] can't list Jobs: the server was unable to return a response in the time allotted, but may still be processing the request (get jobs.batch)
E0419 14:11:33.192279       1 event.go:260] Could not construct reference to: '&v1.ConfigMap{TypeMeta:v1.TypeMeta{Kind:"", APIVersion:""}, ObjectMeta:v1.ObjectMeta{Name:"", GenerateName:"", Namespace:"", SelfLink:"", UID:"", ResourceVersion:"", Generation:0, CreationTimestamp:v1.Time{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, DeletionTimestamp:(*v1.Time)(nil), DeletionGracePeriodSeconds:(*int64)(nil), Labels:map[string]string(nil), Annotations:map[string]string(nil), OwnerReferences:[]v1.OwnerReference(nil), Initializers:(*v1.Initializers)(nil), Finalizers:[]string(nil), ClusterName:""}, Data:map[string]string(nil)}' due to: 'selfLink was empty, can't make reference'. Will not report event: 'Normal' 'LeaderElection' '72713990e9e0 stopped leading'
E0419 14:11:41.119552       1 writers.go:139] apiserver was unable to write a JSON response: http: Handler timeout
E0419 14:11:41.124623       1 writers.go:139] apiserver was unable to write a JSON response: http: Handler timeout
E0419 14:11:41.124725       1 writers.go:139] apiserver was unable to write a JSON response: http: Handler timeout
E0419 14:11:41.128574       1 writers.go:139] apiserver was unable to write a JSON response: http: Handler timeout
2018-04-19 14:11:44.207214 W | etcdserver: apply entries took too long [9.00766777s for 1 entries]
2018-04-19 14:11:44.207317 W | etcdserver: avoid queries with large range/delete range!
E0419 14:11:43.164224       1 writers.go:139] apiserver was unable to write a JSON response: http: Handler timeout
E0419 14:11:42.172092       1 writers.go:139] apiserver was unable to write a JSON response: http: Handler timeout
E0419 14:11:46.167607       1 reflector.go:315] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to watch *v1.NetworkPolicy: Get https://<IP_ADDRESS>:6443/apis/networking.k8s.io/v1/watch/networkpolicies?resourceVersion=1690&timeoutSeconds=511: net/http: TLS handshake timeout
E0419 14:11:46.175040       1 reflector.go:315] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to watch *v1.Pod: Get https://<IP_ADDRESS>:6443/api/v1/watch/pods?resourceVersion=41015&timeoutSeconds=366: net/http: TLS handshake timeout
E0419 14:11:46.186720       1 reflector.go:205] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to list *v1.RoleBinding: Get https://<IP_ADDRESS>:6443/apis/rbac.authorization.k8s.io/v1/rolebindings?resourceVersion=0: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
E0419 14:11:47.153776       1 reflector.go:315] github.com/rancher/rancher/vendor/github.com/rancher/norman/controller/generic_controller.go:129: Failed to watch *v1.RoleBinding: Get https://<IP_ADDRESS>:6443/apis/rbac.authorization.k8s.io/v1/watch/rolebindings?resourceVersion=551&timeoutSeconds=507: net/http: TLS handshake timeout
2018/04/19 14:11:53 [FATAL] leaderelection lost for cattle-controllers
2018/04/19 14:11:54 [INFO] Shutting down JobController controller
2018/04/19 14:11:54 [INFO] Shutting down IngressController controller
2018/04/19 14:11:54 [INFO] Shutting down PodSecurityPolicyController controller
2018/04/19 14:11:54 [INFO] Shutting down RoleController controller
2018/04/19 14:11:54 [INFO] Shutting down ClusterRoleController controller
2018/04/19 14:11:54 [INFO] Shutting down RoleBindingController controller
2018/04/19 14:11:54 [INFO] Shutting down ClusterRoleBindingController controller
2018/04/19 14:11:54 [INFO] Shutting down EndpointsController controller
2018/04/19 14:11:54 [INFO] Shutting down ServiceAccountController controller
2018/04/19 14:11:54 [INFO] Shutting down SecretController controller
2018/04/19 14:11:54 [INFO] Shutting down NamespaceController controller
2018/04/19 14:11:54 [INFO] Shutting down EventController controller
2018/04/19 14:11:54 [INFO] Shutting down ReplicationControllerController controller
2018/04/19 14:11:54 [INFO] Shutting down NodeController controller
2018/04/19 14:11:54 [INFO] Shutting down PodController controller
2018/04/19 14:11:54 [INFO] Shutting down ServiceController controller

Results:

Rancher can only currently run on ports 80 and 443.  Example docker command: docker run -v /home/ubuntu/state:/var/lib/rancher -d -p 80:80 -p 443:443 --restart=unless-stopped rancher/server:v2.0.0-beta4-rc4


[SPARK-33338][SQL] semanticEquals should handle static GetMapValue correctly

What changes were proposed in this pull request?
This PR aims to fix semanticEquals works correctly on static GetMapValue expressions having ArrayBasedMapData and GenericArrayData.
Why are the changes needed?
Currently, it returns false.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the CIs with the newly added test case.

Test build #130596 has started for PR 30246 at commit 8c29c48.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35197/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35197/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/35197/
Test PASSed.

Test build #130597 has started for PR 30246 at commit b7367d7.

Could you review this, @cloud-fan and @maropu ?

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35198/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35198/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/35198/
Test PASSed.

Test build #130596 has finished for PR 30246 at commit 8c29c48.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/130596/
Test PASSed.

Test build #130597 has finished for PR 30246 at commit b7367d7.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/130597/
Test PASSed.

Thank you, @HyukjinKwon and @cloud-fan .
Merged to master/3.0/2.4.


Trying to open a project crashes godot if gui/theme/default_theme_scale project setting is set to NAN.

Godot version
v4.2.dev3.official.013e8e3af
System information
Windows 10.0.19045 - GLES3 (Compatibility)
Issue description
Setting gui/theme/default_theme_scale project setting to NAN (by typing NAN into the field in the Godot editor) makes a project crash and spam the console with the following errors when it is ran:
USER ERROR: ImageLoaderSVG: Couldn't set target on ThorVG canvas.
   at: create_image_from_utf8_buffer (modules/svg/image_loader_svg.cpp:113)
USER ERROR: Failed generating icon, unsupported or invalid SVG data in default theme.
   at: generate_icon (scene/resources/default_theme/default_theme.cpp:92)

Additionally, closing the editor without changing the setting back makes the project virtually non-openable, by crashing the editor every time it tries to open the project.
Steps to reproduce

Create a new project.
Set gui/theme/default_theme_scale project setting to NAN (by typing NAN in).
Try to run the project.
Close the editor.
Try to open the project again.

Minimal reproduction project
Warning: non-openable because of the crash.
default_theme_scale_nan_test.zip

Fixed by #81076.
It can likely be reproduced from code by setting nan manually to that project setting, but I'm not sure we want to go that far into preventing users from shooting themselves in the foot :)


Adding Siderolabs Talos Linux provider

The Talos Linux provider from Siderolabs has been transferred ownership to Pulumiverse. I gave it a big refresh and added the initial docs & examples.
New Provider checklist

[x] The package's schema URL is correct.
[ ] The package metadata file, if present, contains:

[x] a supported category (one of Cloud, Infrastructure, Network, Database, Monitoring, or Utility).
[x] a description that explains what the package does.
[ ] a valid logo URL that points to a PNG whose dimensions conform to the others in this repo (e.g., 100x100).
[ ] a version number prefixed with v that corresponds with a valid GitHub release.

[x] The package repo contains an Overview doc (/docs/_index.md) that includes:

[x] a brief explanation of what the package is and what it does.
[x] at least one representative example in all supported languages.
[ ] a front-matter property for the layout set to package.

[ ] The package repo contains an Installation and Configuration doc (/docs/installation-configuration.md) that includes:

[x] links to SDKs in all supported languages.
[ ] a copyable command for installing the resource plugin if necessary.
[ ] an example of configuring the provider with pulumi config set.
[ ] an example of configuring the provider with environment variables.

[x] Someone from the @pulumi/ai team has reviewed the PR.
[ ] Someone from the @pulumi/docs team has reviewed all documentation.

are there any updates on getting this in? :)

@AaronFriel I will fix the first two, but the docs explicitly mentions this about the config options:

There are no provider configuration options. When accessing Talos Linux machines, use the node property on the machine related resources.

Source: https://github.com/pulumiverse/pulumi-talos/blob/main/docs/installation-configuration.md?plain=1#L18

Fixed in v0.1.5:
https://github.com/pulumiverse/pulumi-talos/blob/v0.1.5/docs/installation-configuration.md

a front-matter property for the layout set to package.

I'll submit a PR to change these, but they needn't block. (We still handle the "old" versions.)

https://github.com/pulumiverse/pulumi-talos/pull/63


dockerTools: Fix streamLayeredImage for symlinks

When archiving /nix/store/foo and foo is itself a symlink, we must
not traverse the symlink target, but archive the foo symlink itself
I think this is sufficient to fix #107021 but I don't know a lot about the streaming mechanics here.

Motivation for this change
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg test docker-tools

@GrahamcOfBorg test docker-tools

Could you turn your example from the issue into a regression test?
Those are in nixos/tests/docker-tools.nix. You can add the image to pkgs/build-support/docker/examples.nix (or a new file for regression test images if you like).
The fix seems to make sense, but I'd appreciate a review by @utdemir.

Could you turn your example from the issue into a regression test?
Those are in nixos/tests/docker-tools.nix. You can add the image to pkgs/build-support/docker/examples.nix (or a new file for regression test images if you like).
The fix seems to make sense, but I'd appreciate a review by @utdemir.

@GrahamcOfBorg test docker-tools

@GrahamcOfBorg test docker-tools

@GrahamcOfBorg test docker-tools

@GrahamcOfBorg test docker-tools

Great! Thank you @srhb and @utdemir!

Great! Thank you @srhb and @utdemir!

Nice, thanks for this fix! 🏆

Thank you!

Thank you!