Fix registers

add missing dot and slash registers - both as supported register names and as highlighted syntax tokens in the pop-up
fetch register contents before opening the pop-up window, so the contents of the % register are properly populated to the file name of the buffer the pop-up was launched from

Great idea. I have tested it and it works just fine.
One point: at the moment the / is still used as "search" in the peekup window. If we make it part of the registers then it will be included in the mapped keys, thereby giving raise, on press, to something like /^/ as per here.
Therefore we must decide what we want the / operator to do in the peekup window:

do we want to still keep it as "search" operator (so that the user can search whatever text in the registers if they do not remember where they put it)?
do we want to have it mapped as copying the corresponding register (as the other keys, in which case we must do some escaping in the mapping)?

Fair point. I'm not sure. I guess I'd like to use / for searching in the window, but have so far not yet actually done it.
Meanwhile, the second commit could stand on its own - all it does is it makes the % register visible and actionable upon.

I would also say that we can keep the / for searching, also because it is very unlikely that users want to paste the content of the last search. In any case if we have second thoughts we can just easily amend the line here - where I escape the * - by also escaping the /.
We can merge this as is for the moment then.

I have just now noticed two things though:

the % does not paste the register content, I am getting an error nothing contained in register ". This is most likely because % is an escape sequence in lua, so concatenating it does not actually concatenate anything (it should be something along the lines of %% I suspect)
the / is still there, I will remove it with a commit on master (please PlugUpdate afterwards).

the % does not paste the register content

If I use the keybind to paste before (or after), it does paste the contents of the % register before/after.
Rather, I don't see it added to the * (or whatever configuration - I added it to the z register) register. But it got pasted as expected.
Note from Vim's docs:

Read-only registers ":, ". and "%
These are '%', '#', ':' and '.'.  You can use them only with the "p", "P",
and ":put" commands and with CTRL-R.

Might it be the case that the code responsible for setting the * (or whatever) register to that value might not be using one of the methods which can be used for all registers, or maybe just for all but those?

In fact when I initially pulled your branch I tested with <leader>p/P and it did work fine. Now that you are mentioning the Vim docs I understand that the error is caused when, in the standard "" behaviour, the register is redirected to the default register with let @'.. ; it seems to be correct Vim behaviour that it does nothing then.
I do not think this is a big problem, it is a very marginal edge case that I suspect most users will even run into. I will give it some more thoughts and in the worst case scenario one can just mention in the docs that % can be used only in PasteBefore/After mode.


[docs-infra] Embed the Google package in writing-rules

Is it possible to embed the Google package in docs/writing-rules.zip?

Originally posted by @Janpot in https://github.com/mui/material-ui/pull/41176#discussion_r1496140006
Search keywords:

I tried in #41516. It's possible to embed them, but I then wasn't able to disable the rules, I gave up.


Support the creation of an events template for new relic developer events

As we're planning Nerd Days for October, Jemiah would like to get a couple landing pages added to the developer website. These pages will be used to register attendees and promote the event.  It’s been suggested that a template is created for this page type so it’s reusable.
Considerations

Jemiah is working with Daniel G on the implementation.
These event pages would exist under the new Attend events side navigation
The DevEx Team would just provide PR support and merging of code.

@danielgolden  and @jaesius were working on this for nerd days...

A table component for listing talks within an event would be awesome! We don't currently have a table component to my knowledge.

@jaesius did the first events page and committed that on #640 he is also going to refactor this later to add reusable components for events.


How to specify custom parameters for initrd?

Hi,
I would like to add the isolcpus parameter on my C2M machines, for improved performance.
What is the way to do it on Scaleway? Support told me to ask here.

It isn't in the code yet but they can add it via the tags of your server (just like they do it for kexec)

However https://github.com/scaleway/initrd might be a better place

@meyskens Thank you, any bit of docs or code so that I can understand what kind of tags should I put on the server?

https://github.com/scaleway/initrd/tree/master/Linux#boot-options which is executed at https://github.com/scaleway/initrd/blob/master/Linux/tree-common/init


pull request for e2e test at 11/13/2016 04:15:09

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

Details

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


🐛 Manual install doesnt pick options from config file

Kairos version:
master
CPU architecture, OS, and Version:
all
Describe the bug
When using a config file and doing manual install kairos-agent manual-install CONFIG supposedly there is an options key in the config that should be passed down to the installer.
Unfortunately this does not work as it uses a different path, so it loads the file and dumps it into option["cc"] and there is nothing to merge those options into the config properly.
An example of how its merged during a normal install is in https://github.com/kairos-io/kairos/blob/master/internal/agent/install.go#L85
To Reproduce
create config file with options, call kairos-agent manual-install CONFIG
Expected behavior

Options are respected and passed down
Logs

Additional context

@Itxaka did you mean that we should merge the options sections like in here:
https://github.com/kairos-io/kairos/blob/94175ca992948c13b039d4a863e84a09a61bdb54/internal/agent/install.go#L102
Indeed, it seems that this function mergeOption is called a few times before we call when running Install:
https://github.com/kairos-io/kairos/blob/94175ca992948c13b039d4a863e84a09a61bdb54/internal/agent/install.go#L237
When running ManualInstall we proceed to RunInstall(options) without running this merge.
https://github.com/kairos-io/kairos/blob/94175ca992948c13b039d4a863e84a09a61bdb54/internal/agent/install.go#L88

@Itxaka did you mean that we should merge the options sections like in here:
https://github.com/kairos-io/kairos/blob/94175ca992948c13b039d4a863e84a09a61bdb54/internal/agent/install.go#L102
Indeed, it seems that this function mergeOption is called a few times before we call when running Install:
https://github.com/kairos-io/kairos/blob/94175ca992948c13b039d4a863e84a09a61bdb54/internal/agent/install.go#L237
When running ManualInstall we proceed to RunInstall(options) without running this merge.
https://github.com/kairos-io/kairos/blob/94175ca992948c13b039d4a863e84a09a61bdb54/internal/agent/install.go#L88

Yep! Otherwise we lose options due to not merging properly


Allow to use a pre-created GitHub release

The autogenerated release notes may not always be descriptive and user-friendly enough. Especially for minor and major releases. As a package maintainer, I want to be able to fine-tune the text that is generated by the bot before it becomes the content of the git tag and is published on GitHub.
There are two approaches that come to mind:

Instead of creating a GitHub release unconditionally, the bot looks up a release draft based on the tag and uses it if it exists.
The release is done in stages: 1) The release notes are drafted; 2) The notes are edited and approved; 3) The process continues.

Seems unnecessary: current release is generated taking milestone description and issues/PRs, and the release can be edited later anyway.


Delete projects with delete institution

There is no way to access a project if its institution is deleted, so delete it also.

Shouldn't we also be setting availability = "archived"? Do we still have an archived field in this table?
--- The only column is "archived" for institutions.


Nothing is returned when window is closed using the button in the upper left corner

filesystem_picker just closes the window (pop()) without  invoking the completer.

@schwenkreis This is as it should be, this button works like "Cancel".

@schwenkreis This is as it should be, this button works like "Cancel".

Well, the problem is that if you are using the approach of your example:
String path = await FilesystemPicker.open(
title: 'Open file',
context: context,
rootDirectory: rootPath,
fsType: FilesystemType.file,
folderIconColor: Colors.teal,
allowedExtensions: ['.txt'],
fileTileSelectMode: FileTileSelectMode.wholeTile,
);
, then it will never return because the Future is never fulfilled.
Can you please let me know how the caller should know that the oicker was closed? Furthermore, there is still an open thread waiting ...
Cheers
Friedemann

Well, the problem is that if you are using the approach of your example:
String path = await FilesystemPicker.open(
title: 'Open file',
context: context,
rootDirectory: rootPath,
fsType: FilesystemType.file,
folderIconColor: Colors.teal,
allowedExtensions: ['.txt'],
fileTileSelectMode: FileTileSelectMode.wholeTile,
);
, then it will never return because the Future is never fulfilled.
Can you please let me know how the caller should know that the oicker was closed? Furthermore, there is still an open thread waiting ...
Cheers
Friedemann

Well, the problem is, that if you are using the approach of your example:
String path = await FilesystemPicker.open(
title: 'Open file',
context: context,
rootDirectory: rootPath,
fsType: FilesystemType.file,
folderIconColor: Colors.teal,
allowedExtensions: ['.txt'],
fileTileSelectMode: FileTileSelectMode.wholeTile,
);
, then it will never return because the Future is never fulfilled.
Can you please let me know how the caller should know that the picker was closed? Furthermore, there is still an open thread waiting ...
Cheers
Friedemann

I understand what you are talking about: FilesystemPicker.open should return null if the user just closed the Picker screen. I will make improvements in the near future.

Well, the problem is, that if you are using the approach of your example:
String path = await FilesystemPicker.open(
title: 'Open file',
context: context,
rootDirectory: rootPath,
fsType: FilesystemType.file,
folderIconColor: Colors.teal,
allowedExtensions: ['.txt'],
fileTileSelectMode: FileTileSelectMode.wholeTile,
);
, then it will never return because the Future is never fulfilled.
Can you please let me know how the caller should know that the picker was closed? Furthermore, there is still an open thread waiting ...
Cheers
Friedemann

I understand what you are talking about: FilesystemPicker.open should return null if the user just closed the Picker screen. I will make improvements in the near future.

@schwenkreis I fixed this bug, now when the user tap on the Cancel button or press the Back button on the device FilesystemPicker.open returns null.

@schwenkreis I fixed this bug, now when the user tap on the Cancel button or press the Back button on the device FilesystemPicker.open returns null.

Fantatstic! Thanks a lot for the support!

Fantatstic! Thanks a lot for the support!


fix: specify type declaration file more precisely

(In another project) rollup struggled to recognise the types for defu without this change.

Thanks


[Bug]: Unit test "[keyboard.spec] Keyboard should report multiple modifiers" should not use legacy properties of key events

Minimal, reproducible example
See details in the background section for the affected Puppeteer unit test.

Error string
Expected: "Keydown: ; Semicolon 186 [Alt Control]"\nReceived: "Keydown: ; Semicolon 59 [Alt Control]\
Bug behavior

[ ] Flaky
[ ] PDF

Background
The mentioned test uses legacy properties for key events which are not standardized and differ between browsers. Those properties are .which and .charCode:
https://github.com/puppeteer/puppeteer/blob/d98f488a514ff9b3bb06923b4fb2d9bfb5919cec/test/src/keyboard.spec.ts#L257-L298
https://github.com/puppeteer/puppeteer/blob/d98f488a514ff9b3bb06923b4fb2d9bfb5919cec/test/assets/input/keyboard.html#L12-L20
The test should be changed to only use standardized properties like .key, .code and maybe .data to verify that the right keys were pressed.
https://dvcs.w3.org/hg/d4e/raw-file/tip/key-event-test.html is a good help here.
@OrKoN can you please have a look? Thanks!
Expectation
Test has to pass in Firefox as well and not fail because legacy properties are used which on purpose are different between browsers.
Reality
The test fails because of inappropriate checks.
Puppeteer configuration file (if used)
No response
Puppeteer version
latest
Node version
latest
Package manager
npm
Package manager version
latest
Operating system
macOS

