[BUG] Allow Steve to handle generated fields.

Rancher Server Setup

Rancher version: v2.7.x
Installation option (Docker install/Helm Chart): N/A

Information about the Cluster

Kubernetes version: 1.25 <
Cluster Type (Local/Downstream): N/A

Describe the bug
When Steve returns requested resources it adds extra information on objects that does exist in ETCd via a Formatter
When a user attempts to update the new object kube-apiserver. Warnings are returned for adding unknown fields.
299 - unknown field "metadata.fields"
299 - unknown field "metadata.relationships"
299 - unknown field "metadata.state"
299 - unknown field "status.conditions[0].error"
299 - unknown field "status.conditions[0].transitioning"
299 - unknown field "status.conditions[1].error"
299 - unknown field "status.conditions[1].transitioning"

To Reproduce
Request a running pod via Steve /v1/pods
Add a new label to the pod
Attempt to persist the updated pod via Steve or kubectl.
Result
Notice that Warnings are returned.
Expected Result

No Warnings are returned.
Additional context

These warnings are now  sent by default in K8s  >= 1.25 due to https://kubernetes.io/docs/reference/using-api/api-concepts/#validation-for-unrecognized-or-duplicate-fields-setting-the-field-validation-level
It is possible for Steve to remove these added fields when updating an object.
This does not handle the use case where a user get's an object from the UI's yaml view and then attempts to use it elsewhere. It would be helpful if we documented which fields are added by Steve so the UI can strip them when displaying  YAML to a Users.
This is related to https://github.com/rancher/dashboard/issues/9016
And can cause failed messages, such as seen here https://github.com/rancher/dashboard/issues/9012

❌ REOPENED
Reproduction Environment

Component
Version / Type

Rancher version
2.7.4

Installation option
Helm (high availability)

RKE binary version used
1.4.4

If Helm Chart k8s cluster
1.25.6

Cert Details
external tls

Docker version
20.10.7, build f0df350

Helm version
v2.16.8-rancher2

Downstream cluster type
Linode RKE1

Downstream K8s version
v1.26.6-rancher1-1

Authentication providers enabled
local

Logged in user role
admin, standard user

Browser type
Microsoft Edge

Browser version
114.0.1823.82

Reproduction steps

Create a config map named test-cm-1
Provide the following data:

key: foo
value: bar

Save the config map
Once seted edit the conifg and add a label
Label that was added:

key: test-key
value: test-value

Make sure the browser network tab is opened before saving and submiting the request
After saving check the network tab in the browser for the response headers
See the following:

Warning:
299 - unknown field "metadata.fields"
Warning:
299 - unknown field "metadata.relationships"
Warning:
299 - unknown field "metadata.state"

Additional Info
Reproduction Results
✅ (Reproduction) Expected
For these unknown fields to be dropped before the PUT request goes through
❌ (Reproduction) Actual
These unknown fields are going through causing these warnings in the response header
Validation Environment

Component
Version / Type

Rancher version
v2.7-67422772955d5830b237fe84dbf1a26d266b55c1-head

Rancher commit link
https://github.com/rancher/rancher/commit/67422772955d5830b237fe84dbf1a26d266b55c1

Installation option
Helm (high availability)

RKE binary version used
1.4.4

If Helm Chart k8s cluster
1.25.6

Cert Details
external tls

Docker version
20.10.7, build f0df350

Helm version
v2.16.8-rancher2

Downstream cluster type
Linode RKE1

Downstream K8s version
v1.26.6-rancher1-1

Authentication providers enabled
local

Logged in user role
admin, standard user

Browser type
Microsoft Edge

Browser version
114.0.1823.82

Validation steps

Create a config map named test-cm-1
Provide the following data:

key: foo
value: bar

Save the config map
Once seted edit the conifg and add a label
Label that was added:

key: test-key
value: test-value

Make sure the browser network tab is opened before saving and submiting the request
After saving check the network tab in the browser for the response headers
See the following:

299 - unknown field "__clone"

The Payload the UI Sent
apiVersion: v1
kind: ConfigMap
metadata:
  name: test-cm-1
  annotations:
    {}
    #  key: string
  creationTimestamp: <REDACTED>
  labels:
    foo: bar
    #  key: string
  namespace: default
  resourceVersion: <REDACTED>
  uid:
  fields:
    - foo
    - 1
    - 0s
data:
  foo: bar
  #  key: string
__clone: true
#binaryData:  key: string
#immutable: boolean

RESULTS
✅ (Validation) Expected
For there not to be response header warnings 299
❌ (Validation) Actual
Getting response header warning: 299 - unknown field "__clone"

Moving back to to-test, the UI should address the remaining fields in https://github.com/rancher/dashboard/issues/9371

✅ PASS

Reproduction details... Click to expand

Component
Version / Type

Rancher version
2.7.4

Installation option
Helm (high availability)

RKE binary version used
1.4.4

If Helm Chart k8s cluster
1.25.6

Cert Details
external tls

Docker version
20.10.7, build f0df350

Helm version
v2.16.8-rancher2

Downstream cluster type
Linode RKE1

Downstream K8s version
v1.26.6-rancher1-1

Authentication providers enabled
local

Logged in user role
admin, standard user

Browser type
Microsoft Edge

Browser version
114.0.1823.82

Reproduction steps

Create a config map named test-cm-1
Provide the following data:

key: foo
value: bar

Save the config map
Once seted edit the conifg and add a label
Label that was added:

key: test-key
value: test-value

Make sure the browser network tab is opened before saving and submiting the request
After saving check the network tab in the browser for the response headers
See the following:

Warning:
299 - unknown field "metadata.fields"
Warning:
299 - unknown field "metadata.relationships"
Warning:
299 - unknown field "metadata.state"

Additional Info
Reproduction Results
✅ (Reproduction) Expected
For these unknown fields to be dropped before the PUT request goes through
❌ (Reproduction) Actual
These unknown fields are going through causing these warnings in the response header

Validation Environment

Component
Version / Type

Rancher version
v2.7-67422772955d5830b237fe84dbf1a26d266b55c1-head

Rancher commit link
https://github.com/rancher/rancher/commit/67422772955d5830b237fe84dbf1a26d266b55c1

Installation option
Helm (high availability)

RKE binary version used
1.4.4

If Helm Chart k8s cluster
1.25.6

Cert Details
external tls

Docker version
20.10.7, build f0df350

Helm version
v2.16.8-rancher2

Downstream cluster type
Linode RKE1

Downstream K8s version
v1.26.6-rancher1-1

Authentication providers enabled
local

Logged in user role
admin, standard user

Browser type
Microsoft Edge

Browser version
114.0.1823.82

Validation steps

Create a config map named test-cm-1
Provide the following data:

key: foo
value: bar

Save the config map
Once seted edit the conifg and add a label
Label that was added:

key: test-key
value: test-value

Make sure the browser network tab is opened before saving and submiting the request
After saving check the network tab in the browser for the response headers
See the following:

The Payload the UI Sent
RESULTS
✅ (Validation) Expected
299 Warnings covered in the PR are not present
✅  (Validation) Actual
299 Warnings covered in the PR are not present

Release note template
Synopsis of issue: Warnings about "unknown field" appeared in the UI when updating any Kubernetes object for Kubernetes versions 1.25 and up.
Resolved (or not): resolved
Versions: 2.7.0-2.7.6

@Shavindra Those are dashboard added properties and should not be sent when creating resource. We don't want to send anything that's not listed in the spec. For instance for containers see https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#pod-v1-core -->
https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#container-v1-core


storage: Fix some tests not working

Signed-off-by: Wish<EMAIL_ADDRESS>What problem does this PR solve?
Issue Number: ref #5237
What is changed and how it works?

Use future.get() instead of future.wait(). Otherwise exceptions in the std::async will be lost.

Drop min max cache for some cases, to avoid it being polluted after some data cleaning. This does not affect CI, as in CI each test runs in a new process.

Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/run-unit-test

/run-unit-test


Menu missing from CustomLearning Admin page

Describe the bug
Parts of the CustomLearning Admin portal are missing.
To Reproduce
Browsing through the CustomLearning Admin page.
Expected behavior
The left menu panel is missing from the CustomLearning Admin page.
Screenshots

Learning Pathways version number
v3.0.4 - I know this is outdated, but I haven't seen this issue before on our other tenants. Would updating fix the problem?
Additional context
Browser console:
M365 LP SOSE console.log

Hi @jnewgard-thrive
I have already tried deleting the CustomConfig list, but that didn't change anything in the Admin web part. I will try to see if upgrading would fix the issue.
Thanks!

Your other option is to view the browser's console to see if any errors are being shown related to learning pathways. We will phase out support for content updates with v3 soon though so I do encourage you to update to v4.

Hi @juliemturner and @jnewgard-thrive, the webpart is now updated to v4.2, but the issue still persists
Here's the browser console:
M365 LP SOSE console 2.log

I looked over the logs, but nothing really stood out to me...
Diagnostically you might try adding a new custom content pack pointing at the source learning pathways library just to validate that it's not any configuration parameter. In other words, set the Base URL property on the custom content pack to: https://pnp.github.io/custom-learning-office-365/learningpathways/

The issue still persists unfortunately :(

M365 LP SOSE console 3.log

Ok. well, given there are not errors in the logs I can't see any obvious reason why that content isn't visible, but it would suggest it's there but not displayed.
-Does the viewer web part work correctly?
-I am only looking at a partial screen shot is it possible that the content is pushed down and there are scroll bars visible?
-Do you have other SPFx customizations installed/enabled in the tenant/site collection?
-If the answers are Yes, No, No then the only solution I would have would be to inspect the html/css and see if the control that holds the content on that left side is hidden either with display = none in css and if so try to determine why, or alternately if the content is not even in the DOM.

The answer is Yes, No, No. I did inspect the html/css and there are some discrepancies compared to another tenant with the content visible. But I'm not sure how to solve this issue.
The main purpose of this would be to hide a few topics that the end-users do not use. Is there a way to hide them by editing the CustomConfig list?

The main purpose of this would be to hide a few topics that the end-users do not use. Is there a way to hide them by editing the CustomConfig list?

Yes, but that really has nothing to do with your problem. You definitely have something else loading on that page (maybe a tenant wide ext or something else) that is causing that menu not to display... the fact that it isn't is at this point almost definitely an HTML/CSS issue specific to your tenant... if we could replicate the issue I could certainly help figure it out...
Based on your previous comment I'm guessing you're only seeing this in this tenant? Is this a production tenant? Is this M365LP instance in production?

This is one of our customer's tenant where M365LP is deployed. None of our other customers are facing this issue and neither are our demo tenants. You're right this can be a tenant specific issue.

Hi @juliemturner and @jnewgard-thrive I have finally found a fix to the issue, there was a custom SharePoint theme that was interfering with the navigation, removing it fixed the issue. I thank you both for your help 😊.


scanner onReady|onErorr

It is good to have $emit methods from component for displaying preloader to the User.
Thanx!

@araimbekoff What we are thinking is to offer a slot option to allow a configurable preloader that the plugin would expose.
What do you think ?

not bad. with the condition that the component is transferred to an arbitrary

Closing this in favour of #6


Update mysql-connector-java to 8.0.27

Updates mysql:mysql-connector-java from 8.0.24 to 8.0.27.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "mysql", artifactId = "mysql-connector-java" } ]

