Make asynchronous process test run asynchronously

Overview
The test in test_async was not running asynchronously. This PR runs the test with processing mode set to distributed, and confirms the process completes.
Related Issue / Discussion
Fix #656
Additional Information
I moved the Sleep process definition with the other test processes.
I had trouble initially because I thought owslib would be able to read the status file. Unfortunately, owslib does not support status files on the local file system.
Contribution Agreement
(as per https://github.com/geopython/pywps/blob/master/CONTRIBUTING.rst#contributions-and-licensing)

[x] I'd like to contribute [feature X|bugfix Y|docs|something else] to PyWPS. I confirm that my contributions to PyWPS will be compatible with the PyWPS license guidelines at the time of contribution.
[x] I have already previously agreed to the PyWPS Contributions and Licensing Guidelines

Note that for longer "sleep" periods, test_async interferes with test_dblog. I solved this by shortening the sleep period, but there should be a cleaner solution to isolate test_dblog.

The update_status calls from the async process do not seem to be captured by the logging database in the test suite. Ideas ?

Coverage increased (+0.5%) to 81.901% when pulling cbd1c29c1816f2ed21ee2bfe232e70a41328c448 on fix-656 into 7839f5276ced486a8b7f83379e919fb05273b4e7 on main.

Hello,
I did a quick code review, imo you should split dca06fb6518bc1e00bf7a3f54981496288c1005d
into:
Refactor test.create_sleep into test.Sleep
Change test_async to actually test asynchronous process.
and to split cbd1c29c1816f2ed21ee2bfe232e70a41328c448, with typo fix separated from the rest.
More over having a loop with proper status check instead of sleep(.5) maybe better in dca06fb6518bc1e00bf7a3f54981496288c1005d

Replaced by #663 and #664


Clearer guidance to validating .travis.yml on the command line

Looking for a way to validate the travis file on the command line I got referred here from the Travis help. After going through the README I figured that this project here has no command executable but is purely to be used as a library (correct me if I am wrong).
After a bit of googling I then wrongly installed the now deprecated travis-lint.
After a bit more googling my current assumption as a user is that the go to command line tool is travis.rb using the 'travis lint' subcommand (right?)
Could the documnentation on Travis and/or here do a bit more handholding regarding the command line way of validating .travis.yml?

I guess this is the right place to look now?
https://github.com/travis-ci/travis-yml


Screeps server url should be configurable option

This will help to support local server installations. Also need to determine what requirements are to support terminal for local server installation.

Pull requests are accepted :-)

ok. Heh sadly i eat my bread with Java not with Python ;) Is Screepsapi third party library or not? As those hardcoded url's are there.

Yeah, it's thirdy party. However, someone made a pull request already for it to support other servers.

I have created a pull request that allows connection to private servers #13

As pull request was made and merged i'm closing this issue.


[cli] consider dropping info message about sound null safety

@kevmoo noticed that today dart compile js and dart compile exe produce an info message saying that the code is compiled with sound null safety:
Info: Compiling with sound null safety.

Now that Dart 3 only supports sound null safety, we should consider dropping this.
This message has been reported since cad04f86049dc09e800f4dbee1a721726e533ba8, reverting the changes to pkg/dart2native/lib/generate.dart and pkg/dartdev/lib/src/commands/compile.dart would probably be enough to remove this info message.
cc @johnniwinther
cc @mit-mit - this seems pretty minor to me, but bringing to your attention in case you think it's worth a cherry-pick later in our future patch release of Dart 3.0.1 or later.

We should keep an output when compiling in any other mode (only will ever apply internally), and drop the output for sound null safety.

Agreed. Here's the corresponding change in the Flutter tool:
https://github.com/flutter/flutter/commit/242bb67d199bf8f4cbe89dcb71a35850505a43e9

Landed in https://dart-review.googlesource.com/c/sdk/+/301385


Add support for two more types of incoming data

Adding two new types of collected data: Raw and Averaged (|r and |a respectively)
The Raw data is pretty much exactly what you would do if you just spoke directly to carbon. I included it in the statsd ecosystem because I like the UDP nature of statsd and so that libraries can be used without needing to code both towards statsd AND carbon.
The Average data counter is a lot like the "ms" type of data, but a bit simpler. I am using it to push monitoring metrics like disk utilization, load average, etc. Trying to use the |c or |ms data types for statsd in these circumstances worked pretty poorly.

I'm also using the Raw type and would love to see it in the main version.

This is good stuff for sure. I think I'd like to merge it in - but it's not going to go cleanly in it's current state. Can you update it to the latest version of statsd?

Will do. It's been on my todo list for this week.
On Feb 10, 2012, at 23:42, Erik Kastner<EMAIL_ADDRESS>wrote:

This is good stuff for sure. I think I'd like to merge it in - but it's not going to go cleanly in it's current state. Can you update it to the latest version of statsd?

Reply to this email directly or view it on GitHub:
https://github.com/etsy/statsd/pull/13#issuecomment-3918603

+1000 I'd love to see average and/or raw support in the main branch!

Yea, I saw this pull a few months back :) Surprised it wasn't integrated already!


Crash opening details page for Rufus

To reproduce:

Switch to “chocolatey” on the left.
Search for "rufus".
Double-click or right-click > details.

Expected:

Open details page.

Actual:

Open this dialog.
When dialog is dismissed, close entirely.
Leave this log file.

Notes:
choco info rufus in admin PS works as expected.
Context:
Chocolatey GUI 0.16.0
Chocolatey 0.10.10
Powershell 5.1.17133.73
Win 10 Pro 1803 build 17133.73

Replicated on another machine:
Chocolatey GUI 0.16.0
Chocolatey 0.10.10
Powershell 5.1.16299.251
Win 10 Enterprise 1709 build 16299.309

I can confirm this issue on my own computer as well. Not sure yet if there is a problem with the rufus package though as the error message mentions that the URI is invalid, but in my opinion such errors should probably be silently ignored by chocolatey gui.

Been looking through the rufus package now, and other than a broken image.
I can't see anything in the package that should cause the error, but from the error report it also seems to be a problem with the markdown, although I couldn't reproduce any error when testing it on the babelmark page.
Basically, I have no idea what's causing this. Could perhaps be wrong data returned by chocolatey? (probably not though).

Is this related to #578 ?

Looks similar, but I've only replicated the issue with rufus. All other packages I've tried work fine, including CCleaner.

well, I tried it with the latest pre-release and I don't get any erros.
Unfortunately I don't know if that is because the update of markdig, or if because the package(s) have been fixed (or at least updated) since last time I checked.

I just replicated this with CGUI 0.16.0, so it's not the package that's fixed.
Then I upgraded to 0.17.0-unstable0080 and Rufus works fine.

@jacktose thanks for confirming! 😄


[EUWE] Remove confirmation when opening the HTML5 vnc/spice console.

EUWE version of: https://github.com/ManageIQ/manageiq/pull/12673
https://bugzilla.redhat.com/show_bug.cgi?id=1348721
1/2 of this was done as part of 9b38984d for Euwe.

@bmclaughlin or @mzazrivec : review, please?

Closed by accident. @simaishi : reviewed, please, merge as it fits you.

@martinpovolny Can you reference PR for master?

@simaishi : added on top


[text analytics] add support for optional string-index-type query param

support will be added for this on the service's v3.0 API

dup of https://github.com/Azure/azure-sdk-for-net/issues/10710


Enable wasm32 compilation by wrapping libc

My plan is to use this with pyodide.
It is unclear how to test this at the moment. I think a reasonable solution is to make sure it compiles with --target wasm32-unknown-unknown after supplying suitable header files, possibly copying from pyodide, and run no tests. When/if things get ready with pyodide, we can consider running integration tests with it, but that would require a very different setup. Due to the nature of the builds, I also think it is unlikely that it can be usable without nightly in the near future.
I'm also happy to leave this as a PR until then. See also #1221

... so as I understand it, libc doesn't provide any exports on wasm32? Should this be fixed upstream?

... so as I understand it, libc doesn't provide any exports on wasm32? Should this be fixed upstream?