@jrandolf PTAL

@jrandolf thanks a lot!


Installing Java 17 instead of Java 8

Since Java 8 is no more compatible with Jenkins since version 2.361.1 (see jenkins docs), so there is no more reason to install it in the image.
Instead, since the same version (see jenkins docs), Jenkins supports Java 17, so it makes sense to install it in the image so that early adopters can already try it.

We can add Java 17 probably, but we can not remove Java 8 yet. There are some users which may still use Java 8 in their jobs so we want it to continue to be available.

We can add Java 17 probably, but we can not remove Java 8 yet. There are some users which may still use Java 8 in their jobs so we want it to continue to be available.

I'm not sure how many people are going to use it. Consider that by default the execution of jobs in master node is de facto disable (configured with 0 executors) and in general is discouraged (see jenkins docs).

I believe that in our images that is not disabled by default yet.

I believe that in our images that is not disabled by default yet.

You're actually right. I checked and the built-in node is not disabled by default, it is used if it is the only node that you have.
So, the only case in which you could benefit having Java 8 is the case in which you don't have any external node or k8s integration and you need to run a specific job that can only run on Java 8. Given that, I think it is safe to drop it.
If you don't think so I will put it back in the PR.

/close


"Binary arithmetic operators" table in "<IP_ADDRESS> PCEP-30-02 Practice Test Compendium – Operators" not correctly presented

[x] 1 cell is missing before the - operator
[x] Unable to merge cells under "Highest" and "Lowest"

No button to merge cells in GitBook
Align cells to the right

No button to merge cells in GitBook
Align cells to the right


Add section to README for troubleshooting installation

The instructions in https://github.com/SwiftDocOrg/swift-doc/issues/211#issuecomment-843997618 are generally useful, and should be added to the README.

I can take this — it's the least I can do to thank you for your help!


Missing cleanup step in the telemetry task.

https://preliminary.istio.io/docs/tasks/telemetry/metrics-logs/
This page starts a port-forwarder for accessing Prometheus, but does not instruct to clean it up in the cleanup stage.

Ditto for https://preliminary.istio.io/docs/tasks/telemetry/distributed-tracing/
(Correct example: https://preliminary.istio.io/docs/tasks/telemetry/querying-metrics/ )

Issue moved to istio/istio.github.io #1842 via ZenHub


Add TokenScript build agent

This PR adds a TS deployment agent. The new features are:

Know how to handle generated .xml and .tsml files (deploy tokenscript).
Add more build toasts to 'deploy with wallet' page.

TODO:

Scroll to completed TS on completion (doesn't work).
Prevent W3GPT from generating the TokenScript before it's deployed the contract (it doesn't yet know the contract address - one possible solution would be to predict the contract address using ethers.js calc, but it would be better to solve this internally).
Compile the contract on generation and provide feedback to the service to re-build if necessary, using the compiler error.
Validate the TokenScript using the TokenScript CLI module.

In order for Vercel to build you require the new environment var


patch: Adding get secret by name

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


Make RRTMGP inherit float type

This PR makes RRTMGP inherit the given float type, so that RRTMGP can run with Float32.

Superseded by #2704.


Contact form

I  make Name field accepts up to 30 chars.
I make Email field accepts only emails.
I make Message field accepts up to 500 chars.
I make  All fields have placeholder text.
I make All fields have the correct type.
I Collect data by using the Formspree service.
I update style file
I update HTML file

Hello @malodev1234 👋,
This is an additional review as a result of the second opinion request.
Important: Please, always ensure that you implement all changes requested by a reviewer before seeking another review to preserve your remaining review requests on your dashboard.
Review Requests:

The 'Get in touch' button does not match the design from Figma. The background color should be white, and the font color should be blue. Please use the exact colors provided in the Figma design.
Great job on removing the extra space from the bottom. However, the design still does not fit the mobile screen size, and the get in touch is not displayed, especially at 376px width * 667px height (71%). Please examine your design on different mobile screen sizes using dev tools and make the necessary adjustments to ensure it fits all screens.

Keep rocking 🚀!


Re-enable static builds

Static option seems to have been removed, though cmake's built-in BUILD_SHARED_LIBS controls both add_library and DEFINE_SYMBOL , so it's easy to enable while keeping the current behaviour.

Also needs Qt5Network in the pkg-config file - all working for me with static and shared builds.

Thanks for getting this working again.


Try to fix flaky VertxServerTest

What does this PR do?
Try to fix VertxServerTest by letting VertX choose a random port
Checklist

[x] This is something else

[ ] I have updated CHANGELOG.asciidoc

:grey_exclamation: Build Aborted

The PR is not allowed to run in the CI yet

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Reason: The PR is not allowed to run in the CI yet

Start Time: 2021-12-21T08:46:33.857+0000

Duration: 3 min 29 sec

Commit: 57dd4677e6c3282d007fa32fdd20838e17bdc8de

:robot: GitHub comments
To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

run benchmark tests : Run the benchmark test.

run compatibility tests : Run the JDK Compatibility test.

run integration tests : Run the APM-ITs.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@eyalkoren Would you mind running the tests again?

@tobiasstadler it looks good, I believe this failure is related to #2354
@Mergifyio update

@eyalkoren Would you please run the /test and run elasticsearch-ci/docs

/test

run elasticsearch-ci/docs

Thank You!

Error processing tar file(exit status 1): write /var/cache/debconf/templates.dat-old: no space left on device
	at co.elastic.apm.servlet.PayaraIT.<init>(PayaraIT.java:37)

:cry:

@Mergifyio update
/test

/test

It finally passed the tests. Would you please merge it?

Thank You!


D&D sounds not playing

When I test sound files on my test world, generic sound files work as intended, but D&D sound files do not play at all.

Hi! I have couple of questions:

What version of the module are you running?
What version of Foundry?
What steps did you exactly do
Are there any errors in the console?

Hi! I have couple of questions:

What version of the module are you running?  0.4.0
What version of Foundry?  V10 - Build 291
What steps did you exactly do?  Installed the module, added the authentication code to the settings, drag and droped a Curse of Strahd sound file to a scene.  Put a token next to the sound area.  Increased computer volume.  Drag and dropped a non-Curse of Strahd sound file, moved token to that sound file.  Heard the sound perfectly.
Are there any errors in the console?  None that I could see.

So I did notice a way to make Curse of Strahd sound files work with a token nearby.  Under the ambient sound controls tab on the left side of the screen, if I have Preview Ambient Sounds enabled it will work, but only when I'm on that screen.
I currently use 2 monitors, and when I switch focus to a different monitor, the sound file stops, regardless of where the token is on the scene.

A new problem has emerged.  I've told the sound file to stop playing, but it's on a loop, and won't stop.

So I did notice a way to make Curse of Strahd sound files work with a token nearby. Under the ambient sound controls tab on the left side of the screen, if I have Preview Ambient Sounds enabled it will work, but only when I'm on that screen.
I currently use 2 monitors, and when I switch focus to a different monitor, the sound file stops, regardless of where the token is on the scene.

Hmm, that needs to be clarified for me.
When you try with an ambient sound created by this module and without "Preview Ambient Sound" enabled, you do not hear the sound even though the toker is in the range of the ambient sound and the token itself is selected?
When triggered via the playlist tab, can you hear a sound (for example, this Curse of Strahd mood)? (I want to exclude the case when the user does not hear syrinscape audio).

Not sure if this is related. But I installed the module and added it to a Starfinder campaign. Selecting sound sets was fine, and they list them but if I play any the drop-down does not and the play button is just the stop button. No progress no time nothing to show it is playing. Which it isn't.
See image.

Is it supposed to cache the files before playing them? In which case does it matter how many sound sets you select?

@develroo If you open the syrinscape online player in a separate tab, does it play the sound when you click the "play" button in the foundry?
Let's check if SyrinControl is sending commands to the Sysrinscape and it's just an audio playback that doesn't work, or perhaps everything is not working in your case.

Also, note that sound doesn't play right away when the audio context is still not acquired. There is a separate #76 for that.

Well, I am just adding it to the sounds playlist and seeing if it plays. Do we have to add a sound context for each sound? Does that mean all one shot sounds have to be a macro?
I have just opened a tab as you suggested and yes it will play in the browser, however I just noticed there is a big difference between the sound sets and the list. Is the sound set supposed to expand to all the sounds in that set because looking at the Syrinscape panel it lists lots of individual sounds for one 'scene' See below how the 'Docking Station' looks.

Am I misunderstanding how this should work?

Well, I am just adding it to the sounds playlist and seeing if it plays. Do we have to add a sound context for each sound? Does that mean all one shot sounds have to be a macro?

What do you mean by "add a sound context for each sound"?
What I meant by writing "when the audio context is still not acquired." is:
Foundry VTT is not going to play any sound until you click and move mouse - interact with the web page. Because otherwise, modern browsers would simply block audio, because auto-playback in WWW is considered harmful. Therefore there has to be "some" interaction before getting sound.
Now in your case we can exclude this case, since well... you clicked the play button in Foundrys VTT sidebar. Therefore, there should be a sound.
It goes like this:

You click "play" button
SyrinControl sends an API request to SyrinScape "please play mood 123".
Meanwhile SyrinControl (independly) connects to the Syrinscape as listener, and SyrinScape should orchestrate Foundry: "Play 123". It's done in that way, because under the hood Syrinscape commands more complex logic - each mood in the soundset is a ... set of elements played in some sequence and some in parallel. And each elements is actually a list of different sound samples that can be looped or played randomly (therefore each time you hear a mood it doesn't sound exactly the same, its not getting boring).

I have just opened a tab as you suggested and yes it will play in the browser,

But have you triggered the mood from the foundry or from the new tab?

however I just noticed there is a big difference between the sound sets and the list. Is the sound set supposed to expand to all the sounds in that set because looking at the Syrinscape panel it lists lots of individual sounds for one 'scene' See below how the 'Docking Station' looks.

Am I misunderstanding how this should work?

Kinda. Yes.
Let me explain:

Based on your comment only sections A, B and C are available from SyrinControl. Section D is unavailable.
A and C - you can access it currently by going into "Import Soundsets" and clicking drum icon - https://github.com/frondeus/fvtt-syrin-control/wiki/How-To-Use#how-to-play-oneshot
now B is the "mood" - the playlist sound that you import from Syrinscape into the Foundry.