labels: library-update, semver-patch

Superseded by #59.


Add link to the Orleans framework

Even though Orleans was already mentioned in https://github.com/Microsoft/dotnet/blob/master/dotnet-developer-projects.md it's one of the most active repositories at https://github.com/dotnet, still gaining momentum, and there is every reason to believe it will become standard choice for distributed applications alongside with https://github.com/akkadotnet/akka.net. Given all of the above I'm sure that Orleans deserves a place in Readme.md

Thanks @wanderq. Appreciated. Good call.


Add PR tests

Some ideas:

JSON Key
Check

Name
^.{2,}$ (2 characters or more)

Description
same as Name

Owner
^[^\s]+$

SupportedDriverVersion
Must be lower than newest release, and have all 4 version subvalues (e.g. <IP_ADDRESS>, not 0.6.4)

PluginVersion
^\d+(\.\d+){1,2}$ or less strict

*Url
must be curl'able (or similar)

CompressionFormat
Whatever we support, zip only for now? Can skip this check

LicenseIdentifier
Ideally, something from a predermined list, but otherwise same check as Owner

Already covered in tests:

SHA256
DownloadUrl

Oops, we already have some tests:
https://github.com/OpenTabletDriver/Plugin-Repository/blob/acc79dccf8325459e2e3f6b2be8bd4c197c222ed/validate.sh
Looks like SHA256 (and DownloadUrl) are the only ones getting tested there, as well as checking whether the file is parseable at all.

Updated OP to address issues fixed in #89


Optional field secret_base64_encoded does not work.

The optional configuration field secret_base64_encoded doesn't work when set to false.
Auth0JWT::decode will always attempt to decode the secret, even if it was never base64encoded to begin with, and verifying the signature fails.

To test:
Set the client_secret option to a plain text value instead of a base64encoded value.

Nvm, should've compared versions...

@paulinevos you manage to make it work?


Automatically pick the fastest pipeline (lowest ping time) for new jobs

If a new job is created and there are multiple open pipelines, ping them all and give the job to the one with the lowest ping time.
(Props to MrRadar for the suggestion, an improvement on the idea of manually setting country and region for each pipeline.)

If anything, then each (available) pipeline should ping the target site and the pipeline with the lowest ping to the target site should get the job (rather than the one with the lowest ping to the control node). But in reality, there's almost never more than one slot empty, so this would hardly ever be relevant.


Misc fixes and updated CI

Fix race condition when refreshing token.
Fixed some tests to work with Go 1.14.
Updated CI to run latest two versions of Go.
Thank you for your contribution to Go-AutoRest! We will triage and review it as soon as we can.
As part of submitting, please make sure you can make the following assertions:

[ ] I've tested my changes, adding unit tests if applicable.
[ ] I've added Apache 2.0 Headers to the top of any new source files.
[ ] I'm submitting this PR to the dev branch, except in the case of urgent bug fixes warranting their own release.
[ ] If I'm targeting master, I've updated CHANGELOG.md to address the changes I'm making.

Fixes
https://github.com/Azure/go-autorest/issues/502
https://github.com/Azure/go-autorest/issues/513


RBAC store into DB wrong type

I config components in config.php with
'authManager' => [
	'class' => 'yii\rbac\DbManager',
	'defaultRoles' => ['member'],
],

But when
$auth = Yii::$app->authManager;
$adminRole = $auth->createPermission('admin');
$adminRole->description = "Admin Role";
$auth->add($adminRole);
I seen in DB type = 2. It's wrong..

whats wrong?
permission type are 2.
https://github.com/yiisoft/yii2/blob/master/framework/rbac/Item.php#L19

@SilverFire but I use follow:
$auth = Yii::$app->authManager;

$adminRole = $auth->getRole('admin');

It return empty record because I use getRole function query with Type = 1 not yet Type = 2.


Fixed the description.

I just just changed the description.

Thank you very much for the errata.


MSIX Dynamic Dependencies - allow any process to use MSIX Framework packages

Proposal: MSIX Dynamic Dependencies (aka DynamicDependencies aka DynDep)
Summary
Provide APIs to enable access to packaged content at runtime, regardless if the caller is packaged or not. This supplements the MSIX appmodel's current static dependency support (via  in appxmanifest.xml) with a dynamic runtime equivalent. It also allows non-packaged processes (which have no appxmanifest.xml) to use packaged content.
Microsoft-internal task 23447728
Rationale

