Flexible URI for connection with DB and new MariaDB driver

Description
Current properties on db.properties are limited and focused only on mysql. This PR adds a new property on db.properties, db.cloud.uri, that when set, will be used for the connection with the DBMS. This enables URI configuration and use with other DBMSs, such as mariaDB.
When using the db.cloud.uri property, the following properties will be ignored:

db.cloud.host;
db.cloud.port;
db.cloud.name;
db.cloud.autoReconnect;
db.cloud.url.params;
db.cloud.replicas;
db.cloud.autoReconnect;
db.cloud.failOverReadOnly;
db.cloud.reconnectAtTxEnd;
db.cloud.autoReconnectForPools;
db.cloud.secondsBeforeRetrySource;
db.cloud.queriesBeforeRetrySource;
db.cloud.initialTimeout;

When using the db.usage.uri property, the following properties will be ignored:

db.usage.host;
db.usage.port;
db.usage.name;
db.usage.autoReconnect;
db.usage.url.params;
db.usage.replicas;
db.usage.autoReconnect;
db.usage.failOverReadOnly;
db.usage.reconnectAtTxEnd;
db.usage.autoReconnectForPools;
db.usage.secondsBeforeRetrySource;
db.usage.queriesBeforeRetrySource;
db.usage.initialTimeout;

When using both, the following properties will also be ignored:

db.ha.enable;
db.ha.loadBalanceStrategy;

This PR also adds support for the MariaDB driver.
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[X] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[X] Minor

How Has This Been Tested?
Using the current version in a setup with mariaDB and Galera, with a cluster size of 3 and the following configuration on the db.properties file:
# High Availability And Cluster Properties
db.ha.enabled=true
db.ha.loadBalanceStrategy=com.cloud.utils.db.StaticStrategy
# cloud stack Database
db.cloud.replicas=<IP_ADDRESS>,<IP_ADDRESS>
db.cloud.autoReconnect=false
db.cloud.failOverReadOnly=false
db.cloud.reconnectAtTxEnd=false
db.cloud.autoReconnectForPools=true
db.cloud.secondsBeforeRetrySource=1800
db.cloud.queriesBeforeRetrySource=5000
db.cloud.initialTimeout=3600

When the mysql service stops in the main node, ACS is able to switch to one of the other two. But if the host is shut down, this switch never occurs.
Using the changes proposed in this PR, by configuring the db.cloud.uri:
db.cloud.uri=jdbc:mariadb:sequential://<IP_ADDRESS>:3306,<IP_ADDRESS>:3306,<IP_ADDRESS>:3306/cloud?autoReconnect=true&prepStmtCacheSize=517&cachePrepStmts=true&sessionVariables=sql_mode='STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION'&serverTimezone=UTC

I was able to configure and use the sequential fail over mode. This way, when the mysql service stops in the main node and even if the host is shut down, ACS was able to switch to the other DBs.

good improvement.
cc @NuxRo

@JoaoJandre
can the uri be generated in java code ?
this looks like there will be some duplicated settings in db.properties

Thanks for the PR @JoaoJandre would these work on either/both MariaDB and MySQL, do you see any operations differences between the two?

Yes, @rohityadavcloud , this should work with any DBMS that uses URI connections (MariaDB, MySQL, PostgreSQL, and others). CloudStack though would probably not work with other DBMSs with the current code base.
About the operation differences between the two (MariaDB and MySQL); each DBMS has different forms of configuring the URI, the URI I used in my tests will not work with MySQL, for example. That is why I am proposing a way for users to specify manually the URI; therefore, we enable operators to configure ACS to handle multiple DBMSs (MariaDB or MySQL) without any need to change the code.
Note that this PR only adds a new property, the old behavior is still maintained if you do not inform the property introduced here (no regression).

@JoaoJandre can the uri be generated in java code ? this looks like there will be some duplicated settings in db.properties

The current behavior is to generate the URI in the java code, using the db.properties. The problem with that is that it lacks flexibility. Every time someone wants to use a new feature in a URI connection, a new property will have to be created and the java code will have to be extended. It is much easier to just give the users the option to directly inform the URI that ACS should use.
Also, I don't see any duplicated settings in db.properties, what will happen is that there will be some properties that are mutually exclusive.

@JoaoJandre can the uri be generated in java code ? this looks like there will be some duplicated settings in db.properties

The current behavior is to generate the URI in the java code, using the db.properties. The problem with that is that it lacks flexibility. Every time someone wants to use a new feature in a URI connection, a new property will have to be created and the java code will have to be extended. It is much easier to just give the users the option to directly inform the URI that ACS should use. Also, I don't see any duplicated settings in db.properties, what will happen is that there will be some properties that are mutually exclusive.

@JoaoJandre
there are following settings in db.properties
db.cloud.replicas=localhost,localhost
db.cloud.autoReconnect=true
db.cloud.url.params=prepStmtCacheSize=517&cachePrepStmts=true&sessionVariables=sql_mode='STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION'&serverTimezone=UTC

@JoaoJandre can the uri be generated in java code ? this looks like there will be some duplicated settings in db.properties

The current behavior is to generate the URI in the java code, using the db.properties. The problem with that is that it lacks flexibility. Every time someone wants to use a new feature in a URI connection, a new property will have to be created and the java code will have to be extended. It is much easier to just give the users the option to directly inform the URI that ACS should use. Also, I don't see any duplicated settings in db.properties, what will happen is that there will be some properties that are mutually exclusive.

@JoaoJandre there are following settings in db.properties
db.cloud.replicas=localhost,localhost
db.cloud.autoReconnect=true
db.cloud.url.params=prepStmtCacheSize=517&cachePrepStmts=true&sessionVariables=sql_mode='STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION'&serverTimezone=UTC

@weizhouapache , these settings will be maintained for backwards compatibility. They are used when the full URI is not set (db.cloud.uri and db.usage.uri).
I'll add a comment to db.properties to make this more clear.

@JoaoJandre can the uri be generated in java code ? this looks like there will be some duplicated settings in db.properties

The current behavior is to generate the URI in the java code, using the db.properties. The problem with that is that it lacks flexibility. Every time someone wants to use a new feature in a URI connection, a new property will have to be created and the java code will have to be extended. It is much easier to just give the users the option to directly inform the URI that ACS should use. Also, I don't see any duplicated settings in db.properties, what will happen is that there will be some properties that are mutually exclusive.

@JoaoJandre there are following settings in db.properties
db.cloud.replicas=localhost,localhost
db.cloud.autoReconnect=true
db.cloud.url.params=prepStmtCacheSize=517&cachePrepStmts=true&sessionVariables=sql_mode='STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION'&serverTimezone=UTC

@weizhouapache , these settings will be maintained for backwards compatibility. They are used when the full URI is not set (db.cloud.uri and db.usage.uri). I'll add a comment to db.properties to make this more clear.

I suggest to add the following, in additional to existing settings
* db.cloud.engine (mysql/mariadb, use mysql if null )

* db.cloud.mariadb.failover.mode (replication/sequential/loadbalance)

a predefined uri is flexible but I do not think it will happen often . If we want to support other engines, normally some jave changes are required as well.

db.cloud.driver is already used to choose which DBMS will be conected (and should be set even when setting the URI!).
There are other parameters that could be informed through the URI, and mapping all of them would only create even more properties. I really do not see the case for not letting users choose the connection URI.

@JoaoJandre can the uri be generated in java code ? this looks like there will be some duplicated settings in db.properties

The current behavior is to generate the URI in the java code, using the db.properties. The problem with that is that it lacks flexibility. Every time someone wants to use a new feature in a URI connection, a new property will have to be created and the java code will have to be extended. It is much easier to just give the users the option to directly inform the URI that ACS should use. Also, I don't see any duplicated settings in db.properties, what will happen is that there will be some properties that are mutually exclusive.

@JoaoJandre there are following settings in db.properties
db.cloud.replicas=localhost,localhost
db.cloud.autoReconnect=true
db.cloud.url.params=prepStmtCacheSize=517&cachePrepStmts=true&sessionVariables=sql_mode='STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION'&serverTimezone=UTC

@weizhouapache , these settings will be maintained for backwards compatibility. They are used when the full URI is not set (db.cloud.uri and db.usage.uri). I'll add a comment to db.properties to make this more clear.

I suggest to add the following, in additional to existing settings
* db.cloud.engine (mysql/mariadb, use mysql if null )

* db.cloud.mariadb.failover.mode (replication/sequential/loadbalance)

a predefined uri is flexible but I do not think it will happen often . If we want to support other engines, normally some jave changes are required as well.

db.cloud.driver is already used to choose which DBMS will be conected (and should be set even when setting the URI!). There are other parameters that could be informed through the URI, and mapping all of them would only create even more properties. I really do not see the case for not letting users choose the connection URI.

