[Snyk] Upgrade org.springframework.boot:spring-boot-starter-thymeleaf from 2.2.2.RELEASE to 2.7.18

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade org.springframework.boot:spring-boot-starter-thymeleaf from 2.2.2.RELEASE to 2.7.18.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 89 versions ahead of your current version.
The recommended version was released 5 months ago, on 2023-11-23.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Checkmarx One – Scan Summary & Details – b7fb228d-6500-458a-a34f-703b73930b36
Fixed Issues

Severity
Issue
Source File / Package

Passwords And Secrets - Generic Password
/dashboard.yml: 37

WORKDIR Path Not Absolute
/Dockerfile: 1

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 21

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 9

Host Namespace is Shared
/docker-compose.yml: 11

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 9

Host Namespace is Shared
/docker-compose.yml: 54

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 30

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 14

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 13

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 9

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 22

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 20

Host Namespace is Shared
/docker-compose.yml: 9

Host Namespace is Shared
/docker-compose.yml: 10

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 10

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 15

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 16

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 4

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 9

Host Namespace is Shared
/docker-compose.yml: 15

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 9

Host Namespace is Shared
/docker-compose.yml: 76

Host Namespace is Shared
/docker-compose.yml: 9

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 9

Host Namespace is Shared
/docker-compose.yml: 16

Host Namespace is Shared
/docker-compose.yml: 7

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 30

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 14

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 18

Host Namespace is Shared
/docker-compose.yml: 4

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 28

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 14

Host Namespace is Shared
/docker-compose.yml: 9

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 63

Host Namespace is Shared
/docker-compose.yml: 22

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 21

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 9

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 11

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 83

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 65

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 4

Host Namespace is Shared
/docker-compose.yml: 16

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 11

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 11

Host Namespace is Shared
/docker-compose.yml: 37

Host Namespace is Shared
/docker-compose.yml: 9

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 4

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 11

Host Namespace is Shared
/docker-compose.yml: 9

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 45

Host Namespace is Shared
/docker-compose.yml: 15

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 12

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 25

Host Namespace is Shared
/docker-compose.yml: 9

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 24

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 14

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 14

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 12

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 9

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 35

Host Namespace is Shared
/docker-compose.yml: 43

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 20

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 21

Host Namespace is Shared
/docker-compose.yml: 74

Host Namespace is Shared
/docker-compose.yml: 81

Host Namespace is Shared
/docker-compose.yml: 15

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 43

Host Namespace is Shared
/docker-compose.yml: 15

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 10

Host Namespace is Shared
/docker-compose.yml: 74

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 54

Host Namespace is Shared
/docker-compose.yml: 16

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 35

Host Namespace is Shared
/docker-compose.yml: 35

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared
/docker-compose.yml: 7

Host Namespace is Shared
/docker-compose.yml: 9

Host Namespace is Shared
/docker-compose.yml: 3

Host Namespace is Shared

More results are available on AST platform


Update CHANGELOG with bug fixes since 12.0.2

Can you tag 12.0.3 as tomorrow's date for this and the release notes? Otherwise :+1:

:ship:


DatetimeAdd test from FunctionTests.cs fails on my local machine

Description of the issue
When running build.ps1 on my machine, I get the follow error from DatetimeAdd test:
[xUnit.net 00:00:07.34]     PSRule.Rules.Azure.FunctionTests.DateTimeAdd [FAIL]
  Failed PSRule.Rules.Azure.FunctionTests.DateTimeAdd [12 ms]
  Error Message:
   Assert.Equal() Failure
Expected: 2020-03-30T00:53:14.0000000+11:00
Actual:   2020-03-29T23:53:14.0000000Z
  Stack Trace:
     at PSRule.Rules.Azure.FunctionTests.DateTimeAdd() in C:\Users\armcleod\Documents\github-repos\PSRule.Rules.Azure\tests\PSRule.Rules.Azure.Tests\FunctionTests.cs:line 813
Results File: C:\Users\armcleod\Documents\github-repos\PSRule.Rules.Azure\reports\armcleod_DESKTOP-6LBF3IE_2021-08-18_16_57_30.trx

Failed!  - Failed:     1, Passed:   113, Skipped:     0, Total:   114, Duration: 265 ms - PSRule.Rules.Azure.Tests.dll (netcoreapp3.1)
ERROR: Command exited with code 1. {
            # Test library
            dotnet test --logger trx -r (Join-Path $PWD -ChildPath reports/) tests/PSRule.Rules.Azure.Tests
        }
