Rasa X changes the order of the form slots mapping

Rasa version: 2.1.1
Rasa SDK version: 2.1.1
Rasa X version: 0.34.0
Python version: 3.7.9
Operating system: Ubuntu
Issue:
When starting Rasa X, the order of the slot mappings defined for forms in the domain file is automatically changed so that they are sorted alphabetically. Given that the order of the mapping changes the order in which the questions are asked by the bot within a form, this should not happen.
Command or request that led to error:
rasa x

Content of domain file (domain.yml) (if relevant):
Before starting Rasa X
forms:
  form_preferences:
    preferences_target_price:
    - intent: ...
    has_pet:
    - intent: ...
    ...

After starting Rasa X
forms:
  form_preferences:
    has_pet:
    - intent: ...
    preferences_target_price:
    - intent: ...
    ...

Thanks for the issue, @Ghostvv will get back to you about it soon!
You may find help in the docs and the forum, too 🤗

What version are you using? Can you try updating to the latest version? It should be fixed there: https://github.com/RasaHQ/rasa-x/issues/3900

@Ghostvv Thanks for your answer! I'm using 2.1.1, hadn't seen 2.1.2 and 2.1.3 were up (I'm monitoring the CHANGELOG file on master but I guess that's not enough for bug fixes)
Will try updating to 2.1.3

oh, sorry, the fix is in rasa OSS, but the new version of rasa x is not released yet

fixed in Rasa X 0.35

fixed in Rasa X 0.35

I think I am still experiencing this issue. Before running rasa x, there are no changes to the domain.yml. After running rasa x, the results are reordered to be in alphabetical order.
gazler> git diff domain.yml
gazler> rasa --version
Rasa Version     : 2.2.9
Rasa SDK Version : 2.2.0
Rasa X Version   : 0.35.0
Python Version   : 3.6.9
Operating System : Linux-4.15.0-132-generic-x86_64-with-Ubuntu-18.04-bionic
Python Path      : /home/gazler/.venv/bin/python3
gazler> rasa x &
gazler> git diff domain.yml

diff --git a/rasa-bot/domain.yml b/rasa-bot/domain.yml
index 78e577d..cea7066 100644
--- a/rasa-bot/domain.yml
+++ b/rasa-bot/domain.yml
@@ -101,12 +101,12 @@ forms:
     - type: from_text
     channel_confirm:
     - type: from_text
-    note:
+    mention:
     - type: from_text
     mention_confirm:
     - type: from_text
-    mention:
-    - type: from_text
     mention_list:
     - type: from_text
+    note:
+    - type: from_text
 e2e_actions: []

Just wanted to update to confirm I am still seeing this issue with the following (latest) versions:
Rasa Version     : 2.3.1
Rasa SDK Version : 2.3.1
Rasa X Version   : 0.36.0
Python Version   : 3.6.9

@Gazler Do you have an example domain which I could use to reproduce? 🙌🏻

@wochinge I created a default project and added the restaurant form, but re-ordered the form fields, so num_people appears before cuisine.
https://github.com/Gazler/rasa_x_form_order
If you run rasa x and then check git diff the form fields should have been reordered.

Hi, I am also getting this issue in 0.37.0. It is making the process very hard because whenever I start rasa x it just messes up the form structure. Here are the screenshots before and after starting rasa x.
Version details:
Rasa Version: 2.3.4
Rasa SDK Version: 2.4.0
Rasa X Version: 0.37.0
Python Version: 3.7.5
Operating System: Linux-5.8.0-48-generic-x86_64-with-debian-bullseye-sid

@Horizon733 Hello,I have same issue and could not solve.Is there any solution?

Hi, I have the same problem, the slots are ordered in alphabetical order in the domain file after running rasa x
Rasa Version: 2.6.2
Rasa SDK Version: 2.6.0
Rasa X Version: 0.40.0
Python Version: 3.8.11

@wochinge any updates here? It seems like a hotfix that turns off the auto-sort that Rasa X does, which overrides the desired user behavior would fix this. I'm not sure why Rasa X would need to sort them alphabetically anyway.
Without a fix, this effectively means using Rasa X breaks the use of forms in a bot entirely if you commit that "updated" domain file. Seems like this should be a high priority given forms are an essential part of a chatbot.
Using Rasa X 0.42.0

Thanks for bringing this up @pmbaumgartner ! @TyDunn I think somebody from Enable should take this one. Changing the order of form slots is bad as the bot asks for the slots in a different order (cc @DominikRos ). I think to make this clearer required_slots should actually be a list instead of a dictionary (@ancalita It's already a list in our slot mappings proposal, isn't it?)

It's already a list in our slot mappings proposal, isn't it?

Yup, that's correct, form required_slots is changed to a list in the new proposal.

I think when Rasa x rewrites the yaml file it reorganizes forms with alphabetical order instead of writing it as it is

Is this issue fixed?
While training domain.yml changes to alphabetical order:
forms:
incident_reporting_form:
required_slots:
country:
- type: from_text
description:
- type: from_text
emp_id:
- type: from_text
full_name:
- type: from_text
gender:
- type: from_text
incident_date:
- type: from_text
industry_sector:
- type: from_text
local:
- type: from_text
Rasa version details:
Rasa Version      :         2.8.2
Minimum Compatible Version: 2.8.0
Rasa SDK Version  :         2.8.1
Rasa X Version    :         0.39.3
Python Version    :         3.8.2
Operating System  :         macOS-11.5.2-x86_64-i386-64bit

@degiz As you have closed this issue, in which version of Rasa X has this been fixed? I checked the changelog (https://rasa.com/docs/rasa-x/changelog/rasa-x-changelog) and cannot see any mention of it being fixed.


JAMES-3754 Searching support IMAP savedate extension

TODO:

[x] Lucene implementation

Conflicts in the branch

Can we merge this?


Drop Elixir 1.2 support

Wait for release of Elixir 1.4

[x] Elixir 1.4 has been released
[ ] Update TODO in Benchee.Formatters.Console.units/1
[ ] Use keyword type declaration in Benchee.Formatter.Unit
[ ] Use String.trim/1 instead of String.strip/1
[ ] use describe blocks in tests a needed

Edited/added describe blocks

Will probably let the next release still be compatible with Elixir 1.2 and then drop support afterwards.

Support will be dropped in 0.8.0.


Support rails 5

This should solve #23

Please do fix the Rails 5 incompatibility.
This problem has been noted elsewhere:
http://stackoverflow.com/questions/39549962/rake-assetsprecompile-failed-when-push-rails5-app-to-heroku/39550697#39550697
On a project I'm on we've had to drop using heroku_rails_deflate because we're transitioning to Rails 5:
https://github.com/linuxfoundation/cii-best-practices-badge/pull/556

Curious, is there anything hold up this PR?


Add a "Sold out" flag

It is a standard marketing trick to mark certain listings as sold out. As of writing, there are several vendors that use this trick, e.g.

Hot Gadgets for You
Tom Woods Jewelry
Refur
TaiwanTea

Each of those vendors use the listing title to mark the item as sold out. My suggestion is to add a flag in the listing object instead so that these can be machine readable (for better searching, filtering and display).

@morebrownies ?

This will be handled by the inventory system improvements we are expanding to all listings after cryptocurrencies.


Cannot start kachery daemon

(kachery-env) typhoon:~% kachery-daemon-start --label franklab --owner<EMAIL_ADDRESS>--auth-group kachery-users
node: 15.14.0
+ export KACHERY_DAEMON_PORT=14747
+ KACHERY_DAEMON_PORT=14747
+ export KACHERY_DAEMON_HOST=typhoon
+ KACHERY_DAEMON_HOST=typhoon
+ npm install -g -y /home/kacheryuser/miniconda3/envs/kachery-env/lib/python3.8/site-packages/kachery_daemon/kachery-daemon-node-1.0.22.tgz
npm WARN deprecated<EMAIL_ADDRESS>this library is no longer supported
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future
npm WARN deprecated<EMAIL_ADDRESS>This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.

changed 224 packages, and audited 225 packages in 12s

9 packages are looking for funding
  run `npm fund` for details

4 high severity vulnerabilities

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.
+ exec kachery-daemon-node start --verbose 0 --auth-group kachery-users --kachery-hub-url https://kacheryhub.org --label franklab --owner<EMAIL_ADDRESS>node:internal/modules/cjs/loader:927
  throw err;
  ^

Error: Cannot find module 'external/real/kacheryStorage/KacheryStorageManager'
Require stack:
- /home/kacheryuser/miniconda3/envs/kachery-env/lib/node_modules/kachery-daemon-node/dist/services/ClientAuthService.js
- /home/kacheryuser/miniconda3/envs/kachery-env/lib/node_modules/kachery-daemon-node/dist/startDaemon.js
- /home/kacheryuser/miniconda3/envs/kachery-env/lib/node_modules/kachery-daemon-node/dist/cli.js
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:924:15)
    at Function.Module._load (node:internal/modules/cjs/loader:769:27)
    at Module.require (node:internal/modules/cjs/loader:996:19)
    at require (node:internal/modules/cjs/helpers:92:18)
    at Object.<anonymous> (/home/kacheryuser/miniconda3/envs/kachery-env/lib/node_modules/kachery-daemon-node/dist/services/ClientAuthService.js:25:33)
    at Module._compile (node:internal/modules/cjs/loader:1092:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1121:10)
    at Module.load (node:internal/modules/cjs/loader:972:32)
    at Function.Module._load (node:internal/modules/cjs/loader:813:14)
    at Module.require (node:internal/modules/cjs/loader:996:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/home/kacheryuser/miniconda3/envs/kachery-env/lib/node_modules/kachery-daemon-node/dist/services/ClientAuthService.js',
    '/home/kacheryuser/miniconda3/envs/kachery-env/lib/node_modules/kachery-daemon-node/dist/startDaemon.js',
    '/home/kacheryuser/miniconda3/envs/kachery-env/lib/node_modules/kachery-daemon-node/dist/cli.js'
  ]
}

Please try 1.0.23 on pypi

Seems like it's resolved. Also sortingview backend started up. Closing


VC allowed/trusted JSON-LD contexts

Need a mode that when set only allows certain JSON-LD contexts.
Need to be able to store some JSON-LD context documents locally (and disable downloads for these context documents).
CRUD to set these JSON-LD contexts.

Need controller APIs.
A component of vdri.