Ahh, yes that was my bad it was the wrong screenshot, sorry. But now you explained it, I am thinking I made a very silly mistake, in so much that I forgot to say  I am running Fvtt stand alone and so there is no link (and I don't know if I can make one ) between Syrinscape and my custom Fvtt instance.
If that is the case, I apologise, and you can feel free to delete all my comments as I am obviously misunderstood how it worked and should not be adding to this topic.


FE-142: update indices view list & index addition to React

Scope & Purpose
Replaces the backbone indices view list with React

[x] :pizza: New feature

Checklist

[x] Tests

[x] Manually tested

[ ] :book: CHANGELOG entry made

Related Information
(Please reference tickets / specification / other PRs etc)

[x] GitHub issue / Jira ticket: https://arangodb.atlassian.net/browse/FE-142

[ ] https://jenkins01.arangodb.biz/job/arangodb-ANY-jslint/27803/


Laravel migration with more than one timestamp column

"laravel/framework": '8.69.0'
PHP 8.0.11 (cli) (built: Sep 23 2021 21:26:24) ( NTS )
mysql  Ver 15.1 Distrib 10.6.4-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2
Description:
im trying to run this code for migration :
            Schema::create('something', function (Blueprint $table) {
                $table->timestamp('a');
                $table->timestamp('b');
                $table->timestamp('c');
            });

And I get this error message :

SQLSTATE[42000]: Syntax error or access violation: 1067 Invalid default value for 'b' (SQL: create table something (a timestamp not null, b timestamp not null, c timestamp not null) default character set utf8mb4 collate 'utf8mb4_unicode_ci')

but when I copy the generated SQL code and run it mysql app there is no problem and it works
Exactly the same thing is explained in this link : https://www.buzzphp.com/posts/laravel-error-in-creating-a-table-with-two-timestamp-columns
Steps To Reproduce:
1- make a migration with more than one timestamp column ( $table->timestamp('a'); )
2-migrate

you need to set a default value or make the columns nullable


Created ValidSquare.java file

This .java file contains the solution of LeetCode problem Valid Square.

Please review my pull request.

@MitadruDatta
Don't worry it will be approved soon as you may know their are a lot PR's right now and also it's a one month program so don't worry it will be approved as soon as possible also I can't merge all PR's blindly as it may result in the repo being excluded from the program like many other repo so be patient full you PR will be accepted soon. Happy Hactoberfest


derive PanicDestruct

This change is

Current dependencies on/for this PR:

main

PR #3232

PR #3233

PR #3234   👈

This comment was auto-generated by Graphite.


[BUG] Error removing auto-discovered containers resulting in all further docker events being ignored

I am regularly seeing errors during the handling of container removal events which then leads to no further docker events being processed (e.g. no logs are gathered for new containers) until the dd agent is restarted.
Agent Environment
Example logs around the error:
2023-01-19 11:49:00 GMT | CORE | INFO | (pkg/serializer/serializer.go:403 in sendMetadata) | Sent metadata payload, size (raw/compressed): 1797/598 bytes.
2023-01-19 11:49:00 GMT | CORE | INFO | (pkg/serializer/serializer.go:427 in SendProcessesMetadata) | Sent processes metadata payload, size: 1461 bytes.
2023-01-19 11:52:08 GMT | CORE | INFO | (pkg/collector/scheduler/scheduler.go:131 in Cancel) | Unscheduling check php_fpm:a2bc89b13d85861a
2023-01-19 11:52:08 GMT | CORE | INFO | (pkg/logs/schedulers/ad/scheduler.go:113 in Unschedule) | New source to remove: entity: docker://aa927fcfaee11e4d3246c4ebb47b6eeddc9b790188fd19af360f608697038698
2023-01-19 11:52:08 GMT | CORE | INFO | (pkg/autodiscovery/config_poller.go:105 in stream) | kubernetes-container-allinone provider: collected 0 new configurations, removed 3
2023-01-19 11:52:08 GMT | CORE | INFO | (pkg/serializer/serializer.go:403 in sendMetadata) | Sent metadata payload, size (raw/compressed): 4507/1216 bytes.
2023-01-19 11:52:08 GMT | CORE | INFO | (pkg/autodiscovery/config_poller.go:105 in stream) | kubernetes-container-allinone provider: collected 0 new configurations, removed 3
2023-01-19 11:52:09 GMT | CORE | WARN | (pkg/logs/internal/tailers/docker/tailer.go:181 in tryRestartReader) | Could not restart the docker reader for container aa927fcfaee1: Error: No such container: aa927fcfaee11e4d3246c4ebb47b6eeddc9b790188fd19af360f608697038698:
2023-01-19 11:52:09 GMT | CORE | INFO | (pkg/logs/internal/tailers/docker/tailer.go:108 in Stop) | Stop tailing container: aa927fcfaee1
2023-01-19 11:52:09 GMT | CORE | WARN | (pkg/logs/internal/tailers/docker/tailer.go:181 in tryRestartReader) | Could not restart the docker reader for container 3850f4b91c96: Error: No such container: 3850f4b91c96560f93ce4848a4bd4d39722ebc7e1799eb8ea7a19e8cdd5cbee8:
2023-01-19 11:52:09 GMT | CORE | INFO | (pkg/logs/internal/tailers/docker/tailer.go:108 in Stop) | Stop tailing container: 3850f4b91c96
2023-01-19 11:52:11 GMT | CORE | WARN | (pkg/workloadmeta/store.go:564 in notifyChannel) | collector ""ad-kubecontainerprovider"" did not close the event bundle channel in time, continuing with downstream collectors. bundle dump: {Events:[{Type:1 Entity:0xc002186180}] Ch:0xc001ed81e0}
2023-01-19 11:52:12 GMT | CORE | WARN | (pkg/workloadmeta/store.go:564 in notifyChannel) | collector ""ad-containerlistener"" did not close the event bundle channel in time, continuing with downstream collectors. bundle dump: {Events:[{Type:1 Entity:0xc002186000}] Ch:0xc003b3b200}
2023-01-19 11:52:18 GMT | CORE | WARN | (pkg/collector/python/datadog_agent.go:125 in LogMessage) | apache:d914e6062fc24d91 | (apache.py:94) | Caught exception HTTPConnectionPool(host='<IP_ADDRESS>', port=26869): Max retries exceeded with url: /server-status?auto (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f8eb036e970>: Failed to establish a new connection: [Errno 111] Connection refused'))
2023-01-19 11:52:18 GMT | CORE | ERROR | (pkg/collector/worker/check_logger.go:69 in Error) | check:apache | Error running check: [{""message"": ""HTTPConnectionPool(host='<IP_ADDRESS>', port=26869): Max retries exceeded with url: /server-status?auto (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f8eb036e970>: Failed to establish a new connection: [Errno 111] Connection refused'))...<<traceback truncated>>
2023-01-19 11:52:30 GMT | CORE | WARN | (pkg/workloadmeta/store.go:564 in notifyChannel) | collector ""ad-kubecontainerprovider"" did not close the event bundle channel in time, continuing with downstream collectors. bundle dump: {Events:[{Type:1 Entity:0xc002186600}] Ch:0xc000180de0}
2023-01-19 11:52:33 GMT | CORE | WARN | (pkg/collector/python/datadog_agent.go:125 in LogMessage) | apache:d914e6062fc24d91 | (apache.py:94) | Caught exception HTTPConnectionPool(host='<IP_ADDRESS>', port=26869): Max retries exceeded with url: /server-status?auto (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f8eb0393a90>: Failed to establish a new connection: [Errno 111] Connection refused'))

Version:
Agent 7.41.1 - Commit: 4f39b9e - Serialization version: v5.0.39 - Go version: go1.18.9

Status:
===============
Agent (v7.41.1)
===============

  Status date: 2023-01-19 16:12:50.588 GMT<PHONE_NUMBER>588)
  Agent start: 2023-01-19 15:40:50.638 GMT<PHONE_NUMBER>638)
  Pid: 368357
  Go Version: go1.18.9
  Python Version: 3.8.14
  Build arch: amd64
  Agent flavor: agent
  Check Runners: 4
  Log Level: info

  Paths
  =====
    Config File: /etc/datadog-agent/datadog.yaml
    conf.d: /etc/datadog-agent/conf.d
    checks.d: /etc/datadog-agent/checks.d

  Clocks
  ======
    NTP offset: -3.138ms
    System time: 2023-01-19 16:12:50.588 GMT<PHONE_NUMBER>588)

  Host Info
  =========
    bootTime: 2022-12-13 17:24:08 GMT<PHONE_NUMBER>000)
    hostId: d672a673-e745-4673-aee9-776136130a78
    kernelArch: x86_64
    kernelVersion: 5.4.0-135-generic
    os: linux
    platform: ubuntu
    platformFamily: debian
    platformVersion: 20.04
    procs: 608
    uptime: 886h16m54s

  Hostnames
  =========
    hostname: copper
    socket-fqdn: localhost
    socket-hostname: copper
    hostname provider: os
    unused hostname providers:
      'hostname' configuration/environment: hostname is empty
      'hostname_file' configuration/environment: 'hostname_file' configuration is not enabled
      aws: not retrieving hostname from AWS: the host is not an ECS instance and other providers already retrieve non-default hostnames
      azure: azure_hostname_style is set to 'os'
      container: the agent is not containerized
      fargate: agent is not runnning on Fargate
      fqdn: 'hostname_fqdn' configuration is not enabled
      gce: unable to retrieve hostname from GCE: GCE metadata API error: Get "http://<IP_ADDRESS>/computeMetadata/v1/instance/hostname": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

  Metadata
  ========
    agent_version: 7.41.1
    config_apm_dd_url:
    config_dd_url:
    config_logs_dd_url:
    config_logs_socks5_proxy_address:
    config_no_proxy: []
    config_process_dd_url:
    config_proxy_http:
    config_proxy_https:
    config_site:
    feature_apm_enabled: true
    feature_cspm_enabled: false
    feature_cws_enabled: false
    feature_logs_enabled: true
    feature_networks_enabled: true
    feature_networks_http_enabled: false
    feature_networks_https_enabled: false
    feature_otlp_enabled: false
    feature_process_enabled: true
    feature_processes_container_enabled: false
    flavor: agent
    hostname_source: os
    install_method_installer_version: datadog_formula-3.4
    install_method_tool: saltstack
    install_method_tool_version: saltstack-3005.1
    logs_transport: HTTP

=========
Collector
=========

  Running Checks
  ==============

    apache (4.2.0)
    --------------
      Instance ID: apache:38fee1db768862ab [OK]
      Configuration Source: container:docker://bbbc5a6d6df8d2a4b87af0a84b06a3cbbb2dcd88d625166ebc2fdf9029a763fa
      Total Runs: 128
      Metric Samples: Last Run: 21, Total: 2,688
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 1, Total: 128
      Average Execution Time : 6ms
      Last Execution Date : 2023-01-19 16:12:50 GMT<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-01-19 16:12:50 GMT<PHONE_NUMBER>000)
      metadata:
        version.major: 2
        version.minor: 4
        version.patch: 54
        version.raw: 2.4.54
        version.scheme: semver

      Instance ID: apache:4bfc7359ef2e5faa [OK]
      Configuration Source: container:docker://030df0dc14386862bdf704e7f2ae554a4807ebaca2b12f587fb4b0fbe7a90dd4
      Total Runs: 127
      Metric Samples: Last Run: 21, Total: 2,667
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 1, Total: 127
      Average Execution Time : 6ms
      Last Execution Date : 2023-01-19 16:12:40 GMT<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-01-19 16:12:40 GMT<PHONE_NUMBER>000)
      metadata:
        version.major: 2
        version.minor: 4
        version.patch: 54
        version.raw: 2.4.54
        version.scheme: semver

      Instance ID: apache:78f10fbd4b35429 [OK]
      Configuration Source: container:docker://34b9a7f741057296e39a3fc66284e17949943183941636e964b54d9243073da0
      Total Runs: 127
      Metric Samples: Last Run: 21, Total: 2,667
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 1, Total: 127
      Average Execution Time : 7ms
      Last Execution Date : 2023-01-19 16:12:38 GMT<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-01-19 16:12:38 GMT<PHONE_NUMBER>000)
      metadata:
        version.major: 2
        version.minor: 4
        version.patch: 54
        version.raw: 2.4.54
        version.scheme: semver

      Instance ID: apache:8af428de6c2145ba [OK]
      Configuration Source: container:docker://f6d9448e8e2e29867654d0cf7bb72468112e2b6a87302fef0e8d7bcd1018138b
      Total Runs: 128
      Metric Samples: Last Run: 21, Total: 2,688
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 1, Total: 128
      Average Execution Time : 6ms
      Last Execution Date : 2023-01-19 16:12:41 GMT<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-01-19 16:12:41 GMT<PHONE_NUMBER>000)
      metadata:
        version.major: 2
        version.minor: 4
        version.patch: 55
        version.raw: 2.4.55
        version.scheme: semver

      Instance ID: apache:b8da6b4ad6cab67a [OK]
      Configuration Source: container:docker://e9aaea3b36d3b88bb54e761868c3f2aae17f689d6e7b9317cb8a27b502b7db58
      Total Runs: 128
      Metric Samples: Last Run: 21, Total: 2,688
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 1, Total: 128
      Average Execution Time : 5ms
      Last Execution Date : 2023-01-19 16:12:42 GMT<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-01-19 16:12:42 GMT<PHONE_NUMBER>000)
      metadata:
        version.major: 2
        version.minor: 4
        version.patch: 54
        version.raw: 2.4.54
        version.scheme: semver

      Instance ID: apache:cb5ee39a3560a785 [OK]
      Configuration Source: container:docker://ecadd0b3743f23aa43be3d17a00ffd0eb49a316a4970763cad222a64b7651e55
      Total Runs: 128
      Metric Samples: Last Run: 21, Total: 2,688
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 1, Total: 128
      Average Execution Time : 6ms
      Last Execution Date : 2023-01-19 16:12:49 GMT<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-01-19 16:12:49 GMT<PHONE_NUMBER>000)
      metadata:
        version.major: 2
        version.minor: 4
        version.patch: 54
        version.raw: 2.4.54
        version.scheme: semver

      Instance ID: apache:dc7a5e672221ab [OK]
      Configuration Source: container:docker://b2c4b275a48cd61699acdf87241d07c938034fdb3852190dea96cd6d62b09c29
      Total Runs: 128
      Metric Samples: Last Run: 21, Total: 2,688
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 1, Total: 128
      Average Execution Time : 6ms
      Last Execution Date : 2023-01-19 16:12:43 GMT<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-01-19 16:12:43 GMT<PHONE_NUMBER>000)
      metadata:
        version.major: 2
        version.minor: 4
        version.patch: 43
        version.raw: 2.4.43
        version.scheme: semver

      Instance ID: apache:eeaaba4a4fb3840a [OK]
      Configuration Source: container:docker://0b7a7782ba6e2989a6a2730c8a979323f31871f05bc16086f056365996d15958
      Total Runs: 127
      Metric Samples: Last Run: 21, Total: 2,667
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 1, Total: 127
      Average Execution Time : 8ms
      Last Execution Date : 2023-01-19 16:12:39 GMT<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-01-19 16:12:39 GMT<PHONE_NUMBER>000)
      metadata:
        version.major: 2
        version.minor: 4
        version.patch: 54
        version.raw: 2.4.54
        version.scheme: semver

    consul (2.2.0)
    --------------
      Instance ID: consul:de4f5e752738aae4 [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/consul.d/conf.yaml
      Total Runs: 128
      Metric Samples: Last Run: 71, Total: 9,155
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 3, Total: 391
      Average Execution Time : 41ms
      Last Execution Date : 2023-01-19 16:12:39 GMT<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-01-19 16:12:39 GMT<PHONE_NUMBER>000)
      metadata:
        version.major: 1
        version.minor: 14
        version.patch: 2
        version.raw: 1.14.2
        version.scheme: semver

    container
    ---------
      Instance ID: container [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/container.d/conf.yaml.default
      Total Runs: 127
      Metric Samples: Last Run: 832, Total: 105,664
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 32ms
      Last Execution Date : 2023-01-19 16:12:38 GMT<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-01-19 16:12:38 GMT<PHONE_NUMBER>000)

    containerd
    ----------
      Instance ID: containerd [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/containerd.d/conf.yaml.default
      Total Runs: 128
      Metric Samples: Last Run: 0, Total: 0
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2023-01-19 16:12:45 GMT<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-01-19 16:12:45 GMT<PHONE_NUMBER>000)

    cpu
    ---
      Instance ID: cpu [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/cpu.d/conf.yaml.default
      Total Runs: 127
      Metric Samples: Last Run: 9, Total: 1,136
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2023-01-19 16:12:37 GMT<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-01-19 16:12:37 GMT<PHONE_NUMBER>000)

    disk (4.7.1)
    ------------
      Instance ID: disk:be54d36a859b42e8 [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/disk.d/conf.yaml
      Total Runs: 128
      Metric Samples: Last Run: 72, Total: 9,216
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 12ms
      Last Execution Date : 2023-01-19 16:12:46 GMT<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-01-19 16:12:46 GMT<PHONE_NUMBER>000)

    docker
    ------
      Instance ID: docker [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/docker.d/conf.yaml.default
      Total Runs: 128
      Metric Samples: Last Run: 99, Total: 12,672
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 1, Total: 128
      Average Execution Time : 119ms
      Last Execution Date : 2023-01-19 16:12:44 GMT<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-01-19 16:12:44 GMT<PHONE_NUMBER>000)

    file_handle
    -----------
      Instance ID: file_handle [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/file_handle.d/conf.yaml.default
      Total Runs: 127
      Metric Samples: Last Run: 5, Total: 635
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2023-01-19 16:12:36 GMT<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-01-19 16:12:36 GMT<PHONE_NUMBER>000)

    io
    --
      Instance ID: io [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/io.d/conf.yaml.default
      Total Runs: 128
      Metric Samples: Last Run: 67, Total: 8,531
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 1ms
      Last Execution Date : 2023-01-19 16:12:43 GMT<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-01-19 16:12:43 GMT<PHONE_NUMBER>000)

    load
    ----
      Instance ID: load [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/load.d/conf.yaml.default
      Total Runs: 128
      Metric Samples: Last Run: 6, Total: 768
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2023-01-19 16:12:50 GMT<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-01-19 16:12:50 GMT<PHONE_NUMBER>000)

    memory
    ------
      Instance ID: memory [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/memory.d/conf.yaml.default
      Total Runs: 128
      Metric Samples: Last Run: 20, Total: 2,560
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2023-01-19 16:12:42 GMT<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-01-19 16:12:42 GMT<PHONE_NUMBER>000)

    network (2.9.2)
    ---------------
      Instance ID: network:d884b5186b651429 [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/network.d/conf.yaml.default
      Total Runs: 128
      Metric Samples: Last Run: 350, Total: 44,800
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 20ms
      Last Execution Date : 2023-01-19 16:12:49 GMT<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-01-19 16:12:49 GMT<PHONE_NUMBER>000)

    ntp
    ---
      Instance ID: ntp:d884b5186b651429 [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/ntp.d/conf.yaml.default
      Total Runs: 3
      Metric Samples: Last Run: 1, Total: 3
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 1, Total: 3
      Average Execution Time : 115ms
      Last Execution Date : 2023-01-19 16:10:56 GMT<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-01-19 16:10:56 GMT<PHONE_NUMBER>000)

    php_fpm (2.2.0)
    ---------------
      Instance ID: php_fpm:119913f20264ee70 [OK]
      Configuration Source: container:docker://8e3f1302b6fc41ca74d05d9b36b957c1ff83fdc2ddc742f773070dfd21f77134
      Total Runs: 128
      Metric Samples: Last Run: 7, Total: 896
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 1, Total: 128
      Average Execution Time : 5ms
      Last Execution Date : 2023-01-19 16:12:44 GMT<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-01-19 16:12:44 GMT<PHONE_NUMBER>000)

      Instance ID: php_fpm:67ff78c127f3d689 [OK]
      Configuration Source: container:docker://4572db2bfa9b422ebb14c85ec36986f229c209fdb783c8f29ee33453424dcf5b
      Total Runs: 128
      Metric Samples: Last Run: 7, Total: 896
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 1, Total: 128
      Average Execution Time : 4ms
      Last Execution Date : 2023-01-19 16:12:45 GMT<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-01-19 16:12:45 GMT<PHONE_NUMBER>000)

      Instance ID: php_fpm:76832668d3fef0b4 [OK]
      Configuration Source: container:docker://00441c041483816d80e1aec7177f94a9177e14528c94980342bd91ff98681b2e
      Total Runs: 128
      Metric Samples: Last Run: 7, Total: 896
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 1, Total: 128
      Average Execution Time : 5ms
      Last Execution Date : 2023-01-19 16:12:48 GMT<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-01-19 16:12:48 GMT<PHONE_NUMBER>000)

      Instance ID: php_fpm:7fa79cf1e1dde427 [OK]
      Configuration Source: container:docker://2bea0471b1c73e8d2fe37fd8cd9ebb2a51954d9307fb2fd0a0c00d06c1f5990d
      Total Runs: 128
      Metric Samples: Last Run: 7, Total: 896
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 1, Total: 128
      Average Execution Time : 9ms
      Last Execution Date : 2023-01-19 16:12:46 GMT<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-01-19 16:12:46 GMT<PHONE_NUMBER>000)

      Instance ID: php_fpm:9c8b94be9990fdaf [OK]
      Configuration Source: container:docker://8b6ed37d19ecdd666d8ee2b22a3347e9493fd8383f93928cc1caa9c9d2aca37d
      Total Runs: 127
      Metric Samples: Last Run: 7, Total: 889
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 1, Total: 127
      Average Execution Time : 4ms
      Last Execution Date : 2023-01-19 16:12:37 GMT<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-01-19 16:12:37 GMT<PHONE_NUMBER>000)

      Instance ID: php_fpm:e9fc1b071eee686c [OK]
      Configuration Source: container:docker://a3c65c04a4270c052e82096bd13036f576321c5f6c2c5a4933f9708c46c9d69c
      Total Runs: 127
      Metric Samples: Last Run: 7, Total: 889
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 1, Total: 127
      Average Execution Time : 4ms
      Last Execution Date : 2023-01-19 16:12:36 GMT<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-01-19 16:12:36 GMT<PHONE_NUMBER>000)

      Instance ID: php_fpm:f8c6d711ddbe909e [OK]
      Configuration Source: container:docker://0ad26c3330c4606b3f2e488335a30bacd7216721f3b35f1796a15b5f5467b39f
      Total Runs: 122
      Metric Samples: Last Run: 7, Total: 805
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 1, Total: 122
      Average Execution Time : 4ms
      Last Execution Date : 2023-01-19 16:12:47 GMT<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-01-19 16:12:47 GMT<PHONE_NUMBER>000)

    uptime
    ------
      Instance ID: uptime [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/uptime.d/conf.yaml.default
      Total Runs: 128
      Metric Samples: Last Run: 1, Total: 128
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2023-01-19 16:12:41 GMT<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-01-19 16:12:41 GMT<PHONE_NUMBER>000)

