Add Intl.ListFormat to es2021 lib

Suggestion
🔍 Search Terms

Intl.ListFormat
Intl
ListFormat

✅ Viability Checklist

My suggestion meets these guidelines:

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

⭐ Suggestion
Add Intl.ListFormat to es2021 lib types (as per Finished Proposals).
Bringing this API to Typescript has been directly suggested before, but didn't follow the issue templates (#46866), and was also mentioned before (https://github.com/microsoft/TypeScript/issues/45646#issuecomment-962430370, https://github.com/microsoft/TypeScript/issues/29129#issuecomment-449608280), but, as I couldn't find any specific active issue where the feature suggestion is being considered, I'm opening this issue.
📃 Motivating Example
Code that uses the Intl.ListFormat API should not fail type checking:
new Intl.ListFormat('bg', {type: 'conjunction'}).format(['a','b','c'])
new Intl.ListFormat('bg', {type: 'disjunction'}).formatToParts(['a','b','c'])

💻 Use Cases
new Intl.ListFormat('bg', {type: 'conjunction'}).format(['a','b','c'])
new Intl.ListFormat('bg', {type: 'disjunction'}).formatToParts(['a','b','c'])

It's ES2021 per the Finished Proposals list.

Thanks for pointing that out, I've updated the issue accordingly.

Is there a workaround for this?

Personally, I used something like:
declare namespace Intl {
    type ListType = "conjunction" | "disjunction";

    interface ListFormatOptions {
        localeMatcher?: "lookup" | "best fit";
        type?: ListType;
        style?: "long" | "short" | "narrow";
    }

    interface ListFormatPart {
        type: "element" | "literal";
        value: string;
    }

    class ListFormat {
        constructor(locales?: string | string[], options?: ListFormatOptions);
        format(values: any[]): string;
        formatToParts(values: any[]): ListFormatPart[];
        supportedLocalesOf(
            locales: string | string[],
            options?: ListFormatOptions,
        ): string[];
    }
}

Thanks for the help. That works great for making the linting errors go away, but (I'm using Deno) I still get [ERROR]: Property 'ListFormat' does not exist on type 'typeof Intl'.  when I try to bundle it or run tests. And yet it works fine in the Deno REPL, so I know that it does exist.... I guess I don't understand Deno/TS enough to see what's going on.

The Deno REPL uses swc to transpile TypeScript without doing any type-checking, so that difference is not indicative of there being types for Intl.ListFormat in Deno or TypeScript.

Yes. I understood that. The types are missing, but the REPL cares not. But the actual code must be there or it wouldn't work at all, no? The VSCode linter picks up the above namespace declaration and the red squiggles go away, but clearly the bundler and test in Deno do not, as they fail the type check.

@chasm I haven't much experience with it, but I found this in Deno's docs:

Another option is to use a configuration file that is configured to include the type definitions, by supplying a "types" value to the "compilerOptions". For example:
{
  "compilerOptions": {
    "types": [
      "./types.d.ts",
<EMAIL_ADDRESS>      "/Users/me/pkg/types.d.ts"
    ]
  }
}

Maybe refering to the .d.ts file would make the bundler aware of it?

Excellent. I will check that out. Thanks.

is this live? i cant find ListFormat after installing https://www.npmjs.com/package/@types/intl

This is live, and that package is outdated and should not be required in any situation. Make sure your target is es2021 or higher, and if that still doesn't work, please open a new issue rather than commenting on an old issue. Thanks.


Fail build when formatting is incorrect

This addition will cause the Travis build to fail if the PR contains dart files that aren't properly formatted.
Kind of an annoying one haha, but I keep committing unformatted code, and figure it can't hurt to verify that we're keeping our code properly formatted.
It also fixes all the files that were causing failures :)

Good idea, I tend to skip formatting as well, this test will keep us in check :)


Wigs preset added

Solving issue#7878

Looks fine, thanks @fakeharahman!
A few tips, try to run npm run build after updating data files and include the derived changes in your commit. Also, you can write "closes #7878" or "fixes #7878" in your pull request comment to automatically close the issue upon merging 🙂

Oh okay I will do that next time!


Vue needs update.