Is a shared component. Needs to be useable for Verifiable Credentials and LD Signatures (#1341) and also DIDs (#1326 ).

We will also need similar for JSON-LD did document parsing.

Need a mode that when set only allows certain JSON-LD contexts.

^ this is effectively implemented with a read-only document loader cache (already done I believe)


45 review contract

Updated queries to match common ones. Fixed tests to match.
With this all the SDKS look to be 98% similar.

Fixes #45

Few notes and whatnot but looks good.


idk what else we need that i can do, some1 check plz

in the edit section, i wouldn't just show the old things separately, because you're not rewriting it, but rather editing it. so just put the old texts into the textboxes.


Unable to match predicate of path and value for grpc request

Hi there, first of all thanks a lot for this plugin to bring grpc to mountebank. Hopefully you are still maintaining this project and could help to sort out an issue related to matching precicates for the grpc request. I have posted the original question on stackoverflow. Below is the question replicated for documenting it here in the project:
I am using the grpc plugin to create stubs for grpc requests. It works very well when matching the path only. However, I am facing issues to match both the path and the value. In particular, I am using the jsonpath to select the fields to match. Here is a sample o the request:
{
  "path": "/service.DataProvider/ReadData",
  "value": {
    "identifiers": [
      {
        "unique_id": "unset",
        "data_id": "point1",
        "system_id": "mock"
      }
    ],
    "start_time": {
      "seconds": "1650431509",
      "nanos": 0
    },
    "end_time": {
      "seconds": "1650431569",
      "nanos": 0
    }
  }
}

and the predicates:
        "predicates": [
        {
            "deepEquals": {
              "path": "/service.DataProvider/ReadData"
            }
          },
          {
            "jsonpath": {
              "selector": "$.identifiers[0].data_id"
            },
            "deepEquals": {
              "value": "point1"
            }
          },
          {
            "jsonpath": {
              "selector": "$.identifiers[0].system_id"
            },
            "deepEquals": {
              "value": "mock"
            }
          }
        ]

Any idea of what is wrong on the predicates above? Any comments will be highly appreciated. Thanks!

Hey @burigolucas , I honestly don't maintain this project that much... hope you're getting some use out of it though.
As for your question... it's going to be a bit before I can actually try to test this. However, when using a plugin with mountebank... the plugin sends the entire request to the mountebank server where mountebank has all of the logic for the predicates. Basically mountebank handles matching the stubs and telling the plugin what response to send back.
In your case I think it should use the jsonpath of the request where the selector might match $..identifiers[0].data_id or $.value.identifiers[0].data_id. If it doesn't though, I'll have to create an example and take a look.
Let me know if that helps. Thanks!


[py] split value histograms

get split value histogram of a feature:
gbdt.get_split_value_histogram('f29', bins=5)
f29  SplitValue  Count
0           7.2     39
1          13.9      9
2          20.6      3
3          27.3      1
4          34.0      2

Sorry I've been quite busy and didn't get a chance to review. Could you utilize compat.py and make sure xgboost doesn't rely on pandas. Also consider adding a test. Thanks.

Is it fine to use the same as for "cv" with "as_pandas" for optional pandas usage?

Yeah

Any update on this?

unitest
using combat
does not rely on pands any longer

ok this way?

Thanks. Maybe a short docstring on what's being returned and move unit test to test_with_sklearn.py if you need sklearn to test it.

ok, sec :)

anything else?

Looks good. Missing a docstring for as_pandas and probably should give a warning if it's not installed. Will merge after the changes and when travis is happy.  :-)

is it fine to use "sys.stderr.write" for the warning here?

Yeah it's fine for now.


How do I create a new file?

How do I create a new file?

Hello! You just have to click on the button in the bottom right corner of the screen 😄 hope it helps!

@hacdias thank you but it keeps spinning and not actually creates any file.
What I did:

Successfully run caddy with the example Caddyfile.
Successfully open the admin interface. I can see the Add button there but:
a. I can only create a new file in the root folder (where I open up the terminal and run caddy)
b. When I navigate to the 'content/post' folder, I click the button and fill in my-new-post.md. After that it keeps spinning and no file is created.
c. I can create a new file in 'content/post' if I type in 'content/post/my-new-post.md' using the button in root folder. But the file does not include any archtypes that go with the theme I clone.

Hey @vanlong441: don't you receive any error in the console, or in the Developer Tools?

@hacdias no it just outputs the same thíng that running hugo alone does.

That is the same error as #97. I already fixed that but it's not currently available on caddyserver.com . Could you build Caddy from source with this plugin to check if everything runs as expected?

Closing due to inactivity.


Track releases for resolver jitpack.io

Where a build includes the resolver "https://jitpack.io", can we track those dependency upgrades?
For example, this project

Yes, I believe Scala steward can track dependency in custom resolver, as long as the resolver(s) are defined in build, and proper credential(s) are give if needed.
See https://github.com/fthomas/scala-steward/issues/319#issuecomment-575882277
I am using private-hosted Scala steward. It works fine with private resolver.

Cool. Maybe i didn’t give it enough time.
Or maybe it’s because the version changed from random sha to v0.0.1 and
that’s not recognised as an upgrade,
Thanks for the reply
On Mon, 8 Jun 2020 at 3:49 pm, TATSUNO Yasuhiro<EMAIL_ADDRESS>wrote:

Yes, I believe Scala steward can track dependency in custom resolver, as
long as the resolver(s) are defined in build, and proper credential(s) are
give if needed.
See #319 (comment)
https://github.com/fthomas/scala-steward/issues/319#issuecomment-575882277
I am using private-hosted Scala steward. It works fine with private
resolver.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/fthomas/scala-steward/issues/1472#issuecomment-640384165,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAFKY45MD4CJTFECSOZKTLRVR3X5ANCNFSM4NYAD4YQ
.


docs: add migration info

Codecov Report

Merging #1871 (93dab2d) into main (7756103) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main    #1871   +/-   ##
=======================================
  Coverage   87.12%   87.12%
=======================================
  Files          83       83
  Lines        9052     9052
  Branches      537      537
=======================================
  Hits         7887     7887
  Misses       1165     1165


Exploration stops too early with single init run

This PR fixes issue #173.
With a single explored point _distance_last_evaluations returns 0 and the algorithm interprets it as a converged state.

Codecov Report

Merging #174 into master will decrease coverage by 0.01%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master     #174      +/-   ##
==========================================
- Coverage   77.08%   77.07%   -0.02%
==========================================
  Files          92       92
  Lines        4233     4235       +2
==========================================
+ Hits         3263     3264       +1
- Misses        970      971       +1

Impacted Files
Coverage Δ

GPyOpt/core/bo.py
57.74% <50%> (-0.08%)
: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 b3f6ece...aeefe2e. Read the comment docs.

Added unit test to cover the change. Code coverage is happy now.
When merged, could you publish a new version to pypi, integrating latest changes from master ?
(note that there are also some typos fixed in the user facing API in master but not published on pypi yet)


feat(@angular/cli): add eject --config option

Fixes https://github.com/angular/angular-cli/issues/9878.

Hi @sinedied,
We do not support eject in 6.0 yet. When we do we'll have a proper eject workflow. If you rebase this PR on top of the 1.7.x branch I'm open to review and merge it (and release it with 1.7.5). Let me know.

@hansl Sure, I'll do that ASAP, thanks for the feedback

@hansl It's done, should be good but seems there's an issue with the command that checks the commit's message, is there anything I should do to fix it?

The eject feature is currently being reimplemented within the angular/devkit repository located here: https://github.com/angular/devkit

@clydin Thanks for the heads up, I'll take a look to rebase the changes.
What about the 1.7.x . branch, isn't it worth merging as it's ready?


GUACAMOLE-680: Implement a guaranteed logout handler hook

This is my attempt at a solution for GUACAMOLE-680.  From the discussion in this https://github.com/apache/guacamole-client/pull/346 I wanted to create a utility 'service' that would handle this use case.
I thought about making this generic and adding handlers for other events...but I don't think that is the route that we want to go.  This is a specific use case for the user logout case so it should be handled by the service that handles those actions.  The AngularJS broadcast system should be good enough for other situations.
Example usage in a guacamole extension:
angular.module('someModule').run(['authenticationService',
    function logoutListener(authenticationService) {

    authenticationService.registerLogoutHandler(() => {
       // Do your actions that are needed here.
    })

}]);

// Ensure the someModule module is loaded along with the rest of the app
angular.module('index').requires.push('someModule');

Thanks @knacktim - Overall I like this approach, but am curious what @mike-jumper has to say about it.
I do have a couple of concerns:

I wonder if there is some other/better way to handle the case where a reload/redirect by a login handler causes the remaining ones to not be processed. It seems like just noting that in the documentation of the function could be confusing when it gets to the admin level and one or more modules (SSO logout, for example) causes another one to fail to actually run. I don't have any great ideas for how to handle that, so curious if we can brainstorm up some possible alternatives.
I don't know if there's any level of sanity checks we should do on the registered functions to make sure that they don't get abused - purposely or inadvertently - to do bad things to the users' browsers? Again, I don't have any great ideas, here, just seems like blindly running whatever function is passed in might be asking for exploitation down the line somewhere...

I wonder if there is some other/better way to handle the case where a reload/redirect by a login handler causes the remaining ones to not be processed. It seems like just noting that in the documentation of the function could be confusing when it gets to the admin level and one or more modules (SSO logout, for example) causes another one to fail to actually run. I don't have any great ideas for how to handle that, so curious if we can brainstorm up some possible alternatives.

I couldn't find anything in the AngularJS API to handle 'guaranteed delivery' of events.  Even using something like the Broadcast Channel API would still break on the reload.  I felt that this was the most straightforward way to accomplish this.

I don't know if there's any level of sanity checks we should do on the registered functions to make sure that they don't get abused - purposely or inadvertently - to do bad things to the users' browsers? Again, I don't have any great ideas, here, just seems like blindly running whatever function is passed in might be asking for exploitation down the line somewhere...

Is there a fundamental difference between what I am doing here and someone implementing a guacamole extension using a $rootScope.on('blah', nefariousFunction)?  Unless I am thinking about this incorrectly?

Used this to implement GUACAMOLE-519.  Here is what it looked like:
angular.module('openid').run(['$routeParams', 'authenticationService',
    function openIDLogoutListener($routeParams, authenticationService) {

    let config = {} // TODO get these from backend

    authenticationService.registerLogoutHandler(() => {
      if ($routeParams && Object.prototype.hasOwnProperty.call($routeParams, 'id_token')) {
        $.get({
          url: config['openid_logout_endpoint'],
          dataType: 'application/json',
          async: false,
          data: {
            client_id: config['openid_client_id'],
            id_token_hint: $routeParams.id_token
          },
          success: function(resp) {
            console.log("Success");
          },
          error: function() {
            console.error("Error when trying to log out");
          }
        })
      }
    })

}]);

