Can’t make it work

Hi,
i installed your extension as it’s exactly what i need, but i can’t get it to work. I’ve tried with the exemple settings and i don’t see any snippets anywhere. What i am doing wrong ?

First, I'm sorry for that.
But if you provide a minimal reproducible setting and the expected behavior you want, then I can help.

Hi,
Thanks for the quick reply. I've used the json file provided in the exemple to test it. If i use the command insert snippet, nothing is showing in the list. I'm new to vscode, so maybe something in my setup isn't right. Also, i don't know what the behavior for the update snippets button is, but when i click on it i see 0/1 appear and disapear really quickly.
Here is my settings json file :
{     "security.workspace.trust.untrustedFiles": "open",     "JSObfuscator.changeFileExtension": "min.js",     "git.ignoreMissingGitWarning": true,     "workbench.colorTheme": "Sublime VSCode Theme",     "[php]": {},     "auto-close-tag.SublimeText3Mode": true,     "workbench.editor.untitled.hint": "hidden",     "remote-snippets.snippets": [         {           "path": "https://raw.githubusercontent.com/hollowtree/vscode-vue-snippets/master/snippets/html.json",           "language": "vue"         }       ] }

@cedrickp32

Also, i don't know what the behavior for the update snippets button is, but when i click on it i see 0/1 appear and disapear really quickly.

This will re-download remote snippets and store them at ~/.vscode-remote-snippets/config.json

This extension didn't provide command insert snippet, so you can't use with that command.

For example, just type vt, and the snippet will show up.

Ok, that's really usefull. I got it working ! Thank you.
I'm able to get the snippets in vue or javascript files, but i don't see them in html, css or php files. Do you know why ?

This extension only supports these languages for now: const supportedLang = ['vue', 'typescript', 'javascript', 'markdown']
I think I need to fix it in the next version.

I just tried the new version, and everything is working ! It's really awesome, thank you so much for your help !


EventHub: Geo DR Feature

Description
New Geo DR Feature added
This checklist is used to make sure that common guidelines for a pull request are followed.

[X] I have read the contribution guidelines.
[X] The pull request does not introduce breaking changes.

General Guidelines

[X] Title of the pull request is clear and informative.
[X] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[X] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[X] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[X] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
[X] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

@shahabhijeet, Swagger change PR link : https://github.com/Azure/azure-rest-api-specs/pull/1709

@cormacpayne, have updated the PR description, version and metadata file, please review and let me know your comments.


Added beginRaster() and endRaster() to draw text in raster coordinates.

Here it is again the proposed API to render text in raster coordinates.  The code is identical to that of Render::begin(), Render::end() but the canvas is not cleared and the shader is not created (it is assumed it was created before hand).
The Render::endRaster() function is a no-op.  Only the Render::beginRaster(imaging::Size& viewportSize) changes the text shader matrix.
If the beginRaster() function is called before the Render::begin(), it will also not change the shader matrix.

How are you using this in your code? What size are you passing into "beginRaster()"?

El 10/11/22 a las 22:55, Darby Johnston escribió:

How are you using this in your code? What size are you passing into
"beginRaster()"?

The same as for p.render->begin().  The matrix is the same as for
begin(), but begin() clears the canvas and sets the blending mode.  That is:
p.render->begin( viewportSize );
p.render->drawVideo( ... );
p.render->end();
p.render->beginRaster( viewportSize );
p.render->drawText(...);
p.render->endRaster();

Message ID: @.***>

Sorry.  I meant:
El 10/11/22 a las 23:15, Gonzalo Garramuño escribió:

p.render->begin( renderSize );
p.render->drawVideo( ... );
p.render->end();
p.render->beginRaster( viewportSize );
p.render->drawText(...);
p.render->endRaster();

Message ID: @.***>

Instead of adding the beginRaster()/endRaster() functions, how about adding an option for whether the canvas is cleared? I think that might be more generally useful and wouldn't need to introduce a new concept of a raster pass.
Something  like:
render->begin(renderSize);
render->drawVideo(...);
render->end();

RenderOptions options;
options.clear = false;
render->begin(viewportSize, options);
render->drawText(...);
render->end();

The options could also include things like the OCIO information which is currently set with "setColorConfig()". That would actually simplify the API a bit which would be nice.

El 12 nov. 2022, a las 18:24, Darby Johnston @.***> escribió:
Instead of adding the beginRaster()/endRaster() functions, how about adding an option for whether the canvas is cleared? I think that might be more generally useful and wouldn't need to introduce a new concept of a raster pass.
Something like:

Yes.  I was going to suggest that too.  I just didn’t know if you felt like changing a lot of already written code.
—
Gonzalo Garramuno
@.***

For a first pass we could add the clear option and migrate the other options later, that way we can minimize the code changes and add the functionality you need.
Something like:
struct RenderOptions
{
    bool clear = true;

    bool operator == (const RenderOptions&) const;
    bool operator != (const RenderOptions&) const;
};

virtual void begin(
    const imaging::Size&,
    const RenderOptions& = RenderOptions()) = 0;

El 12 nov. 2022, a las 18:42, Darby Johnston @.***> escribió:
For a first pass we could add the clear option and migrate the other options later, that way we can minimize the code changes and add the functionality you need.
Something like:
struct RenderOptions
{
bool clear = true;
bool operator == (const RenderOptions&) const;
bool operator != (const RenderOptions&) const;
};
virtual void begin(
const imaging::Size&,
const RenderOptions& = RenderOptions()) = 0;

Sounds great, by me!!!  Go at it !!!
—
Gonzalo Garramuno
@.***

I just realized you don't have code to test this.  I'll do the change myself and add a new PR.

Find the RenderOptions.h changes in PR #66.  I am closing this PR now.


Remove DCP and Dashboard from the .NET Aspire SDK Workload

This is still a prototype and marked as a draft, so currently only looking for feedback on the proposal document being added here.
cc: @davidfowl @danegsta @mhutch @DamianEdwards @marcpopMSFT @eerhardt @danmoseley @maddymontaquila @radical
Microsoft Reviewers: Open in CodeFlow

We should test the DCP nuget packages on Mac/Linux to make sure there won't be any issues with the executable binaries; the SDK/workloads have a special mechanism for applying executable permissions (the UnixFilePermissions.xml file) and I'm not sure if simple nuget files support the same behavior.

We should test the DCP nuget packages on Mac/Linux to make sure there won't be any issues with the executable binaries; the SDK/workloads have a special mechanism for applying executable permissions (the UnixFilePermissions.xml file) and I'm not sure if simple nuget files support the same behavior.

Good point. I did test this on Linux and Windows, and all scenarios I tested work as expected, but I didn't test on Mac yet.

/azp run dotnet.aspire

Most of my feedback can be addressed in a follow up.


Temporarily pin NodeTestVersion of v21 to 21.2.0

Latest 21.3.0 contains changes that breaks writeFileSync of temp files on
MacOS. This PR unblocks js - core release pipeline while we follow up on the
NodeJS issue.

Lets be sure to file a follow-up issue.

https://github.com/Azure/azure-sdk-for-js/issues/27957


created radial deadzones to help with cardinal direction positioning

Created a radial dead zone so that when the controller is pushed in a direction slightly off of one of the cardinal directions it snaps to the cardinal direction.

https://github.com/FRC900/prog_gen_tasks/issues/485

Merged into https://github.com/FRC900/2023RobotCode/pull/129, closing this one.


How to set delegate or selection changed method?

How to set delegate or selection changed method?

Need some help here! Author, please =)

Here is how I had accomplished this task...

Add a protocol to the top of SWSegmentedControl.swift file:

public protocol SWSegmentedControlDelegate {
    func segmentControl(_segmentControl: SWSegmentedControl, didSelectSegmentAt index: Int)
}

Add a delegate property to the SWSegmentedControl:
public var delegate: SWSegmentedControlDelegate!
Add this line of code to the bottom of didTapButton(_ button: UIButton):
self.delegate?.segmentControl(_segmentControl: self, didSelectSegmentAt: self.selectedSegmentIndex)
Add this extension to the object that will delegate selections:

extension YourObject: SWSegmentedControlDelegate {
    func segmentControl(_segmentControl: SWSegmentedControl, didSelectSegmentAt index: Int) {
        // do things
    }
}

Finally set the delegate:

var segmentedControl: SWSegmentedControl {
   let sc = SWSegmentedControl(items: ["item1", "item2"])
   sc.delegate = self
   return sc
}


We should consider having a plugin that will easily allow users to add empty-dir mounts

One the primary ways in which applications work on other distros and not on openshift is that they are given write access inside the container and can create files. To get around this, we should have folks get an empty dir mounted for the information they need to update. This is on a resource/application basis, therefore the UX being easy to see would be nice.
It would also be nice if by looking at a particular Security Context we could tell if this was potentially needed and let users know about this.

/kind feature
/priority normal
/triage accepted


Consider using Nix/Guix to build/install/share daphne

Hello,
I just got introduced to daphne recently, and I have a few comments/remarks on the installation process.
It seems like the build.sh script is doing “manually” operations that other tools are made for.
Functional package managers such as Nix or Guix are awesome to build and share reproducible and traceable software.
Moreover, it is easily possible to have binary caches that users can query to avoid rebuilding (MLIR for instance :wink:). One popular instance for Nix is Cachix.

It works for my use case, but I didn't take care of some details (ie, CUDA, FPGA support): https://github.com/GuilloteauQ/daphne-nix
Of course, these tools have a non-negligible learning curve, which might scare some users.
But they can also build bundled binaries, container images (Docker, Singularity, LXC, etc.) to ease the usage.
If you consider supporting installing daphne via Nix (or Guix), i will be happy to help :slightly_smiling_face:

Hello and welcome!
Thanks for taking interest in DAPHNE.
build.sh is what we started out with and it has grown to something that we want to replace eventually. I had a quick look at nix and to be honest, it would not have been my first choice. Yes, we're very much interested in compilers and languages in DAPHNE, but having another language for the packaging is a considerable burden imho.
We could have Nix as an additional distribution channel and see where it goes. As for support - if you do the "nixing", I'd support that :)
These are my 2 cents in this matter ;-)


Make graph init platform agnostic (non rm and bash execution)

This should be resolved by #215 and #224.


Private source

cc. @Rub21

@Rub21 @karitotp - thank you for writing this! It'll be interesting to run this on planet.
I agree with @maning - can we make the strings more generic? May be use regular expressions? We do similar check on changeset metadata level on OSMCha https://github.com/mapbox/osmcha/blob/master/osmcha/changeset.py#L293-L302

we are ready here https://gist.github.com/anonymous/c2f96cea5932ee55cb1b665bf8ea9e6c, @maning  can you check the output for argentina,
@geohacker @maning , what do you think?, if we run this validator for whole the world and created at a task in to-fix.