new update of vue-server-renderer from 2.6.10 to 2.6.11.
Now getting error:
`UnhandledPromiseRejectionWarning:   Error: Vue packages version mismatch:

<EMAIL_ADDRESS><EMAIL_ADDRESS>

This question is available on Nuxt community (#c10128)

Got the same problem.

Ditto

This fixed it for me:
Try deleting package-lock.json, run npm update and npm run dev again.

This fixed it for me:
Try deleting package-lock.json, run npm update and npm run dev again.

I also had to delete node_modules folder and npm install.


Contributing to fluentbit-operator

Hello,
My team and I are working on a Kubernetes distribution named MetalK8s and we're currently working on our log centralization system composed of Fluent Bit and Loki.
Your project seems really interesting for us and instead of developing yet another operator (or forking your repository), we would like to contribute to your project to help you integrate new plugins support such as Loki Output.
First, do you accept contribution?
If yes, do you have guidelines?
Otherwise, we would like to know what motivated your choice for building this operator instead of using already existing things like Logging Operator?
But above all, why basing the log collection only on Fluent Bit rather than the Fluent Bit + Fluentd couple as we can find in most log centralization architecture using Fluent Bit?
On our side, we chose this to have a minimal resources consumption, but is there anything else motivating your choice?
We're still thinking of our implementation choice and it would help us a lot to have your thought.
Thanks,
MetalK8s team.

Hi @alexandre-allard-scality , yes sure we'll definitely accept your contribution. The dev guide is here, https://github.com/kubesphere/fluentbit-operator#contributing , it's a bit simple though. Let us know if you need anything else.
We did considering logging operator for a while, we develop FluentBit operator by ourselves for a few reasons:

For logging operator, all logs has to flow from FluentBit to Fluentd, and Fluentd might become a single point of failure.

Actually, we developed Fluentbit forward output crd https://github.com/kubesphere/fluentbit-operator/blob/master/docs/plugins/output/forward.md which can output logs from to Fluentd . So if user want to use Fluentd to forward logs to more sinks, he can use the forward output crd to integrate with Fluentd for now.

We do have plan to develop crds for Fluentd to deploy Fluentd as a deployment, ideally it will help users to deploy Fluentd with ease into K8s. The Fluentd crds should be an optional choice instead of a mandatory one in a logging stack in our opinion.

FluentBit's minimal resource consumption is indeed an important factor that we choose to support it by default.

Another reason we develop FluentBit operator is that we found that we have to restart FluentBit pod to reload new FluentBit configs, there is no reload interface when we develop FluentBit operator. Pls refer to https://github.com/fluent/fluent-bit/pull/842 and https://github.com/fluent/fluent-bit/issues/365

And we do have plan to integrate our logging sidecar function into FluentBit operator which helps to collect logs files on Pod's volume instead of stdout

@huanggze is the core maintainer of FluentBit Operator, @huanggze do you have any comments?
Regards,
Benjamin Huo

Thanks for your message.
Our vision is to make a tool for cluster operators to build k8s logging layer flexibly and efficiently. As @benjaminhuo mentioned, we start with lightweight Fluent Bit , but will incorporate Fluentd in the future.
Here is our broad features or roadmap:

Automate the deployment of Fluentd and Fluent Bit (as daemonset/deployment)
Configure and reload Fluentd and Fluent Bit dynamically
Switch on/off input, filter and output plugins
Select and group multiple plugins for different logging purposes
Inject sidecar container to collect log files on pod volume
Support full Fluent Bit/Fluentd plugins (Loki will definitely be includede.)

@alexandre-allard-scality we developed FluentBit Operator using kubebuilder.
@huanggze which kubebuilder version we use? Maybe we coud put kubebuild related info into contribute guide as well.

The project is build with v2.3.0

Thanks for the quick answers,
Ok, that's cool, we totally agree on the fact that Fluentd must be optional, that's the reason we didn't chose logging-operator.
As I said, we're currently working on our log centralization system, so we will probably start working on the Loki output plugin integration soon. We will let you know if we have question regarding the good practices or anything else.

Thanks for the quick answers,
Ok, that's cool, we totally agree on the fact that Fluentd must be optional, that's the reason we didn't chose logging-operator.
As I said, we're currently working on our log centralization system, so we will probably start working on the Loki output plugin integration soon. We will let you know if we have question regarding the good practices or anything else.

We're looking forward to your loki output plugin :)
Let us know if you need any other info
Regards,
Ben

@alexandre-allard-scality , you can join our slack channel sig-observability anytime you have questions

Loki plugin has already been added.
Close this issue for now


[Feature request] Accept Regex expressions in Scan

Proposal
Often I find myself that some clauses are more easily parsed with a regex than with PikaParser clauses. The solution is to user a Scan in a way similar to:
rules = Dict(
    ...,
    :id => PikaParser.scan() do x
        matched = match(r"^[a-z][a-zA-Z0-9_]*", x)
        isnothing(matched) && return 0
        length(matched.match)
    end,
    ...,
)

It would be great if we could just pass the regex to scan.
Unsolved issues
Only regex of the form r"^..." should be accepted. If the ^ clause is not present, then the regex will search the pattern along all the input.

notes for self when I get to this:

we MIGHT want to abuse the do notation for writing folds directly into the grammar, as with bison
the usual form of regex semantics is slightly inconvenient for exact matching, and we unfortunately don't have much freedom in regex implementations to support syntax similar to eg. flex. I'd suggest that for simplifying matters we do 2 helper functions, one if these regex_to (scans everything to the match, including the match) and second regex_before (scans everything to the match without the match), with an optional argument to select which match group is actually being selected. (Can be done by taking .offset and .ncodeunits from m.match or m.captures[N].)
The "to" and "before" variants also allow folks to implement various useful stuff like not_followed_by directly into lexing


removed dependencies

Nice, passes all test. Can you explain how this works exactly? Thanks :+1:

Is this better than #2? Right now I am leaning towards #2

#2 is good, just not readable for most people. Personally I'd go with that one.

Cool, I am going to pull it, but I have also asked him for an explanation to how it works. Fortunately, with the tests we know it works with all edge cases. Can you take a peek at the tests and let me know if you see anything missing?


Find replacement for DI

The di (dependency injection) module we currently use is very outdated and the di setup we have is pretty hard to understand, especially for people new to the code base.
Currently all plugins though depend on it, so we need to find a backwards compatible solution or at least an interface that is as simple to use as the current one for plugin authors.

IMHO
I really like idea of dependency injection :neckbeard: .
Only one thing in karma's DI like a magic. It is DI using comment in function's argument:

fooReporter(/*config.client*/client) { return client }

@dignifiedquire why do you want replace it? Only because people can not understand it?
Really they don't understand it or maybe we could improve DI's API make it more obvious if it's not ovious now
✌

@maksimr I am not sure, maybe just update things to use a newer library. If we are happy with DI itself I am happy to just move to a maintained library.

After doing a short review of how often we actually use di, it seems like it's not really a requirement for the project and could probably be refactored out. I think refactoring it out would make the whole application be less "magic" and probably help with static analysis (via tools like TypeScript).

Main issue is, as you said, refactoring it out of Karma without breaking things for plugin authors.

@dignifiedquire would you be open to a PR utilizing injection-js? Could also combine that feature with moving from pseudo-classes to proper ECMAScript classes, since that should make injection easier. Currently my TypeScript PR (#2893) is blocked by a bunch of ambiguous typing that is a result of pseudo-classing making things unclear.

I'm curious about your definition of pseudo-classes. Are you talking about code like url
https://github.com/karma-runner/karma/blob/39d378d20dee61a88572225db9e1855da3adb346/lib/url.js#L11
which defines methods on .prototype (should be converted to es6 classes) or like dots
https://github.com/karma-runner/karma/blob/39d378d20dee61a88572225db9e1855da3adb346/lib/reporters/dots.js#L13 where methods are defined directly on the objects (where changes may have broader consequences)?
Or both ;-)

Both, although the former is more egregious. I was wrestling with type ambiguity in file-list the other night and the easiest solution was rewriting the whole thing as an ES6 class.

I would love to see the code base upgraded to use class, const, let and arrow functions.
I am very open to use a different di library, as long as we can keep all existing plugins compatible. There are a lot of plugins out there, from various authors which rely on the current workings to work. Maintained + tested is the base requirement. But I would like to stay away from compiling things, so ideally using the regular es6 version, no typescript class annotations

I suggest tackling es6 and new DI separately, starting with a simple case, and developing a documented recipe for these changes. I guess the test coverage for the plugin space is not sufficient to ensure that a passing karma test will ensure plugins work. So patience and documentation will be essential.

Does the old DI work with new class syntax? My concern is that rewriting them separately might raise unexpected compatibility issues and it might just be best to make any breaking changes simultaneously instead of in multiple steps.

es6 classes can be used with es3 code; it may or may not be pretty and some investigation may be needed.
Changing the DI is, I believe, a much bigger issue because it is  part of how plugins interface with karma.  We would need some kind of migration strategy where old and new DI are both allowed, then we reach-out/DIY the changes for the top plugins, then deprecate the old DI.


ocp/ocp4 script cleanup

Builds on https://github.com/openshift/aos-cd-jobs/pull/1721 so only the last two commits are new.
Just some things I wanted to fix before adding the real work I've been doing...

/assign @adammhaile
/assign @tbielawa


[REGRESSION]: DeleteFiles fails with no such file or directory with filename containing emoji

New issue checklist

[X] I searched for existing GitHub issues
[X] I read pipeline troubleshooting guide
[X] I checked how to collect logs

Task name
DeleteFiles
Breaking task version
1.231.1
Last working task version
1.231.0
Regression Description
Expected: DeleteFiles to scan through all files without issue
Actual: DeleteFiles error when trying to parse one specific file within this Node directory. It states that this file does not exist. (We noted that this was the first file that contained emojis).
Environment type (Please select at least one enviroment where you face this issue)

[ ] Self-Hosted
[X] Microsoft Hosted
[ ] VMSS Pool
[ ] Container

Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Windows 2019
Relevant log output
2023-12-15T22:49:49.6680312Z ##[section]Starting: DeleteFiles
2023-12-15T22:49:49.6780409Z ==============================================================================
2023-12-15T22:49:49.6780526Z Task         : Delete files
2023-12-15T22:49:49.6780582Z Description  : Delete folders, or files matching a pattern
2023-12-15T22:49:49.6780674Z Version      : 1.231.1
2023-12-15T22:49:49.6780726Z Author       : Microsoft Corporation
2023-12-15T22:49:49.6780789Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/delete-files
2023-12-15T22:49:49.6780897Z ==============================================================================
2023-12-15T22:50:16.9547428Z ##[error]Unhandled: Failed find: ENOENT: no such file or directory, lstat 'D:\a\_work\1\b\src\third_party\electron_node\deps\v8\test\message\unicode-filename-🎅🎄.js'
2023-12-15T22:50:16.9550552Z ##[error]Error: Failed find: ENOENT: no such file or directory, lstat 'D:\a\_work\1\b\src\third_party\electron_node\deps\v8\test\message\unicode-filename-🎅🎄.js'
    at Object.find (D:\a\_work\_tasks\DeleteFiles_b7e8b412-0437-4065-9371-edc5881de25b\1.231.1\node_modules\azure-pipelines-task-lib\task.js:1000:15)
    at D:\a\_work\_tasks\DeleteFiles_b7e8b412-0437-4065-9371-edc5881de25b\1.231.1\deletefiles.js:29:25
    at Object.<anonymous> (D:\a\_work\_tasks\DeleteFiles_b7e8b412-0437-4065-9371-edc5881de25b\1.231.1\deletefiles.js:101:3)
    at Module._compile (node:internal/modules/cjs/loader:1241:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1295:10)
    at Module.load (node:internal/modules/cjs/loader:1091:32)
    at Module._load (node:internal/modules/cjs/loader:938:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)
    at node:internal/main/run_main_module:23:47
2023-12-15T22:50:16.9860863Z ##[section]Finishing: DeleteFiles

Full task logs with system.debug enabled
No response
Repro steps
# Some files and directories should not be published.
    - task: DeleteFiles@1
      inputs:
        SourceFolder: ${{ parameters._workingDirectory }}
        Contents: |
          **/.azure-devops
          **/.git
          **/.npmrc
          **/.sdl
          src/microsoft/README.md
          src/third_party/depot_tools/win_toolchain/vs_files

@mlaurencin, thanks for reporting!
The error is reproduced due to an issue in node itself. As soon as we are able to update the dependency to include this fix, I will notify you.

@mlaurencin DeleteFilesV1 v1.235.0 is already available.
Could you confirm the fix?

I'm closing this issue for now.
Feel free to reopen if it's still relevant for you.


OpenChat API Non-Deterministic Behavior

Issue:
The OpenChat API appears to exhibit non-deterministic behavior in RAG applications using the same user query.
Details
When using the same user query, I get different answer results. In fact, I am not getting the same output texts with the same user query.
Versions
vllm==0.3.2
ochat=3.5.1
Openchat configuration
model='openchat/openchat-3.5-1210', tokenizer='openchat/openchat-3.5-1210', tokenizer_mode=auto, revision=None, tokenizer_revision=None, trust_remote_code=False, dtype=torch.float16, max_seq_len=8192, download_dir=None, load_format=auto, tensor_parallel_size=2, disable_custom_all_reduce=True, quantization=None, enforce_eager=False, kv_cache_dtype=auto, device_config=cuda, seed=123

@SkanderHellal Thanks for your PR. Can you check if the issue still happens?

@imoneoi Thank you for your reply,  now openchat has a deterministic behavior with seed fiw. I close the issue.


Update README.md

Fix typo 🌷

Thanks! 😄

Coverage remained the same at 100.0% when pulling f6a3363a2fc0a8c46faf6325d50be68b632cef71 on unional:master into eea14afbff76859fc936cc5524796cbcf4964055 on blakeembrey:master.

😀


[KOGITO-4438] PostgreSQL research about doing optmistic locking

It includes optional lock for optimistic concurrency using version for PostgreSQL persistence.
Signed-off-by: Swati Kale<EMAIL_ADDRESS>Many thanks for submitting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[ ] You have read the contributors guide
[ ] Your code is properly formatted according to this configuration
[ ] Pull Request title is properly formatted: KOGITO-XYZ Subject
[ ] Pull Request title contains the target branch if not targeting master: [0.9.x] KOGITO-XYZ Subject
[ ] Pull Request contains link to the JIRA issue
[ ] Pull Request contains link to any dependent or related Pull Request
[ ] Pull Request contains description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket

How to retest this PR or trigger a specific build:

Pull Request
Please add comment: Jenkins retest this

Quarkus LTS checks
Please add comment: Jenkins run LTS

Native checks
Please add comment: Jenkins run native

Full Kogito testing (with cloud images and operator BDD testing)
Please add comment: Jenkins run BDD
This check should be used only if a big change is done as it takes time to run, need resources and one full BDD tests check can be done at a time ...

Can one of the admins verify this PR? Comment with 'ok to test' to start the build.

Can one of the admins verify this PR? Comment with 'ok to test' to start the build.

Can one of the admins verify this PR? Comment with 'ok to test' to start the build.

Can one of the admins verify this PR? Comment with 'ok to test' to start the build.

Can one of the admins verify this PR? Comment with 'ok to test' to start the build.

Can one of the admins verify this PR? Comment with 'ok to test' to start the build.

Can one of the admins verify this PR? Comment with 'ok to test' to start the build.

@tiagodolphine , Can you pls start the build?

@cristianonicolai , Can you pls start the buid? Need  'ok to test' .

ok to test

The Linux check has failed. Please check the logs.

jenkins retest this

The Linux check has failed. Please check the logs.

The Linux check is successful.

jenkins retest this

jenkins retest this

@cristianonicolai , please start the build, as it does not get started automatically.

jenkins please retest this

The Linux check is successful.

The Linux check has failed. Please check the logs.

jenkins please retest this

The Linux check is successful.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

The Linux check has failed. Please check the logs.

@swati-kale I think overall we dont need to create db level locking, but make sure when updating that it matches the version in the db. I guess that can simplify a lot the implementation here.

I removed the db locking provided by postgresql.  Now matching the version while updating the process instance. For delete version matching is not necessary as the subsequent requests will not find the process instance to delete.

The Linux check has failed. Please check the logs.

The Linux check has failed. Please check the logs.

The Linux check has failed. Please check the logs.

The Linux check has failed. Please check the logs.

The Linux check has failed. Please check the logs.

The Linux check has failed. Please check the logs.

jenkins please retest this

The Linux check has failed. Please check the logs.

The Linux check has failed. Please check the logs.

The Linux check has failed. Please check the logs.

jenkins please retest this

The Linux check has failed. Please check the logs.

jenkins please retest this

The Linux check has failed. Please check the logs.

jenkins please retest this

The Linux check has failed. Please check the logs.

The Linux check has failed. Please check the logs.

jenkins please retest this

The Linux check has failed. Please check the logs.

jenkins please retest this

The Linux check has failed. Please check the logs.

@swati-kale needs rebase

The Linux check has failed. Please check the logs.

jenkins please retest this

The Linux check is successful.


Include pattern matching mechanism

Some popular apps like discord do not yet have a stylix module. A hacky way to automate such themes is creating personal key-value map  between base16 theme names and specific themes for said applications. Said maps can then be indexed with a function like
    get = themeMap:
      themeMap.${config.lib.stylix.scheme.scheme}
        or themeMap.default.${config.stylix.polarity or "dark"}
        or themeMap.default
        or (throw "Theme ${config.lib.stylix.scheme.scheme} not found in theme map!");

Example usage:
  home.packages = [ discocss ];
  xdg.configFile."discocss/custom.css".source = config.satellite.theming.get themeMap;

I've been using this approach for a while, and think others might find it useful. Just to be clear, stylix would not provide such modules/mappings, but would simply provide the pattern matching helper.

Although this seems useful, I don't think it should be included in Stylix because it needs a lot of manual setup and only works for certain schemes. Perhaps you could publish it as a separate repository which works alongside?


theme prop is not passed down to styled component

Environment

npx envinfo --system --binaries --npmPackages styled-components,babel-plugin-styled-components --markdown
System:

OS: macOS 13.5.1
CPU: (10) arm64 Apple M1 Pro
Memory: 176.70 MB / 32.00 GB
Shell: 5.9 - /bin/zsh

Binaries:

Node: 14.18.3 - ~/.nvm/versions/node/v14.18.3/bin/node
Yarn: 1.22.19 - ~/.nvm/versions/node/v14.18.3/bin/yarn
npm: 6.14.15 - ~/.nvm/versions/node/v14.18.3/bin/npm

Reproduction
https://codesandbox.io/s/styled-components-base-forked-s54vmg?file=/index.js
Steps to reproduce
Create component which accepts theme prop, for example enum or string
Style it using styled-components
Pass prop theme to styled component
Expected Behavior
Prop passed to styled component should work
Actual Behavior
Theme prop is not getting passed. Probably because styled-component expects it to be Theme object, instead of anything else.
Currently I'm using an external dependency with component which accepts theme prop. I cannot style it with styled components, because string theme prop is not being passed down.

No external dependencies are required. Theme props work differently with styled-components. You can find the documentation here.

No external dependencies are required. Theme props work differently with styled-components. You can find the documentation here.

You don't understand. You can check my codesandbox link for reference.
I have an external component which requires theme prop, which is a string ("red", "blue" etc). Besides that, I want to style it using styled-components.
After wrapping it in styled, my theme prop is not being passed to that external component, because it's taken by styled wrapper...

You're correct, I see what's going on. It seems that styled-components may need something to distinguish between their own theme prop.
However, it may be inconsistent in the first place to use a theme in an non-styled-component and then wrapping it with styled. In your codesandbox example, simply changing theme to any other prop name will suffice. Ideally, when working with themes with styled-components, you're using a ThemeProvider where you can use the theme prop to override colors. If you're attempting to use theme in the context you've provided, it's likely just worth naming it something else to avoid the issue entirely.
Please let me know if there's something I am missing here, and I will look into styled-components to see if there's something better that could be done if this is problem.

I faced the same problem. Styled-components version 6 doesn't pass prop name theme to styled component .
Working solution is wrapping components with different prop name, like buttonTheme and then pass buttonTheme as theme to other component, but it's frustrating
Maybe this code does it
Maybe it's better to make configurable theme prop name to styled components using StyleSheetManager

I also have this problem


jgit clean yy should clean without prompting for input

If you really trust jgit to delete your worktrees and branches, using the command jgit clean yy will act the same as if you do:
$ jgit clean
...
WORKTREES TO DELETE
  ...
Proceed? y/(n): y
...
BRANCHES TO DELETE
  ...
Proceed? y/(n): y

Implemented by 3a3b189


Change Node.js unit test require.

This allows for compatibility with partial Veneers.

Codecov Report

Merging #1264 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1264   +/-   ##
=========================================
  Coverage     86.21%   86.21%
  Complexity     3797     3797
=========================================
  Files           380      380
  Lines         15102    15102
  Branches       1686     1686
=========================================
  Hits          13020    13020
  Misses         1631     1631
  Partials        451      451

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 fd5b638...aaa9a23. Read the comment docs.


Issue 1598: fixes python codegeneration comment block bug

Description
This PR fixes the issue, that it was possible to generate faulty code by adding an escape char "\n" in the comment block.
Removing the method visitStmtTextComment in the MicrobitPythonVisitor class which did not sanitize the input for escape characters fixes the issue, since the original visitStmtTextComment in the AbstractPythonVisitor is already sanitizing it properly.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Run ReuseIntegrationTestsAsUnitTests
Imported Microbit/Robotino file into the lab which contains the problematic block with escape characters

accepted with https://github.com/OpenRoberta/openroberta-lab/commit/c96962dbe69bed166ba4f52148d4452c7d8ec614


typings install fails on latest commit

Hey! Amazing work on this. Even without running it yet, I can see the level of work and attention put in.
I just noticed that the latest commit seems to break typings install:
typings ERR! message Attempted to compile "lodash" as an ambient module, but it looks like an external module.

I don't know a ton of TypeScript but it looks like this is important:
https://github.com/michaelgrosner/tribeca/blob/master/typings.json#L17
I played around for a little bit trying to see if I could fix it but I didn't manage to.
Let me know if I can help!

I'm also keen to experiment with this but hitting the same error when trying to build the docker image.

Sorry about this one. I must have introduced it in my last PR to update all the modules in Tribeca. I'll work on a fix now...

Take a look at the PR I just merged in #95 and let me know if that fixes it.


[release/1.7] Avoid arch info in the sed/replace when building cri-cni-containerd.tar.gz

Cherry pick of https://github.com/containerd/containerd/pull/10964 to release/1.7 branch

/assign @estesp @mikebrow @akhilerm

The 2  failing prow job checks can be ignored as they are not relevant on the release/1.7 branch, but got added here when the same branch was used previously.

The one failing check was the wrong prow test.. e2e-node is wrong .. for 1.7 we only run on the e2e 1.7 node test


Add a PerformanceOverlay driver performance test

Once upon a time, the PerformanceOverlay itself is using ~5ms per frame. Now we've made it faster but we have no benchmarks that guard its regression. Let's add a devicelab driver test to continuously benchmark it.

We still don't have any spare resources to address this. AFAIK, the last improvement we made for PerformanceOverlay is https://github.com/flutter/engine/pull/6225 by @GaryQian . Having a slow PerformanceOverlay could be risky as we can receive false positive performance issues. So far we haven't received any so I'll mark it as low priority for now.

Closing as obsolete


ol.interaction.Translate: Feature disappears while moving it far westward/eastward

I don't know if this is a bug or if I just don't understand the behavior, neither am I a professional geo-calculation guy.
A feature, which is moved far westward/eastward, using ol.interaction.Translate, disappears at a certain value of longitude.
I've prepared a https://jsfiddle.net/cha8wjgz/1/ for demonstration. While moving, it's logging the event.coordinate and ol.proj.toLonLat(event.coordinate) to the console. While latter one looks good, in terms of position, the internal OL longitude value increases and decreases respectively (east / west). I can understand that, because if it's being moved around world 1, world 2 and so on, it needs to de/increase.
For me it looks like the feature is being moved out of OL bounds, or something. Even when the feature disappears from the map, the event.coordinates are still being logged and increasing/decreasing farther.

As stated initially, I don't fully understand this behavior or if it's even desired. So, could someone please explain that to me?

Unfortunately this doesn't work for me because I do actually have 2 markers and a line between them (it's a ruler tool). If I set wrapX: false the lines are not drawn correctly.
I've played around a bit and started to use the translateend event to kind of reset the feature's position to world 1.
https://jsfiddle.net/wtyjcous/
translate.on('translateend', function(evt) { feature.getGeometry().setCoordinates(ol.proj.fromLonLat(ol.proj.toLonLat(evt.coordinate))) });
This works for me, at least it looks like what I wanted to achieve.
But now another, at least from my perpesctive, strange thing happens.
evt.coordinate is not the coordinate of the Point feature, but the coordinate of the click event. So when resetting the feature's position, it kind of bounces a certain amount of pixels, depending on the click position on the feature (click on the feature Style, which can be an image or something).
Can I somehow retrieve the Point position from the Translate process, and not the position of the click? Are there any offsets to the Point itself?

You can move the feature's coordinate into the real world without using evt.coordinate
  translate.on('translateend', function(evt) {
    feature.getGeometry().setCoordinates(ol.proj.fromLonLat(ol.proj.toLonLat(feature.getGeometry().getCoordinates())))
  });

https://jsfiddle.net/rmujL0yg/

Yes, this works. Thanks. Although I'm still not sure about the described problem/behavior. Anyway, as it's working for me now, I'll close this issue.


libreoffice-fresh does not download .MSI file

v6.0.5 does not download the .msi file
libreoffice 5.4.4 gives no error but cannot see .msi file.

Running ChocolateStore to make package...
Downloading: libreoffice-fresh.6.0.5.nupkg
Download Failed: https://download.documentfoundation.org/libreoffice/stable/6.0.5/win/x86/LibreOffice_6.0.5_Win_x86.msi
System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the
transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibl
y closed by the remote host
at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
--- End of inner exception stack trace ---
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
at System.Net.TlsStream.CallProcessAuthentication(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.ConnectStream.WriteHeaders(Boolean async)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetResponse()
at ChocolateStore.PackageCacher.DownloadFile(String url, String destination) in C:\temp\ChocStore\src\ChocolateStore\PackageCacher.cs:line 72
Download Failed: https://download.documentfoundation.org/libreoffice/stable/6.0.5/win/x86_64/LibreOffice_6.0.5_Win_x64.msi
System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the
transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibl
y closed by the remote host
at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
--- End of inner exception stack trace ---
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
at System.Net.TlsStream.CallProcessAuthentication(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.ConnectStream.WriteHeaders(Boolean async)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetResponse()
at ChocolateStore.PackageCacher.DownloadFile(String url, String destination) in C:\temp\ChocStore\src\ChocolateStore\PackageCacher.cs:line 72

Works on my end so this must have been a one time thing ..


Add my-auto

Hello.
Adding "auto" suffix to margin vertical utilites can be usefull with flexbox:

Centered on rest block

        Some button text

How it's currently looks

How I'm expected to be

This is super interesting and is the first time I've ever seen vertical margins of auto do anything at all 😄
I think what we're going to do is add this to the core utility set hardcoded like the horizontal auto variations for now, and then in the next breaking release (0.2.0) we'll move all of it out to the config, so you'll just have an 'auto': 'auto' value in your Tailwind config file under margins.

In the mean time don't forget it's incredibly easy to add these to your own project:
@tailwind preflight;

@responsive {
  .mt-auto { margin-top: auto; }
  .mb-auto { margin-bottom: auto; }
  .my-auto { @apply .mt-auto .mb-auto; }
}

@tailwind utilities;


Alignment

alignment pack

Everything looks great. Looked through the code, and built the branch and loaded things up in game to check it out.
I made two very minor changes -- making the power cards using SELF instead of NONE for target, just to be consistent with the base game even though I'm pretty sure it doesn't really matter.


Conjugate Gradient

CuPy example

Thank you for the review. I removed the scipy part because we have to set N as a very large number to make GPU faster than scipy. I think it's inappropriate as an example.

Thank you for the review. To evaluate the equality of x, I print the Euclidean distance between true x and computed x rather than b.

jenkins, test this please

Test passed. LGTM except the comments.

LGTM


Quoting is still ' for some strings when dumping even if quotingType: '"' is set in dump config

My js-yaml config for dumping is:
dump: {
  lineWidth: -1,
  quotingType: '"',
  sortKeys: true,
},

I'm still getting single quoted strings.
For example, look at this dumped output:
option:
  - Keeps people safe
  - 'Prevents flight diversions, delays or cancellations'
  - Detects in and around the airport territory

Why second option is quoted? (Just because of comma?) And why it is quoted in single quotes?

this:
console.log(require('js-yaml').dump({
  option: [
    'Keeps people safe',
    'Prevents flight diversions, delays or cancellations',
    'Detects in and around the airport territory'
  ]
}, {
  lineWidth: -1,
  quotingType: '"',
  sortKeys: true
}))

prints this:
option:
  - Keeps people safe
  - Prevents flight diversions, delays or cancellations
  - Detects in and around the airport territory

without any quotes in current js-yaml 4.1.0
please provide a code sample we can reproduce

uh... I believe you're using js-yaml version 3.14.1 or earlier, which doesn't have quotingType option at all
please upgrade to the latest one, it won't quote commas anymore


redundant rerendering on first time scroll

When scrolling the table for the first time the cluster rerenders and content has bad flashing effect.
I investigated the problem. In my case problem in method getRowsHeight at line
opts.item_height = nodes[Math.floor(nodes.length / 2)].offsetHeight;
opts.item_height equals 0 during initialization (but nodes exists)
so method getClusterNum return Infinity because of division by zero
i've added hot fix
    getClusterNum: function () {
      this.options.scroll_top = this.scroll_elem.scrollTop;
      if (this.options.cluster_height == this.options.block_height) return 0;
      return Math.floor(this.options.scroll_top / (this.options.cluster_height - this.options.block_height)) || 0;
    }

now it works fine for me. Would be cool if you can fix it right way.
I'm using clusterize as directive in Vuejs framework.

Hey

opts.item_height equals 0 during initialization (but nodes exists)

how this could be possible if nodes exists?
could you please create example at codepen?

Here is an example. http://codepen.io/anon/pen/ORNagp
I've figured out that it's caused by async loading of data and changing between different states.

Whoa, great catch @kamax1 !

Just pushed v0.17.1
Try this http://codepen.io/NeXTs/pen/GjkZON?editors=1010
Once cdn updates you could remove clusterize sources from my codepen and add script tag to cdn with v0.17.1
Pay attention how I changed html and loaded. If your version was important to you - use it, but there would be additional height determination (because until loaded is false - vue doesn't render table so Clusterize could not determine row's height. And will actually investigate row by triggering scroll (when obviously investigation of row height during .update is preferred))

Thank you for the fast response. Works perfectly!


Add support to install nerdctl and buildkit with the alpine-iso template

All 3 binaries are now available in Alpine 3.17, from buildctl and buildkit <sic> and nerdctl apks.

Will make a separate PR to make the setuid chmod optional, to require using sudo with nerdctl...
Originally posted by @afbjorklund in https://github.com/lima-vm/alpine-lima/issues/77#issuecomment-1357393401

I've only created this issue because I want to close https://github.com/lima-vm/alpine-lima/issues/77.
I'm not sure if we care about supporting containerd.system: true for Alpine (although the code would then also work for the regular non-ISO image.
I'm also fine with closing this issue and leaving it to the user to install additional packages via provisioning scripts.

I'm also fine with closing this issue and leaving it to the user to install additional packages via provisioning scripts.

That is OK with me, the original issue was only to split the installation in the ISO into the same three components...

I think the nerdctl containerd-rootless-setuptool.sh script had some issues, when trying to run it outside of systemd.

https://github.com/lima-vm/lima/issues/310

containerd-rootless-setuptool.sh is dedicated for systemd, but containerd-rootless.sh should work without it


DUPLO 16595 Bug fix on update of taskdefnition

Overview
This PR has fix for error related to duplocloud_ecs_task_definition resource update.
Summary of changes
Now on update of task_definition
exisiting service related to task_definition is getting destroyed
task_definition getting destroyed
task_definition got created
service related to task_definition got created
This PR does the following:

Made arn field force new. Which helps in updating task-definition along with associated service
...

Testing performed

[ ] Using unit tests
[ ] Manually, on my local system
[✓ ] Manually, on a remote test system

Describe any breaking changes

...

Task linked: DUPLO-16595 [Bug] Terraform wants to replace ECS task definition in the case of an image update

@tahir-duplo Merge it based on Vishaal Chhabria  response. Coordinate with Shabri


Extract "select all" behavior to new SELECT_ALL_COMMAND

Move the "select all" behavior from LexicalEvents into a new SELECT_ALL_COMMAND. This will make overriding the default behavior easier for developers and matches the way that commands like copy, paste, arrow up, etc are handled.
Overriding "select all" is not common, but several applications have introduced context-aware versions of the behavior that are difficult to change with lexical's current implementation. For example, an editor may choose to have the first invocation of ⌘ + a select the current paragraph and a subsequent ⌘ + a select the entire document.

I'm good with this, but I think if someone is using LexicalEvents directly (looks like this can be called via setRootElement) this could break them. I don't think this is a common case, but might be more common outside in vanilla js implementations.
I think we might want to version bump unless I'm wrong about this.

Sorry for hijacking the thread, but on the off chance anyone also gets issues after upgrading lexical: in my case dependabot created a PR that updated lexical from 0.11.3 to 0.12.0 and suddenly CTRL+A stopped working, even though I used RichTextPlugin.
What was causing this? In my case @lexical/react was still pointing to 0.11.3. Updating it to 0.12.0 (so that both lexical and @lexical/react now point to  0.12.0) fixed the issue.
Which makes sense since this PR changes multiple packages.
Anyway, HTH.


Improved Docs

Invalid

May I know the reason why.?
cuz it's not like you are losing anything..?

Please make meaningful contributions if you want to participate in Hacktoberfest, not just README edits where you add one space and expect a PR to be merged

I'm really sorry I didn't see that..
In many I have improved the codings too.
I thought I did codings for every repository.
Sorry for the inconvenience.!
Hope you understand.!
On Mon, 12 Oct 2020, 9:04 pm Faiz Malkani<EMAIL_ADDRESS>wrote:

Please make meaningful contributions if you want to participate in
Hacktoberfest, not just README edits where you add one space and expect a
PR to be merged
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/faizmalkani/appsite/pull/14#issuecomment-707192567,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARGRFRIYAG6J6YVO3R22FUDSKMOYXANCNFSM4R7ORBLA
.


Upgrade NiGoApi to v0.0.9

Q
A

Bug fix?
no

New feature?
yes

API breaks?
no

Deprecations?
no

Related tickets
-

License
Apache 2.0

What's in this PR?

Upgrade the NiGoApi module to v0.0.9
Why?

To have all the latest modification from the NiFi Api from the 1.23.2 version.
Checklist

[ ] Implementation tested
[X] Error handling code meets the guideline
[X] Logging code meets the guideline
[X] User guide and development docs updated (if needed)
[x] Append changelog with changes

Still need to be tested but it should be good.


Replace "PCI appName" in mail templates

 Replace "The Managing Board of PCI {{appName}}" by "The Managing Board of {{appName}}" in all the email templates of all the PCI websites


Separator character in mini.statusline

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md

Module(s)
mini.statusline
Description
Any thoughts of having a separator character option between sections in mini.statusline to support some of the "angled" or "rounded" dividers you see in lualine and others?

Thanks for the suggestion!
All sections in 'mini.statusline' are plain functions which return strings. It is left to user to combine them however they want. Here is how it is done by default. For the most common case of combining groups, there is combine_groups() which is a bit smarter version of plain string concatenation. Outside of that it is expected to manipulate section strings manually.
Main reason for this kind of design is that it (like like it) would require almost as much code to configure inside setup() as to implement manually inside function. That is assuming configuration is kept flexible enough to allow different separators for different consecutive sections/groups.
Closing as not planned.

I had a bit of trouble getting this to work within my combine_groups fn. Here's my current setup in case anyone's interested, using this custom function:
function create_statusline_separator(before_hl, after_hl, char)
  local hl_name = string.format("Statusline%s%s", before_hl, after_hl)
  vim.cmd(
    string.format(
      [[ hi! %s guifg=%s guibg=%s ]],
      hl_name,
      string.format("#%06x", vim.api.nvim_get_hl_by_name(before_hl, true).background),
      string.format("#%06x", vim.api.nvim_get_hl_by_name(after_hl, true).background)
    )
  )
  return "%#" .. hl_name .. "#" .. char
end

If this can be done easier or better, please ping me!

If this can be done easier or better, please ping me!

Generally, this looks fine. However, it should be noted that this function (config.content.active and hence utils.create_statusline_separator()) will be called very frequently. So I'd some precomputation instead of two nvim_get_hl_by_name calls per create_statusline_separator (which is 6 calls per statusline redraw). Furthermore, I'd use this function only if either of before_hl or `after_hl is not known in advance, which is only for the first call.