// Ensure the openid module is loaded along with the rest of the app
angular.module('index').requires.push('openid');

For CAS, we must assure that function is called after guacamole session is destroyed.
Because next step in protocol is to redirect to
$window.location.href = config['cas_authorization_endpoint"] + "/logout"
Could the logic be inverted ?
service.logout
=> delete cookie
=> call requestService({ method: 'DELETE', url: 'api/tokens/' + token  })
=> on requestService finished, call return $q.all(getLogoutHandlerPromises())

Could the logic be inverted ? : do local stuff then remote SSO stuff

I will take a stab at this

Any update on this? I'm also highly interested in this feature. We need that for the SAML authentication extension to destroy the session on the idp.

Any update on this? I'm also highly interested in this feature. We need that for the SAML authentication extension to destroy the session on the idp.

I have been poking at this when I get time, but I haven't found a good way to do a synchronous REST call.

I have been poking at this when I get time, but I haven't found a good way to do a synchronous REST call.

For CAS, we must assure that function is called after guacamole session is destroyed.
Because next step in protocol is to redirect to
$window.location.href = config['cas_authorization_endpoint"] + "/logout"
Could the logic be inverted ? : do local stuff then remote SSO stuff
service.logout
=> delete cookie
=> call requestService({ method: 'DELETE', url: 'api/tokens/' + token  })
=> on requestService finished, call return $q.all(getLogoutHandlerPromises())

My proposed change for this is the following:
return requestService({
  method: 'DELETE',
  url: 'api/tokens/' + token
}).then(() => {
  return $q.all(getLogoutHandlerPromises());
})

But I need to finish testing on this to ensure its doing what I think it is.

For CAS, we must assure that function is called after guacamole session is destroyed.
Because next step in protocol is to redirect to
$window.location.href = config['cas_authorization_endpoint"] + "/logout"
Could the logic be inverted ? : do local stuff then remote SSO stuff
service.logout
=> delete cookie
=> call requestService({ method: 'DELETE', url: 'api/tokens/' + token  })
=> on requestService finished, call return $q.all(getLogoutHandlerPromises())

My proposed change for this is the following:
return requestService({
  method: 'DELETE',
  url: 'api/tokens/' + token
}).then(() => {
  return $q.all(getLogoutHandlerPromises());
})

But I need to finish testing on this to ensure its doing what I think it is.

@necouchman

I wonder if there is some other/better way to handle the case where a reload/redirect by a login handler causes the remaining ones to not be processed. It seems like just noting that in the documentation of the function could be confusing when it gets to the admin level and one or more modules (SSO logout, for example) causes another one to fail to actually run. I don't have any great ideas for how to handle that, so curious if we can brainstorm up some possible alternatives.

I still don't have a good way to tackle this -- I am open to suggestions.
After looking more at the documentation of $q.all() is that the following updates will get this to where we want this to be.  The only problem that I see is that if ANY of the promises call reject() then it is unclear to me if $q.all will stop processing.  (at least that is how I understood this documentation)
I updated the follow implementation for [GUACAMOLE-519] to use the new handler hooks.
angular.module('openid').run(['$routeParams', 'authenticationService',
    function openIDLogoutListener($routeParams, authenticationService) {

    let config = {} // TODO get these from backend

    authenticationService.registerLogoutHandler((resolve, reject) => {
      if ($routeParams && Object.prototype.hasOwnProperty.call($routeParams, 'id_token')) {
        $.get({
          url: config['openid_logout_endpoint'],
          dataType: 'application/json',
          async: false,
          data: {
            client_id: config['openid_client_id'],
            id_token_hint: $routeParams.id_token
          },
          success: function(resp) {
            resolve("Success");
          },
          error: function() {
            reject("Error when trying to log out");
          }
        })
      }
    })

}]);

// Ensure the openid module is loaded along with the rest of the app
angular.module('index').requires.push('openid');

@necouchman

I wonder if there is some other/better way to handle the case where a reload/redirect by a login handler causes the remaining ones to not be processed. It seems like just noting that in the documentation of the function could be confusing when it gets to the admin level and one or more modules (SSO logout, for example) causes another one to fail to actually run. I don't have any great ideas for how to handle that, so curious if we can brainstorm up some possible alternatives.

I still don't have a good way to tackle this -- I am open to suggestions.
After looking more at the documentation of $q.all() is that the following updates will get this to where we want this to be.  The only problem that I see is that if ANY of the promises call reject() then it is unclear to me if $q.all will stop processing.  (at least that is how I understood this documentation)
I updated the follow implementation for [GUACAMOLE-519] to use the new handler hooks.
angular.module('openid').run(['$routeParams', 'authenticationService',
    function openIDLogoutListener($routeParams, authenticationService) {

    let config = {} // TODO get these from backend

    authenticationService.registerLogoutHandler((resolve, reject) => {
      if ($routeParams && Object.prototype.hasOwnProperty.call($routeParams, 'id_token')) {
        $.get({
          url: config['openid_logout_endpoint'],
          dataType: 'application/json',
          async: false,
          data: {
            client_id: config['openid_client_id'],
            id_token_hint: $routeParams.id_token
          },
          success: function(resp) {
            resolve("Success");
          },
          error: function() {
            reject("Error when trying to log out");
          }
        })
      }
    })

}]);

// Ensure the openid module is loaded along with the rest of the app
angular.module('index').requires.push('openid');

@mike-jumper I am going to try and work on these fixes soon.  (Life is busy for me atm)

Perhaps it would be better to establish a generic, non-Angular, global object defined by the webapp that could be used as the overall Guacamole web application event target? That would allow extensions to hook into and deal with various events independently of AngularJS, and would provide the webapp with a more generic and friendly hook mechanism.

I like this idea.  I took a look at the Event Target that you linked above and I think I would run into the same shortcoming that I had in my use case of making a REST call in the listener function.  I don't want the listener function to be marked as 'done' until the REST call out to the Identity Provider is done and I call some kind of 'resolve' or 'success' callback.
I think it is feasible for me to do some refactoring on the event target to use the Promises API.  Does that sound like what you had in mind?

...
I like this idea. I took a look at the Event Target that you linked above and I think I would run into the same shortcoming that I had in my use case of making a REST call in the listener function. I don't want the listener function to be marked as 'done' until the REST call out to the Identity Provider is done and I call some kind of 'resolve' or 'success' callback.
I think it is feasible for me to do some refactoring on the event target to use the Promises API. Does that sound like what you had in mind?

I'd think either implementation would allow an extension to reliably hook into application logout. Is your concern that you want to be able to manually reject the promise returned by authenticationService.logout() from within a logout hook?

angular.module('openid').run(['$routeParams', 'authenticationService',
    function openIDLogoutListener($routeParams, authenticationService) {

    let config = {} // TODO get these from backend

    authenticationService.registerLogoutHandler((resolve, reject) => {
      if ($routeParams && Object.prototype.hasOwnProperty.call($routeParams, 'id_token')) {
        $.get({
          url: config['openid_logout_endpoint'],
          dataType: 'application/json',
          async: false,
          data: {
            client_id: config['openid_client_id'],
            id_token_hint: $routeParams.id_token
          },
          success: function(resp) {
            resolve("Success");
          },
          error: function() {
            reject("Error when trying to log out");
          }
        })
      }
    })

}]);

@mike-jumper

I'd think either implementation would allow an extension to reliably hook into application logout. Is your concern that you want to be able to manually reject the promise returned by authenticationService.logout() from within a logout hook?

Looking at the above use case as an example.  I am focusing on this part here:
https://github.com/apache/guacamole-client/blob/5319f9011a0cca5b024709adb9a512c2d1070e90/guacamole-common-js/src/main/webapp/modules/Event.js#L217-L230
If users do any async REST calls inside of a relevantListener I need the dispatch method to return a Promise.all() promise to the caller so that if needed, they can trigger a .then() after they are sure all of the listeners have been handled the event.  Otherwise I think there is a risk that we propagate the event, then the page could get refreshed before we are sure that the handler was finished.
I don't think we care if the action was resolve or reject, we just need a hook to tell us when the listener is done.
It is totally possible that I am overthinking this :zany_face:

So, the idea is that implementations need to be able to (somehow) hook into the promise stack of the logout process to ensure that any async operations they may need to perform during logout are allowed to complete before the default behavior (reloading the page) breaks those async operations?

Yep!

In that case, what about:

Leverage Guacamole.Event.Target.
In the event implementation that extends Guacamole.Event, expose the logout promise as a property.

Implementations that hook into the logout event would then be able to layer their own async operations onto the promise. As long as that default reload operation is added to the promise only after dispatching the event, things would work as you describe.

I am hoping to get the time to refactor to this implementation in the next week or so!

I have a new implementation that should satisfy all of the review comments...but I am having a problem with the jasmine spec.
Error:
-------------------------------------------------------
 J A S M I N E   S P E C S
-------------------------------------------------------
[INFO]
Guacamole.Event
  when an event is dispatched
    should invoke the legacy handler for matching events <<< FAILURE!
      * ReferenceError: Can't find variable: Promise in http://localhost:41497/src/all.min.js (line 57)
    should invoke all listeners for matching events <<< FAILURE!
      * ReferenceError: Can't find variable: Promise in http://localhost:41497/src/all.min.js (line 57)
    should not invoke any listeners for non-matching events <<< FAILURE!
      * ReferenceError: Can't find variable: Promise in http://localhost:41497/src/all.min.js (line 57)
    should not invoke any listeners that have been removed <<< FAILURE!
      * ReferenceError: Can't find variable: Promise in http://localhost:41497/src/all.min.js (line 57)
  when listeners are removed
    should return whether a listener is successfully removed

Results: 5 specs, 4 failures, 0 pending

I believe it may be related to PhantomJS not supporting the Promise API.  There are some solutions on this thread here: https://github.com/ariya/phantomjs/issues/12401
Am I missing some other promise API that is already included in Guacamole-client?

Am I missing some other promise API that is already included in Guacamole-client?

While there is a promise API included within the Guacamole webapp via AngularJS ($q), there isn't one included with guacamole-common-js, and the core guacamole-common-js shouldn't rely on the promise API if this would affect compatibility with older browsers.
Shouldn't the change leveraging the promise be at the webapp level rather than in guacamole-common-js? The former is a full-fledged webapp that can rely on bundling any libraries it requires, while the latter is a reusable library that should not be too tightly coupled with the needs of the webapp.
If modifying guacamole-common-js to support promises if the implementation wishes to use promises, this could make sense, but it shouldn't require them.

@mike-jumper It appears I misunderstood what you originally asked for.  I'll take another crack at this today :)

@mike-jumper Is this implementation closer to what you had in mind?  I have more testing to do, just wanted to make sure I am on the right track :)

This is looking better, yes. My feedback on this latest iteration:

It's seems odd to me to subclass Guacamole.Event.Target rather than Guacamole.Event.

For external code to be able to hook into the dispatched Guacamole.Event, there will need to be some sort of global Guacamole.Event.Target that extensions, etc. can rely on existing.

It's a bit disconcerting to me that guaranteed is in quotes here:

Any event handlers that return a Promise will be 'Guaranteed' to finish before the logout refresh happens.

;)

I think it would make more sense to subclass Guacamole.Event, provided some mechanism on that subclass to allow implementations to associate the promises of their own async operations with the event, and then handle $q.all() or similar in the part of the code that owns the event after dispatch() has finished.
For example:

Magical async subclass of Guacamole.Event is dispatched via dispatch(). Perhaps the subclass has an array of associated promises. Perhaps it keeps that hidden and provides a function for associating operations. Perhaps it exposes a single promise that can be replaced with another to form an arbitrary chain. In any case, it provides some API for associating the promises of additional async operations with the event.
A listener associates its own additional async operation promise with the event using the above mechanism.
dispatch() returns and the code that originally invoked dispatch() inspects the contents of that event and deals with the relevant promises.

@knacktim Any further progress, here?

@necouchman I will try to get some more time on this next Monday :)

