Redhat: Error "Failed to initialize CoreCLR" during the installation

Agent version and platform
vsts-agent-rhel.7.2-x64-2.103.1

Red Hat Enterprise Linux Server release 7.2 (Maipo)

VSTS type and version
VisualStudio.com

What's not working?
As described here: https://github.com/Microsoft/vsts-agent/blob/master/docs/start/envredhat.md
I've installed the packages: curl-devel expat-devel gettext-devel openssl-devel zlib-devel gcc perl-ExtUtils-MakeMaker
But when i tried to run ./config.sh i have an error.
Failed to initialize CoreCLR, HRESULT: 0x80004005

## **Agent and Worker's diag log**
Haven't it

We'll investigate.  Thanks

Does this help?
sudo yum -y install libunwind.x86_64 icu

I have the same on a new Azure VM marketplace Ubuntu 16.04 image, followed all the pre-reqs, and got : Failed to initialize CoreCLR, HRESULT: 0x80131500.
including :  sudo apt-get install -y libunwind8 libunwind8-dev gettext libicu-dev liblttng-ust-dev libcurl4-openssl-dev libssl-dev uuid-dev unzip

still happening on fresh installs. the sudo yum command results in sudo: yum: command not found

@brandonh-msft  yum is a redhat version of apt-get

Please try out the latest agent release https://github.com/Microsoft/vsts-agent/releases/tag/v2.125.0
The latest version contains a script to help you install all missing dependencies.

@TingluoHuang What script is that?

Hmm. Seems like that wouldn't work on macOS then?
On Sun, Dec 10, 2017 at 8:20 PM, Ting<EMAIL_ADDRESS>wrote:

@lavahot https://github.com/lavahot https://github.com/Microsoft/
vsts-agent/blob/master/src/Misc/layoutbin/installdependencies.sh
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vsts-agent/issues/455#issuecomment-350619083,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6vjIfbvB_O749SEQnJEyfpmeDgJKyOks5s_K2hgaJpZM4JWows
.

Do you have a repro of a problem on Mac OS or is that a general question?
Get Outlook for iOShttps://aka.ms/o0ukef