========
JMXFetch
========

  Information
  ==================
  Initialized checks
  ==================
    no checks

  Failed checks
  =============
    no checks

=========
Forwarder
=========

  Transactions
  ============
    Cluster: 0
    ClusterRole: 0
    ClusterRoleBinding: 0
    CronJob: 0
    DaemonSet: 0
    Deployment: 0
    Dropped: 0
    HighPriorityQueueFull: 0
    Ingress: 0
    Job: 0
    Namespace: 0
    Node: 0
    PersistentVolume: 0
    PersistentVolumeClaim: 0
    Pod: 0
    ReplicaSet: 0
    Requeued: 0
    Retried: 0
    RetryQueueSize: 0
    Role: 0
    RoleBinding: 0
    Service: 0
    ServiceAccount: 0
    StatefulSet: 0

  Transaction Successes
  =====================
    Total number: 269
    Successes By Endpoint:
      check_run_v1: 127
      intake: 12
      metadata_v1: 3
      series_v2: 127

  On-disk storage
  ===============
    On-disk storage is disabled. Configure `forwarder_storage_max_size_in_bytes` to enable it.

  API Keys status
  ===============
    API key ending with 68a13: API Key valid

==========
Endpoints
==========
  https://app.datadoghq.eu - API Key ending with:
      - 68a13