That level of the API doesn't, no, but part of the idea behind Guacamole.Event is that it may be extended to produce other more specific events.
For example, #613 is partial migration toward using Guacamole.Event which updates Guacamole.Mouse to subclass Guacamole.Event.Target for event handling. The Guacamole.Mouse implementation defines its own subclass of Guacamole.Event (Guacamole.Mouse.MouseEvent) that exposes the mouse state.
Guacamole.Event is not itself aware of mouse state, but subclass of Guacamole.Event specific to the mouse is. The same could go for a subclass of Guacamole.Event intended to be associated with asynchronous operations.

Waaaait a minute ...

So, the idea is that implementations need to be able to (somehow) hook into the promise stack of the logout process to ensure that any async operations they may need to perform during logout are allowed to complete before the default behavior (reloading the page) breaks those async operations?

Yep!

The code in question is:
https://github.com/apache/guacamole-client/blob/754e9649f1fa0ba225ee42b56ded64bc283d17df/guacamole/src/main/webapp/app/navigation/directives/guacUserMenu.js#L145-L148
If things were updated such that:

The guacLogout event behaves as documented.
$location.reload() is not called.
Upon logout, the current contents of the browser window are replaced with a generic "You have been logged out" message (rather than attempting to reload and thus reshow a login prompt).

would that solve things?
I ask because the above would avoid extensive restructuring of the webapp's current handling of events, would avoid having to define a whole new type of event, and would solve the issue with OpenID, SAML, and others where clicking "Logout" appears to have no effect because the user is almost instantly SSO'd back in.

Yes, I believe that would work!
The only risk with doing that is that we need to make sure to clean up the state of the client properly.  Since the reload was doing that for us.  There will also need to be a button to log in again so that a user can get back to the login page.

Yes, I believe that would work!

Great! The relevant PR is: #620

The only risk with doing that is that we need to make sure to clean up the state of the client properly. Since the reload was doing that for us.

It's not the route reload that cleans up client state, but rather the storage management implementation. On the client side, each active client is stored in memory with storage that is tied to the user's session:
https://github.com/apache/guacamole-client/blob/111647b756f6fe33678587fa933ff0964c4c841b/guacamole/src/main/frontend/src/app/client/services/guacClientManager.js#L41-L46
That destructor callback will be invoked by the storage management service when guacLogout is fired.
Of course, that's all independent of the server-side handling of state, which is also automatically cleaned up after logout. Whether malfunctioning or malicious, it's not possible for the client to maintain an active connection if their session has ended.

Closing in favor of #620 (see above).


Virus detected

I am unable to install this because there was a virus detected

Turn off real time protection and exclude it before installing


Erro when use pip install super-gradients

🐛 Describe the bug
I trying install super-gradients on jupyter notebook using !pip install super-gradients ang get this error:
error: subprocess-exited-with-error
Building wheel for pycocotools (pyproject.toml) did not run successfully.
exit code: 1
[17 lines of output]
running bdist_wheel
running build
running build_py
creating build
creating build\lib.win-amd64-cpython-310
creating build\lib.win-amd64-cpython-310\pycocotools
copying pycocotools\coco.py -> build\lib.win-amd64-cpython-310\pycocotools
copying pycocotools\cocoeval.py -> build\lib.win-amd64-cpython-310\pycocotools
copying pycocotools\mask.py -> build\lib.win-amd64-cpython-310\pycocotools
copying pycocotools_init_.py -> build\lib.win-amd64-cpython-310\pycocotools
running build_ext
C:\Users\USER\AppData\Local\Temp\pip-build-env-zm4t8rny\overlay\Lib\site-packages\Cython\Compiler\Main.py:381: FutureWarning: Cython directive 'language_level' not set, using '3str' for now (Py3). This has changed from earlier releases! File: C:\Users\USER\AppData\Local\Temp\pip-install-zk69wcbg\pycocotools_7ed8db31a5e54fb3b9bf7830d670b434\pycocotools_mask.pyx
tree = Parsing.p_module(s, pxd, full_module_name)
Compiling pycocotools/_mask.pyx because it changed.
[1/1] Cythonizing pycocotools/_mask.pyx
building 'pycocotools._mask' extension
error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for pycocotools
ERROR: Could not build wheels for pycocotools, which is required to install pyproject.toml-based projects
Versions
Collecting environment information...
PyTorch version: N/A
Is debug build: N/A
CUDA used to build PyTorch: N/A
ROCM used to build PyTorch: N/A
OS: Microsoft Windows 10 Enterprise
GCC version: Could not collect
Clang version: Could not collect
CMake version: Could not collect
Libc version: N/A
Python version: 3.10.13 | packaged by Anaconda, Inc. | (main, Sep 11 2023, 13:24:38) [MSC v.1916 64 bit (AMD64)] (64-bit runtime)
Python platform: Windows-10-10.0.19044-SP0
Is CUDA available: N/A
CUDA runtime version: Could not collect
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: Could not collect
Nvidia driver version: Could not collect
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: N/A
CPU:
Architecture=9
CurrentClockSpeed=1711
DeviceID=CPU0
Family=198
L2CacheSize=4096
L2CacheSpeed=
Manufacturer=GenuineIntel
MaxClockSpeed=2200
Name=12th Gen Intel(R) Core(TM) i7-1270P
ProcessorType=3
Revision=
Versions of relevant libraries:
[pip3] No relevant packages
[conda] No relevant packages

As the name suggests - you need C++ compiler to build pycocotools:
error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/

Please search in closed issues, since this is a common problem and there were suggestsion how to tackle that.

me, too. I already install c++, but still got this error.