Detection is great.  My main concern is how this should be fixed.  For example ,the changeset for a node in the sample data has other issues. See source tag: http://www.openstreetmap.org/changeset/19622042
I'm not sure this should be a to-fix task.  Such edits should handled at the changeset level.  Specific actions should be:

reach the mapper via changeset discussion;
if confirmed to be of questionable source, revert changeset (partial/full).

@maning I agree with your observations. Not seeing value in pushing this out as a task on to-fix.


Diverts to install.php after pulling latest image

Code of Conduct

[X] I agree to follow this project's Code of Conduct.

Submission validity

[X] This is not a personal support request, that should be posted on discussions community.
[X] I checked current issues and this request isn't a duplicate of an existing issue, opened or closed.

Self troubleshooting

[X] I've read the documentation and made sure to follow it.
[X] I've read the troubleshooting first steps and frequent issues guides.

Version
1.9.2
Description
Yourls sends me to the installation page /admin/install.php after pulling the latest image with Portainer.
This results me to have access to my short urls, but I'm unable to sign in. I loose everything, except for my username and password to the admin page, if I click "install YOURLS".
I use the example docker-compose.yml for yourls at hub.docker.com.
Expectation
Settings should be kept after pulling the latest image.
Reproduction steps

Log in to Portainer.
Go to the container.
Click recreate and select pulling the latest image.
You get the "Install YOURLS" message afterwards. Installation leads to the deletion of all short URLs.

Context
I've tried setting up persistent storage on the container in the past. This lead to me being unable to update the docker image.

Thanks for filing this issue, @Svampebob1.
Indeed, per default, a container data is not persistent and therefore lost when recreated. This is true for YOURLS configuration.
To keep the configuration, a volume must be created to store the config data into a persistent storage.
In our case, a volume on /var/www/html/user/config.php. In fact, it might be useful/simpler to mount the whole user folder, /var/www/html/user.
The update is blocked when the entire YOURLS location is mounted, /var/www/html, to avoid file mismatch.
I'm closing the issue as answered, but don't hesitate to continue the discussion below is needed.

I'm sorry, but I've lost all my short URLs again. I see that there has been an update two days ago.
I'm using watchtower for automatic updates. I've disabled this for this image, until I've found a solution.
What is the best practice on upgrading this image, without data?
I'm thinking about taking regular backups, so that I can restore when this happens the next time.
In case of backup restore, where is the short URLs stored?

What is the best practice on upgrading this image, without data?

First you must elaborate on which data you are talking about:

As of your original report, you were talking about configuration data. The way to handle the configuration has been described in my previous answer.
Now you are mentionning the lost of application data, i.e. actual links, which are stored on a external database. By external, it mease this database is independant of YOURLS, thus not affected by YOURLS updates.
Please refer to this database documentation on how to handle it properly. If you are using MySQL, see its container usage documentation here: https://hub.docker.com/_/mysql

Sorry. It was supposed to be "without loosing data". To be more specific: Without loosing my short URLs.
I've been using the example for docker compose from Docker hub. But I understand the problem now. I've been assuming that the short URLs has been stored as a file and logons has been stored in the database. But I see now that this is a completely wrong assumption.
Thanks for your help 👍.

To anyone else having the same issue, you can use the following Docker compose template for setting up Yourls:
version: '3.1'
services:
yourls:
image: yourls
restart: always
volumes:
- //yourls/user:/var/www/html/user
ports:
- 8083:80
environment:
YOURLS_DB_PASS:
YOURLS_SITE: https://
YOURLS_USER:
YOURLS_PASS:
depends_on:
- mysql
mysql:
image: mysql
restart: always
environment:
MYSQL_ROOT_PASSWORD:
MYSQL_DATABASE: yourls
volumes:
- //yourls/mysql-data:/var/lib/mysql


Another issue about WSL2 GUI apps not launching

Windows build number:
Microsoft Windows [Version 10.0.19043.2006]
Your Distribution version:
20.04
Your WSL versions:
wsl --version does not want to run?

Steps to reproduce:

Run WSL
Attempt to a run a UI app of choice.
Fails to launch.

WSL logs:
WslLogs-2022-10-09_14-04-11.zip
WSL dumps:
No response
Expected behavior:
Gedit launches successfully.
Actual behavior:
Tried https://github.com/microsoft/WSL/issues/6430#issuecomment-785667707 and multiple other solutions, however none of them fully resolve the issue. GTK no longer instantly fails to connect to display after setting the $DISPLAY var (see 1). But, it attempts to launch for ~2 minutes, and then prompts the cannot connect to display error. I believe this may be due to the connection timing out, perhaps?

Case 1: Before setting $DISPLAY

Case 2: After setting $DISPLAY

Something else I noticed is that none of my installed Linux apps sync to my start menu. I don't even seem to have the "Linux" tab in my file explorer.

You're using Windows 10 which doesn't have the integrated GUI features yet.

You're using Windows 10 which doesn't have the integrated GUI features yet.


Is it possible to do subquery LIMIT via GraphQL

In the postgres doku on Controlling Text Search the last example explains how to use ts_headline as follows:
SELECT id, ts_headline(body, q), rank
FROM (SELECT id, body, q, ts_rank_cd(ti, q) AS rank
      FROM apod, to_tsquery('stars') q
      WHERE ti @@ q
      ORDER BY rank DESC
      LIMIT 10) AS foo;

Is it possible to do this LIMIT 10 aka first: 10 in postgraphql?
In the doku they point out that ts_headline is slow as its working on the original body instead of the ts_vector ti. Thats why they advice to use ts_headline only on a limited result-set.
So far i have implemented postgres FTS via a stable postges procedure as described in advanced queries. It would be great to "past-process" a limited query.

You can add additional arguments to your function that apply the limit; if you return a set then you can't name them first but you could do rowLimit or similar?

Year that is true. But then you also have to to the pagination yourself, right?

Interesting, yeah, you’d be limited to only paginating rowLimit rows, right?
Three questions:

Is there a way to flatten the query? I guess not, right, because ts_headline would then run on everything. See if explain analyze has any insight on this as it may be optimized.
If the limit is removed does Postgres optimize with the limit PostGraphQL provides?
Is there a reason you can’t use a ts_vector?

[semi-automated message] Hi, there has been no activity in this issue for over 8 weeks so I'm closing it to keep the issues/pull request manageable. If this is still an issue, please re-open with a comment explaining why.


Image.draw(), make compose draw all tiles at once, optimization. Fixe…

This fixes Issue #44
For bigger images (that requiles sharp to compose with a lot of tiles) the service was slow. This was due to a sequential composition outside of Sharp. Now Sharp handles the composition of all tiles at once.
For 1080x1080 images, we get from 5 seconds to 1.5 seconds speed improvement in a single request.

@JOGUI22 Thanks for the PR. Would you please provide a test as well.

@JOGUI22 Thanks for the PR. Would you please provide a test as well.

Hello Stephan,
May I ask for some guidance about what kind of test do you expect that I provide?
As it's an improvement and not a bugfix about speeding up the algorithm, I don't know how to create a test that validates such improvement.
This is an improvement of a core feature of staticmaps, merging the tile images into the baselayer. It's already used in the following tests (any that uses a tileUrl option when creating a map):

Fetch tiles from subdomains
Rendering text ... -> Render text on NASA Blue Marble

If these two tests passes, it should also show that this PR passes the tests.

Hello Stephan,
May I ask for some guidance about what kind of test do you expect that I provide?
As it's an improvement and not a bugfix about speeding up the algorithm, I don't know how to create a test that validates such improvement.
This is an improvement of a core feature of staticmaps, merging the tile images into the baselayer. It's already used in the following tests (any that uses a tileUrl option when creating a map):

Fetch tiles from subdomains
Rendering text ... -> Render text on NASA Blue Marble

If these two tests passes, it should also show that this PR passes the tests.

If these two tests passes, it should also show that this PR passes the tests.

Agree. Thank you for your work and the PR.

If these two tests passes, it should also show that this PR passes the tests.

Agree. Thank you for your work and the PR.

Published to npm<EMAIL_ADDRESS>

Published to npm<EMAIL_ADDRESS>

@StephanGeorg Thank you Stephan, happy to work with you. Fast and clean.
See ya next time!

@StephanGeorg Thank you Stephan, happy to work with you. Fast and clean.
See ya next time!


The cop correcting usage of $? to $CHILD_STATUS should mention require 'English'

It is not obvious and your code just appears to be broken if you don't do that.

Hmm, it's supposed to do this https://github.com/bbatsov/rubocop/blob/4240ae468edbd1e1589ed3501cc16cbba3ab8513/lib/rubocop/cop/style/special_global_vars.rb#L9

@jcoglan, can you confirm that the message above did not appear to you?

I've realised the problem: that message did appear but I interpreted English as an adjective rather than as a Ruby module; I didn't realise it meant you had to require 'English' to get access to those names. Could the message be clarified so it's more obvious that English is a package from the stdlib?

(And thanks to @whitequark to opening the issue when I was grumbling on twitter)

This has been fixed now and should be closed.

Why this cop has auto-correct if it's required a later action from developer (put require "English" on file)? We rely on autocorrect and this is a case where many developers must find problems. I suggest disable auto-correct from Style/SpecialGlobalVars cop when EnforcedStyle: use_english_names.

Why this cop has auto-correct if it's required a later action from developer (put require "English" on file)?

Because we don't know if English is required somewhere else in the inspected application. This is something we can't determine due to RuboCop's file-by-file inspection algorithm. Always adding require 'English' in each file where the offense is found would be worse IMO. Those unnecessary requires are very hard to spot, whereas the missing requires are easily discovered.


Add IgnoreSelf option