From: Taylor Mansfield<EMAIL_ADDRESS>Sent: Monday, December 11, 2017 1:16:43 AM
To: Microsoft/vsts-agent
Cc: Bryan MacFarlane; Comment
Subject: Re: [Microsoft/vsts-agent] Redhat: Error "Failed to initialize CoreCLR" during the installation (#455)
Hmm. Seems like that wouldn't work on macOS then?
On Sun, Dec 10, 2017 at 8:20 PM, Ting<EMAIL_ADDRESS>wrote:

@lavahot https://github.com/lavahot https://github.com/Microsoft/
vsts-agent/blob/master/src/Misc/layoutbin/installdependencies.sh
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vsts-agent/issues/455#issuecomment-350619083,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6vjIfbvB_O749SEQnJEyfpmeDgJKyOks5s_K2hgaJpZM4JWows
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fvsts-agent%2Fissues%2F455%23issuecomment-350640615&data=04|01|bryanmac%40microsoft.com|66827181c74146ab1ab308d54067219d|72f988bf86f141af91ab2d7cd011db47|1|0|636485734048338799|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D|-1&sdata=NtflQbwmYZPjjKKOGC2B2IGj5zIHkhmeHx%2B6Gt8AvO4%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAA4IDBFxwcjqjhoAAl0xOWqVdAM9YKHNks5s_NbagaJpZM4JWows&data=04|01|bryanmac%40microsoft.com|66827181c74146ab1ab308d54067219d|72f988bf86f141af91ab2d7cd011db47|1|0|636485734048338799|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D|-1&sdata=aVQjfLBH%2FyT24ayN2JZ0YJOkeGRdvOHGjai0Up0jf6A%3D&reserved=0.

Not a very brief one. I need to try to isolate the issue in my cookbook. I'll make a new issue for macOS when I get closer to understanding the problem.

@lavahot https://github.com/Microsoft/vsts-agent/releases/tag/v2.126.0 is built on netcore 2.0, which means there is no requirements for macOS 10.12
https://docs.microsoft.com/en-us/dotnet/core/macos-prerequisites?tabs=netcore2x

... isn't 2.125.0 also built on netcore 2.0?

it is, but 2.125.0 has a little bug that may broken on macOS. you can use 2.125.1 or 2.126.0
the error you get on 2.125.0 is something about "not support exception, the SSL backend is not support for setup customized SSL validation handler."

Okay, I'm going to try a run on 2.126.0. I'll let you know the results.


"Create filter from selection" poor description

Issue in ./help/components/filters/create-filters.md
The description reported in the "Create filter from selection" cell is not clear, and the ordered list is not formatted correctly. Can you please give more details, specifying the actions step by step?
Thanks.

@angeli-adobe - I made some minor changes and am wondering what specifically is not clear to you. Please elaborate. You can re-open this ticket if what I provided is still not clear, thanks.
https://experienceleague.corp.adobe.com/docs/analytics-platform/using/cja-components/cja-filters/create-filters.html

Thanks @MicaPete ! The description is better, but the list is not formatted correctly.


optional one-to-many relationship: none/every filters: Incorrect SQL generated

Bug description
When running none/every filters on a one-to-many optional relationship, incorrect SQL is generated which leads to incorrect values being returned. In particular, this bug is triggered when an item has the optional relationship field set to null.
How to reproduce

Create a new project as per https://www.prisma.io/docs/getting-started/setup-prisma/start-from-scratch-prisma-migrate-typescript-postgres
Edit the schema.prisma file with the schema given below.
Run the migrations and generate the client as per the docs
Create an index.ts file with the contents given below
Run DEBUG="*" npx ts-node index.ts

Expected behavior
Running with debugging turned off we get
LOCATIONS:
[ { id: 310, name: 'A', companyId: null },
  { id: 311, name: 'A', companyId: null },
  { id: 314, name: 'A', companyId: null },
  { id: 312, name: 'B', companyId: null },
  { id: 317, name: 'B', companyId: null },
  { id: 313, name: 'C', companyId: null },
  { id: 315, name: 'C', companyId: null },
  { id: 316, name: 'D', companyId: null } ]
COMPANIES
[ { id: 134,
    name: '1',
    locations:
     [ { id: 310, name: 'A' },
       { id: 312, name: 'B' },
       { id: 313, name: 'C' } ] },
  { id: 135,
    name: '2',
    locations: [ { id: 311, name: 'A' }, { id: 314, name: 'A' } ] },
  { id: 136,
    name: '3',
    locations: [ { id: 315, name: 'C' }, { id: 317, name: 'B' } ] } ]
-----
SOME ('A'): (expect company '1' and '2')
[ { id: 134, name: '1' }, { id: 135, name: '2' } ]
NONE ('A'): (expect company '3')
[ { id: 136, name: '3' } ]
EVERY ('A'): (expect company '2')
[]
-----
SOME ('D'): (expect [])
[]
NONE ('D'): (expect company '1', '2', '3')
[]
EVERY ('D'): (expect [])
[]
-----
SOME ('E'): (expect [])
[]
NONE ('E'): (expect company '1', '2', '3')
[ { id: 134, name: '1' },
  { id: 135, name: '2' },
  { id: 136, name: '3' } ]
EVERY ('E'): (expect [])
[]

Note that we get unexpected return values for:

EVERY ('A'): (expect company '2') []
NONE ('D'): (expect company '1', '2', '3') []

Turning on full debug (DEBUG="*" and { log: ["query"] }) we get
(base) ➜  prisma-issue DEBUG="*" npx ts-node index.ts
  prisma-client { engineConfig:
  prisma-client    { cwd: '/Users/timleslie/src/prisma-issue/prisma',
  prisma-client      debug: false,
  prisma-client      datamodelPath:
  prisma-client       '/Users/timleslie/src/prisma-issue/node_modules/.prisma/client/schema.prisma',
  prisma-client      prismaPath: undefined,
  prisma-client      engineEndpoint: undefined,
  prisma-client      generator:
  prisma-client       { name: 'client',
  prisma-client         provider: 'prisma-client-js',
  prisma-client         output:
  prisma-client          '/Users/timleslie/src/prisma-issue/node_modules/@prisma/client',
  prisma-client         binaryTargets: [],
  prisma-client         experimentalFeatures: [Array],
  prisma-client         config: {} },
  prisma-client      showColors: false,
  prisma-client      logLevel: undefined,
  prisma-client      logQueries: true,
  prisma-client      flags: [],
  prisma-client      clientVersion: '2.2.2',
  prisma-client      enableExperimental: [ 'aggregations' ] } } +0ms
  prisma-client Prisma Client call: +130ms
  ...
LOCATIONS:
[ { id: 321, name: 'A', companyId: null },
  { id: 318, name: 'A', companyId: null },
  { id: 319, name: 'A', companyId: null },
  { id: 320, name: 'B', companyId: null },
  { id: 322, name: 'B', companyId: null },
  { id: 325, name: 'C', companyId: null },
  { id: 324, name: 'C', companyId: null },
  { id: 323, name: 'D', companyId: null } ]
...

NOTE
This bug only triggers if the database contains null values. If none of the Locations have a companyId that is NULL then the queries all work as expected.
Prisma information
schema.prisma
// This is your Prisma schema file,
// learn more about it in the docs: https://pris.ly/d/prisma-schema

datasource postgresql {
  url      = env("DATABASE_URL")
  provider = "postgresql"
}

generator client {
  provider = "prisma-client-js"
}

model Company {
  id        Int        @id @default(autoincrement())
  name      String?
  locations Location[] @relation("Locationcompany")
}

model Location {
  id        Int      @id @default(autoincrement())
  name      String?
  company   Company? @relation("Locationcompany", fields: [companyId], references: [id])
  companyId Int?
}

index.ts
import { PrismaClient } from "@prisma/client";
const prisma = new PrismaClient({
  log: ["query"],
});

async function main() {
  // Create some locations
  const locations = await Promise.all(
    ["A", "A", "A", "B", "B", "C", "C", "D"].map(async (name) =>
      prisma.location.create({ data: { name } })
    )
  );
  console.log("LOCATIONS:");
  console.dir(locations, { depth: null });
  // Create some companies, with different linked locations
  const c1 = await prisma.company.create({
    data: {
      name: "1",
      locations: {
        connect: [
          { id: locations[0].id }, // A
          { id: locations[3].id }, // B
          { id: locations[5].id }, // C
        ],
      },
    },
    include: { locations: { select: { id: true, name: true } } },
  });
  const c2 = await prisma.company.create({
    data: {
      name: "2",
      locations: {
        connect: [
          { id: locations[1].id }, // A
          { id: locations[2].id }, // A
        ],
      },
    },
    include: { locations: { select: { id: true, name: true } } },
  });
  const c3 = await prisma.company.create({
    data: {
      name: "3",
      locations: {
        connect: [
          { id: locations[4].id }, // B
          { id: locations[6].id }, // C
        ],
      },
    },
    include: { locations: { select: { id: true, name: true } } },
  });
  console.log("COMPANIES");
  console.dir([c1, c2, c3], { depth: null });

  console.log("-----");
  console.log("SOME ('A'): (expect company '1' and '2')");
  console.dir(
    await prisma.company.findMany({
      where: { locations: { some: { name: "A" } } },
    }),
    { depth: null }
  );
  console.log("NONE ('A'): (expect company '3')");
  console.dir(
    await prisma.company.findMany({
      where: { locations: { none: { name: "A" } } },
    }),
    { depth: null }
  );
  console.log("EVERY ('A'): (expect company '2')");
  console.dir(
    await prisma.company.findMany({
      where: { locations: { every: { name: "A" } } },
    }),
    { depth: null }
  );

  console.log("-----");
  console.log("SOME ('D'): (expect [])");
  console.dir(
    await prisma.company.findMany({
      where: { locations: { some: { name: "D" } } },
    }),
    { depth: null }
  );
  console.log("NONE ('D'): (expect company '1', '2', '3')");
  console.dir(
    await prisma.company.findMany({
      where: { locations: { none: { name: "D" } } },
    }),
    { depth: null }
  );
  console.log("EVERY ('D'): (expect [])");
  console.dir(
    await prisma.company.findMany({
      where: { locations: { every: { name: "D" } } },
    }),
    { depth: null }
  );

  console.log("-----");
  console.log("SOME ('E'): (expect [])");
  console.dir(
    await prisma.company.findMany({
      where: { locations: { some: { name: "E" } } },
    }),
    { depth: null }
  );
  console.log("NONE ('E'): (expect company '1', '2', '3')");
  console.dir(
    await prisma.company.findMany({
      where: { locations: { none: { name: "E" } } },
    }),
    { depth: null }
  );
  console.log("EVERY ('E'): (expect [])");
  console.dir(
    await prisma.company.findMany({
      where: { locations: { every: { name: "E" } } },
    }),
    { depth: null }
  );
}

main()
  .catch((e) => {
    throw e;
  })
  .finally(async () => {
    await prisma.disconnect();
  });

Environment & setup

OS: Mac OS 10.15.5
Database: PostgreSQL 12
Prisma version: 2.2.2
Node.js version: 12.11.0

I am able to reproduce this with 2.4.0-dev.29


Support priority for APNs, GCM, FCM

https://firebase.google.com/docs/cloud-messaging/http-server-ref

priority	Optional, string
Sets the priority of the message. Valid values are "normal" and "high." On iOS, these correspond to APNs priorities 5 and 10.

Might as well call them "normal" and "high" instead of numbers.
uniqush.priority or priority could be used as query param names in /push calls.

Hi @TysonAndre. Thank you very much for the latest updates to support FCM!
Would it be too much of a hassle to add "priority" as well? It is important for Android and I could really use it on a project I'm on right now.

Please add this functionality its important for VOIP pushes


Problem to enable icons-fonts addon

Describe the bug
When copying the addon folder to my project, I get the following error:
Unable to load addon script from path: 'res://addons/icons-fonts/icons_fonts.gd'. This might be due to a code error in that script.
Disabling the addon at 'res://addons/icons-fonts/plugin.cfg' to prevent further errors.

To Reproduce
Steps to reproduce the behavior:

I downloaded the project and extracted the zip file
I copied the content inside the addon folder and pasted it in my project addon's folder
I try to enable the plugins, and the plugin Rakugo Nodes is enabled properly (I guess), but the plugin Godot Icons Fonts throws the following error:

Unable to load addon script from path: 'res://addons/icons-fonts/icons_fonts.gd'. This might be due to a code error in that script.
Disabling the addon at 'res://addons/icons-fonts/plugin.cfg' to prevent further errors.

Expected behavior
I expect both addons to be enabled
Screenshots
If applicable, add screenshots to help explain your problem.

Runtime (please complete the following information):

Godot version [4.4]
Rakugo Version [master branch]

Additional context
Looking foward to use the addons

Hi, I'm very happy to hear that you are interested in using my project.
Just reload project and it should work.
It is problem with godot addons system itself that it don't allow to set order of loading script and their assets, so at first launch it load of addon it can happen.

I reloaded it, but I don't think that's the issue, I am getting a compilation error in icon_fonts.gd:
await IconsFonts.ready

Thanks for info, it is probably some bug with Godot 4.4.
I only tested it against 4.3.


FR: Support for action markers in Region Playlist OR an action to stop playback

If playback was launched with Region Playlist transport it can't be stopped/paused with action markers.
So my suggestion is to either add support for action markers or alternatively (which is presumably a less labor intensive solution), to add action SWS/S&M: Region Playlist - Stop, because there's already one for starting playback SWS/S&M: Region Playlist - Play and accompanying it with a counterpart for Stop seems logical.

related/duplicate: https://github.com/reaper-oss/sws/issues/914


complete fillIn example

https://github.com/cibernox/ember-native-dom-helpers/pull/115 should fix CI

Thank you!


Disable CodeCov upload in tests on forks

In general we should be doing this, as this step would always fail if we run the PR testing on forks; this should make it easier to manage a RAPIDS fork of this repo with minimal changes

Codecov Report

Merging #349 (f0fe136) into main (476c354) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #349      +/-   ##
==========================================
- Coverage   95.68%   95.68%   -0.01%
==========================================
  Files          66       66
  Lines        2898     2896       -2
  Branches      542      542
==========================================
- Hits         2773     2771       -2
  Misses         75       75
  Partials       50       50

Impacted Files
Coverage Δ

dask_sql/physical/rel/custom/predict.py
95.34% <0.00%> (-0.11%)
:arrow_down:

dask_sql/utils.py
100.00% <0.00%> (ø)

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 476c354...f0fe136. Read the comment docs.


SPK displays “error” when we have a warning

Describe the bug:

This is confusing to users.
Suggestion

Obviously spk infra scaffold runs fine with just command line flags. We shouldn't display a warning for this case. I suspect spk command that work without a configuration file might display this message too. We should re-work that logic.
Additionally the warning message should remove the word error and simply say  The SPK configuration file found.
Also we should only display this warning if verbose mode is activated

My concern with some of the suggestions for this issue is that even though spk infra scaffold runs successfully without initializing spk, a warning should still be displayed because it informs the user that spk infra scaffold can utilize the spk-config.yaml to configure infrastructure settings. Additionally, other spk commands rely on this message to inform users, so I think it makes sense that this message is outputted normally every time spk is not initialized.
Instead, maybe we can lower the severity of the message. We can re-word the message to let users know that the spk config file was not found and that we recommend them to run spk init or ensure that all argument values are passed in, or something along those lines. If have a "warning" message is misleading for users, we can also convert it to info.
@andrebriggs

@yradsmikham we need to remove the word "error". From what I've seem that is anxiety raising to some folks

Additionally the warning message should remove the word error and simply say The SPK configuration file found.

I agree with recommending to a user to run spk init. Sorry if that didn't come through in suggest #1

@andrebriggs Agreed. The word "error" is misleading, and I do intend to remove that.
I guess the point I was trying to make is this should not be displayed only in verbose mode, and by "re-working the logic", it can simply mean re-wording the message, as opposed to revising the code.


Logging

For #

[ ] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[ ] Title summarizes what is changing.
[ ] Has a news entry file (remember to thank yourself!).
[ ] Appropriate comments and documentation strings in the code.
[ ] Has sufficient logging.
[ ] Has telemetry for enhancements.
[ ] Unit tests & system/integration tests are added/updated.
[ ] Test plan is updated as appropriate.
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed).

Codecov Report

Merging #8015 (e716126) into main (84b025c) will increase coverage by 0%.
The diff coverage is n/a.

@@          Coverage Diff          @@
##            main   #8015   +/-   ##
=====================================
  Coverage     70%     70%
=====================================
  Files        367     367
  Lines      22580   22580
  Branches    3419    3419
=====================================
+ Hits       16000   16004    +4
+ Misses      5194    5192    -2
+ Partials    1386    1384    -2

Impacted Files
Coverage Δ

src/client/datascience/baseJupyterSession.ts
72% <0%> (+1%)
:arrow_up:

...client/datascience/kernel-launcher/kernelDaemon.ts
57% <0%> (+1%)
:arrow_up:


fix: escape every CSS ident character necessary

The list of characters to be escaped was determined by the serialize an identifier idiom of the CSSOM spec:

[Ignored rules about control characters and non-letter first symbols…]
If the character is not handled by one of the above rules and is greater than or equal to U+0080, is "-" (U+002D) or "_" (U+005F), or is in one of the ranges [0-9] (U+0030 to U+0039), [A-Z] (U+0041 to U+005A), or [a-z] (U+0061 to U+007A), then the character itself.
Otherwise, the escaped character.

The new list of characters in escapeRegex was generated by applying the rules above:
const arr = [];
for (let i = 0x20; i < 0x80; ++i) {
  if (
    i !== 0x7f &&
    i !== 0x2d &&
    !(i >= 0x30 && i <= 0x39) &&
    !(i >= 0x41 && i <= 0x5a) &&
    i !== 0x5f &&
    !(i >= 0x61 && i <= 0x7a)
  )
    arr.push(String.fromCharCode(i));
}
console.log(arr.join("")); // !"#$%&'()*+,./:;<=>?@[\]^`{|}~

What is this intended to fix?

Generating class names for components with display names which may contain characters to be escaped.