Building wheels for collected packages: pycocotools, termcolor, treelib, antlr4-python3-runtime, stringcase, future
Building wheel for pycocotools (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for pycocotools (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [17 lines of output]
running bdist_wheel
running build
running build_py
creating build
creating build\lib.win-amd64-cpython-39
creating build\lib.win-amd64-cpython-39\pycocotools
copying pycocotools\coco.py -> build\lib.win-amd64-cpython-39\pycocotools
copying pycocotools\cocoeval.py -> build\lib.win-amd64-cpython-39\pycocotools
copying pycocotools\mask.py -> build\lib.win-amd64-cpython-39\pycocotools
copying pycocotools_init_.py -> build\lib.win-amd64-cpython-39\pycocotools
running build_ext
C:\Users\heyongli\AppData\Local\Temp\pip-build-env-d881ntpo\overlay\Lib\site-packages\Cython\Compiler\Main.py:381: FutureWarning: Cython directive 'language_level' not set, using '3str' for now (Py3). This has changed from earlier releases! File: C:\Users\heyongli\AppData\Local\Temp\pip-install-8cwmq8\pycocotools_29e8548005774c608ebde2f056baf8f3\pycocotools_mask.pyx
tree = Parsing.p_module(s, pxd, full_module_name)
Compiling pycocotools/_mask.pyx because it changed.
[1/1] Cythonizing pycocotools/_mask.pyx
building 'pycocotools._mask' extension
error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for pycocotools


Prepare for ODH release and update params env to <IP_ADDRESS>

Please note that the target branch is release-0.12.0 although the tag is <IP_ADDRESS> per @israel-hdez's request. This is so we can match with the rest of the stack semantics for this ODH release.
Description

How Has This Been Tested?

Merge criteria:

[ ] The commits are squashed in a cohesive manner and have meaningful messages.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has manually tested the changes and verified that the changes work

LGTM but @israel-hdez please confirm:

Please note that the target branch is release-0.12.0 although the tag is <IP_ADDRESS> per @israel-hdez's request. This is so we can match with the rest of the stack semantics for this ODH release.

This is more like a @Jooho request than mine. But yes, this is what we want to do.
/lgtm

/hold

/unhold


[HUDI-4433] Hudi-CLI repair deduplicate not working with non-partitio…

…ned dataset
Change Logs
When using the repair deduplicate command with hudi-cli, There is no way to run it on the unpartitioned dataset, so modify the cli parameter.
Impact
Describe any public API or user-facing feature change or any performance impact.
Risk level: none | low | medium | high
Choose one. If medium or high, explain what verification was done to mitigate the risks.
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@pratyakshsharma Could you review this short code?

@yihua I added integration tests by referencing existing ones. Could you review this?

@yihua @codope I have found the cause of the above ci failed.
If an empty string is passed to the duplicatedPartitionPath parameter of the repair deduplicate command, the checkNotNull function recognizes a null value when processing the argument of the sparkLauncher.addAppArgs function, and the spark job does not run properly.
If fixed this part, I think it will be successful.

@yihua @codope I have found the cause of the above ci failed.
If an empty string is passed to the duplicatedPartitionPath parameter of the repair deduplicate command, the checkNotNull function recognizes a null value when processing the argument of the sparkLauncher.addAppArgs function, and the spark job does not run properly.
If fixed this part, I think it will be successful.

@brightwon Is this behavior related to what #6489 is trying to fix?

It could be a spring shell issue! In order to clearly understand this problem, I need to log and check all the parameters passed from the cli.
If I can test in my local machine, it will be easy to check. But I'm having trouble constructing a local docker environments. Is there any other way I can run the integration-tests, check the logs I left, and debug?

@brightwon You may use mvn command to run the specific IT.

@codope rebase is done. and I separated table path for non partitioned dataset tests.


Why is the default idleTimeout 1000ms?

I was trying to understand why kafka-node was consuming faster than no-kafka and saw that kafka-node doesn't have a delay between fetch requests
yet no-kafka defaults to 1000ms for its fetch loop
Was there a reason to set the default at 1000ms (seems high)? Can you think of any risks of setting it to 0? (it also looks like the official Java client fetches continuously)

It suited my needs better than continuous fetching with zero timeout.
I also don't see any risks with setting idleTimeout to 0.

Thank you @oleksiyk and thank you for maintaining a great library.


Ignore uncleanShutdown error when state is .head or .body

Hi there,
I think we should ignore uncleanShutdown when state is .head or .body, please review it. thx.

I am...unsure about this. This is the only place where .uncleanShutdown actually does communicate useful information: specifically, that we didn't know where EOF was, and the remote server didn't use TLS to tell us, so we can't tell whether the response body got truncated or not. I don't think signalling an error here is necessary the wrong thing to do.
What it may be worth doing is making this behaviour configurable, so for users who don't care they can choose to ignore this error and always treat it as a clean EOF.

https://github.com/swift-server/async-http-client/pull/77/files#diff-bd03a2521c79f3da4bd5825512ca9979R431
We know EOF even if we ignore .uncleanShutdown.

No we don't, we only know that when content-length is set: that is, we know it in testWrongContentLengthWithNIOSSLUncleanShutdown, but testNoContentLengthWithNIOSSLUncleanShutdown does not error, and in my view it should.
The problem is that when content-length is not set, the complete response body is signalled by shutting the connection down as discussed in RFC 7230 § 3.3.3 Message Body Length:

Otherwise, this is a response message without a declared message body length, so the message body length is determined by the number of octets received prior to the server closing the connection.

In this case, the .uncleanShutdown error is warning you that a network attacker could have injected a TCP FIN to forcibly truncate the response body. In this case, async-http-client cannot be confident that this has not happened, so we warn against it.
I am open to having settings put in place to allow you to ignore this error, but defaulting to reporting this error is the correct thing to do.

@Lukasa We can configurate it now, please continue to review.

@swift-server-bot test this please

@swift-server-bot test this please

@swift-server-bot test this please

@vkill thank you!


yum conflicts?!

Hello,
getting weird yum conflicts for latest mariadb101u "yum update" - how to solve?
Thx
Andreas Schnederle-Wagner
bash-4.2# yum update
Loaded plugins: fastestmirror, protectbase
base                                                                                | 3.6 kB  00:00:00
epel/x86_64/metalink                                                                                |  26 kB  00:00:00
extras                                                                                | 3.4 kB  00:00:00
ius                                                                                | 2.2 kB  00:00:00
updates                                                                                | 3.4 kB  00:00:00
Loading mirror speeds from cached hostfile
Excluding mirror: gd.tuwien.ac.at
 * base: mirror.easyname.at
 * epel: mirror.inode.at
Excluding mirror: gd.tuwien.ac.at
 * extras: mirror.easyname.at
 * ius: ftp.astral.ro
Excluding mirror: gd.tuwien.ac.at
 * updates: mirror.easyname.at
0 packages excluded due to repository protections
Resolving Dependencies
--> Running transaction check
---> Package epel-release.noarch 0:7-5 will be updated
---> Package epel-release.noarch 0:7-6 will be an update
---> Package mariadb101u.x86_64 1:10.1.12-1.ius.centos7 will be updated
---> Package mariadb101u.x86_64 1:10.1.13-1.ius.centos7 will be an update
---> Package mariadb101u-common.x86_64 1:10.1.12-1.ius.centos7 will be updated
---> Package mariadb101u-common.x86_64 1:10.1.13-1.ius.centos7 will be an update
---> Package mariadb101u-config.x86_64 1:10.1.12-1.ius.centos7 will be updated
---> Package mariadb101u-config.x86_64 1:10.1.13-1.ius.centos7 will be an update
---> Package mariadb101u-connect-engine.x86_64 1:10.1.12-1.ius.centos7 will be updated
---> Package mariadb101u-connect-engine.x86_64 1:10.1.13-1.ius.centos7 will be an update
---> Package mariadb101u-devel.x86_64 1:10.1.12-1.ius.centos7 will be updated
---> Package mariadb101u-devel.x86_64 1:10.1.13-1.ius.centos7 will be an update
---> Package mariadb101u-errmsg.x86_64 1:10.1.12-1.ius.centos7 will be updated
---> Package mariadb101u-errmsg.x86_64 1:10.1.13-1.ius.centos7 will be an update
---> Package mariadb101u-libs.x86_64 1:10.1.12-1.ius.centos7 will be updated
--> Processing Dependency: mysql-libs for package: 1:net-snmp-5.7.2-24.el7.x86_64
---> Package mariadb101u-libs.x86_64 1:10.1.13-1.ius.centos7 will be an update
---> Package mariadb101u-server.x86_64 1:10.1.12-1.ius.centos7 will be updated
---> Package mariadb101u-server.x86_64 1:10.1.13-1.ius.centos7 will be an update
--> Running transaction check
---> Package mariadb100u-libs.x86_64 1:10.0.24-1.ius.centos7 will be installed
--> Processing Dependency: mariadb100u-common(x86-64) = 1:10.0.24-1.ius.centos7 for package: 1:mariadb100u-libs-10.0.24-1.ius.centos7.x86_64
--> Running transaction check
---> Package mariadb100u-common.x86_64 1:10.0.24-1.ius.centos7 will be installed
--> Processing Dependency: mariadb100u-config = 1:10.0.24-1.ius.centos7 for package: 1:mariadb100u-common-10.0.24-1.ius.centos7.x86_64
--> Running transaction check
---> Package mariadb100u-config.x86_64 1:10.0.24-1.ius.centos7 will be installed
--> Processing Conflict: 1:mariadb101u-libs-10.1.13-1.ius.centos7.x86_64 conflicts mariadb-libs < 1:10.1.13-1.ius.centos7
--> Processing Conflict: 1:mariadb101u-config-10.1.13-1.ius.centos7.x86_64 conflicts mariadb-libs < 1:10.1.13-1.ius.centos7
--> Processing Conflict: 1:mariadb101u-config-10.1.13-1.ius.centos7.x86_64 conflicts mariadb-config < 1:10.1.13-1.ius.centos7
--> Processing Conflict: 1:mariadb101u-common-10.1.13-1.ius.centos7.x86_64 conflicts mariadb-common < 1:10.1.13-1.ius.centos7
--> Finished Dependency Resolution
Error: mariadb101u-libs conflicts with 1:mariadb100u-libs-10.0.24-1.ius.centos7.x86_64
Error: mariadb101u-common conflicts with 1:mariadb100u-common-10.0.24-1.ius.centos7.x86_64
Error: mariadb101u-config conflicts with 1:mariadb100u-config-10.0.24-1.ius.centos7.x86_64
Error: mariadb101u-config conflicts with 1:mariadb100u-libs-10.0.24-1.ius.centos7.x86_64
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
CT-386-bash-4.2# rpm -qa | grep mariadb
mariadb101u-10.1.12-1.ius.centos7.x86_64
mariadb101u-devel-10.1.12-1.ius.centos7.x86_64
mariadb101u-config-10.1.12-1.ius.centos7.x86_64
mariadb101u-libs-10.1.12-1.ius.centos7.x86_64
mariadb101u-errmsg-10.1.12-1.ius.centos7.x86_64
mariadb101u-server-10.1.12-1.ius.centos7.x86_64
mariadb101u-connect-engine-10.1.12-1.ius.centos7.x86_64
mariadb101u-common-10.1.12-1.ius.centos7.x86_64

bash-4.2# rpm -qa | grep maria
mariadb101u-10.1.12-1.ius.centos7.x86_64
mariadb101u-devel-10.1.12-1.ius.centos7.x86_64
mariadb101u-config-10.1.12-1.ius.centos7.x86_64
mariadb101u-libs-10.1.12-1.ius.centos7.x86_64
mariadb101u-errmsg-10.1.12-1.ius.centos7.x86_64
mariadb101u-server-10.1.12-1.ius.centos7.x86_64
mariadb101u-connect-engine-10.1.12-1.ius.centos7.x86_64
mariadb101u-common-10.1.12-1.ius.centos7.x86_64

Howdy @futureweb,
I tried to reproduce this issue, but it resolved the dependencies correctly for me.
http://pastebin.centos.org/44111/
You are on the right debugging track with the commands that you you shared already, but can you run them again with a few changes so I can get additional information?  Please pastebin the results.
rpm -qa | grep -i maria | sort
yum -d5 update

Issue confirmed here. It tries to install mariadb100u-config as dep even if mariadb101u is used.

After further troubleshooting we were able to isolate the issue.  net-snmp explicitly requires mysql-libs.  That is provided by stock mariadb-libs and mariadb100u-libs, and used to be provided by mariadb101u-libs until recently (see 1dd3f30).  The RHEL7 stock and Fedora mariadb RPMs are incredibly inconsistent with their use of Provides for mysql* and mysql-compat-* names, and we were attempting to clean this up.
To fix this, we are going to align our packages as closely as possible to RHEL7 stock RPMs (see 1a1db10) to provide the ideal compatibility with packages like net-snmp.
Summary of additions:

mariadb provide mysql
mariadb-libs provide mysql-libs
mariadb-server provide mysql-compat-server
mariadb-devel provide mysql-devel

Summary of removals:

mariadb provide mysql-compat-client

Builds are in progress with this change.

Builds have been completed and will hit the stable repositories after tonight's automation run.

Updated packages are now in the stable repositories.  I just confirmed that mariadb101u packages no longer cause issues when net-snmp is installed.

thx for this fast fix! ;-)

Hi,
did something change again? Got same Error again when trying to update the Server! :-/
CT-386-bash-4.2# yum update
Loaded plugins: fastestmirror, protectbase
Loading mirror speeds from cached hostfile
Excluding mirror: gd.tuwien.ac.at

base: mirror.inode.at
epel: mirror.inode.at
Excluding mirror: gd.tuwien.ac.at
extras: mirror.inode.at
ius: mirrors.ircam.fr
Excluding mirror: gd.tuwien.ac.at
updates: mirror.inode.at
0 packages excluded due to repository protections
Resolving Dependencies
--> Running transaction check
---> Package mariadb101u.x86_64 1:10.1.13-2.ius.centos7 will be updated
---> Package mariadb101u.x86_64 1:10.1.13-3.ius.centos7 will be an update
---> Package mariadb101u-common.x86_64 1:10.1.13-2.ius.centos7 will be updated
---> Package mariadb101u-common.x86_64 1:10.1.13-3.ius.centos7 will be an update
---> Package mariadb101u-config.x86_64 1:10.1.13-2.ius.centos7 will be updated
---> Package mariadb101u-config.x86_64 1:10.1.13-3.ius.centos7 will be an update
---> Package mariadb101u-connect-engine.x86_64 1:10.1.13-2.ius.centos7 will be updated
---> Package mariadb101u-connect-engine.x86_64 1:10.1.13-3.ius.centos7 will be an update
---> Package mariadb101u-devel.x86_64 1:10.1.13-2.ius.centos7 will be updated
---> Package mariadb101u-devel.x86_64 1:10.1.13-3.ius.centos7 will be an update
---> Package mariadb101u-errmsg.x86_64 1:10.1.13-2.ius.centos7 will be updated
---> Package mariadb101u-errmsg.x86_64 1:10.1.13-3.ius.centos7 will be an update
---> Package mariadb101u-libs.x86_64 1:10.1.13-2.ius.centos7 will be updated
--> Processing Dependency: mysql-libs for package: 1:net-snmp-5.7.2-24.el7.x86_64
---> Package mariadb101u-libs.x86_64 1:10.1.13-3.ius.centos7 will be an update
---> Package mariadb101u-server.x86_64 1:10.1.13-2.ius.centos7 will be updated
---> Package mariadb101u-server.x86_64 1:10.1.13-3.ius.centos7 will be an update
--> Running transaction check
---> Package mariadb100u-libs.x86_64 1:10.0.24-1.ius.centos7 will be installed
--> Processing Dependency: mariadb100u-common(x86-64) = 1:10.0.24-1.ius.centos7 for package: 1:mariadb100u-libs-10.0.24-1.ius.centos7.x86_64
--> Running transaction check
---> Package mariadb100u-common.x86_64 1:10.0.24-1.ius.centos7 will be installed
--> Processing Dependency: mariadb100u-config = 1:10.0.24-1.ius.centos7 for package: 1:mariadb100u-common-10.0.24-1.ius.centos7.x86_64
--> Running transaction check
---> Package mariadb100u-config.x86_64 1:10.0.24-1.ius.centos7 will be installed
--> Processing Conflict: 1:mariadb101u-config-10.1.13-3.ius.centos7.x86_64 conflicts mariadb-libs < 1:10.1.13-3.ius.centos7
--> Processing Conflict: 1:mariadb101u-config-10.1.13-3.ius.centos7.x86_64 conflicts mariadb-config < 1:10.1.13-3.ius.centos7
--> Processing Conflict: 1:mariadb101u-libs-10.1.13-3.ius.centos7.x86_64 conflicts mariadb-libs < 1:10.1.13-3.ius.centos7
--> Processing Conflict: 1:mariadb101u-common-10.1.13-3.ius.centos7.x86_64 conflicts mariadb-common < 1:10.1.13-3.ius.centos7
--> Finished Dependency Resolution
Error: mariadb101u-config conflicts with 1:mariadb100u-libs-10.0.24-1.ius.centos7.x86_64
Error: mariadb101u-common conflicts with 1:mariadb100u-common-10.0.24-1.ius.centos7.x86_64
Error: mariadb101u-config conflicts with 1:mariadb100u-config-10.0.24-1.ius.centos7.x86_64
Error: mariadb101u-libs conflicts with 1:mariadb100u-libs-10.0.24-1.ius.centos7.x86_64
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

Andreas

Hey @futureweb,
Looks like we accidentally pushed the readline branch as part of #1 ,into the stable repositories.  It was just meant to be in the testing repositories. I will work to do undo that.

alright!
This was the first Server I installed your REPO - and out of 3 Updates - 2 failed with Errors! :-/
I really hope that this isn't standard with this REPO?!?! :-/
Andreas

@futureweb,
These types of errors are rare, but we are humans and mistakes will happen.  Hopefully, you will hang around to see that these types of things do not happen often.

of course - errors can happen - no Question ... seems like I just had bad luck with my Experience here ... hehe :)
Got lot's of Servers I would like to update PHP ... so your REPO would be a good fit if it's stable!!