libc made a conscious decision to not support wasm32-unknown-unknown,
which makes sense since wasm doesn't come with any libc-like runtime.
For the purposes of building python extensions, this is less of a
problem, since we are building a dynamic library, to be loaded by an
emscripten runtime, which does provide libc-like functionalities.
An in any case, apart from the type definitions, all we need is
libc::atexit, which emscripten does happen to provide (should we provide
failsafes if it isn't present?)
There is a different target, wasm32-unknown-wasi, and wasi is a
standard for provide posix-like system calls in webassembly. libc is
working on an implementation for wasm32-unknown-wasi.
This wrapper is only enabled withen architecture = wasm32 and os =
unknown, so wasm32-unknown-wasi should use the "real" wasi-implemented
libc.

libc made a conscious decision to not support wasm32-unknown-unknown,
which makes sense since wasm doesn't come with any libc-like runtime.
For the purposes of building python extensions, this is less of a
problem, since we are building a dynamic library, to be loaded by an
emscripten runtime, which does provide libc-like functionalities.
An in any case, apart from the type definitions, all we need is
libc::atexit, which emscripten does happen to provide (should we provide
failsafes if it isn't present?)
There is a different target, wasm32-unknown-wasi, and wasi is a
standard for provide posix-like system calls in webassembly. libc is
working on an implementation for wasm32-unknown-wasi.
This wrapper is only enabled withen architecture = wasm32 and os =
unknown, so wasm32-unknown-wasi should use the "real" wasi-implemented
libc.

I see, thanks. In which case to have wasm32 support we're definitely going to need something like this.
To keep the "wrapper" as small as possible, for all types we use which are exported in std::os::raw can you please change this PR to use std::os::raw in the usage site and remove them from the wrapper?
Let's see what's left after they're gone - I think except for size_t, they probably account for most of the usages.

I see, thanks. In which case to have wasm32 support we're definitely going to need something like this.
To keep the "wrapper" as small as possible, for all types we use which are exported in std::os::raw can you please change this PR to use std::os::raw in the usage site and remove them from the wrapper?
Let's see what's left after they're gone - I think except for size_t, they probably account for most of the usages.

I think we can remove atexit but are still discussing at #1355

I think we can remove atexit but are still discussing at #1355

I think before resolving any rustc/wasm32 shenanigans, we can merge the
changes that convert libc to std::os::raw when applicable, which I
think is an positive change in any case (currently both are used,
seemingly arbitrarily)

I think before resolving any rustc/wasm32 shenanigans, we can merge the
changes that convert libc to std::os::raw when applicable, which I
think is an positive change in any case (currently both are used,
seemingly arbitrarily)

we can merge the
changes that convert libc to std::os::raw when applicable,

Agreed - are you willing to factor those changes out into a separate PR?

we can merge the
changes that convert libc to std::os::raw when applicable,

Agreed - are you willing to factor those changes out into a separate PR?

Agreed - are you willing to factor those changes out into a separate PR?

Sure

Agreed - are you willing to factor those changes out into a separate PR?

Sure

Closing in favor of #1368. May be reopened if this turns out to be useful/needed

Closing in favor of #1368. May be reopened if this turns out to be useful/needed


Rewrite RAMF serialization with BouncyCastle's ASN.1 implementation

I decided to change tack in #23 and used BouncyCastle's ASN.1 parser instead of using jASN1, whose parser I found too low-level and error-prone. I think we should eventually consolidate things and rewrite the serializer to use BC as well.
The changes should be minimal but there are more important things to be doing at this point so I'#m deferring it.

Fixed in #254


Edit rezconfig docstrings for package_filter to reflect python form rather than YAML

closes #1372

Closing because something is not configured right with my git user, causing the EasyCLA to fail, will try again


Worker

Should offload the word ladder computation to a worker so that the main thread isn't blocked when working with a large dictionary.

Hello, I'd like to work on this if that's ok :)
I'll try to get back with a PR in a day or two.


Added Indonesian Translations

I reviewed and updated 18 translation for Indonesian Language for Catima Android (Fastlane)

However, there are still 4 strings failed the maximum length checking. I think the limit which is 500 characters is impossible to follow for these case, as the original strings itself has more than 500 characters. Especially if we include the link to pull request. Maybe you can reconsider the maximum length settings.

Thanks!

However, there are still 4 strings failed the maximum length checking. I think the limit which is 500 characters is impossible to follow for these case, as the original strings itself has more than 500 characters. Especially if we include the link to pull request. Maybe you can reconsider the maximum length settings.

The 500 character limit comes from Google, it's not my choice. Although old changelogs are probably never going to reach Google Play, I can't let Weblate know which ones it should and shouldn't care about (and for new changelogs going over the limit would cause pushing to Google Play to fail).
If it was up to me, the limit would be higher. Sadly, it's not up to me :)


Add Nong Song: Electroman Adventures x Shooting Stars

Song Name
Electroman Adventures x Shooting Stars
Artist Name
Waterflame, Bag Raiders
Source
Direct file download
Youtube Link
No response
Direct File Link
https://cdn.discordapp.com/attachments/666654256908206101/1269788884859097119/Electroman.mp3?ex=66b1568d&is=66b0050d&hm=4d3934889264921b02255638e60f66f9784d5044a4a5c2d3f5ca0d8226168934&
Song ID
12
Start Offset [ms]
0
Extra
No response

reject
non-YouTube sources are not supported, unless it is a permanent direct download link from a CDN that has given permission for Auto Nong to download from
(yours is not permanent)


Please, add download games not only from the Torents

Is your feature request related to a problem? Please describe.
I can't download games from torrents due to ISP restrictions
Describe the solution you'd like
Add the ability to download games from other places, for example, from telegram channel - Notorgames
Describe alternatives you've considered
No response
Additional context
No response

There's real debrid support and torbox on the way.
You can download the games yourself and add the exe in the launcher. I don't think a lot of people would want downloading games from telegram channels lol


Timestamp as Node Name

Hello, i have read all the docs but couldn't figure out how can i get the timestamp, or set as Node/folder name, for organization purposes.
What i want to achieve is something like this:
Example
Doesn't necessarily needs to have another timestamp inside node.
Is it possible to do it? Thanks is advance!

Sorry I don't understand your question.
Please try the examples first for how to use.

I would like to set the timestamp on the path.
Something like this:
Firebase.setInt(firebaseData, "Anything/" + Timestamp + "/Variable", variable);

What is the type of Timestamp? Number or string?
If it is number you should make it as  string.
Firebase.setInt(firebaseData, "Anything/" + String(Timestamp) + "/Variable", variable);

Ok, but how can i get it from firebase servers? I need this timestamp but dont know how to get it.
In javascript, there is a function called firebase.database.ServerValue.TIMESTAMP which i can assign to a variable, like this:
timestamp = firebase.database.ServerValue.TIMESTAMP;
and then i could set to the path name. How can i do the same using the library?

https://github.com/mobizt/Firebase-ESP8266/blob/master/examples/Timestamp/Timestamp.ino

I understand now, thank you.


Incompatible with 1.17

I'm working on updating it. I have to rename a bunch of stuff because the mappings changed and the config API I'm using has also been updated, so I have to adapt to that. I can't do anything for Forge yet, just Fabric for now. Thanks for the reminder, though. I might have forgotten for a while without it :)
I'll close this once it's out, since technically the issue described here still exists.

I think I've finished the port!
I say I think because I can't build it right now because the Fabric maven is down, so there could be something left to do that I missed and would see if I tried to build it because it would fail and complain and tell me what was wrong and long run on sentences and fourth wall breakage and... comedy.
Jokes aside, I'll try to get it out once they're back online.

I just checked and I think they might finally be back. I'll try to get it out. I found some more code that needs updated though.

I just remembered that I already did this.


Viewport addon not working as expected

Describe the bug
After registering the addon it's icon shows up in the storybook window but the behavior is odd. Whenever I try to chose a viewport I end up with the same thing.
To Reproduce
Steps to reproduce the behavior:

Install the addon yarn add -D @storybook/addon-viewport
Register it in addons.js

import '@storybook/addon-viewport/register';

Create a story:

import React from 'react';
import { storiesOf } from '@storybook/react';

import ActionDialog from './index';

storiesOf('ActionDialog', module).add('default', () => (
  <ActionDialog>Dialog Content</ActionDialog>
));

Run storybook

Expected behavior
The viewport setting resizes the viewport as shown in the print in the Readme.
Actual behavior
With no breakpoints selected (this is correct)

With any breakpoint selected (in this case, iphone6)

Notice that it changes the size of the viewport (see scrollbar on the right) but not to the expected size.
System:

OS: Ubuntu 16.04
Device: Desktop
Browser: chrome
Framework: react
Addons: breakpoint
Version: 5.0.6

Have you taken a look at our example? Does this work as expected on your machine/browser?
https://storybooks-official.netlify.com/?path=/story/ui-panel--default

Yes it does. I cloned the repo and will test the example to see if I find any difference between my setup and what the example does.

@shilman, I'm definitely seeing an issue similar to this in next. Example can be found here: https://next--storybooks-vue.netlify.com/?path=/story/welcome--welcome

It looks like this is a problem in next but not master. Perhaps it was introduced in https://github.com/storybooks/storybook/pull/6045
@lucas-carl mind taking a look at this?

@shilman I looked into the next version right after my PR but can't seem to find any bugs.

Having the same issue.

Seeing this issue with @next

Same here, broken on @next

@lucas-carl Indeed, I checked and the problem got introduced in alpha.15, probably by this PR: https://github.com/storybooks/storybook/pull/6126
@Armanio mind looking into this?

I check it today. Give me a few hours. 👍

Guys, I apologize: it's my mistake, I fixed zoom and broke background addon.
I create PR to fix my past mistakes. 🔝

Just tested and it is working just fine. Thank you guys :)

w00t!! I just released https://github.com/storybooks/storybook/releases/tag/v5.1.0-alpha.26 containing PR #6502 that references this issue. Upgrade today to try it out!
Because it's a pre-release you can find it on the @next NPM tag.


Generalize data library and update data layer services

Changes

Comments

#403  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @forstmeier and the rest of your teammates on  Graphite


Crash stack is EMPTY!

I modified the ViewController.mm
- (IBAction) onCrash:(__unused id) sender {    char* ptr = (char*)-1;    *ptr = 10; }
- (IBAction) onCrash:(__unused id) sender {     std::string s;     s.resize(-1); }
and catch an empty crash stack! It seem KSCrash can only catch the general exception like "throw "someting happen!" ".

any result? I met the same question and don't know why?


feat: add iagon storage and general improvements.

:tada: This PR is included in version 1.15.0 :tada:
The release is available on<EMAIL_ADDRESS>Your semantic-release bot :package::rocket:


📝 Add verbose parsing failure log

This is a non-issue. Parsing failure was happening because Diagnostics was turned off on some TF builds. Closing!!


PHP out of memory error when calling Artisan commands

Laravel Version: 5.4.15
PHP Version: 7.1.3

Description:
PHP is throwing the following error when trying to deploy with envoyer:

php artisan optimize
PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 262144 bytes) in /home/forge/project/releases/20170327091815/vendor/laravel/framework/src/Illuminate/Container/Container.php on line 621
PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 262144 bytes) in Unknown on line 0
Script php artisan optimize handling the post-install-cmd event returned with error code 255

Steps To Reproduce:
It fails on various commands and I can't replicate it reliably however it can sometimes be fixed by changing debug to true in the .env file.

AFAIK Laravel Framework dropping optimize command since 5.4.

Okay but the php artisan optimize command is still in composer.json scripts. I also get this error when calling other artisan commands such as "php artisan storage:link".

Check all your ServiceProviders. You might be calling $this->register where you're suppose to call $this->app->register() and, thus, causing infinite recursion.

@anewmanjones check your code for any recursive calls and update us :)

How can you fix this bug?


Allow floating ip to be optional

For deployments where Direct Link or a VPN server will be used in the environment, we need a "Bastion" instance (perhaps more appropriately a "jump server" but don't need to expose the VSI via a floating IP address. In that case, apart from the floating ip address all of the logic provided for this module still holds.
It would be helpful to provide a flag like disable_public_ip which is defaulted to false. The output would need to be adjusted to return an empty string instead of a value for the public ip.

makes sense!

added in latest https://registry.terraform.io/modules/we-work-in-the-cloud/vpc-bastion/ibm/latest


Is there any option for relationship filter?

how do you filter collection field relationship? Are there any options?
i've managed to filter it by createdBy: userId, but what i want to achieve is to have, let say, i have a company(HQ) and my company has branches(branch), I have two collections, if i create a document (collection 1) and select the field from relation (collection 2), on which the creator of the document (collection 2) is from my branches.
My desired result is to be able to select that field relation along with all my documents that i've i created on collection 2. right now, i'm unable to do that. the available.
Here's my filter code:
 filter: function(userId) {
      var user = Meteor.users.findOne({"_id": userId},{fields: {profile: 1}});
      var roles = Roles.userHasRole(userId, 'HQ');
      if ( roles ) {
        console.log( "Hello HQ" );
        return { enrollmentId: user.profile.company };
      } else {
        console.log( "Hello Branch" );
        return { createdBy: userId };
      }

      }

i can see the console log message but my code didn't work.
all the branch created document should be available if HQ is the current user
but if branch is current user it should only be his own document

I've already managed to filter the relationship the i want.
filter: function(userId) {
      var user = Meteor.users.findOne({"_id": userId},{fields: {profile: 1}});
      var admin = Roles.userHasRole(userId, "admin");
      var hq = Roles.userHasRole(userId, 'HQ');
      var branch = Roles.userHasRole(userId, 'Branch');
      if ( admin ) {
       return {};
      } else if ( hq ) {
        return { company: user.profile.company };
      } else if ( branch ) {
        return { createdBy: userId };
      }
      }

If user is admin, it should return all documents, if user is hq, it should return all the documents within the company and its branches, if user is branch, return all the documents only he creates.


Add HTTP Proxy to ClientOptions

Feature request
Is your feature request related to a problem? Please describe.
I am accessing supabase from inside corporate network, which require all traffic to go through a HTTP Proxy. So I have to access Restful API through the Http Proxy. And I don't want to use Tun/Tap interface -> Http Proxy.
Describe the solution you'd like
An additional option to tunnel all supabase Restful API through a HTTP Proxy.
Describe alternatives you've considered
Turn or VPN -> Http Proxy, but it is suboptimal as it will affect all other application in my device.
Additional context
Behind corporate network, strict network.

Great. Thanks @4cecoder


Link to drivers

[Enter feedback here]
Hello. I think it would be very useful to have a link to the latest drivers for the Holos. I have 3 bricked units showing
QUSB_BULK_CID in the Device Manager under 'Other devices'. With the proper signed drivers this would be very easy to fix!
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: cd4de184-bdeb-2611-8d75-28376e30b0fc
Version Independent ID: 7b330f9a-d1c0-72f9-0d00-d7fac13e7e00
Content: Restart, reset, or recover HoloLens 2
Content Source: hololens/hololens-recovery.md
Product: hololens
Technology: windows
GitHub Login: @mattzmsft
Microsoft Alias: qianwen

Right click QUSB_BULK and try to update automatically.  This will probably fail, but can help move the process along.
Open up Settings and go to Update & Security.
Open Optional Updates and check for a Qualcomm driver.
Install the update (if available; it may take a hot minute for the driver to appear).
Check Device Manager and see if the device now enumerates under Ports as a Qualcomm HS-USB device.
Use ARC to recover device.
Hope and don't touch the device until it comes back to life.

You can also check out: Improving the update discoverability experience - Microsoft Tech Community


Updated and Added BackBone Labs Liquid Staked Assets.

Updated logos and information for BackBone Labs LSTs across the cosmos.

I noted an issue that needs correction, but otherwise this looks acceptable.

@JeremyParish69 I just noticed that there's another bJUNO token and it's conflicting on the mintscan website. for juno it shows 2 entries for bJUNO and has our logo but the contract address of the other bJUNO.
I am curious if there is another solution besides going by a different name?

IMO, it would be ideal for interfaces to show the names "BackBone Labs Liquid Staked JUNO" vs "StakeEasy bJUNO" to differentiate the assets, however there is no guarantee that users wouldn't confuse assets with a similar or identical ticker symbol.
The symbol of an asset is allowed to match another asset's symbol--the only property that guarantees disambiguation is the base denomination. Any improperly handled differentiation is the responsibility of which 3rd party app isn't displaying correctly.
Sounds like Mintscan aught to correct how they manage asset identifiers, and should be brought up with the Cosmostation team. I'm guessing that some automation they use scrapes the images from the chain registry, but then renames the image files copied to their own repo by symbol, causing any formerly scraped images to be overwritten by the last one.


Make another one

Can you make one for google cloud storage. I noticed that you made one for Azure also.

Awesome, please ping me once you release it so I can test it out and give recommendations if there is any.


angles option for polar chart

Hello,
This should fix #4751.
Demo here : https://jsfiddle.net/wanvfqbr/

It seems this feature is already implemented and tested by angle-array.json.
It's working and it's good enough for me (demo here : https://jsfiddle.net/h1e78vbq/).
We can close this PR and just update the documentation (see #6491)


Add Windows version to minium requirments

Maybe the people using Windows 7 will stop trying. I'm assuming the minimum is 8, correct me if I'm wrong.

The minimum's actually 8.1, not 8 (there's a distinction).
Otherwise sounds good, though I think you're probably being a little optimistic about it stopping people from showing up in #help.

At least they have a way of knowing without asking in #help and being told Win 7 is unsupported.

It's mentioned on Steam too which is where most of our players come from.


Annotations across multiple lines not showing up?

I have an annotation file like the following, generated by SQLFluff 3.0.5
[
    {"file": "high_injury_network/4_HIN/percent_x_percent.sql", "start_line": 12, "start_column": 22, "end_line": 12, "end_column": 31, "title": "SQLFluff", "message": "AL02: Implicit/explicit aliasing of columns.", "annotation_level": "failure"},
    {"file": "high_injury_network/4_HIN/percent_x_percent.sql", "start_line": 20, "start_column": 5, "end_line": 21, "end_column": 75, "title": "SQLFluff", "message": "LT09: Select targets should be on a new line unless there is only one select target.", "annotation_level": "failure"},
    {"file": "high_injury_network/4_HIN/percent_x_percent.sql", "start_line": 20, "start_column": 11, "end_line": 20, "end_column": 12, "title": "SQLFluff", "message": "LT02: Expected line break and indent of 8 spaces before 'SUM'.", "annotation_level": "failure"},
    {"file": "high_injury_network/4_HIN/percent_x_percent.sql", "start_line": 30, "start_column": 1, "end_line": 31, "end_column": 56, "title": "SQLFluff", "message": "LT09: Select targets should be on a new line unless there is only one select target.", "annotation_level": "failure"}
]

I think I've noticed a pattern that where start_line == end_line everything seems to work fine and the annotation shows up as expected. But where that's not true, for annotations referencing multiple lines, the action still fails (as it should), but the annotations are just not shown. It's really hard to debug these!
For context, the full Github action I'm using is here.

Possibly a bug somewhere further down the line?
https://github.com/orgs/community/discussions/122594


Add Install instructions at the top

Good idea, thanks :) One day I'll get around to rewrite the introductory page and create a better documentation webpage (not happy with the layout and I have now a better idea what fips actually is for the introduction page) ;)


DayPlanner timeline empty after new Daily Periodic Note created

I've run into this every day the last week or two. Obsidian will have been open for a while. I sit down for the day, create my new daily note, and the DayPlanner panel will stay empty until I restart or reload the app.
Steps to reproduce the behavior:

Create a new daily note (I typically do this with the Action URI plugin, which "Actions for Obsidian uses". I haven't tested this with another way yet)
The new note is based on a template with several stock items already in it
See that the sidebar is empty

Screenshots

An interesting thing to note, the specific DayPlanner error in the console also appears when reloading or restarting the app...so I'm not sure that's the problem. Maybe it's the interaction between creating a new note with the Actions URI plugin? I'll make tomorrow's note internally to confirm

I second that. Obsidian restart is needed to populate the timeline.

I have the same issue. I never restart my computer, so I have to restart Obsidian every day after I amke the daily note in order to see timeline.

I really love this plugin. But I think many people have same issue. So This issue should be solved as soon as possible.
Same issue
#396 issue
https://github.com/ivan-lednev/obsidian-day-planner/issues/369#issue-2145741609
372 issue
https://github.com/ivan-lednev/obsidian-day-planner/issues/372#issue-2150227700

Hello!
Please update and re-check.

It works for me, thank you !

It works well. Thank you!.
BTW, the console error is not solved.
Uncaught (in promise) TypeError: Cannot read properties of null (reading 'children')
    at t.getSideLeaf (app.js:1:2025424)
    at t.getRightLeaf (app.js:1:2024205)
    at DayPlanner.initTimelineLeafSilently (plugin:obsidian-day-planner:48925:32)
    at async DayPlanner.onload (plugin:obsidian-day-planner:48959:5)

@ivan-lednev
I'm guessing it's not a version problem,
the Task timeline display error when I automatically update 0.20.2 in ob.
But when I manually download 0.20.1 and replace the original files, the timeline is displayed correctly, and I try to download 0.20.2 again and replace it manually, it is still displayed correctly.
I'll leave a comment if I find new anything. For the time being, this problem can probably be solved by manual download and replace old files!

Hey, @kin30528, could you update and re-check?

嘿， @kin30528，您可以更新並重新檢查嗎？

@ivan-lednev thank you, its working, wonderful~~:D


feat: remove help v4 entries

Removed the help_v4 variable from the help extension as it is never used.

Can you also remove it from metadata.yml?

I suppose there's more stuff to remove then.

I removed all references to this, so as it is now completely unavailable.

Looks good to me, merging.


Sould I add another Kdrama Quiz page?

Sure.
You will have to add a js file(with new questions of the drama), css file, drama_name.html file and make necessary changes like add an extra segment in the index.html file. Please provide screenshots of the altered webpage when making the pull request so that I can see what changes have been made. The other js files have the template of question. You would just have to alter. If you planning to add more sections. Send screenshots of those too.
Good luck!!


add option of outputting doc attributes to crates + a doc fetching tool

 Issue by thestinger
Wednesday May 01, 2013 at 22:16 GMT
For earlier discussion, see https://github.com/rust-lang/rust/issues/6160
This issue was labelled with: A-an-interesting-project, A-docs, A-tools in the Rust repository

Similar to Python's pydoc tool, it should just take a path and resolve it to the correct docstring. The REPL could also take advantage of this with a :help meta-command.

This seems almost like a dupe of #647, or at least very very closely related.

Yeah, I decided to import them separately, but they're very, very similar.

As someone who tries to stay as close to the command line as possible, I am going to take this as my first rust project.
My current approach will be:

write or use a library that can parse rust source and convert it into HashMaps of structs. So if you have:

/// this is a function
/// more info about the function
/// # Examples
/// ```
/// let x = myfun(67)
/// ```
fn myfun(x: i32) -> i32 { ... }

You would get a struct like
Doc {
    name: "myfun",
    type: Fn,
    doc: "this is a function\nmore info about the function...", // raw documentation
    sig: "fn myfun(x: i32) -> i32",
    term: &str, // This will be converted to display nicely on a terminal (i.e. color sequences, bold, etc)
    html: &str, // converted to html for other tools
}

Do you know if something like this exists?

the user will specify their cargo and rust source directory. Whenever the user runs the docsearch tool, it will check that the crate/rustsource versions are the same as before -- if they aren't it will reparse only what changed. Parsed data will be stored in an sqllite database.
user queries will be converted to sql queries and parsed, then displayed from the "term" block

I just finished rustbyexample.com and not having a command line doctool was one of my biggest pain points, so I am going to go forth! Would love any feedback on the design.

Aaand, obviously I should be using the rustdoc library for the parsing, which is what I will be doing.
I think my larger goal is to be able to integrate with editor tools so that it is fairly painless to display documentation dynamically (including for the library you are currently working on).

Just letting people know that I'm working on such a tool, oxidoc. Feedback on the current design and contributions are highly encouraged.

oxidoc is no longer maintained as said in the referenced oxidoc issue. It is no longer able to work with the current rust version. Can this issue be reopen?

+1 for re-opening this issue. I personally work on a fairly slow computer, and working in a virtual terminal keeps everything fast and snappy. Not to mention that it's just more convenient to have the docs just print to stdout than to get kicked into another application that may or may not be a hassle to use.
stares at elinks

I was developing C a little earlier this week and was reminded:

How much I hate C
But how nice it is to have terminal manpages for at least the standard library

Not having to open up a browser to check the syntax for say clap for the 100th time would be extremely handy.
As mentioned before, Oxidoc is no longer maintained so it would be really nice to have some official support.

@DarrienG I happen to agree! Here is an issue that was closed in February about it: https://github.com/rust-lang/rust/issues/68870

Opening this issue doesn't really change anything; issues in the RFC repo aren't how work is tracked. The most productive way forward for interested parties here is to try to build such a thing, and then see what interfaces are needed, and then write an RFC to get them stabilized.

I’m working on a command-line viewer for rustdoc documentation, rusty-man.  Currently, it parses the HTML documentation, but of course it would be much better to have some standardized format.  I’d like to help working on such interfaces, but I think someone with more experience with the librustdoc implementation and RFCs should take the lead.


Global variables that store limits

It would be nice to access things like component time limits via a Python API, rather than defining constants ourselves that we have to keep up to date.

Fixed with bot settings (https://docs.meya.ai/docs/bot-settings)


update gSAIL v1(deprecated(2021/08/20)) and add gSAIL v2

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address: Gsai2KN28MTGcSZ1gKYFswUpFpS7EM9mvdR9c8f6iVXJ
Token Name: SolanaSail Governance Token V2
Token Symbol: gSAIL
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token: https://www.solanasail.com
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Close for conflicts reason, will do a new PR


Consume Docker image versions using manifest.json published by Legend

Consume Docker image versions using manifest.json published by Legend (see https://github.com/finos/legend/blob/master/releases/2021-10-18/manifest.json and https://github.com/canonical/charmhub-upload-action

This was added to the legend-juju-bundle repo: https://github.com/finos/legend-juju-bundle/pull/9


Does it support representing forces by means of arrows on sketches?

If it can support representing forces by means of arrows on sketches,we can change the virtual to the real.It will be more vivid.

Closing the issue since there's no response for a while. Feel free to re-open.


Documentation Update

For easier understanding, kindly add to documentation that this middleware does not override the server's default timeout.
In case of the setting timeouts greater than the default of 120000 ms, the usage shall be as below
var express = require('express')
var timeout = require('connect-timeout')
var app = express();
let SERVER_TIMEOUT = 300000;
app.use(timeout((SERVER_TIMEOUT/1000)+"s"))
//Routers here
let server = app.listen(3000);
server.timeout = SERVER_TIMEOUT;
(or)
other better examples.
It could just save a lot of time for the beginners.

Hi! Thanks for the feedback. Writing good doximentation is hard, especially when the person writing it takes their own knowledge for granted and it becomes blinders, not even realizing there is something a prospective user may not know. Sorry for the pain you went though. I'm not sure how to make it better, but maybe would you be willing to make a pull request with your thoughts on the changes that would have helped you through the journey you had?

In that case why is it also necessary to set "server.timeout"?

In that case why is it also necessary to set "server.timeout"?

node.js default (http) server timeout is 120 sec. Requests would hit this limit before connect-timeout's limit.

I noticed that in one of my CentOS Linux 7 environments (Not all of them), the following does not have any effect over the default 30 second express timeout:
app.use(timeout(90000))
Where as the following does have an effect:
app.use(timeout('90s'))
Versions:
express: ^4.15.1
connection-timeout: 1.9.0
Node: 8.12.0
npm: 6.4.1
In the documentation it says both argument formats should work (As it does in most of my environments).
Is there any other reason that the first format should not work?
Thanks!

PR #30 was closed (Link for extra context), same for this issue.


Compatibility List

I think it'd be a good idea to consolidate a "Compatibility List" since napping some apps will cause them to hang indefinitely unless the script is killed and restarted. I use iTerm2 and made the mistake of doing the default "nap everything" setting. It napped even the calling shell so that caused some issues lol.

Good idea! I have a list going in the script, but I'll add iTerm2 to it too.


fix wrong endpoint

as the endpoint requires app specific tenant candos it must be below /apps for the correct cando determination

@SCjona requires frontend change for used endpoint
DELETE /api/v1/access_control/tenant/:tenant_id/users/:user_id
must be changed to
DELETE /api/v1/access_control/apps/:app_id/tenant/:tenant_id/users/:user_id


ISourceCache.KeySelector

What kind of change does this PR introduce?
Adds a public getter for the KeySelector func that a SourceCache uses for retrieving keys from objects.
What is the current behavior?
A user of a cache has no way to determine how a key is retrieved from an object by the cache.  A user must be fed the same func in parallel alongside the cache to do any intelligent logic that needs to align and get the same keys.
What is the new behavior?
A getter only property is exposed by ISourceCache to give the user access to the func used internally.
What might this PR break?
I don't think it will break any code, but may or may not have undesirable API exposure effects.
Other information:
I think the main discussion will probably just be around whether this should be exposed or not.  A user might want to give a cache a key selector "in secret", and/or intend the key selector to only be used by the cache, for some reason.  In these cases, exposing the func to an outside user via the interface will allow outside users to call the func in unexpected ways.
I think the chances of that scenario are pretty low.  So the main issue might just be cluttering the interface.
I do think the change will make some operations/logic much more robust, as the Key Selector doesn't have to be passed around in parallel with a cache in order to be used.  The cache -knows- what selector it's using, it's just currently not telling anybody.
Here's an example snippet.  This whole thing may be obsolete and better handled a different way, but let's use it for example anyway:
public static void SetTo<V, K>(this ISourceCache<V, K> cache, Func<V, K> keySelector, IEnumerable<V> items, SetToEnum setTo = SetToEnum.Whitewash)
{
    if (setTo == SetToEnum.Whitewash)
    {
        cache.Clear();
        cache.AddOrUpdate(items);
        return;
    }
    var toRemove = new HashSet<K>(cache.Keys);
    var keyPairs = items.Select(i => new KeyValuePair<K, V>(keySelector(i), i)).ToArray();
    toRemove.Remove(keyPairs.Select(kv => kv.Key));
    cache.Remove(toRemove);
    switch (setTo)
    {
        case SetToEnum.SkipExisting:
            foreach (var item in keyPairs)
            {
                var lookup = cache.Lookup(item.Key);
                if (!lookup.HasValue)
                {
                    cache.AddOrUpdate(item.Value);
                }
            }
            break;
        case SetToEnum.SetExisting:
            cache.AddOrUpdate(items);
            break;
        default:
            throw new NotImplementedException();
    }
}

I would prefer to be able to remove the need for a keySelector parameter here, as it should be an implicit property of the cache, in my opinion.
Needing to provide a keySelector to this extension function actually increases the potential for mistakes, as a misaligned keySelector (one that the cache isn't actually using) will result in bad results.  The user needs to ensure the keySelectors match, but has no way of confirming this whatsoever.
Being able to just ask the cache what selector it is using, and utilize that for the logic would be much safer and easier to use.

I could see you guys taking or leaving the API change, but I think having the discussion here in a PR is nicer than in slack or wherever else.

Also, I'm not sure if ISourceCache is the best place for the exposure, if done at all.  Could be trickled up to some higher level cache interfaces, if that is felt to be a better location for it.

This looks good to me.


Snapshots and opportunity for distributions

Please take with a grain of salt my words, I'm not an expert in CRDT.
Feel free to point me in the right direction to let me learn more.
If I understood correctly the specification, peritext relays on the following mechanism:

The creation of a sequence, named trough ids
The micro split in log fashion, for each typed (and "clicked") input
The concept of actions, with descriptors such a selection

As emacs user and not per-se the average user, I see too many challenges to consume it.
peritext is builded around how the user provides the input and less how files changes over time.
And since seems to solve Conflict Resolution trough UX.
I imagine that peritext rather than be hooked to an editor, could be run as service like a Language Server Protocol, which runs in background while I'm editing a file.
I will then expect to solve the following:

understands the action that I'm doing to it, by just saving the file and compare the in-memory difference.
allows me to specifically "publish" my changes.
notifies when someone pushes changes and allows me to merge them, interactively when ambiguous.

A bit like git, but without an actual user input, beside saving a file.
If the concept of "publish" exists, snapshot would be cheaper to share.
And if peritext would leverage the LSP architecture could take advantage at the integration with existing editors.
Hoping this wasn't a waste of your time.

Hi @M3kH, Peritext (and other CRDTs) record the individual operations that a user performed, because that allows us to better capture the exact user input and hence the intention of the user's edits. You're right that it is designed for an environment where fine-grained (keystroke by keystroke) editing operations are available directly from the text editor.
It is still possible to use Peritext in conjunction with a text editor that does not provide keystroke-granularity editing operations: in that case you'd need to diff the previous version and the current version of the file, and then apply the necessary deletion operations to the CRDT in order to transform it from the old state into the new state. There are various existing text diffing libraries you can use for this, so we're leaving diffing out of scope for Peritext.
It is possible to integrate with editors such as VSCode and get keystroke-granularity edits in that way; see vscode-automerge-tracker as a proof of concept.


[release-4.12] Update OWNERS

Update OWNERS to current team members

/assign @akram @divyansh42

/lgtm

/jira refresh


Fix matchBiometric and unmatchBiometric commands

The matchBiometric and unmatchBiometric commands failed because of an incorrect parenthesis.
The correct commands are --matchFace or --matchFinger, see https://github.com/wix/AppleSimulatorUtils

The biometrics functionality was introduced with https://github.com/wix/Detox/pull/1554 and https://github.com/wix/Detox/pull/1547

[x] This is a small change
[ ] This change has been discussed in issue #<?> and the solution has been agreed upon with maintainers.

Description:
Using the biometrics commands caused errors on my computer. I fixed them with this PR.
Fyi, using await device.matchFinger(); still fails on my computer with the timeout below. I could not yet find the reason why. There may be additional errors that need fixing.
    1) with his matching finger
detox[71526] WARN:  [Client.js/PENDING_REQUESTS] App has not responded to the network requests below:
  (id = 12) waitForBackground: {}

That might be the reason why the test "Login with the correct fingerprint with his matching finger" has timed out.

  1 passing (6m)
  1 failing

  1) Login with the correct fingerprint
       with his matching finger:
     Error: Timeout of 280000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (e2e/tests/login.test.js)

Thanks!


docs: :memo: 更新 README 和官网文档首页头图

👀 PR includes

🔧 Chore

[ ] Test case
[x] Docs / demos update
[ ] CI / workflow
[ ] Release version
[ ] Other ()

🖼 Screenshot

:tada: This PR is included in version @antv/s2-v1.4.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Snowflake check not loading in agent 7.42.0 - Check snowflake not found in Catalog

The snowflake integration 4.4.5 fails to load on Datadog Agent 7.42.0.
With the same conf.yaml file, the check works fine on Agent 7.40.0 with integration version 4.4.4.
Additional environment details (Operating System, Cloud provider, etc):
Debian 11 on EC2.
Steps to reproduce the issue:

Install datadog-agent 7.42.0 (latest) on Debian 11
Configure /etc/datadog-agent/conf.d/snowflake.d/conf.yaml as follows:

init_config:
instances:
  - account: 'myaccount'
    username: DATADOG_USER
    password: 'mypassword'
    role: DATADOG
    min_collection_interval: 3600

Describe the results you received:
From datadog-agent status:
  Loading Errors
  ==============
    snowflake
    ---------
      Core Check Loader:
        Check snowflake not found in Catalog

      JMX Check Loader:
        check is not a jmx check, or unable to determine if it's so

      Python Check Loader:
        unable to import module 'snowflake': No module named 'snowflake'

Describe the results you expected:
The check to run successfully, as it did on agent 7.40.0.
Additional information you deem important (e.g. issue happens only occasionally):
Output from datadog-agent check snowflake -l debug:
2023-02-01 16:52:43 UTC | CORE | WARN | (pkg/util/log/log.go:618 in func1) | Unknown key in config file: force_tls_12
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/util/log/log.go:557 in func1) | FIPS mode is disabled
2023-02-01 16:52:43 UTC | CORE | INFO | (pkg/util/log/log.go:590 in func1) | Features detected from environment:
2023-02-01 16:52:43 UTC | CORE | INFO | (pkg/util/log/log.go:585 in func1) | process_config.enabled is deprecated, use process_config.container_collection.enabled and process_config.process_collection.enabled instead, see https://docs.datadoghq.com/infrastructure/process#installation for more information
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/util/hostname/providers.go:161 in GetWithProvider) | trying to get hostname from 'configuration' provider
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/util/hostname/providers.go:168 in GetWithProvider) | unable to get the hostname from 'configuration' provider: hostname is empty
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/util/hostname/providers.go:161 in GetWithProvider) | trying to get hostname from 'hostnameFile' provider
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/util/hostname/providers.go:168 in GetWithProvider) | unable to get the hostname from 'hostnameFile' provider: 'hostname_file' configuration is not enabled
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/util/hostname/providers.go:161 in GetWithProvider) | trying to get hostname from 'fargate' provider
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/util/hostname/providers.go:168 in GetWithProvider) | unable to get the hostname from 'fargate' provider: agent is not runnning on Fargate
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/util/hostname/providers.go:161 in GetWithProvider) | trying to get hostname from 'gce' provider
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/config/config.go:1864 in IsCloudProviderEnabled) | cloud_provider_metadata is set to [aws gcp azure alibaba oracle ibm] in agent configuration, trying endpoints for GCP Cloud Provider
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/util/hostname/providers.go:168 in GetWithProvider) | unable to get the hostname from 'gce' provider: unable to retrieve hostname from GCE: GCE metadata API error: status code 404 trying to GET http://<IP_ADDRESS>/computeMetadata/v1/instance/hostname
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/util/hostname/providers.go:161 in GetWithProvider) | trying to get hostname from 'azure' provider
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/util/hostname/providers.go:168 in GetWithProvider) | unable to get the hostname from 'azure' provider: azure_hostname_style is set to 'os'
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/util/hostname/providers.go:161 in GetWithProvider) | trying to get hostname from 'fqdn' provider
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/util/hostname/providers.go:168 in GetWithProvider) | unable to get the hostname from 'fqdn' provider: 'hostname_fqdn' configuration is not enabled
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/util/hostname/providers.go:161 in GetWithProvider) | trying to get hostname from 'container' provider
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/util/hostname/providers.go:168 in GetWithProvider) | unable to get the hostname from 'container' provider: the agent is not containerized
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/util/hostname/providers.go:161 in GetWithProvider) | trying to get hostname from 'os' provider
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/util/hostname/providers.go:172 in GetWithProvider) | hostname provider 'os' successfully found hostname 'prod1-grey-datadog-checks-i0182abe4bf0f7166b'
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/util/hostname/providers.go:161 in GetWithProvider) | trying to get hostname from 'aws' provider
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/config/config.go:1864 in IsCloudProviderEnabled) | cloud_provider_metadata is set to [aws gcp azure alibaba oracle ibm] in agent configuration, trying endpoints for AWS Cloud Provider
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/config/config.go:1864 in IsCloudProviderEnabled) | cloud_provider_metadata is set to [aws gcp azure alibaba oracle ibm] in agent configuration, trying endpoints for AWS Cloud Provider
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/util/ecs/metadata/clients.go:65 in V1) | ECS metadata v1 client init error: temporary failure in ecsutil-meta-v1, will retry later: could not detect ECS agent, tried URLs: [http://localhost:51678/]
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/util/hostname/providers.go:168 in GetWithProvider) | unable to get the hostname from 'aws' provider: not retrieving hostname from AWS: the host is not an ECS instance and other providers already retrieve non-default hostnames
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/aggregator/demultiplexer_agent.go:142 in initAgentDemultiplexer) | Creating forwarders
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/epforwarder/epforwarder.go:261 in newHTTPPassthroughPipeline) | Initialized event platform forwarder pipeline. eventType=dbm-samples mainHosts=dbquery-intake.datadoghq.eu additionalHosts= batch_max_concurrent_send=10 batch_max_content_size=5000000 batch_max_size=1000, input_chan_size=100
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/epforwarder/epforwarder.go:261 in newHTTPPassthroughPipeline) | Initialized event platform forwarder pipeline. eventType=dbm-metrics mainHosts=dbm-metrics-intake.datadoghq.eu additionalHosts= batch_max_concurrent_send=10 batch_max_content_size=20000000 batch_max_size=1000, input_chan_size=100
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/epforwarder/epforwarder.go:261 in newHTTPPassthroughPipeline) | Initialized event platform forwarder pipeline. eventType=dbm-activity mainHosts=dbm-metrics-intake.datadoghq.eu additionalHosts= batch_max_concurrent_send=10 batch_max_content_size=20000000 batch_max_size=1000, input_chan_size=100
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/epforwarder/epforwarder.go:261 in newHTTPPassthroughPipeline) | Initialized event platform forwarder pipeline. eventType=network-devices-metadata mainHosts=ndm-intake.datadoghq.eu additionalHosts= batch_max_concurrent_send=10 batch_max_content_size=5000000 batch_max_size=1000, input_chan_size=100
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/epforwarder/epforwarder.go:261 in newHTTPPassthroughPipeline) | Initialized event platform forwarder pipeline. eventType=network-devices-snmp-traps mainHosts=snmp-traps-intake.datadoghq.eu additionalHosts= batch_max_concurrent_send=10 batch_max_content_size=5000000 batch_max_size=1000, input_chan_size=100
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/epforwarder/epforwarder.go:261 in newHTTPPassthroughPipeline) | Initialized event platform forwarder pipeline. eventType=network-devices-netflow mainHosts=ndmflow-intake.datadoghq.eu additionalHosts= batch_max_concurrent_send=10 batch_max_content_size=5000000 batch_max_size=10000, input_chan_size=10000
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/aggregator/demultiplexer_agent.go:189 in initAgentDemultiplexer) | the Demultiplexer will use 1 pipelines
2023-02-01 16:52:43 UTC | CORE | INFO | (pkg/aggregator/time_sampler.go:46 in NewTimeSampler) | Creating TimeSampler #0
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/aggregator/demultiplexer_agent.go:287 in Run) | Starting forwarders
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/aggregator/demultiplexer_agent.go:309 in Run) | not starting the container lifecycle forwarder
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/aggregator/demultiplexer_agent.go:318 in Run) | Forwarders started
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/aggregator/demultiplexer_agent.go:343 in flushLoop) | flushInterval set to 0: will never flush automatically
2023-02-01 16:52:43 UTC | CORE | INFO | (pkg/workloadmeta/store.go:392 in startCandidates) | workloadmeta collector "ecs" could not start. error: component workloadmeta-ecs is disabled: Agent is not running on Docker
2023-02-01 16:52:43 UTC | CORE | INFO | (pkg/workloadmeta/store.go:392 in startCandidates) | workloadmeta collector "cloudfoundry-vm" could not start. error: component workloadmeta-cloudfoundry-vm is disabled: Agent is not running on CloudFoundry
2023-02-01 16:52:43 UTC | CORE | INFO | (pkg/workloadmeta/store.go:392 in startCandidates) | workloadmeta collector "docker" could not start. error: component workloadmeta-docker is disabled: Agent is not running on Docker
2023-02-01 16:52:43 UTC | CORE | INFO | (pkg/workloadmeta/store.go:392 in startCandidates) | workloadmeta collector "kube_metadata" could not start. error: component workloadmeta-kube_metadata is disabled: Agent is not running on Kubernetes
2023-02-01 16:52:43 UTC | CORE | INFO | (pkg/workloadmeta/store.go:392 in startCandidates) | workloadmeta collector "containerd" could not start. error: component workloadmeta-containerd is disabled: Agent is not running on containerd
2023-02-01 16:52:43 UTC | CORE | INFO | (pkg/workloadmeta/store.go:392 in startCandidates) | workloadmeta collector "podman" could not start. error: component workloadmeta-podman is disabled: Podman not detected
2023-02-01 16:52:43 UTC | CORE | INFO | (pkg/workloadmeta/store.go:392 in startCandidates) | workloadmeta collector "kubelet" could not start. error: component workloadmeta-kubelet is disabled: Agent is not running on Kubernetes
2023-02-01 16:52:43 UTC | CORE | INFO | (pkg/workloadmeta/store.go:392 in startCandidates) | workloadmeta collector "cloudfoundry-container" could not start. error: component workloadmeta-cloudfoundry-container is disabled: Agent is not running on CloudFoundry
2023-02-01 16:52:43 UTC | CORE | INFO | (pkg/workloadmeta/store.go:392 in startCandidates) | workloadmeta collector "ecs_fargate" could not start. error: component workloadmeta-ecs_fargate is disabled: Agent is not running on Fargate
2023-02-01 16:52:43 UTC | CORE | INFO | (pkg/workloadmeta/store.go:153 in Start) | workloadmeta store initialized successfully
2023-02-01 16:52:43 UTC | CORE | INFO | (pkg/collector/python/init.go:322 in resolvePythonExecPath) | Using '/opt/datadog-agent/embedded' as Python home
2023-02-01 16:52:43 UTC | CORE | DEBUG | (pkg/collector/python/init.go:376 in Initialize) | Using '/opt/datadog-agent/embedded/bin/python3' as Python interpreter path
2023-02-01 16:52:43 UTC | CORE | INFO | (pkg/collector/python/init.go:389 in Initialize) | Initializing rtloader with Python 3 /opt/datadog-agent/embedded
2023-02-01 16:52:43 UTC | CORE | INFO | (pkg/tagger/collectors/workloadmeta_main.go:115 in stream) | workloadmeta tagger collector started
2023-02-01 16:52:44 UTC | CORE | INFO | (pkg/collector/python/datadog_agent.go:127 in LogMessage) | - | (ddyaml.py:143) | monkey patching yaml.load...
2023-02-01 16:52:44 UTC | CORE | INFO | (pkg/collector/python/datadog_agent.go:127 in LogMessage) | - | (ddyaml.py:147) | monkey patching yaml.load_all...
2023-02-01 16:52:44 UTC | CORE | INFO | (pkg/collector/python/datadog_agent.go:127 in LogMessage) | - | (ddyaml.py:151) | monkey patching yaml.dump_all... (affects all yaml dump operations)
2023-02-01 16:52:44 UTC | CORE | INFO | (pkg/collector/collector.go:56 in NewCollector) | Embedding Python 3.8.16 (default, Jan 18 2023, 20:37:07) [GCC 4.9.2]
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/collector/collector.go:57 in NewCollector) | Python Home: /opt/datadog-agent/embedded
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/collector/collector.go:58 in NewCollector) | Python path: ['/opt/datadog-agent/embedded/lib/python38.zip', '/opt/datadog-agent/embedded/lib/python3.8', '/opt/datadog-agent/embedded/lib/python3.8/lib-dynload', '/opt/datadog-agent/embedded/lib/python3.8/site-packages', '/opt/datadog-agent/embedded/lib/python3.8/site-packages/setuptools-40.9.0.post20230118-py3.8.egg', '/opt/datadog-agent/embedded/lib/python3.8/site-packages/pip-21.3.1-py3.8.egg', '/opt/datadog-agent/bin/agent/dist', '/opt/datadog-agent/checks.d', '/opt/datadog-agent/bin/agent/dist/checks.d', '/etc/datadog-agent/checks.d']
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/collector/collector.go:66 in NewCollector) | Collector up and running!
2023-02-01 16:52:44 UTC | CORE | INFO | (pkg/autodiscovery/providers/config_reader.go:170 in read) | Searching for configuration files at: /etc/datadog-agent/conf.d
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/activemq.d/metrics.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/apache.d/auto_conf.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/cassandra.d/metrics.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/cert_manager.d/auto_conf.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/check_splitdb_daily_backup.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/check_swift.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/cilium.d/auto_conf.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/confluent_platform.d/metrics.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/consul.d/auto_conf.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/container.d/conf.yaml.default
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/containerd.d/conf.yaml.default
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/coredns.d/auto_conf.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/couch.d/auto_conf.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/couchbase.d/auto_conf.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/cpu.d/conf.yaml.default
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/cri.d/conf.yaml.default
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/database_connection_type.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/database_size_metrics.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/database_user_connections.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/datadog_cluster_agent.d/auto_conf.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/disk.d/conf.yaml.default
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/docker.d/conf.yaml.default
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/ecs_fargate.d/conf.yaml.default
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/eks_fargate.d/conf.yaml.default
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/elastic.d/auto_conf.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/etcd.d/auto_conf.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/external_dns.d/auto_conf.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/file_handle.d/conf.yaml.default
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/harbor.d/auto_conf.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/hazelcast.d/metrics.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/hive.d/metrics.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/hivemq.d/metrics.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/http_check.d/alb.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/http_check.d/ssl.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/hudi.d/metrics.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/ignite.d/metrics.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/io.d/conf.yaml.default
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/istio.d/auto_conf.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/jboss_wildfly.d/metrics.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/journald.d/conf.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/kafka.d/metrics.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/kube_apiserver_metrics.d/auto_conf.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/kube_controller_manager.d/auto_conf.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/kube_dns.d/auto_conf.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/kube_scheduler.d/auto_conf.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/kubelet.d/conf.yaml.default
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/kubernetes_state.d/auto_conf.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/kyototycoon.d/auto_conf.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/load.d/conf.yaml.default
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/mcache.d/auto_conf.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/memory.d/conf.yaml.default
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/mysql.d/conf.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/network.d/conf.yaml.default
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/ntp.d/conf.yaml.default
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/presto.d/auto_conf.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/presto.d/metrics.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/redisdb.d/auto_conf.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/riak.d/auto_conf.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/sftp_file_count.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/snmp.d/auto_conf.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/snowflake.d/conf.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/solr.d/metrics.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/sonarqube.d/metrics.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/tomcat.d/auto_conf.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/tomcat.d/metrics.yaml
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/uptime.d/conf.yaml.default
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/providers/config_reader.go:294 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/weblogic.d/metrics.yaml
2023-02-01 16:52:44 UTC | CORE | INFO | (pkg/autodiscovery/providers/config_reader.go:170 in read) | Searching for configuration files at: /opt/datadog-agent/bin/agent/dist/conf.d
2023-02-01 16:52:44 UTC | CORE | WARN | (pkg/autodiscovery/providers/config_reader.go:174 in read) | Skipping, open /opt/datadog-agent/bin/agent/dist/conf.d: no such file or directory
2023-02-01 16:52:44 UTC | CORE | INFO | (pkg/autodiscovery/providers/config_reader.go:170 in read) | Searching for configuration files at:
2023-02-01 16:52:44 UTC | CORE | WARN | (pkg/autodiscovery/providers/config_reader.go:174 in read) | Skipping, open : no such file or directory
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/autodiscovery/autoconfig.go:296 in addListenerCandidates) | Listener environment was registered
2023-02-01 16:52:44 UTC | CORE | INFO | (pkg/autodiscovery/autoconfig.go:310 in initListenerCandidates) | environment listener successfully started
2023-02-01 16:52:44 UTC | CORE | INFO | (pkg/autodiscovery/config_poller.go:168 in collectOnce) | file provider: collected 67 new configurations, removed 0
2023-02-01 16:52:44 UTC | CORE | INFO | (pkg/autodiscovery/autoconfig.go:204 in LoadAndRun) | Started config provider "file"
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/collector/scheduler.go:65 in InitCheckScheduler) | Added JMX Check Loader to Check Scheduler
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/collector/scheduler.go:65 in InitCheckScheduler) | Added Python Check Loader to Check Scheduler
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/collector/scheduler.go:65 in InitCheckScheduler) | Added Core Check Loader to Check Scheduler
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/collector/scheduler.go:171 in getChecks) | Loading check instance for check 'snowflake' using default loaders
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/collector/python/loader.go:123 in Load) | Performing platform loading prep
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/collector/python/loader.go:152 in Load) | Unable to load python module - datadog_checks.snowflake: unable to import module 'datadog_checks.snowflake': Traceback (most recent call last):
  File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/snowflake/__init__.py", line 14, in <module>
    from .check import SnowflakeCheck
  File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/snowflake/check.py", line 6, in <module>
    import snowflake.connector as sf