@JoaoJandre
You can generate the uri by settings in db properties

driver
replicas
failover mode (new)
url params

what else are missing ?

@JoaoJandre You can generate the uri by settings in db properties

driver
replicas
failover mode (new)
url params

what else are missing ?

@JoaoJandre
I am ok if you add a new db.cloud.uri, however, please ensure that the following configurations will generate the same uri
db.cloud.driver=jdbc:mariadb
db.cloud.failover.mode=sequential
db.cloud.replicas=<IP_ADDRESS>:3306,<IP_ADDRESS>:3306,<IP_ADDRESS>:3306
db.cloud.autoReconnect=true
db.cloud.url.params=prepStmtCacheSize=517&cachePrepStmts=true&sessionVariables=sql_mode='STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION'&serverTimezone=UTC

to
db.cloud.driver=jdbc:mariadb
db.cloud.uri=jdbc:mariadb:sequential://<IP_ADDRESS>:3306,<IP_ADDRESS>:3306,<IP_ADDRESS>:3306/cloud?autoReconnect=true&prepStmtCacheSize=517&cachePrepStmts=true&sessionVariables=sql_mode='STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION'&serverTimezone=UTC

@JoaoJandre You can generate the uri by settings in db properties

driver
replicas
failover mode (new)
url params

what else are missing ?

@JoaoJandre I am ok if you add a new db.cloud.uri, however, please ensure that the following configurations will generate the same uri
db.cloud.driver=jdbc:mariadb
db.cloud.failover.mode=sequential
db.cloud.replicas=<IP_ADDRESS>:3306,<IP_ADDRESS>:3306,<IP_ADDRESS>:3306
db.cloud.autoReconnect=true
db.cloud.url.params=prepStmtCacheSize=517&cachePrepStmts=true&sessionVariables=sql_mode='STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION'&serverTimezone=UTC

to
db.cloud.driver=jdbc:mariadb
db.cloud.uri=jdbc:mariadb:sequential://<IP_ADDRESS>:3306,<IP_ADDRESS>:3306,<IP_ADDRESS>:3306/cloud?autoReconnect=true&prepStmtCacheSize=517&cachePrepStmts=true&sessionVariables=sql_mode='STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION'&serverTimezone=UTC

@weizhouapache seems to me that the PR's scope is to allow the full URI definition, not to extend the current hard coded properties behavior; therefore, it does not make sense to me to require an extension out of the scope.
Also, what is the point on having (and adding) several configurations that operators will have to learn how they work on CloudStack instead of having a single one that represents the full URI, that operators are used to work with?

@GutoVeronezi cc @JoaoJandre You only mentioned the flexible URI in the title and description. However, there are lots of changes for mariadb support. please remove the changes for mariadb support, if it is out of scope, as you said.

@weizhouapache it is the contributors will to add the MariaDB support, not a requirement from another contributor; also there are 6 lines adding support for MariaDB, which is far from "lots of changes", but I do agree this should be added to the PR's description, as the PR's description should describe in details what the PR is introducing and changing, to facilitate revision and tracking of changes. @JoaoJandre, please, could you mention the MariaDB support in the PR's title and description?

@weizhouapache seems to me that the PR's scope is to allow the full URI definition, not to extend the current hard coded properties behavior; therefore, it does not make sense to me to require an extension out of the scope.
Also, what is the point on having (and adding) several configurations that operators will have to learn how they work on CloudStack instead of having a single one that represents the full URI, that operators are used to work with?

Because URI is not user-friendly. it is suitable to premium users, but not for normal users.

Normal users are able to describe a simple URI, it only needs to be well-documented. Anyways, the support for lots of properties to configure the connection is kept (the properties that we have so far); therefore, no problems will be created for users that are used to the current pattern.

@GutoVeronezi cc @JoaoJandre You only mentioned the flexible URI in the title and description. However, there are lots of changes for mariadb support. please remove the changes for mariadb support, if it is out of scope, as you said.

@weizhouapache it is the contributors will to add the MariaDB support, not a requirement from another contributor; also there are 6 lines adding support for MariaDB, which is far from "lots of changes", but I do agree this should be added to the PR's description, as the PR's description should describe in details what the PR is introducing and changing, to facilitate revision and tracking of changes. @JoaoJandre, please, could you mention the MariaDB support in the PR's title and description?
@GutoVeronezi
If you add the mariadb support to the scope, I think it is not fully done: the failover mode is not configurable (except uri).

@weizhouapache seems to me that the PR's scope is to allow the full URI definition, not to extend the current hard coded properties behavior; therefore, it does not make sense to me to require an extension out of the scope.
Also, what is the point on having (and adding) several configurations that operators will have to learn how they work on CloudStack instead of having a single one that represents the full URI, that operators are used to work with?

Because URI is not user-friendly. it is suitable to premium users, but not for normal users.

Normal users are able to describe a simple URI, it only needs to be well-documented. Anyways, the support for lots of properties to configure the connection is kept (the properties that we have so far); therefore, no problems will be created for users that are used to the current pattern.

Currently for normal users, they just need to specify the  db host ip. In order to support mariadb, they might need to specify the driver, failover mode and replicas, but it is still much more simple and friendly than the URI. To achieve it, we just need to add the new property for failover mode, which is not complicated.

@GutoVeronezi cc @JoaoJandre You only mentioned the flexible URI in the title and description. However, there are lots of changes for mariadb support. please remove the changes for mariadb support, if it is out of scope, as you said.

@weizhouapache it is the contributors will to add the MariaDB support, not a requirement from another contributor; also there are 6 lines adding support for MariaDB, which is far from "lots of changes", but I do agree this should be added to the PR's description, as the PR's description should describe in details what the PR is introducing and changing, to facilitate revision and tracking of changes. @JoaoJandre, please, could you mention the MariaDB support in the PR's title and description?

@GutoVeronezi If you add the mariadb support to the scope, I think it is not fully done: the failover mode is not configurable (except uri).

@weizhouapache seems to me that the PR's scope is to allow the full URI definition, not to extend the current hard coded properties behavior; therefore, it does not make sense to me to require an extension out of the scope.
Also, what is the point on having (and adding) several configurations that operators will have to learn how they work on CloudStack instead of having a single one that represents the full URI, that operators are used to work with?

Because URI is not user-friendly. it is suitable to premium users, but not for normal users.

Normal users are able to describe a simple URI, it only needs to be well-documented. Anyways, the support for lots of properties to configure the connection is kept (the properties that we have so far); therefore, no problems will be created for users that are used to the current pattern.

Currently for normal users, they just need to specify the db host ip. In order to support mariadb, they might need to specify the driver, failover mode and replicas, but it is still much more simple and friendly than the URI. To achieve it, we just need to add the new property for failover mode, which is not complicated.

@weizhouapache, a contributor is not bound to address all the use cases. If the author is adding support to MariaDB with the full URI, we have to guarantee that the use case is being addressed and the changes are not breaking compatibility; other than that, is the author's choice to add support for other use cases or not. Therefore, it is on @JoaoJandre to choose adding the support for hardcoded properties or not.

@GutoVeronezi sure, I've added it to the description and title.
@weizhouapache about adding more properties, as previously written by @GutoVeronezi, I think that it is out of the scope of this PR, which is meant to add a single new property and add compatibility for MariaDB driver. If the community believes that new properties are needed, then I am sure that someone else will be happy to create them in another PR.
I think that the functionality added in this PR is already complete, and there is no need for further changes.

@GutoVeronezi sure, I've added it to the description and title.
@weizhouapache about adding more properties, as previously written by @GutoVeronezi, I think that it is out of the scope of this PR, which is meant to add a single new property and add compatibility for MariaDB driver. If the community believes that new properties are needed, then I am sure that someone else will be happy to create them in another PR.
I think that the functionality added in this PR is already complete, and there is no need for further changes.

OK

@GutoVeronezi @weizhouapache @JoaoJandre , is this ready?

@DaanHoogland a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

@blueorangutan test

@DaanHoogland a [SL] Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

@GutoVeronezi @weizhouapache @JoaoJandre , is this ready?

Yes, it's ready :)

@weizhouapache are your concerns all met?

[SF] Trillian test result (tid-8198)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 43257 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr7895-t8198-kvm-centos7.zip
Smoke tests completed. 115 look OK, 0 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

@weizhouapache can you concur?

@weizhouapache are your concerns all met?

@DaanHoogland
no, I am 0 with this PR.

@JoaoJandre @GutoVeronezi will you be making follow ups to this PR?

testing some more to be sure...

@blueorangutan test alma9 vmware-70u3

@DaanHoogland a [SL] Trillian-Jenkins test job (alma9 mgmt + vmware-70u3) has been kicked to run smoke tests

