[Windows] level_zero/ze_api.h not found when running UT.

Describe the bug
When running the UT on Windows, I got the following error. The Triton needs the level_zero to build, but it can't find it.
Note that in Linux, the level_zero headers come with the driver, but on Windows, we don't have this default behavior. May I ask what should I do?
E   subprocess.CalledProcessError: Command '['C:\\Program Files (x86)\\Intel\\oneAPI\\compiler\\latest\\bin\\icpx.EXE', 'C:\\Users\\sdp\\AppData\\Local\\Temp\\tmpr3g8gym8\\main.cpp', '-O3', '-shared', '-Wno-psabi', '-lze_loader', '-L/usr/local\\lib', '-LC:\\Users\\sdp\\miniforge3\\envs\\tongsu_stock_pt\\Lib\\site-packages\\triton\\backends\\intel\\lib', '-LC:\\Users\\sdp\\miniforge3\\envs\\tongsu_stock_pt\\Lib\\..\\libs', '-I/usr/local\\include', '-IC:\\Program Files (x86)\\Intel\\oneAPI\\compiler/latest/include', '-IC:\\Program Files (x86)\\Intel\\oneAPI\\compiler/latest/include/sycl', '-IC:\\Users\\sdp\\miniforge3\\envs\\tongsu_stock_pt\\Lib\\site-packages\\triton\\backends\\intel\\include', '-IC:\\Users\\sdp\\AppData\\Local\\Temp\\tmpr3g8gym8', '-IC:\\Users\\sdp\\miniforge3\\envs\\tongsu_stock_pt\\Include', '-INone', '-IC:\\Users\\sdp\\miniforge3\\envs\\tongsu_stock_pt\\lib\\site-packages\\numpy\\core\\include', '-o', 'C:\\Users\\sdp\\AppData\\Local\\Temp\\tmpr3g8gym8\\spirv_utils.cp310-win_amd64.pyd', '-fsycl']' returned non-zero exit status 1.
--------------------------------------------------------------- Captured stderr ---------------------------------------------------------------
In file included from C:\Users\sdp\AppData\Local\Temp\tmpr3g8gym8\main.cpp:17:
C:\Users\sdp\miniforge3\envs\ts_stock_pt\Lib\site-packages\triton\backends\intel\include\sycl_functions.h:15:10: fatal error: 'level_zero/ze_api.h' file not found
   15 | #include <level_zero/ze_api.h>
      |          ^~~~~~~~~~~~~~~~~~~~~
1 error generated.

Environment details

Correct, download the latest release for Windows from https://github.com/oneapi-src/level-zero/releases and extract it, for example, to c:\level_zero. Then set environment variable ZE_PATH=c:\level_zero.
Workflow example: https://github.com/intel/intel-xpu-backend-for-triton/blob/win-test/.github/workflows/build-test-windows.yml#L19.
Example run (without tutorials and instrumentation tests): https://github.com/intel/intel-xpu-backend-for-triton/actions/runs/12383767088/job/34567109930.

Thanks for the reply!
Manually downloading the level-zero works great.
May I ask if this is a temporary solution or the next release, we will have level-zero shipped with the driver (which is the same as the behavior of Linux)?


Three links of contributors fixed

Three links of contributors (including mine) that did not have the correct syntax were corrected.

I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added Facebook share and tweet feature to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.


Draft for making styles configurable.

Fix #1509

@crolf Moin, Can you have a look at the ice cloud styles? I do not understand the use of dataname. In case a "different" dataname is used the program will crash because clev was not set. Is this intended?

Moin moin @joernu76, yes that's true. And of course it is not intended to crash the program ;-) The plotting classes where only intended to use for the ice_cloud products. I wanted to avoid to create too many styles. But maybe it would be better to create one plot style for each of the three parameter:

ice_cloud_number
ice_cloud_iwc
ice_cloud_radius
and not to use the dataname if statements.
What do you think ?

Moin moin @joernu76, yes that's true. And of course it is not intended to crash the program ;-) The plotting classes where only intended to use for the ice_cloud products. I wanted to avoid to create too many styles. But maybe it would be better to create one plot style for each of the three parameter:
* ice_cloud_number

* ice_cloud_iwc

* ice_cloud_radius
  and not to use the dataname if statements.
  What do you think ?

Agree. The intent of this change is to move the definition of new styles from MSS core code to mswms_settings.py files such that the list does not grow too large.
I'll prepare a draft.

@ReimarBauer Why isn't Christian's review sufficient?

Why isn't Christian's review sufficient?

github destinguishs between contributor and first time contributor.
crolf has not done yet a MR.
On the first MR of a new user also one of us have to enable the tests
Christian has done code commits on our old home on bitbucket with a different name, https://www.openhub.net/p/mss/contributors?query=christian&time_span=&sort=commits


Emit "use strict" if a prologue only contains "use strict" somewhere inside of it

Fixes the main portion of #7918.

:+1:


stickey keys