ModuleNotFoundError: No module named 'snowflake'
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/collector/python/loader.go:152 in Load) | Unable to load python module - snowflake: unable to import module 'snowflake': No module named 'snowflake'
2023-02-01 16:52:44 UTC | CORE | DEBUG | (pkg/collector/python/loader.go:160 in Load) | PyLoader returning unable to import module 'snowflake': No module named 'snowflake' for snowflake
2023-02-01 16:52:44 UTC | CORE | ERROR | (pkg/collector/scheduler.go:201 in getChecks) | Unable to load a check from instance of config 'snowflake': JMX Check Loader: check is not a jmx check, or unable to determine if it's so; Python Check Loader: unable to import module 'snowflake': No module named 'snowflake'; Core Check Loader: Check snowflake not found in Catalog

Error: could not load snowflake:
* JMX Check Loader: check is not a jmx check, or unable to determine if it's so
* Python Check Loader: unable to import module 'snowflake': No module named 'snowflake'
* Core Check Loader: Check snowflake not found in Catalog
Error: no valid check found

I updated to agent 7.42.1 with Snowflake integration 4.4.6 and the issue has been resolved.


add compile flag for number parsing functions

disabling tests in case of providing number parsing function (only build library)

I agree with the changes removing numberparse.h

Disabling tests is disappointing - and apparently unnecessary?