Enable all apps (MSIX-packaged and not) to use framework packages
Support dynamic selection of framework packages at runtime to complement static selection of framework packages at development/install time (via appxmanifest.xml)
DynamicDependencies is the moral equivalent of LoadLibrary - DynamicDependencies supplements static (manifest'd) dependencies as LoadLibrary supplements EXE/DLL import references.

This aligns with Project Reunion's roadmap:

Foundational technology enabling new Project Reunion features to be delivered via Framework packages but accessible by all applications (packaged and not-packaged)
Enable all applications (packaged and not-packaged) to use WinUI's Framework package

Scope

Capability
Priority

APIs available to MSIX and non-MSIX applications
Must

APIs to add and remove a package dependency dynamically at runtime
Must

API to prevent removal of packages not in use by running processes (i.e. install-time pinning)
Must

APIs to enumerate package dependencies in use
Could

APIs to enumerate defined package dependencies (install-time pinned)
Could

Win32 API
Must

WinRT API
Should

Important Notes
All processes have a package graph. A process may be created with entries in its package graph; this is referred to as the 'static package graph'.
Packaged processes (i.e. a process with package identity) are created with a static package graph per their AppxManifest.xml. A process' static package graph cannot be altered, but it can be supplemented at runtime via the Dynamic Dependency API.
Processes without package identity have an no static package graph. They can modify their package graph using the Dynamic Dependency API.
MddPinPackageDependency defines a package dependency.
MddAddPackageDependency determines a package that satisfies a package dependency and updates the caller's process. This includes adding the resolved package to the process' package graph, updating the Loader to include the resolved package in the DLL Search Order, etc. The package dependency is resolved to a specific package if not already resolved.
A resolved PackageDependency is represented by MDD_PACKAGE_DEPENDENCY_CONTEXT.
Once a PackageDependency is resolved to a package all further MddAddPackageDependency calls yield the same result until the package dependency is unresolved. Resolved package dependencies are tracked by User + PackageDependencyId. This ensures multiple overlapping calls to MddAddPackageDependency yield the same result. A package dependency is unresolved when the last MDD_PACKAGE_DEPENDENCY_CONTEXT is closed (via MddRemovePackageDependency or process termination).
MddRemovePackageDependency removes the resolved PackageDependency from the calling process' package graph.
MddUnpinPackageDependency undefines a package dependency previously defined via PinPackageDependency.
PackageDependency definitions and usage are tracked and managed on a per-user basis.
PackageDependency definitions are not persisted or tracked across reboots if MddPinPackageDependency is called with MddPinPackageDependency_LifecycleHint_Process. Specify MddPinPackageDependency_LifecycleHint_FileOrPath or MddPinPackageDependency_LifecycleHint_RegistrySubkey for PinPackageDependency to persist the definition until explicitly removed via MddUnpinPackageDependency or the specified lifetime artifact is deleted.
If concurrent processes need the same package resolution for a defined criteria they should share the packageDependencyId returned by MddPinPackageDependency. Concurrent processes running as the same user calling MddAddPackageDependency with the same packageDependencyId get the same resolved package added to their package graph. This enables multiple concurrent processes needing the same package resolution get a consistent answer.
Package dependencies can only be resolved to packages registered for a user. As packages cannot be registered for LocalSystem the Dynamic Dependencies feature is not available to callers running as LocalSystem.
Win32 API
MsixDynamicDependency.hpp
enum class MddPinPackageDependency : uint32_t
{
    MddPinPackageDependency_None                               0,
    MddPinPackageDependency_DoNotVerifyDependencyResolution    0x00000001,
    MddPinPackageDependency_LifecycleHint_Process              0,
    MddPinPackageDependency_LifecycleHint_FileOrPath           0x00000002,
    MddPinPackageDependency_LifecycleHint_RegistrySubkey       0x00000004,

     // Define the package dependency for the system, accessible to all users
     // (default is the package dependency is defined for a specific user).
     // This option requires the caller has adminitrative privileges.
    MddPinPackageDependency_ScopeIsSystem                      0x00000008,
};
DEFINE_ENUM_FLAG_OPERATORS(MddPinPackageDependency)

enum class MddAddPackageDependency : uint32_t
{
    MddAddPackageDependency_None                       0,
    MddAddPackageDependency_OnlyUseFirstPackageFamily  0x00000001,
    MddAddPackageDependency_PrependIfRankCollision     0x00000002,
};
DEFINE_ENUM_FLAG_OPERATORS(MddAddPackageDependency)

#define PACKAGE_DEPENDENCY_RANK_DEFAULT 0

enum class MddPackageDependencyProcessorArchitectures : uint32_t
{
    MddPackageDependencyProcessorArchitectures_None = 0,
    MddPackageDependencyProcessorArchitectures_Neutral = 0x00000001,
    MddPackageDependencyProcessorArchitectures_X86     = 0x00000002,
    MddPackageDependencyProcessorArchitectures_X64     = 0x00000004,
    MddPackageDependencyProcessorArchitectures_Arm     = 0x00000008,
    MddPackageDependencyProcessorArchitectures_Arm64   = 0x00000010,
    MddPackageDependencyProcessorArchitectures_X86A64  = 0x00000020,
};
DEFINE_ENUM_FLAG_OPERATORS(MddPackageDependencyProcessorArchitectures)

DECLARE_HANDLE(MDD_PACKAGEDEPENDENCY_CONTEXT);

// Define a package dependency expressing a relationship between an
// application and a packaged component or application. The criteria
// for a PackageDependency (package family name, minimum version, etc)
// may match multiple packages, but ensures Deployment won't remove
// a package if it's the only one satisfying the PackageDependency.
//
// @note A package matching a PackageDependency pin can still be removed
//       as long as there's another that satisfies the PackageDependency.
//       For example, if Fwk-v1 is installed and a PackageDependency specifies
//       MinVersion=1 and then Fwk-v2 is installed, Deployment could remove
//       Fwk-v1 because Fwk-v2 will satisfy the PackageDependency. After Fwk-v1
//       is removed Deployment won't remove Fwk-v2 because it's the only package
//       satisfying the PackageDependency. Thus  Fwk-v1 and Fwk-v2 (and any other
//       package matching the PackageDependency) are 'loosely pinned' â€“ Deployment
//       guarantees it won't remove a package if it would make a PackageDependency
//       unsatisfied.
//
// A PackageDependency specifies criteria (package family, minimum version, etc)
// and not a specific package. Deployment reserves the right to use a different
// package (e.g. higher version) to satisfy the PackageDependency if/when
// one becomes available.
//
// @param user the user scope of the package dependency. If NULL the caller's
//        user context is used. MUST be NULL if MddPinPackageDependency_ScopeIsSystem
//        is specified
// @param lifetimeArtifact MUST be NULL if MddPinPackageDependency_LifecycleHint_Process (default)
// @param packageDependencyId allocated via LocalAlloc; use LocalFree to deallocate
//
// @note MddPinPackageDependency() fails if the PackageDependency cannot be resolved to a specific
//       package. This package resolution check is skipped if
//       MddPinPackageDependency_DoNotVerifyDependencyResolution is specified. This is useful
//       for installers running as user contexts other than the target user (e.g. installers
//       running as LocalSystem).
STDAPI MddPinPackageDependency(
    PSID user,
    _In_ PCWSTR packageFamilyName,
    PACKAGE_VERSION minVersion,
    MddPackageDependencyProcessorArchitectures packageDependencyProcessorArchitectures,
    PCWSTR lifetimeArtifact,
    MddPinPackageDependency flags,
    _Outptr_result_maybenull_ PWSTR* packageDependencyId);

// Undefine a package dependency. Removing a pin on a PackageDependency is typically done at uninstall-time.
// This implicitly occurs if the package dependency's 'lifetime artifact' (specified via MddPinPackageDependency)
// is deleted. Packages that are not referenced by other packages and have no pins are elegible to be removed.
//
// @warn MddUnpinPackageDependency() requires the caller have administrative privileges
//       if the package dependency was pinned with MddPinPackageDependency_ScopeIsSystem.
STDAPI MddUnpinPackageDependency(
    _In_ PCWSTR packageDependencyId);

// Resolve a previously-pinned PackageDependency to a specific package and
// add it to the invoking process' package graph. Once the dependency has
// been added other code-loading methods (LoadLibrary, CoCreateInstance, etc)
// can find the binaries in the resolved package.
//
// Package resoution is specific to a user and can return different values
// for different users on a system.
//
// Each successful MddAddPackageDependency() adds the resolve packaged to the
// calling process' package graph, even if already present. There is no
// duplicate 'detection' or 'filtering' applied by the API (multiple
// references from a package is not harmful). Once resolution is complete
// the package stays resolved for that user until the last reference across
// all processes for that user is removed via MddRemovePackageDependency (or
// process termination).
//
// MddAddPackageDependency() adds the resolved package to the caller's package graph,
// per the rank specified. A process' package graph is a list of packages sorted by
// rank in ascending order (-infinityâ€¦0â€¦+infinity). If package(s) are present in the
// package graph with the same rank as the call to MddAddPackageDependency the resolved
// package is (by default) added after others of the same rank. To add a package
// before others o the same rank, specify MddAddPackageDependency_PrependIfRankCollision.
//
// Every MddAddPackageDependency should be balanced by a MddRemovePackageDependency
// to remove the entry from the package graph. If the process terminates all package
// references are removed, but any pins stay behind.
//
// MddAddPackageDependency adds the resulting package to the process' package
// graph, per the rank and options/flags parameters. The process' package
// graph is used to search for DLLs (per Dynamic-Link Library Search Order),
// WinRT objects and other resources; the caller can now load DLLs, activate
// WinRT objects and use other resources from the framework package until
// MddRemovePackageDependency is called. The packageDependencyId parameter
// must match a package dependency defined for the calling user or the
// system (i.e. pinned with MddPinPackageDependency_ScopeIsSystem) else
// an error is returned.
//
// @param packageDependencyContext valid until passed to MddRemovePackageDependency()
// @param packageFullName allocated via LocalAlloc; use LocalFree to deallocate
STDAPI MddAddPackageDependency(
    _In_ PCWSTR packageDependencyId,
    INT32 rank,
    MddMddAddPackageDependency flags,
    _Out_ MDD_PACKAGEDEPENDENCY_CONTEXT* packageDependencyContext,
    _Outptr_opt_result_maybenull_ PWSTR* packageFullName);

// Remove a resolved PackageDependency from the current process' package graph
// (i.e. undo MddAddPackageDependency). Used at runtime (i.e. the moral equivalent
// of FreeLibrary).
//
// @note This does not unload loaded resources (DLLs etc). After removing
//        a package dependency any files loaded from the package can continue
//        to be used; future file resolution will fail to see the removed
//        package dependency.
STDAPI MddRemovePackageDependency(
    _In_ MDD_PACKAGEDEPENDENCY_CONTEXT packageDependencyContext);

// Return the package full name that would be used if the
// PackageDependency were to be resolved. Does not add the
// package to the process graph.
//
// @param packageFullName allocated via LocalAlloc; use LocalFree to deallocate
STDAPI MddGetResolvedPackageFullNameForPackageDependency(
    _In_ PCWSTR packageDependencyId,
    _Outptr_result_maybenull_ PWSTR* packageFullName);

// Return TRUE if packageDependencyId1 and packageDependencyID2
// are associated with the same resolved package.
STDAPI_(BOOL) MddArePackageDependencyIdsEquivalent(
    _In_ PCWSTR packageDependencyId1,
    _In_ PCWSTR packageDependencyId2);

// Return TRUE if PackageDependency pins would produce the same package
// when resolved e.g. whether they share the same packageFamilyName,
// minVersion, and packageDependencyProcessorArchitectures values.
STDAPI_(BOOL) MddArePackageDependencyContextsEquivalent(
    _In_ const PACKAGEDEPENDENCY_CONTEXT* packageDependencyContext1,
    _In_ const PACKAGEDEPENDENCY_CONTEXT* packageDependencyContext2);

NOTE: All APIs prefixed with Mdd/MDD for MSIX Dynamic Dependencies.
WinRI API
namespace Microsoft.ApplicationModel
{
enum PackageDependencyProcessorArchitectures
{
    None    = 0,
    Neutral = 0x00000001,
    X86     = 0x00000002,
    X64     = 0x00000004,
    Arm     = 0x00000008,
    Arm64   = 0x00000010,
    X86A64  = 0x00000020,
};

runtimeclass PinPackageDependencyOptions
{
    PinPackageDependencyOptions();

    PackageDependencyProcessorArchitectures Architectures;
    boolean DoNotVerifyDependencyResolution;
    String lifetimeArtifactFileOrPath;
    String lifetimeArtifactRegistrySubkey;
}

runtimeclass AddPackageDependencyOptions
{
    AddPackageDependencyOptions();

    int Rank;
    boolean OnlyUseFirstPackageFamily;
    boolean PrependIfRankCollision;
}

runtimeclass PackageDependency
{
    PackageDependency(String id);

    String Id { get; }

    static boolean AreEquivalent(String packageDependencyId1, String packageDependencyId2);

    boolean AreEquivalent(PackageDependency otherPackageDependency);

    static PackageDependency Pin(
        String packageFamilyName,
        PackageVersion minVersion,
        PinPackageDependencyOptions options);

    static PackageDependency PinForUser(
        Windows.System.User user,
        String packageFamilyName,
        PackageVersion minVersion,
        PinPackageDependencyOptions options);

    static PackageDependency PinForSystem(
        String packageFamilyName,
        PackageVersion minVersion,
        PinPackageDependencyOptions options);

    void Unpin();

    PackageDependencyContext Add();
    PackageDependencyContext Add(AddPackageDependencyOptions options);

    void Remove();
}

struct PackageDependencyContextId
{
    UInt64 Id;
};

runtimeclass PackageDependencyContext : ICloseable
{
    PackageDependencyContext(PackageDependencyContextId);   //Parameter is MDD_PACKAGEDEPENDENCY_CONTEXT

    PackageDependencyContextId Context { get; } //Return value is MDD_PACKAGEDEPENDENCY_CONTEXT
    String PackageFullName { get; }

    static boolean AreEquivalent(PackageDependencyContextId packageDependencyContextId1, PackageDependencyContextId packageDependencyContextId2);

    boolean AreEquivalent(PackageDependencyContext otherPackageDependencyContext);

    void Remove();
}
}

Open Questions
Q: Package dependencies are only resolved for Framework packages. Should other package types (Main, Resource, Optional) be supported?
Q: A package dependency's critieria includes user, package family, minimum version, and processor architecture. Are there other qualifiers we should be consider?
Q:WinRT: How should 'lifetimeArtifact' and MddPinPackageDependency_LifecycleHint* be expressed in the WinRT API? Some ideas:

String file; String regkey; if both null then it's Process
String lifetimeArtifact; boolean isFile; boolean isReg; boolean isProcess; and only 1 can be true
ILifetimeArtifact property with multiple implementations e.g. FileLifetimeArtifact = { string file; } vs RegistryLifetimeArtifact = { HKEY root; string subkey; } vs Process=null
?

Looks pretty reasonable.  A few issues:

Don't use declspec(dllimport/export) ... use STDAPI and use a .def file & import library for the "flat C" flavor of the API
Use enum class Foo : uint32_t when declaring enumerations (also lets you drop the Foo_Bar prefix on everything.)
The ...NounAreEquivalent should be ...PluralnounAreEquivalent
PinPackageDependencyOptions needs a default ctor so it can be constructed
Should the ...Options types be struct typed since we're being a little looser with versioning here?
For the context type, use a "strongly typed cookie" - the pattern is struct ThingContextId { UInt64 Id; } and then there's methods like static ThingContext GetFromContextId(ThingContextId), etc. ... it's not clear the public surface needs to convert to-from a HANDLE here anyhow, can that be removed?
Feel free to remove the static AreEquivalent method and keep a bool Equals member method instead.
The PackageDependencyContext should probably implement IClosable - see internal Patterns document for more on this (coming to the public soon!)

Thanks Jon!
Approved, done:

declspec/STDAPI
Pluralnoun NOTE:It's ArePluralnounEquivalent
PinPackageDependencyOptions ctor
ICloseable
context strongly-typed-cookie

Rejected:

Equals - The comparisons are for functional equivalency. PackageDependency objects are equivalent if the subset of underlying data match (e.g. same pkgfamilyname but different lifetime artifact). Equals implies same, but that would involve more data than we're checking here. The purpose is "Do these 2 definitions define the same criteria for package resolution?" Hence, 'Equivalent' not 'Equals'. 'PackageResolutionCriteriaAreEqual' is more accurate but a mouthful  I'm open to suggestions

Open issues:

...Options = struct => Good question. Do our API guidelines cover this yet? Would struct restrict us to foundation data types? We need boolean, integers, strings and enums. I could see a use down the road for lists; those aren't compatible with structs, right? If we make a runtimeclass FooOptions2 { struct Foo Foo; ...new v2 properties... } where v1=struct v2=runtimeclass that inconsistency isn't a big deal (if/when that day comes)?

Q: Will this work downlevel?

Q: Will this work downlevel?

Yes! The target is down to whatever releases Project Reunion supports.
A design proposal is coming shortly. That'll explain 'how' we can make the magic happen. Please stay tuned

How exactly does this work from an end user perspective? As an app developer, do I have to call these APIs in my main method? Or will there be something in the SxS manifest that declares the package dependency?

Question about this design. I presume the AppX packages that would be referenced using this API would be framework packages. That’s perfectly OK, until we start implementing APIs with broker processes that might need to be run in full trust. Per that linked doc, framework packages cannot declare either applications (making it awfully hard to run the broker as a separate app for boundary purposes) or capabilities (meaning we are limited to AppContainer-only APIs, since we can’t specify runFullTrust). As I understand it, only framework packages can be listed as dependencies in AppX manifests, and modification/optional packages must specify the exact PFN that they expect to be loaded into, so those won‘t work either. Could someone please clarify this? Thanks!

@stevenbrix Yes, these are APIs apps would call at (un)install and runtime. The basic flow is

Call Pin @ install-time
Call Unpin @ uninstall-time
Call Add in your app before using the framework's content. main() is a common answer but could be later if you choose
Call Remove in your app when done with a framework. Or don't call at all and it's effectively done at process termination

For a rough comparison to an MSIX (packaged) application...

Pin is akin to declaring a  in appxmanifest.xml
Add is akin to...
...the Deployment stack resolving that  to a specific package
...updating the process' package graph so the specific framework's content can be found by LoadLibrary, ActivateInstance, etc
Remove has no direct analogue in an MSIX application
Unpin is akin to uninstalling a package for a user e.g. packageManager->RemovePackageAsync()

A packaged app has a package graph from process creation until process termination. In fact, all process have a package graph, it's just empty/null for non-packaged processes. Either way, a process' package graph is set at process creation (be it a list of packages or empty/null) and is is constant until process termination. Dynamic Dependencies supplements that static package graph with the ability to dynamically alter a process' package graph at runtime.
Unfortunately SxS is no help as Windows lacks the hooks to setup the necessary information at process creation. But let's assume for a moment we could change Windows  Would that be helpful? When would you find it preferable to use the SxS manifest vs the API? Would it still be interesting it it was limited compared to the API e.g. if MddRemovePackageDepedency() couldn't remove such package dependencies? Would this SxS option be attractive if it required a future version of Windows?

@wjk Yes, your understanding is correct.
The Dynamic Dependency API targets Framework packages. That's both a pressing need and a natural fit for how framework packages work -- used by other packages, don't provide their own process/runtime identity etc.
Can you elaborate on what you'd like to accomplish (that frameworks don't suffice)?