I had a bit of trouble getting this to work within my combine_groups fn. Here's my current setup in case anyone's interested, using this custom function:

Thanks for this - I tried, but couldn't get there :-)
One item - if you have "mode" as one of the parameters (before_hl, after_hl) then it gets an error when you switch modes.
This may very well be a config issue on my side - it complains that 'Invalid highlight name "Insert"' or whatever
Thought I would point it out...

@bdillahu you need to pass mode_hl, not mode :)


[dependabot] fix rust dependabot alerts

Fixes current Rust-related Dependabot alerts by upgrading the following packages:
crossbeam-utils, hyper, im, rocksdb
Also renamed scratchpad to diem-scratchpad so Dependabot and cargo audit stop throwing false positives

/canary

:sunny: Canary successful

/land


compute release

https://github.com/Azure/sdk-release-request/issues/3234

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-arm-compute


chore: Add Warnings for event behavior changes

Issue #, if available:
Description of changes:
Checklist:

[ ] Write Design Document (Do I need to write a design document?)
[ ] Write unit tests
[ ] Write/update functional tests
[ ] Write/update integration tests
[ ] make pr passes
[ ] Write documentation

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Closing this, as it has gone stale. We still want to pursue this in the near future, just not in the direct moment.


Decrease Memory footprint

Mime-types 2.6.1+ has a columnar store that only loads the data that is needed for a drastically reduced memory footprint. cc/ @jeremyevans @halostatue