@kripod thanks for getting the tests fixed up. Could you add an entry to the changelog?

Sure!


Add color output to Mocha tests

Before:

After:

Also removes sample test

Simple PR  but nice feature. Thanks @fbricon !


Introduce ShardStorable interface

What this PR does / why we need it:
This PR adds a new interface called ShardStorable interface which is
type ShardStorable interface {
	// ListInUsedShards returns a list of shard which be used to store object of current collection.
	ListInUsedShards() []Shard
	// GetUpdatableShard returns shard which should be referred to on Updating object of current collection.
	// datastore.ErrUnsupported will be returned if there is no such file name exist.
	GetUpdatableShard() (Shard, error)
}

This interface will be used while implement the filedb database
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

NONE

@nghialv @knanao
thanks for the comments, I updated the implementation. In the latest implementation, this PR introduces a new interface named ShardStorable at the datastore layer, it contains 2 functions: ListInUsedShards and GetUpdatableShard.
The first one will be used in the database List, Get, Create interface while the latter for Update interface. The return value is of type Shard which is based on https://github.com/pipe-cd/pipecd/pull/3272#discussion_r808713182 idea, basically, for each object, we will store data of kind under as required shard directory in filestore service. PTAL 🙏

Awesome
/approve


rsync -a & usePolling=true: add event is not triggered for last big copied file

Describe the bug
When using option usePolling=true and copying big files to watched directory with rsync -a an add event is not triggered for last file in a list.
Versions (please complete the following information):

Chokidar version 3.3.1
Node version 10.17.0
OS version: Kubuntu 18.04 & CentOS 7.6

To Reproduce:
Here is a repo to reproduce.
Expected behavior
Trigger add event for last file copied by rsync.

The backlog is going to start from zero as a preparation for v4 release. v4 would bring massive rewrite to the table and drop most dependencies. All issues are being closed as preparation for v4 release.
In the future, only issues with enough community support would be considered.
See issue 1195 for more info. Thank you.


Question: Apple Metal status?

I saw the metal branch hasn't really been updated in quite some time.  Are there any plans to complete it?

Hi @Geenz ,
I am hoping to finish it, but it is delayed atm until we release new version of the library and move the renderer into a separate repo.

Thanks @yozhijk!
Is there any way anyone could perhaps help out with this?

Sure, we eagerly accept contributions, do you have someone in mind?

I was thinking of contributing a few things.  What is there left to be done?

Can you drop me an email at<EMAIL_ADDRESS>we can discuss offline.