Add an 'ignoreSelf' flag that suppresses the ActiveEffect changes of an Aura on the source actor. This is different than the 'Apply while inactive?' flag; the ignoreSelf makes it clear that the aura is either active or inactive to others without deleting the effect on the bearer.
This is appropriate for debuffs and for times when the effect should not affect the bearer. (In my set up, the paladin's Aura of Protection was automatically applied the character via the system - not sure why, but the character was imported from DNDBeyond. Adding an aura with the same effect doubled the bonus, so I added this flag to avoid the duplication.)

The "apply while inactive" is intended for this purpos, keep the effect inactive on the aura token and it will still apply to tokens around it. I'd you have hard coded bonuses on the actor I should suggest removing them rather than chasing the module to match your use case.

The "apply while inactive" is intended for this purpos, keep the effect inactive on the aura token and it will still apply to tokens around it. I'd you have hard coded bonuses on the actor I should suggest removing them rather than chasing the module to match your use case.

Inactive means not active, so why would the aura still affect others? Either the effect is active and affects others, or it’s completely inactive.

Inactive means not active, so why would the aura still affect others? Either the effect is active and affects others, or it’s completely inactive.

Latest push handles missing initial flags for the ActiveEffect (ran into this with adding AA to. a Combat Utility Belt condition)

Latest push handles missing initial flags for the ActiveEffect (ran into this with adding AA to. a Combat Utility Belt condition)

So looking over this, its a bit out of my depth. From what I can tell you prevent the aura from actually applying its effect to the actor that owns the item, even when it is active correct?

So looking over this, its a bit out of my depth. From what I can tell you prevent the aura from actually applying its effect to the actor that owns the item, even when it is active correct?

Thank you for the time to make this change. Ive merged it into the main branch and removed the "apply while inactive" as this replaces that functionality

Thank you for the time to make this change. Ive merged it into the main branch and removed the "apply while inactive" as this replaces that functionality


Network in POD doesn't work fine

I follow this document to establish a one-node k8s cluster with flannel network, hyperd at commit d493b1bf1f9d21277203d18f08928fd56a3a73af (to avoid using Interface.Mtu because of other issue) and frakti 1.9.1 release.
POD can be created but there is a problem with networking.
I execute bash in the POD, and try to ping other POD's IPs then I fail.
I find a workaround that ping the POD IP from master node, the networking of that POD will recover,
but the WA is weird, do I miss some configurations?
Thanks

Which frakti release?

Frakti github 1.9.1 release
Frakti v1.9.1

@gavinmy15  Sorry, I can't re-produce this issue and it's very weird, I can not tell why you ping master and things recover ...
Can you please deploy a new cluster in new machines?

@resouer
New cluster works fine, I cannot re-produce the environment too.

Can frakti work with calico network?

@fanux Yes, it works with any bridged CNI plugin

It's fine to close because I cannot reproduce the issue again.


Weird behavior with powerstrip POST

There's a weird behavior happening with powerstrip v0.0.1
If I run docker create -t -i  -m 512m busybox  to have a 512M max memory on my container I can see the POST request on my powerstrip-adapter, both in pre and post-hook requests
{
    "AttachStderr": true,
    "AttachStdin": true,
    "AttachStdout": true,
    "Cmd": null,
    "CpuShares": 0,
    "Cpuset": "",
    "Domainname": "",
    "Entrypoint": null,
    "Env": [],
    "ExposedPorts": {},
    "HostConfig": {
        "Binds": null,
        "CapAdd": null,
        "CapDrop": null,
        "CgroupParent": "",
        "ContainerIDFile": "",
        "CpuShares": 0,
        "CpusetCpus": "",
        "Devices": [],
        "Dns": null,
        "DnsSearch": null,
        "ExtraHosts": null,
        "IpcMode": "",
        "Links": null,
        "LogConfig": {
            "Config": null,
            "Type": ""
        },
        "LxcConf": [],
        "Memory": 536870912,
        "MemorySwap": 0,
        "NetworkMode": "bridge",
        "PidMode": "",
        "PortBindings": {},
        "Privileged": false,
        "PublishAllPorts": false,
        "ReadonlyRootfs": false,
        "RestartPolicy": {
            "MaximumRetryCount": 0,
            "Name": "no"
        },
        "SecurityOpt": null,
        "Ulimits": null,
        "VolumesFrom": null
    },
    "Hostname": "",
    "Image": "busybox",
    "Labels": {},
    "MacAddress": "",
    "Memory": 536870912,
    "MemorySwap": 0,
    "NetworkDisabled": false,
    "OnBuild": null,
    "OpenStdin": true,
    "PortSpecs": null,
    "StdinOnce": true,
    "Tty": true,
    "User": "",
    "Volumes": {},
    "WorkingDir": ""
}

However when I inspect the memory on the container, I get '0' and not the value I wanted
[aanm@localhost ~]$  DOCKER_HOST=localhost:2375 docker create -t -i  -m 512m busybox
c8ca418dc746582202cc2d50901dac0e63f9feaa0bf6dfe8a73b27de31662ee8
[aanm@localhost ~]$ sudo docker inspect c8ca418dc746582202cc2d50901dac0e63f9feaa0bf6dfe8a73b27de31662ee8 | grep Memory -A 2 -B 2 "Labels": {},
        "MacAddress": "",
        "Memory": 0,
        "MemorySwap": 0,
        "NetworkDisabled": false,
        "OnBuild": null,
--
        },
        "LxcConf": [],
        "Memory": 0,
        "MemorySwap": 0,
        "NetworkMode": "bridge",
        "PidMode": "",

More info: https://github.com/docker/docker/issues/12246

This is strange - so can I confirm that docker create -t -i -m 512m busybox then docker inspect <cid> without powerstrip results in the memory setting being retained?
Also - what powerstrip adapters do you have in adapters.yml?

[debug, my-own, debug]
that output was from the debug which is more odd.

Hmm, what is the docker-client version of powerstrip?

@binocarlos
Thanks for looking at this, I start using a proper docker wrapper and I don't have this problem anymore :-)


Issue with False Positives in Link Check

The link check frequently returns a number of URLs as "bad" links that are actually good. Although there is an "ignore" option, we are hesitant to use it, since there is always a chance that one of these "bad" links will actually go bad down the road.
It would be useful to get a better understanding of why certain good links are returned as bad and, if possible, fixing this in the code so they show up as okay down the road.
Brian is initially assigned, but may pass this along to Tylor along with any notes on progress.

Related issue: Sometimes, when I update a URL that is truly bad, it updates automatically in the Link Check. Other times however, it doesn't update and the old URL still shows up. May be a caching issue so I will check back again.
Here is an example of a resource that still shows up as bad after I updated to a good link: https://hub.aashe.org/_ad/content/academicprogram/13301/change/

Initial research:

Automated link checking may be happening once weekly (unless the hub server has a different value set). This can be updated to any timeframe we want.
Ignore button is functionality that is provided by the package, so it may be something that they see as acceptable workflow.
I have identified links that are 'false broken.' I will look into why this behavior exists.

Thoughts:

We should get rid of the ignore button. Ignoring a 'false broken' link initially may make it easier to clear out the 'broken link' table, but only leads to more difficult site administration. I recommend that we move to three tables (Good Links, Broken Links, Untested Links) with a higher frequency of automated link checking (once daily).
This obviously cant happen until we understand how the linkcheck is working, and until we get it to a state that we can rely on.

FWIW, I have very strong reservations about removing the ignore button. It would make fixing links so much less efficient that I suspect we'd just stop doing it (negating the whole point of the link checker).
At present, there are 120 broken links and 306 ignored links. If you mix them back together, only about 1 of every 4 links would actually need fixing. That ratio will get even worse as we fix the broken links. As a result, unless we are able to somehow memorize all of the false brokens, we would just be spending the vast majority of our time just reconfirming that these links aren't broken. This makes an already dull job infinitely duller.
If the concern is just that ignored links might actually break at some point, a much better solution (in my view anyway) would be to just have an intern manually check the ~300 ignored links once a year. That's way less time intensive and annoying than having to filter through these false broken links every time we want to try to fix some broken links.

Julian,
My approach with false positives has been to add an internal note to the resource indicating that it is not actually broken, and leaving it in the "Broken" list of resources. The internal note field is always included with the resource when it's on the list, so the note can prompt us to ignore it, or, we can double-check to see if it's still working.
I think the ultimate solution will be to eliminate the problem with false positives altogether so we don't have to use the Ignore option. Thanks in advance for digging into the false broken links Tylor, I hope you're able to find something out.

Points taken. As Monika says, the ultimate goal is to eliminate the issue of false broken links. I'm not suggesting that we mix the ignore list back in with broken list without improvements to the link checking code. I think it would be best to get link checking to a state where there is no more need for the ignore button.

For sure, reducing the incidence of false brokens would certainly be a good thing. However, I suspect there's always going to some and the ignore button seems like a helpful way to deal with them.
I don't favor the approach of adding a note to each false positive for 3 reasons: 1) it takes way more time intensive to open the page, write a comment, and save it than just clicking the ignore button; 2) all of the false brokens would still be mixed into the list of actual brokens, making it harder to find those links that actually need your attention; and 3) marking them this way doesn't really accomplish anything better than just ignoring them; we would still be left with the need to manually recheck them periodically.

Hi @monika-aashe, @dodget, @juliandsmith
I have a memory - which could be entirely false! - that when I was last looking at this I noticed that linkcheck was only processing a subset of the entries it was supposed to and didn't have a chance to figure out why.  It's possible that I misinterpreted something I was seeing at the time.
For the false positives I had a couple theories:
One is that network conditions or constraints on Heroku lead to unstable behavior when making a bunch of external network requests. For example, throttling or dropping requests to external networks when an app is making a bunch of them (like a malicious bot might do).  I think this is unlikely, but does lend explanation to why linkcheck would occasionally report a bad URL and when manually checking it in the admin then reports Good.
My other theory is that linkcheck is using older network standard libraries which are known to not play well with the widespread use of TLS-related protocols across the web stack (HTTPS, SSL, SNI,..).  You could probably replace most of this method with a few lines of requests code and possibly clear up some of the errors out of the gate.  https://github.com/DjangoAdminHackers/django-linkcheck/blob/10a09642f82f0446f37f31f03bd88c8468956477/linkcheck/models.py#L287-L376

Thanks for sharing additional feedback, hope it helps, @dodget

Thanks for the input, Brian. It's definitely useful!
I built my own link checking app yesterday, and I've been doing some testing and research. There do seem to be some limitations, but also some improvements that could be made.
Much of the trouble comes from the external site's security not letting scripts make requests to their servers. However, I've noticed in most of the '403 Forbidden' false broken links, the external server will return some html to us explaining the error which we can read. In that case it means that the link is not broken, it just doesn't trust the request. The script my be barred from opening the link, but shouldn't define it as broken. I could pursue this line further if needed, but I believe I found a way around.
I built a second app which uses Selenium to create a headless Firefox browser. The typical issue is that this approach does not provide request data, as in a status that says '200 OK,' or '403 Forbidden.' However, if we use this headless browser to visit the URL, and verify that the page exists (you could simply check that the page has a 'body' html tag) then the link is ok. If not, then the link is bad.
This second approach appears to be simplest, and to get around the networking challenges. In testing, so far, it has been totally accurate. I'll need to test a lot more, and review with Bob if there are any security concerns that I'm not considering.

Sounds cool! One question - what happens in the second approach if you get directed to one of those error pages like this amazing example that have a  tag? Does it still flag those?

Julian, you certainly excel in critical thinking! Most error pages like the one you provided include the error in the title, or somewhere in the body. That means I can check for it. I've been adding those checks this afternoon. I plugged in that site into my new app for fun, and it returned a 404 like we'd hope.