==========
Logs Agent
==========
    Reliable: Sending compressed logs in HTTPS to agent-http-intake.logs.datadoghq.eu on port 443
    BytesSent: 1.26175933e+08
    EncodedBytesSent: 1.1644357e+07
    LogsProcessed: 126571
    LogsSent: 126455

  journald
  --------
    - Type: journald
      Status: OK
      Inputs:
        journald:default
      BytesRead: 6.257091e+06
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 6
      24h Peak Latency (ms): 6

  docker
  ------
    - Type: docker
      Service: ***
      Source: php
      Status: OK
      Inputs:
        00441c041483816d80e1aec7177f94a9177e14528c94980342bd91ff98681b2e
      BytesRead: 165349
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 0
      24h Peak Latency (ms): 0
    - Type: docker
      Service: ***
      Source: apache
      Status: OK
      Inputs:
        030df0dc14386862bdf704e7f2ae554a4807ebaca2b12f587fb4b0fbe7a90dd4
      BytesRead: 364631
      Average Latency (ms): 2
      24h Average Latency (ms): 2
      Peak Latency (ms): 47
      24h Peak Latency (ms): 47
    - Type: docker
      Service: ***
      Source: php
      Status: OK
      Inputs:
        0ad26c3330c4606b3f2e488335a30bacd7216721f3b35f1796a15b5f5467b39f
      BytesRead: 2.31492e+06
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 5
      24h Peak Latency (ms): 5
    - Type: docker
      Service: ***
      Source: apache
      Status: OK
      Inputs:
        0b7a7782ba6e2989a6a2730c8a979323f31871f05bc16086f056365996d15958
      BytesRead: 111703
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 0
      24h Peak Latency (ms): 0
    - Type: docker
      Service: ***
      Source: php
      Status: OK
      Inputs:
        10e0e4131fccf6d3d1282974b574ba6269500207f6951e10ad3c9ccf2f91a714
      BytesRead: 112846
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 0
      24h Peak Latency (ms): 0
    - Type: docker
      Service: ***
      Source: cron
      Status: OK
      Inputs:
        186840bcf100786b21e83d8eff355df5289473501b65961172f43f01314fd7f3
      BytesRead: 55904
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 0
      24h Peak Latency (ms): 0
    - Type: docker
      Service: ***
      Source: php
      Status: OK
      Inputs:
        2bea0471b1c73e8d2fe37fd8cd9ebb2a51954d9307fb2fd0a0c00d06c1f5990d
      BytesRead: 494146
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 1
      24h Peak Latency (ms): 1
    - Type: docker
      Service: fabio
      Source: fabio
      Status: OK
      Inputs:
        33f2c1567affb8d771a6fa4486ab5ce4641ee616dc6e840ff1155751a8434e92
      BytesRead: 1.7317784e+07
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 18
      24h Peak Latency (ms): 18
    - Type: docker
      Service: tyrion-api
      Source: apache
      Status: OK
      Inputs:
        34b9a7f741057296e39a3fc66284e17949943183941636e964b54d9243073da0
      BytesRead: 1.793461e+06
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 13
      24h Peak Latency (ms): 13
    - Type: docker
      Service: ***
      Source: php
      Status: OK
      Inputs:
        4572db2bfa9b422ebb14c85ec36986f229c209fdb783c8f29ee33453424dcf5b
      BytesRead: 762618
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 8
      24h Peak Latency (ms): 8
    - Type: docker
      Service: ***
      Source: apache
      Status: OK
      Inputs:
        69d63b38db79e4f42dde9423f32b8f4a1f71500ea1148089778051de3535bb1e
      BytesRead: 28564
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 0
      24h Peak Latency (ms): 0
    - Type: docker
      Service: ***
      Source: varnish
      Status: OK
      Inputs:
        7db8c907c3b6cd0371f4625c3dba42616c57f60a59d4eb45a1a6722b7669a4ee
      BytesRead: 1.6281605e+07
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 19
      24h Peak Latency (ms): 19
    - Type: docker
      Service: ***
      Source: apache
      Status: OK
      Inputs:
        84dcf31b36c0bc87e95eff8c6213d97465ffb4a7920644243702c3cb57e4a1b5
      BytesRead: 221330
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 0
      24h Peak Latency (ms): 0
    - Type: docker
      Service: ***
      Source: php
      Status: OK
      Inputs:
        8b6ed37d19ecdd666d8ee2b22a3347e9493fd8383f93928cc1caa9c9d2aca37d
      BytesRead: 58157
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 0
      24h Peak Latency (ms): 0
    - Type: docker
      Service: ***
      Source: php
      Status: OK
      Inputs:
        8e3f1302b6fc41ca74d05d9b36b957c1ff83fdc2ddc742f773070dfd21f77134
      BytesRead: 58272
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 0
      24h Peak Latency (ms): 0
    - Type: docker
      Service: ***
      Source: nuxt
      Status: OK
      Inputs:
        8f80c410f6c8dbe3f5cc5e5ce2420b31db86277581b813bd227c5174e5d0ebec
      BytesRead: 2480
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 0
      24h Peak Latency (ms): 0
    - Type: docker
      Service: ***
      Source: nuxt
      Status: OK
      Inputs:
        91160aebc9bde8e4f14e19ec81cfafa94c875f134076e045dbbb489a96bf3c5f
      BytesRead: 6503
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 0
      24h Peak Latency (ms): 0
    - Type: docker
      Service: ***
      Source: nuxt
      Status: OK
      Inputs:
        9a16663605cc6da79be360f684ea3491421827976342a6811729ab35a81e4b5d
      BytesRead: 2480
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 0
      24h Peak Latency (ms): 0
    - Type: docker
      Service: ***
      Source: varnish
      Status: OK
      Inputs:
        9a79a6948181a63a8a8106e8af12e87e30beac105fec096887f49533290e4324
      BytesRead: 1.6014792e+07
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 33
      24h Peak Latency (ms): 33
    - Type: docker
      Service: ***
      Source: cron
      Status: OK
      Inputs:
        a1a5f3b0710444f571fff7e9f056e1d930951d1e24af95f2ea031a8bd3173ea1
      BytesRead: 202824
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 0
      24h Peak Latency (ms): 0
    - Type: docker
      Service: ***
      Source: php
      Status: OK
      Inputs:
        a3c65c04a4270c052e82096bd13036f576321c5f6c2c5a4933f9708c46c9d69c
      BytesRead: 281182
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 10
      24h Peak Latency (ms): 10
    - Type: docker
      Service: ***
      Source: varnish
      Status: OK
      Inputs:
        a9b97c06c2f7567b0e8c5543bec5cb4027a9a747b8630f925fe93b750fd1c9ba
      BytesRead: 406789
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 1
      24h Peak Latency (ms): 1
    - Type: docker
      Service: ***
      Source: apache
      Status: OK
      Inputs:
        b2c4b275a48cd61699acdf87241d07c938034fdb3852190dea96cd6d62b09c29
      BytesRead: 46054
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 0
      24h Peak Latency (ms): 0
    - Type: docker
      Service: ***
      Source: varnish
      Status: OK
      Inputs:
        b5b5b307ed342190eda4ee6b536ad9552d659429f9d1bcca60abc65a96df0521
      BytesRead: 111472
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 0
      24h Peak Latency (ms): 0
    - Type: docker
      Service: ***
      Source: haproxy
      Status: OK
      Inputs:
        bb2549155c03dbf2cf62cdf5b38a630c3ed4b66e627916e83dec44e2073b09df
      BytesRead: 209855
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 0
      24h Peak Latency (ms): 0
    - Type: docker
      Service: ***
      Source: apache
      Status: OK
      Inputs:
        bbbc5a6d6df8d2a4b87af0a84b06a3cbbb2dcd88d625166ebc2fdf9029a763fa
      BytesRead: 1.055271e+06
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 2
      24h Peak Latency (ms): 2
    - Type: docker
      Service: ***
      Source: varnish
      Status: OK
      Inputs:
        dae944d068b1ded2267f0f33da591731b459031a64ab60799577e7882778738e
      BytesRead: 109233
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 0
      24h Peak Latency (ms): 0
    - Type: docker
      Service: ***
      Source: apache
      Status: OK
      Inputs:
        e9aaea3b36d3b88bb54e761868c3f2aae17f689d6e7b9317cb8a27b502b7db58
      BytesRead: 74944
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 0
      24h Peak Latency (ms): 0
    - Type: docker
      Service: ***
      Source: apache
      Status: OK
      Inputs:
        ecadd0b3743f23aa43be3d17a00ffd0eb49a316a4970763cad222a64b7651e55
      BytesRead: 75385
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 1
      24h Peak Latency (ms): 1
    - Type: docker
      Service: ***
      Source: apache
      Status: OK
      Inputs:
        f6d9448e8e2e29867654d0cf7bb72468112e2b6a87302fef0e8d7bcd1018138b
      BytesRead: 767429
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 4
      24h Peak Latency (ms): 4

  container_collect_all
  ---------------------
    - Type: docker
      Service: ***
      Source: ***
      Status: OK
      Inputs:
        83d12ecf40a0ded7ed0001675cd642992dcd1581c5905358589cae65d975e37d
      BytesRead: 4825
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 0
      24h Peak Latency (ms): 0
    - Type: docker
      Service: ***
      Source: ***
      Status: OK
      Inputs:
        bf69ecf38ae246eb87b787774860db4f32ecbe6bf0cb659ce2ffe91cd3566c7d
      BytesRead: 0
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 0
      24h Peak Latency (ms): 0