This issue has been addressed again.


Do not print out client warning so many times

╰─± deis register deis.foo.io
!    WARNING: Client and server API versions do not match. Please consider upgrading.
!    Client version: 2.0
!    Server version: 2.1
username: admin
password:
password (confirm):
email:
!    WARNING: Client and server API versions do not match. Please consider upgrading.
!    Client version: 2.0
!    Server version: 2.1
Registered admin
!    WARNING: Client and server API versions do not match. Please consider upgrading.
!    Client version: 2.0
!    Server version: 2.1
Logged in as admin

We should only warn the first time the command is executed.

👍

So to identify those three, the first one is for a pre-trip check to ensure the controller is up, the second is when registering the user and the third is when logging in. We make three separate requests to the controller in this command, but agree let's only do this on the first check.

These errors are generated by api requests, and if they occur, they're logged. The problem is that there is basically no way to check if the error has already previously occurred.
The easiest solution would be: have only connection test return the api-mismatch error, and to run it before every CLI command that interacts with the API.


Too little vertical margin in the Contact section in mobile

There is too little vertical margin between the Contact section elements on mobile resolutions.
See how the envelope icon is almost touching the phone number. There should be more margin between those elements.

Version: 5.1.4
Browser: Chrome 75 with resolution set to "iPhone X" from dev tools

Fixed in #155 - thanks for pointing this out!


feat(solver)!: Make Problem use builder pattern

Changes the Problem input struct (introduced in #54) to use the builder pattern.
This allows the soft_requirements field to be an Iterator rather than a Vec, which prevents having to unnecessarily clone the SolvableIds passed to soft_requirements (which in some cases could be on the order of hundreds of thousands). Also, this prevents adding a new input argument to Solver::solve (i.e. a new field in Problem) from being a breaking change.
The C++ bindings remain unchanged and rely on using a simple resolvo_cpp::Problem struct as before; they do not expose the builder pattern.

Thanks as always! :)


Embed - HTML error: Failed to execute 'serializeToString' on 'XMLSerializer'

Preflight Checklist

[x] agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Describe the bug
When I do File - Embed - HTML, and choose "Public URL of the diagram" — there is a problem the resulting snippet doesn't work.
It always fails with an error:
Failed to execute 'serializeToString' on 'XMLSerializer': parameter 1 is not of type 'Node'.
Expected behavior
The diagram should be loaded. This export for this file worked for me some time ago.
draw.io version:

20.5.3

Additional context
I found that the snippet does a request:
https://viewer.diagrams.net/embed2.js?&fetch=https%3A%2F%2Fdrive.google.com%2Fuc%3Fid%3D1aF7xgHkYU5kZfWriDrQN1l5bzBgrDWOg%26export%3Ddownload

and the result from the server should contain the content of a diagram file, but instead, there is an empty string inside decodeURIComponent call:
GraphViewer.cachedUrls['https:\/\/drive.google.com\/uc?id=1aF7xgHkYU5kZfWriDrQN1l5bzBgrDWOg&export=download'] = decodeURIComponent('');

Later this string is parsed as an XML and fails with the mentioned error.

Could you attach a print screen showing the error or if possible video showing all the steps and the result?
At the moment I am not able to reproduce the issue

Embedding settings

Then I download a result file, rename .txt to .htm and open in the browser.
Result:

How do you open the HTML file in the browser? Directly from the file system? That won't work, needs a web server.


trying to install development for local use

Hi, still new at this, but i tried following your instructions to install and got stuck at the "flask db init" section

any chance you could walk me through the install?

Hi, I am on vacation without access to my PC, and will not be able to answer in the next 10 days.
But then I will make sure to check the issue, please check for an answer later in October.

Fixed in 132ede588e696a8537648a0f46027f25d8bacdeb. Please pull changes and proceed with instructions starting from python -m pip install -r requirements.txt.
Alternatively just install missing dependency directly python -m pip install python-dotenv and flask db init must work.


docs: add kubeReserved default note

Fixes #5676
Description
Adds a note about how kubeReserved defaults effect ephemeral storage calculation
How was this change tested?
N/A
Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[x] No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 82.634%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5258

Relevant Lines:
6363

💛  - Coveralls


[ZEPPELIN-2764] update packages and documentation for ZeppelinHubRepo storage

What is this PR for?
update the packages/documentation/links due to migration of domain and renaming
What type of PR is it?
Documentation | Refactoring
Todos

[x] - update package/class names
[x] - update config
[x] - update docs

What is the Jira issue?
ZEPPELIN-2764
How should this be tested?
CI pass
Screenshots (if appropriate)
Questions:

Does the licenses files need update? n
Is there breaking changes for older versions? n
Does this needs documentation? n

This is for fixing ASF rule. LGTM


last-working-dir not working for me on OSX 10.10?

I'm running OSX 10.10 (Yosemite), zsh 5.0.5 and have updated to the latest oh my zsh.  I just switched over to zsh, and while other plugins seem to work out of the box (git, common-aliases, osx), last-working-dir doesn't start new shells in the last directory.
I checked that ~/.oh-my-zsh/cache exists, but nothing ever gets written to the directory.  I don't see how this would collide, but I used to have
#Recover and save workingdir
cd "$(<~/.lastdirectory)"
export PROMPT_COMMAND='printf %s "$PWD" > ~/.lastdirectory'

in my .profile (it's still there, but I checked it's not being run when a new shell starts).  Thanks for any help.

I'm embarrassed to say the issue was that I separated my plugins in .zshrc with commas rather than spaces.  Everything works.  Sorry for the spam!


Release 15.0.0 Tracking PR

🚨 Breaking Changes

TextInput size prop removed in favor of new variant prop #581
Label size prop removed in favor of new variant prop #581
Button size prop removed in favor of new variant and fontSize props #581
CircleBadge size prop now overrides default sizes based on new variant prop #581

🔨 Changes / Fixes

CircleBadge now accepts an inline boolean prop for inline rendering #581
TypeScript props interface for BorderBox now includes border props #599

@emplums @primer/ds-core How do you feel about releasing this today? Anything else we want to get into it?


Delete Overlap Issue #6288

Issue Reference
Link: https://github.com/bagisto/bagisto/issues/6288

@devansh-webkul
This is working fine. Please find the screenshot Here


ervice Fabric Managed Clusters - api version 2022-08-01-preview

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific language SDKs and CLIs that must be refreshed after the swagger is published.