Sorry to drop in on an old issue, but is the Metal support in Radeon ProRender (e.g. https://pro.radeon.com/en/radeon-prorender-macos-get-beta-now/) built upon RadeonRays? If so, are there plans to upstream those changes?

In my experience MoltenVK (Vulkan-on-Metal) is surprisingly robust, so I wonder if the simplest solution is for RadeonRays to support Metal via its Vulkan backend.  Note that this would require a few updates to Anvil first, in order to build on MacOS.


Label_image demo always gives same outputs

@tensorflow/micro
Hi all !
While testing our models with basic label_image example, we faced with strange results.
We tried label_image with 2 different YOLO models with their corresponding label.txt. However regardless the input images and labels, the test output is always in the same order as [2 3 0 1]. Finally we also gave the Grace Hopper image from official source and still we faced with same issue. You can see the outputs in the image below.
Normally our models are working smoothly on PC. But, it is important for us to test them in our iMX6 device with this basic sample. Do you have any idea or solution about this problem ?
Thank you in advance.

@ardtrkc  Could you please submit a new issue here since all micro related issues are handled separately.Thanks!


Java programmatic configuration should not be suggested by default

What needs to be changed? Describe the update that is required.
The Java manual instrumentation page provides an example based on the Spring Boot framework. Some users could find this page and starts to do programmatic configurations with Spring Boot. However, the Java agent, or the OpenTelemetry starter for some cases such as GraalVM native images, should be the options suggested first for Spring Boot in the documentation.
What is the name + path of the page that needs changed?
Manual Instrumentation
docs/instrumentation/java/manual/
cc @open-telemetry/java-approvers @open-telemetry/java-instrumentation-approvers

This issue began to be discussed during the Java SIG meeting of January 4, 2024. Some options have been suggested:

The Java manual instrumentation page could show an example not based on a microservice framework (Spring Boot, Quarkus)
the Java manual instrumentation page could give pointers to the Spring Boot page and the new Quarkus page (cc @brunobat).

Thanks for raising this issue @jeanbisutti, I am not sure if I understand the title of this issue correctly + the description of it: to me it sounds that using spring boot is the problem and not "programmatic configuration". I am OK with switching the framework, but then we also need to consider chaning it as well for the getting started to keep consistency. What alternative options do we have? Spring Boot is used because the example is fairly small and allows us to express everything that is needed in only a few lines of code.

I think the best option is number 1 from Jean's comment, that is, showing an example that doesn't instrument a framework. Couldn't we use the dice roll demo app for that?

@svrnm

to me it sounds that using spring boot is the problem and not "programmatic configuration"

The problem is to implicitly incite people to use programmatic configuration with Spring Boot. We have seen an issue doing this in the opentelemetry-java-instrumentation repo.

I am OK with switching the framework, but then we also need to consider chaning it as well for the getting started to keep consistency.

I don't think. The getting started uses a Spring Boot application with the OpenTelemetry Java agent. Spring Boot is know by a lot of Java programmers and the Java agent should cover most of the user needs with Spring Boot. I will create a PR to clarify more when it could be interested to use the OTel starter with Spring Boot and not the Java agent.
Spring Boot is used because the example is fairly small and allows us to express everything that is needed in only a few lines of code.
This point was mentioned by @jack-berg (I think) during the last Java SIG meeting.

My argument for switching the framework for the getting started as well, is not only around "what people know", but also for maintaining consistency. If people go through the getting started with the Spring Boot App, then switch to manual instrumentation and are presented with an example app that does something entirely different, this is a break in their user experience.

Any update?


Add zoom-in and zoom-out functionality

zoomIn and zoomOut functionality with control + and control - for zooming into and out of the field.
Currently, zoomIn shortcut is not working yet.

Turns out you have to use the names of the unmodified/unshifted keys in the shortcut, hence ctrl+= instead of ctrl-+ with splitKey set to +.

oh right, i overthought that!


feat(codepipeline): change to stand-alone Artifacts

This commit changes the way Artifacts are used in CodePipeline.
Instead of being properties on the Actions,
they are now stand-alone objects,
created independently of the Actions,
and referenced when instantiating them.
This is to not force users to assign Actions to intermediate variables
when defining a Pipeline.
This change had a few interesting consequences:

We no longer needed the abstract subclasses of Action like SourceAction,
DeployAction, etc., and so they were removed.
The old naming convention of inputArtifacts and outputArtifactNames
was shortened to be simply inputs and outputs.
There was no longer any need to differentiate Build and Test Actions,
and so the two CodeBuild and Jenkins Actions were merged into one.

BREAKING CHANGE: CodePipeline Actions no longer have the outputArtifact
and outputArtifacts properties.

inputArtifact(s) and additionalInputArtifacts properties were renamed
to input(s) and extraInputs.
outputArtifactName(s) and additionalOutputArtifactNames properties
were renamed to output(s) and extraOutputs.
The classes CodeBuildBuildAction and CodeBuildTestAction were merged
into one class CodeBuildAction.
The classes JenkinsBuildAction and JenkinsTestAction were merged
into one class JenkinsAction.

Fixes #2230

Pull Request Checklist

[x] Testing

Unit test added (prefer not to modify an existing test, otherwise, it's probably a breaking change)
CLI change?: coordinate update of integration tests with team
cdk-init template change?: coordinated update of integration tests with team

[x] Docs

jsdocs: All public APIs documented
README: README and/or documentation topic updated

[x] Title and Description

Change type: title prefixed with fix, feat will appear in changelog
Title: use lower-case and doesn't end with a period
Breaking?: last paragraph: "BREAKING CHANGE: <describe what changed + link for details>"
Issues: Indicate issues fixed via: "Fixes #xxx" or "Closes #xxx"

[x] Sensitive Modules (requires 2 PR approvers)

IAM Policy Document (in @aws-cdk/aws-iam)
EC2 Security Groups and ACLs (in @aws-cdk/aws-ec2)
Grant APIs (only if not based on official documentation with a reference)

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

Changes after review comments.

Added a missing test for action Artifacts bound validation.


Add a selftest for the "lwaftr loadtest" command

Add a selftest for the snabb lwaftr loadtest command. Part of #412, implements #754.
Also small changes to the run selftest.

Removed hard-coded CPU affinity settings as agreed upon.


fix(accordion): fix icon position in IE11

:tada: This PR is included in version 4.3.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


On Windows 10, lldb 'v' and 'p' commands get error regarding scratch context

I am unsure if this is due to a "bug" in the Swift installation procedure for Windows 10, or if there is an issue in LLDB itself.  I am new at Swift, and other thoughts are welcome!  And many thanks to all who helped bring Swift to Windows!!! :)
Environment
build number: Swift 5.6.1
OS: Windows 10 desktop computer
Issue Description
On Windows 10, lldb 'v' and 'p' commands get error: Cannot create Swift scratch context (couldn't load the Swift stdlib)
Test Case
After an install of Swift on Windows 10, run swiftc and lldb as shown below:
md Point
cd Point
create Point.swift with these lines:
    class Point {
        var x: Double
        var y: Double

        init(_ x: Double, _ y: Double) {
            self.x = x
            self.y = y
        }
    }

    let int = 1
    var dbl = 3.14159
    var str = "alpha"
    var pt = Point(3.0, 5.0)

    print("int: \(int)")
    print("dbl: \(dbl)")
    print("str: \(str)")
    print("pt: \(pt)")

compile it
set SWIFTFLAGS=-sdk %SDKROOT% -I %SDKROOT%\usr\lib\swift -L %SDKROOT%\usr\lib\swift\windows
swiftc -g -use-ld=lld -Xlinker -debug:dwarf Point.swift -o Point.exe %SWIFTFLAGS%
debug it
lldb point
(lldb) target create "point"
Current executable set to 'point' (x86_64).

(lldb) b 16
Breakpoint 1: where = point.exe`main + 206 at Point.swift:16:7, address = 0x00000001400012ce

(lldb) r
Process 18136 launched: 'K:\Point\point.exe' (x86_64)
Process 18136 stopped
* thread #1, stop reason = breakpoint 1.1
    frame #0: 0x00007ff6828a12ce point.exe`main at Point.swift:16:7
   13   var str = "alpha"
   14   var pt = Point(3.0, 5.0)
   15
-> 16   print("int: \(int)")
   17   print("dbl: \(dbl)")
   18   print("str: \(str)")
   19   print("pt: \(pt)")
Target 0: (point.exe) stopped.

(lldb) v int
(Int) int = 1

(lldb) v dbl
(Double) dbl = 3.1415899999999999

(lldb) v str
(String) str = "alpha"

(lldb) v pt
Cannot create Swift scratch context (couldn't load the Swift stdlib)Cannot create Swift scratch context (couldn't load the Swift stdlib)(lldb) (Point.Point) pt = 0x0000016dcb4a88c0 (x = 3, y = 5)

(lldb) v pt
(Point.Point) pt = 0x0000016dcb4a88c0 (x = 3, y = 5)

The first 'v pt' elicits the error above.  But it does at least display the value of 'pt'.
The second 'v pt' simply displays the value of 'pt' (no error).
Like 'v', the 'p' command elicits the error, but unlike 'v', it does not display the value at all - not for 'pt' and not even for 'int', 'dbl', or 'str':
(lldb) p int
Cannot create Swift scratch context (couldn't load the Swift stdlib)Cannot create Swift scratch context (couldn't load the Swift stdlib)(lldb) (lldb)

Is there a solution that eliminates the 'cannot create Swift stdlib' error for 'v' and 'p', and that gets 'p' to work?

This should be fixed as of a recent build.  Thanks for reporting the issue!

@compnerd, Thanks so much!

@compnerd Was this fixed in the llvm fork? Do we know which PR is was?


Implement composite bucket aggregation

We have all aggregations implemented expect composite.
https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-bucket-composite-aggregation.html

Added in v0.10.0


Permit use of Project Network Isolation with other compatible RKE network providers

This PR will allow the use of the Project Network Isolation feature for any RKE network provider that by default enforces Kubernetes network policies. In order to use the feature with plugins other than canal the built-in ingress provider must be disabled (ingress.provider=none) or configured with ingress.networkMode=hostPort|none.
Details
The Project Network Isolation feature (enableNetworkPolicy) is implemented via a controller that maintains Kubernetes network policies configured to either permit or allow traffic between namespaces based on whether the namespace is assigned to a particular project.
Being based on native Kubernetes network policies that feature is compatible with any CNI plugin that enforces Kubernetes network policies. This includes the following RKE network providers:

Canal
Calico
Weave
ACI

The only CNI plugin-specific functionality included in the network policy management controller is a Canal-specific workaround that allows the creation of network policy ingress rules for the NGINX ingress controller in the case where it's running in hostNetwork  mode (which requires the use of an IP-based policy rule).
https://github.com/rancher/rancher/issues/31338

Closing in favour of broader solution as discussed


Issue 53 - Product Superseding

Updates to how products are handled for superseded jobs/recipes:

New is_superseded and superseded fields added to the product_file model
Superseded jobs do not publish products
When a job publishes its products, it also unpublishes the products of any job(s) it supersedes
When a new product is published, any previously published product with the same UUID is superseded and unpublished
When a recipe job is superseded with no new job to "replace it", its products are immediately unpublished

LGTM

LGTM


[IMPROVE] NaN values in PVGO

For the following code snippet:

from financetoolkit import Toolkit

toolkit = Toolkit(["NVDA", "AAPL","BRK.B"], api_key=API_KEY, start_date="2000-01-01")

pvgo = toolkit.models.get_present_value_of_growth_opportunities()

I get the following result:

AAPL
BRK.B
NVDA

2000
0.4451
207.172
1.3462

2001
0.3214
98.699
5.283

2002
0.2313
114.778
1.0905

2003
0.3125
20.3332
1.677

2004
nan
5.1102
1.6264

2005
nan
-25.3974
1.8248

2006
nan
3.8913
nan

2007
nan
-39.0508
nan

2008
nan
81.6841
nan

2009
nan
48.8492
4.3185

2010
nan
31.844
3.6831

2011
nan
-113.76
-2.3902

2012
nan
32.7019
1.6914

2013
10.6612
91.6904
3.0434

2014
10.24
75.3026
3.5505

2015
-197.63
-482.481
-16.096

2016
7.5209
57.8841
24.4573

2017
30.7936
110.427
46.3468

2018
93.9601
248.859
44.3535

2019
64.6675
90.3009
56.1368

2020
113.997
109.681
125.633

2021
159.81
89.0447
290.602

2022
155.176
209.412
154.967

2023
170.215
102.937
491.612

2024
nan
nan
815.209

Does the FMP API miss something?

Solved! Total Debt was 0 for Apple which is why you see the NaNs. Please update to v1.8.5.

Ah I see, probably because interest expense is NaN in that case. I'll adjust this later.

Is that because we use WACC instead of the cost of equity, I can implement a flag to swap between using WACC or cost of equity.

Feel free to do so! Makes sense to have both.

I also talked to one of my finance teachers, and we figured it'd be better to go with the estimatedNetIncomeAvg from https://site.financialmodelingprep.com/developer/docs/analyst-estimates-api instead of using earnings from current period.

That's indeed also a good option, note that this is obtainable directly from the Finance Toolkit as well: https://www.jeroenbouma.com/projects/financetoolkit/docs#get_analyst_estimates (but I think you are aware of that :))


support sampler polyphonic syntax

feature mentioned in https://github.com/Tonejs/Tone.js/issues/345

Coverage decreased (-0.02%) to 98.755% when pulling adc6f0d22f74e3019bbc11a3a3474a8466f21ca2 on zfan40:dev into 6438f4688c9691a558ab56f650c307b4ec2a7bc0 on Tonejs:dev.

thanks!

Hey! This is cool! Would be cool if I could use the
polySampler.releaseAll()
function as well. Currently it is not working, or am I missing something?


when the Logic SQL is very long, SQLLogger print too much. if the Logic SQL is Cross-sharding，that's worse

Feature Request
when the Logic SQL is very long, SQLLogger print too much. if the Logic SQL is Cross-sharding，that's worse：
if there are 128 sharding table，there are 128 Actual SQL .
and SQLStatement and Logic SQL also will Output thousands of lines .
These outputs are of little value. So suggest that add a configuration(for example: sharding.jdbc.config.props.sql.show.simple=true) to simple it.

Cloud you submit a pull request

I am to  glad to add  this feature ,but which mentor can  help me to discuss the design of this ?  I am new to the opensource....

@betterjava Welcome to contribute code. you you can read contributor guide first: https://shardingsphere.apache.org/community/en/contribute/contributor/, hope to help you.

I have read it some days ago. Furthermore I have pull a request  to add the future.But I close the pull due to it let test coverage decrease. #2074. I added a integer properties (not boolean) to log config , and I do not know whether it is suitable or not ..


Runtime Warning

Experienced RuntimeWarning when trying to fit ParetoNBDFitter. I have removed NaN and negative values for the quantity my transaction data but I still get an error. Please advise how I can solve this issue.
Code
df= summary_data_from_transaction_data(data, customer_id_col='Customer_ID', datetime_col='Date')
pnf = ParetoNBDFitter(penalizer_coef=1e-06)
pnf.fit(df['frequency'], df['recency'], df['T'])
Warning Message
c:\Users\wqqs\Miniconda3\envs\env1\lib\site-packages\numpy\core\fromnumeric.py:86: RuntimeWarning: invalid value encountered in reduce
return ufunc.reduce(obj, axis, dtype, out, **passkwargs)
c:\Users\wqqs\Miniconda3\envs\env1\lib\site-packages\lifetimes\fitters\pareto_nbd_fitter.py:216: RuntimeWarning: invalid value encountered in logaddexp
A_2 = logaddexp(-(r + x) * log(alpha + T) - s * log(beta + T), log(s) + log_A_0 - log(r_s_x))

Hey @rachelyee,
Development on lifetimes ceased 3 years ago. Here's the link to the successor library:
https://github.com/pymc-labs/pymc-marketing
We're still finalizing the PR for ParetoNBD to fix this and other known issues with the lifetimes implementation, but for now, try using L-BFGS-B for the fit method and let me know how it goes:
ParetoNBDFitter().fit(fit_method='L-BFGS-B', *args)

Hi @ColtAllen ,
I have tried changing the fit method but got another warning message.
Optimize function with L-BFGS-B
c:\Users\wqqs\Miniconda3\envs\marketing\lib\site-packages\scipy\optimize_numdiff.py:576: RuntimeWarning: invalid value encountered in subtract
df = fun(x) - f0
<lifetimes.ParetoNBDFitter: fitted with 1603563 subjects, alpha: 829.34, beta: 790.13, r: 1.04, s: 1.05>

Thanks for sharing model.__repr__; your model probably isn't converging properly due to the input data containing huge T values.
alpha and beta represent the scale parameters for the time between transactions and average customer lifespans in the population, respectively. Large values for both parameters often happen when training over many years of data. This can lead to DIV/0 errors in the model's likelihood and predictive methods, causing RunTimeWarning to be raised.
If your data is aggregated by day, try training on two years or less of data. If you have to include the full timespan, then in summary_data_from_transaction_data(), try aggregating your data by week or month instead of day. Both suggestions will reduce the scale of the T variable and should lead to more stable results.


SimpleCommunication sample doesn't use powers of 2 for flags

https://github.com/Microsoft/Windows-universal-samples/blob/fe8567faf2efdea3672c2ba642ba7b925ff6467e/Samples/SimpleCommunication/common/MediaExtensions/Microsoft.Samples.SimpleCommunication/StspDefs.h#L64
Why the StspSampleFlags flag values are default enum value {0,1,2,3,4,5,6}, should it be {1,2,4,8,16,32,64} ?

Yeah that does look wrong. Let me see what the feature team says.

Feature team agrees. Fix will be in the next update. Thanks for reporting.


kratos: 0.10.1 -> 1.0.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ory/kratos/releases.
meta.description for kratos is: "An API-first Identity and User Management system that is built according to cloud architecture best practices"
meta.homepage for kratos is: "https://www.ory.sh/kratos/"
meta.changelog for kratos is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.11.0 with grep in /nix/store/c94wd26kb2d230g9108sii30mbxdck3j-kratos-0.11.0
found 0.11.0 in filename of file in /nix/store/c94wd26kb2d230g9108sii30mbxdck3j-kratos-0.11.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
kratos

Instructions to test this update (click to expand)

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

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

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

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

kratos

Maintainer pings
cc @MrMebelMan for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ory/kratos/releases.
meta.description for kratos is: An API-first Identity and User Management system that is built according to cloud architecture best practices
meta.homepage for kratos is: https://www.ory.sh/kratos/
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.11.1 with grep in /nix/store/g6xvkj68k03465hgqr56i5k78k4jm44k-kratos-0.11.1
found 0.11.1 in filename of file in /nix/store/g6xvkj68k03465hgqr56i5k78k4jm44k-kratos-0.11.1

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
kratos

Instructions to test this update (click to expand)

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

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

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

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

kratos

Maintainer pings
cc @MrMebelMan for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ory/kratos/releases.
meta.description for kratos is: An API-first Identity and User Management system that is built according to cloud architecture best practices
meta.homepage for kratos is: https://www.ory.sh/kratos/
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.13.0 with grep in /nix/store/zb8a7zkirjd1vi15590gcqzxib0srdvm-kratos-0.13.0
found 0.13.0 in filename of file in /nix/store/zb8a7zkirjd1vi15590gcqzxib0srdvm-kratos-0.13.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
kratos

Instructions to test this update (click to expand)

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

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

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

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

kratos

Maintainer pings
cc @MrMebelMan for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ory/kratos/releases.
meta.description for kratos is: An API-first Identity and User Management system that is built according to cloud architecture best practices
meta.homepage for kratos is: https://www.ory.sh/kratos/
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.0.0 with grep in /nix/store/7nw6lc8mh5dh1d1w80fbfkn0ng4h3d2g-kratos-1.0.0
found 1.0.0 in filename of file in /nix/store/7nw6lc8mh5dh1d1w80fbfkn0ng4h3d2g-kratos-1.0.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
kratos

Instructions to test this update (click to expand)

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

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

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

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

kratos

Maintainer pings
cc @MrMebelMan for testing.

I totally forgot about this automatic PR and did a manual upgrade: https://github.com/NixOS/nixpkgs/pull/253391
Should I close the new PR?


Only owner of the publisher can do delete operation

Only the owner of the publisher can do delete operation.

[ ] Create annotation @requires_roles
[ ] Check the use has enough permission to do that operation else throw 401

@rgrp I have one question. Can a user has multiple roles on a publisher[owner+member+read+write] or a single role[owner or member].

Will be done with #108


Patches for CAPT BMC-Hardware Power and Deprovision

Description of changes:
The patches involve changes to CAPT for enabling Hardware-BMC correspondence.

When a hardware is made part of the cluster, the bmcRef object is patched to perform powerOn.
When cluster is deleted and hardware is made available . bmcRef object is patched to perform Power Reset and setting PXE boot.
The BMC credentials are now referenced from a k8s secret.

The commits are the top 5 commits on my fork
pokearu/cluster-api-provider-tinkerbell
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/hold
Waiting on tests

/unhold

/hold

/unhold

/lgtm
/approve


Add a workaround to avoid issues when devstack needs APT

It's rare but it can happen that devstack runs at the same time as a
crontab is triggered and runs APT to e.g. execute unattended upgrades of
the system.
Devstack would fail since APT isn't available.
This patch adds a workaround so it'll remove the crontabs before
deploying devstack.

recheck

@wangxiyuan when CI is green please have a look.

sorry I had to rebase on master.


quick question

so looking at https://github.com/udu3324/Typsnd/blob/master/LICENCE.md that means its ok to make a carbon copy of Typsend on Kotlin (at https://github.com/afkvido/TSR), as long as i include a copyright notice for you.
are you ok with that or should i not make TSR at all?

*not all of it is a carbon copy, more of a similar replica, but the client code is copied

Yeah you can create Typsnd in Kotlin
It would also be nice if you could link back to the original project :>

Bet

It would also be nice if you could link back to the original project :>

https://github.com/afkvido/TSR/commit/dcfd3487550d08ae29fdfd2fdb9caf0af74d1f18

Oh also https://github.com/afkvido/TSR/commit/d12dcb85f9f08564e46344e508fe559b6409503c


Custom validation context

Implements issue #4 with suggested solution.

as long as it is implemented, I guess :smile:

Hi, I cannot see this.getContext() in a custom validator function. Hasn't this PR been integrated yet?  I'm using version 1.5.3 @aldeed

@davidecantini it's this.validationContext instead :smile:

@yanickrochon Thanks but unfortunately that is not available either. Here is what this contains in a custom function:

Based on your answer I assume that this PR has been integrated already, so the question is why some properties mentioned in the specs, including validationContext, are not available?
Thanks in advance to you, @aldeed or anyone who can help with this.

@davidecantini, 1.5.3 is the Meteor package, right? This was added to the NPM package only. I'm not adding new features to the Meteor package.

@aldeed yes, that's the case, thanks. I'll switch to the NPM package.
p.s. I'd suggest to put a link to the NPM package on the Meteor package page


changed dashes in every "tag_name" to underscores

This PR aims to address #1397.
All dashes in tags are replaced by underscores so that a vanilla call to set_tags with tag_name=tag_value will not break as tag_name does not contain any dash symbol.

uh-oh... lots of conflicts...

you probably based this on an outdate state of main? Rebase might help.


Use fully qualified collection names (FQCN) and fix linting for latest ansible-later version and drop Ubuntu 18.04

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


Upgrade from v3.17.10 to v4.2.0 problem

Bugs should be filed for issues encountered whilst operating logging-operator.
You should first attempt to resolve your issues through the community support
channels, e.g. Slack, in order to rule out individual configuration errors. #logging-operator
Please provide as much detail as possible.

Describe the bug:
I use banzai-cloud/logging-operator 3.17.10 and banzai-cloud/logging-operator-logging 3.17.10 configured to send the logs to OpenSearch v2.5.0 with ElasticSearch plugin.
I would like to upgrade from v3.17.10 to v4.2.0.
When I try to upgrade with my current elasticsearch cluster output config I get an error that server is not Elasticsearch.
             elasticsearch:
               buffer:
                 flush_interval: 1s
                 flush_mode: interval
                 flush_thread_count: 2
                 retry_max_interval: 60s
                 retry_timeout: 72h
               default_elasticsearch_version: "8"
               hosts: log-opensearch1.myserver.com,log-opensearch2.myserver.com
               include_timestamp: true
               index_name: cluster-a
               log_es_400_reason: true
               password:
                 valueFrom:
                   secretKeyRef:
                     name: opensearch-credentials
                     key: password
               port: 9200
               reconnect_on_error: true
               scheme: https
               ssl_verify: false
               suppress_type_name: true
               target_index_key: 'cluster-a'
               user: myuser
               verify_es_version_at_startup: false

  2023-04-17 16:03:59 +0000 [warn]: #0 suppressed same stacktrace
2023-04-17 16:03:59 +0000 [warn]: #0 [flow:logging:events:clusteroutput:logging:opensearch] failed to flush the buffer. retry_times=7 next_retry_time=2023-04-17 16:05:00 +0000 chunk="5f98a4f8e4d99797074acfbc8f0a54fc" error_class=Fluent::Plugin::ElasticsearchOutput::RecoverableRequestFailure error="could not push logs to Elasticsearch cluster ({:host=>\"log-opensearch1.myserver.com\", :port=>9200, :scheme=>\"https\", :user=>\"myuser\", :password=>\"obfuscated\"}, {:host=>\"log-opensearch1.myserver.com\", :port=>9200, :scheme=>\"https\", :user=>\"myuser\", :password=>\"obfuscated\"}): The client noticed that the server is not Elasticsearch and we do not support this unknown product.

When I change the output to opensearch and config to:
             opensearch:
               buffer:
                 flush_interval: 1s
                 flush_mode: interval
                 flush_thread_count: 2
                 retry_max_interval: 60s
                 retry_timeout: 72h
               default_opensearch_version: 2
               hosts: log-opensearch1.myserver.com,log-opensearch2.myserver.com
               include_timestamp: true
               index_name: cluster-a
               log_os_400_reason: true
               password:
                 valueFrom:
                   secretKeyRef:
                     name: opensearch-credentials
                     key: password
               port: 9200
               reconnect_on_error: true
               scheme: https
               ssl_verify: false
               suppress_type_name: true
               target_index_key: 'cluster-a'
               user: myuser
               verify_os_version_at_startup: false

I get an error of broken ruby gems in logging-operator-logging-fluentd-configcheck pod:
fluentd -c /fluentd/etc/fluent.conf --dry-run
2023-06-20 08:17:34 +0000 [info]: init supervisor logger path=nil rotate_age=nil rotate_size=nil
2023-06-20 08:17:34 +0000 [info]: parsing config file is succeeded path="/fluentd/etc/fluent.conf"
2023-06-20 08:17:35 +0000 [info]: gem 'fluentd' version '1.15.3'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-mixin-config-placeholders' version '0.4.0'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-aws-elasticsearch-service' version '2.4.1'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-azure-storage-append-blob' version '0.2.1'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-cloudwatch-logs' version '0.14.3'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-concat' version '2.5.0'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-datadog' version '0.14.2'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-dedot_filter' version '1.0.0'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-detect-exceptions' version '0.0.15'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-elasticsearch' version '5.3.0'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-enhance-k8s-metadata' version '2.0.0'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-gcs' version '0.4.0'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-gelf-hs' version '1.0.8'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-geoip' version '1.3.2'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-grafana-loki' version '1.2.20'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-grok-parser' version '2.6.2'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-kafka' version '0.18.1'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-kinesis' version '3.4.2'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-kube-events-timestamp' version '0.1.3'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-kubernetes-metadata-filter' version '2.5.3'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-kubernetes-sumologic' version '2.0.0'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-label-router' version '0.2.10'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-logdna' version '0.4.0'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-logzio' version '0.0.22'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-mattermost' version '0.2.2'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-multi-format-parser' version '1.0.0'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-mysqlslowquery' version '0.0.9'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-newrelic' version '1.2.2'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-opensearch' version '1.0.10'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-oss' version '0.0.2'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-parser-logfmt' version '0.0.0'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-prometheus' version '2.0.3'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-record-modifier' version '2.1.1'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-redis' version '0.3.5'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-remote-syslog' version '1.1'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-rewrite-tag-filter' version '2.4.0'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-s3' version '1.7.2'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-splunk-hec' version '1.3.2'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-sqs' version '3.0.0'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-sumologic_output' version '1.8.0'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-syslog_rfc5424' version '0.9.0.rc.8'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-tag-normaliser' version '0.1.2'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-throttle' version '0.0.5'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-vmware-log-intelligence' version '2.0.6'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-vmware-loginsight' version '1.4.0'
2023-06-20 08:17:35 +0000 [info]: gem 'fluent-plugin-webhdfs' version '1.5.0'
2023-06-20 08:17:35 +0000 [info]: starting fluentd-1.15.3 as dry run mode ruby="3.1.4"
2023-06-20 08:17:35 +0000 [info]: [flow:acme-website-dev:logs:2] DeDot will recurse nested hashes and arrays
/usr/lib/ruby/3.1.0/rubygems/specification.rb:2288:in `raise_if_conflicts': Unable to activate faraday_middleware-aws-sigv4-0.6.1, because faraday-2.7.6 conflicts with faraday (>= 1.8, < 2) (Gem::ConflictError)
        from /usr/lib/ruby/3.1.0/rubygems/specification.rb:1419:in `activate'
        from /usr/lib/ruby/3.1.0/rubygems.rb:211:in `rescue in try_activate'
        from /usr/lib/ruby/3.1.0/rubygems.rb:204:in `try_activate'
        from <internal:/usr/lib/ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:153:in `rescue in require'
        from <internal:/usr/lib/ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:149:in `require'
        from /usr/lib/ruby/gems/3.1.0/gems/fluent-plugin-opensearch-1.0.10/lib/fluent/plugin/out_opensearch.rb:58:in `<top (required)>'
        from <internal:/usr/lib/ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
        from <internal:/usr/lib/ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/registry.rb:103:in `block in search'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/registry.rb:100:in `each'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/registry.rb:100:in `search'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/registry.rb:44:in `lookup'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/plugin.rb:169:in `new_impl'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/plugin.rb:114:in `new_output'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/agent.rb:130:in `add_match'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/agent.rb:74:in `block in configure'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/agent.rb:64:in `each'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/agent.rb:64:in `configure'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/label.rb:31:in `configure'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/root_agent.rb:146:in `block in configure'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/root_agent.rb:146:in `each'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/root_agent.rb:146:in `configure'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/engine.rb:105:in `configure'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/engine.rb:80:in `run_configure'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/supervisor.rb:731:in `run_supervisor'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/command/fluentd.rb:350:in `<top (required)>'
        from <internal:/usr/lib/ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
        from <internal:/usr/lib/ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/bin/fluentd:15:in `<top (required)>'
        from /usr/bin/fluentd:25:in `load'
        from /usr/bin/fluentd:25:in `<main>'
/usr/lib/ruby/3.1.0/rubygems/specification.rb:2288:in `raise_if_conflicts': Unable to activate faraday_middleware-aws-sigv4-0.6.1, because faraday-2.7.6 conflicts with faraday (>= 1.8, < 2) (Gem::ConflictError)

Expected behaviour:
Fluentd config check passes and logs are sent to OpenSearch successfully.
Steps to reproduce the bug:
Try to upgrade from version v3.17.10 to v4.2.0 with both configurations from above.
Environment details:

Kubernetes version (e.g. v1.15.2): v1.24.9+rke2r2
Cloud-provider/provisioner (e.g. AKS, GKE, EKS, PKE etc): Bare-metal, RKE2
logging-operator version (e.g. 2.1.1): v4.2.0
Install method (e.g. helm or static manifests): Helm
Logs from the misbehaving component (and any other relevant logs): Logs mentioned above
Resource definition (possibly in YAML format) that caused the issue, without sensitive data: yamls mentioned above

/kind bug

Conflict exists in fluentd image release. I have proposed a fix in this PR

That fix is already published, did that resolve your problem?

Closing for now, please reopen if needed


Not validating service numbers of India

Imported from Google Code issue #334 created by nayak.chandra1 on 2013-08-06T11:15:54.000Z:

What steps will reproduce the problem?

Go to "Phone Number Parser Demo" page, under "Demo" section.
Give any emergency numbers like 100(local police), 101(fire service) etc
Result shows Invalid Number.

What is the expected output? What do you see instead?

It should show the given number as a valid one.
The getNumberType() should be EMERGENCY.

What version of the product are you using? On what operating system?
Please provide any additional information below.

We have recently done many India updates from the dot.gov.in website and have more coming up so the docs from 2003 were either covered in the meantime or are out of scope. The short number results are working as intended.

Actually we will add some more short-code support to India. Will leave this open to track this.

Fixed in release 8.4.0


my screen rotates 90 degrees automatically.

Whenever I connect the USB of Intel realsense, my screen rotates 90 degrees automatically. Why is that? My system is Ubuntu20.04 , camera D435i.

Hi @chrisxu1995  This may occur because your D435i's IMU component (which contains a gyro and accelerometer) is being detected by Ubuntu and activating Ubuntu's screen rotation feature.  You can lock screen rotation in Ubuntu, as described in the link below.
https://github.com/IntelRealSense/librealsense/issues/6941

Hi @chrisxu1995 This may occur because your D435i's IMU component (which contains a gyro and accelerometer) is being detected by Ubuntu and activating Ubuntu's screen rotation feature. You can lock screen rotation in Ubuntu, as described in the link below.
#6941

it works, thx

Hi! Same thing happens with my Ubuntu 22.04 LTS.
I cannot turn off screen rotation because I need it rotated at 180º (inversed horizontal)
Is there any way to disable this feature from Camera-Side? Thank you.


Please add reference.

Problem description
I could not find how to install Docker to deployed Amazon Linux environment,
I tried to install Docker reffering to this page(https://docs.docker.com/install/linux/docker-ce/centos/).
But i failed the following step 'Set up the repository>1.Install required packages'.
Problem location

I couldn't find the information I wanted. I expected to find it near the following URL:https://docs.docker.com/docker-for-aws/

Suggestions for a fix
I could not find how to install Docker to deployed Amazon Linux environment,
I tried to install Docker reffering to this page(https://docs.docker.com/install/linux/docker-ce/centos/).
But i failed the following step 'Set up the repository>1.Install required packages'.

@shimada123 , it should be straightforward. Please try this:
sudo yum install -y yum-utils device-mapper-persistent-data lvm2
sudo yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo
sudo yum install docker-ce
sudo systemctl start docker
sudo docker run hello-world

$ sudo docker version

Client:
 Version:      18.03.1-ce
 API version:  1.37
 Go version:   go1.9.5
 Git commit:   9ee9f40
 Built:        Thu Apr 26 07:20:16 2018
 OS/Arch:      linux/amd64
 Experimental: false
 Orchestrator: swarm

Server:
 Engine:
  Version:      18.03.1-ce
  API version:  1.37 (minimum version 1.12)
  Go version:   go1.9.5
  Git commit:   9ee9f40
  Built:        Thu Apr 26 07:23:58 2018
  OS/Arch:      linux/amd64
  Experimental: false

Closing this ticket due to its age, and the impending refactor. If you think this is in error, feel free to reopen. Thanks!


Number of spaces for indentation

Hi,
I just tried your this new tool, and it works great, and I like the output a lot.
I am curious why you decided to go with 2 spaces for indentation.
Pretty much all of my own projects, the projects I contribute to (zope, plone, ...) or I use e.g. tox, pytest, flask, ... use 4 spaces for indentation in config files, especially for tox.ini.
As a Python developer, this is something we are used to, but imho the better reason is, that the ini file then is way easier to scan, as there is a bigger distinction between keys and values ( This is similar to when you have a text and you make the heading not just one font size bigger, but some more).
Do you plan to make the number of spaces configurable?
Thanks!

I went for the two space to save some screen real estate, that being said this project wants to compliment setup-cfg-fmt, and that uses 4 spaces, so we should probably also use 4 spaces, now that I think about it.

Great news!
Well, I spent some time on my smartphone reading the source how to figure out how to implement a command line flag to make this optional, but just using indentation of 4 would be even better :-)
Just in case, I create #28 - no pressure :-)


SponsorBlock doesn't work as it should in python code

Checklist

[X] I'm reporting a bug unrelated to a specific site
[X] I've verified that I'm running yt-dlp version 2021.10.22. (update instructions)
[X] I've checked that all provided URLs are alive and playable in a browser
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Description
Sponsorblock didn't fetching segments when i use in postprocessors.
Code:
import yt_dlp

ydl_opts = {
    'format': 'bv*[ext=mp4]+ba*[ext=m4a]',
    'postprocessors': [{
        "key":"SponsorBlock",
        "categories":"all",
    }]}

with yt_dlp.YoutubeDL(ydl_opts) as ydl:
    ydl.download([input("URL: ")])

URL example:
https://www.youtube.com/watch?v=54-9xeWLHqQ
Verbose log
(idk how to add flag "verbose" in python code)
[youtube] 54-9xeWLHqQ: Downloading webpage
[youtube] 54-9xeWLHqQ: Downloading android player API JSON
[info] 54-9xeWLHqQ: Downloading 1 format(s): 137+140
[download] Destination: ЧТО СТАЛО С ЦЫПЛЕНКОМ РЭМБО В ДЕРЕВНЕ [54-9xeWLHqQ].f137.mp4
[download] 100% of 177.67MiB in 00:17
[download] Destination: ЧТО СТАЛО С ЦЫПЛЕНКОМ РЭМБО В ДЕРЕВНЕ [54-9xeWLHqQ].f140.m4a
[download] 100% of 6.54MiB in 00:00
[Merger] Merging formats into "ЧТО СТАЛО С ЦЫПЛЕНКОМ РЭМБО В ДЕРЕВНЕ [54-9xeWLHqQ].mp4"
Deleting original file ЧТО СТАЛО С ЦЫПЛЕНКОМ РЭМБО В ДЕРЕВНЕ [54-9xeWLHqQ].f137.mp4 (pass -k to keep)
Deleting original file ЧТО СТАЛО С ЦЫПЛЕНКОМ РЭМБО В ДЕРЕВНЕ [54-9xeWLHqQ].f140.m4a (pass -k to keep)
[SponsorBlock] Fetching SponsorBlock segments
[SponsorBlock] No segments were found in the SponsorBlock database

Duplicate of https://github.com/yt-dlp/yt-dlp/issues/1238
Also, that video doesnt have any segments

[SponsorBlock] No segments were found in the SponsorBlock database


updating the model for range slider does not update the view.

In example 9, changing value in the input text field does not update the slider handles.

same problem i am facing. Have you find any solution ?

Fixed via #95


Lending Affiliate Fees

Separating this out from Pull requests for better tracking. From PR #5813 ; uncluttering #6679
Upstream blockers

[ ] https://gitlab.com/thorchain/thornode/-/merge_requests/3425
[x] DFC vote on params

DFC vote held quorum https://discord.com/channels/554694662431178782/920449863408287855/1225575197776543754
Lending fee parameters
fox_max_discount_threshold= 300_000
no_fee_threshold_usd = 1_000
max_fee_bps = 69 // :nice:
 min_fee_bps = 10
FOX midpoint_usd = 150_000
 steepness = 40_000

https://gitlab.com/thorchain/thornode/-/merge_requests/3425
aaaand we're merged. LFG

PR #5813 - addresses this, blocked by testing since lending caps are in place.

caps never removed. 😭


Fix tooltips in segmentations without locations in spatial layer

Fixes #1981

Change List

packages/view-types/spatial/src/Spatial.js was not calling setHoverInfo, so no information about the hovered obs or hovered coordinates was being stored or passed to packages/view-types/spatial/src/SpatialTooltipSubscriber.js
packages/view-types/spatial/src/SpatialTooltipSubscriber.js was applying a transform to the raw x and y mouse coordinates that was causing it to appear in the wrong location.

Checklist

[X] Have tested PR with one or more demo configurations
[X] Documentation added, updated, or not applicable

@keller-mark could you check this out when you have a chance? Thanks in advance!


World generation

Can one of the admins verify this patch?

Urm... be quiet, Jenkins

Looks good! :+1:


Migrating SQLite db to ForestDB

iOS Ticket: https://github.com/couchbase/couchbase-lite-ios/issues/870

I started working on this to complete the missing part in openDatabase API so I will assign this issue to myself.


Twitter service does not account for URLs in the message

See e.g. https://twitter.com/encodings/status/528586451504463872 having truncated URL in it that therefore points to the wrong bug.

We rely on Twitter to shorten URLs using their shortener. You can read more in the Twitter service. There have also been other bugs solved around this area since this issue so it is likely this is already fixed.

The problem is that truncated URLs get shortened. And no this is not fixed. Could you please reopen this? Recent example: https://twitter.com/urlstandard/status/632595525796253696

Hey @annevk! Yup, I'll re-open this issue. Thanks for adding more information to this issue.

The issue is that you truncate the commit message yourselves to fit within the 140 char limit, but you don't account for URLs in the commit message which would be shorted, and so should not count for their own length but for the t.co length (you take it into account only for the URL you are adding yourselves): https://github.com/github/github-services/blob/f804613a178f0f46acc53eded85308d5db25929a/lib/services/twitter.rb#L58

Thanks for clarifying @stof :zap:
We'd be happy to look at a PR that implements a bug fix for this.

Well, the logic implementing the computation of the tweet length is available in https://github.com/twitter/twitter-text/blob/6f7eef096abb10b17d43a391b637fc494877ae21/rb/lib/twitter-text/validation.rb#L13-L36
I don't know whether you would consider using this library to compute it.
In any case, I will let someone else work on this. I'm a PHP developer, not a Ruby one

We'd probably rather this is done without adding another library. If anyone wants to try and create a pull request (or needs help) feel free to ask.

We may accept a PR that doesn't use another library but I'm closing this out for now.


navigation buttons optional property - buttons missing from the options

With the default navigation set to anything but linear we have some buttons missing from the options when changing the navigation button options for a particular page. e.g. at the moment we have the following:
All
Back and Next
Back only
Next only
None
However with navigation set to historic there isn't an option to include or exclude the home button
and with navigation set to menu or menu with page controls (or indeed linear) there's no option to include or exclude the contents button which in the case of the 2 menu options is what goes back to the menu on the first page. But I guess adding these to the navigation button options isn't straightforward because control over each additional button add at least 3 extra permutations. e.g. just to add the home button in the mix (which would be useful) I think we would need:
All
Home only
Home, Back and Next
Back and Next only
Home and Back only
Back only
Home and Next only
Next only
None
And then even more if you add Contents to the mix.
I know we can show/hide via jquery and/or css but just wondering if there's a way to enable this for everyone but also in a way that doesn't require so many permutations in the list menu?

How about we change it so that it uses the new group of optional properties instead of just 1 drop down. You also wouldn't need separate options for home & contents etc. as I think when the home button's there the content button is normally not. The options would look something like this...
Navigation buttons:

[ ] Home / Contents / Menu
[ ] Back / Previous
[ ] Next

@FayCross sounds like a good idea. Assuming that change wouldn't break existing LO's that have used the dropdown options?

Ok, I'll look into it

@ronm123 Just realised I assigned this to myself months ago - what I've just committed shouldn't break existing projects but give a bit more flexibility as to which buttons can be turned on / off

@FayCross great I'll give it a try.
By coincidence I was looking at some projects yesterday and realised and recalled that it would also be quite useful to add an optional property to include a home button when using linear navigation and perhaps with control over what page that actually goes to. I know the TOC button allows that but obviously that's two clicks and less intuitive. What do you think is it worth adding that as an enhancement issue for future development?

Yes we could add something like that too. I was wondering also about the option to show / hide the page numbers when it's linear. At the moment when adding a progress bar you can choose to hide the numbers but it would give greater flexibility to have progress bar & page numbers as two separate options.
Much more complicated but I was also thinking about how it would be useful when navigation is linear to allow for pages to be taken out of the main flow (& page numbering) and only accessed via links from other pages. So, for example, you could have a link from a page to something like a 'more info' page which wouldn't be numbered & wouldn't have a next button but the back button would work as a historical back to take you back to the main strand. I guess it would be similar to hide page option but you could actually access the hidden pages from links if needed.

@FayCross I'm probably forgetting how this worked previously and so thes issue may have existed already but looking at the table of contents group of properties it seems like there's a bug with some of this.
If I set the LO navigation to menu or menu with page controls and set the page image option to 'Use Panel' I get an image in a panel on the menu page and using the buttons to navigate to a page shows the content of that destination page. So I think that's how it should be except that the image is displayed below the buttons and I seem to recall it used to display to the right of the buttons?
If I set the page image to 'Full Screen' rather than 'Use Panel' I don't get an image on the menu page on first playing the LO but the image becomes a full screen background to all the pages. If I then click the TOC button to go back to the menu page the 'Full Screen' image is then shown on the menu page but also remains on all the pages. That image also overrides any image that was set using the separate LO background image option e.g. the background image doesn't show with the TOC image set to full screen. Clearly the TOC image should only show on the menu page.
Also if I have lots of pages e.g. 16 so that the buttons need to scroll on first play that scrolling is hidden but then shown after navigating to a page and then back to the menu.

Sorry I clicked comment before finishing :-(
Also as the TOC group options apply to the menu page the page numbering option works but the ticks when viewed don't. e.g. the ticks don't appear on the menu buttons.
Ron

@ronm123 it does look like there's something odd going on with the images on the menu pages but I think this must have been broken for some time as I haven't touched that side of the code. I'll copy your comment into another issue.


WIP: Design documentation for ACME self check failure policy

What this PR does / why we need it:
This PR adds a design document for controlling failure policies for the ACME self-check.
Which issue this PR fixes:
The design documentation does not solve anything per se, but the functionality that the design documentation suggests is related to #1292.
Special notes for your reviewer:
This is a work in progress. The namings aren't optimal and should be improved before merge.
Release note:

NONE

Does anyone have any thoughts on naming convention here? Maybe better with more descriptive enumeration values:

MustSucceed
FailureAllowed

I think FailureAllowed sounds like... for what do you need it for? I would guess it's like "do the checks, but we will ignore the results". I would prefer something "Do NOT check, since I will ignore the results". Why should it be checked if it's ignored? It's only filling the logs and important log entries might be hidden. So maybe something like

disabled
successRequired / requireSuccess / validationRequired

Currently not sure if there are useful additional semantics.

I would guess it's like "do the checks, but we will ignore the results". I would prefer something "Do NOT check, since I will ignore the results". Why should it be checked if it's ignored?

The thinking is that a failure policy is universally applicable regardless of what strategy you choose, i.e. if we added an alternate strategy like 'external', it'd make sense to also be able to say "but permit failures". By still performing the check, we can report potential issues to users (i.e. 404 page not found was detected, but trying anyway due to policy) which can better inform people as to why it may still be failing after that.
I don't think this proposal is exclusive of also having a strategy field in future, and that strategy field may accept a value like None, but there's a fair bit more design around API surface that we'd need to consider, and given users are not really asking for ways to implement alternate strategies and instead want a way to skip the self check due to awkward network configurations, failurePolicy is something that can be added without creating too much controversy/complexity.

I will squash the commits - properly signed-off - and rebase the branch when the design has gotten an OK!

Looking great! Just one tiny spelling comment :wink:

Hey @anton-johansson - just checking in 😄 is there anything we can do to help this along?

Hey @munnerz. No, sadly. I pinged you on Slack a while ago about a way forward.

Closing old stale PRs to keep an overview for the reviewers. Feel free to /reopen if work started on this again.
/close


Sincerely consult

Dear author, thank you for your great work! I have two questions.

What is the meaning of "96,192,336,720" of column "Metrics" in Table 1 in your paper?

2)I try to reproduce the experimental results through Option B. However, I get this error. Could you give me some advice?

Thank you very much! I really appreciate it!

Those are forecast horizons, i.e. how many time steps to predict.

Thank you very much for your swift reply!
2. Definitely! I have run make build-all path=experiments/configs/ETTm2.

I can't really help without more information... you can try checking whether the files indicated in the script are generated, and try to run the commands in the run.sh file directly

Thank you very much! Let me have more try and provide some feedback for avoiding it from happening for other user!
Thank you again:D

I successfully solve it! I realize I unzip the all_six_datasets.zip dataset but forget to move them to the upper folder. Sorry for the time caused by me:D


domI18n is not defined?

I followed your example.
But it seems that domI18n is not in the global namespace.
Uncaught TypeError: window.domI18n is not a function
at ign.html:12

hi @CreatCodeBuild can you be more specific, which example did you followed?
The only case I can imagine for now is that you may have an exports global object defined somewhere that is breaking the UMD detection mechanism.
Let me know if that's the case and if not, please link a running example if possible 😊
Thanks in advance!


Arrays in C++

in data structure folder create arrays folder then create arrays .cpp

Okay!
On Fri, 7 Oct, 2022, 12:12 am Shashank Bhardwaj, @.***>
wrote:

Closed #18 https://github.com/shashank1623/c_plus_plus/pull/18.
—
Reply to this email directly, view it on GitHub
https://github.com/shashank1623/c_plus_plus/pull/18#event-7537782089,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AY3OO4TLZAK4GGTZRP7ADE3WB4MQ3ANCNFSM6AAAAAAQ64JSFU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hey I have created a file name Array.cpp under data_structures please have
a look.
On Fri, 7 Oct, 2022, 12:30 am TUSHAR MISHRA, @.***>
wrote:

Okay!
On Fri, 7 Oct, 2022, 12:12 am Shashank Bhardwaj, @.***>
wrote:

Closed #18 https://github.com/shashank1623/c_plus_plus/pull/18.
—
Reply to this email directly, view it on GitHub
https://github.com/shashank1623/c_plus_plus/pull/18#event-7537782089,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AY3OO4TLZAK4GGTZRP7ADE3WB4MQ3ANCNFSM6AAAAAAQ64JSFU
.
You are receiving this because you authored the thread.Message ID:
@.***>


Write Program to Buffer Account

Verifiably build the program and write the program to the designated buffer account.
Commit: <>
Buffer address: <>

[ ] Devnet
[x] Testnet
[ ] Mainnet-Beta

Note this buffer account cannot be deployed until sol_get_sysvar is active on the target cluster, as per ELF verification.
https://github.com/anza-xyz/feature-gate-tracker/issues/39


Nice features from other UTFs for Igor Pro

[ ] Random Seed was reset to a value of (1 / 32060) before each test function was called.
[x] Randomize test order in a test suite
[ ] Nice GUI (can readback JUNIT XML output e.g., or we create JSON output, see #191)
[x] Pass string into test assertion. This string is then outputted on a failed assertion.

https://github.com/byte-physics/igor-unit-testing-framework/issues/11

Pass string into test assertion. This string is then outputted on a failed assertion.

Isn't this done with the INFO() statement?

Pass string into test assertion. This string is then outputted on a failed assertion.

Isn't this done with the INFO() statement?

Yes!

Random Seed was reset to a value of (1 / 32060) before each test function was called.

Do we need this? The user can do this in the test begin hooks for each test case...


Coverage seems broken

Something with the coverage seems odd. How can line 1 be missed, but line 11 run?

Do you dynamically recreate / reload modules?

@sobolevn there is code to dynamically load views but this code right here is imported directly

I've seen problems like this when:

sys.modules are modified after initial load
pytest plugin conflict, when some plugin loads your modules before pytest-cov does, example:  https://github.com/dry-python/returns/blob/master/tests/conftest.py#L10-L11

@sobolevn Hm. The loading mechanic is a feature i don't want to remove. I had a similar problem in another project a while ago. This line fixed it, but i think it's a hack
https://github.com/pengutronix/aiohttp-json-rpc/blob/master/tox.ini#L47

@sobolevn, @maratori I tried this approach in https://github.com/lona-web-org/lona/tree/fscherf/fix-coverage and it really seems to fix this problem, but is this a good fix? The problem seems to be that the coverage is loaded to late, or is capturing to late.

@fscherf I don't know what is the right way to fix it. Here is another example, I've hound https://github.com/pytest-dev/pytest-print/blob/eb776107d83a94e90edeb7381d679251ae45bcf0/tox.ini#L27-L33.

@maratori ah ok! Similar approach but cleaner implemented. To my eyes that looks less like a hack

The problem was solved in #139. @maratori, @sobolevn Thanks for your time!


prefer python 3

document that we prefer python 3 over python 2.

this fixes #52

Digital Marketplace are currently in the process of upgrading our apps from Python 2 to Python 3. Our API is already there, the remaining apps should follow in this sprint.

@timblair hi! I'm from "Better Use of Data", how can I help?

I spoke to Dan Heron from better use of data and he says they're happy with this wording.


Allow to ignore CVEs

When a list of CVEs to ignore is provided, a Grype config file is generated with ignore entries.

Could we print the list of ignored CVEs in the summary output please.


Should you consider adding adb's configuration file？

When I use this program to enter pubg, I found that adb is working, but I cannot add my own code, which is bad

What do you mean?

I hope that I can add adb commands to better control the game

For example, add a mouse control in adb

I'm not sure to understand, but I guess you want something to programmatically inject mouse clicks or other events: #399


Persisting data to disk for node version

Are there any plans to implement asynchronous persistent disk storage for the rdf-store?
If no - it would be nice to have it. ;)

A persistent MongoDB backend has been added

I'm evaluating MongoDb RDF persistence but can't seem to get any statements actually written into Mongo using the script below.  Is it necessary to run the SPARQL endpoint for persistence?   The launch script for that isn't included with the npm install distribution, and after building the node.js version (from zip) the script throws error cannot find module './index'.  Any help appreciated :)
var rdfstore = require('rdfstore');
new rdfstore.Store({persistent:true,
engine:'mongodb',
name:'mwa', // quads in MongoDB will be stored in a DB named mwa
overwrite:false,    // delete all the data already present in the MongoDB server
mongoDomain:'localhost', // location of the MongoDB instance, localhost by default
mongoPort:27017 // port where the MongoDB server is running, 27017 by default
}, function( store ){
        store.execute('SELECT * { ?s ?p ?o }', function(success,results) {
	console.log('\n\nFIRST SELECT returned ' + success + ' and results ' + JSON.stringify(results) );
	if ( results.length==0) {
		// try an insert and then a query
		store.execute('INSERT DATA { <http://example/book3> <http://example.com/vocab#title> <http://test.com/example> }', function(result, msg){
			console.log('\n\nINSERT returned ' + result + ' and msg ' + JSON.stringify(msg) );
			store.execute('SELECT * { ?s ?p ?o }', function(success,results) {
				console.log('select returned ' + success + ' and results ' + JSON.stringify(results) );
			});
		});
	}
});

});


JSX/JS: Single field objects should not expand

Reposted: Originally reported here
Its common in a react app to write a set field method
_setFoo: function() { this.setState({foo: "bar"}); },

currently the beautifier expands that to and just scrolls.
_setFoo: function() {
  this.setState({
    foo: "bar"
  });
},

Would be great to support a a folded version based on a flag option.

Hi. Any chance of this feature landing any time soon? Thx!

This is another aspect of #315.  It is highly requested feature.


Selected feature is not deselected when hiding parent layer

When hiding a layer from view, if the selected feature comes from that layer, the selection should be cleared.
Currently, the highlighted selection is still displayed, even though all other features of that layer aren't visible.
Steps to reproduce:

click on a feature to select
hide layer to which the feature belongs
the highlighted feature is still visible

With the new selection highlight implementation (#35), the highlight is no longer shown if the main layer itself is hidden.
However, the feature sidebar for the selected feature is still shown, even if the feature is not visible on the map.
@tomalrussell do we want to do anything about this (e.g. hide the sidebar if the feature is not visible) or is the functionality fine as it is now and we can close this issue?

Happy to close this


FSI Tool Window Cannot Load

Repro steps

Right click in an F# source code pane or try to launch FSI from the View menu or a toolbar button

When the menu or toolbar button is used that dialog box appears once
The dialog box appears twice (once again after you close the first) after every single right click
The right click menu can be used normally after both dialog popups have been closed.
Expected behavior
FSI Tool Window works
Known workarounds
Change VisualStudio.Shell package in packages.config to
  <package id="Microsoft.VisualStudio.Shell.15.0" version="15.0.26201" targetFramework="net46" />

Then the FSI tool window will actually open, but still doesn't work

After copying FSharp.Core.sigdata & FSharp.Core.opdata from
visualfsharp\release\net40\bin to
C:\Users\jared\AppData\Local\Microsoft\VisualStudio\15.0_adf57419FSharpDev\Extensions\Microsoft.VisualFSharpTools\Visual F# Tools\<IP_ADDRESS>
FSI works again

Related information
VS 2017 with VisualFSharpOpenSource.vsix built off of master @ b89d98e

FSI window working again as of 331dde6aa9e37930eed1bdf2dd81f8da8ac53790 at the least


The game ends abruptly sometimes

the ai didnt even have a chance to take a card

appears to be while() problem, gonna try and fix it

fixed with #4


Cleanup buildRustCrate expression

Motivation for this change
I am working on test support for buildRustCrate and as a prerequisite I started cleaning up the expression so it gets easier to grasp what is actually going on. Some reformatting, minor code changes, moved stuff around. The main part is probably the "simpler" buildPhase were we are no longer constructing a huge script from a huge file but have a file with common primitives that we are driving based on the current crate.
There is probably more stuff that we can cleanup and rework here but before this gets too big I'd like to land this.
I did successfully rebuild two of my larger private projects, carnix,  toml2nix & the entire buildRustCrateTests set.
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

Notify maintainers
cc @

@GrahamcOfBorg test buildRustCrateTests