============
System Probe
============
  Status: Running
  Uptime: 31m45.000270514s
  Last Updated: 2023-01-19 16:12:38 GMT<PHONE_NUMBER>000)

  NPM
  ===
    Status: Running
    Last Check: 2023-01-19 16:12:27 GMT<PHONE_NUMBER>000)

=============
Process Agent
=============

  Version: 7.41.1
  Status date: 2023-01-19 16:13:00.117 GMT<PHONE_NUMBER>117)
  Process Agent Start: 2023-01-19 15:40:50.786 GMT<PHONE_NUMBER>786)
  Pid: 368358
  Go Version: go1.18.9
  Build arch: amd64
  Log Level: info
  Enabled Checks: [process rtprocess connections]
  Allocated Memory: 36,363,928 bytes
  Hostname: copper

  =================
  Process Endpoints
  =================
    https://process.datadoghq.eu - API Key ending with:
        - 68a13

  =========
  Collector
  =========
    Last collection time: 2023-01-19 16:12:59
    Docker socket: /var/run/docker.sock
    Number of processes: 389
    Number of containers: 34
    Process Queue length: 0
    RTProcess Queue length: 0
    Connections Queue length: 0
    Event Queue length: 0
    Pod Queue length: 0
    Process Bytes enqueued: 0
    RTProcess Bytes enqueued: 0
    Connections Bytes enqueued: 0
    Event Bytes enqueued: 0
    Pod Bytes enqueued: 0
    Drop Check Payloads: []

=========
APM Agent
=========
  Status: Running
  Pid: 368367
  Uptime: 1929 seconds
  Mem alloc: 8,985,784 bytes
  Hostname: copper
  Receiver: <IP_ADDRESS>:8126
  Endpoints:
    https://trace.agent.datadoghq.eu

  Receiver (previous minute)
  ==========================
    No traces received in the previous minute.

  Writer (previous minute)
  ========================
    Traces: 0 payloads, 0 traces, 0 events, 0 bytes
    Stats: 0 payloads, 0 stats buckets, 0 bytes

==========
Aggregator
==========
  Checks Metric Sample: 324,293
  Dogstatsd Metric Sample: 1,020,844
  Event: 1
  Events Flushed: 1
  Number Of Flushes: 127
  Series Flushed: 393,356
  Service Check: 6,004
  Service Checks Flushed: 6,090

=========
DogStatsD
=========
  Event Packets: 0
  Event Parse Errors: 0
  Metric Packets: 1,020,843
  Metric Parse Errors: 0
  Service Check Packets: 0
  Service Check Parse Errors: 0
  Udp Bytes: 159,459,477
  Udp Packet Reading Errors: 0
  Udp Packets: 141,172
  Uds Bytes: 0
  Uds Origin Detection Errors: 0
  Uds Packet Reading Errors: 0
  Uds Packets: 0
  Unterminated Metric Errors: 0

====
OTLP
====

  Status: Not enabled
  Collector status: Not running

Describe what happened:
I'm seeing this on average a couple of times a day on each of 12 cluster nodes. Through the day, as new services (consisting of one or more containers) are deployed and old versions of services terminated, logs for the new services stop appearing in datadog. Existing services continue to log without issue. The cause seems to be, from the logs, an error handling the shutting down of containers that results in the dd agent failing to handle further docker events until restarted.
Describe what you expected:
I'd expect that dd agent should correctly handle the termination of docker containers and the identification and registration of new containers consistently.
Steps to reproduce the issue:
While this issue happens frequently across all of our cluster nodes I have seen it also happen simply with datadog-agent and docker on a standard ubuntu setup and with manually started and stopped containers. I cannot, however, see a pattern of behaviour to guarantee the error is triggered.
Additional environment details (Operating System, Cloud provider, etc):
I've managed to get this to happen with latest datadog-agent install and latest docker-ce install from apt on ubuntu 20.04 (with latest updates).
It may be of importance that our docker is running in subuid/subgid mode (with the config value "userns-remap": "default" in daemon.json). As datadog-agent doesn't handle standard json-based log processing in this docker mode (because docker writes the container data to a different folder in this mode) we also use journald as our docker log driver.
Our daemon.json docker config is:
{
  "storage-driver": "overlay2",
  "log-driver": "journald",
  "userns-remap": "default",
  "live-restore": true
}

Issue #12101 very likely related.

This issue will be fixed in version 7.43.0 with https://github.com/DataDog/datadog-agent/pull/15138.

@vickenty As far as I can tell from release notes, this one didn't make it in. Can you confirm?

@grickit The fix was merged without a release note unfortunately, but it was included in the release.


Gen Otel using ast

Since the routes are generated it’s possible to gen Otel telemetry ?

probably but I think middleware would be a better fit? Just depends on what telemetry you're referring to


Improve test

Use direct import for IDE
Skip environment variable check.

Do we need to backport it?

It is better.

test this please

LGTM


Default remote port

When the cluster server is exposed on TCP 443, the context server url doesn't have port.
remote_port var can't set and we have an index out of bounds error.
Could you set this variable by default to 443 if port doesn't specify in the url ?
Thanks,

I suppose it makes sense. Will poke at it when I have a chance.


chore(all): address sonarqube code smells

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: ad8b96150b6dfa80ba05f982bfcb4d9279f6704b
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Improved integer matrix multiplication performance by modifying tuning parameters

This pull request close to doubles performance compared to the baseline, and is comparable with the volta sgemm kernel fp32 performance on RTX 2070s.

Should improve performance on #6611

This is interesting, thanks for the tuning work! Is the value determined based on some heuristics? Could you share the perf numbers before/after the change?

Sure @leofang, here are the numbers before and after (Platform: RTX 2070 Super, Ryzen 3700x) on the script in #6611:
Before: GPU-0:19393.219 us   +/-283.384 (min:19037.249 / max:19775.520) us
After: GPU-0: 9992.426 us   +/-277.752 (min: 9629.440 / max:10451.392) us
Improvement: ~1.94x
The rough heuristic I tried to use was maximizing SMEM usage/minimizing memory accesses + minimizing uncoalesced accesses (Note that this kernel is templated for different dtypes, which may cause uncoalesced accesses with smaller dtypes that would not be apparent with larger dtypes). However, even some parameters that should be better based on this heuristic lead to worse performance, so it seems the heuristic is not super accurate, and the kernel is very sensitive to changes in the tuning parameters.
Profiling suggests that compared with the equivalent fp32 volta sgemm the effective memory throughput is much worse, which is another area to look at.
However, compared to the original kernel, SM and FMA pipeline utilization is much higher, probably indicating the larger sizes we are working with using these tuning parameters compensates/overlaps with memory transfers making it less of an issue. This is further indicated by the higher % of eligible warps for the new tuning parameters.

Thanks for all the effort in fine tuning this!
Just glazed through the numbers and they make complete sense for modern architectures.
I originally just ripped the magma kernel without considering anything else as the main goal was to solve numerical issues because we were converting the arrays to fp since cublas does not support integers.

/test mini

Looks like there are some numerical issues. IIRC those tuning parameters are constrained. Maybe this patch broke some assumptions.

I’ll have to take a closer look to see what’s causing this.

Thanks! The kernel has some fishy stuff where out-of-bound accesses are happening shouldn't affect but who knows ...
We are willing to use a different kernel or switch to cutlass if possible. So feel free to do the thing that you feel is easier. :)

So I took a look at why it wasn't working again after a few days. It seems like the constraints to ensure correctness are that, at least from a rough look, the following:
$$\mathtt{dim_x \cdot dim_y = blk_m \cdot blk_k = blk_n \cdot blk_k = dim_{xa} \cdot dim_{ya} = dim_{xb} \cdot dim_{yb}}$$
Under these constraints from whatever quick testing I've done the original parameters seem to work best. Hence, using cutlass or a different kernel may be a better option as @emcastillo suggested.

Another quick update. According to the Cutlass README the integer types supported for multiplication are 32 bit, 64 bit, and 1 byte booleans. From the below lines it seems like cupy supports a much wider range of integer types. Hence, I'm not sure if cutlass will work, at least not directly. @emcastillo did you have any thoughts https://github.com/cupy/cupy/blob/1c55be4179e93470afe994daa864b568ee6de7a5/cupy/_core/_routines_linalg.pyx#L291-L301

So, I had a chance to take a quick look again, and improve the tuning slightly. The LSU utilization goes down 15% from around 85% to 60%. The improvement is below.
Before: 19561.722 us   +/-1014.614 (min:17894.272 / max:21265.888) us
After: 15132.362 us   +/-2005.728 (min:13217.984 / max:18647.297) us
Improvement: 1.3x
So, there is a clear improvement, but it is not significant when compared to the FP32 and FP16 performance. The kernel may need to be rewritten to support better load store semantics, but hopefully this tuning improvement is still useful until more effort can be invested in this. @emcastillo @leofang

/test full

Thanks a lot for trying this again!! Hope this time the tests won't have problems :)


⚠ Bofrost.fr has degraded performance

In fdc4cd9, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1824 ms

Resolved: Bofrost.fr performance has improved in 982e630 after 7 minutes.


doc: add search bar

add docusaurus search bar

The highlight color in the popup is white and it makes the text unreasonable. Is it possible to change this?

@chancehudson done!


Add  WizardCoder models (that are CodeLLama based) evaluation

The WizardCoder models (starting from CodeLlama) now add <s> token at the beginning of tokenized text but have bos_token set at </s> which impacts the post-processing (see issue)
We add evaluation using the same prompt and post-processing (an Instruction version of HumanEval slightly different from HumanEvalSynthesize) as the original authors here (could be moved to HumanEvalPack task later)

@loubnabnl  Hello loubnabl, I have question for this PR. I use the following command to test the WizardCoder in bigcode-evaluation-harness, it seems the inference time is almost 13hours and the result is poor.


Prevent Modal Close when Clicking Outside the Modal

Hi,
I still pretty new to UI-Bootstrap so this may be a simple one.
I am trying to configure the modal to:
1.User is required to make a selection from the Modal options
2. If the user clicks outside the Modal, it does not close
Any help would be great!

See the backdrop: 'static' option, as listed in the documentation here - this should do the trick


Handle seccomp agent upgrades without disruption to running containers