[x] SDK of .NET (need service team to ensure code readiness)
[x] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[x] PowerShell
[x] CLI
[x] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[x] Check this box if any of the following appy to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.

[x] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

what's the change since 2022-06-01?

what's the change since 2022-06-01?
@weidongxu-microsoft below are the changes we are introducing on this api:

New properties:
Node Type properties
○ VmImageResourceId
○ FrontendConfigurations.ApplicationGatewayBackendAddressPoolId
Node Type Actions:
○ NodeTypeActionParameters.UDWiseUpdate

what's the change since 2022-06-01?
@weidongxu-microsoft below are the changes we are introducing on this api:

New properties: Node Type properties ○ VmImageResourceId ○ FrontendConfigurations.ApplicationGatewayBackendAddressPoolId
Node Type Actions: ○ NodeTypeActionParameters.UDWiseUpdate

Next time, please have one commit that contains these essential changes along. Don't mix it with api-version update or anything else. (I can find it in your 2nd commit, but it is just hard to review with other changes to dozens of examples.

what's the change since 2022-06-01?
@weidongxu-microsoft below are the changes we are introducing on this api:

New properties: Node Type properties ○ VmImageResourceId ○ FrontendConfigurations.ApplicationGatewayBackendAddressPoolId
Node Type Actions: ○ NodeTypeActionParameters.UDWiseUpdate

Next time, please have one commit that contains these essential changes along. Don't mix it with api-version update or anything else. (I can find it in your 2nd commit, but it is just hard to review with other changes to dozens of examples.

sure, will do that in the future

/azp run

/azp run

@weidongxu-microsoft the api is now available, please merge the pr.


Retrieve secrets using get_secret_value

Summary

I think it just sets the value as Secret() rather than the actual string without
Relevant Issue(s)

Checklist

[ ] Summarized PR's changes in CHANGELOG.md

I think need to add some logic too (if None)

Can you update the block type name to "Snowflake Credentials" and add a logo as part of this PR also?


Guessing

A fundamental flaw of minesweeper as a concept is that it is a puzzle game that you can lose. Guesses have to be made. Generation of the grid should ensure that the user does not have to guess.

Solver AI should make sure that it can be solved without guesswork. Will implement in near future.

Solver AI has been implemented with grid generation. However, for it to work properly, I need to have some sort of "tank solver", which will make the puzzles it generates a lot harder and enable the user to generate an expert guessless game (basic solver AI cannot solve that yet.).


README: "You can even run 32-bit applications on pure 64-bit systems" is not true: looks like I need to enable in kernel CONFIG_IA32_EMULATION

Pure 64-bit systems here means systems without 32-bit binaries and libraries. There is no way for me to make it work without CONFIG_IA32_EMULATION since it's a container, not a virtual machine.


webpack config changed for url and file loaders

Hi @KleoPetroff,
Are you planning to merge this or you want to keep this as a separate branch? I can add history fallback and redux next. Even if the Redux is added, people can still use React state management and it's always optional. Please tell me what I should do next?

I'm planning to merge it after I review it since it contains the file loader fix. It was better to create another PR just for the dependency updates, as I have some considerations about updating eslint, which may delay the merge.
You can go for the history fallback next. As for Redux, I don't plan to add it to master. You can create a separate branch for the implementation.

Thank you again for the wonderful work you did. :)


add script to aid in he last steps for releasing new images

What this PR does / why we need it:
Makes the life of maintainers a bit easier, while sticking to the manual tagging workflow.

/assign @xmudrii


Changing tabs to tab for vue/html-indent

See #1440 changing 'vue/html-indent': ['error', 'tab']` to match the vue/html-indent specs
I hope this is where the fix is. If not no harm in closing this.
Thanks for the great work!

Thanks! :+1:


Add /etc/hostname fix for macOS

This fix (or workaround) was identified by @oslook in #472. If it's a satisfactory fix then it would make sense to include it in the README.

Thanks @garettmd
Merged.


⚠ Site ANTS has degraded performance

In 745a111, Site ANTS (https://ants.gouv.fr) experienced degraded performance:

HTTP code: 200
Response time: 3299 ms

Resolved: Site ANTS performance has improved in 5ac41a3 after 14 minutes.


Coins with vendors

I don't know if it's since the new patch but the vendors all have the same bank of coins. if Haldor is at 0 coins all the sellers are at 0 coins too
In my memory, each trader had his own money
Thank you.
Simoss
ValheimPvpQc

Thanks! I'll check for that.

It worked as intended. Current trader coins limit is 10000. After sleep coins were updated accordingly.
I even spent some money at different traders to see if spent money somehow shared between them.
If you have more info on the issue it needs reproduction steps.
The code responsible for coins update is pretty simple and I can't see even potential issue or any compatibility problem.


Spelling error

Great library!
One small thing I noticed, "manhatten" distance is spelled wrong, should be "manhattan".
https://github.com/Mathigon/fermat.js/blob/master/src/geometry.js

Thanks for spotting this!
Fixed in https://github.com/Mathigon/fermat.js/commit/70bf6515870cb265dcee03987bcf653f8fb5e05b


Support isAnyOf

Also extracts the anyOf expression building for re-usage

Thank you.

btw I think my test cases with the class-strings are odd. Not sure if they add much value, I might get rid of them again :)


GraphRBAC should be under the "preview" folder

Discussed with @marstr , that being the history of graphrbac, this file should be in a "preview" folder. And then this deserves an issue here :)

Closing, I don't think it's relevant anymore

Closing, I don't think it's relevant anymore


docs: add ECR docs

Adds a reference to ECR support and the blog post.
Closes #105;

@RichiCoder1 Thanks for this and for pinging on #105, I was not aware of the recent change.
According to the AWS docs, authentication to a repo via AWS CLI v2 is done like so
aws ecr get-login-password --region $AWS_REGION --profile $PROFILE | oras login \
        --password-stdin \
        --username AWS \
        "${AWS_ACCOUNT_ID}.dkr.ecr.${AWS_REGION}.amazonaws.com"

It prevents this ugly warning:

WARNING! Using --password via the CLI is insecure. Use --password-stdin.

@RichiCoder1 Thanks for this and for pinging on #105, I was not aware of the recent change.
According to the AWS docs, authentication to a repo via AWS CLI v2 is done like so
aws ecr get-login-password --region $AWS_REGION --profile $PROFILE | oras login \
        --password-stdin \
        --username AWS \
        "${AWS_ACCOUNT_ID}.dkr.ecr.${AWS_REGION}.amazonaws.com"

It prevents this ugly warning:

WARNING! Using --password via the CLI is insecure. Use --password-stdin.

I think I had originally leaned towards keeping the example concise, but it's probably much better with that full example.

Thanks for the update. Meanwhile I opened a support ticket because I keep hitting 500 Internal Server Error
So I don't know how stable this is :)

Thanks for the update. Meanwhile I opened a support ticket because I keep hitting 500 Internal Server Error
So I don't know how stable this is :)

Oof :. I admit, this being AWS I expected it to be pretty rock solid from the outset. Hopefully you can quickly get to a solution!

LGTM, will probably want somebody from Amazon to review, cc @omieomye @mhausenblas @jtoberon

@RichiCoder1 can you rebase when you have a minute?

@jdolitsky Rebased and up to date


Initial work on Manage Packages page (and Delete Account shared code)

Updates PackageService.FindPackagesByOwner to include organization packages, which is used by both the ManagePackages and DeleteAccount views.
For Issue #4894:

Displays organization packages
Added logo next to Organization owners
Remaining work: Filtering by owner will come in separate PR

For Issue #5016:

Displays organization packages, and changes orphaned state to factor in organizations
Added logo next to Organization owners
Disables delete of organization and organization member accounts, until we have time to finish this

Adding screenshots now:
Route '/account/delete' showing org packages (org has 2 members / packages not orphans):

Route '/account/Packages' showing org packages:


TypeError on empty suggestions and can't reselect user in suggestions

https://github.com/stackernews/stacker.news/assets/27162016/6fef6895-8eab-47f6-af4b-c65240cc4466

<InputUserSuggest> seems to be behave not consistently. Can't reselect the same user:
https://github.com/stackernews/stacker.news/assets/27162016/d5778b3a-e6fc-4986-93a3-21e05a755900


[Breaking change]: Media Picker (legacy) (Umbraco.MediaPicker2) to be deprecated from version 11 and removed in version 14

Description
The "old" Media Picker (legacy) will not be implemented with the new backoffice that currently is expected to be introduced in version 14.
Version
Umbraco 14
Previous behavior
You could choose among the Media Picker (legacy) and its successor the Media Picker (v3).
New behavior
Use the Media Picker v3.
Type of breaking change

[ ] Binary incompatible: Existing binaries may encounter a breaking change in behavior, such as failure to load/execute or different run-time behavior.
[X] Source incompatible: Source code may encounter a breaking change in behavior when targeting the new runtime/component/SDK, such as compile errors or different run-time behavior.

Reason for change
With the new backoffice we want to streamline both the developer- and editor experience while we invest our effort in property editors that we foresee usable on a long term.
Recommended action
Avoid using the Media Picker (legacy).
Affected APIs
N/A

Is there any easy way on a v10 LTS site to see if Umbraco.MediaPicker2 is in-use anywhere? One of the things we're struggling with on these v14 LTS removals is evaluating what's in use and how to migrate everything. For example, someone suggested USync Migrations to move things from Grid/Nested Content. Now this MediaPicker v2 stuff (potentially) needs attention and other smaller things like 404 using Xpath needs to get sorted out. Ideally Umbraco would have some sort of migration tooling (maybe even building off of uSync Migrations) to make this easier for big sites with tons of content where it's a monumental task to re-do all of the content (again--we just did this in rebuilding from v7 to v10 LTS this summer and these items being removed weren't marked as deprecated unfortunately.)

I can recommend the plugin "diplo godmode". You can easily check where certain datatypes are used wih that.


Error: 'registerPlugin' is not exported

I am seeing the following error while trying to use it (npm run dev):
[!] Error: 'registerPlugin' is not exported by node_modules/filepond/dist/filepond.js, imported by node_modules/svelte-filepond/src/index.js
Versions

"filepond": "^4.21.0"
"svelte-filepond": "0.0.1"

Can you create a test case on https://codesandbox.io/

I've had the same problem. My solution was to change rollup-plugin-node-resolve to '@rollup/plugin-node-resolve.

I am already using  "@rollup/plugin-node-resolve": "^7.1.1",
and the error remains.
Error: 'registerPlugin' is not exported by node_modules/filepond/dist/filepond.js, imported by node_modules/svelte-filepond/src/index.js
does the svelte file pond have a different dependency version ?