Awesome! I think is super rad and kind of amazing that you just whipped up not one but two alternatives that seem to perform as well or better than what we had been using.
"Excelling in critical thinking" seems like a nice way of describing difficult people! ;-)


📊 Create Altimir (1986) dataset and stitch it to SEDLAC for Argentina

@paarriagadap Just checking; is this work still going?


universal-ctags: generate manpage

Motivation for this change
ctags is a complex program with lots of flags, manpage is really helpful
Things done
The manpage is generated via the rst2man utility present in python.docutils. Add it as a nativeBuildInput dependancy.

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

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

cc @mimadrid

Awesome. Thanks a lot.
Could You also update to the last git commit and delete the sed patch?

I pushed the required changes; well that was a good idea, it helped me solve https://github.com/majutsushi/tagbar/issues/446#issuecomment-331301162

Thank you


Issue with progressive_val_score

Hi,
I am trying to use this library for some experiments I have with big-ish data. I am running into issues when using the latest master branch. The issue is reproducible with the Toulouse Bikes example (small modifications to account for recent re-structuring on creme-ml).
from creme import compose
from creme import linear_model
from creme import metrics
from creme import model_selection
from creme import preprocessing
from creme import datasets

X_y = datasets.toulouse_bikes.ToulouseBikes()

model = compose.Whitelister('clouds', 'humidity', 'pressure', 'temperature', 'wind')
model |= preprocessing.StandardScaler()
model |= linear_model.LinearRegression()

metric = metrics.MAE()

model_selection.progressive_val_score(X_y, model, metric, print_every=20_000)

Running this give me this error message:
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-39-0dae00385f94> in <module>
     14 metric = metrics.MAE()
     15
---> 16 model_selection.progressive_val_score(X_y, model, metric, print_every=20_000)

~/PyLibrary/creme/creme/model_selection/score.py in progressive_val_score(X_y, model, metric, on, delay, print_every)
     68             # Else update the metric and the model and remove the oldest answer
     69             if y_pred_old != {} and y_pred_old is not None:
---> 70                 metric.update(y_true=y_old, y_pred=y_pred_old)
     71             model.fit_one(x=x_old, y=y_old)
     72             del answers[0]

~/PyLibrary/creme/creme/metrics/mae.py in update(self, y_true, y_pred, sample_weight)
     34
     35     def update(self, y_true, y_pred, sample_weight=1.):
---> 36         return super().update(x=abs(y_true - y_pred), w=sample_weight)
     37
     38     def revert(self, y_true, y_pred, sample_weight=1.):

TypeError: update() takes no keyword arguments

I hope this helps,
J.

Mmm I'm not able to reproduce this, even when running python setup.py build_ext --inplace --force to recompile the Cython code (Mean is implemented in Cython). I'm using Python 3.7.4, how about you?
By the way how is creme working out for you? I'm thinking that it's probably a bit slow for your needs.

Hi!
Yeah, even though I was fully up-to-date with the source from master, re-installing it seems to alleviate the issue (so do need to label this as a bug, I will close it).
As for speed/performance, I hope to try it out over the next few days on a couple of big-ish datasets (30-100GB / several hundred million to few billion samples). While speed is welcome, I put more importance (at least right now) on the "out-of-coreness", so as long as the algorithms are stable seeing so much data I am happy :).
I saw that you have a AdaBoost classifier, which is quite interesting! I hope to test it out soon:). Any other tree-based models would be very welcome, since they seem to be very popular!
Keep up the good work!:)

Cool!
The AdaBoostClassifier is generic and so you can pass any classifier to it. It works pretty well in practice.
Regarding speed the big next step is to be able to cythonize dict operations. For instance we would like to cythonize a dot product between two vectors represented as dicts. I've been learning and I even bought an O'Reilly book but I'm having no luck with dicts. Maybe you people at @vaexio could point us in the right direction!


Kernel died with exit code 1

Issue Type: Bug
When using Shift+Enter to run import os from a python file, I get the error in the Jupyter Output logs shown below.
The bug is that I am not trying to run  anything from "o:\Notes\pythonEx\email.py", I don't even have that file open!  The file I am running single line import os is in a completely different directory!
Are you telling me that the Jupyter extension scans the entire workspace and if a single line is incorrect or incomplete in any file, then the entire Jupyter extension will fail?!  This is insane!
Inconsistently, the second or third time I attempt to run the simple line import os it will work.
Kernel died with exit code 1. Traceback (most recent call last):
  File "D:\Users\user1\Miniconda3\lib\runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "D:\Users\user1\Miniconda3\lib\runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "D:\Users\user1\Miniconda3\lib\site-packages\ipykernel_launcher.py", line 15, in <module>
    from ipykernel import kernelapp as app
  File "D:\Users\user1\Miniconda3\lib\site-packages\ipykernel\__init__.py", line 2, in <module>
    from .connect import *
  File "D:\Users\user1\Miniconda3\lib\site-packages\ipykernel\connect.py", line 13, in <module>
    from IPython.core.profiledir import ProfileDir
  File "D:\Users\user1\Miniconda3\lib\site-packages\IPython\__init__.py", line 56, in <module>
    from .terminal.embed import embed
  File "D:\Users\user1\Miniconda3\lib\site-packages\IPython\terminal\embed.py", line 17, in <module>
    from IPython.terminal.ipapp import load_default_config
  File "D:\Users\user1\Miniconda3\lib\site-packages\IPython\terminal\ipapp.py", line 28, in <module>
    from IPython.core.magics import (
  File "D:\Users\user1\Miniconda3\lib\site-packages\IPython\core\magics\__init__.py", line 18, in <module>
    from .code import CodeMagics, MacroToEdit
  File "D:\Users\user1\Miniconda3\lib\site-packages\IPython\core\magics\code.py", line 23, in <module>
    from urllib.request import Request, urlopen
  File "D:\Users\user1\Miniconda3\lib\urllib\request.py", line 86, in <module>
    import email
  File "o:\Notes\pythonEx\email.py", line 10, in <module>
    from email.mime.multipart import MIMEMultipart
ModuleNotFoundError: No module named 'email.mime'; 'email' is not a package

Extension version: 2021.8.2031190714
VS Code version: Code 1.60.0 (e7d7e9a9348e6a8cc8c03f877d39cb72e5dfb1ff, 2021-09-01T10:41:52.311Z)
OS version: Windows_NT x64 10.0.14393
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz (2 x 2400)

GPU Status
2d_canvas: unavailable_softwaregpu_compositing: disabled_softwaremultiple_raster_threads: disabled_offoop_rasterization: disabled_offopengl: disabled_offrasterization: disabled_softwareskia_renderer: enabled_onvideo_decode: disabled_softwarevulkan: disabled_offwebgl: unavailable_softwarewebgl2: unavailable_software

Load (avg)
undefined

Memory (System)
8.00GB (1.55GB free)

Process Argv
--crash-reporter-id 1e88d7ed-dfc2-42ed-b5d3-970568cb872e

Screen Reader
no

VM
0%

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
pythonvspyt700cf:30270857
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vstes516:30244333
pythonvspyt639:30300192
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
pythonvsuse255:30340121
vscod805cf:30301675
pythonvspyt200:30340761
vscextlangct:30333562
binariesv615:30325510
pythonvssor306:30344512
bridge0708:30335490
pygetstartedc2:30360494
bridge0723:30353136
pythonf5test824cf:30361778
vsdyn478:30356813
pythonvspyt187:30362782
pydsgst2:30361792
vscus224cf:30358040
vssid140:30362080

Hey @clayms sorry about the issue here, and some of the other issues that I've seen you file. We've just moved the Interactive Window over the new VS Code native notebook interface, and there are a few hitches we are still ironing out here.
What you are reproing here isn't something that I've seen reported before. Looking at that error chain what it looks like to me is that we are dealing with an issue here with module path resolution. In o:\Notes\pythonEx you have an email.py file, and when request.py looks to do 'import email' it's picking that up as opposed to the basic python e-mail package. Did you open up the interactive window via a file that was located in o:\Notes\pythonEx? What might be happening here is when the IW is launched from a file in that directory the current working directory is updated to that directory an that directory is added to sys.path. Does that sound like your scenario here?

Closing this issue as removing the email.py file should fix this


[FEATURE REQUEST] Add pin feature to the widget.

It would be nice if the widget had a "pin" feature like the system tray widget for instance.

@Sriramgireesh  should  be able to  pin the  widget  since v0.6


Opening a lease when there are no prices(lease/downpayment) provided by the Oracle - is allowed

Missing error message when a borrower tries to open a lease without having a currency price (lease/downpayment) provided by the Oracle. Currently, the result of such an attempt is: tx resolved instead of rejected which causes the lease to be blocked in the  opening:buy_asset state.
Related to: #50

@desislavva is this still reproducible? If not please close

@desislavva is this still reproducible? If not please close

It is still there.
More details: there is a price for the downpayment currency but no price for the lease currency

Still there.
And one more thing.
Due to the restrictions, we have introduced (min_asset, min_transaction), in case there are no prices when trying to open a lease, and in particular, there is no price for the downpayment currency - the following error occurs: "The asset amount should worth at least 15000 USDC_AXELAR:".
This error is not a sufficient description of the problem. Personally, I tried to increase the amount I was sending until I noticed that there were no prices.

indeed, it's a good UX to prevent the lease from getting stuck on the buy asset step ... but even if we add such a validation we would not eliminate the probability of no prices at the time the lease opening gets to that step


Add docs about neovim-lsp

Maybe can help also for https://github.com/kiteco/issue-tracker/issues/143?
Anyway with my instance this config let kite to run with my neovim nightly.

Thanks for this.  I've asked @metalogical to take a look at it because he's more familiar with Kite's LSP than I am.

Thanks for this.  I've asked @metalogical to take a look at it because he's more familiar with Kite's LSP than I am.

It is just the same for coc but with the settings for the neovim lsp official plugin.

It is just the same for coc but with the settings for the neovim lsp official plugin.


we can place node on the top node of the door

Sadly, that's normal. Homedecor's doors are a single node expanded onto two places. I don't have any way of preventing this.

Indeed, it's normal, the second node of the door isn't a "real node", it's an hack of the doors mod.
Closed the issue, thank you anyway for your report :)

It was fixed by @LeMagnesium some time ago with the glass_door, am I wrong ?

@ObaniGemini : You're right, but it was not me. @VanessaE applied a fix on the upstream repository that I merged. I will see if we can use the same principle for those doors then.


Tracking fixes

fix signup flow on save (open save dialog after signup/login)
add GA tracking for save, join, leave; frontpage; signup and login dialogs and completion

If you can confirm point (2) in my comment is not a problem, lgtm