Ideal future situation
Roll a new version of the agent without impact on any running container on the nodes.
Implementation options
Some random ideas that come to mind:

Configure the daemonset to create the new pod before destroying the old one. The new pod can communicate and receive the fds from the old. This of course doesn't help with crashes, though.
Have a small binary that holds the fds and pass them to the agent when it starts. This will handle just fine if the agent crashes or needs to be restarted. This binary should probably be another daemonset. Need to decide how the flow would look like (this binary receives from the socket and passes fds to the agent? So it needs to communicate with the agent not only on startup? Can the fds be received by both, the agent and the small binary, so the agent only queries the small binary on startup?)
Investigate if CRIU has any interesting idea we can use here: https://criu.org

We could get some inspiration from systemd and its "FD Store" facility that stores file descriptors from services when they restart (systemctl restart). See FDSTORE=1 in

https://manpages.debian.org/testing/libsystemd-dev/sd_pid_notify_with_fds.3.en.html
https://manpages.debian.org/testing/libsystemd-dev/sd_listen_fds_with_names.3.en.html

We could have this second daemonset you mention (seccomp-fdstorage) to store the fds along with the related metadata.
But is the additional complexity worth it?

Oooor, just rely on the host systemd to save the fds for us, using that functionality. No "inspiration", just use it!
We should explore more that option (like security concerns, etc.) but seems worth exploring. Also, Kubernetes graceful shutdown KEP works only with systemd hosts, so most hosts really should have systemd. Maybe we can't use it if we want to run on GKE Autopilot, but all at its own time :)


Booting on cloud VM

Hi,
I tried both CSR and XVR images (from the list of supported firmwares). It stops just a few seconds after running the container and it stays like this forver. Port 22 is open on the container though but no "ssh" banner or anything.
[root@virtualserver01 ~]# docker logs e1820d46918b
2020-05-24 18:09:51,216: vrnetlab   DEBUG    Creating overlay disk image
2020-05-24 18:09:51,233: vrnetlab   DEBUG    Starting vrnetlab CSR
2020-05-24 18:09:51,234: vrnetlab   DEBUG    VMs: [<main.CSR_vm object at 0x7f736cd25588>]
2020-05-24 18:09:51,247: vrnetlab   DEBUG    VM not started; starting!
2020-05-24 18:09:51,247: vrnetlab   INFO     Starting CSR_vm
2020-05-24 18:09:51,248: vrnetlab   DEBUG    ['qemu-system-x86_64', '-display', 'none', '-machine', 'pc', '-monitor', 'tcp:<IP_ADDRESS>:4000,server,nowait', '-m', '4096', '-serial', 'telnet:<IP_ADDRESS>:5000,server,nowait', '-drive', 'if=ide,file=/csr1000v-universalk<IP_ADDRESS>a-overlay.qcow2', '-device', 'pci-bridge,chassis_nr=1,id=pci.1', '-device', 'e1000,netdev=p00,mac=52:54:00:2a:b3:00', '-netdev', 'user,id=p00,net=<IP_ADDRESS>/24,tftp=/tftpboot,hostfwd=tcp::2022-<IP_ADDRESS>:22,hostfwd=udp::2161-<IP_ADDRESS>:161,hostfwd=tcp::2830-<IP_ADDRESS>:830,hostfwd=tcp::2080-<IP_ADDRESS>:80,hostfwd=tcp::2443-<IP_ADDRESS>:443', '-device', 'e1000,netdev=p01,mac=52:54:00:5d:29:01,bus=pci.1,addr=0x2', '-netdev', 'socket,id=p01,listen=:10001', '-device', 'e1000,netdev=p02,mac=52:54:00:9f:d7:02,bus=pci.1,addr=0x3', '-netdev', 'socket,id=p02,listen=:10002', '-device', 'e1000,netdev=p03,mac=52:54:00:83:35:03,bus=pci.1,addr=0x4', '-netdev', 'socket,id=p03,listen=:10003', '-device', 'e1000,netdev=p04,mac=52:54:00:33:a4:04,bus=pci.1,addr=0x5', '-netdev', 'socket,id=p04,listen=:10004', '-device', 'e1000,netdev=p05,mac=52:54:00:f6:9c:05,bus=pci.1,addr=0x6', '-netdev', 'socket,id=p05,listen=:10005', '-device', 'e1000,netdev=p06,mac=52:54:00:71:52:06,bus=pci.1,addr=0x7', '-netdev', 'socket,id=p06,listen=:10006', '-device', 'e1000,netdev=p07,mac=52:54:00:32:59:07,bus=pci.1,addr=0x8', '-netdev', 'socket,id=p07,listen=:10007', '-device', 'e1000,netdev=p08,mac=52:54:00:35:9f:08,bus=pci.1,addr=0x9', '-netdev', 'socket,id=p08,listen=:10008', '-device', 'e1000,netdev=p09,mac=52:54:00:e2:e3:09,bus=pci.1,addr=0xa', '-netdev', 'socket,id=p09,listen=:10009']
I have Docker and the KVM driver loaded. This is Citrix environment and hardware based nested virtualization is not really supported but I can run containers with the native Linux driver. Have you seen this issue before? Could it be related to the fact that I am trying to run it on CentOS VM?
Thanks.