Very belatedly, thank you for the contribution!


dhcpcd: 10.0.6 -> 10.1.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/NetworkConfiguration/dhcpcd/releases.
meta.description for dhcpcd is: Client for the Dynamic Host Configuration Protocol (DHCP)
meta.homepage for dhcpcd is: https://roy.marples.name/projects/dhcpcd
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS

[!CAUTION]
A test defined in passthru.tests did not pass.

found 10.0.10 with grep in /nix/store/kh7r06cz855inyyqsr37nhbxxxrx06k7-dhcpcd-10.0.10
found 10.0.10 in filename of file in /nix/store/kh7r06cz855inyyqsr37nhbxxxrx06k7-dhcpcd-10.0.10

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

461 total rebuild path(s)

461 package rebuild(s)

First fifty rebuilds by attrpath

CuboCore.coretoppings
adapta-gtk-theme
ags
airgeddon
appgate-sdp
autosuspend
ayatana-indicator-datetime
ayatana-indicator-display
ayatana-indicator-messages
ayatana-indicator-power
ayatana-indicator-session
ayatana-indicator-sound
blueman
bottles
bottles-unwrapped
breath-theme
budgie-analogue-clock-applet
budgie-control-center
budgie-desktop
budgie-desktop-with-plugins
budgie-gsettings-overrides
budgie-session
budgie-user-indicator-redux
cage
cagebreak
calligra
cinnamon-common
cinnamon-control-center
cinnamon-gsettings-overrides
cinnamon-screensaver
cinnamon-session
cinnamon-settings-daemon
cinnamon.cinnamon-common
cinnamon.cinnamon-control-center
cinnamon.cinnamon-gsettings-overrides
cinnamon.cinnamon-screensaver
cinnamon.cinnamon-session
cinnamon.cinnamon-settings-daemon
cinnamon.muffin
cinnamon.nemo-fileroller
cinnamon.nemo-with-extensions
claws-mail
clight
cobang
collision
colloid-kde
cosmic-comp
dbmonster
dbus-test-runner

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/b48d698f48b7c56378d283cf6e363119cd4b65c6#dhcpcd

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

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 120m and timed out

