Agent possibly reporting Lambda function time outs incorrectly

Agent Environment
We are using the following Datadog Lambda layers:

arn:aws:lambda:us-east-1:464622532012:layer:Datadog-Node18-x:96
arn:aws:lambda:us-east-1:464622532012:layer:Datadog-Extension:46

Our Lambda functions are using the Node.js 18.x runtime and x86_64 architecture.
Describe what happened:
On multiple occasions, we have seen error messages that look like this that we believe may not be correct.

The pattern we have observed is that there is an actual instance of a Lambda function timing out (i.e., the execution time exceeding the Lambda function’s configured time out). What happens next is subsequent invocations of that same Lambda function appear to execute successfully, and well under the 30 time out. Still, they are reported as time-out errors in Datadog. What is more peculiar is the time-out value that is reported is well under 30 seconds:

A specific occurrence of this happened this Thursday in one of our applications. Here are the corresponding Datadog logs. As you can see, the first execution did exceed 30s (31.16s). But all subsequent executions did not.

Further evidence that this is likely an issue attributed to Datadog is we do not see these logs in CloudWatch. Here is a screenshot from CloudWatch for that exact time range as the Datadog query above, and we only see the first instance of the “Task timed out” error message.

The fact that we are also sending these logs to Datadog, but the incorrect time-out logs only appear in Datadog leads me to believe that this incorrect behavior is something caused by Datadog.
I dug into the code for the Datadog agent, and there is one place in that code where it is explicitly sending a “Task timed out” message:
// createStringRecordForTimeoutLog returns the `Task timed out` log using the platform.report message
func createStringRecordForTimeoutLog(l *LambdaLogAPIMessage) string {
	durationMs := l.objectRecord.reportLogItem.durationMs
	durationSeconds := durationMs / 1000
	timeStr := l.time.Format(time.RFC3339Nano)
	return fmt.Sprintf(`%s %s Task timed out after %.2f seconds`, timeStr, l.objectRecord.requestID, durationSeconds)
}

And it looks like this function is invoked in exactly one place:
isTimeoutLog := message.logType == logTypePlatformReport && message.objectRecord.status == timeoutStatus
if isTimeoutLog {
    lc.out <- logConfig.NewChannelMessageFromLambda([]byte(createStringRecordForTimeoutLog(&message)), message.time, lc.arn, message.objectRecord.requestID, isTimeoutLog)
}

I am not sure in what circumstances this block of code will be executed. It feels like the state of the log messages becomes “tainted” after a time-out, and subsequent log events are erroneously categorized as time-outs.
Describe what you expected:
We only expect to see a Task timed out message in our logs when a Lambda function actually times out.
Steps to reproduce the issue:
Have a Lambda function exceed its configured time-out value, then invoke that same function again.
Additional environment details (Operating System, Cloud provider, etc):
See the information provided above regarding our Lambda function configuration.

Apologies that we missed your report of this issue here! This was fixed in v47 of the Extension: https://github.com/DataDog/datadog-lambda-extension/releases/tag/v47.


[rel/17.4] Fix Invalid target architecture 'S390x' error

Description
In commit 3ae5c4aef823 ("Add support for s390x processor architecture") support for S390x architecture was provided for .NET6. This is broken in .NET7. Add missing case statements to fix this for S390x and also Power architectures.
Related issue
https://github.com/microsoft/vstest/pull/2954
Cherry picking #4066

We're a bit late like this one https://github.com/microsoft/vstest/pull/4035 we won't ship on 7.0

@nohwnd
I think https://github.com/microsoft/vstest/pull/4028 should be first merged to branch rel/17.4 to avoid failure in pipeline


[BUG] Warning message You are not authenticated...

I noticed that this warning is only displayed to the user if they have already logged in to the site. In other words, if you have never logged in and change your skins, you will not receive this warning, so you will not be notified that you need to be logged in to synchronize your skins.
Wouldn't it be correct for the message to appear to all users, even if they have never logged in to the site?

That's the intended behavior, if the user for some reason got unauthenticated they are notified they are changing items without reflecting it with the server. Returning users will know they need to authenticate if it's the first time they are accessing the page on the browser.


Fix for #4780

Added padding-top: 0px to avoid wrong placement of the icon as stated by the fix in the fiddle from the issue comment.

Seems to be fixed in #4872. Closing.

Fixed in next release. Removed the @lineHeightOffset


uv pip install under certain circumstances generates long paths (\\?\) on Windows under Python 3.13t when it does not do so under other Python versions