@DrusTheAxe See #62 for an example. If that proposal were to be implemented, we would not be able to use a framework package to deploy it, as it needs to supply a full-trust helper application that uses App Services to communicate with the main app, and framework packages cannot define those. Thanks!

@wjk For some of our planned features we need brokering so AppContainer/Universal apps can get access (with appropriate control) to other user content. We’ve discussed a model like this:

Define a framework package with the in-process part of the brokered operation
Define a main package with an appservice extension and the runFullTrust capability
The UWP app calls into code from the framework package, which calls through the appservice entrypoint
The full-trust component does what it needs to achieve the goal
This is how an app can implement brokered access from an AppContainer/Universal app to the clipboard or other functionality. But instead of everybody building their own one-off "access the clipboard through my custom broker implementation" Project Reunion will do the work. We can provide a common implementation and apps just call "ProjectReunion.Clipboard.RequestWriteAsync(dataPackage)"

In this picture the framework and main package work collectively to provide the end-to-end integrated solution. Better together :-)
Yay for packaged applications. The DynamicDependencies proposal goes one step further, providing access to unpackaged Win32 (MSI, setup.exe, xcopy-deploy, ...) apps as well as packaged apps.
We're still mulling over whether AppService is the right technology for this, and how to ensure your Win32 application can co-deploy that Framework Package and its Main Package helpers. Stay tuned real soon for more on that front.

I've posted a PR with a spec for this proposal => Spec for MSIX Dynamic Dependencies #108
Feedback is welcome :-)

@DrusTheAxe would it be possible to use the same manifest file for unpackaged apps? This seems like the appropriate time and place to converge the appxmanifest and sxs manifest into something that works in all scenarios. Then we don't need to put an extra burden on the app author, or tooling to support multiple different techs, which I imagine will just continually diverge over time. The build just produces a ProjectReunionManifest.xml, which is an appxmanifest.xml with some metadata that says "this app isn't running in a container"

would it be possible to use the same manifest file for unpackaged apps? This seems like the appropriate time and place to converge the appxmanifest and sxs manifest into something that works in all scenarios

Are you asking/suggesting if it's possible to make the Dynamic Dependency behavior declarative and automagically happen at process creation, with the right declarative work by a developer?
Or could we merge SxS and MSIX manifests to have a single artifact?
Or could we leverage SxS to avoid the need for a helper 'sidecar' Main package?
Or something else?
Are you aware of the recent SxS support to add package identity to a non-packaged app via <msix>? Is that related to your query? Though that's more a complementary use of SxS and MSIX than a merging of manifests.
Hoping to get a clearer idea what's on your mind before trying to answer.

Are you aware of the recent SxS support to add package identity to a non-packaged app via ? Is that related to your query? Though that's more a complementary use of SxS and MSIX than a merging of manifests.

@DrusTheAxe I was not aware that already existed, that's amazing!! That's a huge part of the puzzle, so it's cool to see that already working. Could this be extended to make https://github.com/microsoft/ProjectReunion/issues/55 a reality?

Or could we merge SxS and MSIX manifests to have a single artifact?

Or could we leverage SxS to avoid the need for a helper 'sidecar' Main package?

Yes and yes 😄
Ultimately, it would be nice to have a single manifest, so that we can have a single build pipeline, single winrt activation story, single manifest designer in visual studio, and single inner-loop workflow for developers, and single next best thing.
IMO, a perfect design wouldn't require me (as an app developer) to do anything extra, like having to pin dependencies or give myself identity in an unpackaged app.  All of this should be in the manifest (which it already is for packaged apps), and the system should just take care of it for me when my app launches.
Here's some rough c++ psuedo-code to describe what I'm talking about:
bool hasManifest = ExistsReunionManifest();
if (hasManifest && !IsRegistered())
{
   // App isn't registered. Loose register, this can do 3 different things:
   // 1. Install MSIX dependencies
   // 2. Grant identity
   // 3. Run in container
   RegisterDynamicReunionManifest();
}

And yes, any one of these things can fail during startup, so there needs to be an elegant way the app can handle this. I don't show this, but I know we can figure that out. Even if it were designed in such a way that higher level frameworks like WPF or WinUI handle this special behavior, that's fine by me.
This makes our story very simple:

You build an app with a manifest, and the exact same build pipeline and app startup path are used for all Windows apps
To provide the best experience for customers, you put your app and manifest in an .msix, and submit it to the store/winget.

@stevenbrix

a perfect design wouldn't require me (as an app developer) to do anything extra,
like having to pin dependencies or give myself identity in an unpackaged app

Of course. ProjectReunion is striving to unify and expand the Windows platform but, much like Rome, Windows is big and broad and wasn't built in a day. It'll take us time to bring some features to where we all desire them to be. And some features are more difficult than others to make available as smooth and seamlessly as we'd like, without at least some changes to Windows itself. That's why feedback like yours is so important, to help us understand where we should focus our efforts. To identify where we can provide great solutions today, and where we need to invest in foundational improvements to improve them going forward.

Here's some rough c++ psuedo-code to describe what I'm talking about:

What if I said you could do that today?... 🤨
When we built the plumbing described in Identity, Registration and Activation of Non-packaged Win32 Apps we also identified how it plays well with the 'XCOPY-install' model -- no 'install', just dump some files on a machine, run an app and have it discover on the fly if work's needed and handle it. I don't see this mentioned in the blog post (or elsewhere); I'll follow up on that. But it's actually quite easy to do, given the new features outlined in that blog:

Create a 'sparse package'
Create your exe with an embedded SxS manifest containing
In your main() detect if (not running with identity) then { Install(mysparsepackage.msix); relaunch self }

Step 2 is the key here
Historically, activating a packaged app required Windows (ultimately) go through ActivateApplication() to start the process appropriately (package identity, RuntimeBehavior, TrustLevel and other manifest activation information. Let's call this Activation-via-ActivationManager.
You could make a DesktopBridge application in the classic Win32 sense (Winmain etc) instead of a Universal app, but you couldn't just run the executable. CreateProcess("foo.exe") would fail.(a)
(a) Yes we've added <Extension Category="windows.appExecutionAlias"....> that can make some of those scenarios work, but not quite all. A handy improvement, but not a complete solution. Not quite the same as just double-click an exe in Explorer and run.
The <msix> element is the game changer.
During process creation, if the executable has a SxS manifest containing <msix> we check if that package is registered for the user and if so, we create the process just like ActivateApplication() would! Let's call this Activation-via-CreateProcess 😄 Regardless whether you CreateProcess("kittens.exe") or ActivateApplication("Kittens_<IP_ADDRESS>_x86__1234567890abc!App") you get a process with the same package identity and other properties.
Now here's the the critical piece.
If process creation sees <msix> in the SxS manifest but that package is not registered, we create the process anyway, as if there was no <msix> in the SxS manifest. We don't fail.
This is where step 3 comes in.
The kittens.exe process will be created whether or not the Kittens package is registered for the user. You can detect this in your app and adapt e.g.
int main()
{
    // Are we running with package identity?
    UINT32 n = 0;
    if (GetCurrentPackageFullName(&n, nullptr) == ERROR_NO_APPMODEL_PACKAGE)
    {
        // Nope. Let's correct that...
        ...install kittens package e.g. packageManager.AddPackageByUriAsync()...
        ...launch self...
        ...quit...
    }

    // We're running with package identity! Let's roll
    ...
}

Per your checklist...

MSIX dependencies installed? Check.
Identity granted? Check.
Run in container (and/or other activation properties, as specified in your appxmanifest)? Check.

Voila! All the runtime benefits, with no explicit, user-driven or visible 'install' step.
You can further extend this with Dynamic Dependencies per your pseudo-code's RegisterDynamicReunionManifest(). they're complementary techniques.
One caveat of this 'XCOPY-install friendly' technique is it requires Windows >= 10.0.19041.0 (aka May 2020 Update aka 20H1).
How does that sound?

When we built the plumbing described in Identity, Registration and Activation of Non-packaged Win32 Apps we also identified how it plays well with the 'XCOPY-install' model -- no 'install', just dump some files on a machine, run an app and have it discover on the fly if work's needed and handle it. I don't see this mentioned in the blog post (or elsewhere); I'll follow up on that. But it's actually quite easy to do, given the new features outlined in that blog:

Thanks for sharing a link to this blog. The blog mentions that there is no VS support for this, are there any plans to add VS tooling for all of this to make it smoother?
The meta point I'm trying to make is a) I don't see anything in these specs about how these can be tooled so that they are easy for developers to accomplish and b) I don't want there to be separate tooling for unpackaged and packaged apps.