@JoaoJandre @GutoVeronezi will you be making follow ups to this PR?

@DaanHoogland, PR is good to me as it is; other improvements can be addressed further.

[SF] Trillian test result (tid-8297)
Environment: vmware-70u3 (x2), Advanced Networking with Mgmt server a9
Total time taken: 54170 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr7895-t8297-vmware-70u3.zip
Smoke tests completed. 113 look OK, 2 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_02_balanced_drs_algorithm
Failure
133.27
test_cluster_drs.py

test_08_upgrade_kubernetes_ha_cluster
Failure
730.40
test_kubernetes_clusters.py


[examples] Suggestion to add DOOM fire recreation example.

Recently, I recreated the DOOM fire effect and I would like to add it as an example. But before opening any PR I just wanted make sure you would want such example. If so please let me know and I will open a PR.
For context here is the original effect from doom:
https://www.youtube.com/watch?v=YJB0gfP-GRY&t=10s
Here is my code:
https://github.com/nart38/raylib-playground/blob/main/doomfire.c
And here is the result of this code:

@nart38 Thanks for the offer, it looks great! But usually raylib examples try to showcase some of raylib's functionality; this examples seems more oriented to teach a specific fire-algorythm.
Also note, the algorithm uses DrawPixel() that is very low-performant (drawing 1 quad per pixel), it would be nice if the same example used a shader instead...


dequeueReusableCell(withIdentifier:configure:) is unavailable

How did you fix this ? Thanks!

I forgot it but I think it should to swift 3 as dequeueReusableCellWithIdentifier


Task/5 setup navigation route

Improvements as per the last feedback
Corrected UI for login screen
Added Splash screen
Added Datastore manager

Mergin this pull request as there is no major changes.


No matching distribution found for urlparse

$ pip install -r requirements.txt
Collecting requests (from -r requirements.txt (line 1))
...
  Could not find a version that satisfies the requirement urlparse (from -r requirements.txt (line 3)) (from versions: )
No matching distribution found for urlparse (from -r requirements.txt (line 3))

Python 2.7.10 (default, Oct  6 2017, 22:29:07)

urlparse is a standard library of python 2.7, just ignore the error and proceed.

Sorry about that, now removed from requirements


v4: Remove Fluent status flag text.

We still want the status flag, but as discussed in the UX Issues/PRs, core does not support multiple status flag texts being present.
I think this one was just missed when we removed the others.

Hey Chris. Happy to get this merged but as it's a bugfix could you switch the branch to 4.1 and rebase.
If you could also edit that commit message to have a prefix of "FIX" that would be peachy 🙂

Hi @ScopeyNZ,
This should be sorted now. The failing test is not from my changes.