Yeah, point 2 isn't a problem because the existing dialog flow is interrupted, that's why it's important also to use / resolve the same deferred as returned to the original caller, so that it can show eg. the Save dialog.


When I use the --namespaces parameter, the app is created successfully, but no traffic is generated

It may be because traffic-generator and gateway are not in the same namespace, gateway and other application services are not in the same namespace, and it is still not possible to cross namespaces.
default deployment env :
containers:
      - env:
        - name: ENV_UPSTREAM
          value: gateway

maybe correct env ：
containers:
      - env:
        - name: ENV_UPSTREAM
          value: gateway.current_namespace

Yes. I can confirm this bug and will fix it in the next few minutes.

In the latest version, the traffic generator and the gateway are always in the same namespace.

Maybe also consider other business services, the downstream service needs to know the namespace of the upstream service


fix wmstats unittest

test this please

test this please

test this please

test this please

test this please

test this please

test this please

test this please


luci-lib-nixio: update TLS support

luci-lib-nixio: Update TLS support
Changelog:
Modify makefile.
Replace cyassl to wolfSSL.
Remove axTLS support.
Replace the deprecated function:
TLSv1_client_method()
TLSv1_server_method()
Signed-off-by: Yuan Tao<EMAIL_ADDRESS>

Sorry the patch does not apply on my master branch of LuCI, am I missing something?

@aparcar
Since the code repository integrates the complete axTLS code with some line feeds and non-UTF-8 characters, using git am to merge patches directly will cause some errors.
Here I recommend just cloning from my branch to generate the patch and then using git am to open the merge.
git clone -b update_nixio https://github.com/wevsty/luci.git
cd luci
git format-patch --binary -1
# This should generate 0001-luci-lib-nixio-update-TLS-support.patch, copy the file.
# cd to the need patch luci path
# Finally, use the git am merge patch (need to add --ignore-whitespace)
git am --ignore-whitespace 0001-luci-lib-nixio-update-TLS-support.patch

If there are still questions you can post the error log.

Can we have this patch merged ?

@jow- comments?

It will be possible to have in 22.03?
This PR is very old and good...

The regression potential is too high, also there's no TLS users for nixio left in LuCI, so I likely won't touch it anymore in the future.

@jow-: I think it is better to use current system that an old and unsecure...

https://www.cvedetails.com/vulnerability-list/vendor_id-17579/product_id-43200/Axtls-Project-Axtls.html

@cotequeiroz: Thanks for your review, I hope that @wevsty will see your comments and will change it ^^

@cotequeiroz: Thanks for your review, I hope that @wevsty will see your comments and will change it ^^

I saw that, if I need to change the PR, I need to retest it, please give me a few days to work on it.

One more suggestion:  split this into different commits:

Remove axTLS support from nixio proper (i.e. changes outside of ax*/).  This will make the changes to nixio code easier to see and audit.
Remove axTLS source code

At this point we should not have any changes to the OpenWrt package, or to anyone building the library with OpenSSL, so I would definitely merge it (new PR, maybe?).  Then:

Move from cyaSSL to wolfSSL
Enhancements to the nixio code (TLS version changes)
Reenable the TLS options in OpenWrt.

@cotequeiroz  @Neustradamus
All the questions and suggestions I have raised so far have been modified as much as possible.
I split the PR into 3 commits and now it looks a bit easier.
I have done basic compilation tests and found no problems so far.
I need more time for the complete test, I will update this message when I finish.
Please contact me if you still have questions.

The conditional dependencies in the package Makefile need to follow the "OpenWrt syntax" to be processed correctly. scripts/package-metadata.pl does not read .config to write the dependencies, so you can't have make add them based on the .config contents.

I have made changes to these sections.

@jow-
I've reviewed this, and I believe it is good enough to be accepted.

Removal of axTLS from tree is long overdue.  Removal of its support from code was done cleanly, only removing code that was either guarded by WITH_AXTLS or calls to nixio_tls__check_connected and nixio_tls__set_connected macros that were empty without WITH_AXTLS.
The update to wolfSSL was done by using 100% the same code as OpenSSL.  The only difference when building them is the location of the headers.  The difference in certificate validation behavior between libraries had already been taken care of before this change.  It is off by default (OpenSSL behavior), and can be changed with TLSContext.set_verify.  So if the OpenSSL code is OK, then I don't see why wolfSSL would not be.
When built with OpenSSL, the one visible change brought by this is the update from TLSv1_*_method  to TLS_*_method, along with the call to SSL_CTX_set_min_proto_version(). This changes supported TLS versions from 1.0-only to 1.2 and above.

What do you think?

No comments. But this looks like a good PR if TLS is required in the future here.


refactoring of events, it should be about 4 times faster now

This is an updated version of #2755, originally by @fab1an.
I have merged with current master, resolved conflicts and fixed code style issues.

Thanks to both of you.

How does performance look in your benchmarks?

Let's follow along in #4709 which includes the changes from this PR.

Should I close my original PR: #2755  as well?

Re-opening since performance of these changes seem better than #4709.

Let's rebase this on master (cleaning up history with fixups), and then I'm up for merging.

@mourner I rebased on master, but did you also mean squash commits?
I've often squashed commits when merging the PR, from GitHub's interface, but I can of course squash on this branch if you prefer it.

@mourner Ok, rebased and squashed it into two commits.

Awesome, I'm happy to see this merged, thanks guys!


Static Configuration using groups, tags, and monitors in different files does not create monitors

Issue: Unable to create monitors
Starting with a fresh installation of uptime-kuma using a username and password, I am attempting to create an AutoKuma configuration using static configuration files only. I have split my static configuration into separate files, which I don't think is causing the issue.
Uptime Kuma version: louislam/uptime-kuma:latest v1.23.15
AutoKuma version: ghcr.io/bigboot/autokuma:master v0.8.0-132419e5
AutoKuma docker compose log

```
autokuma  | WARN [kuma_client::util] [/autokuma/static-monitors/07-edge1.json] No monitor named edge1 could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static-monitors/07-edge1.json] No monitor named edge1 could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static-monitors/07-edge1.json] No monitor named edge1 could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static-monitors/07-edge1.json] No monitor named edge1 could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static-monitors/07-edge1.json] No monitor named edge1 could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static-monitors/07-edge1.json] No monitor named edge1 could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static-monitors/09-edge2.json] No monitor named edge2 could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static-monitors/09-edge2.json] No monitor named edge2 could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static-monitors/09-edge2.json] No monitor named edge2 could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static-monitors/09-edge2.json] No monitor named edge2 could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static-monitors/09-edge2.json] No monitor named edge2 could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static-monitors/09-edge2.json] No monitor named edge2 could be found
autokuma  | INFO [autokuma::sync] Creating new Monitor: static-monitors/01-groups[2]
autokuma  | INFO [autokuma::sync] Creating new Monitor: static-monitors/01-groups[0]
autokuma  | INFO [autokuma::sync] Creating new Monitor: static-monitors/01-groups[4]
autokuma  | INFO [autokuma::sync] Creating new Tag: static-monitors/03-tags[1]
autokuma  | INFO [autokuma::sync] Creating new Tag: static-monitors/03-tags[0]
autokuma  | INFO [autokuma::sync] Creating new Tag: static-monitors/03-tags[2]
autokuma  | INFO [autokuma::sync] Creating new Tag: static-monitors/03-tags[7]
autokuma  | INFO [autokuma::sync] Creating new Tag: static-monitors/03-tags[4]
autokuma  | INFO [autokuma::sync] Creating new Tag: static-monitors/03-tags[5]
autokuma  | INFO [autokuma::sync] Creating new Monitor: static-monitors/01-groups[1]
autokuma  | INFO [autokuma::sync] Creating new Monitor: static-monitors/01-groups[3]
autokuma  | INFO [autokuma::sync] Creating new Tag: static-monitors/03-tags[3]
autokuma  | INFO [autokuma::sync] Creating new Tag: static-monitors/03-tags[6]
autokuma  | INFO [autokuma::sync] Creating new Notification: static-monitors/05-notification
autokuma  | WARN [kuma_client::util] [/autokuma/static-monitors/07-edge1.json] No monitor named edge1 could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static-monitors/07-edge1.json] No monitor named edge1 could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static-monitors/07-edge1.json] No monitor named edge1 could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static-monitors/07-edge1.json] No monitor named edge1 could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static-monitors/07-edge1.json] No monitor named edge1 could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static-monitors/07-edge1.json] No monitor named edge1 could be found
autokuma  | INFO [autokuma::sync] Updating Notification: static-monitors/05-notification
```

AutoKuma compose.yaml content

```
services:
  autokuma:
    image: ghcr.io/bigboot/autokuma:master
    container_name: ${CONTAINER_NAME1}
    hostname: ${HOSTNAME1}
    domainname: ${DOMAINNAME}
    environment:
      - AUTOKUMA__DOCKER__ENABLED=${AUTOKUMA__DOCKER__ENABLED}
      - AUTOKUMA__STATIC_MONITORS=${AUTOKUMA__STATIC_MONITORS}
      - AUTOKUMA__TAG_NAME=${AUTOKUMA__TAG_NAME}
      - AUTOKUMA__TAG_COLOR=${AUTOKUMA__TAG_COLOR}
      - AUTOKUMA__LOG_DIR=${AUTOKUMA__LOG_DIR}
      - AUTOKUMA__ON_DELETE=${AUTOKUMA__ON_DELETE}
      - AUTOKUMA__KUMA__URL=${AUTOKUMA__KUMA__URL}
      - AUTOKUMA__KUMA__USERNAME=${AUTOKUMA__KUMA__USERNAME}
      - AUTOKUMA__KUMA__PASSWORD=${AUTOKUMA__KUMA__PASSWORD}
      - AUTOKUMA__KUMA__CALL_TIMEOUT=${AUTOKUMA__KUMA__CALL_TIMEOUT}
      - AUTOKUMA__KUMA__CONNECT_TIMEOUT=${AUTOKUMA__KUMA__CONNECT_TIMEOUT}
      # - RUST_LOG=kuma_client=trace
      # - RUST_BACKTRACE=1
    volumes:
      - ${DIRECTORY_DATA}:/data
      - ${DIRECTORY_STATIC}:/autokuma/static-monitors
      - ${DIRECTORY_LOGS}:/autokuma/logs
      - /etc/timezone:/etc/timezone:ro
    restart: unless-stopped
```

AutoKuma .env.example content