are there any plans to add VS tooling for all of this to make it smoother?

Are you referring to the blog post, this Dynamic Dependencies feature or something else? Just want to make sure I understand the question

a) I don't see anything in these specs about how these can be tooled so that they are easy for developers to accomplish

Agreed, it's not just a matter of it can work, it should also be easy to accomplish. Tooling's been an active area of discussion and investigation. What sort of tooling would you desire? Is something akin to VS' current new-UWP-project what you have in mind? GUI property pages etc to add/edit? Is VS your environment of interest? VSCode? Other?

b) I don't want there to be separate tooling for unpackaged and packaged apps

I expect not. After all, it's all just Windows development. We're actively trying to erase those lines between those development experiences :-)

I'm glad this all seems to be doable, but I don't understand how I can accomplish it, and it looks like way too much work to do.

Which part(s) seem too-much-work?

are there any plans to add VS tooling for all of this to make it smoother?

Are you referring to the blog post, this Dynamic Dependencies feature or something else? Just want to make sure I understand the question

@DrusTheAxe I was referring to the blog post.

? a) I don't see anything in these specs about how these can be tooled so that they are easy for developers to accomplish

Agreed, it's not just a matter of it can work, it should also be easy to accomplish. Tooling's been an active area of discussion and investigation. What sort of tooling would you desire? Is something akin to VS' current new-UWP-project what you have in mind? GUI property pages etc to add/edit? Is VS your environment of interest? VSCode? Other?

Developers shouldn't have to write code in their main method. Maybe this is fine for frameworks where the app author owns the main method. But in WPF and WinUI, the main method is generated by tooling.

I'm glad this all seems to be doable, but I don't understand how I can accomplish it, and it looks like way too much work to do.

Which part(s) seem too-much-work?

The whole end-to-end, I don't understand what steps I need to go through in order for this to work. It would be helpful to see a doc that outlines how a customer will be successful.
Also, how does this play into the concept of .NET Core SelfContained apps? The promise there is that the app carries all of it's dependencies with it and the app author has full control. This is currently the recommended approach from the .NET team. If an app author sets SelfContained to true in their project file, will that ensure the framework package is never updated? How do we educate developers in this scenario that some of their dependencies are bundled with the app, but then some are not?

We're discussing tooling and integration options to make this as friction-free as possible. The end-of-end story spans multiple parts - Dynamic Dependencies, the #156 Deployment Information API and some tooling and additional APIs to further shrinkwrap the picture.
The generated-main issue is a good one. I'll follow up on that.
Some folks are looking specifically at the .NETCore space. I've heard SelfContained come up but I don't know the latest thinking (yet :P). StayTuned.

@marb2000 can help with SelfContained, he has done a lot of work in this space already.

The generated-main issue is a good one. I'll follow up on that.

XAML ask => Proposal: Extensibility hooks in generated main #3408
WPF ask => Proposal: Extensibility hooks in generated main #3632

@DrusTheAxe #158 seems to have been lost in the transition from master to main. It shows as merged on GitHub, but is not present in the main branch (and the master branch it was merged into has been deleted). Since the source branch has since been deleted also, it is now impossible to use the MSIX DD code, as it now exists only in the form of diffs on the PR page; it cannot be checked out now. Could someone please resuscitate this code and get it into main? Thanks!