I do not understand the need for a compile time flag.  If numberparse is specific to tests, then move that module to a "libtest.a"

My fault. Just removed the exclusion.

If i'd like to use UniValue in a non bitcoin-core project, i require the ParseIntXXX() functions and therefor i'd like to have these functions within libunivalue.a. In case of bitcoin-core, we wan't to avoid having duplicated symbols... Do you see a better way? Copy the source code and rename/namespace the parsing function?

OK.  Looks good once comment is fixed.


Not all import errors should be under the same rollbar entry

There has been no activity on this issue for more several months. We are closing it. If you think this still needs to be addressed please open a new issue.


Add a separate section for FAQs

Description:
We need a dedicated FAQ page to provide users with answers to common questions about contributing to open-source projects and mastering web development. This page should improve user experience by offering easily accessible information.
Features:
A list of frequently asked questions categorized by topics (e.g., contributions, project guidelines, learning resources).
Clear, concise answers to help users navigate the platform.
A search bar or filter to quickly find relevant FAQs.
Task List:
Design the layout for the FAQ page.
Add categories for FAQs.
Implement a search/filter function for ease of use.
Ensure responsiveness and accessibility.

someone is already working on it


Please add Distributed Map

https://aws.amazon.com/blogs/aws/step-functions-distributed-map-a-serverless-solution-for-large-scale-parallel-data-processing/
Can we add distributed map state into SDK? Thank you.