```
# Host specifics
CONTAINER_NAME1=autokuma
CONTAINER_PORT1=
HOSTNAME1=autokuma
DOMAINNAME=example.com
# Directory locations
DIRECTORY_DATA=/srv/autokuma/data
DIRECTORY_STATIC=/srv/autokuma/config
DIRECTORY_LOGS=/srv/autokuma/logs
# Container specifics
AUTOKUMA__DOCKER__ENABLED=false
AUTOKUMA__STATIC_MONITORS=/autokuma/static-monitors
AUTOKUMA__TAG_NAME=AutoKuma
AUTOKUMA__TAG_COLOR="#42C0FB"
AUTOKUMA__LOG_DIR=/autokuma/logs
AUTOKUMA__ON_DELETE=keep
AUTOKUMA__KUMA__URL=http://<IP_ADDRESS>:3002
AUTOKUMA__KUMA__USERNAME=admin
AUTOKUMA__KUMA__PASSWORD=[password]
AUTOKUMA__KUMA__CALL_TIMEOUT=15
AUTOKUMA__KUMA__CONNECT_TIMEOUT=30
```

AutoKuma config/01-groups.json content

```
[
    {
        "type": "group",
        "name": "edge1",
        "description": "All monitors for server edge1"
    },
    {
        "type": "group",
        "name": "edge2",
        "description": "All monitors for server edge2"
    },
    {
        "type": "group",
        "name": "services",
        "description": "All monitors for server services"
    },
    {
        "type": "group",
        "name": "security",
        "description": "All monitors for server security"
    },
    {
        "type": "group",
        "name": "media",
        "description": "All monitors for server media"
    }
]
```

AutoKuma config/03-tags.json content

```
[
    {
        "name": "external",
        "color": "#e28743",
        "type": "tag"
    },
    {
        "name": "internal",
        "color": "#de2348",
        "type": "tag"
    },
    {
        "name": "reverse-proxy",
        "color": "#26aa38",
        "type": "tag"
    },
    {
        "name": "local",
        "color": "#86B09A",
        "type": "tag"
    },
    {
        "name": "azure",
        "color": "#007fff",
        "type": "tag"
    },
    {
        "name": "direct",
        "color": "#FF00FF",
        "type": "tag"
    },
    {
        "name": "dns",
        "color": "#FF00FF",
        "type": "tag"
    },
    {
        "name": "network",
        "color": "#800080",
        "type": "tag"
    }
]
```

AutoKuma config/05-notification.json content

```
{
    "type": "notification",
    "name": "Instant Dreams Telegram",
    "active": true,
    "isDefault": true,
    "userId": 1,
    "config":
    {
        "applyExisting": true,
        "isDefault": true,
        "name": "Instant Dreams Telegram",
        "telegramBotToken": "[token]",
        "telegramChatID": -1001969298385,
        "telegramThreadId": 6
    }
}
```

AutoKuma config/07-edge1.json content

```
[
    {
        "name": "edge1.node-exporter-1",
        "parent_name": "edge1",
        "type": "http",
        "url": "http://<IP_ADDRESS>:9100",
        "tag_names":
        [
            {
                "name": "direct",
                "value": ""
            },
            {
                "name": "internal",
                "value": ""
            }
        ],
        "notification_names":
        [
            {
                "name": "Instant Dreams Telegram"
            }
        ]
    },
    {
        "name": "edge1.pihole-1",
        "parent_name": "edge1",
        "type": "http",
        "url": "http://<IP_ADDRESS>:8080/admin",
        "tag_names":
        [
            {
                "name": "direct",
                "value": ""
            },
            {
                "name": "internal",
                "value": ""
            }
        ]
    },
    {
        "name": "edge1.promtail-1",
        "parent_name": "edge1",
        "type": "http",
        "url": "http://<IP_ADDRESS>:9080/metrics",
        "tag_names":
        [
            {
                "name": "direct",
                "value": ""
            },
            {
                "name": "internal",
                "value": ""
            }
        ]
    },
    {
        "name": "edge1.traefik",
        "parent_name": "edge1",
        "type": "http",
        "url": "http://<IP_ADDRESS>:8888",
        "tag_names":
        [
            {
                "name": "direct",
                "value": ""
            },
            {
                "name": "internal",
                "value": ""
            }
        ]
    },
    {
        "name": "edge1.traefik-metrics",
        "parent_name": "edge1",
        "type": "http",
        "url": "http://<IP_ADDRESS>:8082/metrics",
        "tag_names":
        [
            {
                "name": "direct",
                "value": ""
            },
            {
                "name": "internal",
                "value": ""
            }
        ]
    },
    {
        "name": "edge1.pihole-1.dns",
        "parent_name": "edge1",
        "type": "dns",
        "dns_resolve_server": "<IP_ADDRESS>",
        "dns_resolve_type": "A",
        "hostname": "pihole-1.example.com",
        "port": "53",
        "interval": "240",
        "max_retries": "3",
        "retry_interval": "240",
        "tag_names":
        [
            {
                "name": "dns",
                "value": ""
            },
            {
                "name": "internal",
                "value": ""
            }
        ]
    }
]
```

Uptime-Kuma status:

5 monitors created from file 01-groups.json
8 tags created from file 03-tags.json
1 notification created from file 05-notification.json (but I need to pull the telegram details to get this correct)
0 monitors created from file 07-edge1.json

The error message indicates the parent group edge could not be found. I've tried this with the following references:

edge1
01-groups[0]
edge2
01-groups[1]

What am I missing here? Do the groups and the monitors have to be in the same file, as in multi_example.json? How do I get the autokuma id of the parent group?

Hi, there's currently an issue regarding the file provider not correctly stripping the base path: #93
So this causes your ids to end up as e.g.: static-monitors/01-groups[0]. Note that this is a bug and will be fixed in the future, so if you end up using these id's you'll need to change them back once it's fixed.

Thank you, that worked!
I changed:

host location to /srv/autokuma/static
container location to /autokuma/static
static configuration file to appropriate "parent_name": "static/01-groups[0]"

I now have an issue with tags where the following are created:

groups
notifications
tags

But the http and dns monitors could not be created as the tags could not be found:
autokuma  |                                                        v0.8.0-132419e5
autokuma  | WARN [kuma_client::util] [/autokuma/static/07-edge1.json] No monitor named static/01-groups[0] could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/07-edge1.json] No monitor named static/01-groups[0] could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/07-edge1.json] No monitor named static/01-groups[0] could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/07-edge1.json] No monitor named static/01-groups[0] could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/07-edge1.json] No monitor named static/01-groups[0] could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/07-edge1.json] No monitor named static/01-groups[0] could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/09-edge2.json] No monitor named static/01-groups[1] could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/09-edge2.json] No monitor named static/01-groups[1] could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/09-edge2.json] No monitor named static/01-groups[1] could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/09-edge2.json] No monitor named static/01-groups[1] could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/09-edge2.json] No monitor named static/01-groups[1] could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/09-edge2.json] No monitor named static/01-groups[1] could be found
autokuma  | INFO [autokuma::sync] Creating new Monitor: static/01-groups[1]
autokuma  | INFO [autokuma::sync] Creating new Tag: static/03-tags[2]
autokuma  | INFO [autokuma::sync] Creating new Tag: static/03-tags[3]
autokuma  | INFO [autokuma::sync] Creating new Tag: static/03-tags[6]
autokuma  | INFO [autokuma::sync] Creating new Tag: static/03-tags[1]
autokuma  | INFO [autokuma::sync] Creating new Tag: static/03-tags[7]
autokuma  | INFO [autokuma::sync] Creating new Monitor: static/01-groups[0]
autokuma  | INFO [autokuma::sync] Creating new Monitor: static/01-groups[3]
autokuma  | INFO [autokuma::sync] Creating new Tag: static/03-tags[0]
autokuma  | INFO [autokuma::sync] Creating new Tag: static/03-tags[5]
autokuma  | INFO [autokuma::sync] Creating new Tag: static/03-tags[4]
autokuma  | INFO [autokuma::sync] Creating new Notification: static/05-notification
autokuma  | INFO [autokuma::sync] Creating new Monitor: static/01-groups[2]
autokuma  | INFO [autokuma::sync] Creating new Monitor: static/01-groups[4]
autokuma  | WARN [kuma_client::util] [/autokuma/static/07-edge1.json] No tag named direct could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/07-edge1.json] No tag named direct could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/07-edge1.json] No tag named direct could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/07-edge1.json] No tag named direct could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/07-edge1.json] No tag named direct could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/07-edge1.json] No tag named dns could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/09-edge2.json] No tag named direct could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/09-edge2.json] No tag named direct could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/09-edge2.json] No tag named direct could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/09-edge2.json] No tag named direct could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/09-edge2.json] No tag named direct could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/09-edge2.json] No tag named dns could be found
autokuma  | INFO [autokuma::sync] Updating Notification: static/05-notification

Should these also be static/03-tags[0-7] ?

I answered my own question - yes, they should. :)
autokuma  |                                                        v0.8.0-132419e5
autokuma  | WARN [kuma_client::util] [/autokuma/static/07-edge1.json] No monitor named static/01-groups[0] could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/07-edge1.json] No monitor named static/01-groups[0] could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/07-edge1.json] No monitor named static/01-groups[0] could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/07-edge1.json] No monitor named static/01-groups[0] could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/07-edge1.json] No monitor named static/01-groups[0] could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/07-edge1.json] No monitor named static/01-groups[0] could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/09-edge2.json] No monitor named static/01-groups[1] could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/09-edge2.json] No monitor named static/01-groups[1] could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/09-edge2.json] No monitor named static/01-groups[1] could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/09-edge2.json] No monitor named static/01-groups[1] could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/09-edge2.json] No monitor named static/01-groups[1] could be found
autokuma  | WARN [kuma_client::util] [/autokuma/static/09-edge2.json] No monitor named static/01-groups[1] could be found
autokuma  | INFO [autokuma::sync] Creating new Monitor: static/01-groups[0]
autokuma  | INFO [autokuma::sync] Creating new Monitor: static/01-groups[3]
autokuma  | INFO [autokuma::sync] Creating new Tag: static/03-tags[5]
autokuma  | INFO [autokuma::sync] Creating new Tag: static/03-tags[6]
autokuma  | INFO [autokuma::sync] Creating new Monitor: static/01-groups[4]
autokuma  | INFO [autokuma::sync] Creating new Tag: static/03-tags[7]
autokuma  | INFO [autokuma::sync] Creating new Monitor: static/01-groups[1]
autokuma  | INFO [autokuma::sync] Creating new Notification: static/05-notification
autokuma  | INFO [autokuma::sync] Creating new Tag: static/03-tags[3]
autokuma  | INFO [autokuma::sync] Creating new Monitor: static/01-groups[2]
autokuma  | INFO [autokuma::sync] Creating new Tag: static/03-tags[0]
autokuma  | INFO [autokuma::sync] Creating new Tag: static/03-tags[2]
autokuma  | INFO [autokuma::sync] Creating new Tag: static/03-tags[4]
autokuma  | INFO [autokuma::sync] Creating new Tag: static/03-tags[1]
autokuma  | INFO [autokuma::sync] Creating new Monitor: static/07-edge1[4]
autokuma  | INFO [autokuma::sync] Creating new Monitor: static/07-edge1[2]
autokuma  | INFO [autokuma::sync] Creating new Monitor: static/09-edge2[1]
autokuma  | INFO [autokuma::sync] Creating new Monitor: static/09-edge2[3]
autokuma  | INFO [autokuma::sync] Creating new Monitor: static/07-edge1[0]
autokuma  | INFO [autokuma::sync] Creating new Monitor: static/07-edge1[1]
autokuma  | INFO [autokuma::sync] Creating new Monitor: static/07-edge1[5]
autokuma  | INFO [autokuma::sync] Creating new Monitor: static/09-edge2[0]
autokuma  | INFO [autokuma::sync] Creating new Monitor: static/09-edge2[2]
autokuma  | INFO [autokuma::sync] Creating new Monitor: static/07-edge1[3]
autokuma  | INFO [autokuma::sync] Creating new Monitor: static/09-edge2[4]
autokuma  | INFO [autokuma::sync] Creating new Monitor: static/09-edge2[5]