We have some intermittent test failures now from localised sorting changes =( I've restarted the builds


Remove Class "onEnd" callback

I'm trying to figure out how I can remove the class using "onEnd" callback but it doesn't seem to be working.

(function ($) {
'use strict';
var $body    = $('html, body'),
    content  = $('#main').smoothState({
        prefetch: true,
        pageCacheSize: 4,
        onStart: {
            duration: 250,
            render: function (url, $container) {
                content.toggleAnimationClass('is-exiting');
                $body.animate({
                    scrollTop: 0
                });
            }
        };

        onEnd: {
            duration: 0,
            render: function (url, $container, $content) {
                $body.css('cursor', 'auto');
                $body.find('a').css('cursor', 'auto');
                $container.html($content);
               $('nav').removeClass('hide')
            }

        }
    }).data('smoothState');
})(jQuery);

@clestcruz this should be working just fine. Can you provide your markup along with this?

I've realized it would best to move personal support requests over to Stack Overflow. There's a special smoothstate.js label for us there. This will help us keep the Github issue tracker clean for bugs, pull requests, and enhancements. If you're not having any luck on Stack Overflow, feel free to join the Gitter room and ping me there. I'll try to help as much as I can.
That said, I'll be closing out this issue.


Let the text-to-mask .mask.png file be used as a mask

Ironically, the black and white mask file generated by the invoke> !mask command could not be passed as the mask to img2img. This is now fixed and the documentation updated.

Merged from command line.


feat: bring back the IntoResponse trait

Brings back the IntoResponse trait. Not having a trait for the conversion wouldn't feel like a Rust framework.

This is a good start. I like the idea of limiting the amount of blanket impls for IntoResponse to allow the community to define their own.


sunset jacdac.org

If you search jacdac today, most of the hits land on jacdac.org. In order to send a consistent message, we need sunset the jacdac v1 web site and redirect to the new web site.

There is also the question of have a domain for jacadac which would be nice.

why can't we use jacdac.org

If you search JACDAC on google, it's pointing almost exclusively to the old stuff.

jacdac.org has been retired.


Remove version: OpenJS.NodeJS.LTS version 16.19.0

Replaced by another Pull Request
Microsoft Reviewers: Open in CodeFlow

https://www.github.com/microsoft/winget-pkgs/pull/143386#issuecomment-1986949152 [Policy] Needs-Author-Feedback

Close with reason: See discussion in above linked issue;


Prototyped tab-sets for RelNotes to link to C# as well as C++

Review this prototype PR, and then Close this PR without Merging.  Demonstrates two approaches:

Heavyweight tab-sets, in Promotions.
A lightweight inline list item, in Bug Fixes; the list item is two C# links, could it be reduced to 1 C# link?

Rendered section for review:
https://review.docs.microsoft.com/en-us/microsoft-edge/webview2/release-notes?branch=pr-en-us-2010#promotions
Consider change of design & tagging, to link to C# as well as C++.  Linking to the iface/Summary table works for C++, doesn't necessarily work for C#.  Reexamine list formatting convention in light of dual linking to both languages' API Ref, which are parallel but different structures.
Impact on Dev's script?

Docs Build status updates of commit 335bcaf:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/webview2/release-notes.md
:bulb:Suggestion
View
Details

microsoft-edge/webview2/release-notes.md

Line 79, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/microsoft-edge/webview2/reference/win32/icorewebview2profile2?view=webview2-1.0.1245.22&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 98, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.web.webview2.core.corewebview2navigationcompletedeventargs.httpstatuscode?view=webview2-dotnet-1.0.1245.22&preserve-view=true#microsoft-web-webview2-core-corewebview2navigationcompletedeventargs-httpstatuscode' will be broken in isolated environments. Replace with a relative link.
Line 102, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/microsoft-edge/webview2/reference/win32/icorewebview2navigationcompletedeventargs2?view=webview2-1.0.1245.22&preserve-view=true#get_httpstatuscode' will be broken in isolated environments. Replace with a relative link.
Line 113, Column 287: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.web.webview2.core.corewebview2.statusbartextchanged?view=webview2-dotnet-1.0.1245.22&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 113, Column 483: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.web.webview2.core.corewebview2.statusbartext?view=webview2-dotnet-1.0.1245.22&preserve-view=true' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 61e857a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/webview2/release-notes.md
:bulb:Suggestion
View
Details

microsoft-edge/webview2/release-notes.md

Line 79, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/microsoft-edge/webview2/reference/win32/icorewebview2profile2?view=webview2-1.0.1245.22&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 98, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.web.webview2.core.corewebview2navigationcompletedeventargs.httpstatuscode?view=webview2-dotnet-1.0.1245.22&preserve-view=true#microsoft-web-webview2-core-corewebview2navigationcompletedeventargs-httpstatuscode' will be broken in isolated environments. Replace with a relative link.
Line 102, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/microsoft-edge/webview2/reference/win32/icorewebview2navigationcompletedeventargs2?view=webview2-1.0.1245.22&preserve-view=true#get_httpstatuscode' will be broken in isolated environments. Replace with a relative link.
Line 113, Column 287: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.web.webview2.core.corewebview2.statusbartextchanged?view=webview2-dotnet-1.0.1245.22&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 113, Column 483: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.web.webview2.core.corewebview2.statusbartext?view=webview2-dotnet-1.0.1245.22&preserve-view=true' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit ee68705:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/webview2/release-notes.md
:bulb:Suggestion
View
Details

microsoft-edge/webview2/release-notes.md

Line 86, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/microsoft-edge/webview2/reference/win32/icorewebview2profile2?view=webview2-1.0.1245.22&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 105, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.web.webview2.core.corewebview2navigationcompletedeventargs.httpstatuscode?view=webview2-dotnet-1.0.1245.22&preserve-view=true#microsoft-web-webview2-core-corewebview2navigationcompletedeventargs-httpstatuscode' will be broken in isolated environments. Replace with a relative link.
Line 109, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/microsoft-edge/webview2/reference/win32/icorewebview2navigationcompletedeventargs2?view=webview2-1.0.1245.22&preserve-view=true#get_httpstatuscode' will be broken in isolated environments. Replace with a relative link.
Line 120, Column 287: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.web.webview2.core.corewebview2.statusbartextchanged?view=webview2-dotnet-1.0.1245.22&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 120, Column 483: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.web.webview2.core.corewebview2.statusbartext?view=webview2-dotnet-1.0.1245.22&preserve-view=true' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


CLI tool for this module

Hey Ionica,
I'm super happy now I got a chance to use this module, so I wonder if there is anything like image-to-ascii-cli exists. Otherwise maybe we can create one to use it directly via CLI   😂

@egoist Thanks for this! :sparkles: I do have a working version on my disk, but it's not yet published. :grin: But it's coming!

Thanks!

@egoist I published the cli tool here: https://github.com/IonicaBizau/image-to-ascii-cli
It's not providing a lot of options, but feel free to contribute. It's exactly the piece of code I wrote about one year ago when traveling with the train. Today I just initialized the git repo and open-sourced it. :grin:
I'm trying to organize my stuff on my drive, so I upload everything lots of things on GitHub. :smile:


Add support for alternatives to Firestore

Firestore unfortunately is a proprietary Google Cloud service. I would like the option to use a different database such as MariaDB/MySQL or SQLite for the purpose of self-hosting my own Bridgy-fed instance, since I don't have a Google account and would prefer to avoid them entirely when possible.

Yes! Definitely understood. This is #627, merging in there.


Netlify preview site for Docusaurus, provided by the project infrastructure.

Someone is needed to set this up. I can do it given the Netlify account/access details.
Requires help from Yang Chiu, returning 2024-03-18. https://suse.slack.com/archives/C02DR3N5T24/p1710326329538839

Not sure that Yang can help here based on his reply on Slack.

All seems to be working well.


adding a periodic ping to test p2p connection to the signers

This would greatly enhance awareness and aid debugging keysign/keygen issues when connectivity is at fault.
Consider using the libp2p builtin ping protocol; each signer will ping other signers periodically (every 1min?)
and print out a log if some signer is not responsive for an extended period of time.

closed by https://github.com/zeta-chain/node/pull/3041


Config server could copy the repo for a file:// URL (not use it in place)

So I have my config server and webservices in the same repo. I'll make a new branch and do some work. When I start up the ConfigServer and start code/testing it automatically switched back to master. Since I have my webservices in the same repo it switches those too.
It appears that it isn't coping the repo.

There is a reason for the current behaviour, which is that it is (very) convenient for local development to be able to edit files in place without having to push back to the remote repo. So there is a dirty check, and if the repo is dirty we don't attempt to pull, and this is quite useful IMO. I think maybe your "workaround" should just be documented as best practice for repos that contain both code and configuration.


Expose pods without workload as applications

Functional
Allow all users to manage pods that are running without controller/workload (pods created without a Deployment, ReplicaSet, DaemonSet or StatefulSet...).
UI/UX
Update the existing application-list and application details view to support pod-based applications. Introduce a new value "Pod" for the application type (related to #278)
Technical
Isolated pods should be retrieved as pods that are not controlled by a ReplicaSet (thus a Deployment), a StatefulSet or a DaemonSet.

Blocked by:

[ ] #3989
[ ] #3991
[ ] #3993
[ ] #3994

There is an issue deleting naked pods

deploy naked pod
select naked pod in portainer and click remove
get error

see pod is not deleted

Reopening due to the following issue still present where you cannot save notes on naked pods.
GIVEN: you are in the application details view of a naked pod
AND: the note text area is expanded
WHEN: you enter text in the note text area
AND: click save note
THEN: you receive an error i.patch is not a function

@itsconquest i'll close that one and re-open a bug report for 2.1.0 for that one.


vere uses too much memory

The current release (v2.6) and prior maintain the entire persistent state in memory. As of #402, clean, persistent pages of the home-road heap (north.bin) are in a file-backed mapping, reducing the resident set and improving performance under memory pressure (no need to swap those pages). When the snapshot is updated, the full home-read heap is remapped to north.bin, and all ephemeral memory (contiguous free space within the loom) is discarded with MADV_DONTNEED. But much more can be done.

To reduce ephemeral memory usage:

unused pages can be returned to the host OS more aggressively

MADV_FREE or MADV_DONTNEED could be issued as often as after every event.

consume memory more incrementally

unused pages are currently initialized to dirty, read-write state, which reduces page faults.
an option to initialize to a clean, read-only state would reduce pre-commitment overhead (RAM + swap),
allowing larger loom sizes by default.

roll-your-own swap

for environment were configuring/managing swap space is impossible or honerous (apparently including kubernetes),
the ephemeral portions of the loom could be placed in an ephemeral file-backed mapping (and never sync'd).

improve tooling efficiency

mass, pack, and meld each make the entire persistent state resident. additionally, meld uses absurd amounts of off-loom heap.

adapt the ares PMA design to vere

long term, this is the most efficient/promising design for a single-level store

To reduce persistent memory usage

reclaim from cold jet state

unreferenced registrations could be deleted (after a full |meld, to ensure that refcounts are semantically precise).

compress cells

a special representation for small allocations would allow us to reduce cells from 24 to 16 bytes.
(aligning on 16 bytes would then allow doubling the loom maximum to 16GB)
see urbit/urbit#6599

It is useful to be able to put a (mostly) hard limit on the amount of memory that a ship can use.  Demand paging is relatively good at increasing the number of ships that can be run in a given amount of memory, but relatively bad at reducing the amount of memory that a ship needs, at least when interpreted naively.  If we roll our own swap, then we can say something like: as long as you have a few tens of MB for vere's non-loom state, you can restrict memory as much as you want, and it will only impact performance (and ability to meld).
To roll our own swap, we would need to map the ephemeral memory to a file, and I suppose also any time a clean page is dirtied, that would also get mapped into that file?  And yeah, never sync it.  Is that as easy as:

creating such a file
changing the second mmap in _ce_loom_mapf_north from MAP_ANON | MAP_PRIVATE to MAP_SHARED
in _ce_flaw_protect, mmap the faulting page into that ephemeral file (can replace the mprotect call)
_ce_loom_mapf_north will already remap the dirty heap pages back into the snapshot on save, so no additional changes needed there

It is useful to be able to put a (mostly) hard limit on the amount of memory that a ship can use.  Demand paging is relatively good at increasing the number of ships that can be run in a given amount of memory, but relatively bad at reducing the amount of memory that a ship needs, at least when interpreted naively.  If we roll our own swap, then we can say something like: as long as you have a few tens of MB for vere's non-loom state, you can restrict memory as much as you want, and it will only impact performance (and ability to meld).
To roll our own swap, we would need to map the ephemeral memory to a file, and I suppose also any time a clean page is dirtied, that would also get mapped into that file?  And yeah, never sync it.  Is that as easy as:

creating such a file
changing the second mmap in _ce_loom_mapf_north from MAP_ANON | MAP_PRIVATE to MAP_SHARED
in _ce_flaw_protect, mmap the faulting page into that ephemeral file (can replace the mprotect call)
_ce_loom_mapf_north will already remap the dirty heap pages back into the snapshot on save, so no additional changes needed there


[tests-only] extend API test coverage for content-disposition header

Description
Added API test to check Content-Disposition header for a file containing comma in its name
Related Issue
Coverage for:

https://github.com/owncloud/ocis/issues/8361
https://github.com/cs3org/reva/pull/4498

Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Technical debt
[x] Tests only (no source changes)

Checklist:- [ ] Code changes

[ ] Unit tests added
[ ] Acceptance tests added
[ ] Documentation ticket raised:

@saw-jan we can merge this.
But it would also be nice to know what happens if the file name contains single or double quotes. Those will involve some sort of escaping in the Content-Disposition header, which could easily cause problems.
So some more scenario examples could be added in another PR.


Discrepancy in File Name and Package Versions in Conda Environment File

The Conda environment file provided in the repository has a couple of issues:
File Naming: The documentation refers to the file as langchain_ai.yml, but the actual file in the repository is named langchain_ai.yaml. This discrepancy can lead to confusion.
Package Versioning: The specific versions and build IDs listed for each package in langchain_ai.yaml can lead to ResolvePackageNotFound errors during environment creation, especially if the user is on a different operating system or architecture.
Suggested Fixes:
Update the documentation to match the actual file name in the repository.
Consider removing specific versions and build IDs from the Conda environment file to make it more universally compatible. Alternatively, provide separate environment files for different operating systems or architectures.

Thanks @netmin, for reporting this. I've just changed the README file to use the correct extension.


Properly handle errors in meshdb

Motivation
See #2407
I'm not sure this will solve the issue, but at least it will properly catch and report on errors writing block data to the mesh.
Changes

properly surface errors when writing block data to the mesh

Test Plan
tbd
TODO

[x] Explain motivation or link existing issue(s)
[ ] Test changes and document test plan
[ ] Update documentation as needed

DevOps Notes

[x] This PR does not require configuration changes (e.g., environment variables, GitHub secrets, VM resources)
[x] This PR does not affect public APIs
[x] This PR does not rely on a new version of external services (PoET, elasticsearch, etc.)
[ ] This PR does not make changes to log messages (which monitoring infrastructure may rely on)

This still needs a test
I think it may have been already included in #2427, need to double check

this code is almost completely rewritten


Well I create another account and fixed

Well I create another account and fixedWell I create another account and fixedWell I create another account and fixedWell I create another account and fixedWell I create another account and fixedWell I create another account and fixedWell I create another account and fixedWell I create another account and fixedWell I create another account

You will be reported to GitHub authorities for abusing of the issue tracker.


Fails in Python 3.12 due to usage of pkg_resources

setuptools is being removed as of Python 3.12, and with it pkg_resources.
The simplest fix might be to specify and use the packaging module instead.

I am releasing new version right now 🎉

Thanks a lot for helping with https://github.com/typeddjango/pytest-mypy-plugins/releases/tag/1.11.0 👍

Thanks @sobolevn!


Not catching lured pokemon

Latest dev version. Does the bot differentiate between lured pokemon and wild pokemon? It tells me that the fort is lured but doesn't say which pokemon are a result of the lure.

Why would you need this information ? I don't think the bot can distinguish between them

@OVO647 the pokemon it finds and capture right after that is the lured one.


Solution for IQC2021 Exercise 5 - Anuranan Das

Name - Anuranan Das
Score - 3
Chemical Accuracy - 2.339767 mHa
Number of parameters - 32

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Sorry for the delay. Thank you very much for your submission!


3 tps with full server on powerful pc.

When my server is full, /lag writes me only 3 TPS. And all players have ping 500+
Six-Core processor 2.6 Ghz, 4 gb ram and 1 gigabit internet... 20 slots.
There was no such problem earlier...
There is forum topic with same problem: https://rocket.foundation/viewtopic.php?f=3&t=382

Is this a Rocket or Vanilla issue? Please test it without Rocket.

I think that is Rocket issue. There is no problem on the older version of Rocket. Turned on testing server without Rocket.


md-spinner and md-progress-circle determinate should allow to display value/content in-between the circle with defined width

Bug, feature request, or proposal:
No sure. But I think its a feature request if not present. Excuse me if these features are already present.
What is the expected behavior?
     <md-progress-circle class="col-xs-4" mode="determinate" value="+{{(hours*100)/60}}">
          {{hours}} hours
      </md-progress-circle>

      <md-progress-circle class="col-xs-4" mode="determinate" value="+{{(minutes*100)/60}}">
          {{minutes}} minutes
      </md-progress-circle>

      <md-progress-circle class="col-xs-4" mode="determinate" value="+{{(seconds*100)/60}}">
          {{seconds}} seconds
      </md-progress-circle>

With respect to above code, it should display content that has been placed in-between md-progress-circle tag. I want to put other things in-between the circle as well with style.

it should also allow to define size(width and height) of md-prorgess-circle defined with class='col-xs-4'.

What is the current behavior?

Content is there still it doesn't display anything.

it doesn't  expand itself according to given class class="col-xs-4" .

What are the steps to reproduce?
Providing a Plunker (or similar) is the best way to get the team to see your issue.
https://plnkr.co/edit/t2DA6YS6RRCDL1AwmMTA
What is the use-case or motivation for changing an existing behavior?
I believe that white space circle should be used appropriately to display content if any. I want to use angular2-material-progress bar circle with mentioned functionalities.
Which versions of Angular, Material, OS, browsers are affected?
Latest Angular2 and material version. All browsers.
Is there anything else we should know?
Not sure.

There's a pending PR for it: https://github.com/angular/material2/pull/1994


module react has a dependency for react 16 or 17, while another dependency requires 18

The react module requires react and react-dom to have major version 16 or 17:
https://github.com/visgl/deck.gl-community/blob/646f8328d27d67d596f05c9154072051ec5cf4f0/modules/react/package.json#L46
The dependency styled-react-modal: ^3.1.1 itself requires react and react-dom to have major version 18:
https://github.com/AlexanderRichey/styled-react-modal/blob/60f42fc5bce647387e8e7e8c9e34881f7a63ee0b/package.json#L35
This leads to a dependency conflict in npm install.
I see the following two solutions for this:

Remove the dependencies to react and react-dom, because it comes as transient dependency.
Update the dependencies to react and react-dom to ^18. This has the disadvantage, that any future version upgrades for styled-react-modal needs to be reflected in the minimum react version as well.

@cg-sat Thanks for reporting.

Update the dependencies to react and react-dom to ^18.

Yes. Since this repo is a set of modules building on top of deck.gl, and latest deck.gl/react is using "react": "^18.2.0", I see no reason to deviate from that.
Now, as they name says, this repo is called deck.gl-community because it is maintained by the community, meaning that we mostly rely on contributors to make PRs.
I am however happy to help review, land, and publish.

Landed, pending #126

@deck.gl-community/react v 9.0.2 was just published.


Update references from onDark to inverse

Is your feature request related to a problem? Please describe.
With the new token theming work, we have decided to change the naming of dark themed tokens to ending in -inverse instead of -on-dark. This needs to be reflected in the built out list of tokens.
Describe the solution you'd like
Change the naming convention of the tokens from onDark to inverse for the dark themed tokens in their respective JSON files.
Describe alternatives you've considered
N/A
Additional context
N/A

This is a duplicate ticket and this work is already done.


Type checking error from example in docs

The following example from the docs has a pyright type checking error:
(L, H, W, t) = (100.0, 20.0, 20.0, 1.0)
pts = [
    (0, H / 2.0),
    (W / 2.0, H / 2.0),
    (W / 2.0, (H / 2.0 - t)),
    (t / 2.0, (H / 2.0 - t)),
    (t / 2.0, (t - H / 2.0)),
    (W / 2.0, (t - H / 2.0)),
    (W / 2.0, H / -2.0),
    (0, H / -2.0),
]

ln = Polyline(pts)
ln += mirror(ln, Plane.YZ)

sk8 = make_face(Plane.YZ * ln)
ex8 = extrude(sk8, -L).clean()

The error, using Pyright, is:
Argument of type "Plane | List[Plane] | Unknown" cannot be assigned to parameter "edges" of type "Edge | Iterable[Edge]" in function "make_face"

build123d version v0.8.0

Thanks for raising the problem.
There is currently a large refactoring of the code being worked on (see this PR: https://github.com/gumyr/build123d/pull/812).  As part of this work I'm fixing all of the typing errors in topology.py (which gets divided into several files) - the core functionality of build123d.  At this point I'm down to 145 errors (actually less as I'm counting lines) and will get this to zero before merging the PR. As a follow-up the rest of the typing errors will be fixed so that mypy can be run on the entire code base for each submission to ensure errors don't accumulate over time.  This is quite a massive amount of work though - 14 files changed, 1865 insertions(+), 1777 deletions(-) from just the splitting- so it may take a while to get to zero.
There is a Discord thread discussing this refactoring work if you're interested: https://discord.com/channels/964330484911972403/1306732934866403452


TileMap ScenesCollections tiles ignore y-sort origin of layer they are placed in.

Tested versions
-Reproducible in 4.3dev5.
System information
Windows 11 - Godot v4.3dev5 mono - Vulkan (Forward+)
Issue description
Scenes used inside a TileMap as a ScenesCollection completely ignore the y_sort_origin set for the layer they are placed in. Their y sorting is only affected by the base node's y position.
It is expected that scenes placed inside of a TileMap would respect the y-sort origin like any other tile. Because their y-sorting cannot be directly accessed in order to sort them correctly their origin and texture offsets would have to be individually modified; however, SceneCollections cannot even have their variables accessed inside of the TileSet so this is impossible (and even then if the TileSet is reused inside multiple layers with different y-sort origins this doesn't even help).
Steps to reproduce

Create a TileMap with y_sort_enabled = true.
Create 2 Layers inside of this TileMap with y_sort_enabled = true.
Create a Sprite2D scene and give it a texture.
Create a TileSet inside of the TileMap that has a grid_size smaller than the sprite scene so tiles will overlap.
On one of the layers inside the TileMap change the y_sort_origin to be larger than the grid's y size.
Inside the TileSet create a new ScenesCollection tile and add the sprite scene.
In the TileMap Editor place the new tile on both layers.
Note that tiles inside the layer with a higher y_sort_origin value still appear behind the other layer when placed in the cell above.

Minimal reproduction project (MRP)
BugReportMRP.zip

This might be the same issue as tihs one https://github.com/godotengine/godot/issues/78685

Hello, sorry to bother you! I'm curious if you've managed to solve this issue? I've encountered the same problem but haven't been able to find a viable solution. If you have any methods, I would greatly appreciate it if you could point me in the right direction. Thank you very much!


[wg14, wg21] Fix project names

See https://www.iso.org/standard/79358.html and
https://www.iso.org/standard/74528.html for the proper names of the standards.
The working groups are not part of the title of the project, so I moved the working group designations to separate positions.

@tabatkins Could I interest you in this change? I''ll make the C++ and C papers that use BS a bit more correct :-)


My page set force https by javascript, then amp what can i do this?

Because use static pages, not set httpserver (such as nginx/apache etc.) .
var url = window.location.href;
if (url.indexOf("https") < 0) {
    url = url.replace("http:", "https:");
    window.location.replace(url);
}

@ky0ncheng
I think that you do not need to do anything about hexo-generator-amp .  Can not open AMP HTML page with HTTPS ?

@tea3 thx,I can edit sample-amp.ejs


added executive report page for instances

Description
Executive report V2
Jira:
https://issues.redhat.com/browse/RHIROS-707
https://issues.redhat.com/browse/RHIROS-778
https://issues.redhat.com/browse/RHIROS-708
Screenshot:

/retest

/retest

/retest

/retest


[Trivial-ish] Deciding on single conventional letter for Lazy

First of all I would like to say thanks to all the wonderful people who made and contributed to Lazy.js. It's an amazing library.
However, I think the use of the name Lazy is a bit tedious, especially when compared to Underscore's... well.. underscore. The advantage of Lazy, though, is that it explicitly states that the operators are lazy. But I still think that we should decide on one letter, that, like _, should be used by most everyone who's using the library. It could be l, @, ~, or whatever.
Feedback? Suggestions?

Isn't this kind-of moot as the consumer can change the variable name to whatever they want?
const _ = require('lazy.js')

window._ = window.Lazy

Granted the 2nd method is pretty ugly but attaching to window.Lazy saves conflicts with lodash/underscore in the situation where someone wants to use both Lazy and lodash.

@mattstyles Yes, even with Lodash and Underscore this is moot (you can just say let literallyAnything = _, all I'm saying is we should decide on one letter, that, only by convention, is used as a short form for Lazy.

I see your point, @eshansingh. It would make it easier to understand Lazy code used other places if everyone uses the same shortcut, if any, instead of everyone having their own twist.

The larger question seems to be for me looking from the outside in is whether this repo/project is even being actively worked on. Too bad as it seems to have some real potential, but nothing has been worked on in months. Am I wrong to assume this project is dead? I'm a newb, so maybe I'm not looking at the right signal regarding library legitimacy.


Add "adapters" aliases for LayerInterfaces

Hi,
In the article The Clean Architecture the layer 3 is called "Interface Adapters". Currently go-cleanarch only supports using the term interfaces. When using Go, we found the term "interface" to be confusing and decided to use "adapters" instead to avoid any confusion. This PR adds support for the term adapters for the layer 3.

Good idea, thanks for contribution!

Nice, thank you for the quick reaction :)

@roblaszczak I forgot to update the README!


Initial creation of data package

This ticket is just to get the process started. We'll need an installable data package and at least one table in it.
We'll need at least

DESCRIPTION - use oepsData for the package name
data-raw/
one R script in data-raw that loads a CSV of ours and uses usethis::use_data() (see example) at least once to spit out a .rda file to data/
make sure it's installable/loadable withdevtools::install_github('healthyregions/oepsData')
library('oepsData')

Some useful resources for getting started (may be better ones out there, this is just what I've found so far):

Good overview of concepts and examples: https://www.davekleinschmidt.com/r-packages/#fnref1
Full walkthrough: https://rstudio4edu.github.io/rstudio4edu-book/data-pkg.html

Made the mistake of not including little "#1"'s in my commit messages, but as of commit #5a2a3ce this first step should be done!

Great! I'm able to install this and preview the table. One warning I'm getting is to use
Warning in person1(given = given[[i]], family = family[[i]], middle = middle[[i]],  :
  It is recommended to use ‘given’ instead of ‘first’.

Can you make that update? Then I'd say we can close this ticket and discuss next steps later today.

Fixed! (Although I once again forgot to include a little #1 in the commit message..)


Error at 'Run gradle test' - "Process completed with exit code 1."

console looks like this
. . .
Starting a Gradle Daemon (subsequent builds will be faster)

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':app'.
> Failed to notify project evaluation listener.
   > The file '/home/runner/work/"Repository Name"/"Repository Name"/local.properties' could not be found

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 38s
Error: Process completed with exit code 1.

I'm new with this kind of thing (GitHub actions), maybe I do some mistake in the beginning, but can someone explain what is the error mean?

it looks like your local.properties file was not pushed to the github repository / it could be .gitignore @MNRosyad. you need to double check all the files in the repository

Thank you for your respond, that solve the problem.
I'm using version control from Android Studio and that file is automatically go into .gitignore file.
You can close this Issue

For better .gitignore you can try this
*.iml
/.gradle
.gradle
.idea
/local.properties
/.idea/libraries
/.idea/modules.xml
/.idea/workspace.xml
.DS_Store
build
/build
/captures
.externalNativeBuild

built application files
.apk
.ap_

files for the dex VM
*.dex

Java class files
*.class

generated files
bin/
gen/
.externalNativeBuild/

Local configuration file (sdk path, etc)
local.properties
app/version.properties

# SonarQube
.sonar/

@MNRosyad

btw don't worry about your local.properties, this action also running well on private repository @MNRosyad


please publish to the Debian/Ubuntu repository or make PPA

It seems that this can be pretty easily accomplished with goxc, as that is what is being used to build the releases currently.  Both this issue on goxc and this example .goxc.json file seem to be about all you need to generate the .deb.  Then it's a matter of uploading it or something to a PPA

Although, I was curious about this as well, and it seems there's a lot of documentation to be found for a more formal release as well:

Debian Go Packaging
Debian/dh-make-golang - Automatically creates Debian packaging for Go packages
pkg-go team


Add css var overrides for primary and link colors

What this PR does / why we need it:

adds css counterparts for each of the variables.scss
adds some coarser overrides for changing the blue color

Which issue(s) this PR fixes:

Fixes # https://app.shortcut.com/replicated/story/70225/simplify-theming-for-custom-branding-in-kots
Special notes for your reviewer:

Steps to reproduce

Add the following to your app manifest (merge with the rest of the spec):

spec:
  branding:
    css:
      - "style.css"

Create a file in your release called style.css and add the following to it

:root {
  --card-color: #e9f3ff;
  --icon-color: #000000;
  --link-color: #93a9a4;
  --primary-color: #a3bbb6;
  --primary-disabled-color: #bfc8d5;
  --primary-hover-color: #93a9a4;
  --secondary-hover-color: #e9f3ff;
  --subnav-color: #e9f3ff;
  --tooltip-color: #5b5b5b;
}

Does this PR introduce a user-facing change?

- kots/web(beta): add support for overriding primary scss variables with css variables to support theming

Does this PR require documentation?

some additional info here: https://app.shortcut.com/replicated/story/70225/simplify-theming-for-custom-branding-in-kots#activity-70480


Implement resample method

In this PR, the resample method in time.py is implemented. It resamples input data to target frequency.
Example about how to use it:
import s2s.time
import pandas as pd
import numpy as np

cal = s2s.time.AdventCalendar()
time_index = pd.date_range('20211101', '20211111', freq='1d')
var = np.arange(len(time_index))
input_data = pd.Series(var, index=time_index)
bins = cal.resample(input_data, target_freq='5d')
bins
>>> 2021-11-01     2.0
>>> 2021-11-06     7.0
>>> 2021-11-11    10.0
>>> Freq: 5D, dtype: float64

A tutorial notebook is also included to explain how to use the function. For the future developments, we could always include notebooks in the notebooks folder to explain the new functions.
This PR closes #11.

Note that currently the resample function only supports pd.DataFrame. We will extend it to support xarray.DataArray in another PR. I have created an issue #17 for this.

A tutorial notebook is also included to explain how to use the function. For the future developments, we could always include notebooks in the notebooks folder to explain the new functions.

Would this come in addition to the example code in the method docstring? I like the idea of using notebooks as a user-guide in the documentation, in that case we could use nbsphynx. But the downside is that, in my experience, maintaining those is a pain.


Reduce scope of places field

Reimplementation of #493.

Sorry @veyndan , I just realized that as this version of the code was mostly written by whym, I should probably request his review first.


Config model

I rule and have completed some work on Case Manager that's ready for review!
Attempt to whip up a generalizable config model and smash insurance options into it.
TK: Figure out how to handle update assignment, figure out how to handle defaults, figure out how to mash it into the existing helper, determine whether this is the proper model structure, write controller tests, add to navbar dropdown.
This pull request makes the following changes:

Create config model and tests
Create configs controller and update-y forms

It relates to the following issue #s:

Fixes #1074 ... in theory

Codecov Report

Merging #1092 into master will decrease coverage by 3.23%.
The diff coverage is 26%.

@@            Coverage Diff            @@
##           master   #1092      +/-   ##
=========================================
- Coverage   96.54%   93.3%   -3.24%
=========================================
  Files          50      53       +3
  Lines        1041    1091      +50
=========================================
+ Hits         1005    1018      +13
- Misses         36      73      +37

Impacted Files
Coverage Δ

app/controllers/configs_controller.rb
0% <0%> (ø)

app/helpers/configs_helper.rb
100% <100%> (ø)

app/models/config.rb
100% <100%> (ø)

Continue to review full report at Codecov.

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

After some chatter I'm kinda uncomfortable with rolling this out without a pretty extensive review from the likes of @lomky and @DarthHater and the rest of the corps, so switching efforts to getting #1080 in place for insurance and ext pledges.

Still a WIP, but this fleshes this out a LOT and turns it into something usable for insurance and ext pledges. Sorry, it got a little bulkier than I meant it to.
Here's what this does:

creates two config objects for insurance and ext pledges
makes a config route, accessible only by admins, to tweak them
hooks them into existing helpers that populate dropdowns
adds a rake task to generate stubbed objects in the model easily for orgs to fill in
tesssssssts

Here's what's TK:

add language to this
get a second opinion on the model structure
get a second opinion on names
get tests to pass. A lot of stuff relies on these objects existing now and I need to come up with a good holistic way to handle that.

PS We should not merge this before resolving the enumeration PR.
@lomky for review pls!

Brainstorming conclusion: this is awesome and clever. :100:
Happy to hash through any reservations you may have, but this looks like a solid ++ to me.

Since you can't really warm up the test suite with a rake task, I added a rails initializer that reads the Config key enum options and creates objects for them as part of boot. It adds some noise to the logs, but should work painlessly with the test suite. (he said, hopefully.)

Just kidding, still chokes on integration tests in the same way. Still an improvement in that we don't have to remember to manually bump rake test whenever we move something new to the configs, so I'm going to leave it, but I'll need to dig into that.

I think we have an honest working version of this in d435282 ! It's a little heavier than I'd like, and I really don't love DB queries in helpers, but the initializer is an absolute mess. Currently working on getting the test suite to pass.

(Note to self, make absolutely sure you bump the tests for ext pledges helper and the insurance helper methods, since those are now doing a lot more heavy lifting than they were.)

This turned into a real yak but I feel pretty great about where it ended up! We have a flexible, hopefully extendable model that we can pop into dropdown populator functions, and an easy adminuser-facing way to make it work.
The single remaining task here is to write tests for Config#autosetup and the new controller#index behavior. (And get CI to pass.) But after that I'll punch it up for ~ final review ~ and maybe we can ship it Sunday!

kaboom! @lomky for review please!
The transition process from our current yml to this is basically creating the config objects and mashing them into the config option text, separated by commas. Other than that, this should more or less be seamless.
This is wired up (with a few well-placed find_or_create_bys and an autosetup method) so that it shouldn't err out if anything doesn't exist.

Will give this the review it deserves ASAP.  :100:
Quick Thought: will this mean updates in any of our Docs?

Yeah, we'll want to bump the deploying or setup doc to include 'set
configs'. A++++ flag! I'll def bump that.
On Sat, Aug 5, 2017, 6:55 PM Kathryn Tipton<EMAIL_ADDRESS>wrote:

Will give this the review it deserves ASAP. 💯
Quick Thought: will this mean updates in any of our Docs?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/DCAFEngineering/dcaf_case_management/pull/1092#issuecomment-320474927,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADsA9DX-e6MaBgh9SYaQXZMhNoqsjXPDks5sVPLPgaJpZM4NvdzA
.

One suggestion: The order of the configs on the edit page isn't set, so on hitting "Update options for [Thing]" the page reloads and sometimes swaps them! It would be nice if the configs appeared in the same order each time.

@lomky we should be all clear on this! If this looks good to you and CI passes, you should go ahead and Smash That Merge Button.


API Gateway implementation?

Hi, is there an article of this series that covers the API Gateway implementation?
Thank you.

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

ID: 376577d9-c559-9d5d-e263-ff9f0fb6ac27
Version Independent ID: 29164c20-12a7-6bf2-a946-03ef2477d61b
Content: Creating a simple data-driven CRUD microservice
Content Source: docs/standard/microservices-architecture/multi-container-microservice-net-applications/data-driven-crud-microservice.md
Product: dotnet
GitHub Login: @CESARDELATORRE
Microsoft Alias: wiwagn

Here:
https://docs.microsoft.com/en-us/dotnet/standard/microservices-architecture/multi-container-microservice-net-applications/implement-api-gateways-with-ocelot
Also in the eBook .PDF (.NET Microservices), same chapter:
https://aka.ms/microservicesebook
And this related/original Blog Post in my blog:
https://blogs.msdn.microsoft.com/cesardelatorre/2018/05/15/designing-and-implementing-api-gateways-with-ocelot-in-a-microservices-and-container-based-architecture/
Hope it helps. 👍


Add possibility to disable animations for an open action

Sometimes its necessary to open a modal layer instantaneously without any animation taking place. For example when  a link to a page with the layer opened is shared, the receiver of the link would be puzzled by the unexpected initial animation.

Implemented on master (v1.5.0) and release-1.4.x (v1.4.0)
New Feature
The new optional feature skipAnimations.actionSelectorPath can take a JSON path to a property within the open action event, that tells whether to skip animations on opening or not. If it is true, animations will be skipped.


Dev > Master for release

Many thanks to contributing to nf-core/chipseq!
Please fill in the appropriate checklist below (delete whatever is not relevant). These are the most common things requested on pull requests (PRs).
PR checklist

[X] This comment contains a description of changes (with reason)
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If necessary, also make a PR on the nf-core/chipseq branch on the nf-core/test-datasets repo
[X] Ensure the test suite passes (nextflow run . -profile test,docker).
[X] Make sure your code lints (nf-core lint .).
[X] Documentation in docs is updated
[X] CHANGELOG.md is updated
[X] README.md is updated

Learn more about contributing: https://github.com/nf-core/chipseq/tree/master/.github/CONTRIBUTING.md

Ok. Everything passing. Phew. This has been a long time coming 😅
Ill add the DOI after the release.

Thanks @apeltzer Got stuck in meetings!


FIX: background script so extension loads

This fixes - ironically - an ordering issue with the variables in the background script introduced here:
https://github.com/uProxy/uproxy/commit/8f512d1c33573bc6635431d4e64c6abb83b4c2a0
(the no-use-before-declare tslint rule)

This change is

👍


Add new failing subprocess call, and check all subprocess calls

Dependency problems need to be sorted out before merging this.
(Also, it feels like this really would be less cluttered as a plain bash script, but your call.)

Shell might be better but I get the feeling that it always starts out seeming easier and then becomes harder once the tests pile up.


cp.lambda_max discrepancies

Max eigenvalue seem to be very different than when I calculate it with numpy. There is also a good chance that I am misunderstanding something. I believe numpy's solution is the correct one.
>>>cp.lambda_max(np.array([[0., 1.0],[-578.09782526, -67.43751973]])).value
>>>545.3615889098268
>>>np.linalg.eig(np.array([[0., 1.0],[-578.09782526, -67.43751973]]))[0]
>>>array([-10.07860459, -57.35891514])

Version

OS: Ubuntu 18.04
CVXPY Version: 1.0.25

Thanks for the help and/or suggestions for workarounds. Essentially, I want to put a constraint to ensure that the output of the optimization gives me a stabilizing controller.

The function lambda_max(A) is only convex when A is a symmetric (or Hermitian) matrix. You matrix is not symmetric, and that is why you are seeing strange behavior.
To get into details: CVXPY calls specialized a numpy function to compute lambda_max under these assumptions. Here is the code showing what happens when we apply your matrix:
>>> A = np.array([[0., 1.0],[-578.09782526, -67.43751973]])
>>> np.linalg.eigh(A)
>>> (array([-612.79910864,<PHONE_NUMBER>1]), array([[ 0.68621129, -0.72740227],
        [ 0.72740227,  0.68621129]]))

the first entry in the tuple returned by eigh is the eigenvalues, and that max of that vector is what CVXPY reported.
As to your specific problem-- I don't think convex optimization will help you. In order to enforce stability of a nonsymmetric matrix A, you need to get a handle on the real part of A's eigenvalues. The map from a nonsymmetric matrix to the largest eigenvalue (measured by real-part) is not convex. Now, there are some special nonconvex constraints that the optimization community has figured out how to handle. However a stability constraint is not one of those special cases. Even projecting A onto the set of stable matrices takes serious work. See https://arxiv.org/pdf/1611.00595.pdf for more information.

For developers / contributors: here are the TODO's for resolving this issue:

Add some basic input checking, where lambda_max.value raises an exception when the input is far-from-symmetric.
Check other symmetric-matrix atoms to see if .value can be called on nonsymmetric inputs.
Note: This won't happen if the input is the result of solving an optimization problem, since we constrain input expressions to be symmetric. This case happened because the input matrix was never subject to cvxpy's backend symmetry constraints.

@rileyjmurray Thanks so much! Ya, this makes sense.

Closed by #944 and #950.


some things are downloaded over http

there are a bunch of tools downloaded over http. this isn't great in the case of being somewhere where your wifi can't be trusted (onsite at a ctf for example ;-) )

Looks like:
yans@oth ~/tools $ grep "http://" */install
afl/install:curl http://lcamtuf.coredump.cx/afl/releases/afl-latest.tgz | tar xvz
df/install:wget -O - http://www.bay12games.com/dwarves/df_40_24_linux.tar.bz2 | tar xj
dislocker/install:wget http://www.hsc.fr/ressources/outils/dislocker/download/dislocker.tar.bz2
edgessh/install:svn checkout http://edgessh.googlecode.com/svn/trunk/ edgessh-read-only
evilize/install:wget http://www.mscs.dal.ca/~selinger/md5collision/downloads/evilize-0.2.tar.gz
fuzzgrind/install:wget -O - http://esec-lab.sogeti.com/dotclear/public/fuzzgrind/fuzzgrind_090622.tar.gz | tar xvz
gdb/install:curl http://ftp.gnu.org/gnu/gdb/gdb-7.10.tar.gz | tar xvz
hash-identifier/install:svn checkout http://hash-identifier.googlecode.com/svn/trunk/ hash-identifier-read-only
msieve/install:wget -O msieve.tar.gz http://sourceforge.net/projects/msieve/files/latest/download
qemu/install:curl http://wiki.qemu-project.org/download/qemu-<IP_ADDRESS>.tar.bz2 | tar xvj
reveng/install:curl http://jaist.dl.sourceforge.net/project/reveng/1.3.1/reveng-1.3.1.tar.gz | tar xvz
steganabara/install:curl http://www.caesum.com/handbook/steganabara-1.1.1.tar.gz | tar xvz
stegdetect/install:#wget -O - http://www.outguess.org/stegdetect-0.6.tar.gz | tar xvz
stegdetect/install:wget -O - http://archive.debian.org/debian-archive/debian/pool/main/s/stegdetect/stegdetect_0.6-3.tar.gz | tar xvz stegdetect-0.6/file/Magdir/varied.out
stegsolve/install:wget http://www.caesum.com/handbook/Stegsolve.jar -O stegsolve.jar
taintgrind/install:curl http://valgrind.org/downloads/valgrind-3.11.0.tar.bz2 | tar xvj
testdisk/install:curl http://www.cgsecurity.org/testdisk-7.0.linux26-x86_64.tar.bz2 | tar xvj
yafu/install:wget "http://downloads.sourceforge.net/project/yafu/1.34/yafu-1.34.zip?r=http%3A%2F%2Fsourceforge.net%2Fprojects%2Fyafu%2F&ts=1446080941&use_mirror=skylineservers" -O yafu.zip

The majority of the websites do not support SSL (or only with a deprecated and blocked cipher-suite or with an invalid certificate). See PR #50.

would it be reasonable to rehost some of the packages (can be done by making a github "release" and uploading files to that. or is that getting dangerously close to making ctf-tools a "real" package manager

Yeah, I'd rather not move in that direction. Too many headaches. As we all know, convenience trumps security ;-)


New playbook to setup disks for swift deployment

This playbook depends on an change to ceph_disks.py (renamed to scan_disks) to return a list of all disks (SSD and HDD) and their paths.

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

These commits need to be squashed down. There is really no need for 8 commits for this.

@j2sol if you are asking for a more targeted approach to unmount/zap because you are worried about affecting the sda drive, Siva's library explicitly leaves that drive out of his list of disks that it returns as to not disrupt any operation.

I'm concerned that this will target any SSD device on a system, whether it's a system in SL, or a different datacenter, or somebody's bare metal at their house. I'd prefer we target specific disks that are agreed upon (via settings) to be at swift's disposal.

Please rebase on master to pick up required fixes to pass tests.


sql: Allow restart savepoint to be renamed

From release notes:

Users can customize the auto-retry savepoint name used by the SAVEPOINT command by setting the force_savepoint_restart session variable. For example, SET force_savepoint_restart=true; BEGIN; SAVEPOINT foo will now function as desired. This session variable may also be supplied as part of a connection string to support existing code that assumes that arbitrary savepoint names may be used. [#31971][#31971] {% comment %}doc{% endcomment %}

Dup of https://github.com/cockroachdb/docs/issues/4176.


Allow to sweep private key for the channel opening.

Background
In a usual operation, the user is required to send his funds to the lnd wallet before opening a channel. This means that the user needs to make two transactions to open the channel which increases the cost of channel opening.
Expected behaviour
Assuming that the user is actually in control of the funds he would like to use for the channel creation, he could also import the private keys from another wallet and fund the channel with a single transaction.
Actual behaviour
User has to make two transactions or go through complicated proceeding of PSBT channel opening.

This is already possible via PSBT channel opening. IMO, it's a bad idea to allow users to pass lnd a raw private key. Even beyond that we'd need to do a chain scan just to get all the proper UTXO information, and even then it wouldn't be clear what inputs/outputs to use.


Translation to Chinese

New to GitHub, I will try my best to translate.

Thank you for your efforts! When I update to A16 I will definitely include these.

I saw that some people wants the description on steam to be translated. I can help if you want.

I am definitely not translating the Steam description since Steam does not offer multilingual Workshop pages. It would just be a mess. :P


Use standard package.json exports pattern

This updates the alpha branch package.json to use exports to declare the different available exports. I was having a lot of trouble using the ESM code in the current alpha with how it is currently set up.
This would be considered a breaking change, however it seems like the right direction to pursue for a future major release.
The first commit implements the proposed package exports changes.
The second commit updates the repository so that test code continues to compile. This was a little more involved.

The package.json exports pattern is only handled in TS 4.7+, so I updated typescript to that version.
Webpack also seemed like it needed to be updated due to webpack#14532 which otherwise causes an error like "Error: error:0308010C:digital envelope routines::unsupported."
The tests don't pass, however I believe the not passing behavior is the same as on the existing alpha branch.

Just putting this out here in case there is interest in taking the change upstream. I published this as @wnayes/electron-redux if anyone is interested.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


NH-26100 - Container metrics

Allow compute CPU Usage and CPU utilization on client

You will need to walk through https://github.com/solarwinds/swi-k8s-opentelemetry-collector/blob/master/doc/development.md#updating-tests-if-processing-is-changed to updated expected_output.json in integration test


Updates to showCustom Method

Feature / Problem

There is no way (in documentation) to add an id to a toast when the showCustom method is used. Therefore, there is no way to dismiss the toast by id using the dismiss method.

Callbacks can't be used with the showCustom method, so i resorted to using a GestureDetector to achieve onTap functionalities.

A solution

An id property should be accepted by the toast items created using the showCustom method to allow for further actions to be executed on the toasts.
Callbacks for the toast items.

Additional context
The package is wonderful and works great and the ability for users to customise their notifications how they want is in fact one of the features that make this package stand out from the rest. Now giving even more access and functionality to their custom notifications will be a wonderful feature.

Hey @iamjohnseun
I think you intend to dismiss a toast by an ID when you are using show Custom method, right?
to do that you can use the return value of the showCustom method
https://github.com/payam-zahedi/toastification/blob/31589038c3abf2a796b35474bd46f85c7a6f9e1e/lib/src/core/toastification.dart#L113
all show methods of Toastfication will return a ToastificationItem, and each ToastificationItem has an ID.
you can use that to dissmiss your toast.
check out this simple:
 final toastItem = toastification.show(title: Text('Hello World'));

  toastification.dismiss(toastItem);
  // or
  toastification.dismissById(toastItem.id);


functional enum's do not support specifing a shape

Using the functional API to create a enum does not allow for specifing a shape. RFC 3 does not mention the functional API at all, so I guess this is in some way intended, but it would be a useful feature for dynamically creating enum's anyways.
One can workaround this using
MyEnum = types.new_class('MyEnum', (Enum,), kwds={"shape": ...}, exec_body=lambda ns: ns[...] = ...)

Yeah, I'd say this is a bug.