When run under free-threading Python 3.13 on Windows, uv under certain circumstances emits long paths (prefixed with \\?\) which seem to trip up certain compilers (such as MSCV).
A lot more context is available in https://github.com/pypa/cibuildwheel/issues/1975
This issue is limited to Python 3.13t. It does not happen on any regular Python version (including 3.13).
It is also purely limited to Windows and works on all other operating systems.
CI runs in https://github.com/pypa/cibuildwheel/issues/1975 have also shown that this is limited to uv (as early as 0.2.35, but also tested just now with 0.4.2) and does not happen when using plain old pip.
An example of a 3.13t run producing a long path can e.g. be found here: https://github.com/cda-tum/mqt-qcec/actions/runs/10634832174/job/29568141103?pr=432#step:7:1526 (look at the PYTHON_EXECUTABLE, Python_ROOT_DIR and the related variants in the log)
It's a bit harder to show the output for a successful run as up until #6903 was merged, uv swallows the build system output.
It also seems to be a combination of a couple of specific things that lead to uv emitting long paths here.
The CI for our dependency project (https://github.com/cda-tum/mqt-core/tree/shared-libs) succeeds without problems on 3.13t: https://github.com/cda-tum/mqt-core/actions/runs/10634400958/job/29481632914#step:8:5742
Only once the depending project (https://github.com/cda-tum/mqt-qcec/tree/use-mqt-core-package) declares the git dependency on mqt-core in its build time requirements, the issues start to come up when trying to build mqt-qcec.
Maybe the root cause somewhat has to do with the double build isolation going on here as the mqt-qcec build is built in an isolated environment, but then the mqt-core git dependency is being built in another isolated environment (supposedly spawned from the first isolated env).
A way to reproduce the failures and see the long paths (adapted from https://github.com/cda-tum/mqt-qcec/blob/a15710a4faec2ccd62f28d6575800a8632a6ec2a/.github/workflows/cd.yml#L88-L107C14):
git clone https://github.com/cda-tum/mqt-qcec
cd mqt-qcec
git switch use-mqt-core-package
nuget.exe install python-freethreaded -Version 3.13.0-rc1 -FallbackSource https://api.nuget.org/v3/index.json -OutputDirectory '<wherever you want this>'
uv venv --python "<wherever you want this>\python-freethreaded.3.13.0-rc1\tools\python.exe"
uv pip install -vvv .

Sorry that I couldn't get the example any smaller or more isolated. I really tried but could not fabricate a simpler scenario that triggers the issues.

Thanks! Am I correct that this call is ultimately failing?
DEBUG Calling `scikit_build_core.build.build_wheel("\\\\?\\C:\\Users\\runneradmin\\AppData\\Local\\uv\\cache\\built-wheels-v3\\git\\c4f0338be623b94c\\e17ea8269bf6b83a\\.tmpiVR21p", {}, None)`

I think we should avoid introducing these in that context. I'll take a look.

I admittedly have no idea why this would affect the free-threaded Pythons, but not Python 3.13 without free-threading.

Thanks! Am I correct that this call is ultimately failing?
DEBUG Calling `scikit_build_core.build.build_wheel("\\\\?\\C:\\Users\\runneradmin\\AppData\\Local\\uv\\cache\\built-wheels-v3\\git\\c4f0338be623b94c\\e17ea8269bf6b83a\\.tmpiVR21p", {}, None)`

I think we should avoid introducing these in that context. I'll take a look.

Yeah. At least that's what I read from the logs. Everything after that in https://github.com/cda-tum/mqt-qcec/actions/runs/10634832174/job/29568141103?pr=432#step:7:1526 is the error output.
Just saw that 0.4.3 was released. So I should be able to get you a "successful" build log on a different Python version as well now.

Alright, new runs with 0.4.3 here: https://github.com/cda-tum/mqt-qcec/actions/runs/10673641135?pr=432
Specifically, compare:

Successfully running uv on Python 3.12 (uv venv --python 3.12): https://github.com/cda-tum/mqt-qcec/actions/runs/10673641135/job/29582964862?pr=432
Successfully running uv on Python 3.13 (from nuget): https://github.com/cda-tum/mqt-qcec/actions/runs/10673641135/job/29582965007?pr=432
Unsuccessfully running uv on Python 3.13t (from nuget): https://github.com/cda-tum/mqt-qcec/actions/runs/10673641135/job/29582965255?pr=432

I got a different failure here: https://github.com/astral-sh/uv/actions/runs/10673961604/job/29583752151?pr=6949. Does that look... correct?

At least it seems to be able to build the mqt-core build time dependency as well as the mqt-qcec package itself in that log.
It seems to me that it then fails when trying to install numpy from source (which is a regular install dependency of mqt-qcec). That seems to be a known issue on the numpy side according to their tracking issue for 3.13t support (https://github.com/numpy/numpy/issues/26157)
I believe if you install with --no-deps the install of mqt-qcec should succeed.

Ok cool that actually worked. (A subsequent test failed, unrelated.) I'll merge that change and link it to this issue.

Should be fixed in the next release via https://github.com/astral-sh/uv/pull/6949.

Nice 🎉 thanks for looking into this so quickly! Love what you and your team are building! 🚀


Add VSCode & IntelliJ / IDEA to .gitignore + split the file into categories

Added the generated folders from VS Code and IntelliJ IDEA/Webstorm to the gitignore file.
As part of that, also restructured the file into categories.

Note: This should not affect the .vscode folder we want to keep.

Thanks sir :)


Remove healthchecker ceph client

Solves: https://github.com/red-hat-storage/ocs-operator/issues/2829

/test all

/test verify generated changes (1.22)

/assign @Madhu-1

/hold for testing

/unhold verified

/test ocs-operator-bundle-e2e-aws

/unhold

The changes look good, just wondering if we should update the name for setCephResourceStatus method and CephResources field in the StorageConsumer Status to reflect that they can be any kind of Resources (NoobaaAccount or any other fields we might want to add in future)

The changes look good, just wondering if we should update the name for setCephResourceStatus method and CephResources field in the StorageConsumer Status to reflect that they can be any kind of Resources (NoobaaAccount or any other fields we might want to add in future)

@rewantsoni Yes I agree the name should be changed from CephResources to GenericResources or some other name to clearly justify the need and the purpose of the field.

/test ocs-operator-bundle-e2e-aws

The changes look good, just wondering if we should update the name for setCephResourceStatus method and CephResources field in the StorageConsumer Status to reflect that they can be any kind of Resources (NoobaaAccount or any other fields we might want to add in future)

@rewantsoni Yes I agree the name should be changed from CephResources to GenericResources or some other name to clearly justify the need and the purpose of the field.

This might need API change as API is tied to the CephResource name

/test ocs-operator-bundle-e2e-aws


Change visibility  collectAttributes().

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
❌

👍


this._core._renderService?._onIntersectionChange is not a function

TypeError: this._core._renderService?._onIntersectionChange is not a function
at zi.forceUnpause (vscode-<REDACTED: user-file-path>:<REDACTED: user-file-path>%20vs%<REDACTED: user-file-path>:1971:27069)
at Hi._resizeNow (vscode-<REDACTED: user-file-path>:<REDACTED: user-file-path>%20vs%<REDACTED: user-file-path>:3121:3652)
at Hi._resize (vscode-<REDACTED: user-file-path>:<REDACTED: user-file-path>%20vs%<REDACTED: user-file-path>:3121:2736)
at vscode-<REDACTED: user-file-path>:<REDACTED: user-file-path>%20vs%<REDACTED: user-file-path>:6:42864

Go to Errors Site

/duplicate https://github.com/microsoft/vscode/issues/164899


Rails 5 API deployed as microservices

Has anybody done this before with this gem? We are planning to divide our rails API into microservices and deploy them using docker-compose. How does devise_token_auth works in this case? For example I have auth_service, service1, service2 etc.. deployed, clients will get authenticated with auth_service, and calling different services with the same token. Assuming all services are connecting to the same database, can I use devise_auth_token in all other services to authenticate the token?
I want to expose all the methods available with devise_auth_token only in our auth service, and sign_in only in other services. Is it possible?

Is this an issue or a question? If question, you are better sticking with StackOverflow or somewhere else.

It is a question. I am closing this since I haven't heard from anybody.


Set base url to my actual domain

I need this for my canonical links.

Wait on this: https://github.com/getzola/zola/issues/2650


Add Arch-based Projects

https://github.com/PandaFoss/Awesome-Arch/blob/master/README.md
Arch Linux is an independently developed, x86-64 general purpose GNU/Linux distribution versatile enough to suit any role. This awesome list aims to collect all those projects based on Arch Linux and its philosophy.
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request

Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
You have to review at least 2 other open pull requests.
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration.
You have read and understood the instructions for creating a list.
This pull request has a title in the format Add Name of List.

✅ Add Swift
✅ Add Software Architecture
❌ Update readme.md
❌ Add Awesome Swift
❌ Add swift
❌ Adding Swift
❌ Added Swift

Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.

✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
✅ - [Framer](…) - Prototyping interactive UI designs.
❌ - [iOS](…) - Resources and tools for iOS development.
❌ - [Framer](…)
❌ - [Framer](…) - prototyping interactive UI designs

Your entry should be added at the bottom of the appropriate category.
The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
Includes a succinct description of the project/theme at the top of the readme. (Example)

✅ Mobile operating system for Apple phones and tablets.
✅ Prototyping interactive UI designs.
❌ Resources and tools for iOS development.
❌ Awesome Framer packages and tools.

It's the result of hard work and the best I could possibly produce.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
The repo name of your list should be in lowercase slug format: awesome-name-of-list.

✅ awesome-swift
✅ awesome-web-typography
❌ awesome-Swift
❌ AwesomeWebTypography

The heading title of your list should be in title case format: # Awesome Name of List.

✅ # Awesome Swift
✅ # Awesome Web Typography
❌ # awesome-swift
❌ # AwesomeSwift

Non-generated Markdown file in a GitHub repo.
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate. Please search for existing submissions.
Only has awesome items. Awesome lists are curations of the best, not everything.
Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
Includes a project logo/illustration whenever possible.

Either centered, fullwidth, or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.

Can be placed centered if the list has a centered graphics header.

Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of nested lists, preferably none.

Has an appropriate license.

That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
WTFPL and Unlicense are not acceptable licenses.
If you use a license badge, it should be SVG, not PNG.
To verify that you've read all the guidelines, please add comment with just the word unicorn.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.

Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.
Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

[Insert URL to the list here]
[Explain what this list is about and why it should be included here]
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request

Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
You have to review at least 2 other open pull requests.
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration.
You have read and understood the instructions for creating a list.
This pull request has a title in the format Add Name of List.

✅ Add Swift
✅ Add Software Architecture
❌ Update readme.md
❌ Add Awesome Swift
❌ Add swift
❌ Adding Swift
❌ Added Swift

Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.

✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
✅ - [Framer](…) - Prototyping interactive UI designs.
❌ - [iOS](…) - Resources and tools for iOS development.
❌ - [Framer](…)
❌ - [Framer](…) - prototyping interactive UI designs

Your entry should be added at the bottom of the appropriate category.
The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
Includes a succinct description of the project/theme at the top of the readme. (Example)

✅ Mobile operating system for Apple phones and tablets.
✅ Prototyping interactive UI designs.
❌ Resources and tools for iOS development.
❌ Awesome Framer packages and tools.

It's the result of hard work and the best I could possibly produce.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
The repo name of your list should be in lowercase slug format: awesome-name-of-list.

✅ awesome-swift
✅ awesome-web-typography
❌ awesome-Swift
❌ AwesomeWebTypography

The heading title of your list should be in title case format: # Awesome Name of List.

✅ # Awesome Swift
✅ # Awesome Web Typography
❌ # awesome-swift
❌ # AwesomeSwift

Non-generated Markdown file in a GitHub repo.
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate. Please search for existing submissions.
Only has awesome items. Awesome lists are curations of the best, not everything.
Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
Includes a project logo/illustration whenever possible.

Either centered, fullwidth, or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.

Can be placed centered if the list has a centered graphics header.

Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of nested lists, preferably none.

Has an appropriate license.

That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
WTFPL and Unlicense are not acceptable licenses.
If you use a license badge, it should be SVG, not PNG.
To verify that you've read all the guidelines, please add comment with just the word unicorn.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.

Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.
Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

unicorn

The list looks great and it's very informative. I like it!

The list looks great and it's very informative. I like it!

Thank you! Unfortunately it takes a long time to merge it and it consumes my anxiety hahaha

❯ awesome-lint https://github.com/PandaFoss/Awesome-Arch
✖ Linting

  README.md:64:3
  ✖   1:1  License was not detected by GitHub             remark-lint:awesome-github
  ✖   1:1  Missing main list heading                      remark-lint:awesome-heading
  ✖  64:3  Link to http://morpheusarchlinux.com/ is dead  remark-lint:no-dead-urls

  3 errors

https://github.com/sindresorhus/awesome-lint

The header should be Awesome Arch in text and the badge should come after.

The Arch Linux logo should not steal so much attention. It should be much smaller. The header looks quite messy right now.

Remove Official link: Arch Linux Homepage and linkify Arch Linux in the description instead.

@sindresorhus I have done everything you advised me. I think it is ready to be published.

I would right-align the Arch logo like done here: https://github.com/sindresorhus/awesome-electron

@sindresorhus Ready, changes made.

Tweet: https://twitter.com/awesome__re/status/1196274557448900613

Also note: https://github.com/sindresorhus/awesome/commit/b9338ca9226bf2dabacb46a847dd5f9db1856821


 is not recognised

Hello !
I have a set of emails in MJML in 2.2.0. I'm trying to rework some of them in 3.2.0 and use the <mj-include> tag, however it doesn't seems to be recognise with the validator or the new atom plugin.
I tried with a simple exemple but I receive the same error.
<mjml>
  <mj-body>
    <mj-container>
      <mj-include path="./header" />
    </mj-container>
  </mj-body>
</mjml>

<mj-section>
  <mj-column>
    <mj-text>This is a header</mj-text>
  </mj-column>
</mj-section>

Line 5 (mj-include) — Element mj-include doesn't exist or is not registered
I also tried with other release but the error keep coming back.
The only way I can make it work is when I put the <mj-include> before the <mj-body> but only one file is render.
Thank you.

Hi there,
I don't really understand, it's only an issue with the atom package or with the cli too ?
The linter-mjml doesn't support mj-include, so it's normal

It's an issue with the CLI, the mjml --validate main.mjml return
Line 4 (mj-include) — Element mj-include doesn't exist or is not registered

Can you provide a ls -l within the folder ?

Sure.
➜  Digest git:(master) ✗ ls -l main
total 8
-rw-r--r-- 1 501 dialout 2774 Feb  8 21:01 digest.mjml
-rw-r--r-- 1 501 dialout  632 Feb  7 23:17 header.mjml

Oh right, validate doesn't replace mj-include so that's fine, can you try to render it and tells me if it renders fine ?

Ok my bad, the rendering does work I thought I was stuck with the --validate, but the result is correct.
However since I'm using gulp mjml to render my files I have to put the relative path from the root of the project. Is it possible to set the path="" from <mj-include> relative to the .mjml file itself ?
Putting ../partial/header.mjml instead of ./src/MVB/Bundle/MailerBundle/Resources/views/mjml-3.2.0/Digest/partial/header.mjml

I fixed that by adding a process.chdir('./src/MVB/Bundle/MailerBundle/Resources/views/mjml-3.2.0') to the gulp task. Everything is now working correctly.
Thanks for the help :)

Oh yeah, it could be easily fix by passing optionfilePath to mjml2html with current file you're compiling

I'm getting this issue when I try and render using the miml command line.
Is it possible that the command line doesn't handle this correctly?

Hello @techdragon, my bet is that you're missing the closing slash / using <mj-include > instead of <mj-include />.
If I'm wrong, can you please provide:

the markup of the file you're rendering
the markup of the file you're including
the version of MJML you're using
your folder structure (where is the file you're rendering relatively to the file you're including)


Add more documentation

Just a reminder to myself to add more documentation

Added some documentation to README (https://github.com/NebraLtd/LoRa-mPCIe/blob/main/README.md)
But now need to populate variants file with more details to help to sort #3
https://github.com/NebraLtd/LoRa-mPCIe/blob/v1.1/VARIANTS.md


chore(contributions): new issue template

What project are you opening a pull request for?

react-instantsearch
instantsearch.js

Summary
We want users to be very precise in their issue descriptions so we can better help them solve their problems. We also want to leverage discourse forum for generic questions.
Result
This will trigger a new issue template when opening issues.

My take
<!--
  ***************************
  🎉 Thanks for participating in this project! 🎉

  This form is to report issues or new features.
  As for general questions like "How to do routing using react-instantsearch",
  please search or post a question to our discourse forum: https://discourse.algolia.com/ (preferred).

  ⚠ In any case,
    - make sure you are using the latest version of the library;
    - do at least one search in current issues or questions, your question might already be answered;
  ***************************

  ❓ Do you want to request a *feature* or report a *bug*?
-->

## 🐛 I want to report a bug

### What is the current behavior?

### What is the expected behavior?

### What browsers are impacted? Which versions?

<!-- ⚠ or -->

## 🍭 I want to request a feature

### What is your use case?

### What is your proposed API entry, new option, to add if any?

<!--
  ⚠ *************************** ⚠

  🐛 If the current behavior is a bug, please provide all the steps to reproduce and a minimal
  [JSFiddle](https://jsfiddle.net/) example or a repository on GitHub that we can `npm install`
  and `npm start`.

  🍭 If you are requesting a new feature, we need to understand WHY would you
  need this feature, which means you should give the use case for such feature.

  ⚠ *************************** ⚠
-->

## What project are you opening an issue for?

- react-instantsearch
- instantsearch.js

## What is the version you are using?

🚨 Please always use the latest one before opening a bug issue.

<!-- 🚫 Delete any HTML comment and non relevant questions 🚫 -->


fix: use octokit.rest interface for github

I broke this with the node20 upgrade in #31. The octokit.pulls, octokit.checks objects are now nested inside octokit.rest, which broke existing usages. This was not uncovered with unit tests because the jest mocking covered this.
This PR:

switches all github calls to use octokit.rest
updates the unit tests accordingly

Testing
Tested locally this time by running things like:
DEBUG="true" INPUT_TOKEN="github_pat_<pat>" GITHUB_REPOSITORY="adRise/update-pr-branch" INPUT_REQUIRE_AUTO_MERGE_ENABLED="false" INPUT_REQUIRE_PASSED_CHECKS="false" INPUT_BASE="master" INPUT_REQUIRED_APPROVAL_COUNT="0" node dest/index.js

Example of errors before this fix:
TypeError: Cannot read properties of undefined (reading 'list')
TypeError: Cannot read properties of undefined (reading 'updateBranch')
TypeError: Cannot read properties of undefined (reading 'checks')

@zhiyelee Sorry for breaking it.

@erikburt Thanks for the report and fix. No worries. Will take a look and release a new patch release soon


Automatically detecting categories

Is there a way to have access to the Mint function that classifies transactions into categories?
Like when transactions are taken from your bank account, it automatically finds the category and generally does a pretty good job at it.
Since I'm batch uploading transactions, but I don't have categories, I was wondering if there would be away to access that classifier.
Thanks!

Unfortunately, mint does not expose the function on how they're classify transactions to categories.

Okay thanks!


enhancement: set empty value

Is there possible to support write key with empty value like that:
networks:
    networkName:

Not at the moment - though not sure what the value of that would be?
There was some discussion of being able to delete a node - would that make more sense? Though that also has not been done - happy to take Pull Requests!

This requirement occurs when I tried to using yaml to generate docker-compose file.
Some examples show that no data or value under the key 'networkName'. But after testing, it seems those examples cannot work perfectly.
So never mind. Deleting a node is a more reasonable feature.

Cool - I'll keep this issue but rename it to delete a node.

I'm interested in this feature. I like the suggestion of a --delete/-d or --remove/-r on the cli, but i'm thinking the way this depends on the gopkg.in/yaml.v2 library for scripts that it might look like this for the scripted updates:
yq w -s update_instructions.yaml --delete-script delete_instructions.yaml
yq w -s update_instructions.yaml -ds delete_instructions.yaml

That or something like it or things will have to get far more complicated (like functions in jq) in order to make it work.
Ideas?

As it is, my workaround for today will probably involve outputting to json, using the jq delpaths() function, and then re-importing that json through yq


Choose a license

We'd like the materials to be able to be reused / referenced by The Turing Way and by Remotely Green, so CC-BY seems most appropriate.

Agreed on CC-BY.
Implemented in d8f0222 and 35feb1f6f035f555b0051941d0e9988c8b1263ec


Exported variables behave weirdly

Godot version:
v3.2.1
OS/device including version:
Windows 10
Issue description:
Global variables initialized with an exported variable will use its default value and not the value that has been set in the inspector.
Steps to reproduce:

Create a new project.
Set Node2D as the root node.
Give it a script.
Paste in:

extends Node2D
export var exported: int
var test = exported
func _ready():
print("These should always be the same: ")
print(exported)
print(test)

Set the value of "Exported" in the inspector to 100
Run the project.
Observe the weird results:

These should always be the same:
100
0
Minimal reproduction project:
It would be faster to just do as described above.

Does it work if you use export var exported: int = 0?

This is because of the exported variables are set at a later point in time.
(I did read that somewhere... But don't ask me where :D )
An easy solution would be to have your var test be an onready variable
onready var test = exported
Or just initialize it in the _ready function.

Thank you, I didn't know "onready" was a thing. I still think it isn't intuitive but I'll close the issue because, from what you said, it seems that it has already been accounted for.


Terraform Provider Does Not Support Hyphen in Custom Properties Configuration

Description:
The current version of the Terraform provider exhibits a limitation by not supporting hyphens in Custom Properties configuration. This deviation poses an inconsistency with the expected behavior and functionality.
Additional Information:

Terraform Provider Version: v2.0.3
Relevant Code Snippet:
https://github.com/splunk/terraform-provider-synthetics/blob/cd6630800b5836a83367eabe3af6b45de3c7e64c/synthetics/resource_api_check_v2.go#L205
https://github.com/splunk/terraform-provider-synthetics/blob/cd6630800b5836a83367eabe3af6b45de3c7e64c/synthetics/resource_api_check_v2.go#L210
Custom properties Document:

Key Requirements:

Must start with a letter.
Allowed characters include letters, numbers, underscores, and hyphens.
Naming restrictions: Can't be named test_id or test.
Character limit: Key size cannot exceed 128 characters.

Value Requirements:

Allowed characters include letters, numbers, underscores, and hyphens.

Thanks for adding this issue! Will double check the regex with the backend and if other chars are allowed update the validate function!

@greatestusername-splunk can you confirm the requirements of the property values? Hyphens and other special characters are allowed in the UI however are excluded by terraform

@bambro
These should work in terraform now. Latest version included an updated regex for allowing hyphens and underscores.

Closing as https://github.com/splunk/terraform-provider-synthetics/pull/44 should address this issue in full. If it does not please re-open another issue.
Thanks!


Added ep4 youtube and description

the post will still need the libsyn entry when @dave-tucker publishes that end

@dave-tucker @mestery This posts the youtube page
It still needs the libsyn ID when Dave has that end published. We just need to paste it into the following and append it to episode4.md
Or listen here:

{{< libsyn-player ID_GOES_HERE >}}

{{< podcasts >}}

The youtube link will be live around 4pm EST at https://youtu.be/8xiPvrAfZPE
Ty!


Create CITATION.cff

@MarkLee634 I don't know if that is your orcid id, there were multiple under your name

double check contents later


Fix crash in nativeInjectHMRUpdate

Fix crash in nativeInjectHMRUpdate if it is called with only one argument from JS
Fixes #22116
For more deep explanation, see comments thread from here: https://github.com/facebook/react-native/issues/22116#issuecomment-440420713
Environment:
This fix dedicated for 0.57-stable branch, because crashed code was part of old JSC executor, that was replaced in master with new JSI code.
Test Plan:
Ensure that application no more crash when enable HMR from dev menu.
Changelog:
[iOS] [Fixed] - Fix application crash when HMR enabled

Thanks for being so quick! Super appreciated :) If you can add the comment it would be perfect, in the meantime I'll have it double-checked & tested in my release :)
(btw, if you are on twitter, can you shoot me a DM over there?)


chore(internal): Implement ConfigService

chore(internal): Implement ConfigService
This PR:

adds a ConfigService that can be consumed by the engine and the client separately.
ConfigStore now only holds primitive store-level operations regarding the configs, and the rest of the higher level logic is moved to ConfigService.

As a result, the interface for ConfigStore has slight changes.

Next (in order of priority)

Swap out DConfig with ConfigService

This will resolve various local override vault issues (before engine v3 rollout)

Deprecate DConfig
Refactor ConfigUtils to be part of the service
Make ConfigService an @injectable (after wider tsyringe adoption)
Implement ConfigEventEmitter to enable real time config updates and remove the need for reload

Pull Request Checklist
Code
Basics

[x] code should follow Code Conventions
[x] circular dependency check: make sure your code is not introducing new circular dependencies in plugin-core.  See Avoiding Circular Dependencies.
[x] sticking to existing conventions instead of creating new ones

eg: if configuration for utilities are already in one module or package, add future utilities there as well

Extended

General

[x] check whether code be simplified
[x] check if similar function already exist in the codebase. if so, can it be re-used?
[x] check if this change adversely impact performance

Operations

[x] when shipping this change, will it just work or will it introduce additional operational overhead due to complicated interface or known bugs?

Architecture

[x] check if code is introducing changes on a foundational class or interface. if so, call for design review if needed

eg: making changes to DNode

Instrumentation
Basics

[~] if you are adding analytics related changes, make sure the Telemetry docs are updated

Extended

[~] can we track the performance of this change to know if it is successful?

eg: see usage for export pod

Tests
Basics

[x] Write Tests
[x] Confirm existing tests pass
[x] Confirm manual testing
[x] Common cases tested
[x] 1-2 Edge cases tested
[x] If your tests changes an existing snapshot, snapshots have been updated

Extended

[~] If you are adding a new language feature (graphically visible in VS Code/preview/publishing), an example is included in the test workspace
CSS

[~] display is correct for following dimensions

[~] sm: screen ≥ 576px, eg. iphonex, (375x812)
[~] lg: screen ≥ 992px
[~] xxl: screen ≥ 1600px eg. mac (1600x900)

[~] display is correct for following browsers (across the various dimensions)

[~] safari
[~] firefox
[~] chrome

Docs

[~] if your change reflects documentation changes, also submit a PR to dendron-site and mention the doc PR link in your current PR
[~] does this change introduce a new or better way of doing things that others need to be aware of? if so, an async should be created and a process added in Development or Packages

Close the Loop
Extended

[~]  is this a developer BREAKING change? if another person cloning from this branch will need to adjust their dependencies or mental model of the architecture, then it is. if this is the case, make sure this is communicated according to Close Loop

eg: breaking dev change due to new dependency

very small nit update: flipped applyOverride to be default true since we always want that.


nvim-compe invalidated some keymap( and )

nvim-compe invalidated some keymap( and ) in insert mode.
minimal vimrc:
set nocompatible
set runtimepath=$VIMRUNTIME
set runtimepath+=/home/ring/.local/share/nvim/site/pack/packer/opt/nvim-compe

lua << EOF
  require'compe'.setup {}
EOF

inoremap <C-n> <esc>:echo 'hi'<cr>
inoremap <C-p> <esc>:echo 'hi'<cr>

press <c-n> but nothing happen.

@66RING It isn't a nvim-compe's problem, I think.
The vim does not support <C-n> and <C-p> mapping when the completion-menu is showing.

@hrsh7th I have no idea. I pressed <c-p> to test it in insert mode when the completion-menu was not show.
this mapping work well when set completeopt=menuone,noinsert,noselect.
And I have also tried other plugins(nvim-lua/completion-nvim) and they work well.

well, it good since last commit

Sorry. I've misunderstood what your mean. Good to hear that works.


Stop button (front end)

Merges master
Adds missing ABORTED value in API specs
Controls enabled state of Stop button

manually merged, thanks a lot!!


year select like https://schnitzler-briefe.acdh.oeaw.ac.at/calendar.html

as new element

additionally, allow to enabled/disable displaying sparse years (those without events) via data-attribute.
in the select element, empty years should be skipped.
in the radio group, empty years should be disabled <input type="radio">


Rolling mean on dask array does not preserve dtype

What happened?
Calling rolling().mean() on a dask-backed array sometimes outputs a different dtype than with a numpy backed array, for example with a float32 input. This is due to the optimized _mean function introduced in #4915.
What did you expect to happen?
This is a simple enough operation that if you start with float32 I would expect to get float32 back.
Minimal Complete Verifiable Example
>>> import xarray as xr
>>> da = xr.DataArray([1,2,3], coords={'x':[1,2,3]}).astype('float32')
>>> da.rolling(x=3, min_periods=1).mean().dtype
dtype('float32')
>>> da.chunk({'x':1}).rolling(x=3, min_periods=1).mean().dtype
dtype('float64')

MVCE confirmation

[X] Minimal example — the example is as focused as reasonably possible to demonstrate the underlying issue in xarray.
[X] Complete example — the example is self-contained, including all data and the text of any traceback.
[X] Verifiable example — the example copy & pastes into an IPython prompt or Binder notebook, returning the result.
[X] New issue — a search of GitHub Issues suggests this is not a duplicate.

Relevant log output
No response
Anything else we need to know?
#5877 is somewhat related.
Environment

INSTALLED VERSIONS
------------------
commit: e6791852aa7ec0b126048b0986e205e158ab9601
python: 3.8.13 | packaged by conda-forge | (default, Mar 25 2022, 06:04:10)
[GCC 10.3.0]
python-bits: 64
OS: Linux
OS-release: 5.15.0-46-generic
machine: x86_64
processor: x86_64
byteorder: little
LC_ALL: None
LANG: en_US.UTF-8
LOCALE: ('en_US', 'UTF-8')
libhdf5: 1.12.1
libnetcdf: 4.8.1
xarray: 2022.6.1.dev63+ge6791852.d20220921
pandas: 1.4.2
numpy: 1.21.6
scipy: 1.8.1
netCDF4: 1.5.8
pydap: installed
h5netcdf: 1.0.2
h5py: 3.6.0
Nio: None
zarr: 2.12.0
cftime: 1.6.0
nc_time_axis: 1.4.1
PseudoNetCDF: 3.2.2
rasterio: 1.2.10
cfgrib: <IP_ADDRESS>
iris: 3.2.1
bottleneck: 1.3.4
dask: 2022.04.1
distributed: 2022.4.1
matplotlib: 3.5.2
cartopy: 0.20.2
seaborn: 0.11.2
numbagg: 0.2.1
fsspec: 2022.8.2
cupy: None
pint: 0.19.2
sparse: 0.13.0
flox: 0.5.9
numpy_groupies: 0.9.19
setuptools: 62.0.0
pip: 22.2.2
conda: None
pytest: 7.1.3
IPython: None
sphinx: None

Is this also true with xr.set_options(use_bottleneck=False)?

Without bottleneck, I guess both options from the MVCE above get routed through _mean:
>>> xr.set_options(use_bottleneck=False)
>>> da = xr.DataArray([1,2,3], coords={'x':[1,2,3]}).astype('float32')
>>> da.rolling(x=3, min_periods=1).mean().dtype
dtype('float64')
>>> da.chunk({'x':1}).rolling(x=3, min_periods=1).mean().dtype
dtype('float64')

And after #7063:
>>> xr.set_options(use_bottleneck=False)
>>> da = xr.DataArray([1,2,3], coords={'x':[1,2,3]}).astype('float32')
>>> da.rolling(x=3, min_periods=1).mean().dtype
dtype('float32')
>>> da.chunk({'x':1}).rolling(x=3, min_periods=1).mean().dtype
dtype('float32')


CI: K8sPolicyTest Multi-node policy test with L7 policy using connectivity-check to check datapath: provided port is already allocated

CI failure
/home/jenkins/workspace/Cilium-PR-K8s-1.12-net-next/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:514
cannot install connectivity-check
Expected command: kubectl apply --force=false -f /home/jenkins/workspace/Cilium-PR-K8s-1.12-net-next/src/github.com/cilium/cilium/examples/kubernetes/connectivity-check/connectivity-check-proxy.yaml
To succeed, but it failed:
Exitcode: 1
Err: exit status 1
Stdout:
 	 deployment.apps/echo-c created
	 deployment.apps/echo-c-host created
	 deployment.apps/pod-to-a-intra-node-proxy-egress-policy created
	 deployment.apps/pod-to-a-multi-node-proxy-egress-policy created
	 deployment.apps/pod-to-c-intra-node-proxy-ingress-policy created
	 deployment.apps/pod-to-c-multi-node-proxy-ingress-policy created
	 deployment.apps/pod-to-c-intra-node-proxy-to-proxy-policy created
	 deployment.apps/pod-to-c-multi-node-proxy-to-proxy-policy created
	 service/echo-c created
	 service/echo-c-headless created
	 service/echo-c-host-headless created
	 ciliumnetworkpolicy.cilium.io/pod-to-a-intra-node-proxy-egress-policy created
	 ciliumnetworkpolicy.cilium.io/pod-to-a-multi-node-proxy-egress-policy created
	 ciliumnetworkpolicy.cilium.io/pod-to-c-intra-node-proxy-to-proxy-policy created
	 ciliumnetworkpolicy.cilium.io/pod-to-c-multi-node-proxy-to-proxy-policy created
	 ciliumnetworkpolicy.cilium.io/echo-c created
	 deployment.apps/echo-a created
	 service/echo-a created
	 deployment.apps/echo-b created
	 deployment.apps/echo-b-host created
	 service/echo-b-host-headless created

Stderr:
 	 The Service "echo-b" is invalid: spec.ports[0].nodePort: Invalid value: 31313: provided port is already allocated

/home/jenkins/workspace/Cilium-PR-K8s-1.12-net-next/src/github.com/cilium/cilium/test/k8sT/Policies.go:1495

After investigating this, it turns out that there's a chance that Services that are created in the test suite could conflict with each other's nodePort. In some cases, we don't explicitly set the nodePort and leave it up to K8s to allocate a port between the range of 30000 and 32768. In other cases, we do explicitly set the nodePort. In this test failure, we had a Service created first and was allocated a random port of 31313, and later we deploy a Service with a set port to 31313, causing the conflict.
The reason the conflict occured in the first place is because of a failure to clean up, which we don't have logs for, as it happened in a different block and didn't trigger an error, which we usually ignore. We only retrieve output when an error occurs in a specific block [It(), etc]).
I posted on the #testing channel about different approaches and I will quote the post here, in case the Slack link expires.

I've come across a test failure that failed because two different Services conflicted on their nodePort. From what I can tell, a NodePort Service was allocated to port 31313 in the test suite, and then later in the test suite, a totally different NodePort Service was created, setting 31313 as the explicit NodePort. This obviously created a conflict and spit out a msg like:

The Service "echo-b" is invalid: spec.ports[0].nodePort: Invalid value: 31313: provided port is already allocated

The first Service should have been deleted, but it clearly was not cleaned up, and there are no logs to explain why. We ignore errors when cleaning up to prevent the test suite from halting for "minor" reasons, but it does allow us to get into these situations, where we've potentially polluted the next test.Specifically for Services, I see two approaches to prevent this in the future:

Explicitly set the nodePort for every Service we create, so that we don't get bitten by the random allocation between 30000 - 32767.
Where we set the nodePort explicitly, choose a port from outside the range (30000 - 32767), to avoid conflicts with random allocation within that range.

Actually I just realized that this happened in the same parent Context block, and has nested Contexts within it.Essentially it looks like:
Context A {
  BeforeAll() { Created Service with randomly allocated port 31313 }
  AfterAll()  { Cleaned up resources, but failed on Service above } ...
  Context B {
    BeforeAll() { Created Service with explicit port 31313; conflict }
    AfterAll() {
      Fails to clean up because above Service wasn't created
    }
  }
}

Unfortunately, trying to dig into why the clean up failed would be moot, because we don't retrieve output from succeeding runs, so we still wouldn't have the reason of why it failed to clean up in the first place. We only have Context B's output (we actually only have the It() block within it). So that leaves us with the two aforementioned approaches above.
Found during https://github.com/cilium/cilium/pull/13053

Following the discussion on Slack (link above), @joestringer pointed out this could be a bug in Cilium where we fail to delete / clean up the Service, even though the delete may have succeeded from the K8s perspective.
Adding needs-triage.

When I look at the original commandline output again, it seems to be kubectl reporting this failure, which means it should actually be that there are conflicting k8s objects installed when attempting to configure this new YAML. This suggests that it's actually just kubectl service cleanup from previous test that is not performed properly (ie test-code bug), rather than an agent bug.

When I look at the original commandline output again, it seems to be kubectl reporting this failure, which means it should actually be that there are conflicting k8s objects installed when attempting to configure this new YAML. This suggests that it's actually just kubectl service cleanup from previous test that is not performed properly (ie test-code bug), rather than an agent bug.

Ah, thanks for catching that. It slipped my mind that we were seeing the failure from kubectl. So then this reinstates that the solution lies between the two approaches originally listed. @aanm also pointed out that we can't choose a NodePort outside the NodePort range, leaving us with only approach (1) from above.
Removing needs/triage.

I also came across this when working with cilium connectivity-checks. This seems to be an issue in Kubernetes itself where the allocation of nodePort is done from the local cache which can be out of sync from the etcd data. See https://github.com/kubernetes/kubernetes/issues/85894 for more context.
I was even able to reproduce it using connectivity checks from a simple script[1]. At this point, there doesn't seem to be a proper solution for this. The way I fixed it for my use case is by retrying during connectivity-check.yaml apply until it succeeds or a timeout is reached.
What I am not sure of exactly is if the above error is due to this out of sync behavior or due to the port collision as mentioned in the issue description. My assumption here is that since the issue was fixed in the latest releases and we only see these errors in GKE/net-next this might not be due to port collision.
[1] - The script will fail with an error similar to that mentioned in the issue description.
#!/bin/bash

set -e

URL="https://raw.githubusercontent.com/cilium/cilium/v1.9.0/examples/kubernetes/connectivity-check/connectivity-check.yaml"
NAMESPACE="temp-namespace"

kubectl create namespace "${NAMESPACE}" || true

function echo_sep() {
    echo "---------------------------------------"
}

for i in {1..10}
do
    echo "LOOP COUNT : ${i}"
    echo "[*] List services in the namepsace before apply"
    kubectl get svc -n "${NAMESPACE}"

    echo_sep

    echo "[*] Applying connectivity check in the namespace"
    kubectl apply -n "${NAMESPACE}" -f "${URL}"

    echo_sep

    echo "[*] Listing services in the namespace after apply"
    kubectl get svc -n "${NAMESPACE}"

    echo_sep

    echo "[*] Deleting connectivity check in the namespace"
    kubectl delete --wait -n "${NAMESPACE}" -f "${URL}"

    echo_sep

    echo "[*] Listing services in the namespace after delete"
    kubectl get svc -n "${NAMESPACE}"

    echo_sep
done

@fristonio It looks like the issue linked has been fixed and was included in K8s 1.19. Are you saying that you still experience this flake with this test when running net-next and 1.19 (I realize that's not a setup that we have).

Hit this in CI with Kernel 4.9 and K8s 1.20: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.20-kernel-4.9/533/testReport/junit/Suite-k8s-1/20/K8sPolicyTest_Multi_node_policy_test_with_L7_policy_using_connectivity_check_to_check_datapath/

Hit this in CI with Kernel 4.9 and K8s 1.20: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.20-kernel-4.9/533/testReport/junit/Suite-k8s-1/20/K8sPolicyTest_Multi_node_policy_test_with_L7_policy_using_connectivity_check_to_check_datapath/

Hit this one via https://jenkins.cilium.io/job/Cilium-PR-K8s-GKE/5174/testReport/junit/Suite-k8s-1/17/K8sPolicyTest_Multi_node_policy_test_with_L7_policy_using_connectivity_check_to_check_datapath/. Code changes were via https://github.com/cilium/cilium/pull/15759 which are unrelated.

@pchaigno Yes it appears so. I can take this up and use an even-numbered port.

Hit again in https://jenkins.cilium.io/job/Cilium-PR-K8s-1.21-kernel-4.9/616/testReport/junit/Suite-k8s-1/21/K8sPolicyTest_Multi_node_policy_test_with_L7_policy_using_connectivity_check_to_check_datapath/, this time with the new even-numbered port:
/home/jenkins/workspace/Cilium-PR-K8s-1.21-kernel-4.9/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:518
cannot install connectivity-check
Expected command: kubectl apply --force=false -f /home/jenkins/workspace/Cilium-PR-K8s-1.21-kernel-4.9/src/github.com/cilium/cilium/examples/kubernetes/connectivity-check/connectivity-check-proxy.yaml
To succeed, but it failed:
[...]
Stderr:
 	 The Service "echo-b" is invalid: spec.ports[0].nodePort: Invalid value: 31414: provided port is already allocated

The sysdump doesn't reveal any process holding that port :thinking: Could be that the process released the port between the test failure and the sysdump capture. I'm reopening so we can track this properly and see if another fix is necessary.

Hit in #18779:
2022-03-28T17:28:12.226792259Z
2022-03-28T17:28:12.227448548Z   \{^_^}/ hi!
2022-03-28T17:28:12.227459255Z
2022-03-28T17:28:12.227491452Z   Loading /default.json
2022-03-28T17:28:12.233540108Z   Done
2022-03-28T17:28:12.238630566Z
2022-03-28T17:28:12.238679750Z   Resources
2022-03-28T17:28:12.238686068Z   http://:41002/private
2022-03-28T17:28:12.238772007Z   http://:41002/public
2022-03-28T17:28:12.238778630Z
2022-03-28T17:28:12.238781174Z   Home
2022-03-28T17:28:12.238783454Z   http://:41002
2022-03-28T17:28:12.238785736Z
2022-03-28T17:28:12.239035451Z   Type s + enter at any time to create a snapshot of the database
2022-03-28T17:28:12.239894213Z   Watching...
2022-03-28T17:28:12.239905751Z
2022-03-28T17:28:12.242164441Z Some error occurred Error: listen EADDRINUSE: address already in use :::41002
2022-03-28T17:28:12.242177948Z     at Server.setupListenHandle [as _listen2] (node:net:1306:16)
2022-03-28T17:28:12.242180849Z     at listenInCluster (node:net:1354:12)
2022-03-28T17:28:12.242183145Z     at Server.listen (node:net:1441:7)
2022-03-28T17:28:12.242185392Z     at Function.listen (/usr/local/lib/node_modules/json-server/node_modules/express/lib/application.js:618:24)
2022-03-28T17:28:12.242188820Z     at /usr/local/lib/node_modules/json-server/lib/cli/run.js:135:20 {
2022-03-28T17:28:12.242191141Z   code: 'EADDRINUSE',
2022-03-28T17:28:12.242193372Z   errno: -98,
2022-03-28T17:28:12.242195628Z   syscall: 'listen',
2022-03-28T17:28:12.242197834Z   address: '::',
2022-03-28T17:28:12.242200063Z   port: 41002
2022-03-28T17:28:12.242202250Z }

Hit in - https://github.com/cilium/cilium/pull/21054.
https://jenkins.cilium.io/job/Cilium-PR-K8s-1.17-kernel-4.9/827/testReport/junit/Suite-k8s-1/17/K8sPolicyTest_Multi_node_policy_test_with_L7_policy_using_connectivity_check_to_check_datapath/

I believe the same issue is still happening but now with a different output: https://github.com/cilium/cilium/issues/22749.

Hit this with
The Service "echo-b" is invalid: spec.ports[0].nodePort: Invalid value: 31414: provided port is already allocated

logs_1317838.zip

JFYI, this flake is a bit unfortunate because we don't have control over the nodeport range which can conflict with the port range used by Cilium's proxy. We moved to even-numbered port numbers to reduce the likelihood but there's still a chance we get unlucky.

Hit on https://github.com/cilium/cilium/pull/27466.

Hit on #26836.
Sysdump:  cilium-sysdumps.zip

Hit on https://github.com/cilium/cilium/pull/34229
Sysdumps:
cilium-sysdumps.zip

What about instead of hard-coding the port, we should simply create the nodePort, let k8s do the allocation, and then retrieve the port that it generated.


Form: can't define array predicate with block syntax

Here's how to reproduce the error:
require 'dry-validation'

form = Dry::Validation.Form do
  key(:foo) { array? { each { int? } } }
end
NoMethodError: undefined method `each_with_object' for #<Dry::Types::Constructor:0x007fab2229d158>
	from /Users/luca/.gem/ruby/2.3.0/gems/dry-types-0.7.0/lib/dry/types/constructor.rb:69:in `method_missing'
	from /Users/luca/.gem/ruby/2.3.0/gems/dry-types-0.7.0/lib/dry/types/hash.rb:7:in `schema'
	from /Users/luca/.gem/ruby/2.3.0/gems/dry-types-0.7.0/lib/dry/types/hash.rb:23:in `symbolized'
	from /Users/luca/.gem/ruby/2.3.0/gems/dry-types-0.7.0/lib/dry/types/decorator.rb:35:in `method_missing'
	from /Users/luca/.gem/ruby/2.3.0/gems/dry-types-0.7.0/lib/dry/types/compiler.rb:66:in `merge_with'
	from /Users/luca/.gem/ruby/2.3.0/gems/dry-types-0.7.0/lib/dry/types/compiler.rb:54:in `visit_form_hash'
	from /Users/luca/.gem/ruby/2.3.0/gems/dry-types-0.7.0/lib/dry/types/compiler.rb:28:in `visit_type'
	from /Users/luca/.gem/ruby/2.3.0/gems/dry-types-0.7.0/lib/dry/types/compiler.rb:15:in `visit'
	from /Users/luca/.gem/ruby/2.3.0/gems/dry-types-0.7.0/lib/dry/types/compiler.rb:11:in `call'
	from /Users/luca/.gem/ruby/2.3.0/gems/dry-types-0.7.0/lib/dry/types/compiler.rb:43:in `visit_form_array'
	from /Users/luca/.gem/ruby/2.3.0/gems/dry-types-0.7.0/lib/dry/types/compiler.rb:28:in `visit_type'
	from /Users/luca/.gem/ruby/2.3.0/gems/dry-types-0.7.0/lib/dry/types/compiler.rb:15:in `visit'
	from /Users/luca/.gem/ruby/2.3.0/gems/dry-types-0.7.0/lib/dry/types/compiler.rb:62:in `visit_key'
	from /Users/luca/.gem/ruby/2.3.0/gems/dry-types-0.7.0/lib/dry/types/compiler.rb:15:in `visit'
	from /Users/luca/.gem/ruby/2.3.0/gems/dry-types-0.7.0/lib/dry/types/compiler.rb:67:in `block in merge_with'
	from /Users/luca/.gem/ruby/2.3.0/gems/dry-types-0.7.0/lib/dry/types/compiler.rb:67:in `map'
... 8 levels...
	from /Users/luca/.gem/ruby/2.3.0/gems/dry-validation-0.7.3/lib/dry/validation/schema.rb:45:in `new'
	from /Users/luca/.gem/ruby/2.3.0/gems/dry-validation-0.7.3/lib/dry/validation.rb:36:in `Schema'
	from /Users/luca/.gem/ruby/2.3.0/gems/dry-validation-0.7.3/lib/dry/validation.rb:41:in `Form'
	from (irb):7
	from /Users/luca/.gem/ruby/2.3.0/gems/bundler-1.11.2/lib/bundler/cli/console.rb:14:in `run'
	from /Users/luca/.gem/ruby/2.3.0/gems/bundler-1.11.2/lib/bundler/cli.rb:319:in `console'
	from /Users/luca/.gem/ruby/2.3.0/gems/bundler-1.11.2/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
	from /Users/luca/.gem/ruby/2.3.0/gems/bundler-1.11.2/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
	from /Users/luca/.gem/ruby/2.3.0/gems/bundler-1.11.2/lib/bundler/vendor/thor/lib/thor.rb:359:in `dispatch'
	from /Users/luca/.gem/ruby/2.3.0/gems/bundler-1.11.2/lib/bundler/vendor/thor/lib/thor/base.rb:440:in `start'
	from /Users/luca/.gem/ruby/2.3.0/gems/bundler-1.11.2/lib/bundler/cli.rb:10:in `start'
	from /Users/luca/.gem/ruby/2.3.0/gems/bundler-1.11.2/exe/bundle:19:in `block in <top (required)>'
	from /Users/luca/.gem/ruby/2.3.0/gems/bundler-1.11.2/lib/bundler/friendly_errors.rb:7:in `with_friendly_errors'
	from /Users/luca/.gem/ruby/2.3.0/gems/bundler-1.11.2/exe/bundle:17:in `<top (required)>'
	from /Users/luca/.gem/ruby/2.3.0/bin/bundle:23:in `load'

It works fine, with the macro syntax:
require 'dry-validation'

form = Dry::Validation.Form do
  key(:foo).each(:int?)
end

@jodosha this appears to work on the master branch, could you test from there and let me know if it's still an issue, thanks

@AMHOL Yes, it works! Thanks for letting me know.


Handling intermediate ssl certs ?

I only see one option for the ssl cert, how should we reference the main cert and the intermediate one?

http-server uses union, which calls createServer on http, https or spdy respectively. https.createServer and spdy.createServer both use tls.createServer under the hood, **which accepts cert, key and ca option.
(I know that wasn't obvious 😁)

@derhuerst okay,  thanks!
So... Just to be clear I need to manually edit the http-server file and add my intermediate cert as ca in the createserver method?
Sorry if that is unclear,  I am VERY new to all of this.

So... Just to be clear I need to manually edit the http-server file and add my intermediate cert as ca in the createserver method?

I haven't tried this, but it looks like you can just pass ca as a property of options.https. It looks like it will be passed through to union.createServer().

Thanks for answering !
So I edited the http-server file created after install by node, added an I argument to use to pass the ca, and added the ca line to options.https as you said.
It worked perfectly, now my doesn't throw errors because of the cert. Thanks :)
I would create a pull request but I'm not sure it would be interesting, seeing as you guys have quite a lot of them open already. Let me know :)

I would create a pull request but I'm not sure it would be interesting, seeing as you guys have quite a lot of them open already. Let me know :)

I'm not really an expert in SSL stuff, but isn't it possible to "embed" the chain into the certificate directly? At least when using Let's Encrypt, I pass fullchain.pem as cert.

Well I tried by cat-ing the two files together like for nginx as cat  intermediate.crt >> public.crt but I had an EOF error. Tried all possible permutations,  but no dice. Hence this issue in the first place

SSLLabs shows me the certificate chain for https://transport.rest/, even though I just used the Let's Encrypt fullchain.pem as cert. So it is possible.

Okay,  didn't work with a geotrust one.Gave me cert, intermediate,  and key as separate files.
Closing the issue in any case,  it's solved.  😊


mis-spelt the product name, oops  :)

Hi, mis-spelt "Configuration Manger" in the 'Important Note" just after this anchor https://docs.microsoft.com/en-us/deployoffice/change-update-channels#change-the-update-channel-with-configuration-manager

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

ID: d23ac821-9cb8-8855-598f-d1327df04fac
Version Independent ID: 78f2127a-0c6b-d236-a415-6215c582ce8b
Content: Change the Microsoft 365 Apps update channel for devices in your organization - Deploy Office
Content Source: DeployOffice/change-update-channels.md
Service: o365-proplus-itpro
GitHub Login: @DHB-MSFT
Microsoft Alias: danbrown

@DonPick Thanks for pointing that out. It's been fixed. We also checked the rest of our "Deploy Office" content to make sure we didn't have any other instances of "Manger" (we didn't).


Installation & Usage Guide

Hi can you include an Installation Guide in the README?
I'm getting this error when I clone, and run npm install; npm start:
/Library/Caches/com.apple.xbs/Sources/AppleGVA/AppleGVA-10.1.5/Sources/Slices/Driver/AVD_loader.cpp: failed to get a service for display 3
I just have an empty black window, and none of the Mac menu items do anything.

I agree. I get the exact same blank screen.

errors all over the place
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node',
1 verbose cli   '/usr/local/bin/npm',
1 verbose cli   'run',
1 verbose cli   'dev-start' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose config Skipping project config: /Users/macuser/.npmrc. (matches userconfig)
5 verbose stack Error: ENOENT: no such file or directory, open '/Users/macuser/package.json'
5 verbose stack     at Error (native)
6 verbose cwd /Users/macuser/Desktop/Reactide
7 error Darwin 16.4.0
8 error argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "dev-start"
9 error node v6.9.1
10 error npm  v3.10.8
11 error path /Users/macuser/package.json
12 error code ENOENT
13 error errno -2
14 error syscall open
15 error enoent ENOENT: no such file or directory, open '/Users/macuser/package.json'
16 error enoent ENOENT: no such file or directory, open '/Users/macuser/package.json'
16 error enoent This is most likely not a problem with npm itself
16 error enoent and is related to npm not being able to find a file.
17 verbose exit [ -2, true ]

Deco = REACT-NATIVE
reacttide = React (web not mobile)

Gottcha my bad

@jel111 don't want to be harsh but this is really early in development it hasn't even had a beta release version yet. If you don't understand how to fix your error yourself then its to early for you to try using it.

I think most of us here just want a simple guide to install. That's pretty rudimentary for a README.

On Apr 3, 2017, at 2:28 AM, Michell Gailing<EMAIL_ADDRESS>wrote:
@jel111 don't want to be harsh but this is really early in development it hasn't even had a beta release version yet. If you don't understand how to fix your error yourself then its to early for you to try using it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

When I run npm run dev in one terminal and npm run dev-start in a second terminal, Electron pops up and says: To run your app with Electron, execute the following command in your Console (or Terminal):
/Users/jackpark/Documents/Projects/DKR2/ReactIDE/reactide/node_modules/electron/dist/Electron.app/Contents/MacOS/Electron path-to-your-app
The path-to-your-app should be the path to your own Electron app.
What am I missing?

@KnowledgeGarden you did an npm i, right?

npm i says something about no repository.
Removed nodemodules, did a yarn install, then everything else as yarn rather than npm. No cigar. Tries the two runs with npm again. Same issue.

@KnowledgeGarden considering it as a bug. MacOS might be the only OS at the moment presenting this event... @JiniHendrix will probably assist you better :D

I can confirm it works on MacOS with running Yarn, then npm run dev and npm run dev-start in another term. So, I don't think this is a bug.
@KnowledgeGarden it sounds like an issue with your npm and/or node.
What version of NPM and Node are you running?
If you are not familiar with Electron, then you should head over to the quickstart for Electron to start learning about how it works since this repo is still very early in development and not fully documented. https://github.com/electron/electron-quick-start

node 5.10.0 and npm 3.8.3
I suppose I should install the latest versions.

updated node and npm.  Not sure what to do with it, but it appears to be working (i think). Thanks!

@KnowledgeGarden it's the actual state of the project. I don't think you can start any project with it, at least for now. But it's nice to see how the whole thing is being built! :)
@dustintownsend thanks for clarifying!

Hi everyone,
Some of this has been discussed at #51 and #35.

Have anyone ever setup reactide successfully. cuz i'm not able to set it up

After tried git clone on the repo:
fatal: could not create work tree dir 'reactide': Permission denied
???

@tatiana-passarella if you want to use the application rather than contribute to its source, I'd suggest getting the latest build through https://github.com/reactide/reactide/releases
If your intention is to contribute to this software you should create a issue detailing what caused this git error. Personally I can't tell what's going on as this project hasn't been updated in almost a year, so I'm not aware of its current state. Cheers


For what specific versions is it

Is the mod only for forge or for fabric too and also is the mod available for 1.19.2 or only 1.18.2/1.18.1/1.18?

forge 1.18.2 and possibly also 1.19.2


[Bugfix] Parse on errorMatcher.set / handle no errorMatcher correctly

This PR fixes two bugs:

Errors are now highlighted, when the build is finished, not when the user goes to the first error
no error matching is performed, when no errorMatcher is set

I tried to rebase this and run the test but I can't get it to work. Do you have time to look into this?

Done.
I also noticed, that the specs fail in many ways on windows, even if I start atom from cygwin. If I have time, I may look into fixing this.

Thank you so much for this! Once again, sorry for taking so long to review this


Fix Monolog Bundle config example in readme

Oh, my mistake when adding this to README.md. Sorry ! 😞

Closing, superseeded by #238


Update Set-SPOTenant.md

For some reason, one of the parameters for Set-SPOTenant shows up as "undefined".
In this change, I add the type for -ReSyncTenantPrivacyProfile param to be set to SwitchParameter so it no longer shows "undefined"

Docs Build status updates of commit efb5ebe:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenant.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@kaarins

@JohanFreelancer9

@get-itips @tseward

Ready to merge? @tseward

@liamfernandez yep I already did my approval. I believe @tiburd is responsible for performing the merge.


No service running on Raspberry pi zero

[x] I confirm that this is an issue rather than a question.

Bug report
When i install using the script on raspberry pi zero W,  there is no service created, no hyperion.config.json created and no directory /etc/hyperion
Steps to reproduce
https://releases.hyperion-project.org/
curl -sSL https://releases.hyperion-project.org/install | bash
What is expected?
Have the service running and port listening
What is actually happening?
ls -al /etc/hyperion/
ls: cannot access '/etc/hyperion/': No such file or directory
sudo systemctl status hyperion
Unit hyperion.service could not be found.
$ ls -al  /usr/share/hyperion/
total 44
drwxr-xr-x   7 root root  4096 Aug 18 15:50 .
drwxr-xr-x 118 root root  4096 Aug 18 13:19 ..
drwxr-xr-x   2 root root  4096 Aug 18 15:50 bin
drwxr-xr-x   2 root root  4096 Aug 18 15:50 effects
drwxr-xr-x   6 root root 20480 Aug 18 15:50 lib
drwxr-xr-x   2 root root  4096 Aug 18 15:50 scripts
drwxr-xr-x   2 root root  4096 Aug 18 15:50 service
$ ls /etc/systemd/system
bluetooth.target.wants                      dbus-org.freedesktop.timesync1.service  halt.target.wants            sockets.target.wants
dbus-fi.w1.wpa_supplicant1.service          default.target                          multi-user.target.wants      sshd.service
dbus-org.bluez.service                      dev-serial1.device.wants                network-online.target.wants  sysinit.target.wants
dbus-org.freedesktop.Avahi.service          getty.target.wants                      poweroff.target.wants        timers.target.wants
dbus-org.freedesktop.ModemManager1.service<EMAIL_ADDRESS>                  reboot.target.wants
dbus-org.freedesktop.nm-dispatcher.service  graphical.target.wants                  remote-fs.target.wants
Here's the complete installating log :
https://pastebin.com/8kNQRwGB
One last thing i did fix is the :
Raspberry Pi found, but SPI is not set, we write "dtparam=spi=on" to /boot/config.txt
But it is no longer /boot/config.txt that file change to /boot/firmware/config.txt
System

You can start Hyperion from your menu now

You can start Hyperion from your menu now

I’m using raspberry is lite , so no GUI

Thank you, installed the service like you documented.  I still don't understand why it did install a lot of package regarding X11 library , qt, gtk.  I did connect with MobaXterm using defaut config so maybe it pretend to use as a source for X11 ?  Because it does create an X11 server by default, maybe that is why... Have a good day.


question: fan out

I a wondering if mango provide fan out ?
this is when the producer, sends the message out ot many consumers, with each consumer getting only one of the original messages.
Its a bit like what a load balancer does in round robin sequence.

Like a load balancer.  We do have a dumb form of this in the req code where we choose one of several destinations. The algorithm used is fairly dumb so it's not well suited to making sophisticated decisions based on queuing or topology etc.
The other patterns lack this.  Only req sockets have this sort of single destination selection as its kind of nonsensical to do so for other socket types.


Display rune on /rune/RUNE

block in which rune was etched
transaction in which rune was etched
associated inscription, if any
supply
block height
transaction index
id

Done.


Basic structure

Hi @PierreBarba,
While you made a great effort in this project, I cannot proceed to review your code.
Invalid Code Review Request
Kindly add a PR description as requested previously

Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.


[Snyk] Security upgrade setuptools from 40.5.0 to 70.0.0

Snyk has created this PR to fix 2 vulnerabilities in the pip dependencies of this project.
Snyk changed the following file(s):

requirements-dev.txt

⚠ Warning
flake8 5.0.4 has requirement importlib-metadata<4.3,>=1.1.0; python_version < "3.8", but you have importlib-metadata 4.13.0.
flake8 5.0.4 has requirement pycodestyle<2.10.0,>=2.9.0, but you have pycodestyle 2.10.0.

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.
Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Regular Expression Denial of Service (ReDoS)
🦉 Improper Control of Generation of Code ('Code Injection')

Already updated


[Off-Topic] - How to make a beat detection?

This is off topic! If you do not want this, please delete this issue!
I don't want to create too many accounts for forums, so I want to ask you if you can help/explain me how to create a music beat detection in godot.
I want a pattern to move to the next step to a beat in the music.   (Is this possiblein Godot?)
I hope you can help me with that,
Gamemap
Here is an example for an pattern (later as an Animationplayer in Godot)
https://user-images.githubusercontent.com/71942164/109418456-c5918300-79c8-11eb-8801-6b06a0bdd282.mp4

I'm not an expert but I think this is certainly possible in Godot. But I really think it is better if you ask this in Godot Q&A, Godot Discord server, Godot subreddit, etc. I maybe can help you there and others can help as well.

Ok, I think i will make an account at Godot Q&A.

I will look at you Input threshold. Maybe something like that is what I need.

Somehow you send the audio data only when the input sensitivity is lower than the sound. Could you shortly explain how you did that and if it is possible to get a signal when the music is "louder"?

Yes I use the capture effect to get the microphone input for the plugin.
See:
    var stereo_data = _effect_capture.get_buffer(_effect_capture.get_frames_available())

    #Loop over the array to get the highest value.
    var max_value = 0.0
    for i in range(stereo_data.size()):
      var value = (stereo_data[i].x + stereo_data[i].y) / 2.0
      max_value = max(value, max_value)

    #If value is lower than the threshold stop
    if max_value < input_threshold:
      return

After that the logic you want to run when the threshold is reached.

Thank you!
I will try to implement this in the next few days.
Would the audio capture also work with music files or only with a mic?

Yes, you just have to add the capture effect to the same audio bus you play your music in and you will be able to capture it.

I'm glad to tell you that the beat detection works :)
Thanks a lot for this code!
I have not done any fine tuning yet.
Here is an example (with audio):
https://user-images.githubusercontent.com/71942164/109793866-7e4c0200-7c15-11eb-947c-6add51a47891.mp4


Add GitHub logo to sponsoring page

@ekohl yes. let me clarify the text.

@ekohl should be fine now.


"clear keys" blinking,  in import seed

If the user leave the space empty, where he needs to enter "clear keys", then the text with "Type 'clear keys'  below to confirm:" should blink, or change color, or whatever to get the attention of the user.

Becoming red now
https://github.com/clemahieu/raiblocks/commit/5072a14dd6ad982bdb77c6a7ce4b911de04c438b


[fix][zeta] fix can't release resource issue

Purpose of this pull request
close #6761

Does this PR introduce any user-facing change?

How was this patch tested?

Check list

[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update change log that in connector document. For more details you can refer to connector-v2
Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist

[ ] Update the release-note.

will add ut later

cc @Hisoka-X

please retry ci


fix(rbac): add more static plugins to RBAC list

Description
Add more static plugins to the RBAC list. These plugins are required to retrieve plugin permissions and condition rules, providing them to the frontend via REST.
Which issue(s) does this PR fix

Fixes #?

PR acceptance criteria
Please make sure that the following steps are complete:

[ ] GitHub Actions are completed and successful
[ ] Unit Tests are updated and passing
[ ] E2E Tests are updated and passing
[ ] Documentation is updated if necessary (requirement for new features)
[ ] Add a screenshot if the change is UX/UI related

How to test changes / Special notes to the reviewer

LGTM

@kadel Sorry, I don't have rights to merge.

Looks like the CI is failing because you are missing a changeset. Can you please add one?


Images are not loaded..

Hi there,
I am trying to use your typescript webpack teact starter project..and its great repo for starting point.. thanks for sharing and hosting the code..
However i am unable to use it for images...
Meaning if i use
< img src="someimage.jpg" />
In my comppnent.. and the image exists in the same folder as the component.. it stll doesnt show...
I have tried to use
< img src="/assets/someimage.jpg" />
as a path and
also tried to use
"import statement in the component.tsx...
e.g import img from "./someimage.jpg"
but none of the above options work ..
Can you please show me with example how to achieve this?
Thanks a million.

This pull request adds example how to use image #15

Hi Pepaar,
Thanks for showing the example in the pull request above.
I have tried this option, however the typescript compiler is complaining and giving me following error.
error TS2322: Type '{}' is not assignable to type 'string'.
I am using latest version of typescript..
can you please help?
Regards,
Hitesh


[BUG] expect_row_values_to_have_data_for_every_n_datepart can fail if model has never been run

Is this a new bug in dbt-expectations?

[x] I believe this is a new bug in dbt-expectations
[x] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
The run_query operation in expect_row_values_to_have_data_for_every_n_datepart can fail if test_start_date or test_end_date are not specified and the model dbt-expectations is testing hasn't been created yet in the target DB.
In our case, this happens at the dbt compile step in a CI build that validates the dbt project associated with a PR is able to compile.
While I don't expect tests to pass if a model doesn't exist in a DB, I do generally want compile to complete, and this blocks that.
Expected Behavior
dbt compile is able to complete when using expect_row_values_to_have_data_for_every_n_datepart even if dbt build/run hasn't been run on a model yet.
Steps To Reproduce

Create a new model and don't run it.

# models/datamart/expectations_test.sql
{{config(
    schema='datamart',
    materialized='view',
) }}

select '2023-01-01'::date as foo
union all
select '2023-01-02'::date as foo
union all
select '2023-01-03'::date as foo
union all
select '2023-01-04'::date as foo
union all
select '2023-01-05'::date as foo

Create a expect_row_values_to_have_data_for_every_n_datepart against that new model

# models/datamart/expectations_test.yml
version: 2

models:
  - name: expectations_test
    tests:
      - dbt_expectations.expect_row_values_to_have_data_for_every_n_datepart:
          date_col: foo
          date_part: day

Try and compile the model

❯ dbt compile -m models/datamart/expectations_test.sql
00:43:58  Running with dbt=1.6.6
00:43:58  Registered adapter: snowflake=1.6.4
00:44:01  Found 729 models, 22 snapshots, 2244 tests, 392 sources, 9 exposures, 0 metrics, 791 macros, 0 groups, 0 semantic models
00:44:01
00:44:07  Concurrency: 6 threads (target='dev_snowflake')
00:44:07
00:44:08  Encountered an error:
Runtime Error
  Database Error in test dbt_expectations_expect_row_values_to_have_data_for_every_n_datepart_expectations_test_foo__day (models/datamart/expectations_test.yml)
    002003 (42S02): SQL compilation error:
    Object 'DVERHEY_DEV.DATAMART.EXPECTATIONS_TEST' does not exist or not authorized.

Optional: Add a start/end date boundary and notice the error no longer repros, because the macro doesn't enter the problem code path

# models/datamart/expectations_test.yml
version: 2

models:
  - name: expectations_test
    tests:
      - dbt_expectations.expect_row_values_to_have_data_for_every_n_datepart:
          date_col: foo
          date_part: day
          test_start_date: '2023-01-01'
          test_end_date: '2023-01-05'

❯ dbt compile -m models/datamart/expectations_test.sql
00:46:43  Running with dbt=1.6.6
00:46:43  Registered adapter: snowflake=1.6.4
00:46:45  Found 729 models, 22 snapshots, 2244 tests, 392 sources, 9 exposures, 0 metrics, 791 macros, 0 groups, 0 semantic models
00:46:46
00:46:52  Concurrency: 6 threads (target='dev_snowflake')
00:46:52
00:46:53  Compiled node 'expectations_test' is:
...

Environment
- OS: MacOS 14.1
- Python: 3.9.16
- dbt: 1.6.6
- dbt-expectations: 0.10.0

Which database adapter are you using with dbt?
Snowflake
Additional Context
I don't have any great suggestions on how to fix this beyond making the date boundary required - being able to use expect_row_values_to_have_data_for_every_n_datepart without a date boundary is a nice feature.

having the same issue!

Facing the same issue, we had to use the workaround suggested here to progress.


Use spread

Issue

The javascript actions operator is difficult to maintain.
Vectorization of integration tests currently depends on the github ci language.

Solution
Use spread.

[ ] task/suite or promtool check rules and promtool test rules (refs: 1, 2, 3)

References:

https://github.com/canonical/rockcraft/blob/main/spread.yaml
https://github.com/canonical/chisel/blob/main/spread.yaml
arm backend: https://github.com/snapcore/snapd/blob/master/spread.yaml#L199
https://github.com/canonical/charmcraft/blob/main/tests/spread/charms/k8s-operator/task.yaml

Testing Instructions
$ spread

@cmatsuoka would you be able to take a look at this draft?

Wdyt about the file organization?
Any idea why it hangs?

$ spread -v
2024-01-23 22:32:45 Found /home/ubuntu/code/o11y/prometheus-k8s-operator/spread.yaml.
2024-01-23 22:32:48 Project content is packed for delivery (19.59MB).
2024-01-23 22:32:48 If killed, discard servers with: spread -reuse-pid=93746 -discard
2024-01-23 22:32:48 Allocating lxd:ubuntu-20.04...
2024-01-23 22:32:48 Using cached LXD image for lxd:ubuntu-20.04: 28edbe767c2e
2024-01-23 22:32:56 Waiting for lxd container spread-8-ubuntu-20-04 to have an address...
2024-01-23 22:32:58 Allocated lxd:ubuntu-20.04 (spread-8-ubuntu-20-04).
2024-01-23 22:32:58 Connecting to lxd:ubuntu-20.04 (spread-8-ubuntu-20-04)...
2024-01-23 22:33:03 Connected to lxd:ubuntu-20.04 (spread-8-ubuntu-20-04) at <IP_ADDRESS>.
2024-01-23 22:33:03 Sending project content to lxd:ubuntu-20.04 (spread-8-ubuntu-20-04)...
2024-01-23 22:33:04 Preparing lxd:ubuntu-20.04 (spread-8-ubuntu-20-04)...
2024-01-23 22:33:24 Preparing lxd:ubuntu-20.04:tests/spread/k8s/ (spread-8-ubuntu-20-04)...
2024-01-23 22:38:24 WARNING: spread-8-ubuntu-20-04 (lxd:ubuntu-20.04:tests/spread/k8s/) running late. Current output:
-----
+ snap install microk8s --channel=1.26-strict/stable
2024-01-24T03:34:31Z INFO task ignored
microk8s (1.26-strict/stable) v1.26.11 from Canonical** installed
+ usermod -a -G snap_microk8s ubuntu
+ microk8s status --wait-ready
-----
.
2024-01-23 22:43:24 WARNING: spread-8-ubuntu-20-04 (lxd:ubuntu-20.04:tests/spread/k8s/) running late. Output unchanged.
2024-01-23 22:48:23 Error preparing lxd:ubuntu-20.04:tests/spread/k8s/ (spread-8-ubuntu-20-04) :
-----
+ snap install microk8s --channel=1.26-strict/stable
2024-01-24T03:34:31Z INFO task ignored
microk8s (1.26-strict/stable) v1.26.11 from Canonical** installed
+ usermod -a -G snap_microk8s ubuntu
+ microk8s status --wait-ready

<kill-timeout reached>
-----
.
2024-01-23 22:48:23 Discarding lxd:ubuntu-20.04 (spread-8-ubuntu-20-04)...
2024-01-23 22:48:25 Successful tasks: 0
2024-01-23 22:48:25 Aborted tasks: 1
2024-01-23 22:48:25 Failed suite prepare: 1
    - lxd:ubuntu-20.04:tests/spread/k8s/
error: unsuccessful run

Closing this PR. Please reopen it if it's still relevant and you want it merged.


conflict with fcitx

when enable fcitx pulgin        Plug  'h-youhei/vim-fcitx'
vim-multiple-cursors will be work error

@rinetd could you please provide us with:

a minimal .vimrc
the steps to repoduce the bug
the error message or bad behavior we are supposed to see

Without that, we won't be able to help you.
Thanks in advance :)
Antoine

Step to reproduce the bug on Ubuntu:

install fcitx: sudo apt install fcitx
use the following .vimrc:

call plug#begin('~/.vim/plugins_by_vimplug')
Plug '/home/amadec/source/vim-multiple-cursors'
Plug 'h-youhei/vim-fcitx'
call plug#end()

set nocompatible               " get rid of vi compatibility

Any PR or workaround is welcome.

if i enable  Plug 'h-youhei/vim-fcitx'
vim-multiple-cursors will not work
Plug 'terryma/vim-multiple-cursors'
Plug 'h-youhei/vim-fcitx'
let g:multi_cursor_use_default_mapping=0
let g:multi_cursor_start_word_key='<C-n>'
let g:multi_cursor_next_key='<C-n>'
let g:multi_cursor_prev_key='<C-p>'
let g:multi_cursor_skip_key='<C-x>'
let g:multi_cursor_quit_key='<Esc>'

call plug#begin('~/.vim/bundle')

let g:plug_threads = 8
let g:plug_timeout = 3600

for files in s:plug_files
  for f in split(glob(s:vim_home.files), "\n")
    exec "source ".f
  endfor
endfor
call plug#end()

set nocompatible

aftet enbale fctix
when i select multi words  and then press s key
this section will be insert:
<Plug>(multiple-cursors-input)lug>(multiple-cursors-apply)

aftet enbale fctix
when i select multi words and then press s key
this section will be insert:
<Plug>(multiple-cursors-input)lug>(multiple-cursors-apply)

The function of s key is delete current char and insert.


Support for T84A1 (S100 Wall Light Cam)

Support for T84A1 (S100 Wall Light Cam) does not exist.
I want support for this cam :)

.

.

Same

wait for this to be completed: https://github.com/bropat/eufy-security-client/issues/318
nothing required from integration side, it needs support from add-on


Make type class versions of SQSStream, MessageStream, et al

While we're here, let's look at whether all these methods should really return Try or Either.

This has sat untouched for three years, and I’m not even sure we use all these classes any more – we can close this for now, and revisit it if/when we're doing Scala-libs work again.


Feature request: Multiple country selection

In addition to just picking one country, it would be great for this to support selecting multiple countries. Thanks!

bump

want multiple countries too


Hiding stack trace details on click of something else

When looking at e.g., https://upload.clinicjs.org/public/ffb89434db9839063ae706417196ed615b2356e2f3d3adc2a4e646e76892eac5/15662.clinic-bubbleprof.html I noticed that the stack trace will not vanish when I click on a different node that does not show the stack trace right away. It will zoom into that node in the background tough.
I think it would be best to always hide the stack trace when clicking on a different node.

Good spot, frames aren't closed on opening another node in the same layout, but they are still closed on other types of navigation e.g. arrow shortcuts and navigation using breadcrumbs, buttons, search etc.
I think this is a regression that slipped through when I fixed a separate bug with animation chaining opening frames at the end. I'll add it to the list.


How to set Start Parameter in windows service

My Application  have to get http port to run.
I have to set the port number in windows start parameter

Use configuration file or pass args on install.
On Tue, Oct 18, 2016, 03:51 Vigneshr6<EMAIL_ADDRESS>wrote:

My Application have to get http port to run.
I have to set the port number in windows start parameter
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kardianos/service/issues/75, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAuFsQLKw3fXB7i5ecqhK2LevEyHSJ6Yks5q1KS_gaJpZM4KZpPD
.

The link you gave is not valid for my account.
Can u give me the Sample code?

I used your logger.go program to run my go application as a service in windows.
But It did not work in linux.
Do you have any sample program for linux?

Github issues is not really a place to ask for help with writing your code. They are to report problems with the product.
You might be better go and check stackoverflow.com or ask the question there.

Use configuration file or pass args on install.

Or the library could pass the start arguments instead of ignoring them: #82  :)

Github issues is not really a place to ask for help with writing your code. They are to report problems with the product.

I think it is the right place when the confusion is partly caused by a missing feature.

To configure service to run an executable with a given set of arguments, set https://godoc.org/github.com/kardianos/service#Config.Arguments to the arguments before install. Then when it is started the windows service manager will pass those arguments to the executable. To access them at runtime you should use https://golang.org/pkg/os/#Args .
Please let me know if this answers your questions.

Yes This is what I asked?
thanks @kardianos


no-mixed-operators rule

http://eslint.org/docs/rules/no-mixed-operators
It could increase readability in my opinion

I agree with this

Ok for ERROR with allowSamePrecedence at false


Implicit call tracing in xref creation

The current call graph maybe incomplete.
Fro example, in the following code snippet, I think that the method onCreate() will invoke method procedure() which invokes methods download() and activate(). However, when I obtain the call graph, I
find that onCreate() only invokes an initialize function AlertActivity$1;->, which is generated by the compiler (I guess).
The smali code show that the method procedure() is invoked by method run(), but there does not exist an edge between onCreate() and run(). So, is there necessary to add an edge between onCreate() and run(), such that there is a relationship like onCreate()->run()->procedure()->download()/activates()?
code snippet of Dropdialer.apk
`public class AlertActivity extends Activity {
protected void onCreate(Bundle savedInstanceState) {

    this.workThread = new Thread(new Runnable() {
        public void run() {
            AlertActivity.this.procedure();
            Log.d("Thread", "end thread");
            AlertActivity.this.handler.sendEmptyMessage(0);
        }
    });
}

public void procedure() {
    download("http://dl.dropbox.com/u/87265868/srv.txt", "srv.txt");
    activate(parse("srv.txt"));
    Log.d("procedure", "end");
}

public void download(String inurl, String name) {

}

public void activate(String activateCode) {

}

}`
smali code (simplified)
`.class AlertActivity$1;
direct methods
.method constructor (AlertActivity;)V
.locals 0
.prologue
.line 1
iput-object p1, p0, AlertActivity$1;->this$0:AlertActivity;

.line 133
invoke-direct {p0}, Ljava/lang/Object;-><init>()V

return-void

.end method
virtual methods
.method public run()V
.locals 2
.prologue
.line 137
iget-object v0, p0, AlertActivity$1;->this$0:AlertActivity;

invoke-virtual {v0}, AlertActivity;->procedure()V

.end method
`

It looks like the call between onCreate() and run() is never found as run() is never called explicitly and is also "hidden" inside the anoymous Runnable object.
Inside onCreate there is this bytecode:
      58 (0x00000118) new-instance                   v0, Ljava/lang/Thread;
      59 (0x0000011c) new-instance                   v1, Lcom/nnew/superMariowallpapers/AlertActivity$5;
      60 (0x00000120) invoke-direct                  v1, v3, Lcom/nnew/superMariowallpapers/AlertActivity$5;-><init>(Lcom/nnew/superMariowallpapers/AlertActivity;)V
      61 (0x00000126) invoke-direct                  v0, v1, Ljava/lang/Thread;-><init>(Ljava/lang/Runnable;)V
      62 (0x0000012c) iput-object                    v0, v3, Lcom/nnew/superMariowallpapers/AlertActivity;->workThread Ljava/lang/Thread;

So, the call to the constructor is recorded but not the run, as it is called implictly by the Thread.
Maybe we can add an implicit call tracer to _create_xref... But this will take some time.

Btw are there other implicit calls? Would be nice to record them in such a way:
Classname, methodname, object type, called method
Ljava/lang/Thread; <init>, Ljava/lang/Runnable; run
...

Thanks for your reply and these nice works!
Actually, there are five implicit calls in methods onCreate() of class AlertActivity of Dropdialer.apk, they are:
[Lcom/nnew/superMariowallpapers/AlertActivity; onCreate(),  Landroid/view/View$OnClickListener; onClick]
[Lcom/nnew/superMariowallpapers/AlertActivity; onCreate(),  Landroid/view/View$OnClickListener; onClick]
[Lcom/nnew/superMariowallpapers/AlertActivity; onCreate(), Landroid/content/DialogInterface$OnClickListener; onClick]
[Lcom/nnew/superMariowallpapers/AlertActivity; onCreate(), Landroid/os/Handler; handleMessage]
[Lcom/nnew/superMariowallpapers/AlertActivity; onCreate(), Ljava/lang/Runnable; run]
These implicit calls are caused by creating a new object using keyword new. For instance, the implicit call between onCreate() and  run() is caused by the following code snippet.
this.workThread = new Thread(new Runnable() {
            public void run() {
                AlertActivity.this.procedure();
                Log.d("Thread", "end thread");
                AlertActivity.this.handler.sendEmptyMessage(0);
            }
        });

In this case, the compiler will generate an auxiliary class like AlertActivity$5. So, a solution is to add edges from onCreate() to all methods in auxiliary class  AlertActivity$5.

So, a solution is to add edges from onCreate() to all methods in auxiliary class AlertActivity$5.

Is it a good idea to use all methods? I think one can gather a list of all implicit calls and create the correct edge. Of course, you need to know all implicit calls beforehand, which might be quite hard.
But it should be possible to implement such a system.
But then there are again new problems: What about conditional implicit calls like callbacks?

please leave this open, maybe we can implement this some day


feat: Add experiment setup output option

Closes #98

@jkriwet : This feature enables mat files to get smaller, adds postprocessing inside simulate, enables tests for Dymola-API in CI (fixing some bugs) and enable python 3.12. Do you have time for a review? :)