At C:\Users\armcleod\Documents\github-repos\PSRule.Rules.Azure\pipeline.build.ps1:222 char:9
+         exec {
+         ~~~~~~
At C:\Users\armcleod\Documents\github-repos\PSRule.Rules.Azure\pipeline.build.ps1:214 char:1
+ task TestDotNet {
+ ~~~~~~~~~~~~~~~~~
At C:\Users\armcleod\Documents\github-repos\PSRule.Rules.Azure\pipeline.build.ps1:510 char:1
+ task Test Build, Rules, TestDotNet, TestModule
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Build FAILED. 15 tasks, 1 errors, 0 warnings 00:00:57.3449600
Invoke-BuildExec: C:\Users\armcleod\Documents\github-repos\PSRule.Rules.Azure\pipeline.build.ps1:222:9
Line |
 222 |          exec {
     |          ~~~~~~
     | Command exited with code 1. {             # Test library             dotnet test --logger trx -r (Join-Path $PWD
     | -ChildPath reports/) tests/PSRule.Rules.Azure.Tests         }

Code: https://github.com/Azure/PSRule.Rules.Azure/blob/main/tests/PSRule.Rules.Azure.Tests/FunctionTests.cs#L801-L820
Expected behaviour
Tests should pass. Although this seems like an issue on my machine with time zones. It seems to be the second assert that is problematic.
I can actually force this test to pass by doing this:
[Fact]
[Trait(TRAIT, TRAIT_DATE)]
public void DateTimeAdd()
{
    var context = GetContext();
    var utc = DateTime.Parse("2020-04-07 14:53:14Z", new CultureInfo("en-US")).ToUniversalTime(); # Force to UTC format.

    var actual1 = DateTime.Parse(Functions.DateTimeAdd(context, new object[] { utc.ToString("u"), "P3Y" }) as string, new CultureInfo("en-US"));
    var actual2 = DateTime.Parse(Functions.DateTimeAdd(context, new object[] { utc.ToString("u"), "-P9D" }) as string, new CultureInfo("en-US"));
    var actual3 = DateTime.Parse(Functions.DateTimeAdd(context, new object[] { utc.ToString("u"), "PT1H" }) as string, new CultureInfo("en-US"));

    Assert.Equal(utc.AddYears(3), actual1.ToUniversalTime());
    Assert.Equal(utc.AddDays(-9), actual2.ToUniversalTime().AddHours(1)); # Add one hour
    Assert.Equal(utc.AddHours(1), actual3.ToUniversalTime());

    Assert.Throws<ExpressionArgumentException>(() => Functions.DateTimeAdd(context, null));
    Assert.Throws<ExpressionArgumentException>(() => Functions.DateTimeAdd(context, new object[] { }));
    Assert.Throws<ExpressionArgumentException>(() => Functions.DateTimeAdd(context, new object[] { 1, 2 }));
    Assert.Throws<ExpressionArgumentException>(() => Functions.DateTimeAdd(context, new object[] { utc.ToString("u"), 2 }));
}

Which makes me believe this could be a DST issue, since adding an hour to the second Assert passes the test. Could be completely wrong about this 😄 . This definitely isn't a fix because the CI would break since it doesn't seem to be affected by this issue.
I could probably try reinstalling dotnet to see if that fixes the issue. Or we could set a specific time zone and use that?
Environment
$PSVersionTable:
Name                           Value
----                           -----
PSVersion                      7.1.4
PSEdition                      Core
GitCommitId                    7.1.4
OS                             Microsoft Windows 10.0.19043
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

dotnet version: 5.0.303

I guess another thing to consider is that should we separate the tests from the build? Like create a test.ps1 script that runs just the tests. At least this way builds will be quicker when running locally and don't rely on tests passing. Just a thought :smiling.

@ArmaanMcleod If just updating var utc = DateTime.Parse("2020-04-07 14:53:14Z", new CultureInfo("en-US")).ToUniversalTime(); alone fixes the issue I think that is fine. The intent it that it should be UTC anyway by specifying Z in the time string. But unusual it is not automatically picking it up as UTC.
Does it fix the issue? or is the +1 hour also required?

@ArmaanMcleod

I guess another thing to consider is that should we separate the tests from the build? Like create a test.ps1 script that runs just the tests. At least this way builds will be quicker when running locally and don't rely on tests passing.

Did you try the VSCode build task? Should work a treat to just build instead of build + test. But I'm open to this if you think it would improve your workflow. Feel free to open an issue and PR to close the loop. 😄

@ArmaanMcleod If just updating var utc = DateTime.Parse("2020-04-07 14:53:14Z", new CultureInfo("en-US")).ToUniversalTime(); alone fixes the issue I think that is fine. The intent it that it should be UTC anyway by specifying Z in the time string. But unusual it is not automatically picking it up as UTC.
Does it fix the issue? or is the +1 hour also required?

@BernieWhite Unfortunately the +1 is required. var utc = DateTime.Parse("2020-04-07 14:53:14Z", new CultureInfo("en-US")).ToUniversalTime(); does force the time format to be the same e.g. 2020-03-29T13:53:14.0000000Z, but the hours are still 1 apart when doing Assert.Equal().

Did you try the VSCode build task? Should work a treat to just build instead of build + test. But I'm open to this if you think it would improve your workflow. Feel free to open an issue and PR to close the loop. 😄.

Ah didn't realize that task existed, I think that should be fine 🎉 . I might add some extra documentation to https://github.com/Azure/PSRule.Rules.Azure/blob/main/docs/install-instructions.md#building-from-source to include this way for anyone else who is just wanting to do a simple build.

@ArmaanMcleod Ok. I adjusted my time zone to match yours with DST enabled and can repo the issue.

Thanks @BernieWhite for looking into this 🙂 . I knew it had something to do with DST but didn't get much time to look into the issue this week with all my customer work.


Message viewer: Subgroup Underlying Instrument not present in visual representation

Here is a sample of a FIX message that has underlying symbol information:
8=FIX.4.4^9=316^35=R^34=45^49=XXXXXXXX^52=20230117-09:41:05.721^56=ENDPOINT^58=a repo req for ofrs^131=Q_RQ_REPO_1^1300=MktName^146=1^55=N/A^167=REPO^917=20230417^711=1^311=STCK^879=3000^537=1^54=2^38=5000^15=AZN^1=111000^581=3^44=2.5^453=3^448=YYYYYYYY^447=B^452=33^448=ZZZZZZZZ^447=B^452=33^448=KKKKKKKK^447=B^452=33^10=802^
In message viewer, the visual representation of the message, the UnderlyingInstrument group information is not displayed. Interesting, however, that the FinancingDetails subgroup is shown.

Are you using the same dictionary file as in the previous issue?

yes, I am.
I am using as an alternate tool FixPusher, and that one  has no problem with the message structure as defined

Issue fixed in https://github.com/yaalalabs/fixyl/releases/tag/v1.0.8
Please re-open if this re-creates again.


Issues with Redis Docker

1:M 09 Apr 01:26:27.413 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
redis       | 1:M 09 Apr 01:26:27.413 # Server started, Redis version 3.0.7
redis       | 1:M 09 Apr 01:26:27.413 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis       | 1:M 09 Apr 01:26:27.414 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.

Not using redis for anything anymore.


feat: update layout dependency

Checklist

[ ] npm test passes
[ ] tests and/or benchmarks are included
[ ] commit message follows commit guidelines

Description of change

Update @antv/layout dependency for mobile and pc packages

Thanks for your pr!


Panda CSS default theme not applying

Description
When I apply a padding, margin, height to a component using the default panda CSS theme unit measurements (https://panda-css.com/docs/customization/theme), nothing is applied and in the DOM inspection, the values are not recognized (striked-through). For it to work, I have to use px or rem.
Code snippet:
export const IntroSection = ({ introContent }: IintroSection) => {
  const { title, introText } = introContent;

  return (
    <SmallerWrapper>
      {title && (
        <h2
          className={css({
            textStyle: "text700_xl",
            mb: "8",
            lg: { textStyle: "text700_3xl" },
          })}
        >
          {title}
        </h2>
      )}
      {introText && (
        <MarkdownContent content={introText} paragraphFontSize="lg" />
      )}
    </SmallerWrapper>
  );
};

Screenshot of the DOM element:

Please ignore the link to reproduction since it is not possible for me to reproduce my application on stackblitz and set up is different.
Link to Reproduction
https://stackblitz.com/edit/vitejs-vite-33fjgd?file=src%2FApp.tsx,postcss.config.cjs&terminal=dev
Steps to reproduce

Assign a panda CSS unit to the css in any element
Go to the web browser
Check the DOM and UI
changes are ignored

JS Framework
React, Next, Typescript
Panda CSS Version
0.19.0
Browser
Google Chrome Version 121.0.6167.85 (Official Build) (arm64)
Operating System

[X] macOS
[ ] Windows
[ ] Linux

Additional Information
No response

Hi @bikeclub-caroline,
Could you attach a valid reproduction? The attached repro doesn't reflect the code snippet you shared.
From the look of things, I sense you have a custom preset or theme, but it's hard to tell.
Consider adding this to your panda config
include: ["@pandacss/preset-base"]

you might also want to update your panda version to latest (v0.28.0)

Hello, updating to the latest version worked for me. thanks! I haven't added  include: ["@pandacss/preset-base"]
Do I need it, what does it do? Thank you

if you use another custom preset then it's needed to explicitly import the built-in one
https://panda-css.com/docs/customization/presets#which-panda-presets-will-be-included-
if you don't use a custom preset then you don't need to do anything !

Ok, thanks a lot

Hello,
Sorry is it possible to reopen this ticket, please. I thought my problem was solved but, when I add a chakra-ui default theme measurement, it actually converts it to px. ie: margin set to "2" will show margin: "2px" in the DOM:

If you need me to update the link to reproduction with my files, could you indicate which files you want me to copy?
Thank You very much

your panda config and a file containing a reproduction to your issue should be enough

thank you. I have updated the folder with panda.config, package.json, and an examoke if component IntroSection.tsx where I have the issue : https://stackblitz.com/edit/vitejs-vite-33fjgd?file=package.json,panda.config.ts,IntroSection.tsx&terminal=dev

your stackblitz link isnt working... this is not a valid minimal reproduction 😓
in the future please make a valid minimal reproduction, this will help a lot for non-trivial issues like this

that being said, just looking at the config was enough without needing to run the app to spot the issue:
you didn't wrap the theme.tokens in extend so you're overriding every tokens provided by the default presets
so you need to change it like this:
theme: {
-    tokens: {
-      colors,
-    },
    extend: {
+     tokens: {
+         colors
+    },
      textStyles,
      layerStyles,
      breakpoints,
    },
  },


[MB-6949] Add BGN EDI segment and tests

Description
This PR adds the BGN segment and its validations as defined in this mapping doc.
Reviewer Notes

I added tests for Parse and StringArray that we don't seem to have in most other segments.  I'm getting 100% coverage (at least according to GoLand) where most of the other segments show 0% coverage.  That's perhaps a little misleading since we do test validations in all segments, but we aren't getting credit for those since those are are defined via struct tags.
The BGN segment has a Date field, but I'm storing it as a string rather than a time.Time to match what the other date/time fields do in other segments.  I'm not sure it matters much for this since it's got to be converted to a string anyway to create the EDI.

Setup
There's no way to use this in the app yet, but make server_test will exercise the code.  Also, please verify the fields/validations against the mapping doc.
Code Review Verification Steps

[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change
Spreadsheet of mapped values
824 specification

Messages

:book:
:link: MB-6949

  Generated by :no_entry_sign: dangerJS against 8e2daad7c12a9814482e211cfd0768451d07f400


[REEF-91] Create a script for publishing REEF website

Write a script for updating local contents of the website to
the Apache SVN server.

The script itself
Changes in pom.xml and website/pom.xml to prevent unnecessary builds

JIRA: REEF-91
Note and thanks (not included in commit message):

You do not have to have a svn client installed to run the script
@johnyangk kindly helped me in the Apache committer authentication process involved, since I am not a committer.

@jsjason Is this ready to be merged?

@bgchun Yes, it is.
2015년 2월 20일 금요일, Byung-Gon<EMAIL_ADDRESS>작성한 메시지:

@jsjason https://github.com/jsjason Is this ready to be merged?
—
Reply to this email directly or view it on GitHub
https://github.com/apache/incubator-reef/pull/83#issuecomment-75178252.


[3|Topic Detail Page] Topic Header

 🍰 Appetite 🍰

Property
Value

Points
10 points

Difficulty rating
★★☆☆☆

Maximum Assignees
2 person

🤔 Problem Statement

Create a header for the Topic Detail Page above the List of Topic Resources
The Header will have a background image that is pulled down from Payload CMS. On the top left corner is a hamburger button that does nothing for now. On the top right is a feedback button that for now also does nothing
🧪 Required Tests
Mainly screenshot tests.
Review the Code & Testing Guidelines for more info.
⚠ Careful about:
No major rabbit holes identified. But always be careful with scope creep!
🤖 Technologies focused on in this feature

React
Tailwind
Shadcn
NextJS

Can I work on this?

can I work on it? @hzz4343

@project manger, May I work on this one? Thanks

@project-manager, may I work on this one? Thanks

@hjing2 sure

@Tyson-a you're in!


Compilations fails on Arduino Mega

If I try to compile
#include <StateMachine.h>

void setup() {}

void loop() {}

for Arduino Mega with v1.0.13 I get Compilation error: Error: 2 UNKNOWN: exit status 1.

Reinstall Arduino (try with non Arduino IDE) and reinstall your board specific files

This fails to compile on arduino because the linked list library includes the following in a "tests.cpp" file:
#include
std::cout<< "Tests pass"<< std::endl;
I am not that experienced but it does not appear that iostream is supported with Arduino.
when I comment out these two lines, then the whole thing compiles successfully

BTW: I don't need the lib anymore and discontinued investigating this issue.

I followed the step to allow StateMachine to compile and download to my Arduino but unfortunately is does not output anything to the serial monitor.  I have set the baud rate to 19200 in the program and on IDE but its make no difference.  I am a novice so on a steep learning curve so any help greatly received.


 I think is a lot of work for a mobile device to filter this out.
One solutiion could be take the user from the authorization token? or just ask me my id in the service call.
keep me updated 👍

Fixed and published


Allow setting of container scale with ENV variable

:rocket: deployment of nhsuk/profiles-etl-combiner succeeded (http://profiles-etl-combiner-pr-21.dev.beta.nhschoices.net)


Run tests in a matrix of python versions and system architectures

Suggested enhancement: Automated tests could be run in a matrix for different architectures and python versions:

system architectures: x86_64, aarch64
python versions, e.g., cp37 through to cp311

Tooling, possible solutions:

test runtime on github ci:

Using the matrix feature of github actions to define a matrix of architectures and python versions
Using quemu emulation for aarch64 using https://github.com/uraimo/run-on-arch-action
The tests could be started directly by invoking python unittest, or indirectly via tox with the skip_missing_interpreters option.

test runtime for local testing:

GNOME Builder can run cross platform builds using quemu
Tox with the skip_missing_interpreters option

Not sure if we need this. And the ci is already quite complex... I think we could just leave the ci tests as is.

A matrix of python versions will be useful and easy to setup. I never worked on this issue because of the arm request.

hm ok, I guess we could ignore ARM for now.

I'd opt for closing this issue.

fine with me


Avoid race condition when handling timer timeouts

When using timeouts:
e.g.: response.timeoutAfter(std::chrono::milliseconds(100));
we get sometimes timer already armed error followed by a SEGV+core dump (running run_http_server)
The problem is apparently due to a race condition between the time the timerfd is closed, and the time it is erased from the timers map.
The timerfd is first closed, and then erased from the map,
If we have the following sequence a problem can happen (it happens almost every time in my tests when load gets a bit high)
e.g.:
thread 1 close(timerfd) (http.h:) around line 210
thread 2 void arm(Duration duration) { (http.h)
Async::Promise<uint64_t> p([=](Async::Deferred<uint64_t> deferred) {
timerFd = TRY_RET(timerfd_create(CLOCK_MONOTONIC, TFD_NONBLOCK));
it reuses the closed the timerfd
thread 1: timers.erase(it) (transport.cc line 85)
We should actually close the timerfd only after doing timers.erase(it)

@ywahl
I just discovered this awesome lib recently and I have run into a question regarding timers. how do you externally fill a request that already has returned but has a timer running?
I'm making another curl request from the request handler and since the curl request blocks the active thread the timeout will never occur. any ideas for a fix?

This PR is stale and has merge conflicts.  I'm going to close it for now.  If you would still like this change merged, please update this PR and re-open it.


Work on a consistent method for validation of fields with limited values

Things such as the Algorithm field in SpdxChecksumV2, are supposed to have a value from a limited set

( "SHA256", "SHA1", "SHA384", "MD2", "MD4", "SHA512", "MD6", "MD5", "SHA224" )

So how do we handle when reading a file that has a typo or otherwise unrecognized value?  Currently SpdxChecksumV2 will error out which kills the entire file read, preventing correction except by editing of the text file which isn't great.  So that implies a validation method being called later so that the user can more easily find and fix things. But should we error out when a user makes a mistake creating an object in Julia?  That implies calling the validation within the constructor.
Much to think about.

That feeds into the question of how to validate other aspects of the SPDX document, such as whether all required fields are present.  Should that even be a function of this package?


HHH-9836: enhance extensibility of MultipleHiLoPerTableGenerator

maxLo, hiloOptimizer, returnClass and keySize should be protected to allow access in custom implementations.

MultipleHiLoPerTableGenerator is deprecated in 5.0; also, now that 5.0.0.Final is out, we are no longer making improvements to 4.3


Concurrency optimization for native graph loading

Description
Fixes https://github.com/opensearch-project/k-NN/issues/2265
Refactors the graph load into a 2 step approach detailed here - https://github.com/opensearch-project/k-NN/issues/2265#issuecomment-2518306522
This will help to move out the opening of indexInput file outside of the synchronized block so that the graphfile can be downloaded in parallel even if the graph load and createIndexAllocation are inside synchronized block.
Related Issues
Resolves #2265

Check List

[ ] New functionality includes testing.
[ ] New functionality has been documented.
[ ] API changes companion pull request created.
[ ] Commits are signed per the DCO using --signoff.
[ ] Public documentation issue/PR created.

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

Please add an entry in the changelog.

HI @Gankris96, thank you for the PR.
I see this clearly will bring benefit for the cases where multiple threads are competing each other.
But just curious, after this fix, how much performance gain do you see?

HI @Gankris96, thank you for the PR. I see this clearly will bring benefit for the cases where multiple threads are competing each other. But just curious, after this fix, how much performance gain do you see?

Hi @0ctopus13prime  - yes i am working on getting the benchmarking numbers. Primarily trying to test it on remote store backed index to see the performance gains.

@Gankris96 please fix the failing CIs.


Why isn't the player also embedded in the explorer?

What is this discussion about? (required)
The fact that there are two separate web properties to maintain, when it could be just one.

media.livepeer.org - which shows content being broadcast
explorer.livepeer.org - which shows what's going on with the protocol

The distinction between the two kinda implies that broadcasting isn't really anything to do with the protocol, which feels a bit narrow-minded.
What do you hope to learn by the end of this discussion? (required)
Whether it's a good idea to embed the player into the protocol explorer, and if so, what are the steps required to do it.
Additional context
So, of you take a look at this webpage, and connect MetaMask to Rinkeby, it shows:
a) Broadcast Funds
b) Broadcast History
I think we're missing an opportunity to also show the livestream content associated with any of these streams if they are streaming right now.
It could be a really great way to get more traffic going through the explorer, and also a way to use something like www.livepeer.tv to connect viewers in with the protocol.

@chrishobcroft interesting idea.
The livepeer.tv player is a basically a bare-bones example decentralized video application that folks can clone and whitelabel easily. Its purpose is more as an example devs can use as a starting point and  as a dApp anyone can easily deploy to get a shareable link, if they bold enough to try to broadcast in today's world.
The explorer is really about delegation and pretty much serves a totally separate purpose. The task flows are completely unrelated to anything that happens in the player. I'm not really into merging them since I don't see any clear benefit from doing so, and even if we did, it's a pretty big development task.
That being said, it might still be worthwhile to think about ways to crosslink these two apps. If we just want more traffic to flow between them, that should suffice 👍
Perhaps, in the future, when broadcasting can be easily done from a web browser, we can think about a single "Livepeer dApp" that is a bit broader in its scope! :)

Echoing Josiah's comments above, the explorer is definitely built and iterated upon to be a protocol explorer - information and actions related to the protocol. And the player hosted at media.livepeer.org is built and iterated upon for displaying media - as an example DApp. While I encourage anyone to fork either, or build a DApp that combines features from protocol interactions with media use cases, each of these tools should stay separate in this context. The explorer should not turn into a portal for every sort of media experience that someone could dream up on top of Livepeer. Closing the issue for bookeeping, but feel free to continue discussing in the comments.


Arrow key bindings no longer working

I'm using the latest nightly release (   0.5.2038) and the up, down, left and right arrow keys no longer move the cursor in normal or insert or visual or list mode. I've managed to remap them with 'noremap' for normal mode using the 'experimental.viml' option, but I don't know how to fix it for insert or other modes.
The hjlk keys do work, but I don't use them as I have a non-US keyboard layout.

I think this fix https://github.com/onivim/oni2/pull/3414, may also work here. It applies a stricter restriction on the newly added bindings, which includes both an up and down binding.
Locally, on Mac at least, I can see left/right working fine, its just up/down that don't work. So there may be an additional bug that is causing the left/right issue for you.

I think this fix #3414, may also work here. It applies a stricter restriction on the newly added bindings, which includes both an up and down binding.

Yep, exactly 👍
This should be fixed now with #3414 (and in the latest nightlies). I'll close this out as fixed by #3414 , but let us know if you still see issues on the latest -

I'm on 0.5.2048 and this appears to be working now (once I remove my attempts at custom keybindings)


Troubleshooting notes

Notes for users encountering problems with the proxy playground and how to deal with expected behaviour in API calls.

/lgtm


i18n(es): translate using-components

Description

What does this PR change? Give us a brief description.
Translates using-components with spanish

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

es
components/using-components.mdx
Localization added, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


feat: probot stats improvement

Since /probot/stats built-in endpoint is being disabled in probot@v10, we need to use gr2m/app-stats-action to generate the response and serve it under the same path in order for our stats to stay up-to-date on https://probot.github.io.
We're number 1 by far though 😉 .
The json format is
{
  "installations": 0,
  "popular": []
}

Completed in pull-app/stats


Create rake file for users, assignments, groups, and rubric

Distributed the seeds file into four different files users.rake, assignments.rake, groups.rake, and rubric.rake.

@dannyreis Sorry, noticed one more thing.


[WIP][SPARK-15472][SQL] Add support for writing in csv, json, text formats in Structured Streaming

What changes were proposed in this pull request?
This patch adds support for writing in csv, json, text formats in Structured Streaming:
1. at a high level, this patch forms the following hierarchy(text as an example):
                <OutputWriter>
                      ↑
             TextOutputWriterBase
                 ↗          ↖
BatchTextOutputWriter   StreamingTextOutputWriter

                    <OutputWriterFactory>
                        ↗          ↖
BatchTextOutputWriterFactory   StreamingOutputWriterFactory
                                              ↑
                              StreamingTextOutputWriterFactory

The StreamingTextOutputWriter and other 'streaming' output writers would write data without using an OutputCommitter. This was the same approach taken by SPARK-14716.
2. to support compression, this patch attaches an extension to the path assigned by FileStreamSink, which is slightly different from SPARK-14716. For example, if we are writing out using the gzip compression and FileStreamSink assigns path ${uuid} to a text writer, then in the end the file written out will be ${uuid}.txt.gz -- so that when we read the file back, we'll correctly interpret it as gzip compressed.
How was this patch tested?
FileStreamSinkSuite is expanded much more to cover the added csv, json, text formats:
test(" csv - unpartitioned data - codecs: none/gzip")
test("json - unpartitioned data - codecs: none/gzip")
test("text - unpartitioned data - codecs: none/gzip")

test(" csv - partitioned data - codecs: none/gzip")
test("json - partitioned data - codecs: none/gzip")
test("text - partitioned data - codecs: none/gzip")

test(" csv - unpartitioned writing and batch reading - codecs: none/gzip")
test("json - unpartitioned writing and batch reading - codecs: none/gzip")
test("text - unpartitioned writing and batch reading - codecs: none/gzip")

test(" csv - partitioned writing and batch reading - codecs: none/gzip")
test("json - partitioned writing and batch reading - codecs: none/gzip")
test("text - partitioned writing and batch reading - codecs: none/gzip")

Test build #60008 has started for PR 13518 at commit 2035b59.

Test build #60008 has finished for PR 13518 at commit 2035b59.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test FAILed.

Test build #60009 has started for PR 13518 at commit 4737361.

Test build #60009 has finished for PR 13518 at commit 4737361.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Jenkins retest this please

Test build #60021 has started for PR 13518 at commit 4737361.

Test build #60021 has finished for PR 13518 at commit 4737361.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #60031 has started for PR 13518 at commit 90d02c4.

Test build #60033 has started for PR 13518 at commit 43b68d4.

Test build #60031 has finished for PR 13518 at commit 90d02c4.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #60033 has finished for PR 13518 at commit 43b68d4.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test FAILed.

Test build #60039 has started for PR 13518 at commit 56dbb9b.

Test build #60039 has finished for PR 13518 at commit 56dbb9b.

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

Merged build finished. Test PASSed.

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

Test build #60041 has started for PR 13518 at commit 91e51ae.

Test build #60041 has finished for PR 13518 at commit 91e51ae.

This patch fails executing the dev/run-tests script.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #60043 has started for PR 13518 at commit eb2090c.

Test build #60043 has finished for PR 13518 at commit eb2090c.

This patch fails executing the dev/run-tests script.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Jenkins retest this please

Test build #60101 has started for PR 13518 at commit 1e9af1c.

Test build #60101 has finished for PR 13518 at commit 1e9af1c.

This patch fails executing the dev/run-tests script.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #60102 has started for PR 13518 at commit 7fca579.

Test build #60102 has finished for PR 13518 at commit 7fca579.

This patch fails executing the dev/run-tests script.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test FAILed.

Test build #60103 has started for PR 13518 at commit 2ead307.

Test build #60103 has finished for PR 13518 at commit 2ead307.

This patch fails executing the dev/run-tests script.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #60104 has started for PR 13518 at commit b64afc6.

Test build #60104 has finished for PR 13518 at commit b64afc6.

This patch fails executing the dev/run-tests script.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #60108 has started for PR 13518 at commit 2c52c2c.

Test build #60108 has finished for PR 13518 at commit 2c52c2c.

This patch fails executing the dev/run-tests script.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test FAILed.

Test build #60113 has started for PR 13518 at commit aa61f1d.

Test build #60113 has finished for PR 13518 at commit aa61f1d.

This patch fails executing the dev/run-tests script.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #60114 has started for PR 13518 at commit c5ac63e.

Test build #60114 has finished for PR 13518 at commit c5ac63e.

This patch fails executing the dev/run-tests script.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #60115 has started for PR 13518 at commit cc84273.

Test build #60115 has finished for PR 13518 at commit cc84273.

This patch fails executing the dev/run-tests script.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Jenkins retest this please

Test build #60217 has started for PR 13518 at commit fc0fb51.

Test build #60218 has started for PR 13518 at commit 345fdba.

Test build #60217 has finished for PR 13518 at commit fc0fb51.

This patch fails executing the dev/run-tests script.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #60218 has finished for PR 13518 at commit 345fdba.

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

Merged build finished. Test PASSed.

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

Jenkins retest this please

Test build #60219 has started for PR 13518 at commit bc28f41.

Test build #60219 has finished for PR 13518 at commit bc28f41.

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

Merged build finished. Test PASSed.

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

Jenkins retest this please

Test build #60638 has started for PR 13518 at commit ec51f98.

Test build #60638 has finished for PR 13518 at commit ec51f98.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Jenkins retest this please

Test build #60640 has started for PR 13518 at commit ec51f98.

Test build #60640 has finished for PR 13518 at commit ec51f98.

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

Merged build finished. Test PASSed.

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


Fix bug where caplog handlers were removed by clean_reset fixture

Description
Fix issue where the caplog handlers were removed by the clean_reset fixture.
Self Check:

[ ] Attached issue to pull request
[x] Changelog entry
[x] Type annotations are present
[x] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation
[ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)

Processing this pull request

Pull request rejected by merge tool. The tests for this branch did not succeed.

Processing this pull request

Pull request rejected by merge tool. The tests for this branch did not succeed.

Processing this pull request

Merged into branches master in 5166f236c8eb4188ecd920654a2684c77348ef6f

Processing #7661.


Add vhost creation test

In preparation for some other work, this adds a test for config generation for http vhost generation. In a newly cloned copy of the repo, the patch applies cleanly and the test succeeds.

Wonderful, thanks!


Incorrect generation of control dependences when the block terminator is an unreachable LLVM IR instruction

The LLVM unreachable instructions should not be handled differently, since that may lead to incorrect post-dominance frontier calculation, and therefore an incorrect control dependence graph (CDG).
For example
#include <stdlib.h>
#include <stdio.h>

#define N 5

void foo() {
  int i;
  for (i = 0; i < N; i++) {}
  return;
}

void bar() {
  int i;
  for (i = 0; i < N; i++) {}
  exit(0);
}

The corresponding IR can be produced with clang -emit-llvm -S foo.c -o foo.ll.
The CDG's for both for and bar functions should be identical, but they are not since the bar CDG is empty.
The 2 CFG's only differ by a single unreachable basic block, as can be seen below:
cfg.bar.pdf
cfg.foo.pdf
This issue was triggered by the use case described in 1.

This bug was missed because the analysis was applied at bitcode which was obtained with O1 or higher optimization level. This means the unreachable block elimination pass is run which hides this issue.
Running  opt -unreachableblockelim foo.ll -o foo-elim.ll should fix this case.

The core issue seems to be the different handling of unreachable instructions, for no apparent reason.


Avoid split packages for testutil- modules

For example, testutil-server module has server.entity package.
This is going to hurt under Java 9.

We can have a testing package under server, and move current split packages there.

@armiol, to the subject of changing packages.


range will not reset itself, it will adapter user's selecting operation

… by NestedScrollView
when CalendarPickerView was contained by NestedScorllView, it can only show its first child, this is one candidate solution.

when we select dates in range mode, it is normal that we modify our selection from date to date. it's a better experience that the selected range adapt the user's change rather than reset itself.

when selected date's distance to start and end is equal, set the selected date as new range's end rather than start. i think this is a better experience than set the selected date as the new range's end.

solve that when we click a date before former start date, the new start date remains unselected.
if we click the date of the border date, start or end, the other edge's date will be called with unselected, but the current one will not be called with unselected. this may not be the same performance as before, i think i will consider to restore the former performance if someone complains about this.

Hey there, can you create another pull request from a branch, so I can try the code before merging it?

@savvisingh ok


Error while running the pipeline: No hosted parallelism has been purchased or granted.

When starting the pipeline with the standard ASP.NET Core template, the execution fails with the following error:
##[error]No hosted parallelism has been purchased or granted. To request a free parallelism grant, please fill out the following form https://aka.ms/azpipelines-parallelism-request
Pool: Azure Pipelines
Image: ubuntu-latest
Started: Today at 16:51
Duration: 3m 49s

Job preparation parameters
ContinueOnError: False
TimeoutInMinutes: 60
CancelTimeoutInMinutes: 5
Expand:
  MaxConcurrency: 0
  ########## System Pipeline Decorator(s) ##########

  Begin evaluating template 'system-pre-steps.yml'
Evaluating: eq('true', variables['system.debugContext'])
Expanded: eq('true', Null)
Result: False
Evaluating: resources['repositories']['self']
Expanded: Object
Result: True
Evaluating: not(containsValue(job['steps']['*']['task']['id'], '6d15af64-176c-496d-b583-fd2ae21d4df4'))
Expanded: not(containsValue(Object, '6d15af64-176c-496d-b583-fd2ae21d4df4'))
Result: True
Evaluating: resources['repositories']['self']['checkoutOptions']
Result: Object
Finished evaluating template 'system-pre-steps.yml'
********************************************************************************
Template and static variable resolution complete. Final runtime YAML document:
steps:
- task: 6d15af64-176c-496d-b583-fd2ae21d4df4@1
  inputs:
    repository: self

  MaxConcurrency: 0

Does anyone have an idea how I can get this to work?

Hello @MarioAugustin ,
Microsoft has changed the policy for the free tier of newly created organisations. You need to register in order for Your DevOps organisation to be approved for the parallelism. The link is included in the first line of the error message.

Oh, my bad, I didn't recognize that part of the error message. Thank you for the help!


Vulkan bools should maybe not map to Rust bool

Rust supposes that bools always contain either 0 or 1. A GPU might not write the value 1 when you write true, although this needs to be checked from the specs.

From a quick check of the current spec version, I believe we can be confident in Bool32 values being the same as Rust bool values:
VK_TRUE represents a boolean True (integer 1) value, and VK_FALSE a boolean False (integer 0) value.

All values returned from a Vulkan implementation in a VkBool32 will be either VK_TRUE or VK_FALSE.

Applications must not pass any other values than VK_TRUE or VK_FALSE into a Vulkan implementation where a VkBool32 is expected.
```

That's not the same as a bool on the GPU though. I think there's another section that talks about data types on the GPU.

Based on #1331, the shader compiler never generates code with OpTypeBool in descriptor set bindings anyway. The type can be used in specialization constants, but Vulkano-shaders has extra code to handle it there.


The problem of comments disappearing when saving when modifying tables in DM database.

Description
I am using a DM database, and when I create a table, the comments on the columns in the table are normal. However, when I modify the comments on the columns in the table and save them, there is no new comment code in the SQL. Do any experts have any suggestions? thank you！
DBeaver Version
24.1.5
Operating System
Windowns 11
Database and driver
Dameng JDBC driver 18RELEASE
Steps to reproduce

Connect to the DM database
Find a table with annotations in the columns.
Modify the comments on the columns in the table.
Click to save
There is no new comment code in the SQL pop-up box.

Additional context
win 11环境

duplicate of https://github.com/dbeaver/dbeaver/issues/34641

Thank you for bug report.
I'm closing it as it's a duplicate of #34641


persist ip forwarding settings across reboots

Currently the GCP nat gateway settings do not persist across reboots, this PR fixes it.
More info can be found here: https://cloud.google.com/vpc/docs/special-configurations#natgateway

Hi,
Thanks for the pull request. We no longer provide terraforming.


When the user holds their phone horizontally, toolbar should go vertical and on the right (or left ?)

Currently: the buttons are always on top of the page regardless of the phone's orientation (horizontal / vertical).
Instead we want:
horizontal   =>   vertical toolbar buttons on the right (or left; we need to decide what is more ergonomic)
vertical => what we currently have: horizontal tool bar at the top of the page.
Can we do this in BSS using CSS Media Queries some how?
Reason:
When the user holds their phone screen horizontal, there isn't much vertical space left to draw diagrams in.

Example media query docs


configuration-service: git pull first

Is your feature request related to a problem? Please describe.
Manual commits to a Git repo managed by Keptn can break the configuration-service. This happens even if the changes have been reverted (by that I mean the files end up identical but the commit IDs known to Keptn and what's on GitHub will be different).
Describe the solution you'd like
Keptn configuration-service could do a git pull first before pushing.
Working Example of Issue
keptn create project demo \
--shipyard=shipyard.yaml
--git-user=whoever \
--git-remote-url=wherever \
--git-token=whatever

Manually change the shipyard.yaml on GitHub. For example, adding a stage.
Manually remove the change to shipyard.yaml on GitHub.
Describe alternatives you've considered
Clearer documentation on what manual changes are allowed on GitHub (eg. direct changes to sli.yaml or slo.yaml files are OK but changes to files A, B, C and X have the potential to cause Keptn errors). Or a blanket statement: Any file modifications must be done via keptn add-resource commands so that Keptn knows about new commit IDs.

Actually, there is already a git pull happening before any changes are applied on the git repository.
Could you please provide more information, what exactly isn't working anymore? Do you have any logs etc...?

I cannot recreate this now on 0.9.2 even adding a new stage to the shipyard, which used to cause this issue, no longer does.
Of course, the new stage won't show in the bridge but at least nothing breaks.
We can close this.


volcano plot with fixed ylim (scales) cannot be "freed up" with scales="free"

Hoi Witold,
As you may have seen in the comments, one user SH realized that the volcanos are by default fixed on ylim.
Relaxing this with the scales parameter does not work .
-> in all these volcanos, the y-axis always has the same fixed length.
pl$volcano(scales = c("fixed"))
pl$volcano_plotly(scales = "free")
pl$volcano(scales = "free")
pl$volcano(scales = "free_y")
Gruess & bis am Dienstag
j

@jjGG
I did run the examples in the prolfqua package ContrastsPlotter documentation:
cp$volcano(scales = "fixed")

cp$volcano(scales = "free")

Please try to reproduce an possible error using any of the example datasets provided with prolfqua.

@jjGG
I did limit the p.values to a minimum of 0.0001 ...
Now, there is a parameter minscorein the volcano function, which you can set to whatever you want.

@wolski  - super cool. Thanks for tghe fix!

Hei Witold,
Leider funktioniert bei mir (prolfqua 1.1.5) der minscore parameter nicht. Eine Idee?
v3 <- plotter$volcano(minscore=c(1E-10))
Error in plotter$volcano(minscore = c(1e-10)) :
  unused argument (minscore = c(1e-10))

Super - Danke Witold.
Hat funktioniert. RTFM!
minscore =/ min_score


bla1

some stuff

[ ] Check that no weird commits “slipped” into the merge due to human error

another

[x] bla?
[ ] Go over briefly on the commits and make sure they are aligned with what you are planning to merge into master.
[x] blo!

The Checklist :see_no_evil: :hear_no_evil: :speak_no_evil:
Go over briefly on the commits and make sure they are aligned with what you are planning to merge into master.
Check that no weird commits “slipped” into the merge due to human error
Go over briefly on the “File Changed” and make sure the files are aligned with what you expect
In a one-liner hotfix, you shouldn’t see other files besides the one modified
Ensure that “All checks have passed”, that should include:

[ ] build
[ ] Unit tests
[ ] Automated tests

In case the version includes a new service:
Validate with the devops team that the new service is configured in preprod and prod environments (terraform, helm chart).
In case this is a “big deploy” merge (from develop / from preprod):
Go over “Next Deploy” report to see that all the deploy blockers have been marked as “Done” as needed
Validate the deploy to preprod with the same changes have been made and sanity tests have been performed
In case this is a “hotfix” merge:
Validate there is a PR merged in “develop” with the same changes
Validate the change was properly tested in “app-test”
The code was reviewed and approved

The Checklist :see_no_evil: :hear_no_evil: :speak_no_evil:
Type of the change:

[ ] :fire: Hotfix
[ ] :rocket: "Big Deploy" (from develop / from preprod)
[ ] :warning: New service

The basics:

[ ] Review the commits and make sure they are aligned with what you are planning to merge.

[ ] Check that no weird commits “slipped” into the merge due to human error.

[ ] Go over briefly on the “File Changed” and make sure the files are aligned with what you expect

[ ] Ensure that “All checks have passed”, that should include:

Build
Unit tests
Automated tests

In case the version includes a new service:

[ ] Validate with the devops team that the new service is configured in preprod and prod environments (terraform, helm chart).

In case this is a “big deploy” merge (from develop / from preprod):
Go over “Next Deploy” report to see that all the deploy blockers have been marked as “Done” as needed
Validate the deploy to preprod with the same changes have been made and sanity tests have been performed
In case this is a “hotfix” merge:
Validate there is a PR merged in “develop” with the same changes
Validate the change was properly tested in “app-test”
The code was reviewed and approved


Empty objects should be validated as None for optional fields

Checks

[X] I added a descriptive title to this issue
[X] I have searched (google, github) for similar issues and couldn't find anything
[X] I have read and followed the docs and still think this is a bug

Bug
Output of python -c "import pydantic.utils; print(pydantic.utils.version_info())":
             pydantic version: 1.8.2
            pydantic compiled: True
                 install path: /home/aaron/Dev/Python/twistbot/.venv/lib/python3.9/site-packages/pydantic
               python version: 3.9.0 (default, Aug  2 2021, 23:21:12)  [GCC 11.2.1 20210728 (Red Hat 11.2.1-1)]
                     platform: Linux-5.14.9-200.fc34.x86_64-x86_64-with-glibc2.33
     optional deps. installed: ['devtools', 'dotenv', 'email-validator', 'typing-extensions']

(i'm not sure if is actually bug, maybe is a Feature Request )
when we pass an empty dict (and list too?) for an Optional field,  it's should be handle as None if not all of this field fields are optional.
lets say,
if some field raises ValidationError, we should try handle it as None, at last when is an empty object (list or dict)
from typing import Optional, Dict
from pydantic import BaseModel

class Data(BaseModel):
    some: Dict

class EmptyDictTest(BaseModel):
    data: Optional[Data] = None

EmptyDictTest.parse_obj({"data": {}})

pydantic.error_wrappers.ValidationError: 1 validation error for EmptyDictTest
data -> some
  field required (type=value_error.missing)

This can't become the default. The workaround is easy in V1 and easier in V2:
from typing import Annotated, Any, Dict, Optional, TypeVar

from pydantic import BaseModel
from pydantic.annotated_arguments import BeforeValidator

class Data(BaseModel):
    some: Dict[Any, Any]

T = TypeVar('T')

def falsy_to_none(x: Any) -> Any:
    return x or None

LeniantOptional = Annotated[Optional[T], BeforeValidator(falsy_to_none)]

class EmptyDictTest(BaseModel):
    data: LeniantOptional[Data] = None

assert EmptyDictTest.parse_obj({'data': {}}).data is None

Using pydantic 2.7.1, I wasn't able to find pydantic.annotated_arguments import
So here is another solution using field_validator
#!/usr/bin/env python3
# Python imports
from typing import Optional
# Packages imports
from pydantic import BaseModel, field_validator

class B(BaseModel):
    var3: str
    var4: str

class A(BaseModel):
    var1: int
    var2: Optional[B] = None

    @field_validator('var2', mode='before')
    def check_empty(cls, value):
        return value or None

if __name__ == "__main__":
    data = {
        "var1": 1,
        "var2": {}
    }
    result = A.model_validate(data)
    print(result)

Just import it straight from pydantic:
from typing import Annotated, Any, Dict, Optional, TypeVar

from pydantic import BaseModel
from pydantic import BeforeValidator

class Data(BaseModel):
    some: Dict[Any, Any]

T = TypeVar('T')

def falsy_to_none(x: Any) -> Any:
    return x or None

LeniantOptional = Annotated[Optional[T], BeforeValidator(falsy_to_none)]

class EmptyDictTest(BaseModel):
    data: LeniantOptional[Data] = None

assert EmptyDictTest.parse_obj({'data': {}}).data is None


Add missing reference to pageContainer.tsx

The walk through misses the reference to memberFormValidation in pageContainer.tsx.

Thank you


Given parent class emacsql-sqlite-connection is not a class

hi  @abougouffa
when first open magit
here is the log
Turning on magit-auto-revert-mode...done
Given parent class emacsql-sqlite-connection is not a class

See #49
You can run M-x minemacs-update to fix it.

emacs 29.0.92
I deleted the previous .emacs.d and re-cloned to ensure a clean environment
When all packages are installed and compiled
run minemacs-update
then space g g
still have this problem


Fix EOS token in multilingual_denoising

Fixes https://github.com/pytorch/fairseq/issues/1785, where in multilingual_denoising the generic eos token is used instead of the langid token.
Specifically, the problem is that the collater in the denoising_dataset uses the generic self.vocab.eos() instead of self.eos, which in the case of multilingual_denoising is set to the language id of a given language.
See https://github.com/pytorch/fairseq/issues/1785#issuecomment-626171602 for an example of the issue.

I realized that even this won't work, because each batch is a mixture of many languages, and the way that denoising_dataset works, it uses the same eos_idx for all samples in the batch.
> print(list("".join([self.task.dictionary.symbols[t] for t in s]) for s in sample['net_input']['prev_output_tokens'][:5].tolist()))

['[de]<s>▁Das▁ist▁phänomenal,▁da▁kann▁man▁sich▁schon▁ausmalen,▁was▁in▁Leipzig▁los▁ist,▁wenn▁wir▁Erstliga-Fußball▁anbieten.</s>',
 '[de]<s>▁Offering▁something▁for▁everyone,▁the▁hemlines▁varied▁from▁just▁above▁booties▁to▁tapered▁at▁the▁ankle▁or▁flowing.</s>',
 '[de]<s>▁Construction▁will▁start▁in▁the▁second▁quarter▁of▁this▁year▁and▁the▁first▁windmills▁from▁Vestas▁will▁be▁delivered▁and▁installed▁in▁2018.</s>',
 '[de]<s>▁You\'ve▁probably▁heard▁the▁term▁"glycemic▁index"▁(GI)▁touted▁on▁more▁than▁a▁few▁diet▁commercials.</s>',
 '[de]<s>▁The▁retired▁footballer,▁whose▁been▁pictured▁enjoying▁quality▁time▁shopping▁with▁his▁brood▁in▁London▁earlier▁this▁week,▁was▁praised▁by▁London▁Ambulance▁Service.</s>']

So the problem was in merge inside the collate function. It uses a single eos_idx which when move_eos_to_beginning=True and the --add-lang-token flag is used in the multilingual_denoising task, makes all the samples in a batch have the same langid token in the target sequence. This is problematic because each batch might contain a mixture of many languages.
I changed data_utils.collate_tokens to set dst[0] = src[-1] when eos_idx=None and move_eos_to_beginning=True and passed eos_idx=None to it. When not using --add-lang-token in multilingual_denoising, the shared eos token will be used, which is set here.


Elasticsearch cluster cannot find the master node in the docker swarm using docker stack deploy

Hi all I have tried this for ES cluster in docker swarm , https://github.com/deviantony/docker-elk/wiki/Elasticsearch-cluster
but i cannot get Elastic cluster in docker swarm.
docker-compose.yml
version: '3.3'
services:
elasticsearch:
image: docker.elastic.co/elasticsearch/elasticsearch:7.8.0
ports:
- "9200"
- "9300"
volumes:
- elasticsearch1-data:/usr/share/elasticsearch/data
environment:
- "node.name:elk_elasticsearch.{{.Task.Slot}}"
- "discovery.seed_hosts:tasks.elasticsearch"
- "cluster.initial_master_nodes:elk_elasticsearch.1,elk_elasticsearch.2,elk_elasticsearch.3"
- "discovery.zen.ping.unicast.hosts=tasks.elasticsearch"
- "ES_JAVA_OPTS=-Xms512m -Xmx512m"
- "cluster.name=docker-cluster"
- "bootstrap.memory_lock=true"
- "node.max_local_storage_nodes:'3'"
- "discovery.type: ''"
networks:
- elasticsearch_distributed
deploy:
mode: replicated
replicas: 1
restart_policy:
delay: 30s
max_attempts: 10
window: 120s
volumes:
elasticsearch1-data:
networks:
elasticsearch_distributed:
driver: overlay
Inside the log in a container , i have found
{"type": "server", "timestamp": "2020-07-27T12:03:59,936Z", "level": "WARN", "component": "o.e.c.c.ClusterFormationFailureHelper", "cluster.name": "docker-cluster", "node.name": "57246b31c6ee", "message": "master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and [cluster.initial_master_nodes] is empty on this node: have discovered [{57246b31c6ee}{X5_mB1FiR7C5_Wjz89G3BQ}{Fvypf8HeR5y5qihELLcOBA}{<IP_ADDRESS>}{<IP_ADDRESS>:9300}{dilmrt}{ml.machine_memory=16656715776, xpack.installed=true, transform.node=true, ml.max_open_jobs=20}]; discovery will continue using [<IP_ADDRESS>:9300] from hosts providers and [{57246b31c6ee}{X5_mB1FiR7C5_Wjz89G3BQ}{Fvypf8HeR5y5qihELLcOBA}{<IP_ADDRESS>}{<IP_ADDRESS>:9300}{dilmrt}{ml.machine_memory=16656715776, xpack.installed=true, transform.node=true, ml.max_open_jobs=20}] from last-known cluster state; node term 0, last-accepted version 0 in term 0" }
Can anyone help me resolve this ?
Thanks

The format of your environment variables looks strange, with a mix of quotes, colons and equal signs.
Could you please try using this exact format without any other modification? (just for now, you can tweak later)
  elasticsearch:
    environment:
      node.name: elk_elasticsearch.{{.Task.Slot}}
      discovery.type: ''
      discovery.seed_hosts: tasks.elasticsearch
      cluster.initial_master_nodes: elk_elasticsearch.1,elk_elasticsearch.2,elk_elasticsearch.3

Now its fine !
version: '3.3'
services:
elasticsearch:
image: docker.elastic.co/elasticsearch/elasticsearch:7.8.0
ports:
- "9200"
- "9300"
volumes:
- elasticsearch1-data:/usr/share/elasticsearch/data
environment:
- node.name:elk_elasticsearch.{{.Task.Slot}}
- discovery.seed_hosts:tasks.elasticsearch
- cluster.initial_master_nodes:elk_elasticsearch.1,elk_elasticsearch.2,elk_elasticsearch.3
- discovery.zen.ping.unicast.hosts=tasks.elasticsearch
- ES_JAVA_OPTS=-Xms512m -Xmx512m
- bootstrap.memory_lock=true
- node.max_local_storage_nodes:'3'
- discovery.type:''
networks:
  - elasticsearch_distributed
deploy:
  mode: replicated
  replicas: 1
  restart_policy:
    delay: 30s
    max_attempts: 10
    window: 120s

volumes:
elasticsearch1-data:
networks:
elasticsearch_distributed:
driver: overlay


NPM start

I'm submitting a ...

[ ] bug report
[x] feature request

Feature Request:
Use npm start to proxy npm run dev

hi, thanks for your issue. This feature was added in 339f7ca1cccd1ce10ddf9c7a044bdd5b72eac890.

Maybe move to yarn?
Thanks for the most awesome react starter kit ever (semantics :)) :)


[Emulator] Getting forbidden error in emulator when it gets triggered

Describe the bug
I am running a local emulator for SignalR and whenever the emulator is triggered it throws following error:
fail: Microsoft.Azure.SignalR.Emulator.HubEmulator.HttpServerlessMessageHandler[0]
      The response for {hub}=signalrhub,{event}=connected,{category}=connections is unexpected: Forbidden.

To Reproduce

Start the emulator
Start the Azure Function app locally that contains SignalR triggers
Start the web app that will negotiate with the locally running SignalR instance (emulator's connection string)

Follow the prompts on the web app

This does a successful negotiation and then invoked OnConnected - which throws the error described above.

Exceptions (if any)
fail: Microsoft.Azure.SignalR.Emulator.HubEmulator.HttpServerlessMessageHandler[0]
      The response for {hub}=signalrhub,{event}=connected,{category}=connections is unexpected: Forbidden.

I am using the default Upstream settings as:
{
  "UpstreamSettings": {
    "Templates": [
      {
        "UrlTemplate": "http://localhost:7071/runtime/webhooks/signalr",
        "EventPattern": "*",
        "HubPattern": "*",
        "CategoryPattern": "*"
      }
    ]
  }
}

Forbidden means your local azure function returns 403 Forbidden, do you see any trace in your azure function side?

Hi @vicancy ! I have the same issue. No trace in my function. I am using version '1.1.0' of Microsoft.Azure.SignalR.Emulator.

Oh.. just saw I have a different error:
fail: Microsoft.Azure.SignalR.Emulator.HubEmulator.HttpServerlessMessageHandler[0]       The response for {hub}=local,{event}=disconnected,{category}=connections is unexpected: NotFound.

Please feel free to reopen the issue if there are updates


Creating a permalink is crazy slow when there are many branches

The git command that is used by the git extension API getBranches is extremely slow when there are many branches. Since getBranches is used to determine the best remote to create a permalink for, creating a permalink is now very slow.

Verified on https://github.com/9at8/vscode-pull-request-github-test-1884 (300 branches). It takes about 1-2 seconds to open the link.


Update docstrings

Docstrings for the following transforms were updated:

Quantile
Functional
EigenAnalysis / PCA / DRS / SDS
Sequential
Parallel

Codecov Report

Merging #50 (ac0214e) into master (928b8e5) will decrease coverage by 0.09%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #50      +/-   ##
==========================================
- Coverage   92.84%   92.74%   -0.10%
==========================================
  Files          19       19
  Lines         461      455       -6
==========================================
- Hits          428      422       -6
  Misses         33       33

Impacted Files
Coverage Δ

src/transforms/eigenanalysis.jl
79.62% <ø> (ø)

src/transforms/functional.jl
93.75% <ø> (ø)

src/transforms/parallel.jl
91.52% <ø> (ø)

src/transforms/quantile.jl
93.33% <ø> (-1.12%)
:arrow_down:

src/transforms/sequential.jl
92.59% <ø> (ø)

src/transforms/scale.jl
92.30% <0.00%> (-1.03%)
:arrow_down:

src/distributions.jl
90.90% <0.00%> (-0.40%)
:arrow_down:

Continue to review full report at Codecov.

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


auto update wrappers behind a flag

This restores the auto update feature introduced by #490 for v3, but behind a feature flag. mount now needs the same treatment to keep the tree in sync that shallow used to. Fixes #1175.
For what it's worth, since pre-v3 both shallow and mount essentially auto-updated by default, the only Enzyme tests that break without the flag checks are these two, which are fixable by asserting with deep equality if that's on the table.
https://github.com/airbnb/enzyme/blob/106b5d14c79a1dfc4d3ee13f87b13ffb609c5c4a/packages/enzyme-test-suite/test/ReactWrapper-spec.jsx#L3696-L3710

This PR seems to be reasonable to me.

@jwbay are you no longer interested in continuing this?


Investigate custom certificates for webconsole without interfering with wildcard apps domain

We need to verify that a custom certificate for the console can be applied to a cluster without attempting to replace or disrupt the *.apps.mydomain.com certificates.
Use passthrough on the pod itself to terminate SSL.

/assign

Currently this is not possible but will be a feature in 4.5.
Custom URL

https://issues.redhat.com/browse/CONSOLE-2036
Then down the road there is a request to customize more cluster components.  This is still an RFE and hopefully will be implemented down the road:
Custom Route Name and Certificates for all OCP Cluster Components

https://issues.redhat.com/browse/RFE-718


fix: 修复笔误

Types of changes

[ ] New feature
[ ] Bug fix
[ ] Documentation change
[x] Coding style change
[ ] Refactoring
[ ] Performance improvement
[ ] Test cases
[ ] Continuous integration
[ ] Typescript definition change
[ ] Breaking change

Background and context
修复笔误，变化为baseConig修改为baseConfig
Solution

How is the change tested?

Changelog

Changelog(CN)
Changelog(EN)
Related issues

Checklist:

[ ] Provide changelog for relevant changes (e.g. bug fixes and new features) if applicable.
[ ] Changes are submitted to the appropriate branch (e.g. features should be submitted to feature branch and others should be submitted to master branch)

Other information

@dyggod 首先感谢pr。commit message 麻烦做个统一，使用英文哈。

@dyggod 首先感谢pr。commit message 麻烦做个统一，使用英文哈。
我覆盖了我的分支上原本不符合commit规范的提交。please approve~


upgrade needed

Following steps on a new ubunut 18.04 vm, the sudo "apt-get install moby-engine" failed until I had done a "sudo apt-get upgrade"

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

ID: a3b8296d-c923-e990-dcad-35ef2b908a2a
Version Independent ID: 5f85fd7b-f2b6-b3b1-6be2-b6054bb33507
Content: How to install Azure IoT Edge on Linux
Content Source: articles/iot-edge/how-to-install-iot-edge-linux.md
Service: iot-edge
GitHub Login: @kgremban
Microsoft Alias: kgremban

My bad... I missed the first steps:
Install repository configuration
curl https://packages.microsoft.com/config/ubuntu/16.04/prod.list > ./microsoft-prod.list
sudo cp ./microsoft-prod.list /etc/apt/sources.list.d/
Install Microsoft GPG public key
curl https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor > microsoft.gpg
sudo cp ./microsoft.gpg /etc/apt/trusted.gpg.d/
So in my case it's working according to the instructions above.

Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

Thanks @toddwhitehead instructions updated.
@sergaz-msft #please-close


after update settings reset

What I did: Updated audio switcher.
What happened: This reset my favorites.
What should have happened: keep favorites across updates.

It should update, and take all settings across. On the odd chance that it doesn't read settings correctly it has to create them.
I think you have stumbled across a very edge case.


Official documentation is scattered / weak / inadequate

Description
https://www.swift.org/package-manager is apparently the place where I can navigate to that documents everything about the package manager, but it's woefully incomplete; it doesn't link to https://docs.swift.org/package-manager/, which exists but only describes part of the package manager's API.  Oh, and there's https://developer.apple.com/documentation/packagedescription which also The PackagePlugin module doesn't appear to be documented anywhere except in code and some doc files in the package manager's GitHub repository.
More generally, insufficient attention has been given to a description of how the system fits together such that I can understand things like, why can I sometimes use a string to identify a dependency, and why must I sometimes use a .product? or, why does a particular thing get rebuilt? As a result, trying to use SPM ends up involving a lot of guesswork.
Expected behavior
No response
Actual behavior
No response
Steps to reproduce
No response
Swift Package Manager version/commit hash
No response
Swift & OS version (output of swift --version ; uname -a)
No response

Another example that came up in slack and is still unanswered:

Dave Abrahams
5 days ago
I'm trying to understand the role of products.  Am I correct to think that every executable or library that can actually be built directly my package is a product of that package, and that there is no distinction made for products such as build tools and their support libraries that I might not want to ship with a compiled version of the resulting application?
1 reply

compnerd
5 days ago
I'd love to fully understand this too.  AIUI, products are only the publicly visible artifacts that are produced (libraries or executable).

It's incredibly frustrating try to look up details about, for example, SwiftSetting.enableUpcomingFeature() on the supposed "reference" API page (https://docs.swift.org/package-manager/PackageDescription/PackageDescription.html) and finding absolutely nothing there.

+1, @MaxDesiatov can we move these docs into a docc archive and host them with SPI and/or swift.org? I dont think the markdown files in repro are really working for users.

cc @bnbarham for thoughts too


log can still contain clear text credential

Looks like there are still some paths exist that do not handle redaction as expected.
Using a sandbox cluster where all user credentials are randomly generated, before the cluster is ready the prometheus-exporter would show this:
level=info ts=2019-10-24T18:02:45.076664968Z caller=clusterinfo.go:200 msg="triggering initial cluster info call"
level=info ts=2019-10-24T18:02:45.07681672Z caller=clusterinfo.go:169 msg="providing consumers with updated cluster info label"
level=error ts=2019-10-24T18:02:50.077032958Z caller=clusterinfo.go:253 msg="failed to get cluster info" err="Get https://admin:t5%2AzdjfO3e%3C3&c88p%5DUO1M04%2FvNl%3E%7Dp$@elasticsearch:9200/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
level=error ts=2019-10-24T18:02:50.173526771Z caller=clusterinfo.go:174 msg="failed to retrieve cluster info from ES" err="Get https://admin:t5%2AzdjfO3e%3C3&c88p%5DUO1M04%2FvNl%3E%7Dp$@elasticsearch:9200/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
level=info ts=2019-10-24T18:02:55.076968842Z caller=main.go:153 msg="initial cluster info call timed out"
level=info ts=2019-10-24T18:02:55.274039775Z caller=main.go:188 msg="starting elasticsearch_exporter" addr=:9114

This is our kubernetes pod container definition
  containers:
  - args:
    - --es.uri=https://$(PROMETHEUS_EXPORTER_USER):$(PROMETHEUS_EXPORTER_PASS)@elasticsearch:9200
    - --es.all
    - --es.ca=/usr/share/elasticsearch/config/elk-root-ca.pem
    - --es.client-private-key=/usr/share/elasticsearch/config/elk-key.pem
    - --es.client-cert=/usr/share/elasticsearch/config/elk-crt.pem
    - --es.ssl-skip-verify
    - --web.listen-address=:9114

where the two env vars are injected from secrets.

Thanks for reporting!
it's a bit strange, as the leaked password is returned by a http.Client.Do() call error, which should be correctly redacted. See https://github.com/golang/go/blob/master/src/net/http/client.go#L594
I have a closer look what's wrong here

this is fixed in go1.13, but we're still on go1.12. See https://github.com/golang/go/issues/31808. I'll try to switch to go1.13 as fast as possible.


Wrong removal of import

TypeScript Hero incorrectly removes the following import:
import * as moment from "moment";
...
<FormGroup label={LocalizationService.formatMessage("userGeneral.createdAt", "Created At")}>
    <TextLabel>{moment(this.state.user.createdAt!).format(LocalizationService.dateTimeFormat)}</TextLabel>
</FormGroup>

As you can see, it is needed.

Happens a lot to me too

Yep, this is duplicated to #352


add test suite

Closing as new repo location is at https://github.com/facelessuser/MarkdownPreview.


Use B+ Tree iterator instead of DFS to find scheduled jobs to be executed

Hi
I would like to know if this issue has been published on a specific version? or not yet published?
I tested on version 5.16.4 and it doesn't seem to be fixed.
Thank you.

Hey @lovemai073, I just noticed this.. . I posted an answer here regarding my findings on 5.16.3 vs. 5.16.4: https://github.com/apache/activemq/pull/728

yes, I have see that.
I am also doing a test again....


Add source whitelist

We have a large number of services and sharing the secret between the services has been proven difficult. As an alternative we are using ALLOWED_SOURCES in thumbor:
ALLOWED_SOURCES: >
            [".*\.foobar\.com","my\.foobar\.com", "sendbird-ap-9\.s3\.amazonaws\.com"]

This will only accept and process images from the listed sources.
Looking at something similar in imagor.

The equivalent in form of environment variable:
HTTP_LOADER_ALLOWED_SOURCES=*.foobar.com,my.foobar.com,sendbird-ap-9.s3.amazonaws.com

from the configuration arguments
  -http-loader-allowed-sources string
        HTTP Loader allowed hosts whitelist to load images from if set. Accept csv wth glob pattern e.g. *.google.com,*.github.com.

🤦🏼 Should have put my reading glasses on 🤓 . Thanks!

🤦🏼 Should have put my reading glasses on 🤓 . Thanks!


Simplify code example using std::chrono.

It's a bit simpler and cleaner to work with std::chrono::time_point and only convert to nanoseconds at the end.

Thank you!


Allow opt-in/out of detect links feature

https://phabricator.wikimedia.org/T288570
At the moment, the plugin will use the detect links feature on all posts. However, it may be undesirable on some posts that contain a large number of Wikipedia links where the preview doesn't work (special pages).
In this case, it is better to disable Wikipedia Preview completely on a specific post.
This PR adds a checkbox on the post metadata sidebar to enable/disable Wikipedia Preview just for this post. It is enabled by default.
Also

Added some unrelated useful commands (check-engines, check-license)
Made src/index.js the single entry point for the editor side
Moved the feature toggling to js so the postmeta can be enabled but the custom format disabled

It works on the posts, but it doesn't work on page

The on/off toggle button on the sidebar is working correctly for hyperlinks for me, but I'm not able to activate the gutenberg option yet. How does customFormatEnabled work exactly? I tried adding the wikipediapreview_gutenburg=1 url param manually but looks like I'm missing something?

Oh nevermind got it now, was missing the & for the url param

Note that the gutenburg secret param is highly unofficial. It is just for us. There is no plan to ask anyone to try the feature with this param.

Note that the gutenburg secret param is highly unofficial. It is just for us. There is no plan to ask anyone to try the feature with this param.

this page is public though...

Note that the gutenburg secret param is highly unofficial. It is just for us. There is no plan to ask anyone to try the feature with this param.

this page is public though...

That's right. It's also mentioned publicly on phab.
It's still 100% unsupported. If it's causing any issue anywhere we'll just remove it.


AKS create command doesn't work in this page as AKS default subnet has been changed to be <IP_ADDRESS>/12

AKS create command doesn't work in this page as AKS default subnet has been changed to be <IP_ADDRESS>/12
Error snapshot:

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

ID: e4a217cd-8949-e9b8-d8c5-a0f864b10237
Version Independent ID: e38769a3-04f6-c695-da48-8d0598a06bb9
Content: Tutorial: Enable the Ingress Controller add-on for a new AKS cluster with a new Azure Application Gateway
Content Source: articles/application-gateway/tutorial-ingress-controller-add-on-new.md
Service: application-gateway
GitHub Login: @Caya
Microsoft Alias: caya

@alexxiongxiong
Thanks for your feedback! We will investigate and update as appropriate.

@alexxiongxiong , thank you for your feedback. I was able to replicate the issue in my lab. We have assigned this to the content owner/author for review.
@mscatyao , could you please check the CLI command for deploying an AKS cluster with the add-on enabled as it is throwing an error as below?

#reassign:halkazwini

@alexxiongxiong
Thanks for the feedback, the CLI command is updated with <IP_ADDRESS>/16 which solves the above problem.


KAFKA-16823: Extract LegacyConsumer-specific unit tests from generic KafkaConsumerTest

KafkaConsumerTest -> unit tests that apply to both consumers.
LegacyKafkaConsumerTest -> unit tests that apply only to the LegacyKafkaConsumer, either because of the logic they test, or the way they are written (file to be created with this task)
AsyncKafkaConsumerTest -> unit tests that apply only to the AsyncKafkaConsumer (this file already exist)

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@FrankYang0529 It would be nice to review all tests before separating them. Maybe we can do a bit rewrite to make them works with both consumes.


Uncaught DOMException: Failed to execute 'define' on 'CustomElementRegistry'

I have tried to use  component in my 2 different components like fetch users and fetch modules.
My both components are placed in single HTML file so it gave below error because both component tried to define .
Uncaught DOMException: Failed to execute 'define' on 'CustomElementRegistry': this name has already been used with this registry.
Could you please guide how to use same component multiple time on same page?
To Reproduce
Create 2 Stencil web components.
NPM install mwc-linear-progress  in both components.
Use these 2 stencil web components in single page
It will throw an error  "Uncaught DOMException: Failed to execute 'define' on 'CustomElementRegistry'"

Hello, it seems as if you have a dependency clash. The solution is to npm ls @material/mwc-<name of duplicated component> which should tell you which dependencies are causing this clash. You must then clear your node_modules, update your package.json dependencies, and then reinstall.
If this solution does not work, please paste in your npm ls output and your package.json dependencies here and i will reopen the issue


Samples?

Hey

thank u for making this its awesome
Do you know how to access Samples? as in the actual Sample files that show the aggregated data per region

I've added support for samples, please let me know if works fine.
See readme for usage.


OCPBUGS-43746: add ValidIDPConfiguration condition to report IDP config issues

Combine clean picks of https://github.com/openshift/hypershift/pull/4852 and https://github.com/openshift/hypershift/pull/4955
The changes to API and HO are not required but don't hurt and make the picks clean

/jira cherry-pick OCPBUGS-38132

/jira refresh

/area control-plane-operator

/retest

/test e2e-kubevirt-aws-ovn-reduced

/lgtm

/cherry-pick release-4.16


TESSDATA_PREFIX

Environment

Tesseract Version: 4.0.0
Platform: Linux debian 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3.1 (2019-02-19) x86_64 GNU/Linux

Current Behavior:
pytesseract.pytesseract.TesseractError: (1, 'Error opening data file ./fra.traineddata Please make sure the TESSDATA_PREFIX environment variable is set to your "tessdata" directory. Failed loading language 'fra' Tesseract couln't load any languages! Could not initialize tesseract.')
Reading the wiki I found this command :
export TESSDATA_PREFIX=/usr/share/tesseract-ocr/
but It's not working at all. I tried to add it to PATH, into ~/.profile file but not working :/
Any ideas ?
Thanks in advance

Please respect guidelines for posting issue: we do not provide support for 3rd party projects.


Domain Activation

When I set up domain in Amplify, an error occurred like below.
Something went wrong. Please refer to our troubleshooting guide below to diagnose the issue. After fixing the issue, choose retry below. If retrying fails, please create an issue in our GitHub issue tracker.
Error message: One or more of the CNAMEs you provided are already associated with a different resource.
I'd like you to mention which CNAME is conflicted.
Best

Please review our troubleshooting guide: https://docs.aws.amazon.com/amplify/latest/userguide/custom-domain-troubleshoot-guide.html


FIX: Ensure deferred CMS panels are locale-specific (fixes #94)

Moved urlForLocale so it’s not bound to a selector, changed it to accept a URL as an argument rather than assume document.location.href is the URL in question;
Updated $(".cms-fluent-selector .cms-fluent-selector-locales a").onclick() to reflect new urlForLocale logic;
Added $('.cms-panel-deferred').onadd() to add the fluent locale parameter to the deferred URL

I initially tried just disabling the deferred panels from ever being cached, but I think this is a better approach as it keeps that caching in-place. It’s not specific to the CMS tree view (#94 is the issue I’m trying to fix), but I don’t think that matters.

Thanks @tractorcow. Any chance of a new tag? :)

https://github.com/tractorcow/silverstripe-fluent/releases/tag/3.2.1


Remove commented code from volumeprovisioner/profile.go file

Is this a BUG REPORT or FEATURE REQUEST?
FEATURE REQUEST
Details
There are a lot of commented code in the following file:
https://github.com/openebs/maya/blob/master/volumes/profile/volumeprovisioner/profile.go

Exercise care not to remove valid comments. Just remove the commented code & comments of this commented code.

@AmitKumarDas Working on it!


Avoid jdk8 incompatible code in CodeStyleTest

Jdk8 doesn't support Path.of yet, so we should revert to Paths.get.

Thanks a lot - how did you found this as the test are only compiling with JDK 11. do you use some kind of a checker?

IntelliJ complained about it. There are other problems I’ve had to work around, but this one seemed simple enough. I had also seen another commit that changed a Path.of to Paths.get so I assumed it was the intent to keep code as jdk8 friendly as possible.

Ah ok, i use IntelliJ from time to time but eclipse most of the time.
The test are requiring a JDK 11 because the selenium stuff is at jdk 11.
But for the lib build jdk 8 is still sufficient.
you can use something like
mvn deploy -Dmaven.test.skip=true

to deploy a local snapshot with jdk 8