I'll continue to work on turning my ClickOps configuration into a GitOps configuration and monitoring the fixes on AutoKuma. Fantastic work so far.


NodeAuditAnalyzer failed on /github/workspace/client/package-lock.json

Hi,
I am using Dependency Check as Github Action, that is configured to run on PR on my nodeJs project. Below is the file for workflow. I want it to skip devdependencies with the flag --nodeAuditSkipDevDependencies, but introducing this flag throws error that
Error:  NodeAuditAnalyzer failed on /github/workspace/client/package-lock.json
[WARN] An error occurred while analyzing '/github/workspace/client/package-lock.json' (Node Audit Analyzer).

Can anyone help me getting rid of this error? This fails my check even though it generates the report but check gets failed and is causing hinderance.
`name: Dependency-Checker
on:
  pull_request:
    branches:
    - master
    - trunk

jobs:
  depchecktest:
    runs-on: ubuntu-latest
    name: depecheck_test
    steps:
      - name: Checkout
        uses: actions/checkout@v2
      - name: Build project with NPM
        run: npm ci --production
      - name: Depcheck
        uses: dependency-check/Dependency-Check_Action@main
        id: Depcheck
        with:
          project: 'myProject'
          path: '.'
          format: 'HTML'
          args: >
            --failOnCVSS 7
            --nodeAuditSkipDevDependencies`

Having encountered similar, and tested this with a local build of the main branch of Dependency-Check.
I believe that PR #6690 (done in the context of #6437) has fixed this.

Thank you for testing and confirming this is closed.


Bug: Error initializing Agent

Came across this while configuring and initializing the Agent
Error creating key with key type 'ed25519': Cannot read property 'Software' of undefined
Tracing down the stack trace to
async getMediationConnection(mediatorInvitationUrl) ->
    this.mediationRecipient.getRouting({ useDefaultMediator: false });
     const recipientKey = await agentContext.wallet.createKey({ keyType: crypto_1.KeyType.Ed25519 });

In previos versions of credo its working fine, but after upgrading to 0.5.9, we have this error

I think you need to update your version of Aries Askar

@TimoGlastra You are totally right, after updating ask version, it worked
Thank you


Question about "is_exec" & "priv" in ref model

for “is_exec” in https://github.com/riscv-non-isa/riscv-iommu/blob/1ab22196074b110c2a5aa124f4993fef90e0b926/iommu_ref_model/libiommu/src/iommu_translate.c#L94 .

it has to be "is_read && req->exec_req".  is this a software constraint or hardware constraint that the request has to be a read? .Although it's unlikely, but if iommu receives a write/amo request with a execute req(for example, a write/atomic transaction with awprot[2]==1 using axi protocal), does iommu need to check X permission？

for "priv" in https://github.com/riscv-non-isa/riscv-iommu/blob/1ab22196074b110c2a5aa124f4993fef90e0b926/iommu_ref_model/libiommu/src/iommu_translate.c#L96 .

it has to be "req->pid_valid && req->priv_req", is this a software constraint or hardware constraint that the request has to be pid_valid?does hardware need to consider both pid_valid & priv_req to decide whether it is  requesting supervisor privilege?

it has to be "is_read && req->exec_req". is this a software constraint or hardware constraint that the request has to be a read?

Instructions are read so that they can be executed. I am not aware of a write-semantics for instructions. This is a hardware constraint.

it has to be "req->pid_valid && req->priv_req", is this a software constraint or hardware constraint that the request has to be pid_valid?does hardware need to consider both pid_valid & priv_req to decide whether it is requesting supervisor privilege?

For G-stage address translation and protection, all memory accesses are treated as unprivilged. This is a hardware constraint.

But why there is a constraint about req->tr.at == ADDR_TYPE_UNTRANSLATED || req->pid_valid ?
    is_exec = ( (is_read && req->exec_req &&
                (req->tr.at == ADDR_TYPE_UNTRANSLATED || req->pid_valid)) ) ? 1 : 0;

Does req->pid_valid == 0  can equal to a G-stage address translation  ?  Why not DC.iohgatp.mode !=Bare equal to a G-stage address translation ?
    priv = ( req->pid_valid && req->priv_req ) ? S_MODE : U_MODE;

But why there is a constraint about req->tr.at == ADDR_TYPE_UNTRANSLATED || req->pid_valid ?

Translated and Translation requests can request execute permission only when there is a PASID TLP prefix i.e. process ID is valid.

Does req->pid_valid == 0  can equal to a G-stage address translation ? Why not DC.iohgatp.mode !=Bare equal to a G-stage address translation ?

G-stage address translation may be Bare or not Bare irrespective of whether the request is to a process address space i.e. process ID is valid. Privilege based separation - user vs. supervisor - is valid only when process based isolation is used i.e. process ID is valid.


Update GettingStartedGuide.md

Update GettingStartedGuide.md.

Fix incorrect links and text.

Relates-To: OLPEDGE-1118.
Signed-off-by: Bautista, Iryna<EMAIL_ADDRESS>

@HalynaDumych Fixed review comments in the following MR:
https://github.com/heremaps/here-olp-sdk-typescript/pull/62


Modify ImageContentSourcePolicy to distinguish between sources (pull specs) and mirrors

Note: This modifies an already committed type. Is that OK?
The current ImageContentSourcePolicy does not scale well when a large set of sources are all mirrored into a single mirror repository; in that case they are all considered to be possible mirrors of each other (in some order), and referring any of them could cause all of the others to be accessed (taking a long time to search through them, especially if they were firewall off and had to time out).
Instead, make an explicit distinction between sources (where images come from, and which appear in pull specs) and mirrors (where images are copied to, an infrastructure concept invisible to most of the cluster, which only refers to the sources).

/hold
... for discussion. @smarterclayton @umohnani8 @abhinavdahiya PTAL.
This is a follow-up to #354.

This looks good to me (see my comment).  It's ok to break this field but we may need to stage the changes with installer (or have installer temporarily disable setting this field).
Will let others review but I think this is a better API than before, and I would expect it to be mirrored into install-config unless issues are discovered that would counter that (let's have that discussion here)

Note that if we do merge this we need to communicate to everyone that we will be breaking the API within the master branch and the timeframe for the fixes landing, so that teams aren't held up by being unable to vendor their code.

:+1:

Waiting for Abhinav feedback

The API looks sound. I can stage changes in installer based on this bump...
/lgtm

/hold cancel

/approve

@abhinavdahiya @smarterclayton We need approve from you :)

LGTM. @smarterclayton needs an approve label

/approve


What is the training/validation dataset used for the model?

Hello~
Thanks for sharing the code, It is a good tool to do the face recognition.
Now I am trying to reproduce the result. Wounding what is the training and validation dataset used for the following models?
Models: "VGG-Face",   "Facenet",   "Facenet512",   "OpenFace", "DeepFace",   "DeepID", "ArcFace",   "Dlib",   "SFace"
Thanks.

you can follow the links in license section, this will redirect you to the original studies. you can find this information in there.

Hi Serengil,
Got it! I'll take a look.
Thanks.


Fix ftp port

Use the correct port (21) for the ftp scheme.

 Thanks for the eagle eyes.


MRW: Cannot debug any folder except first

testing https://github.com/Microsoft/vscode/issues/30722, specifically "debugging (node.js and extension host debugging) work as before".
Insiders 1.15.0 9a308d11
I've created a workspace with all of my extensions and the idea is that I could do a lot of copy/paste between folders and then run/debug any of the individual extensions.
However, it appears I can only debug the first folder of my multi-root workspace, there is no way for me to pick which one I wish to launch.
On backlog?

Yeah: https://github.com/Microsoft/vscode/issues/29245


Check if manual control inputs not coming from radio disturb mode switching

@julianoes Mode switching is broken if QGC is connected as joystick (not known if on QGC or Firmware side). You reported something similar using RC input in simulation.

Its not really disturbing it. But we do need to de-conflict manual and joystick.


Home page is not responsive

The theme is using Bootstrap but the theme is not fully responsive. there are some design issues and the images do not have the appropriate responsive class (img-responsive).

I can see that there are a lot to fix yet. Can i join to improve this?
On Jul 30, 2015 12:08 AM, "Matt Lee"<EMAIL_ADDRESS>wrote:

Closed #91
https://github.com/creativecommons/creativecommons.org/issues/91.
—
Reply to this email directly or view it on GitHub
https://github.com/creativecommons/creativecommons.org/issues/91#event-368637074
.


i18 es translations added

Translations for the Spanish language

Sorry for the late reply, I have merged this PR. Thanks for your contribution!


MINOR: Align swagger dependencies with gradle plugin

Otherwise the build fails with
Caused by: java.lang.NoSuchMethodException: io.swagger.v3.jaxrs2.integration.SwaggerLoader.setOpenAPI31(java.lang.Boolean)
Committer Checklist (excluded from commit message)

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

cc @mumrah

Thanks, I've pushed an update.

Build failures are not related, merging


window.unwrap should not be assumed

In shadow dom without webcomponents polyfill, there is no window.unwrap

Right you are, sir. Fix in https://github.com/vaadin/vaadin-date-picker/pull/285


CLOUD-48457 modify database migration to run pending scripts too

@akanto please review

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1908/


Button with Icons - not clickable

When displaying an icon within a button, such as:

-or-
<button class="btn btn-small btn-clear2 js-modal-toggle" data-modal="recipient_edit" title="Edit"></button>
Screen capture of implementation example:

the  containing the icon is a non-clickable area of the button
@nikolaswise  @paulcpederson  @tdolanwork