Maintainer pings
cc @edolstra for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/NetworkConfiguration/dhcpcd/releases.
meta.description for dhcpcd is: Client for the Dynamic Host Configuration Protocol (DHCP)
meta.homepage for dhcpcd is: https://roy.marples.name/projects/dhcpcd
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 10.1.0 with grep in /nix/store/vc21wgdk08hxfdgq0prlha2hzsgbdwc3-dhcpcd-10.1.0
found 10.1.0 in filename of file in /nix/store/vc21wgdk08hxfdgq0prlha2hzsgbdwc3-dhcpcd-10.1.0

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

485 total rebuild path(s)

485 package rebuild(s)

First fifty rebuilds by attrpath

CuboCore.coretoppings
adapta-gtk-theme
ags
airgeddon
appgate-sdp
autosuspend
ayatana-indicator-bluetooth
ayatana-indicator-datetime
ayatana-indicator-display
ayatana-indicator-messages
ayatana-indicator-power
ayatana-indicator-session
ayatana-indicator-sound
blueman
bottles
bottles-unwrapped
breath-theme
budgie-analogue-clock-applet
budgie-control-center
budgie-desktop
budgie-desktop-with-plugins
budgie-gsettings-overrides
budgie-session
budgie-user-indicator-redux
cage
cagebreak
cinnamon-common
cinnamon-control-center
cinnamon-gsettings-overrides
cinnamon-screensaver
cinnamon-session
cinnamon-settings-daemon
cinnamon.cinnamon-common
cinnamon.cinnamon-control-center
cinnamon.cinnamon-gsettings-overrides
cinnamon.cinnamon-screensaver
cinnamon.cinnamon-session
cinnamon.cinnamon-settings-daemon
cinnamon.muffin
cinnamon.nemo-fileroller
cinnamon.nemo-with-extensions
claws-mail
clight
cobang
collision
colloid-kde
cosmic-comp
dbmonster
dbus-test-runner

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/4f4657a495a3a818967a1e5708d4f8d7d8cad01f#dhcpcd

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

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 120m and timed out

Maintainer pings

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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


Change Terraform output command

[Enter feedback here]
When I use  the below command. It will append the EOT in starting and ending of the file.
echo "$(terraform output kube_config)" > ./azurek8s
So when I run the get nodes command its not working.
kubectl get nodes
error: error loading config file "./azurek8s": yaml: line 2: mapping values are not allowed in this contex
Solution:
Change the command like below
echo "$(terraform output -raw kube_config)" > ./azurek8s
About command will write the raw output to the azurek8s file
 terraform version
Terraform v0.15.1
on linux_amd64
+ provider registry.terraform.io/hashicorp/azurerm v2.58.0

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

ID: 1a750d14-2f87-914e-8715-fac805c8ba3b
Version Independent ID: f8d16dbe-e594-408c-18d8-26fc95de6c65
Content: Create a Kubernetes cluster with Azure Kubernetes Service (AKS) using Terraform
Content Source: articles/terraform/create-k8s-cluster-with-tf-and-aks.md
Service: terraform
GitHub Login: @TomArcherMsft
Microsoft Alias: tarcher

@sri53 Thanks for the feedback. This article has been updated and will publish later today (PST).