@wjk Yes something went weird with the branching. I've killed the PR. Rebase'ing against main shows some merge conflicts :-(
Let me get the branch back up and verified it's current.

OK I made a new branch user/drustheaxe/dyndep that's rebased against the latest in main. All code preserved and builds and tests pass so yay.

Feedback from recent design reviews centered on the 'helper' main package and asks to do something simpler / more streamlined for developers. So we made a change to plan - Project Reunion will provide the 'helper' main package for folks using Dynamic Dependencies. Thus is born the 'Dynamic Dependencies Lifetime Manager'.
The branch has the core implementation. I'm working on an update to the spec about this, plus some remaining work e.g. integrate the DDLM into the CI/Build pipeline. Coming soon

Mission accomplished, just forgot to resolve the issue


Add tutorials

I have added the tutorials on the calculation of anharmonic IFCs of BaTiO3 ans Si, SCPH-based structural optimization of BaTiO3, and QHA calculation of wurtzite ZnO.

Thank you!


Poisonfix

Fix for poison bottles when u dclick on one.
-FIXED: (Poison`s potions)
	-Now it dosnt raise magic resistance if poison comes from a potion.
	-Potion is consumed when dclick and the Empty bottle retrieved into backpack.
	-Eating animation added.
-Known Issues:
	-Poison effect is the same always no matter poison strenght. And duration is short.
	-There still no cooldown for poison bottles (complex to implement and not really needed I think)

This fix is done due this report of jhobean

On a clean build, u need to activate this option on sphere.ini or poison will not take effect.

In OSI jhobean tested u get poisoned if u dclick on poison bottle.

I tested it and work well!  Good job

When merging this fix, we should merge this revert on X pack too
https://github.com/Sphereserver/Scripts-X/pull/35

I did a mistake. fixing it, dont merge

I tested it and work well! Good job

Ty for testing :D I fixed one more mistake. Works fine for me now. Just left the Cooldown issue. What does OSI? Do they put cooldown to poison potions as well?

The code you added in CClientUse.cpp can be replace with.
m_pChar->Use_Drink(pItem);
and also you can remove
m_pChar->OnSpellEffect(SPELL_Poison, m_pChar, pItem->m_itSpell.m_spelllevel, nullptr);
As it's already include in m_pChar->UseDrink

Even better, the case
if ( RES_GET_INDEX(pItem->m_itPotion.m_Type) == SPELL_Poison )
can be removed as everything related to dclicking a potion (Except explosion potion) is handled by useDrink


Add tag to the resources created for amplify to more easily indentify.

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting questions.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
NEW_APP
AWS Region
us-east-2
Amplify Hosting feature
Not Applicable
Is your feature request related to a problem? Please describe:
Having issue figure out what S3 Bucket correspond with an specific amplify app
Describe how you'd like this feature to work
I want to go to a bucket on s3, or cloud form, and filter by tag to find the corresponding resource to an specific amplify app.

This is now available: https://docs.amplify.aws/react/build-a-backend/add-aws-services/tagging-resources/


Handle "snapshot rejected due to size" error

Encountered this failure in a test environment (with older rpki-client version) where the snapshot is 245MB due to a keyroll:
rpki-client: ta/ta-example-org: loaded from network
rpki-client: https://rrdp.example.org/notification.xml: pulling from network
rpki-client: https://rrdp.example.org/notification.xml: downloading snapshot
rpki-client: parse failed - content too big
rpki-client: https://rrdp.example.org/notification.xml: parse error at line 109209: parsing aborted
rpki-client: https://rrdp.example.org/notification.xml: load from network failed, fallback to rsync
rpki-client: rsync/rpki.example.org/repository: pulling from rsync://rpki.example.org/repository

Encountered on 7.5.

This error is due to a FILE on the manifest being too big. Will just try to catch the parse error line and the content too big line separately.


AttributeError: type object 'Tasks' has no attribute 'face_quality_assessment'？

The Tasks have not  face_quality_assessment,why?
AttributeError: type object 'Tasks' has no attribute 'face_quality_assessment'

which model are you tying to used? from the error, it looks like the model is still in the process of integrating into modelscope, and is not ready for usage yet.

which model are you tying to use? from the error, it looks like the model is still in the process of integrating into modelscope, and is not ready for usage yet.

OK,thanks!


Out-of-proc host (Ready for review)

Setting this up so you can see my changes in isolation from the .net core stuff

General context that might help to digest how this works:
ScriptHost starts:

Creates and starts GrpcServer
Creates top level objects (Dispatcher, DescriptorProvider, etc)

Function Indexed:

WorkerFunctionDescriptorProvider tests if the language is supported - if so:
Creates a buffer for invocations for this function (producer consumer queue)
Registers the function metadata & buffer with the FunctionDispatcher (misnamed, the dispatcher basically manages channel state)
Creates a WorkerLanguageInvoker, which posts invocations to the buffer

Registering a function with the Dispatcher:

creates a LanguageWorkerChannel if one does not already exist for that language / worker config
adds the registration to a ReplaySubject (so that we can replay function registrations to new channels)

LanguageWorkerChannel:

intended to have the lifetime of the worker process (if you need a new one, create a new channel)
starts worker process when constructed
listens to eventManager for RpcEvents (StartStream => WorkerInit -> if success, worker ready)
when WorkerReady, subscribe to:

function registrations (load all the functions registered with this worker)
function load responses

on a load response, begin consuming messages from that function's input queue

function invocation responses

On Channel Error:

stop consuming invocation messages (unlink action blocks)
notify the dispatcher of worker error via WorkerErrorEvent
dispatcher attempts to create new channel if within retry limits

Keep the review simple for now. This work is currently targeting the core branch, which will go through a review soon. Matt will squash this so reviewing the work there will still be pretty straight forward. In other words, the bar is a bit lower and we'll have an opportunity to go through design review cycles before this work makes its way to dev.


[SPARK-43952][FOLLOWUP] Don't set JobGroup in Spark Connect after all

What changes were proposed in this pull request?
After further discussion, setting JobGroup in Spark Connect for the scope of the query is not necessary.
Use cases that want to identify Spark Connect queries (e.g. SparkListener events from https://github.com/apache/spark/pull/41443) should use their jobTag for that instead.
Why are the changes needed?
Discussion around where Jobgroup should be used. Since there may be only one Jobgroup at a time, using it for Spark Connect queries is prone to being reset by another unrelated user. Better to use the new "jobTags".
Does this PR introduce any user-facing change?
No.
How was this patch tested?
CI

Merged to master.


Make 24/12 hour clock switch sticky

Could the switch from a 12 to a 24 hour clock please be made sticky?
This would probably require a cookie. This would work similar as the language settings cookie that is given as an example of the kind of cookie that doesn't require permission in this guide on the gdpr.

hartman/zonestamp#21


[CNDIT-232] Deduplication algorithm to check HL7 duplicate

Notes
This PR is the first baby step for the deduplication algorithm we planned to implement in the Data Ingestion pipeline. With this change, after validating the incoming HL7 document, 32 byte hash for the document is generated and validated against the database for any existing duplicate records. If none present, then validation check passes and the document is converted to FHIR. If the validation fails, then an exception is thrown and the record is moved to the elr_validated-dlt kafka topic.
JIRA

https://cdc-nbs.atlassian.net/browse/CNDIT-232

Testing
I was able to test the changes in the local database and hit the endpoint using the test payload. Successful payloads were inserted into raw, validated and fhir tables. Unsuccessful ones are inserted into raw and then moved to dlt topic. Also, captured the exceptions to make sure the incorrect payload fails.

Looks good to me


HELP: BUILD and POS xml with Flutter Example

Hi,
Thanks for xml plugin. I made a small app for example. Please update https://pub.dartlang.org/packages/xml
I mange to build xml in Flutter and be able to post and get the response. Here is the code:
DEPENDENCIES:
// Add pubspec.yaml:   xml: "^3.2.1"
import 'package:xml/xml.dart' as xml;
import 'dart:io';

BUILD XML:
// TODO: BUILD XML FILE
Future<HttpClientResponse> _sendOTP() async {
  var builder = new xml.XmlBuilder();
  builder.processing('xml', 'version="1.0" encoding="iso-8859-9"');
  builder.element('MainmsgBody', nest: () {
    builder.element('UserName', nest: “xxxxxxxx”);
    builder.element('PassWord', nest: “yyyyyyyy”);
    builder.element('Action', nest: 5);
    builder.element('Mesgbody', nest: “I am Fluttering with Dart”);
    builder.element('Numbers', nest: 5);
  });
  var bookshelfXml = builder.build();
  String _uriMsj = bookshelfXml.toString();
  print("_uriMsj: $_uriMsj");

  String _uri = "https://*******.******.com/http****”;
  var _responseOtp = postOTP(_uri, _uriMsj);
  print("_responseOtp: $_responseOtp");
}

POST XML:
 // TODO: POST XML FILE
Future<String> postOTP(String _uri, String _message) async {
  HttpClient client = new HttpClient();
  HttpClientRequest request = await client.postUrl(Uri.parse(_uri));
  request.write(_message);
  HttpClientResponse response = await request.close();
  StringBuffer _buffer = new StringBuffer();
  await for(String a in await response.transform(utf8.decoder)) {
    _buffer.write(a);
  }
  print("_buffer.toString: ${_buffer.toString()}");
  return _buffer.toString();
}

Thank you for your feedback. What exactly would you like me to update?

The overall score shows 48 and their suggestions is to maintain the example. If you can make a small example read write xml via http (https) I think overall score will be much higher than current one. I would like to help to keep such a perfect plugin score to be on top. :)

Ahh, interesting. I didn't realize the score was so low. Not sure, if this is just about the missing example though? I'll see what I can do ...

Such a wonderful plugin and such a low score :( hope you can improve the score. Thanks

I've added an example, but the score didn't change. Looks to me like this is a bug on pub.dartlang.org. I've filed a bug against them: https://github.com/dart-lang/pub-dartlang-dart/issues/1659.

Thanks, renggli
They analysed this package (today) on Sep 27, 2018, and I guess they are working on suggestions. Now there is no suggestions for the plugin...

Thanks for the help, back at a score of 98:


Wind pruf

Changes:

cmod_windpower

Add individual wind pruf loss percents as inputs (ie avail_bop_loss, avail_grid_loss...)

Add grouped wind pruf loss percents as outputs (ie avail_losses) for loss diagram

Remove wind_farm_losses_percent

get_fixed_losses calculates a lossMultiplier from all loss percents EXCEPT wake_int_loss_percent, which can be either provided as an input given Constant Wake Model, or is calculated by wake modeling

individual derates from loss percents should be multiplied: change calculation of lossMultiplier

lossMultiplier replaces windTurbine's lossesRatio

p50p90 calcs

common.cpp

p50p90 vtab and function

lib_windwakemodel

remove lossesRatio and lossesAbsolute

cmod_windpower_test

due to change in how lossMultiplier is calculated, test values change a little bit

NOT to be merged:
CMakeLists

ones in wind_pruf branch assume submodule structure

All windpower unit tests and integration tests passing


Allow for multiple env-files

Closes #553
Keeps backwards compatibility with the compose_env_file parameter, but advises the user to use the new compose_env_files parameter instead. If both parameters are given, the compose_env_files will take presedence.
Added tests to verify behavior

Closing in favor of PR #616


Preview in Swift is broken

[REQUIRED] Step 1: Describe your environment

Xcode version: 12.4
Firebase SDK version: 7.10
Installation method: `CocoaPods
Firebase Component: importing Firebase, so Core?

[REQUIRED] Step 2: Describe the problem
Steps to reproduce:
What happened? How can we make the problem occur?
Once I imported Firebase, previews stopped working. The error is in 'FirebaseCoreDiagnostics', a bunch of 'Umbrella header for module 'GoogleDataTransport' does not include header 'GDTCOR[Registrar/StorageEventSelector/etc].h'. Lastly, it says parse issue: 'could not build module GoogleDataTransport'.
Relevant Code:
All previews fail, doesn't matter if it's my own code or a hello world.

I'm not able to reproduce. It's possible something about your installation has been corrupted.  I recommend pod deintegrate and pod install and clearing DerivedData.
If that doesn't help, please send a reproducible example.

@maxiedaniels Had a similar issue in my project that was solved by this: https://stackoverflow.com/a/58973469


[C++ GMS]，why not use GPU ORB to detect and compute keypoints？

I am confused about that I got less keypoints when I used GPU ORB to detect keypoints. opencv3.2.0

I don't know the reason, but I am sure that the GPU implementation of ORB is not as good as the CPU version in OpenCV library.

Thanks，I also found GPU_ORB crashed using Multithread.


Load config from well-known locations + add init command for initializing config

Description
This adds the start of an init command for configuring Homestar from the CLI. When run interactively, it currently provides a wizard for configuring the keys used by homestar, however it can also be run non-interactively using values configured through CLI flags.
It also includes allowances for outputting a generated configuration over stdout, and the start of some patterns for handling some common CLI knobs, like --no-input, --quiet, and --force, though these are only likely to see more use as we expose more configuration options to this interactive wizard.
There's still a lot of polish that can be done around how we handle error reporting and interrupts, like control+c, during interactive usage, but this is a start that should make it a lot easier to begin expanding the configuration options we expose to the user.
Link to issue
Please add a link to any relevant issues/tickets.
Screenshots/Screencaps

I pushed up some small tweaks, including converting InquireError to a miette report, so that we're able to cleanup the error reporting on a SIGINT received during prompting. Here's how that looks now:

Exceptional errors still currently panic, which I think is possibly the right call for now, until we do the work of translating those into a miette error that directs users to file an issue in the repo or something.

@QuinnWilton could we add some integration/CLI (no runtime needed) tests to have tests around the functionality here?

Added some comments thus far.

[ ]  Q: Shouldn't we also have the option to generate a PEM/DER file for users (not just provide your own) as another option? Essentially, replace the OpenSSL genkey we've/users have been doing manually? I thought this was one goal of the work?

❤ the experience btw.

I don't see any APIs exposed by the libp2p-identity crate for encoding keys as PEM/DER files. Are you aware of anything that I may have missed? Or were you imagining that we'd pull in another crypto crate / shell out to OpenSSL for that?
Either way, I just pushed up fixes for all of your other comments.

@zeeshanlakhani I just pushed up PEM generation for ed25519, improved PEM parsing for ed25519, and the tests you requested! Headed to dinner now, but merge conflicts are fixed and I'll check CI in the morning 😊

@QuinnWilton Code is looking pretty good, but there was a new setting added in main that's missing here after rebase. Once that's updated, I'll do a run through and check the DX experience.

Hey @QuinnWilton! Trying out the new PEM key file features. They work great, and I love them. ❤
I have a couple of minor DX requests:

Could we update the help text to indicate that the --key-file flag will generate a key if an existing key does not exist at the path?
When generating a key file with the --key-file flag and selecting the Secp256k1 option, an unsupported error is thrown (as expected) but an empty key file is created. Could we clean up and remove the key file in this error case?

@QuinnWilton last minor thing:

Could we generate the pem in the config directory by default if no file is given to key-file and override the default path if run again?


TAVILY replacment?

Hi,
Seems tavily is pretty good until we found its lowest price plan is $100/m, this is much more expensive than serp.
Is it possible to replace tavily with replacment? And how?
Thanks!

Brave has also an api for llm-s
https://brave.com/search/api/


[MRESOLVER-382] allow setting outgoing interface

fixes MRESOLVER-382

Lgtm, but a nitpick: is Optional really needed?

Of course not. I just find it easier to read and write, but YMMV and I can change it to sth like:
if (bindAddress == null) {
  return null;
}

return this.resolveAddress(bindAddress);


Bump :editor evil

emacs-evil/evil-collection@b45ec5b → emacs-evil/evil-collection@b6025cf
emacs-evil/evil@7eace67 -> emacs-evil/evil@d998a81
The register system has been rejigged in the last week, and some
packages in the Evil ecosystem are already making use of the new vars.
emacs-evil/evil@229ebb4
mamapanda/evil-owl#10

I'm not sure if I got the format of the commit message right. Apologies!
I did try to run doom/commit-bumps but it looks like that function needs to be written?
;;;###autoload
(defun doom/commit-bumps ()
  (interactive))

I'm guessing it won't be trivial to implement, but will take a quick stab at it.

There's a subtle difference between Bump package-name and Bump :editor evil. The latter implies you've bumped the whole module and any packages that haven't been bumped either a) have no updates or b) are blocked by something else. The former explicitly means "I'm only bumping this one package."

@hlissner that makes sense. I thought my use of :editor evil might be a little… excessive. I've bumped evil-collection as requested, and force pushed a new commit with an update commit message.
I'm already subscribed to #4273, so will keep an eye on things there, and help out wherever I can.
Thanks!

Looks good to me! Thanks again!


Introducing new configurations on sentry

I ran author rewrite script (https://help.github.com/articles/changing-author-info/) so thats why it is showing so many changes. I had two users on my computer and it was not showing my actual account on github. Only changes are in README.md and GrailsLog4jSentryAppender.groovy. Let me know if that is ok.
https://github.com/agorapulse/grails-raven/compare/master...anujku:develop?expand=1

Introducing optional subsystems as a filter on sentry dashboard similar to what you see onYouTrack.Let me know if something like this will make sense ?
Default subsystem will be MISC, exceptions with package name starting with org. will be under LIBRARY.

Introducing optional priority filter based on predefined priority map containing level and list of exceptions with that level of priority. Similarly library exceptions are MID level priority.

Introducing optional classname parameter that will add the class name for the exception on sentry.

Removing comma separated values for logger, tags, levels and using List or Map which is a much better way to do the same in groovy.

I think it will really improve experience while browsing errors on sentry.The current logic though can always be be improved.(?)

Coverage decreased (-0.95%) to 4.41% when pulling 76c13a39b167350ea14f66ad7f49cefa5eccf031 on anujku:master into 1d5775755ca1b530f020734d0357aaa8b7733387 on agorapulse:master.

Coverage decreased (-0.95%) to 4.41% when pulling 2faac97ea43c66d160ba584fe3a6d9667bf4794d on anujku:master into 1d5775755ca1b530f020734d0357aaa8b7733387 on agorapulse:master.

More things will be added.

Coverage decreased (-1.74%) to 3.61% when pulling 914d4db50b58a3c1609d6d0e56c9fdbecd661f33 on anujku:master into 1d5775755ca1b530f020734d0357aaa8b7733387 on agorapulse:master.

Coverage decreased (-1.74%) to 3.61% when pulling 914d4db50b58a3c1609d6d0e56c9fdbecd661f33 on anujku:master into 1d5775755ca1b530f020734d0357aaa8b7733387 on agorapulse:master.

I ran author-rewrite script (https://help.github.com/articles/changing-author-info/)
as I was using two accounts and it was not showing my actual account. Sorry for this.

Coverage decreased (-1.91%) to 3.45% when pulling<PHONE_NUMBER>ba040a9ee9283bc7489e02057d0c31 on anujku:master into 1d5775755ca1b530f020734d0357aaa8b7733387 on agorapulse:master.

Coverage decreased (-1.91%) to 3.45% when pulling<PHONE_NUMBER>ba040a9ee9283bc7489e02057d0c31 on anujku:master into 1d5775755ca1b530f020734d0357aaa8b7733387 on agorapulse:master.

I've released <IP_ADDRESS> version.
I'll give it a try today.
Thanks!
2015-03-18 23:20 GMT+01:00 Coveralls<EMAIL_ADDRESS>
[image: Coverage Status] https://coveralls.io/builds/2144724
Coverage decreased (-1.91%) to 3.45% when pulling 1343456
https://github.com/agorapulse/grails-raven/commit/1343456157ba040a9ee9283bc7489e02057d0c31
on anujku:master into 1d57757
https://github.com/agorapulse/grails-raven/commit/1d5775755ca1b530f020734d0357aaa8b7733387
on agorapulse:master.
—
Reply to this email directly or view it on GitHub
https://github.com/agorapulse/grails-raven/pull/12#issuecomment-83206409
.

Thank you very much !!


Process poll_answer update event

[ ] All tests pass
[ ] I have run npm run doc

Description

References

Duplicate of #777


GenderMag Recorder's Assistant crashing

Extension crashes all the time
-when we click on save and continue button after filling the action form (if Abby did the right thing (the one you just demonstrated), will she know that she did the right thing and is making progress toward her goal?)
Blank screen no option to exit

updated the action.html file under template folder
issue resolved and verified
commit ce1e40990304c9c1603b356d4afe3bb5a17d07b5


Monorepo setup: unable to pin Typescript version relative to working directory

Version
4.1.2
Reproduction link
https://github.com/AlexandreBonaventure/ts-monorepo-repro
Environment info
-

Steps to reproduce
I know this not strictly a vue-cli bug but in a monorepo setup (using yarn workspaces), I am unable to pin a specific version of typescript because there is seemingly no way to provide a configuration to explicitly do so. Basically, here we have to rely on node module resolution and package manager which is not deterministic.
Scenario 1: bare workspace setup
|_ node_modules
  |_ @vue
  |_ ts-loader
  |_<EMAIL_ADDRESS><------ this typescript will always be used when compiling repro1 AND repro2
|_ apps
  |_ repro1 (requires<EMAIL_ADDRESS>  |_ repro2 (requires<EMAIL_ADDRESS>    |_<EMAIL_ADDRESS><-- this one should be used but because of @vue packages being hoisted up in the root, it won't

Scenario 2: using nohoist option
|_ node_modules
|_ apps
  |_ repro1 (requires<EMAIL_ADDRESS>  |_ repro2 (requires<EMAIL_ADDRESS>    |_ node_modules
        |_ @vue
           |_cli-plugin-typescript
              |_ node_modules
                |_<EMAIL_ADDRESS><------ this typescript will be used by ts-loader is coming from devDepedencies of cli-plugin-typescript
                |_ ts-loader
       |_<EMAIL_ADDRESS>
What is expected?
Ability to have control on using a typescript version specifically for each project
What is actually happening?
Difficult to do so

possible solutions could be :

plugin option to provide typescript binaries by ourselves
remove typescript devDepedencies in cli-plugin-typescript so we can use the yarn nohoist option

I also have this problem when I try to use monorepo.
Temporary solutions:
// vue.config.js
chainWebpack: config => {
  config
    .plugin('fork-ts-checker')
    .tap(args => {
      args[0].typescript = require.resolve('typescript')

      return args
    })
  config.module
    .rule('ts')
    .use('ts-loader')
    .tap((args) => {
      args.instance = require('typescript')
      return args
    })
  config.module
    .rule('tsx')
    .use('ts-loader')
    .tap((args) => {
      args.instance = require('typescript')
      return args
    })
}

Ran into a similar issue. Since the typescript plugins resolve both typescript and the tsconfig.json relative from where it was installed (which node_modules folder it ended up in). Now my (intentionally) in base tsconfig.json in the root of my monorepo is used. However, what I'd want is that the tsconfig.json from the package where the CLI command was invoked is used.
It would already help if I could provide the path to the tsconfig.json that I'd like it to use manually. Because it is not even guaranteed that the file will be called tsconfig.json.


Server UI

Offer an official UI for monitoring and debugging purpose. Perhaps as an extension, or directly integrated in the repo depending on the dependency graph.
Possible features:

Console
Memory graph
Process usage, mspt, per thread usage
Entity tab, possibility to query entities using the target selector syntax. Clicking on one should show the "entity editor" page where every part of the entity can be modified
Tag editor, ability to view in real time the tags applied to an entity, block, instance & chunk.
Packet listening (debugging purpose)
Provide an API for other extensions to create their own tab
Include async-profiler
Entity pathfinding debugger (show target, path, goal, etc) (maybe part of an entity viewer/editor)
Event graph viewer (to see them triggering in realtime perhaps)
Some kind of block handler info? (time stats? count?)
File browser/basic text editor (restricted to server working directory)
"Item editor" (or part of entity editor)

i think this should be done with some kind of "official extension." but if this is offered as a official extension with access to sensitive information like console and files then great care need to be taken to make it secure.

also idk the best way to implement this but it would be cool if it worked with multiple servers and supported adding servers dynamically.
possible model
web client <-> web panel <-> minestom servers with extension

I've started working on what will aim to be this just as a bit of fun to see if I can get anywhere, but it's likely I'll stall after a bit.
I have no idea how I'm going to make the UI element because I want it to work with both a single server that will run the panel, and also as part of a cluster where the server can register itself with a master node.
If anyone has any suggestions regarding anything feel free to ping me on discord (Zak).


Incorrect examples for viewing environment variables

The PowerShell examples (and mabye CLI examples) are incorrect.

Once both containers' state is Terminated (use Get-AzContainerInstanceLog to check state), pull their logs with the Get-AzContainerInstanceLog command.

Get-AzContainerInstanceLog requires three parameters but the examples only show two.
However, Get-AzContainerInstanceLog is probably the wrong command. I believe that seeing the state and environment variables requires the Get-AzContainerGroup command.

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

ID: 8cd0d0a1-65c0-ec3f-ab56-ef68f9f819a0
Version Independent ID: 9a0d1414-0cf7-e17d-ca40-5a9cc0ea369e
Content: Set environment variables in container instance - Azure Container Instances
Content Source: articles/container-instances/container-instances-environment-variables.md
Service: container-instances
GitHub Login: @macolso
Microsoft Alias: macolso

Also, New-AzContainerGroup no longer supports the -EnvironmentVariable parameter. It seems this is now under New-AzContainerInstanceObject, but I'm having trouble with the environment variables. Really would like an up-to-date set of examples on how to create and view container environment variables.

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

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. Though the scope of our feedback channel here on GitHub covers specific documentation fixes, we can help redirect you to the right support channel to get an answer to your question: [reference to alternative product/service or community endpoint]. Because this issue does not relate to documentation, we are closing this issue. #please-close


Multiple FlowCharts On a Dashboard

When creating and saving multiple FlowCharts on a Dashboard, sometimes on the first time of saving, both Flowcharts show the same content.  Valid in Version 0.3.0 and 0.4.0
To reproduce:

Add a panel to a dashboard, configure it to be a Flowchart, open the draw io editor clean everything out, and add a component, give it some text like "Hello" and save.  So far so good.
Add a second panel to the same dashboard, configure it to be a Flowchart, open the draw io editor clean everything out, and add a component, give it some text like "World" and save.
Sometimes when saving the second instance for the first time, both instances of the FlowCharting component will have one component and both say "World".  So it looks like your serializer back to JSON has problems sometimes when saving back to find the proper instance of the FlowCharting component.  So what I do to work around this is to copy the json XML config for the first instance to my clipboard or external editor, then create the second one.  If the problem happens, then I paste the Json xml back into the dashboard json for the first instance and things work fine.  After that, editing either one works fine for ever more.  Interesting bug.  :) Hope you fix this one.  :)

yes Interesting bug. I'll try it ;)

Fixed in 0.5.0 SNAPSHOT


[FEATURE] glowing

Maybe you can add team glowing options
When player toggle
It will let same team player glowing

What command would be used to activate the glowing effect?
Would activating the glowing effect only enable it for them or the whole team?


builds started failing on Hydra's new hash-named x86 machines

A couple days ago, i686 nixos tests started failing consistently, e.g. https://hydra.nixos.org/build/95616203  I can't reproduce the problem locally, and apparently there's something different about those hash-named build machines (which might have been added or at least changed around that time, too).
i686 tests aren't too important nowadays, I suppose, but we could at least do something simple, e.g. remove the i686 platform tag from these machines.

Eh, another problem, likely related and much worse – those machines quite often end an x86_64-linux build with:
checking for references to /build/ in /nix/store/gwawakcjhr48xgf04dhc16fkhw4xdnng-automake-1.15...
invalid ownership on file '/nix/store/gwawakcjhr48xgf04dhc16fkhw4xdnng-automake-1.15/bin/aclocal-1.15'

Again, I could never reproduce these.
/cc @NixOS/rfc-steering-committee  I don't really have an idea about whom to ping, but some of them certainly should know about those new Hydra machines.

Apparently this currently blocks larger rebuilds, even with multiple restart attempts, e.g. see this build.  /cc @FRidh who deals with staging-next a lot (to know I've made a thread for this).

@grahamc have you seen this?

No, I haven't seen this.

These hash-named x86 machines have Intel Scalable Gold 5120 cpus, and are transient -- so it is a bit lucky that this exact build's machine still exists.
However, unlucky because I can't log in to it:
$ ssh<EMAIL_ADDRESS>[SOS Session Ready. Use ~? for help.]
[Note: You may need to press RETURN or Ctrl+L to get a prompt.]

nixos login: grahamc
^C

[grahamc@Petunia:~]$ ssh<EMAIL_ADDRESS>^C

Evidently something very strange happened to it. I've since destroyed that server.
I picked up another one of the machines (b5b77143) which is alive, and boy did something stick out to me!
 :)
These machines are spot and transient, so they never fully "install". In the x86 case I accidentally left the / mount as a unionfs of the netboot image and a mount point on disk. I've killed these problematic x86 machines until I can fix this by moving the netboot'd / on to the actual disk to avoid unionfs problems.

Also, I'm sorry for breaking it, and not noticing sooner. Thank you @vcunat for tracking it down, and thank you @FRidh for the ping!

@grahamc: thanks for the quick reaction.  I should've tried to mention you directly; now I'll know who knows best about these builders, too.
The aarch64-linux ones also suffer from this, apparently: this build (step 6).

Yes, indeed. I have terminated those now as well. Same problem with unionfs. I'm traveling this week, which makes it a bit trickier to fix and re-launch these instances, but I'll give it a go!
Thank you for the heads up.

I have updated the filesystem layout, and / is now a zfs filesystem of its own, with no layering. I'll be re-launching the aarch64 and x86 builders with this new mechanism.

I think the issue has been resolved so closing.


Add more functionality to conv transpose shape inference

Signed-off-by: Philip Lassen<EMAIL_ADDRESS>

Jenkins Linux amd64 Build #8509 [push] Add more functionality t... started at 19:02

Jenkins Linux ppc64le Build #7576 [push] Add more functionality t... started at 20:04

Jenkins Linux amd64 Build #8509 [push] Add more functionality t... passed after 1 hr 16 min

Jenkins Linux s390x Build #8525 [push] Add more functionality t... passed after 1 hr 30 min

Jenkins Linux ppc64le Build #7576 [push] Add more functionality t... passed after 1 hr 42 min


prepare release 0.33.0

aligns ruby versions for travis, rubocop and the gem itself

Coverage remained the same at 99.322% when pulling 8c5178c54b1e948916c4c53f7624b6a247648697 on LeFnord:master into 4573a827772225df875f499ab39257822af5817e on ruby-grape:master.


fix(search): remove useless observed at from temporal entity evolution response closes 236

In the PR description, reference the issue with a # instead of closes  (and you can also link the issue to the PR if you want automatic closing when the PR is merged)


Broken links...

Hi & thank you for this interesting piece of software
some links in README are broken (first iotJumpWay link, database start input, all the 3 Install iotJumpWay links,  Server/Media/Images/var/www, /var/www/classes/AIcore/confs.json ...)
Even the registration link under https://www.iotjumpway.com/developers/getting-started is broken ...
Furthermore the command "sudo pip install JumpWayMQTT" do not work anymore (arises a dependency error), we will have to use "pip3 install" instead ...
Furthermore you speak about your php encryption function but show instead the decrypt function in a code sample. You do not say how to call the encrypt function but I guess any base64 encoder will do that :)
would you mind repairing this all for your community (guess I cannot)?
KR

Thanks this project is very outdated now and won't be updated for a while. You could try https://github.com/LeukemiaAiResearch/HIAS and the other repositories in our Leukemia AI Research repository. All those projects are up to date.

Thanks to you Adam.
Actually I am very interested in uses of your NLU - not really here.
Any way to bypass "server" and use NLU alone without reverse engineering your nice software?
Thank you for any hint...

I am going to be adding the new TF2 version to this repository soon. These repositories are going to be archived. Thanks.

I am going to be adding the new TF2 of the NLU to this Github organization and the latest version of the server will be added. For a complete up to date project that has recently been checked you can check out the following project https://github.com/AMLResearchProject/ALL-Detection-System-2019 or use HIAS as I mentioned to you. If you want to use the NLU entirely on it's own just remove the iotJumpWay code, there is not much of it.


Add --chance flag for inferno start command

Closes https://github.com/oldschoolgg/oldschoolbot/issues/3222
Description:
Added a --chance flag to +inferno start command. This just shows the user their Boosts, pre-Zuk death chance and Zuk death chance.
Changes:
Added a check for --chance flag and return message early (before supply usage).
Moved the construction of parts of the return message to earlier in the file to accommodate.
Other checks:
Checked that the Inferno command with --chance flag doesn't take any items.
Checked that the information returned is the same between --chance flag and not.
Checked that inferno runs start as expected without the flag, removing and telling the user of consumables taken.

[x] I have tested all my changes thoroughly.

I think we should also mention these in the base command so that people know it exists.

I think we should also mention these in the base command so that people know it exists.

Added a message into the base command to alert the user of the --chance flag.

Bump


UnoCSS does not add  after:content-[''] class automatically when I want to use pseudo classes like after and before.

Clear and concise description of the problem
I used both Tailwind and WİndiCSS.I started to learn UnoCSS before one week ago.I noticed that UnoCSS does not add ' after:content-['']' class(content:'') automatically when I use before or after pseudo classes.
If you can add this feature will be helpful.
Thanks in advance :)
Suggested solution
Add 'after:content-['']' if A user describes before or after pseudo classes.
Alternative
No response
Additional context
No response
Validations

[X] Read the Contributing Guidelines.
[X] Read the README.md of using the package.
[X] Already used the Interactive Docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Our behavior should already be aligned with tailwind, windi.
If so, can you send a link to the online playground?
Otherwise it sounds like an own requirement, you can use shortcuts

Our behavior should already be aligned with tailwind, windi. If not, can you send a link to the online playground?
Otherwise it sounds like an own requirement, you can use shortcuts

TailwindCSS Playground
UnoCSS Playground
Looks like content is indeed automatically set in TailwindCSS

From the devtools, `tailwind` adds `content` to each pseudo-element, but from the output, I don't think this is a wise choice.

Is it because of the generated CSS bundle size? Using before and after pseudo-elements is already a rare case, and gzip will compress them to virtually nothing, as they are all the same. I truly don't believe bundle size should be a concern in this situation. However, if there is another reason, I would be open to understanding it.

I personally don't like too much style overrride, and increase the invalid css bundle size, thank you for a content-emptynothing bad. You can send a PR to get more people to review it.

@zyyv At least we should have a way to write arbitrary values, but currently this is not offered.
https://tailwindcss.com/docs/content#arbitrary-values
Or alternatively, I think aligning with WindiCSS's content-DEFAULT would be a good way
https://windicss.org/utilities/general/variants.html#pseudo-element-content

For a temp workaround, this is how you can define it in shortcuts
['content-DEFAULT', [{ content: `''` }], { layer: 'utilities' }]

At least we should have a way to write arbitrary values, but currently this is not offered.

We already supported it. https://unocss.dev/interactive/?s=content-['test']

For a temp workaround, this is how you can define it in shortcuts
['content-DEFAULT', [{ content: `''` }], { layer: 'utilities' }]

Use content-empty. https://unocss.dev/interactive/?s=content-empty

I think we should choose good ones to align. I personally think there is no need to align with tailwind in this issue. There is nothing wrong with writing an unitility content-empty. If you have other comments, PR welcome, let everyone review.

Emm yeah, you are right. I've no idea why it didn't work for me, guess it's some kind of HMR issue. After I restart the dev server again it works. Thanks!


Reduce gradle log level

Purpose
Reduce gradle log level

Codecov Report

Merging #15032 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master   #15032      +/-   ##
============================================
- Coverage     63.09%   63.08%   -0.01%
  Complexity      560      560
============================================
  Files          2336     2336
  Lines        103753   103753
  Branches      13830    13830
============================================
- Hits          65458    65451       -7
- Misses        33225    33231       +6
- Partials       5070     5071       +1

Impacted Files
Coverage Δ
Complexity Δ

...a/org/ballerinalang/bre/bvm/WorkerDataChannel.java
83.95% <0%> (-3.71%)
0% <0%> (ø)

...org/ballerinalang/bre/bvm/WaitCallbackHandler.java
82.88% <0%> (-1.81%)
0% <0%> (ø)

...ain/java/org/ballerinalang/net/websub/hub/Hub.java
69.53% <0%> (-1.57%)
0% <0%> (ø)

.../org/ballerinalang/database/sql/SQLDatasource.java
67.58% <0%> (+0.54%)
0% <0%> (ø)
:arrow_down:

...et/http/actions/httpclient/AbstractHTTPAction.java
79.14% <0%> (+0.85%)
0% <0%> (ø)
:arrow_down:

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 3e1adc8...4e1b93e. Read the comment docs.


[1.16.5] Doesn't work with disable broadcast

If you set broadcast-removal: false pokemons/items will never be removed.
Tested with 1 min repeat and entity youth 30

I cannot reproduce this behavior. Please could you provide further details or evidence?

So I've deleted config, in new changed all broadcasts to false (broadcast-removal and warning-broadcasts), removal time set to 1 min and still the same. It clears them only once 1 min after server restart, then for next 5 min nothing

@danorris709 I was just about to create a ticket for this. Noticed that my items were not being removed.
I keep only the pixelmon broadcast on so items and pixelmon get removed together without doubling the broadcast.
Tested by throwing an item and spawning a pokemon at the same time, then waiting for the removal broadcast.
Only the pokemon was removed, the item remained but was deleted later... seems like the timing might be off.
Both settings are the same. Here is my config: https://pastebin.com/j1manTcC
I am using Arclight, with multiverse. (This was tested in my spawn world which is not the overworld)
Worlds within spigot could be the issue?


Fix output of kubectl logs on README

@line 123 Old file is mentioned, correcting to latest naming convention "/etc/oci/cloud-provider.yaml"

?