@fgarofalo10 is there a reason you have to use a ? Why not just put the icon on the button?
<button class="btn btn-small btn-clear icon-ui-edit icon-ui-flush js-modal-toggle" data-modal="recipient_edit" title="Edit"></button>

That seems to work fine.

ah, I didn't know icon-ui-flush was an option, it doesn't seem to be documented on the Icons page: http://esri.github.io/calcite-web/documentation/icons/
I'll give that a try

@fgarofalo10 good point, I'll update the docs!

opened #684 to remember, closing this issue.


[wish] Placing non-interacting glyphs into clusters

Imagine a large font that has many glyphs, and many of them “interact” with each other somehow, via the composite glyph mechanism, GSUB or GPOS. Some glyphs form GSUB ligatures or alternates of others, some are combining marks that appear next to other glyphs and are positioned via GPOS mark, and some glyphs have GPOS kern kerning between each other, and some use others as components. But it should be possible to form clusters of glyphs in such a way that glyphs that interact with each other would be in the same cluster but glyphs that don't interact with each other would be in separate clusters.
So, for example, in a Chinese font, where there are no OTL features at all and there is no kerning and each glyph is in an ideographic box, each glyph could reside in a separate cluster. In an Arabic font, where there is intense interaction, there would be very few clusters, and quite likely, all or most Arabic glyphs would form just one cluster. But in a Latin font where there is only lightweight kerning and no GSUB, there would be a healthy number of discreet clusters. For example, all “straight” letters could be in separate clusters, and the diagonal glyphs such as A and V and T would all be in one cluster because of kerning.
Ultimately, one could run the subsetter and produce a separate font for each cluster. This approach would allow one to produce smaller webfonts that work like “progressive PNG encoding”: the CSS font stack would transparently recombine them but less-frequent disjoint glyphs would be placed in separate fonts.
It would be useful to be able to declare some glyphs as “to duplicate”. For example, combining marks may be an “involuntary glue” that would normally prevent clusters from disjoining but if specified as “to duplicate”, they would be placed in each cluster that needs them, but would not form glue between clusters.
Another potential use comes to mind: “viral” glyphset closure for the subsetter. If you specify A-Za-z0-9 on your subset and use the clusterer, it could find glyphs that “you may have forgotten to include” like marks and punctuation — if it’s been kerned by the designer, it’s probably important. The subsetter already does the glyphset closure via composites and GSUB but in a conservative way: it only adds glyphs that can be produced by already-existing glyphs. The viral closure would use GSUB, GPOS and composites, so it would allow for very lightweight declarative subsetting as in “take this monstrous font and give me a ‘safe chunk’ of it that contains these chars and more”.

Duplicate of #1312


Bump Hawkular-client gem to 2.2.1 to fix a regression.

Bump the hawkular client gem to 2.2.1 to fix a regression in CM
"Local" travis run
https://travis-ci.org/pilhuhn/manageiq/builds/143368233
Gem changelog:
https://github.com/hawkular/hawkular-client-ruby/blob/master/CHANGES.rdoc#v-221
Gem pull-request with the changes https://github.com/hawkular/hawkular-client-ruby/pull/107
@miq-bot add_label providers/hawkular, bug, darga/no
@yaacov please verify
@miq-bot assign @chessbyte

LGTM :+1:


Not possible to use parametrized string

Let's say I want next string "{number}mm"
With that library it's only possible to do next:
"$number mm"
But I really don't want to use space here
How to handle such a case without splitting it into two strings

${factor} also can be used.


Add JSON output support

This PR adds an --output/-o json switch that outputs linting errors as JSON. Since this is a user-facing/command-line tool change, the tests will be added as a part of #2.

LGTM


Holding the Enter key in diagram-js freezes the window

Describe the bug
When I add rows by pressing "Enter", and I keep it pressed, the window freezes for a bit and then adds all Rows at once

Steps to reproduce

Open a dmn-js decision table
Enter the last row
Hold Enter key
Release it after a while

Expected behavior
The rows are added one-by-one as I hold the key.
Environment

Version: 5.4.0-rc.1
Operating System: Linux x86_64 amd64 (Ubunru 20.04)
Plugins:
Execution Platform: DMN - Camunda Platform 8

Additional context
I can reproduce it on https://demo.bpmn.io/dmn/new , but it only starts to lag after ~60 Rows were added, so this seems to be  performance related
Alternative to consider:

Don't do anything, adding rows like this probably has limited use-cases
Get a better laptop

Get a better laptop

Go for it! :heart:

If you agree I'm inclined to close this issue. Seems like a super edge case. We could of course throttle the rate at which we listen to ENTER, but I've not seen this in any tool.
Is that the issue?

Agreed, it is an edge case and throttling Enter would be weird


Using the package with Laravel 5.1

Hello there,
Can I get some help on using this package with Laravel 5.1 ?
I composer required the package but could not use it as I couldn't actually add it to config/app.php in the list of providers.
Any help would be much appreciated.
Thank you in advance.

This is a simple library and not a finished Laravel provider. Thus it's clear you can't add it to the config/app.php :smirk:
Simply FFMpeg class directly in your code/controller/services as described in the readme.


Fix typos and improve language in docs

What is the problem?
When I first discovered this repo, the only thing I disliked was that the language in the docs was a bit cluncky at times.
Since good docs are really important for any library, I figured that I might go through them and attempt to improve them as much as I can. I am by no means a native english speaker, so there surely will remain room for improvement.
I plan on going through all of the docs over a few pull requests, so that a single pull request would not get too big to review.
Note that I am attempting to only fix typos and improve the general language, not change what is said in the docs.
What changes does this PR make to fix the problem?
Fix typos and improve the language in:

README.md
CONTRIBUTING.md
The introduction page
All of the hooks in the State category

Thanks for the review! As I expected, there was room for improvement. And yeah, I tried to keep this PR from getting too big, but I guess it got kind of big anyway.
I was thinking of next going through the docs of each category of hooks and making PR's of those. They don't contain much text so I don't expect the PR's to get bigger than this one. If they do, I'll split them to smaller ones.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


x/crypto/acme/autocert: allow easy use of certificate alternate chains

What version of Go are you using (go version)?

$ go version
go version go1.17.1 linux/amd64

Does this issue reproduce with the latest release?
Yes (using golang.org/x/crypto v0.0.0-20210921155107-089bfa567519)
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/ahochhaus/.cache/go-build"
GOENV="/home/ahochhaus/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/ahochhaus/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/ahochhaus/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/ahochhaus/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/ahochhaus/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.17.1"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build1798779825=/tmp/go-build -gno-record-gcc-switches"

What did you do?
The new acme Client.ListCertAlternates API from @jameshartig and @FiloSottile is great when directly using an acme client. However, most users likely use autocert instead and no easy method to select an alternative / preferred chain is provided.
What did you expect to see?
An easy way to select the preferred certificate chain in autocert.
What did you see instead?
The need to use the acme library directly to select an alternate cert chain.

CC @FiloSottile @rolandshoemaker via https://dev.golang.org/owners

Hello, are there any updates?

@andreasschulze If you are looking for a shot term work around you can use https://github.com/hochhaus/crypto/commit/ba7d272dee0b9dccf253ddc91a14797a6af88f47.
If this change is directionally acceptable to an OWNER I could clean it up and submit upstream.

@hochhaus: my go skills are limited. Could you show me how to use your version https://github.com/hochhaus/crypto/commit/ba7d272dee0b9dccf253ddc91a14797a6af88f47?
I would try it here: https://github.com/andreasschulze/scmdhttpd/blob/main/scmdhttpd.go

@andreasschulze Absolutely. The API change is very minimal. Basically just add the PreferredChain your autocert.Manager. It might look something like:
cm := &autocert.Manager{
  Cache:      autocert.DirCache(filepath.Join(*certdir, certsDir)),
  Prompt:     autocert.AcceptTOS,
  HostPolicy: hostPolicy(),
  PreferredChain: "ISRG Root X1",
}

Depending on your needs you will need to modify the value of the PreferredChain.

yes, PreferredChain: "ISRG Root X1" is what most users would choose ...
how do I decleare "please use https://github.com/hochhaus/crypto/commit/ba7d272dee0b9dccf253ddc91a14797a6af88f47"?
I assume, I've to change something here?

@andreasschulze I use bazel / rules_go (instead of the normal go build tools) so unfortunately I'm not sure the correct method to plug this into scmdhttpd. Does updating the import to github.com/hochhaus/crypto/acme/autocert not work?

ok, this is my change
I've removed all certs from cache and let autocert fetch a new one. But the server still deliver DST Root CA X3
Checked with openssl s_client -connect scmdhttpd.example:443 -showcerts ...
The file in the cache contain 3 PEM blocks.

leaf issued by R3
R3 issued by ISRG Root X1
ISRG Root X1 issued by the expired DST Root CA X3

Hi @andreasschulze. Thanks. You are correct -- my change is buggy. Can you try https://github.com/hochhaus/crypto/commit/cceb102a4601f585dbc03ecdff0ae8483cd1f310 instead?
I reimplemented this feature from memory without testing as it originally was written in a closed source repo. During the rewrite I incorrectly checked x509Cert.Subject.CommonName instead of x509Cert.Issuer.CommonName.

Yea! with this commit, go1.18beta2 and a forced cert renew the server now no longer present DST Root CA X3 in the TLS handshake

Glad it worked! Thanks for debugging.

now we've to wait your change will merged upstream ...

If an OWNER is willing to review I will clean it up, add tests and send it out.

@hochhaus Could you please make a pull request with your change?

Webserver using acme/autocert/autocert.go still deliver the old "DST Root CA X3". Users like to disable this.
is there a chance, to get this fixed (at least let the user have a choice) in go-1.20? What would be needed? I'like to see some progress.

are there any news / progress?
using go-1.21 acme/autocert/autocert.go still deliver the old "DST Root CA X3" :-/


ssh-agent for Windows Powershell

It would be nice to have details on ssh-agent for Windows users, I would like to use ssh without explicitly defining which key to use.

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

ID: 69db0238-ad2d-43b9-52db-2f2fad0ea380
Version Independent ID: 6f355823-2d16-5085-0fbc-294d20597223
Content: Detailed steps - SSH key pair for Azure Linux VMs - Azure Linux Virtual Machines
Content Source: articles/virtual-machines/linux/create-ssh-keys-detailed.md
Service: virtual-machines-linux
GitHub Login: @cynthn
Microsoft Alias: cynthn

@kismet-cai  Thank you for your feedback, we will further look into it and get back to you at the earliest.

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

@kismet-cai Thank you for the feedback. I'm working on some changes to the SSH content and I'm tracking this and other updates to that content separately. I'm going to close this issue for now. Thanks!
#please-close