I noticed when playing with the keyboard controlled demos that the keys are sticking. I've tried quite a few of the demos on the examples site and can reproduce this every time.
The issue is that the key sticks down after being pressed, if you press more than one key at a time.
For example in the starstruck demo (http://examples.phaser.io/_site/view_full.html?d=games&f=starstruck.js&t=starstruck) if you press and hold the right key to run right, and then press and release the spacebar to jump (keep right arrow pressed), then you can let go of the right arrow and the character will keep running right until the right arrow is pressed and released once more.

I just tested this on OSX 10.10.1, on a Macbook Pro, using Google Chrome 39.0.2171.99.  Was not able to reproduce the sticky keys.

Chrome 41 is not yet stable channel AFAIK, try first in an incognito window (which disables all extensions unless told otherwise) and if the problem persists, probably is a beta bug.

Going to close this one off I'm afraid, as I just re-tested Chrome on OS X with no ill effects, so am thinking it's Canary / device specific.


Uploading Operations cannot be done.

Is your feature request related to a problem? Please describe.

I'm currently using Gradio. When I wanted to start it locally, I have to upload something to the interface. But I couldn't find anything that provides to select files.
Describe the solution you'd like:

There may be something to select files like an OpenFileDialog object.
Thanks in advance! ^^

Hello there,
I am confused about this. Are you trying the in-extension browser to try and debug a web site that needs you to upload something and it doesn't work?

Hello sir, thanks for your quick response.
I have no problem with debugging any of my code. I cannot do image upload or drag events in the interface I run locally. When I press Submit, I cannot select any file, nor can I add any files by dragging.
Here is the screenshot.

As you mentioned, edge tools may not be designed for exactly this kind of functionality. But, I just wanted to let you know.

Ah, thanks, that makes more sense. I will investigate. This could be a problem as the browser embedded is a screencast. Great catch, thank you!

Glad to hear that, have a good day. ^^


feat: simplify and split models/definition/filters files

[x] simplify model files by removing any attributes of the fields that are not strictly required (valueType, value,  ...)
[x] rename properties of default content models to adhere to block naming conventions (field collapsing)
[x] split models/definitions/filters into partials
[x] release the used merge-json-cli to npmjs.org

Each block now has a _component.json partial with a json object that contains definitions, models and filters. Each of them is an array as a block may expose 0..n of either of them. The default content model partials are now stored in models/ as well as the partials for component-models.json, component-definition.json and component-filters.json. The file name format with the leading _ was inspired by sass partials (files that are meant to be imported into other files).
Besides that this commit adds husky pre-commit hook support, with a simple hook that merges the models/definition/filters files if any of the partials changed.

A few suggestions:

I’d rename blocks/cards/_component.json to blocks/cards/_cards.json to be consistent with models/_button.json
I’d rename component-definition.json and _component-definition.json to make it plural: component-definitions.json and _component-definitions.json to make it consistent with component-filters and component models

@jckautzmann

I’d rename blocks/cards/_component.json to blocks/cards/_cards.json to be consistent with models/_button.json

Very good suggestion as this allows

(a) to use autocomplete search and find the .json by name. Currently if you search for components you find a lot.
and (b) allows to split it even further per block like _cards.json and _card.json

I’d rename component-definition.json and _component-definition.json
that would be a breaking change which I would not want to do now. I agree though.

Hi all,
Any ETA when this will be merged? I'm about to migrate a project and would like to know if I should wait a little bit, or just move forward with the current approach.
Thanks.

This will be merged after the next AEM Cloud Services release scheduled for this / next week.
The majority of changes can be used. Unfortunately I made some changes to the default content models (button, title, image) and rename the fields according to our naming conventions so that they can be used in container blocks without any changes. This change is the only thing that requires the AEM CS release. Spitting/merging the files works today.


[WIP] remove dependencies on resumable

closes #2697

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "go-1.11" git@github.com:davidswu/distribution.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

This is great, glad we can use the upstream hash libraries again!
Can you point to the 1.11 change related to http.CloseNotifier? Curious what changed there

@dmcgowan staticchecks was failing the build about it since it is deprecated
Since we can just switch to Request.Context() I opted to clean it up rather than remove the static checks from gometalinter. I can revert the change and remove the checks instead if you think it's too disruptive


chore: revert #12404

Description of changes
Reverts https://github.com/aws-amplify/amplify-cli/pull/12404 since the proposed functionality does not allow more than 1 Amplify app per AWS account.

Issue #, if available

Description of how you validated changes
Checklist

[ ] PR description included
[ ] yarn test passes
[ ] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
[ ] Pull request labels are added

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

Codecov Report

:exclamation: No coverage uploaded for pull request base (feat/replace-lambda-callouts@4ebfa59). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@                       Coverage Diff                       @@
##             feat/replace-lambda-callouts   #12649   +/-   ##
===============================================================
  Coverage                                ?   47.72%
===============================================================
  Files                                   ?      847
  Lines                                   ?    38486
  Branches                                ?     7896
===============================================================
  Hits                                    ?    18366
  Misses                                  ?    18486
  Partials                                ?     1634

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


How can we support multi peer replication with CDTDatastore

How can we support multi peer replication with CDTDatastore
Explanation of the issue
Currently we are able to replicate from the cloud to the iOS devices using the replication which is working fine. Thanks for the wonderful support you guys provided earlier which made it possible and our clients happy.
Now we are doing some experiments around multi peer connectivity framework and replication in between iOS devices which are not necessarily connected to internet but, local wifi network, and for this we need your help with
https://developer.apple.com/videos/play/wwdc2014/709/
https://developer.apple.com/documentation/multipeerconnectivity
https://nshipster.com/multipeer-connectivity/
@tomblench @ricellis Can you please provide your insights?
Environment details

iOS

12

CDTDatastore (and sync-android) were designed to communicate with a remote CouchDB or Cloudant server via the replication protocol. In essence the pull replication source or push replication target must provide the HTTP API endpoints required by the CouchDB replication protocol. There is no functionality built-in to the libraries for exposing these HTTP endpoints nor do we have plans to add this capability. Replication via alternative non-HTTP protocols is completely out of scope.

K thanks for the quick reply, is there a way to create a duplicate copy of a doc in datastore if say we get it from another source  E.g. (a socket event etc.) and we manually insert it into a datastore the same exact replica of the doc with it's revision history intact ?
Just to be clear, we don't want to exactly create a new revision, to avoid document conflicts later on however we do need to be able to create an exact replica doc from one datastore to another by manually inserting it into the datastore.
Can you provide something like a copy function as outlined in the couchdb docs ?
https://couchdb-13.readthedocs.io/en/latest/api/documents/#copying-from-a-specific-revision
Also, I do remember the android version of the library having a forceInsert API for the datastore but, the same is not exposed in CDTDatastore.
Can you please advice on the risks involved if any or any other alternatives?

is there a way to create a duplicate copy of a doc in datastore if say we get it from another source E.g. (a socket event etc.) and we manually insert it into a datastore the same exact replica of the doc with it's revision history intact ?

I don't think so, the library's replicator inserts revision history via TD_Database's forceInsert, but I don't think this internal API is accessible.

Can you provide something like a copy function as outlined in the couchdb docs ?

CouchDB's COPY {db}/{doc} doesn't preserve any revision history, so I don't think this is what you want.

Also, I do remember the android version of the library having a forceInsert API for the datastore but, the same is not exposed in CDTDatastore.

Correct, in response to a feature request we reluctantly exposed an advanced Database interface with a createWithHistory API.

Can you please advice on the risks involved if any or any other alternatives?

As I said this is outside the scope of what the library was intended for and beyond what we have tested (or will test) so is always likely to be brittle. There are, I think, three possibilities:

You provide an HTTP API that the library replicator can pull from. This is low-risk from the library perspective as it will be treated as any other replication source, assuming the HTTP API honours the CouchDB replication protocol.
You open a PR or make a feature request for adding an advanced CDTDatastore API with createWithHistory similar to what was done for sync-android. This is much riskier because the interaction of additional forceInsert operations on the device DB outside the remit of the existing replicator is unknown territory. Full disclosure - a feature request for this would not be high on our priority list.
In the special case where the document does not exist in the local datastore you could send and insert the revs in order to recreate the tree, but I think this is almost uselessly fragile.

I don't think there is another alternative if you want to maintain the revision history.

Ok, thanks for your inputs, let me discuss this with my team, will get back to you if any further help is needed.


Enhancement Request: Add ability to exclude edges when pinning to any constrainable

Right now, you can do this:
someView.edgesToSuperview(excluding: .bottom)

And you can do
someView.edges(to: anotherView.safeAreaLayoutGuide)

But you can't do what I'd like to be able to do, which is:
someView.edges(to: anotherView.safeAreaLayoutGuide, excluding: .bottom)

Would it be possible to add an optional excluding parameter for any Constrainable.edges(to: call?

+1

I added this now in 3.2.0. ✌


Run Jenkins as non-root user

I want to run Jenkins with non root user.
how can I do that?

This should help me?

Hi, @m3llo96 - This repo is being archived and no help is available here.
You may want to look at https://github.com/jenkinsci/helm-charts, which is active and more likely to have people who can help with Jenkins & Helm questions. Thanks.


Cannot get home-manager setup to work

Hey,
I'm kind of in the same situation as described in issue #26, first time using an external flake in my Nix config.
I'm failing to adapt the NixOS example in the Readme to the Home-manager-only case. Here's what I have:
    ...
    nixosConfigurations = {
      my-machine = nixpkgs.lib.nixosSystem {
        system = "x86_64-linux";
        modules = [
          ./configuration.nix
          home-manager.nixosModules.home-manager
          {
            home-manager.useGlobalPkgs = true;
            home-manager.users.auguste = import ./home.nix;
          }
          xremap.homeManagerModules.default
          {
            services.xremap = {
              config = {
                modmap = [
                  {
                    name = "Global";
                    remap = {"CapsLock" = "Esc";}; # globally remap CapsLock to Esc
                  }
                ];
              };
            };
          }
        ];
      };
    };
    ...

where I just replaced inputs.xremap-flake.nixosModules.default with xremap.homeManagerModules.default (as I named the flake input xremap) and removed all the options that were causing "unknown option" errors. Now the error I get is:
   error: The option `systemd.user.services.xremap.Install' does not exist. Definition values:
       - In `/nix/store/.../homeManagerModules':
           {
             WantedBy = [
               "graphical-session.target"
             ];
           }

Any idea what could be causing this? Am I even using this flake output correctly?
Thanks in advance for any feedback :)

The error you're getting:

The option `systemd.user.services.xremap.Install' does not exist. Definition values:

happens because home manager has a different systemd services syntax compared to NixOS modules. In NixOS a service would look like this:
{
  systemd.user.services.foo = {
    description = "Foo" # This turns into the service description
    # Some other service fields have a top-level option here
    serviceConfig = {
        # unit settings  go here
        ExecStart = "hello";
    };
  };
}

whereas on home manager:
{
    systemd.user.services.foo = {
        # all unit settings go here
        ExecStart = "hello";
    };
}

In the config you provided you're using home manager module as a "system"-level module.
You could get this flake to work in two ways:

Use nixosModule:

Replace xremap.homeManagerModules.default with xremap.nixosModules.default
Add userName (like here), depending on the features specify with* and set serviceMode (see the matrix in README)

Import homeManager module in the context of your user

Remove top-level import of xremap.homeManagerModules.default

Remove top-level import of the xremap settings

Replace home-manager.users.auguste = import ./home.nix; with something along the lines of:
{
    home-manager.users.auguste = {
        imports = [
            ./home.nix
            xremap.homeManagerModules.default
            {
                services.xremap = {
                  config = {
                    modmap = [
                      {
                        name = "Global";
                        remap = {"CapsLock" = "Esc";}; # globally remap CapsLock to Esc
                      }
                    ];
                    # other xremap settings go here
                  };
                };
             }
        ];
    };
 }


The update_activity python documentation contains errors and no samples for update_activity

The current documentation on update_activity for python contains errors and so isnt directly usable without modification, further the referenced example of update_activity is focused on updating a card activity but doesent actually give a example of updating a regular message factory. This would be useful as currently im struggling to find an answer to "error unknown" as a resulting response and it would help to reduce the confusion if the samples were actually functional and demonstrated the API's usage correctly.
# Send initial message
message = await turn_context.send_activity("<Your Message>")
activityId = message.id # Fetch activity id.

# MessageFactory.Text(): Specifies the type of text data in a message attachment.
new_activity = MessageFactory.text("The new text for the activity")
new_activity.id = activity_id

# A method that can participate in update activity events for the current turn.
update_result = await context.update_activity(new_activity)

An error occurred while updating the activity: (ServiceError) Unknown
context seems like it should be referencing turn_context which would be consistent with other examples however as mentioned this sample does not work for me as update_activity always results in a error: unknown. Further the activity_id seems to reference the variable defined previously activityId, so in short this is a confusing example and I cant get the code to function even if i imply that the error is caused by these mistakes i get an ambiguous error unknown message.

Hello @DeanHnter - Thanks for raising your query.
Could you please share the doc link that you are following including the sample, if you are referring?
Also, please let us know what exact version you are using for Python?

Hello @DeanHnter - Thanks for raising your query. Could you please share the doc link that you are following including the sample, if you are referring? Also, please let us know what exact version you are using for Python?

Hi thanks for looking into it. Here is the link to the original document and the python version is 3.11
https://learn.microsoft.com/en-us/microsoftteams/platform/bots/how-to/update-and-delete-bot-messages?tabs=dotnet

facing the same issue in update activity. any updates ?

facing the same issue in update activity. any updates ?

Looks like the referenced ticket isn't addressing the same issue (superficially) here so not sure if we will see a fix soon Expecting that moving to c# implementation would be easier than waiting on a fix at this point.

@DeanHnter , we are actively working on this and will let you know the updates.

Hello @DeanHnter ,
We got an update from the sample team that using below code we will be able to update regular message and also the adaptive card.
Send initial message
message = await turn_context.send_activity("")
activityId = message.id # Fetch activity id.
MessageFactory.Text(): Specifies the type of text data in a message attachment.
new_activity = MessageFactory.text("The new text for the activity")
new_activity.id = activity_id
A method that can participate in update activity events for the current turn.
update_result = await context.update_activity(new_activity)

Hello @DeanHnter ,
We got an update from the sample team that using below code we will be able to update regular message and also the adaptive card.
message = await turn_context.send_activity("")
activityId = message.id # Fetch activity id.
new_activity = MessageFactory.text("The new text for the activity")
new_activity.id = activity_id
update_result = await context.update_activity(new_activity)

Hi thank you for the feedback. Unfortunately the problem hasn't been addressed in any direction.

I update the packages and fixed the code provided, and I still received an unknown error response as outlined in my original issue.
The sample provided as outlined in my original response still won't work and will never work. It contains obvious errors that even the worst AI or even IDE could point out yet apparently the sample team cannot even detect. It's very clear either activity_id should actually be the variable activityId or there is another variable that isn't clearly outlined at play in this example.

I cannot recommend anyone actually use this library until the basic functionality actually works and samples that are coherent are produced, it makes no sense that this is the response.

@DeanHnter ,
We will again look into this on priority basis and let you know the updates asap.

@Vaibhav-MSFT  any updates on this? facing the same issue

@sethteo - Apologies for the delay, we will check this and update you soon.

Any updates?

I am closing this issue. It seems resolved either by upgrading to a newer version of python or by upgrading to the latest (4.16.1) version of bot-builder. Either way for me it now works, the documentation however is still not updated and still contains the incorrect variable names as previously outlined. I no longer care to keep this issue/discussion open as its clear microsoft employees arent capable. I would still recommend migrating to another solution for anyone encountering this issue.


Update IoTHubClient_LL_DoWork frequency recommended value

Usually we recommend running IoTHubClient_LL_DoWork every one hundred milliseconds, not every second.
The sample should reflect that recommended value.

@ewertons : Thanks for your contribution! The author, @yzhong94, has been notified to review your proposed change.

This change is approved.  #sign-off


Bug - F401 Unused imports in Jupyter Notebook breaks shell commands

Hello!
First of all, thanks for the great tool!
Inside notebooks (e.g., Google Colab), it is very common, and recommended, to run pip install Python packages by linking to the appropriate Python executable, which hence needs sys.executable, see code snippet below.
However, Ruff will not detect that sys is needed in the shell command (with !) and will remove the import sys line, which will ultimately break the notebook.
Without --fix, the output is:
notebook.ipynb:cell 2:7:12: F401 [*] `sys` imported but unused

Keywords: "Ruff", "F401", "Jupyter", "Notebook", "unused import", "shell command".
Minimal code snippet:
try:
    import package  # noqa: F401
except ImportError:
    import sys
    !{sys.executable} -m pip install package

A temporary fix is to add disable this check on import sys:
try:
    import package  # noqa: F401
except ImportError:
    import sys  # noqa: F401
    !{sys.executable} -m pip install package

While this fix is fine, I had to learn it the hard way, as the unused-import fix is considered stable and will not warn you about this if you directly run with --fix.

Same type of issue as #8094.

Indeed @tdulcet, couldn't find it :-)

👍 I'm going to combine with #8094. Thanks!


Add Functional Tests for AAD 3.3v1

💡 Summary
To fully close issue #410, need to complete the functional test cases to improve automated testing features.
What is the work, as a high-level summary?
Motivation and context
MS.AAD.3.3v1 requires checks on the Microsoft Authenticator MFA login user context settings to help protect the tenant when phishing resistant MFA has not been enforced and Microsoft Authenticator is used. The functional unit tests should check for various combinations of these settings to ensure that pass/fail conditions are being successfully met by the Rego code.
Implementation notes
Run Functional Unit Tests
Acceptance criteria
How do we know when this work is done?

[ ] Functional tests are passing

Was completed as part of PR #1014


Allow end to end flow for new brief responses

Part of this story on Pivotal https://www.pivotaltracker.com/story/show/129843611.
This PR is a small update to the supplier frontend which allows the new style brief-responses to work end to end. Without it, new style brief responses would cause the app to fall over after submission.
There is a check made when viewing the response result that all of the essentialRequirements are True. The new style brief responses do not have this key, instead it they have essentialRequirementsMet which is just a boolean. This PR makes the app check if this new key exists and if it's True, before checking the original essentialRequirements key.

If a user visits the incorrect flow should we redirect or should we 404? I'd personally lean towards 404 but could go either way. I don't know if we have any precedent of this in our apps?

Yeah, it's a good point. Part of me thinks that it'd be more helpful to redirect, but on the other hand a user would need to manually change the URL before they experience the 'help', so perhaps a 404 is better.
@tombye, what are your thoughts?

I think it's a 404 too. The URLs we'd redirect have/will have never existed for those briefs so my feeling is we shouldn't enable their use or at least support it with a redirect.

Cool. I've chucked another commit in which 404's instead of redirecting.

Might need to do similar how we have with the API and check if a feature flag is off then the redirect code does what we want it to

Good shout. If the flag was set to False/not set it was causing a type error when using the /create route. Have updated and added a couple of tests.

Should be good after a rebase and tests pass 👍


One field from the table is not uploaded to ES

My pgsync config
[
    {
        "database": "clients",
        "index": "issues",
        "nodes":
        {
            "table": "issues",
            "schema": "public",
            "columns":
            []
        }
    }]

this is table ddl
create table issues
(
    id               uuid                                                        not null
        primary key,
    created_at       timestamp with time zone default CURRENT_TIMESTAMP          not null,
    updated_at       timestamp with time zone default CURRENT_TIMESTAMP          not null,
    home_device_id   uuid
        constraint fk_issues_clients__83bc2d24
            references clients_home_devices
            on delete restrict,
    client_id        uuid                                                        not null,
    description      text,
    status           varchar(50)              default 'new'::character varying   not null,
    help_type        varchar(50)              default 'video'::character varying not null,
    worker_id        uuid,
    livetime         integer,
    cancel_comment   text,
    card_id          uuid,
    oid              bigserial,
    bo_status        varchar(50)              default 'new'::character varying   not null,
    address_parts_id uuid
        unique
);

the problem is, oid is not uploaded to elastic. How can I fix that?

oid is a system column? Did you try including it explicitly in your columns list?

nope
now, I've added it explicitly, everything is fine now, thanks


Uncaught TypeError: this.con.DoCommandAsync is not a function

I encounter this problem in Atom whenever I shut down Stata while Atom is open. It cannot be solved by reopening Stata but restarting Atom.
[Enter steps to reproduce:]

...
...

Atom: 1.24.1 x64
Electron: 1.6.16
OS: Microsoft Windows 10 Pro
Thrown From: stata-exec package 1.4.3
Stack Trace
Uncaught TypeError: this.con.DoCommandAsync is not a function
At C:\Users\liqia\.atom\packages\stata-exec\lib\stata-exec.js:203

TypeError: this.con.DoCommandAsync is not a function
    at Object.sendCode (/packages/stata-exec/lib/stata-exec.js:203:20)
    at Object.sendCommand (/packages/stata-exec/lib/stata-exec.js:147:10)
    at HTMLElement.subscriptions.add.atom.commands.add (/packages/stata-exec/lib/stata-exec.js:92:45)
    at CommandRegistry.handleCommandEvent (~/AppData/Local/atom/app-1.24.1/resources/app/src/command-registry.js:388:36)
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (~/AppData/Local/atom/app-1.24.1/resources/app/node_modules/atom-keymap/lib/keymap-manager.js:621:22)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (~/AppData/Local/atom/app-1.24.1/resources/app/node_modules/atom-keymap/lib/keymap-manager.js:412:28)
    at WindowEventHandler.handleDocumentKeyEvent (~/AppData/Local/atom/app-1.24.1/resources/app/src/window-event-handler.js:108:40)

Commands
  2x -0:27.7.0 stata-exec:send-command (input.hidden-input)

Non-Core Packages
atom-python-run 0.9.6
atom-runner 2.7.1
autocomplete-python 1.10.5
busy-signal 1.4.3
copy-on-select 0.2.0
file-icons 2.1.17
highlight-selected 0.13.1
Hydrogen 2.3.0
intentions 1.1.5
language-stata 1.3.1
linter 2.2.0
linter-flake8 2.3.0
linter-ui-default 1.7.1
material 2.2.0
minimap 4.29.8
minimap-highlight-selected 4.6.1
python-autopep8 0.1.3
script 3.17.3
stata-exec 1.4.3
Visual-Studio-2015-Dark-Theme 2.4.2
visual-studio-code 0.4.0
visual-studio-dark-syntax 0.2.0

I also found that it is unable to run more than one Stata programs simultaneously. I can only run one do file in atom at a time. If I open the first do file and then clear everything in stata, then start to run the second do file, which began with “use”. Then stata will return 601 error, the file was not found. I have to restart Atom and open the second do file to run it.
Is this caused by the desige of the package? Or something to debug?


Allow non-stringly typed table properties

Feature Request / Improvement
Currently table properties like write.parquet.compression-level need to be stringly typed in PyIceberg. Should we allow for other types as well?

@jonashaag Can you give an example? Table properties are encoded as strings by default.

See the example in my post. The pydantic Schema doesn't allow for non strings currently

But we convert it to an int when setting the level?

Do you think we should automatically convert them to a string if safe? It is just really awkward to set eg the compression level as a string

Yes, that's what we are doing here:
https://github.com/apache/iceberg-python/blob/853a77c5d24280a1048ebcef9a9bfe0cedb642ca/pyiceberg/io/pyarrow.py#L1766-L1773

It is just really awkward to set eg the compression level as a string

It is a string map, so I don't think we have any other options.

convert them to a string

The code you are showing converts them from a string.
I meant the other end:
create_table(..., properties={"write.parquet.compression-level": 42})

@jonashaag Ahh, thanks, it already felt like I was missing a piece. We should accept everything that can coerce into a string. I like to follow the idea of being liberal in what you accept and being strict when writing.

@jonashaag is this something that you're interested in contributing? :)

@jonashaag this should work now!


API Key authorization errors when integrating with API Umbrella 0.11

Since experimenting with API Umbrella 0.11, we have encountered several errors related to the API Umbrella user API Key not being authorized to perform certain functions. For example, when setting up a new developer environment, we create an API Umbrella superuser and API Key, but the API Key is not authorized to create new users on API Umbrella.
Steps to reproduce

Log in to API Umbrella (0.11 @ nightly.umbrella.apinf.io)
Go to Users -> Admin Accounts
Create a new admin user

check 'superuser' box

Go to Users -> API Users
Click 'Add New API User'
Create new API user with same email as admin user

Under Permissions -> Roles, add api-umbrella-key-creator

Sign-in with new Admin user
Get API Key and Admin API Token for new user
Add API Key and Admin API Token to settings.json
Launch Apinf
Register a new user

Observed behavior
When registering a new user, the screen displays an Internal server error message. In the server console, the following error appears:
Exception while invoking method 'ATCreateUserServer' Error
     at new ApiUmbrellaError (packages/brylie_api-umbrella/server/apiUmbrellaError.js:33:1)
     at Object.self.adminApi.v1.apiUsers.createUser (packages/brylie_api-umbrella/server/apiUmbrellaWeb.js:275:1)
   ...

The main issue is related to the following line Object.self.adminApi.v1.apiUsers.createUser (packages/brylie_api-umbrella/server/apiUmbrellaWeb.js:275:1, where we are trying to create an user on API Umbrella. FWIW, that part of our integration code hasn't changed since 12 November 2015.
Related

See issue #217 on API Umbrella backlog
Related issue on nightly #893

@jykae please use this issue to track the integration errors.

@bajiat lets use this issue to track the recent API Umbrella 0.11 integration errors.

@brylie Ok, thanks! Shall we assign this to @jykae?

@jykae will you please self-assign?

assigned and in progress

This seems to happen only in nightly as nightly.umbrella has been reinstalled and is down. I successfully registered new user on apinf.io

@jykae please follow the steps to reproduce after installing a fresh API Umbrella 0.11 instance. We were getting the errors on the previous 0.11 installation.
Also, be sure to test with newly created users.

@Alapan @saralavanip Once this bug is fixed, you can continue with your tasks.

We are rolling back nightly Umbrella to previous state and testing that the key rights are correct.

This was related to wrong settings in nightly.apinf.io Giving settings.json on deployment command did not override the existing Settings object in DB. I got in with my old account that existed on nightly and changed settings to point nightly Umbrella and verified that registration works now.

@Alapan @saralavanip please let me know if you are able to register now to nightly. @brylie was also able to do it so nightly registration should work now I think this can be closed then.

@jykae Yes I was able to register now.

@jykae However, I am still unable to login/register on my local application. I tried git pull in the api-umbrella-dashboard, but it appears no changes were made there. Do I have to change any file to make it work on my localhost application?
The error on the server console is still the same:
Exception while invoking method 'ATCreateUserServer' TypeError: Cannot read property 'length' of null

Worked the settings file together via chat. @Alapan verified that local development works now against nightly Umbrella.

Great work @jykae :-)

Thanks for solving the issue @jykae
2016-03-02 10:36 GMT+02:00 Brylie Christopher Oxley <
<EMAIL_ADDRESS>
Great work @jykae https://github.com/jykae :-)
—
Reply to this email directly or view it on GitHub
https://github.com/apinf/api-umbrella-dashboard/issues/899#issuecomment-191128384
.

--
Taija Björklund
p. 040 5177 969
<EMAIL_ADDRESS>www.linkedin.com/in/taijabjorklund

@jykae , Verified and was successful in Sign up/ Register on https://nightly.apinf.io

@jykae Sign In/Register was working correctly in the local environment.


ci: change to use GitHub actions

Which issue(s) this PR fixes:
https://github.com/longhorn/longhorn/issues/8039
What this PR does / why we need it:
Special notes for your reviewer:
Additional documentation or context

@FrankYang0529
Can you help check

/home/runner/_work/_actions/codecov/codecov-action/v4/node_modules/@actions/io/lib/io.js:213
                    throw new Error(`Unable to locate executable file: ${tool}. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.`);
^
Error: Unable to locate executable file: git. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
    at Object.<anonymous> (/home/runner/_work/_actions/codecov/codecov-action/v4/node_modules/@actions/io/lib/io.js:213:1)
    at Generator.next (<anonymous>)
    at fulfilled (/home/runner/_work/_actions/codecov/codecov-action/v4/node_modules/@actions/io/lib/io.js:24:1)

Hi @derekbit, I install git and resolve the error. However, there may have flaky test. I can't finish Build AMD64 binaries at the first try, but it pass at the second try.

https://github.com/longhorn/longhorn-spdk-engine/actions/runs/9576741080/attempts/1
https://github.com/longhorn/longhorn-spdk-engine/actions/runs/9576741080/attempts/2

For Build ARM64  binaries, test cases are always failed.

Hi @derekbit, I install git and resolve the error. However, there may have flaky test. I can't finish Build AMD64 binaries at the first try, but it pass at the second try.

https://github.com/longhorn/longhorn-spdk-engine/actions/runs/9576741080/attempts/1
https://github.com/longhorn/longhorn-spdk-engine/actions/runs/9576741080/attempts/2

For Build ARM64 binaries, test cases are always failed.

Weird. No issues in the local environment.

I might know the reason of the failure.
spdk_test.go:78:
    c.Assert(err, IsNil)
... value *errors.fundamental = timeout executing: /usr/bin/c [nsenter --mount=/proc/1/ns/mnt --ipc=/proc/1/ns/ipc --net=/proc/1/ns/net sh -c /usr/src/spdk/build/bin/spdk_tgt  --logflag all 2>&1 | tee /tmp/spdk_tgt.log] ("timeout executing: /usr/bin/nsenter [nsenter --mount=/proc/1/ns/mnt --ipc=/proc/1/ns/ipc --net=/proc/1/ns/net sh -c /usr/src/spdk/build/bin/spdk_tgt  --logflag all 2>&1 | tee /tmp/spdk_tgt.log]")

spdk_tgt is running on foreground. If nsenter... cannot return within 60 seconds, it will error out.

We can merge the PR. The ARM64 isn't related to the CI, and I will check it.


DMC Kanye is pinned to Capybara 2.4.4

Because DMC Kanye duck-punches Capybara, it is necessarily pinned to specific versions of Capybara, e.g. 0.0.1 is pinned to Capybara 2.4.4.
If version 0.0.1 is compatible with more versions of Capybara, we should loosen the restriction to allow users to use more-current versions of Capybara (or less-current versions if necessary).
If newer versions of Capybara mess with Kanye's flow, we should tweak Kanye (and release a new version) to support them.

#5 also addresses this. When these two changes are tagged, we should have versions of Kanye supporting Capybara 2.4.0 and up; if we need to support older versions, we'll address that when it happens.

With #4 merged to master and #5 tagged as v0.0.2 (and v0.0.3) this is "fixed" (supported Capybara versions are still limited, but the pool is bigger).


Send message with function

Hi ! Thank's for your work !
I'm wondering if there is a way to send a message directly with a function without using the chat (for Android and iOS) ?

As I know, we can use a backend that integrates with crisp api to handle it.

@stephoune the crisp API docs can be found here https://docs.crisp.chat/api/v1/#top. Also you could post the same question on the crisp chat ios sdk repo (https://github.com/crisp-im/crisp-sdk-ios)

@stephoune the crisp API docs can be found here https://docs.crisp.chat/api/v1/#top. Also you could post the same question on the crisp chat ios sdk repo (https://github.com/crisp-im/crisp-sdk-ios)


Fixes #82 webp support

Does this provide a fallback for browsers that don't support the webp option? I am wondering this because I myself and 60% of my users use Firefox Quantum and Firefox Quantum Developer Edition, and while I would like to have webp, I am wondering if this is a addon to the current format or would this replace the entire format.

@rouing  is this blocking the merge?

@rouing As coded, this is a committed choice - Dynmap only renders a given map in a single image file format, so opting for 'webp' will result in the given map being rendered in that single format (and, thus, breaking anyone that has a browser that lacks support).  I'll be accepting the PR, but as I'd indicated in the conversation on the issue requesting the support (#82), it will not be a recommended nor particularly supported choice, as I don't think the improvement in the image size is justified versus the impact due to incomplete browser support - if you want smaller maps, use the existing jpeg format vs the default png format, and you'll get nearly all the size improvement.  Dynamically reencoding the webp to one of those formats isn't going to happen - it'll kill server performance, and would be a real problem for external server users (where the image files are directly served as files, versus being served via custom code), and encoding the map twice (once for webp and once for some other format) completely defeats any point in having the webp support.

@bmhm Code is not building properly, as the com.google.webp library is not being found on the maven central repository.  Where did you get it from?  I need a supported and open source reference from a trusted source, or else I'll need to drop the merge.

I have no idea anymore. It's been a while... Did you Google for it? I do not have an IDE at the moment.


Relax oppressive rules

Using this issue to keep a track of rules that should be removed because they are overly oppressive.
ESLint:

prefer-const

TSLint:

prefer-const
jsx-no-lambda
only-arrow-functions
jsx-no-multiline-js
no-shadowed-variable

TSLint:

no-floating-promises conflicting with mongoose projects

Fixed by #16


[Bug Report] Refresh my schedule

Problem
It's not bug, but it might be better to implement refresh feature on my schedule.

Sounds good.

I'm gonna close this issue cuz it's an unnecessary specification.


Switch missing

I just freshly installed luci, but the switching section under network ist missing.
Thanks for any help.
OpenWrt Chaos Calmer 15.05
LuCi git-15.276.51144-8832d53
Linksys WRT1900ACS
Let me know if you need further information. I'm totally new to OpenWrt/LuCI/Linux in general.

Try the following on the console:
uci add network switch
uci set<EMAIL_ADDRESS>uci set<EMAIL_ADDRESS>uci set<EMAIL_ADDRESS>uci add network switch_vlan
uci set<EMAIL_ADDRESS>uci set<EMAIL_ADDRESS>uci set<EMAIL_ADDRESS>1 2 3 4 5"
uci commit network
reboot

Thank you for your response. I will try that at the weekend. At the moment I already switched back to the original firmware.

No additional comment for 10 months, closing.


Alternative physics engine: Nvidia PhysX

With this issue I want to collect some resources and assess whether there's any interest from the community to provide support to Nvidia Physx.
Historically, Gazebo Classic supported ODE, bullet, DART, and simbody. In these past weeks, I noticed some new movement in the custom branches for implementing bullet, and this is great. For what concerns ODE and simbody, there's already a ticket open https://github.com/ignitionrobotics/ign-physics/issues/63.
Nvidia Physx has been open-sourced "recently". It is Nvidia's choice for their Isaac Sim simulator and I expect a bright future for this engine. One of the notable features is the possibility to simulate physics on GPUs, allowing to scale a simulation to hundred or thousands of models.
I'd be super excited to see anything similar running in Gazebo. I've just found rumors about a new major release https://github.com/NVIDIAGameWorks/PhysX/issues/309#issuecomment-665751081.

That would be exciting. Just wearing my personal hat, not representing any organization (where's my GitHub account number 2). PhysX's deformable object demo is really cool. I've seen limited robotics applications using it. Do you have a short list of robotics applications you've seen (that isn't NVIDIA's own promo)? I'm wondering about the physics fidelity. Issac was something I kept an look out for a few years ago.

That would be exciting. Just wearing my personal hat, not representing any organization (where's my GitHub account number 2). PhysX's deformable object demo is really cool. I've seen limited robotics applications using it. Do you have a short list of robotics applications you've seen (that isn't NVIDIA's own promo)? I'm wondering about the physics fidelity. Issac was something I kept an look out for a few years ago.

I've just found rumors about a new major release NVIDIAGameWorks/PhysX#309 (comment).

FYI there has been a follow up on this: https://github.com/NVIDIAGameWorks/PhysX/issues/371#issuecomment-756794998 .
TL;DR: Unfortunately the focus of the PhysX team switched from the open source C++ SDK for integration with other tools to the use of PhysX in Nvidia Omniverse so while they are working on it, it is not a priority and they don't have a release scheduled yet.

I've just found rumors about a new major release NVIDIAGameWorks/PhysX#309 (comment).

FYI there has been a follow up on this: https://github.com/NVIDIAGameWorks/PhysX/issues/371#issuecomment-756794998 .
TL;DR: Unfortunately the focus of the PhysX team switched from the open source C++ SDK for integration with other tools to the use of PhysX in Nvidia Omniverse so while they are working on it, it is not a priority and they don't have a release scheduled yet.

I missed that follow up, good catch @traversaro. It's a shame the SDK got delayed. As commented in the original issue, not much system integration seems possible from Omniverse.
@mabelzhang not really, I was impressed as well from their results, but then I couldn't find many third-party projects using PhysX. Here below few links I found in my starred projects:

https://github.com/petrikvladimir/pyphysx
https://github.com/Unity-Technologies/marathon-envs
https://github.com/YunzhuLi/PyFleX

A while ago I tried to have a look to PhysX, but I found it difficult to import the SDK in an external project, see https://github.com/NVIDIAGameWorks/PhysX/issues/208 and https://github.com/NVIDIAGameWorks/PhysX/issues/249. There is an external contribution that didn't get much interests from upstream https://github.com/NVIDIAGameWorks/PhysX/pull/222.
Up to today, I think that vcpkg/ports/physx is a reasonable solution to install PhysX if anyone wants to have a look. As reported in https://github.com/microsoft/vcpkg/pull/13849, there no GPU support yet, but it can be a good starting point.

I missed that follow up, good catch @traversaro. It's a shame the SDK got delayed. As commented in the original issue, not much system integration seems possible from Omniverse.
@mabelzhang not really, I was impressed as well from their results, but then I couldn't find many third-party projects using PhysX. Here below few links I found in my starred projects:

https://github.com/petrikvladimir/pyphysx
https://github.com/Unity-Technologies/marathon-envs
https://github.com/YunzhuLi/PyFleX

A while ago I tried to have a look to PhysX, but I found it difficult to import the SDK in an external project, see https://github.com/NVIDIAGameWorks/PhysX/issues/208 and https://github.com/NVIDIAGameWorks/PhysX/issues/249. There is an external contribution that didn't get much interests from upstream https://github.com/NVIDIAGameWorks/PhysX/pull/222.
Up to today, I think that vcpkg/ports/physx is a reasonable solution to install PhysX if anyone wants to have a look. As reported in https://github.com/microsoft/vcpkg/pull/13849, there no GPU support yet, but it can be a good starting point.

There is interest from my side and the research institute (robotics) I am working for, too. We are currently working (mostly) with the good old Gazebo (minus ignition). Switching to Nvidia Isaac Sim just because of PhysX is not really what we want at this point, eventho I found it pretty nice to work with its at a very early stage and makes you kindof dependent on the Nividia eco-system. So pushing forward Ignition along with PhysX is definitly something we would appreciate and I could offer to participate in the integration

On the PhysX side, it sounds like the starting point is the vcpkg link above. I haven't tried to install it.
On the Ignition side, there's a recent effort to integrate the Bullet engine, which might give some good pointers to what's needed to hook things up https://github.com/ignitionrobotics/ign-physics/pull/208

I too would like to contribute in some manner, is anyone working on this at present? In the opinion of you all, will 5.0 be easy to port to once it releases? and since the 5.0 release timeline is uncertain, if one has to work on this, going forward with 4.1 integration in the meanwhile seems to be a sound choice right?

is anyone working on this at present?

Open Robotics currently has no plans to work on this, but we welcome pull requests. The plugin could also be implemented in a separate repository and does not need to be included into this one.

will 5.0 be easy to port to once it releases? and since the 5.0 release timeline is uncertain, if one has to work on this, going forward with 4.1 integration in the meanwhile seems to be a sound choice right?

I assume you mean Ignition Physics 5.0? We just released 4.0 with Ignition Edifice. At the moment, we can't say for sure whether 5.0 will be included into Ignition Fortress, coming up September 2021, or if that's going to use 4.x. Whether we bump the version or not will depend on whether breaking changes are needed until then, and we usually make this decision in the middle of the development cycle.
In any case, adding support to a new physics engine should be possible against any existing stable release. I would suggest you target Ignition Physics 2.X, which is the version used in the current LTS, Citadel.

Might be talking about NVIDIA PhysX 5.0, which was supposed to be released in 2020 but still isn't :sweat_smile:
https://github.com/NVIDIAGameWorks/PhysX/issues/309#issuecomment-665751081


feat: Include site level metrics in the CWV response (Projected Traffic Value)

…
Please ensure your pull request adheres to the following guidelines:

[ ] make sure to link the related issues in this description
[ ] when merging / squashing, make sure the fixed issue references are visible in the commits, for easy compilation of release notes

Related Issues
https://jira.corp.adobe.com/browse/SITES-26928
Thanks for contributing!

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

v1.42.0
GitHub release

Your semantic-release bot :package::rocket:


Review starter kits and check that asset importing guidance is correct

current guidance may be out of date: https://github.com/LBHackney-IT/lbh-frontend/blob/main/docs/developing/installing-from-npm.md
starter kits do it in different ways: https://github.com/LBHackney-IT/hackney-design-system-examples/

updated


Issue: Fix Integration test test_mailbox_evm_to_strk

This PR fix the current integration tests that stop working after the the refactor of the contracts in this commit https://github.com/astraly-labs/hyperlane_starknet/commit/6ef5aa2e0fd1b3491e27f37e18e08bec35c36d00
Solve issue: #26

Add  Bytes, Message from multisig_ism.
Fix the deploy_multisig by  replacing the .setValidators  and calling the verify(&metadata, &message)  at the end of the test.
Fix the send_msg_strk_to_evm by adding the missing paramter of mailbox,dispatch. Err [E0599].

Hey, apparently the integration tests fail. Furthermore, we might not want to verify a mesage inside the deployment section.


OLS-459: mark all unreachable URLs in the output and fail if any are found

A follow-up to https://github.com/openshift/lightspeed-rag-content/pull/9
The generate_embeddings.py script now keeps processing if unreachable docs URLs are found, but marks them with UNREACHABLE in the log and exits with an error and exit code 1.
file_path: /workdir/ocp-product-docs-plaintext/4.15/applications/working_with_helm_charts/odc-working-with-helm-releases.txt, title: Working with Helm releases, docs_url: https://docs.openshift.com/container-platform/4.15/applications/working_with_helm_charts/odc-working-with-helm-releases.html, UNREACHABLE
file_path: /workdir/ocp-product-docs-plaintext/4.15/applications/working_with_helm_charts/understanding-helm.txt, title: Understanding Helm, docs_url: https://docs.openshift.com/container-platform/4.15/applications/working_with_helm_charts/understanding-helm.html, UNREACHABLE
There were documents with unreachable URLs, grep the log for UNREACHABLE
Error: building at STEP "RUN python generate_embeddings.py -f ocp-product-docs-plaintext/${OCP_VERSION} -md embeddings_model     -mn ${EMBEDDING_MODEL} -o vector_db/ocp_product_docs/${OCP_VERSION}     -i ocp-product-docs-$(echo $OCP_VERSION | sed 's/\./_/g') -v ${OCP_VERSION}": while running runtime: exit status 1

/lgtm
/approve


This is not an issue, I'd just like to point it out.

Your learn git branching app was used by the CIA.


Pre-selected Option in Multiselect component [Question]

Hello, I need to preselect an option in a MultiSelect component.
Options have the following format
options: [ {label: "Label 1", value: Object1}, {label: 'Label 2: value: Object}, ...]

I've tried to put my preselected option in the selection binding array
this.selection.push(Object)

but the Multiselect display [object Object] value as Label.
Screenshot

How can I set correctly a pre-selected option?
Thank you for your help

You need to push the value into your selected array. If the value is an object, make sure that you're pushing the same reference of it.
Here is a demo: https://codepen.io/wxsm/pen/ZEOBLqK

I confirm that's what I expected.
Thank you @wxsms :-)

welcome.


Last line isn't highlighted when undoing

If the last line is deleted, undoing this action won't highlight the last line.
https://github.com/tzachar/highlight-undo.nvim/assets/84649544/83465f21-84e5-46f8-97ac-62c557f5870d
Looking at the code, I suspect it's an upstream bug, but I'm not sure. Any thoughts?

Thanks for the quickfix!


Release Components Documentation

As a user of the SDP I want to know for every platform release:

What components are included (at the application level)?

version
status (deprecated, long-term-support, supported)

What container images are part  the release?

This information should be part of the feature tracker (Stackable Feature Tracker) and it should be generated automatically for every release.
Implementation ideas

Prerequisite: The component status should be pinned down in some form before adding it to the RBOM.

Generate a release bill of materials for each release. (cyclone dx, json). This will be at the application level but will not get down to the package level.

Should contain the image references

Location (docker.stackable.tech...)
PURL pkg:docker/customer/dockerimage@sha256:244fd47e07d1004f0aed9c?repository_url=gcr.io
A reference (BOM link) to the SBOM of the image

The RBOM should also contain the application/product names and versions.

Question: Should additional components also be included in the MVP ? Ex: vector, python, etc.

If an operator patch release is made, everything in the platform is also released in lock-step.

Example component in a SBOM file (cyclone dx):

Adding the component status is possible via properties.
There is a stackable namespace reserved already: https://github.com/CycloneDX/cyclonedx-property-taxonomy

{
  "publisher": "The Apache Software Foundation",
  "group": "org.apache.druid",
  "name": "druid-processing",
  "version": "27.0.0",
  "description": "A module that is everything required to understands Druid Segments",
  "scope": "required",
  "hashes": [
    {
      "alg": "MD5",
      "content": "ce6da3eb7fc34d2ba21800658b130ff7"
    },
    {
      "alg": "SHA-1",
      "content": "742b372ae5f8e369c12991309e4bb4724451b629"
    },
    {
      "alg": "SHA-256",
      "content": "a1a8c74bd15b4965fb50787750791d043760982038e0807386bf4907204b28f0"
    },
    {
      "alg": "SHA-512",
      "content": "c098b2d60fc955a9de4f7bfef1600ca16e6ba9e3c561f6e7cbf228fe858e903ace57ce2563c74140f59f052575160a329a8054b7d93edc4b49ba01f1ceca39fe"
    },
    {
      "alg": "SHA-384",
      "content": "ec9183161b65370a9c2552d5423497fa68ff427182fd2830db5d965213f3d6548f091dfe4e7160d7975280d0c6911796"
    }
  ],
  "licenses": [
    {
      "license": {
        "id": "Apache-2.0"
      }
    }
  ],
  "purl": "pkg:maven/org.apache.druid/druid-processing@27.0.0?type=jar",
  "externalReferences": [
    {
      "type": "website",
      "url": "https://druid.apache.org/druid-processing/"
    },
    {
      "type": "distribution",
      "url": "https://repository.apache.org/service/local/staging/deploy/maven2"
    },
    {
      "type": "mailing-list",
      "url": "https://mail-archives.apache.org/mod_mbox/druid-dev"
    },
    {
      "type": "vcs",
      "url": "https://github.com/apache/druid.git/druid-processing"
    }
  ],
  "type": "library",
  "bom-ref": "pkg:maven/org.apache.druid/druid-processing@27.0.0?type=jar"
}

Are there any initial ideas on where the source of truth is (looking at the code I see an API and DB connection), and how that will be serialized/transported to the Feature Tracker (presumably the API in this repo)?

How should this be presented in the Feature Tracker?

Eg: Just a table of Release, Product+version, Status for now?

Do we want the presentation to determine the data model, or do we need to think ahead (linking SBOMs, dependencies, CVEs, etc...) and define how it is presented later?


Deployment fails when template stored on VMFS5 and deployment done on VMFS6

What happened:
When eksctl anywhere create ... created the bottlerocket template, it ended up on a VMFS5 volume by default. When the installer subsequently attempted to clone the template to VMs, it got stuck in a seemingly infinite loop of failed operations, referencing "the specified delta disk format 'redoLogFormat' is not supported". Thousands of attempts where made, and the only way to stop it (well, the way I realized at the time at least) was to convert the template to a VM and then delete it.
What you expected to happen:
Cloning the template to VMs should work.
How to reproduce it (as minimally and precisely as possible):

VM Template on VMFS5
EKSA pointing to a VMFS6 datastore for the VMs
Ruh eksctl anywhaere create ...

Anything else we need to know?:
Converting the template to a VM, using vMotion to move it from the VMFS5 to a VMFS6 datastore and converting it back to a template solved the issue for me.
Environment:

EKS Anywhere Release: 0.66
EKS Distro Release:

Hi @f97johan thanks for trying out EKS-A. I was trying to reproduce this issue on my environment and failed to do so. I created a content library on VMFS5, deployed the template from the library to a VMFS5 backed folder and provisoned a vm on VMFS6 datastore from the template on VMFS5 folder. I checked that the full version is VMFS 5.81 on my datastore. Could you please let us know if there is some special configuration that you may have on your environment, that could help us with debugging this issue?

Hi @f97johan, is this still not working for you? If not, would it be possible for you to share the details of any special configurations that you made in your environment?
We could not reproduce this issue locally after following the steps mentioned in the previous comments. It would be very helpful to understand your lab environment better.

Glad to know that you could get eks-anywhere to work. I am closing this for now. If you find any other problem,  please reopen this ticket or create a new one.


Strange/chaotic/incorrect method resolution with overloaded method signatures

I have been noticing some strange behavior when Pebble attempts to resolve methods that are overloaded. I've added a test case on this branch demonstrating some of the strange behavior.
Here's my general findings. All are based on a single method name testMethod in a model class, and all methods have accept a single argument. There are multiple different versions of this method where the type of the argument changes, but the method name does not.

When both the primitive and boxed versions exist, it seems like the Boxed version is preferred. I would expect the non-boxed version to be preferred.
When a more generic type exists, it is preferred to the specific type. This goes all the way to the base case where a method with an argument of type Object is preferred to all other types and all method calls go to that one method.
When two methods both extend the same base class, and a method for the base class doesn't exist, I frequently get either a ClassCastException or an IllegalArgumentException (argument type mismatch).

For this situation, by removing any one method, any of them can successfully be called. Having both methods but only calling one of them also seems fine, so I think this particular issue is related to caching. For reference, I've added a few log statements in DefaultAttributeResolver that show the selected method accepts a different parameter than what is passed to it

All of the above behavior seems very chaotic. Adding or removing an overloaded method from the model may make the primitive method selected over the boxed version, and may also cause a ClassCastException instead of an IllegalArgumentException as it is currently set up to do. This makes me think that the strategy for selecting a method is not deterministic when it probably should be.

Yeah, this portion of the engine is crucial for performance, so I agree that we shouldn't change it significantly.
I think including the method parameters array (or empty/null array for fields) in the MemberCacheKey is necessary to prevent the exceptions. And for the "perfect match" method candidate, I think we could still get away with using isAssignableFrom if we don't break out of the loop on the first matching method, but continue the loop and see if there is a better match. As this gets cached, hopefully it wouldn't affect performance too much.

Sure thing


feat: implement runepool deposit

Description
Pretty straighforward:

We disable every part not needed for RUNEPool (APY, Slippage)
We hide unneeded parts (APY, Slippage)
We build the memo conditionnaly using DEPOSIT+ if isRunePool
And voila!

Pull Request Typew

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[x] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

partial #7302
Risk
Low risk
Testing
Use the whole RUNEPool deposit flow until the end!
Please be sure that the opportunity balance is updated when you deposit
Engineering
n/a

Operations
n/a

Screenshots (if applicable)
https://jam.dev/c/560c8e9a-a7cd-4513-abe5-41316bcd8992
https://viewblock.io/thorchain/tx/293AEFE6E6706858E0EB4E57A57D9E72A8043DD3243BB8E4A22F1B8E524AA6CF

Withdraw is like 90 days, thinking we might want that at the beginning of the flow. Do we want an ACK popup or just warning text ?
@NeOMakinG @gomesalexandre thoughts?

Withdraw is like 90 days, thinking we might want that at the beginning of the flow. Do we want an ACK popup or just warning text ?
"RUNEPool deposits have a 90 day minimum lock up period. "
@NeOMakinG @gomesalexandre thoughts?

We have some checkbox at overview step and could absolutely add it there as a warning @twblack88

Withdraw is like 90 days, thinking we might want that at the beginning of the flow. Do we want an ACK popup or just warning text ?
"RUNEPool deposits have a 90 day minimum lock up period. "
@NeOMakinG @gomesalexandre thoughts?

We have some checkbox at empty overview step and could absolutely add it there as a warning @twblack88

Looks legit to me, as an alert on top or included in the checkbox label?

forgot we did checkbox. just add it in there, they are related. Longer lockup and thus impermanent loss.
'I understand that RUNEPool has impermanent loss and a 90 day minimum lockup."


Update: Texmaker.Texmaker version <IP_ADDRESS>

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.0 schema?

Microsoft Reviewers: Open in CodeFlow

This looks like the same domain no? 🤔
https://www.xm1math.net/texmaker/download.html
https://www.xm1math.net/texmaker/assets/files/Texmaker_5.1.2_Win_x64.msi

@wingetbot waivers Add Validation-Domain


Support lazy insertions and retractions

Rules that have many activations, inserting many derived facts into the working memory, could be made more efficient. Today we process each activation independently, but lazily firing them as batches after a set of activations would allow them to take advantage of the batch network optimizations more efficiently.

The above commits improve performance based on some real-world use cases as expected. Closing this issue.


How to Calling Java methods

Hello,
I want to call the Java method in actions and how to do it.

in README.md https://github.com/j-easy/easy-rules#either-in-a-declarative-way-using-annotations
// java method
public MethodExample {
    public static void callExampleFunction() {
        ....
    }
}

@Rule(name = "example rule", description = "...")
public class ExamplerRule {

    @Condition
    public boolean isCond(@Fact("cond") boolean cond) {
        return cond;
    }

    @Action
    public void doing() {
        // call function
        MethodExample.callExampleFunction();
    }
}

OK，thanks


Wrong asset path in Linux/bash

Package version (if known):
Python 3.9.17
Node 14.21.3
npm 6.14.18
invenio-cli 1.1.0
Invenio 11.0
Describe the bug
Running invenio-cli install after running cookie cutter for Invenio 11.0 results in the following error:

ERROR in ./node_modules/semantic-ui-less/semantic.less
Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
ModuleBuildError: Module build failed (from ./node_modules/less-loader/dist/cjs.js):

@import (multiple) '../../theme.config';
^
Less resolver error:
'../../theme.config' wasn't found. Tried - /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/node_modules/semantic-ui-less/theme.config,../../theme.config

Webpack resolver error details:
resolve '../../theme.config' in '/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/node_modules/semantic-ui-less/definitions/modules'
  using description file: /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/node_modules/semantic-ui-less/package.json (relative path: ./definitions/modules)
    aliased with mapping '../../theme.config': '/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config' to '/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config'
      using description file: /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/node_modules/semantic-ui-less/package.json (relative path: ./definitions/modules)
        Field 'browser' doesn't contain a valid alias configuration
        using description file: /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/package.json (relative path: ./less/theme.config)
          no extension
            Field 'browser' doesn't contain a valid alias configuration
            /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config doesn't exist
          .less
            Field 'browser' doesn't contain a valid alias configuration
            /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config.less doesn't exist
          .css
            Field 'browser' doesn't contain a valid alias configuration
            /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config.css doesn't exist
          as directory
            /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config doesn't exist
        root path /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets
          using description file: /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/package.json (relative path: ./home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config)
            no extension
              Field 'browser' doesn't contain a valid alias configuration
              /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config doesn't exist
            .less
              Field 'browser' doesn't contain a valid alias configuration
              /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config.less doesn't exist
            .css
              Field 'browser' doesn't contain a valid alias configuration
              /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config.css doesn't exist
            as directory
              /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config doesn't exist

Webpack resolver error missing:
/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config,/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config.less,/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config.css,/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config,/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config.less,/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config.css

      Error in /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/node_modules/semantic-ui-less/definitions/modules/transition.less (line 19, column 0)
    at /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/node_modules/webpack/lib/NormalModule.js:316:20
    at /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/node_modules/loader-runner/lib/LoaderRunner.js:367:11
    at /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/node_modules/loader-runner/lib/LoaderRunner.js:233:18
    at context.callback (/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/node_modules/loader-runner/lib/LoaderRunner.js:111:13)
    at /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/node_modules/less-loader/dist/index.js:62:5
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
 @ ./js/invenio_theme/theme.js 13:0-40

ERROR in ./js/invenio_theme/templates.js
Module not found: Error: Can't resolve '@templates' in '/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/js/invenio_theme'
 @ ./js/invenio_theme/templates.js 24:17-86
 @ ./js/invenio_search_ui/util.js
 @ ./js/invenio_search_ui/app.js

ERROR in ./js/invenio_app_rdm/deposit/RDMDepositForm.js
Module not found: Error: Can't resolve '@templates/custom_fields' in '/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/js/invenio_app_rdm/deposit'
 @ ./js/invenio_app_rdm/deposit/RDMDepositForm.js 397:17-74
 @ ./js/invenio_app_rdm/deposit/index.js

ERROR in ./js/invenio_communities/community/new.js
Module not found: Error: Can't resolve '@templates/custom_fields' in '/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/js/invenio_communities/community'
 @ ./js/invenio_communities/community/new.js 205:19-76

ERROR in ./js/invenio_communities/settings/profile/index.js
Module not found: Error: Can't resolve '@templates/custom_fields' in '/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/js/invenio_communities/settings/profile'
 @ ./js/invenio_communities/settings/profile/index.js 728:19-76
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!node_modules/less-loader/dist/cjs.js!less/invenio_app_rdm/previewer/iiif_simple.less:
    Entrypoint mini-css-extract-plugin = *
    [1] ./node_modules/css-loader/dist/cjs.js!./node_modules/less-loader/dist/cjs.js!./less/invenio_app_rdm/previewer/iiif_simple.less 1.14 KiB {0} [built]
        + 1 hidden module
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!node_modules/less-loader/dist/cjs.js!node_modules/semantic-ui-less/semantic.less:
    Entrypoint mini-css-extract-plugin = *
       1 module

    ERROR in ./node_modules/semantic-ui-less/semantic.less (./node_modules/css-loader/dist/cjs.js!./node_modules/less-loader/dist/cjs.js!./node_modules/semantic-ui-less/semantic.less)
    Module build failed (from ./node_modules/less-loader/dist/cjs.js):

    @import (multiple) '../../theme.config';
    ^
    Less resolver error:
    '../../theme.config' wasn't found. Tried - /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/node_modules/semantic-ui-less/theme.config,../../theme.config

    Webpack resolver error details:
    resolve '../../theme.config' in '/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/node_modules/semantic-ui-less/definitions/modules'
      using description file: /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/node_modules/semantic-ui-less/package.json (relative path: ./definitions/modules)
        aliased with mapping '../../theme.config': '/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config' to '/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config'
          using description file: /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/node_modules/semantic-ui-less/package.json (relative path: ./definitions/modules)
            Field 'browser' doesn't contain a valid alias configuration
            using description file: /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/package.json (relative path: ./less/theme.config)
              no extension
                Field 'browser' doesn't contain a valid alias configuration
                /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config doesn't exist
              .less
                Field 'browser' doesn't contain a valid alias configuration
                /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config.less doesn't exist
              .css
                Field 'browser' doesn't contain a valid alias configuration
                /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config.css doesn't exist
              as directory
                /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config doesn't exist
            root path /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets
              using description file: /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/package.json (relative path: ./home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config)
                no extension
                  Field 'browser' doesn't contain a valid alias configuration
                  /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config doesn't exist
                .less
                  Field 'browser' doesn't contain a valid alias configuration
                  /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config.less doesn't exist
                .css
                  Field 'browser' doesn't contain a valid alias configuration
                  /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config.css doesn't exist
                as directory
                  /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config doesn't exist

    Webpack resolver error missing:
    /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config,/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config.less,/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config.css,/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config,/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config.less,/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/less/theme.config.css

          Error in /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance/assets/node_modules/semantic-ui-less/definitions/modules/transition.less (line 19, column 0)
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!node_modules/sass-loader/dist/cjs.js!scss/invenio_previewer/bottom.scss:
    Entrypoint mini-css-extract-plugin = *
    [1] ./node_modules/css-loader/dist/cjs.js!./node_modules/sass-loader/dist/cjs.js!./scss/invenio_previewer/bottom.scss 1.11 KiB {0} [built]
        + 1 hidden module
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!node_modules/sass-loader/dist/cjs.js!scss/invenio_previewer/pdfjs.scss:
    Entrypoint mini-css-extract-plugin = *
     [2] ./js/invenio_previewer/pdfjs/web/images/texture.png 3.19 KiB {0} [built]
     [3] ./js/invenio_previewer/pdfjs/web/images/loading-small.png 9.68 KiB {0} [built]
     [4] ./js/invenio_previewer/pdfjs/web/images/toolbarButton-menuArrows.png 183 bytes {0} [built]
     [5] ./js/invenio_previewer/pdfjs/web/images/toolbarButton-sidebarToggle.png 339 bytes {0} [built]
     [6] ./js/invenio_previewer/pdfjs/web/images/toolbarButton-sidebarToggle-rtl.png 339 bytes {0} [built]
     [7] ./js/invenio_previewer/pdfjs/web/images/toolbarButton-secondaryToolbarToggle.png 363 bytes {0} [built]
     [8] ./js/invenio_previewer/pdfjs/web/images/toolbarButton-secondaryToolbarToggle-rtl.png 367 bytes {0} [built]
     [9] ./js/invenio_previewer/pdfjs/web/images/findbarButton-previous.png 307 bytes {0} [built]
    [10] ./js/invenio_previewer/pdfjs/web/images/findbarButton-previous-rtl.png 299 bytes {0} [built]
    [11] ./js/invenio_previewer/pdfjs/web/images/findbarButton-next.png 299 bytes {0} [built]
    [12] ./js/invenio_previewer/pdfjs/web/images/findbarButton-next-rtl.png 307 bytes {0} [built]
    [13] ./js/invenio_previewer/pdfjs/web/images/toolbarButton-pageUp.png 367 bytes {0} [built]
    [14] ./js/invenio_previewer/pdfjs/web/images/toolbarButton-pageUp-rtl.png 367 bytes {0} [built]
    [15] ./js/invenio_previewer/pdfjs/web/images/toolbarButton-pageDown.png 359 bytes {0} [built]
    [38] ./node_modules/css-loader/dist/cjs.js!./node_modules/sass-loader/dist/cjs.js!./scss/invenio_previewer/pdfjs.scss 90.9 KiB {0} [built]
        + 24 hidden modules
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!node_modules/sass-loader/dist/cjs.js!scss/invenio_previewer/prismjs.scss:
    Entrypoint mini-css-extract-plugin = *
    [1] ./node_modules/css-loader/dist/cjs.js!./node_modules/sass-loader/dist/cjs.js!./scss/invenio_previewer/prismjs.scss 5.87 KiB {0} [built]
        + 1 hidden module
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!node_modules/sass-loader/dist/cjs.js!scss/invenio_previewer/simple_image.scss:
    Entrypoint mini-css-extract-plugin = *
    [1] ./node_modules/css-loader/dist/cjs.js!./node_modules/sass-loader/dist/cjs.js!./scss/invenio_previewer/simple_image.scss 860 bytes {0} [built]
        + 1 hidden module
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!node_modules/sass-loader/dist/cjs.js!scss/invenio_previewer/txt.scss:
    Entrypoint mini-css-extract-plugin = *
    [1] ./node_modules/css-loader/dist/cjs.js!./node_modules/sass-loader/dist/cjs.js!./scss/invenio_previewer/txt.scss 501 bytes {0} [built]
        + 1 hidden module
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!node_modules/sass-loader/dist/cjs.js!scss/invenio_previewer/zip.scss:
    Entrypoint mini-css-extract-plugin = *
    [1] ./node_modules/css-loader/dist/cjs.js!./node_modules/sass-loader/dist/cjs.js!./scss/invenio_previewer/zip.scss 1.38 KiB {0} [built]
        + 1 hidden module
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!node_modules/sass-loader/dist/cjs.js!scss/invenio_theme/admin.scss:
    Entrypoint mini-css-extract-plugin = *
    [1] ./node_modules/css-loader/dist/cjs.js!./node_modules/sass-loader/dist/cjs.js!./scss/invenio_theme/admin.scss 312 KiB {0} [built]
        + 1 hidden module
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR<EMAIL_ADDRESS>build: `NODE_PRESERVE_SYMLINKS=1 NODE_ENV=production webpack --config ./build/webpack.config.js`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/stefano/.npm/_logs/2023-08-28T16_47_42_888Z-debug.log
Traceback (most recent call last):
  File "/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/bin/invenio", line 8, in <module>
    sys.exit(cli())
  File "/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/lib/python3.9/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
  File "/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/lib/python3.9/site-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
  File "/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/lib/python3.9/site-packages/click/core.py", line 1688, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/lib/python3.9/site-packages/click/core.py", line 1719, in invoke
    rv.append(sub_ctx.command.invoke(sub_ctx))
  File "/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/lib/python3.9/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/lib/python3.9/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
  File "/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/lib/python3.9/site-packages/click/decorators.py", line 33, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/lib/python3.9/site-packages/flask/cli.py", line 357, in decorator
    return __ctx.invoke(f, *args, **kwargs)
  File "/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/lib/python3.9/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
  File "/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/lib/python3.9/site-packages/flask_webpackext/cli.py", line 64, in build
    current_webpack.project.build(*args)
  File "/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/lib/python3.9/site-packages/pywebpack/helpers.py", line 48, in inner
    raise RuntimeError("Process exited with code {}".format(exit_code))
RuntimeError: Process exited with code 2
Failed to install dependencies.

The problem is that scheme.config is in a folder that got created with a strange path:
$ find /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/ -name theme.config
/home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/instance?[0 q/assets/less/theme.config

That folder got created along with a "normal" seeming folder:
$ ls -l /home/stefano/.local/share/virtualenvs/invenio11-test-W2x8TNwy/var/
total 8
drwxr-xr-x 4 stefano stefano 4096 Aug 28 12:45  instance
drwxr-xr-x 4 stefano stefano 4096 Aug 28 12:45 'instance'$'\033''[0 q'

It looks like the script is having some issues escaping path names.
Steps to Reproduce
In Archlinux + bash:
python3.9 -m venv venv
source venv/bin/activate
export PIPENV_IGNORE_VIRTUALENVS=1
pip install invenio-cli
invenio-cli init -c v11.0
<answer interactive questions; project folder is invenio11-test>
cd invenio11-test
invenio-cli install
<receive error>

Expected behavior
Invenio install should complete with out errors.

I retried this with a vanilla Archlinux docker image, installing just Python 3.9, Node 16, etc. It builds now. This means that something in my user startup scripts might be causing the problem. I'll try now with a new user on my native OS to confirm this is indeed the case.
Maybe I can focus further on the problematic bits so we can decide whether I have a non-standard setup or if it's a standard setup that's causing invenio-cli to misbehave.

Confirmed that a new user without customized .bashrc and .profile* works.

I found the problem, but I don't have a solution.
The lines here run a non-interactive IPython shell, which on exit leaves some junk characters. These characters are caused by a setting in my home folder:
 $ ipython --show-config
Python 3.9.17 (main, Aug 18 2023, 15:45:01)
Type 'copyright', 'credits' or 'license' for more information
IPython 8.14.0 -- An enhanced Interactive Python. Type '?' for help.
Loaded config files:
  /home/stefano/.ipython/profile_default/ipython_config.py

TerminalInteractiveShell
  .editing_mode = 'vi'

this difference shows when I run
ipython -c "print('hello')" | less

in the same virtualenv. (without piping to less the junk won't show as it's not printable)
By removing the editing_mode = 'vi'  option, the install script runs just fine. However, I don't want to change my config just to install a software package.
I tried passing the option --quick to IPython, which doesn't load my configuration, and that seems to work. But if I add the same option to the install script, for some reason it will still produce the wrong output.
Is it necessary to use IPython as the default shell to run non-interactive commands? Or is  there another way to get the Flask app context within the install script?


remove yaml cpp binary and use bazel native rules

Purpose of this pull request
Make the compilation faster for yaml cpp
How would this pull request resolve the issue
This pull request untars the binary tar ball into actual files and directly uses bazel to compile. Hence yaml cpp does not depend on make/automake/cmake/autoconfig etc. Since bazel uses parallelism underneath, it speeds up compilation.
What would be when the pull request is merged: (Issues resolved? What's the expected results?)
The expected result is in the increase faster compilation. This is a part of the broader effort to remove tar balls out of the code base. If Twitter were to mirror selective github repos, we can further simplify the PR using new_git_repository rules. It can be done in a later PR once repos are setup.

I didn't understand the purpose of this change. Why is it better?

It is incremental benefit as we move towards removing tar balls out of the source code base
yaml cpp does not make use make/cmake/autoconf/automake tools to setup and compile. Instead, it directly uses bazel - because of that bazel can parallelize the compilation of the yaml cpp files - thus reducing the compilation time. While it might be small in yaml-cpp, as we convert other projects it will get better and better.

@kramasamy
Can we have following parts in the description?
Current issue:
The purpose of this pull request:
How would this pull request resolve the issue:
What would be when the pull request is merged: (Issues resolved? What's the expected results?)

Purpose of this pull request

Make the compilation faster for yaml cpp

How would this pull request resolve the issue

This pull request untars the binary tar ball into actual files and directly uses bazel to compile. Hence yaml cpp does not depend on make/automake/cmake/autoconfig etc. Since bazel uses parallelism underneath, it speeds up compilation

What would be when the pull request is merged: (Issues resolved? What's the expected results?)

The expected result is in the increase faster compilation. This is a part of the broader effort to remove tar balls out of the code base. If Twitter were to mirror selective github repos, we can further simplify the PR using new_git_repository rules. It can be done in a later PR once repos are setup.

Closing this pull request. If you believe the PR is still needed, please leave a comment.

Closing this pull request. If you believe the PR is still needed, please leave a comment.


Build the Database migrator tool as part of the backend build

This PR does two things:

It dynamically generates a go file that includes that references all of the go-based migration files, so that you don't have to modify main.go when you add a new migration.

It adds the build of the db migration tool to the backend build target. This will allow us to remove this from the build script used when deploying in Cloud Foundry and also allows us to us this migrator tool across all environments. We should be able to reduce the size of the postflight image since it will no longer need go to be installed.

Merged during https://github.com/SUSE/stratos-ui/pull/1318


Not doing anything

So ive just recently been getting into linux and pentesting etc, and i saw a video on this by JackkTutorials, so i decided to give it a go but unfortunately it doesnt do anything.
im running kali linux 3 and its a live boot from usb on a laptop, ive tried to use it on my android phone to no avail as well as my iphone, and i can still browse the web and use my internet.
i have installed the requirements(it shows they are satisfied with no other errors)
what am i doing wrong?

So when you start it, it just hangs and does not show the menu with the KickThemOut logo?

I have the same issue, after running sudo python kickthemout.py, I receive nothing, just an empty line. however, when the command is not run as root, you receive the red and green message telling you to run as root, meaning that kickthemout is present.

Hi there. In a recent commit, we changed the whole scanning process in order to improve usability and resolve issues previously raised. Please try following the new installation procedure.
If this issue still occurs, please let us know.
Thank you.


Use test host for unit tests

Coverage decreased (-5.1%) to 86.873% when pulling b03619ca5fd9bbfde9aa9fe74b6d7cd2411a5c79 on testhost into 0cedf87e4686ebe3fc97c78da2308c9d985d2644 on master.

Coverage decreased (-5.1%) to 86.873% when pulling 3d1ad9c564578876d248fec39eb327b1a3b5b285 on testhost into 0cedf87e4686ebe3fc97c78da2308c9d985d2644 on master.

Coverage decreased (-92.0%) to 0.0% when pulling 80609c65a0c453ba8758becc75e3b64a2693d97f on testhost into 0cedf87e4686ebe3fc97c78da2308c9d985d2644 on master.

Coverage increased (+0.2%) to 92.231% when pulling 4b75a2c0ad218257940d1ba0bf0ab43291d0774c on testhost into 0cedf87e4686ebe3fc97c78da2308c9d985d2644 on master.

Coverage decreased (-5.2%) to 86.824% when pulling 4b75a2c0ad218257940d1ba0bf0ab43291d0774c on testhost into 0cedf87e4686ebe3fc97c78da2308c9d985d2644 on master.

Coverage increased (+0.2%) to 92.183% when pulling f5448d5aa227d85d815a50429abbddeaf45ba76a on testhost into 0cedf87e4686ebe3fc97c78da2308c9d985d2644 on master.

Coverage increased (+0.2%) to 92.183% when pulling 6d714278f80a3f34b7e83c7754c423beabe7b8c2 on testhost into cdd2f403e9d6083aab6ec284b4dc99589d7a6084 on master.

Coverage increased (+0.2%) to 92.183% when pulling 6d714278f80a3f34b7e83c7754c423beabe7b8c2 on testhost into cdd2f403e9d6083aab6ec284b4dc99589d7a6084 on master.

Coverage increased (+0.2%) to 92.183% when pulling ff48d6d7810030ab8eacfcaaa1bb5ff9b91d0cd8 on testhost into 85b2a5c1b925c0c7e0783bbca29128d9ad700169 on master.