It's weird, it's trying to import from the iife version of FilePond instead of the es module which is in the same folder. Anyone know how to instruct bundlers to use the esm version?

I've faced the same issue. It was solved by upgrading of @rollup/plugin-commonjs:
"@rollup/plugin-commonjs": "^14.0.0",

Same problem on vite

fixed the issue by removing the export from the index file and importing registerPlugin from filepond directly

@Taha-Firoz Can you share an example of how you solved the issue with vite?


Unexpected behavior for out-of-bounds filters

If a container to which the filter is applied is partially out of bounds, the filter can have unintended behavior.
Consider the reflection filter. The default point at which it switches from normal to "reflected" is at y = 0.5.

If we move the duck so that part of it is outside the viewport, the image we get is different:

The reason for this is that the filter is applied to the visible portion of the container.
However, what should one do to get the filter applied to the container as if it wasn't out of bounds? That is, the duck from the first picture, but translated up?
Is there even a way to get the position and size of the final filtered texture, so that we can at least compare it to the source container.
For example, in the above pictures, let's say that the original position of the duck sprite was [50, 50], with the size of [100, 100]. We then move it to [50, -50]. The filtered texture gets rendered at [50, 0], with size [100, 50]. Is there a way to get this "final" position of the filtered texture?

This may help in the coming pixi.js release: https://github.com/pixijs/pixijs/pull/10923

Yep, saw it on dev docs a moment ago.
Thanks :grin:
Is the release already scheduled? If so, where could I see the date?

Broken
https://jsfiddle.net/bigtimebuddy/tmjpovec/
Fixed
https://jsfiddle.net/bigtimebuddy/sfkah960/
It's unclear when the release will happen, but likely this week or next. In the meantime you  can get the latest dev version by running.
npm install pixi.js@dev


IB: Failed to render and update auto layout status.

Hello. First of all I would like to thank you for this library. I am trying to use this library to build my skeleton loading views, but when I insert a single GradientContainerView, IB breaks,and nothing renders, resulting in all of my VCs being blank in the IB.
The error I get in the build log is the following:
file:///.../LoadingView.xib: error: IB Designables: Failed to render and update auto layout status for UIView (iN0-l3-epB): dlopen(Skeleton.framework, 1): no suitable image found.  Did find:
	Skeleton.framework: required code signature missing for 'Skeleton.framework'

I suppose, as the message says, that if I fix the signature problem then my views will render and there will not be any problems. Is this something I need to solve on my side, or there is a signing problem in the library itself? (Keep in mind that the project builds just fine, it's just that InterfaceBuilder is broken)
Thank you!

I used CocoaPods. I have removed the library temporarily while I develop my app and will add it once I'm done using IB.
Any ideas/recommendations are appreciated!

Hmm. It would seem like this library might not be the problem after all. I will need to take a deeper look into this.
After disabling Skeleton, other libraries were giving me the same error (GoogleMobileAds SDK for example) and after removing them and adding Skeleton back in, it works as expected with no errors. I'll close the issue and if I face the problem again I'll let you know. Thank you for the support :)


vivaldi: libs to enable wayland native

Motivation for this change
Attempt to enable native wayland support for vivaldi, fixing #144860
Things done
Add wayland libs and handling for $NIXOS_OZONE_WL following wayland pkg. Add libglvnd to enable start up, suggested in https://github.com/NixOS/nixpkgs/issues/144860#issuecomment-1040839893
Vivaldi seems to run fine as native wayland, but lines are blurry on my hidpi display, probably because wayland isn't properly supported yet.
I don't have particular domain expertise here so further suggestions wanted.

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

I didn't make the libs optional as suggested in #126652, not sure if anyone has opinions there. IMO they should at least default to enabled so the cached build works with wayland.

not sure if this related to this activities, but just in case..
❯❯❯❯ vivaldi
[262616:262616:0901/120028.077757:ERROR:egl_util.cc(44)] Failed to load GLES library: /nix/store/6q7f1arn02xy7da74ppc6hjgxkv8mn5d-vivaldi-5.4.2753.37-1/op
ivaldi/libGLESv2.so: libwayland-client.so.0: cannot open shared object file: No such file or directory
[262616:262616:0901/120028.078708:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
[262682:262682:0901/120028.141825:ERROR:egl_util.cc(44)] Failed to load GLES library: /nix/store/6q7f1arn02xy7da74ppc6hjgxkv8mn5d-vivaldi-5.4.2753.37-1/op
ivaldi/libGLESv2.so: libwayland-client.so.0: cannot open shared object file: No such file or directory
[262682:262682:0901/120028.143074:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
[262704:262704:0901/120028.198485:ERROR:egl_util.cc(44)] Failed to load GLES library: /nix/store/6q7f1arn02xy7da74ppc6hjgxkv8mn5d-vivaldi-5.4.2753.37-1/op
ivaldi/libGLESv2.so: libwayland-client.so.0: cannot open shared object file: No such file or directory
[262704:262704:0901/120028.199535:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
[262729:262729:0901/120028.219852:ERROR:egl_util.cc(44)] Failed to load GLES library: /nix/store/6q7f1arn02xy7da74ppc6hjgxkv8mn5d-vivaldi-5.4.2753.37-1/op
ivaldi/libGLESv2.so: libwayland-client.so.0: cannot open shared object file: No such file or directory
[262729:262729:0901/120028.220849:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
[262750:262750:0901/120028.236317:ERROR:egl_util.cc(44)] Failed to load GLES library: /nix/store/6q7f1arn02xy7da74ppc6hjgxkv8mn5d-vivaldi-5.4.2753.37-1/op
ivaldi/libGLESv2.so: libwayland-client.so.0: cannot open shared object file: No such file or directory
[262750:262750:0901/120028.237313:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
[262777:262777:0901/120028.252366:ERROR:egl_util.cc(44)] Failed to load GLES library: /nix/store/6q7f1arn02xy7da74ppc6hjgxkv8mn5d-vivaldi-5.4.2753.37-1/op
ivaldi/libGLESv2.so: libwayland-client.so.0: cannot open shared object file: No such file or directory
[262777:262777:0901/120028.253371:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
[262785:262785:0901/120028.260714:ERROR:egl_util.cc(44)] Failed to load GLES library: /nix/store/6q7f1arn02xy7da74ppc6hjgxkv8mn5d-vivaldi-5.4.2753.37-1/op
ivaldi/libGLESv2.so: libwayland-client.so.0: cannot open shared object file: No such file or directory
[262785:262785:0901/120028.261756:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
[262792:262792:0901/120028.268892:ERROR:egl_util.cc(44)] Failed to load GLES library: /nix/store/6q7f1arn02xy7da74ppc6hjgxkv8mn5d-vivaldi-5.4.2753.37-1/op
ivaldi/libGLESv2.so: libwayland-client.so.0: cannot open shared object file: No such file or directory
[262792:262792:0901/120028.269892:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
[262799:262799:0901/120028.276324:ERROR:gpu_init.cc(486)] Passthrough is not supported, GL is disabled, ANGLE is
[262579:262579:0901/120029.818610:ERROR:CONSOLE(0)] "Uncaught (in promise) Error: A listener indicated an asynchronous response by returning true, but the
ssage channel closed before a response was received", source: chrome-extension://mpognobbkildjkofajifpdfhcoklimli/browser.html (0)
[262579:262579:0901/120029.959896:ERROR:CONSOLE(0)] "Uncaught (in promise) Error: A listener indicated an asynchronous response by returning true, but the
ssage channel closed before a response was received", source: chrome-extension://mpognobbkildjkofajifpdfhcoklimli/browser.html (0)

Vivaldi	5.4.2753.37 (Stable channel) stable (64-bit)
Revision	afc102add9800804fc6b151cdb0e28ff64064e2c
OS	Linux
JavaScript	V8 <IP_ADDRESS>

You probably need to add the drivers for your graphics card to https://search.nixos.org/options?query=hardware.opengl.extraPackages.

I'm getting the same issue as halturin, but I'm running home-manager on Ubuntu 22.04. Haven't made the complete switch to NixOS yet. I've tried starting vivaldi with nixGL vivaldi, but I still get the same message.
$ nixGL vivaldi
Opening in existing browser session.
[3167:3167:0100/000000.296651:ERROR:egl_util.cc(44)] Failed to load GLES library: /nix/store/r47wnjpbgr0bggy21yppf53h3vd6jp9s-vivaldi-5.4.2753.47/opt/vivaldi/libGLESv2.so: libwayland-client.so.0: cannot open shared object file: No such file or directory

I'm getting the same issue as halturin, but I'm running home-manager on Ubuntu 22.04. Haven't made the complete switch to NixOS yet. I've tried starting vivaldi with nixGL vivaldi, but I still get the same message.
$ nixGL vivaldi
Opening in existing browser session.
[3167:3167:0100/000000.296651:ERROR:egl_util.cc(44)] Failed to load GLES library: /nix/store/r47wnjpbgr0bggy21yppf53h3vd6jp9s-vivaldi-5.4.2753.47/opt/vivaldi/libGLESv2.so: libwayland-client.so.0: cannot open shared object file: No such file or directory

This is a different bug. Fixed in #222718.
I think, this can be closed, as its contribution is effectively in upstream already.


Update Icons

You got a lot of icons from #127, time to update them to be more Doki-Themed

 Update Icons #129

[ ] Update light theme icons


Not able to configure logshark with external Mongodb

Hi,
I am in the process of configuring Logshark with an external MongoDB. I have edited the Logshark.config as mentioned in the Guide. However, when I tried to run the following, I have been receiving an authentication error.
C:\Program Files\Logshark>logshark D:\Logs\logs.zip
Loading Logshark user configuration..
Failed to open connection to MongoDB database 'XX.XXX.XXX.XXX:27017': Command listDatabases failed: command listDatabases requires authentication.
Logshark run failed: Failed to open connection to MongoDB database 'XX.XXX.XXX.XXX:27017': Command listDatabases failed: command listDatabases requires authentication.
(IP hidden due to security reasons)
I did mention the credentials but for some reason logshark seems to be not able to read it. Please let me know if am missing anything here.
Appreciate your help.
Thanks,
Shruthi

Hi,
FWIW, here's the guide we use to enable authentication on our own internal databases:
https://docs.mongodb.com/manual/tutorial/enable-authentication/
The only two problems I had in the past causing similar errors were:

Forgot to include "--auth" into Mongo startup command
Did not have "admin" database

LogShark v4.1 is now the current version and it doesn't use MongoDB anymore. It is MUCH faster than the previous version as well, so please give it a try. In the meantime I am going to close this issue as it is no longer relevant to the current version.