This is a :rocket: Feature Request

I can't believe this feature is not created yet , did the maintainers already stopped working on this repo ??


How to create a SAPUI5 library?

I'm looking to create a SAPUI5 library that can be utilized by multiple SAPUI5 applications, all of which are hosted in SAP Business Technology Platform (BTP). My main question is regarding the process of creating this library and deploying it on SAP BTP. I've been searching for official documentation on this topic, but I haven't been able to find any comprehensive resources.
I did come across information on how to achieve this using SAP Web IDE, but what I'm specifically interested in is understanding how to configure the library manually so that I can deploy and consume it within a BTP environment without relying on Web IDE. Any guidance or pointers to relevant official documentation would be greatly appreciated.
Thank you!

Hello @CosminPascal ,
You may find this information helpful:
https://blogs.sap.com/2022/11/01/build-and-deploy-ui5-freestyle-applications-to-sap-btp-cloud-foundry-environment/
https://blogs.sap.com/2020/10/16/using-ui5-libraries-in-cf-approuter/


Build sci as static binary

This would allow to incorporate it into any arbitrary rootfs

@m-kat The idea here is that we can incorporate sci in any rootfs tree even those which does not provide our tooling. Since sci is our init=... entrypoint, a static version of it can be used in any arch compatible rootfs image.
My plan ist that we can do something like this:
flake-ctl firecracker pull \
    --name firecracker-quickstart-image \
    --kernel wget https://s3.amazonaws.com/spec.ccfc.min/img/quickstart_guide/x86_64/kernels/vmlinux.bin \
    --rootfs wget https://s3.amazonaws.com/spec.ccfc.min/ci-artifacts/disks/x86_64/ubuntu-18.04.ext4