Let me elaborate a bit more. So it stays with the message above for about 10 minutes. During this time ports 22, 830 are open but there aren't any services listening on these ports (e.g. I can't ssh). After about 10 minutes it seems like the router starts running the last two lines from above in a loop every 10-20 seconds:
2020-05-24 18:09:51,247: vrnetlab INFO Starting CSR_vm
2020-05-24 18:09:51,248: vrnetlab DEBUG ['qemu-system-x86_64', .......... (5 pages long command line parameters)
--- in 10-20 seconds ---
2020-05-24 18:09:51,247: vrnetlab INFO Starting CSR_vm
2020-05-24 18:09:51,248: vrnetlab DEBUG ['qemu-system-x86_64',  ......

I'm having a very similar issue with CSR in a VMware environment.
Did you manage to resolve it or find out the cause?

My post was about running this in container. The solution was ... just to wait more. It took something line 20 minutes to get the container up. I tried it on my personal PC ... took even longer.

The qemu process doesn't have access to KVM hardware acceleration. This is evident of the qemu args, as there's not -enable-kvm argument in there. If the /dev/kvm device would have been available, it would have enabled KVM.
Lack of hardware acceleration means it is going to be very slow, which is congruent with the described symptoms. I am going to close this as it's not a bug or feature enhancement.

The qemu process doesn't have access to KVM hardware acceleration. This is evident of the qemu args, as there's not -enable-kvm argument in there. If the /dev/kvm device would have been available, it would have enabled KVM.
Lack of hardware acceleration means it is going to be very slow, which is congruent with the described symptoms. I am going to close this as it's not a bug or feature enhancement.


Give XYZ a real name

I am not sure yet.

stream
bus
queue
flow

Can we call it a flow?
It's main purpose is to deliver data, so I think yes, we can call it a flow.
Isn't it a bus?
Actually it is some kind of bus implementation, since everybody can listen to message going through it, but the bus allows message delivery to multiple listeners, while this flow does not allow that.
Isn't it a stream?
Certainly isn't.
Is it a queue?
It does not have queue interface, so no. It may contain 2 queues, but that's all. http://stackoverflow.com/a/1590262/607033


[BUG] Wrong ARCtrl namespace in YAML project

https://github.com/nfdi4plants/ARCtrl/blob/dc3822fd1fec14c6009425e618531adf8828119a/src/Yaml/Decode.fs#L1
It should be ARCtrl

Already fixed on my branch introducing Tests for said library, will include in pr

should be fixed via #409 , can you confirm @Freymaurer ?


The Second Great Split on levels.txt and File Reading

The file reader (load_levels) needs to now be able to read multiple files (higher in scope) and add onto the existing level dictionaries instead of overwriting them. What needs to be done in dsn_class is:

[ ] Change load_levels to add onto level_set and level_elements
[ ] Add a new method in memory to read a folder through a file path and get all the files containing levels. Then have this method call load_levels
[ ] This would also be a good opportunity to put in error checks (try/except/else) into the file reader too

What do you mean by the second great split? Are you exclusively referring to levels.txt as the second great split with the first great split being in the code being the three way split of class, main, and levels?

Yea, levels.txt is the second great split


Change docker test job dependency

change form existence of dockerfile to docker-compose.test.yml to run docker compose tests.
Change-type: patch
Signed-off-by: fisehara<EMAIL_ADDRESS>

Will need more separation of docker_test and docker building steps. Closing for now


232 SIM Database Schema Migration

What
This is the first attempt to use ADRs
Purpose
In this PR, I'd like your feedback on the ADR. Once we agree, we can continue the actual implementation work in another PR
Reviewer tips
Read this with a markdown renderer
Future
I'm trying out this approach for discussions. I'm open to hearing more options on how to do this process

Please add the steps needed to test this PR :)

Sure! I've put it as a draft while its a WIP, you can unsubscribe from the notifications until I reopen it :)


Issue/670 docs

Monika Pull Request (PR)
What feature/issue does this PR add
This PR fixes #670
How did you implement / how did you fix it

Revert back to getStaticProps
Run the cron to publish the Docs every 12 AM and 12 PM

How to test

Run the docs
Go to localhost:3000/docs

Screenshots

Unlinked #674 because I misunderstand the task

@nicnocquee For the docs, I temporarily disable eslint error in npm run build https://nextjs.org/docs/api-reference/next.config.js/ignoring-eslint
I think if we want to resolve all types and lining errors, it should be in a different ticket because the issue is pretty huge. In the meantime, we want to be able to deploy the docs ASAP


why heartbeat param not in amqp.get_producer

this is a question to understand why the heartbeat feature is not used for all connections.
in fact, we found out that our very small micro-service stack (5 micro-services) was consuming more and more memory of our small rabbitmq server (> 400mb ) for 1 message every minutes.
we found out that more connection (which consume around 16Mb each) was created over the time, without being closed. the «stale» connections was without heartbeat.
I investigated to find that nameko was opening $max_woker connections to the rabbitmq during medium load via get_produced function, but these connections was without the heartbeat parameters, and was not closed after use.
I just ask if this is intended, or if this should be reworked.
after some experiment, it seem the add of heartbeat for get_producer remove the extra connection after the load has passed and thus the memory used by rabbitmq is lower for a small cluster of services.
version for testing:
nameko latest master (commit 286d141af2e0fe3fc5b592228c4cea93ca495d81)
amqp==1.4.9
RabbitMQ 3.6.10, Erlang 19.3

Kombu (the library we use to send and receive AMQP messages) only supports heartbeats for consumer connections. Publishers use a pool of connections managed by Kombu, and at least within Nameko there's no mechanism to regularly send the heartbeats down these connections (unlike the consumers, which have a thread each).
You can probably improve your memory consumption by limiting the size of the pools.
By adding the heartbeat parameter to get_producer you're probably configuring the underlying connection with a heartbeat, but never actually sending the beat from the client side. The server will close the connection after two heats are missed, which is probably why you get your memory back. It's very inefficient though, since every connection lives for a maximum of 2 * heartbeat seconds.
Ultimately I'd love to support heartbeats for publisher connections, but we'd need to replace kombu with a better AMQP library to do so.

Ok, I was expecting something like that.
we will work on the pool size instead
thanks to you for this very helpful response. I hope I will be of some use for this project one day :D

How to solve the dead TCP connections problem then?
Rabbitmq documentation says to use heartbeats for all connections. We see a lot of dead connections when producers connect/disconnect.
https://www.rabbitmq.com/heartbeats.html

@epetrovich the ultimate solution is to replace kombu, which actually in progress now. No promises on when it will land though.
In the mean time, you shouldn't see that many dead connections assuming you're using the kombu pools (which nameko does most of the time). What is "a lot" and what problems occur as a result?

@mattbennett Is there some branch to see the progress? By the way what do you think about allowing to override get_producer here https://github.com/nameko/nameko/blob/master/nameko/amqp/publish.py#L175, which will allow to set some heartbeat to producer connection and thus will help rabbitmq close idle producers connections (as far as i understand if pool sees a broken connection it will release it and create a new one)?

Our producers are running on AWS spots for batch scheduled jobs.
We can launch and shot down about 200-500 spot instances  per day.
One working day adds about 2-3k dead connections from producers. We are working on graceful shutdown of rabbitmq producers also.

@mattbennett we found our problem regarding too many dead connections. We just did not shutdown supervisor gracefully when terminating spot instances. But still it would be a nice feature to have producer heartbeat separate from consumer heartbeat (which might be None by default keeping backward compatibility). I personally do not like the workaround with inheriting from PublisherCore because I will have to copy-paste the whole PublisherCore.publish method, because there is no way to override get_producer inside it. Producer heartbeat although has no application (until there is an implementation supporting producer heartbeats) except for RabbitMQ will have a chance to clean up dead connections after a timeout, so maybe adding a support to supply connection kwargs though Producer class is not bad. What do you think?

This issue was moved to https://discourse.nameko.io/t/why-heartbeat-param-not-in-amqp-get-producer/306


Add windows badge and FFmpeg installation guide

closes https://github.com/akamhy/videohash/issues/11

closes https://github.com/akamhy/videohash/issues/11


Skyrim crashes with recent builds

Describe the bug

Since updating to the latest Remix and Bridge builds, I have experienced major stability and graphical issues
Issues:

Skyrim - Crashes seemingly at random after extended periods of time. I cannot narrow down what portion of Remix is crashing. Reverting to older builds fixes the issue

Bridge: 5aa73bc
Remix: 7f763ed
RTX 3090
537.42
Skyrim - Steam

Attach logs!
Skyrim:
d3d9.log
TESV_d3d9.log
NvRemixBridge.log
To Reproduce
This isn't easily reproducible. The issues are abundant and present in a strangely inconsistent manner
Expected behavior
Anything but this
(This is a repost, split from the original issue)

REMIX-2240 for tracking

Hello! We have been able to confirm this fix internally on a recent build. Please try again on the latest release and let us know if this issue persists. Thank you!

@NV-LL The main crashing issue does appear to have been resolved, which is great!
I did run into this crash, but this has been happening across various games for me. As far as I can tell, it's only in games that pause rendering when you alt-tab:

Glad to hear the crashing has been resolved. Will you please open a new ticket for the alt-tabbing issue? That way we can investigate and track it separately. Thanks!


Target package organization

In order to keep organized as things scale, we need to structure the packages a little differently.
Each online resource should have an interface class:

NCBI Variation Services: This is a wrapper class for the NCBI API. The current api_class.py has a few methods that could form the basis of this class (e.g., spdi_to_hgvs, hgvs_to_spdi).
VICC: This is a wrapper class for the VICC API. The current api_class.py has a few methods that could form the basis of this class (variation_to_vrs).

Each format should have a class:

VRS: DONE? - the VRS packages already define a VRS object and many methods for translation/validation. Any time we have a VRS object, this class should be used to manipulate it.

I believe this package already has to_hgvs and to_spdi methods

HGVS: DONE? - the biocommons hgvs packages already define a HGVS object and many methods for translation/validation. If we get an HGVS string, it should be parsed with this class. Any time we have an HGVS object, this class should be used to manipulate it.

If the hgvs package does not have a "to_spdi" method, we can extend it by adding a method that uses the NCBI Var Services class.
to_vrs: if this doesn't already exist, we could add it as a pass-through call to one of the VRS methods

SPDI: Currently there is no SPDI class defined (that I am aware of). We should write this. It will be a simple class with 4 required input params (SPDI) that uses the NCBI Var Services class for validation. Methods include:

init: create an object from scratch using required params
to_hgvs( format ): returns an HGVS object or string, as determined by the value of "format". This method can use the NCBI Var Services class to do the heavy lifting.
to_vrs: if this doesn't already exist, we could add it as a pass-through call to one of the VRS methods

Gen Std Core: this is the primary class we're working on now, to serve as the common data structure. The class needs to have the following methods.

init: create an object from scratch using required params
var_obj_to_core: takes as input a VRS, HGVS, or SPDI object, extracts values for required params, calls init()
to_spdi( format ): returns a SPDI object, string, or dict ( { sequence, position, deletion, insertion } ) as determined by the value of "format"
to_hgvs( format ): returns an HGVS object or string, as determined by the value of "format". This method can use the NCBI Var Services class to do the heavy lifting, or the hgvs package if we want to try to assemble it from scratch (probably harder)
to_vrs( format ): returns a VRS object or JSON structure, as determined by the value of "format". This method can use the VICC class to do the heavy lifting.

Additional classes (future):

Core db interface
FHIR R5+
FHIR R4?

@SalemBajjali Work from the top-down, beginning with the 2 interface classes since they should just need a bit of cut/paste from what you already have. Then check the VRS packages to see if they have everything we need as per above.
Let me know when you start on the HGVS package because I want to make sure we're on the same page regarding implementation (subclass/extension/wrapping).
The SPDI class should be straightforward.
Once those are done (hopefully it won't take very long) we can hit the gen std core class again. The guts of it shouldn't change much (see existing code and the associated issues I created tonight), and the methods for to_spdi/hgvs/vrs should be mostly pass throughs. The ingest method might take a bit of work but if we're using the pre-built objects it might be easier than taking strings.
While you're doing this I'll work with Jeff on the db schema, so it should be up and running by the time you start thinking about the core db interface class. You can take what you already have for that and update it as needed, then test it against the db he creates.
At that point we'll be ready to load some data and do some testing.
We'll do the FHIR classes last, of course.


Graphical glitch/bug nethersx2

Hello,
How to fix this bug ?

Its about the white bar/area on top.

Hello,
How to fix this bug ?

Can you please tell the community what game you are playing, that's because if it's only reproducible to this specific game, then the community needs to play this exact game to try to replicate this.
Didn't PCSX2 get a 2.0 version that already addressed this.
I think the next major thing the dev should do is not to fix bugs, but to update PCSX2 to the new 2.0 because that itself will fix more bugs than nethersx2 devs could ever dream of.
Is nethersx2 even open source, if it's open source then maybe i try addressing the issue myself, but i could not find any code, do we patch aethersx2 with proprietary patchers that's been provided by nethersx2 devs?


Saving python path

Issue Type: Feature Request
Currently the python path is being saved to .vscode/settings.json
That's not very portable because many times the python path contains the user directory path. I might be a lot better if the the python is from a conda or pyenv to store the name of the environment instead. At least then the user can create the same named environment on each of their machines and the settings.json file would no longer need to change each time. Right now one has to continuously stash and stash apply this file to exclude it from normal commits.
VS Code version: Code 1.57.1 (507ce72a4466fbb27b715c3722558bb15afa9f48, 2021-06-17T13:28:07.755Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No
Remote OS version: Linux x64 4.19.128-microsoft-standard
Remote OS version: Linux x64 4.19.128-microsoft-standard
Remote OS version: Linux x64 4.19.128-microsoft-standard
Remote OS version: Linux x64 4.19.128-microsoft-standard
Remote OS version: Linux x64 4.19.128-microsoft-standard

We have an experiment that just rolled out to 50% of users which stops saving to settings.json for your Python environment path, so we will no longer be doing this shortly.
Closing as a duplicate of #2125 .

Also worth mentioning that this experience is already available in our insiders build 😊


Assistant no longer knows how to play music

First of all,i know it didn't play music ever,but as of a few days ago,it doesn't even say music isn't supported,it just says it doesn't know how to help me with that "yet",and so do the chromecast commands,which used to work just fine

Which Chromecast commands stopped working?
Not knowing how to play music may be a change in the TTS response to reflect its current capability.

For example YouTube casting,Which used to work,still works on my phone

I used to tell assistant to cast videos from YouTube to the TV,it used to do it,I don't know why it doesn't work anymore

Were you using the library or gRPC version when executing these commands?

library,installed using pip

I believe this has since been fixed.


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[1.5.x] Add fix issue with setting value to openAPI title section

Purpose

Fix https://github.com/ballerina-platform/openapi-tools/issues/1252
Related PR: https://github.com/ballerina-platform/openapi-tools/pull/1253

Goals

Describe the solutions that this feature/fix will introduce to resolve the problems described above

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI (email<EMAIL_ADDRESS>to review all UI text). Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

User stories

Summary of user stories addressed by this change>

Release note

Brief description of the new feature or bug fix as it will appear in the release notes

Documentation

Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter “N/A” plus brief explanation of why there’s no doc impact

Training

Link to the PR for changes to the training content in https://github.com/wso2/WSO2-Training, if applicable

Certification

Type “Sent” when you have provided new/updated certification questions, plus four answers for each question (correct answer highlighted in bold), based on this change. Certification questions/answers should be sent to<EMAIL_ADDRESS>and NOT pasted in this PR. If there is no impact on certification exams, type “N/A” and explain why.

Marketing

Link to drafts of marketing content that will describe and promote this feature, including product page changes, technical articles, blog posts, videos, etc., if applicable

Automation tests

Unit tests

Code coverage information

Integration tests

Details about the test cases and coverage

Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes/no
Ran FindSecurityBugs plugin and verified report? yes/no
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes/no

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

Migrations (if applicable)

Describe migration steps and platforms on which migration has been tested

Test environment

List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested

Learning

Describe the research phase and any blog posts, patterns, libraries, or add-ons you used to solve the problem.

@lnash94 Why have we sent a separate PR for master? we agreed to sync 1.4.x with master time to time right?

@lnash94 Why have we sent a separate PR for master? we agreed to sync 1.4.x with master time to time right?

Yeah, we agreed to send a PR from time to time when if there is no conflict between these two branches but It's hard to sync a bunch of fixes at once to master from 1.4.x because these two branches already have conflicts, and there is a chance we might miss some of the fixes.

Approved as per https://github.com/ballerina-platform/openapi-tools/pull/1253