flake-ctl firecracker register --app /usr/bin/apt-get --vm firecracker-quickstart-image

apt-get --help

and it just works. So in the end we gain a lot flexibility because we can consume any data also provided by others, e.g the firecracker project in this case. I believe this is important because other people will not take care that an sci binary is needed when they build a firecracker image for use with flake-pilot
Thoughts ?


_1password-gui: 8.10.36 -> 8.10.40, _1password-gui-beta: 8.10.38-13.B…

…ETA -> 8.10.44-21.BETA
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

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

Hey, sorry for the delay 8.10.44 and new beta got released already - can you update please?

Merged this one and will do a follow up then


OnBuild session output folder path on multiple lines

It would be useful to separate
Build results in: C:/Users/norbe/AppData/Local/Temp/Dado/CAS-6.0/

into two lines.  It's easier to prepend ]open ... without needing to delete "Build results in:"
I.e.

Build results in:
  C:/Users/norbe/AppData/Local/Temp/Dado/CAS-6.0/

or

Build results in:
  ]open C:/Users/norbe/AppData/Local/Temp/Dado/CAS-6.0/

Noted, done.


consider means of waiting for container init

It'd be useful if there were a built-in way to wait for a container to finish initializing.
(One of the problems this solves is running apt update too soon in the container, before the user's custom apt mirror has been configured.)
Currently we poll cloud-init status until we get status: done (or time out).
Depending on the container image the definition of "ready" may vary, so perhaps waiting for cloud-init should just be a default, overridable by the image supplying a hook script of some sort.

For the curious, or those who have a similar problem:
function lxc_wait_for_cloud_init_done {
    lxc=$1
    echo -n "Polling ${lxc} for cloud-init completion..."
    for x in {1..20} ; do
	status=$(lxc exec $lxc cloud-init status)
	case "$status" in
	    "status: done")
		echo " done."
		return 0	# exit status, not boolean
		;;
	    *)
		echo -n .
		;;
	esac
	sleep 3
    done

    return 1			# again, exit status
}

Having LXD run arbitrary commands inside all starting containers to try to figure out if they're running or not isn't going to happen. This would cause potentially massive load on systems running a lot of containers and would also require awareness from LXD as to what the containers are running which isn't something we've ever wanted to have to deal with.
There's also the general issue of the definition of "ready" varying very widely based on user preference.
For some, this means that network is functional, though whether that means routable or routable+DNS can also be debated.
For others, this means having their main service started and responding appropriately.
Or in some cases, waiting for all services to be started.
In practice, it tends to be far better for whoever interacts with the containers/VMs to check what actually matters to them, whether it be cloud-init being done, network being initialized, some service running or whatever may fit their use case.


DBAAS-1069: upgrade API and support RDS Aurora

Upgrade the operator to use DBaaS API v1beta1, and support importing Aurora and clusters from RDS.
Jira: https://issues.redhat.com/browse/DBAAS-941
https://issues.redhat.com/browse/DBAAS-1069

Based on PR: https://github.com/RHEcosystemAppEng/dbaas-operator/pull/307 and https://github.com/RHEcosystemAppEng/rds-dbaas-operator/pull/15


Windows claims to detect a trojan

I ran ValheimToolerLauncher.exe and updated to 1.9.1.
Then installed it, launched Valheim and then launched the Tooler.
Overlay is shown in Valheim, but Windows gave me a warning on the file
ValheimTooler_1.9.0\ValheimToolerLauncher.exe
and calls the threat "Trojan:Win32/Bearfoos.A!ml"
It is under quarantaine now.
Anyone else experiencing this?

Hi @tofferlicious ,
Yes my launcher is detected as a virus by most of AntiVirus, see this report: https://www.virustotal.com/gui/file/b552f8cea2acbb9cb4496742c5f4d88cfd3c84ff106db3ac38b1f4324bfd2110/detection
The reason is legitimate, since one of the purposes of my launcher is to force the game to execute code that comes from an unofficial external source. From a technical point of view, this technique is called DLL Injection. As this technique can also be used for malicious purposes, antivirus software automatically detects it and lists my software as malicious.
Unfortunately, there's not much I can do about it. The best to do is define an exception on my tool in the antivirus.
Kind regards,
Astropilot

Hi @Astropilot,
thank you very much for the fast answer and in general for this great tool!
Will close the ticket, thanks again!


Fix Node 12 and vulnerabilities

Require Node 12
Change upstream for ed25519 to a fork with Node 12 fixes
npm audit updates

for #10


Black 24.4.2 is not compatible Black 24.8.0

Diagnostic Data

Python version (& distribution if applicable, e.g., Anaconda): Python3.10
Type of virtual environment used (e.g., conda, venv, virtualenv, etc.): No
Operating system (and version): Mac Os
Version of tool extension you are using: Latest

Behaviour
Expected Behavior
Format with the extension will not fail the linting with latest Black
Actual Behavior
Black 24.4.2 does not passing the CI that uses Black 24.8.0
Logs:
Information on the failing CI
@@ -872,19 +871,17 @@
                 logger.warning(
                     f"Faulty padding argument, defaulting to {paddingDefault}"
                 )
                 padding = paddingDefault
         else:
-            logger.info(
-                f"No padding specified, defaulting to {paddingDefault}")
+            logger.info(f"No padding specified, defaulting to {paddingDefault}")
             padding = paddingDefault

         if 4 <= padding <= 32:
             self.fabricGen.genGeometry(padding)
             logger.info("Geometry generation complete")
-            logger.info(
-                f"{geomFile} can now be imported into the FABulous Editor")
+            logger.info(f"{geomFile} can now be imported into the FABulous Editor")
         else:
             logger.error("padding has to be between 4 and 32 inclusively!")

@KelvinChung2000 If you want to use latest black, you can set black-formatter.importStrategy to fromEnvironment, and install latest black in your environment. The extension provides various ways for you to configure it so that it always matches your CI.
Here are the options:

black-formatter.importStrategy allows you to use black from the environment. This means if you have different versions of black used in different projects, this will pick black from environment so always matching the project.
black-formatter.path this setting allows you to set path to a black formatter. If you us the same black formatter, you can install it into a global tools environment using tools like pipx. Then point the extension to use black from that environment.

The extension itself ships with black but sometimes tools might release newer versions, and the above settings can help you use the one that works for you.


WIP: Update Android Auto to Car App Library 1.1.0

fixes #93
Adds the following new features:

New vehicle data screen with gauges for battery percentage, range and speed
Use Car's GPS
Chargeprice price comparison (fixes #80)

some screenshots of the current state:


fix: workaround for coverage bug

The fit function in the CLI has the structure
https://github.com/alexander-held/cabinetry/blob/d888ec054e080f474a12de6de375857631c55987/src/cabinetry/cli/__init__.py#L134-L137
and both branches are tested:
https://github.com/alexander-held/cabinetry/blob/d888ec054e080f474a12de6de375857631c55987/tests/cli/test_cli.py#L172-L182
In CI, where the coverage is calculated with Python 3.7, everything shows up as covered. When using Python 3.8 it does not. This is presumably due to a CPython optimization, and can seemingly be fixed by the addition of a pass:
https://github.com/alexander-held/cabinetry/blob/1a11641e214072c3922d7a1269304c97754496b8/src/cabinetry/cli/__init__.py#L138
This PR adds this pass and a link to a coverage issue which discusses what I believe is the same underlying issue.

The CI seems unstable, it sometimes passes and sometimes fails. This was also observed in https://github.com/alexander-held/cabinetry/actions/runs/962573993. Possibly related to the release of numpy 1.21.


Fix for IZPACK-1313

console implementation of language selection
fixed parameter "-language" that was not accepted from command line
for both gui and console

Thanks, great!


Make --namespace= behave as promised

The help string for --namespace says you can pass an empty string, and it would have the same effect as namespace(None).
However, it looks like this setting is never propagated to step command. That is, scheduler does not pass --namespace flag to the step process, and then namespace defaults back to username.
I have tested this in local mode and with @batch

@oavdeev Thanks for the PR. I verified that it works in the local mode and with @batch. However, it doesn't work as expected with Step Functions. I believe step_functions.py needs a similar TLC.

Good call, fixed for step functions


[Enhancement] (BE PYTHON) Handle Incorrect Success Notification During Payment Upgrade Process

Description:
When attempting to upgrade a payment plan on Anchor python boilerplate, even without filling any fields, a success notification is incorrectly displayed. This should be corrected to prevent misleading the user.
Acceptance Criteria:
No success notification should appear unless all required fields are filled out and the upgrade process is genuinely successful.
Purpose:
To ensure that users receive accurate feedback during the upgrade process, preventing confusion and enhancing user trust.
Requirements:

Validate the upgrade process to ensure success notifications only appear upon genuine success.
Implement error handling for cases where fields are incomplete or invalid, providing appropriate feedback to the user.

Expected Outcome
Success notifications are only displayed when the upgrade process is completed correctly, with all fields properly filled and validated.
Payment Information Page: https://anchor-python.teams.hng.tech/dashboard/admin/settings/payment-information
Figma file for reference:
Watch issue video here: https://github.com/user-attachments/assets/e5a6bee9-9971-4436-b38c-3592271e4541

@Kah-keh please assign to me


New-HTML -Minify  shows error: Format-HTML is not found

Hi,
if using the "-Minify" switch with New-HTML, an error is generated:

Get-Command : The term 'Format-HTML' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

This can easily be replicated by creating a simple HTML file:
New-HTML -Online:$false -Temporary -ShowHTML -Minify -TitleText "Minify" {
    New-HTMLTextBox -Alignment center -TextBlock {
        New-HTMLHeading -HeadingText "Minify" -Heading h1
    }
}

Results in the error (as above):

Get-Command : The term 'Format-HTML' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:\Users\user\OneDrive\Documents\WindowsPowerShell\Modules\PSWriteHTML\0.0.131\PSWriteHTML.psm1:18555 char:21
$Commands = Get-Command -Name 'Format-HTML'
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CategoryInfo          : ObjectNotFound: (Format-HTML:String) [Get-Command], CommandNotFoundException
FullyQualifiedErrorId : CommandNotFoundException,Microsoft.PowerShell.Commands.GetCommandCommand

Removing the "-Minify" shows no error.
The file is still generated just fine, but the error is displayed and as far as I can tell, there is big difference between the files.

Minify/Format requires PSParseHTML installed. I've fixed the error, but you still require it. PSParseHTML requires some updates as well to properly handle comments as it removes Internet Explorer auto-unblock JS support.


setData for restore cropper positions (without workarounds)

setCanvasData + setCropBoxData = setData

Or, getImageData + getCropBoxData + setCropBoxData = setData, see #261.

v0.9.3 implements setData now.

Aewwwww yeahhh!!

Em 10/05/2015, às 05:06, Fengyuan Chen<EMAIL_ADDRESS>escreveu:
v0.9.3 implements setData now.
—
Reply to this email directly or view it on GitHub.