Add attribute to results data model(s) to keep track of the type of each "report"

In order to render plots described in SED documents as discussed at the end of the HARMONY with Lucian Smith and Frank Bergmann, we need to save the data for plots (e.g. to HDF/CSV). After thinking about this, I think the simplest solution is to basically treat report and plot data the same -- save the plot data to CSV/HDF and use the same typescript/MongoDB data structures.
To help keep track of which data corresponds to SedReports and which to SedPlot2D or SedPlot3d, it would helpful to record the type of the output associated with each instance of ResultsModel (SedReport, SedPlot2D or SedPlot3d).
Example: add attribute with name type or _type to ResultsModel in biosimulations/apps/dispatch-api/results/results.model.ts. The value of this attribute could be SedReport, SedPlot2D or SedPlot3D.
(Ideally, we'd also rename attributes from reportId to outputId, reflecting their new more general meaning. But changing this seems like a lower priority.)

This will be handled directly by the hsds return information. Still todo, define the model for the returned data

This information is captured in HDF5 by the _type attribute. The values can be Report, Plot2D, or Plot3D.

@jonrkarr  could you take a look at this commit and approve the changes to the datamodel? This is the data that is returned from the dispatch-api.  I am not sure if sedmlName and sedmlId are designed to be exposed
https://github.com/biosimulations/Biosimulations/pull/2627/commits/b02ab010150be4484e6b672d0518ead45c542dde

Looks good. I added a couple thoughts about attribute names (mainly for consistency between the classes) before I saw your latter commit already does some of this.


Collected patches for consideration in next release.

I've come up with a collection of patches that resolve a number of the issues
reported against this project. I'm creating this report as a catch-all to
collect these in one place.

At this point I'm starting to think that moving this project to github would be
a good idea, though without being able to modify these pages it would be hard
for existing users to get from here to there.

Simon

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 3 Jul 2015 at 12:32
Attachments:

ash-sjjf-collected-fixes-20150703.patch
ash-sjjf-proposed-dont-pretend-we-know-where-_ash-log-is-20150703.patch
ash-sjjf-proposed-interactive-shell-fix-20150703.patch
ash-sjjf-proposed-source-should-not-exit-20150703.patch

Integrated in the github version.


test spark websockets?

Any way to test websockets through this?

Hi @dessalines. Sorry for the huge delay! I think that testing websockets is possible. Would you like to contribute with a pull request?


Provide container_runtime flag to Kubelet in CoreOS.

Tested on a cluster bringup and it came up with the option as expected.
/cc @yujuhong @yifan-gu @dchen1107 @zmerlynn

LGTM.


Syft cannot get license from package.json in nested node_modules dir

What happened:
Syft cannot get a license from a package.json file in a nested node_modules dir.
If library A is in a nested node_module dir, like following, then Syft cannot output its license.
| --- yarn.lock <--- including library A as a dependency
| --- node_modules
       | --- library B
              | --- node_modules
                    | --- library A
                          | --- package.json <--- including a license field

What you expected to happen:
The license of library A is also included in the output.
Steps to reproduce the issue:
I happen to this issue when I use<EMAIL_ADDRESS>Following steps can reproduce this issue.
$ pwd
/path/to/YOUR_TEST_DIR
$ yarn init -y
$ yarn add<EMAIL_ADDRESS>
$ syft . -o spdx-json | jq '.packages[] | select(.licenseDeclared == "NOASSERTION") | {name, sourceInfo, licenseDeclared, licenseConclude} '
{
  "name": "babel-plugin-apply-mdx-type-prop",
  "sourceInfo": "acquired package info from installed node module manifest file: /yarn.lock",
  "licenseDeclared": "NOASSERTION",
  "licenseConclude": null
}
{
  "name": "trim",
  "sourceInfo": "acquired package info from installed node module manifest file: /yarn.lock",
  "licenseDeclared": "NOASSERTION",
  "licenseConclude": null
}
$ cat<EMAIL_ADDRESS>| jq .license
"MIT"

Anything else we need to know?:
This issue does not occur when I use npm i<EMAIL_ADDRESS>instead of yarn add.
And yarn version is:
$  yarn -v
1.22.19

Environment:

Output of syft version:

$ syft version
Application: syft
Version:    0.96.0
BuildDate:  2023-11-09T14:04:09Z
GitCommit:  0891d35e0774f175e3a3f170edcce9ad2f4f015b
GitDescription: v0.96.0
Platform:   darwin/arm64
GoVersion:  go1.21.3
Compiler:   gc

OS (e.g: cat /etc/os-release or similar):

$ sw_vers
ProductName:		macOS
ProductVersion:		13.4.1
BuildVersion:		22F82

Hi @sasakiyuta84, thanks for the report and great reproduction steps and sorry it took a while to reply. We will take a closer look and see if we can tell what's going on here.


NK-579 Update Satori client to comply to latest API

Include Nakama session token id as SessionID in Satori generated auth tokens.

I have a few more things to review before this could be merged


QoL changes

I'll comment on the changes to explain some changes that I think aren't clear.

A few things changed since this PR was opened.

deko3d nanovg incoming

requires application.cpp to be completely changed
requires my nanovg changes there to be applied there

Images are now copyable

in conflict with my changes
is stupid

I'll rebase the changes that aren't in conflict with your design decisions after platform_drivers is merged.


Error installing agent on Centos: Failed: WARNING: Unzip (tee) Failed with return code 127

I have a new Centos image which i have created a user and then went to install the agent. I get the following output:
[_USER_@_MACHINENAME_ myagent]$ curl -skSL http://aka.ms/xplatagent | bash
Platform: Linux

--------------------------------------
     Acquiring Node 5.6.0
--------------------------------------

Downloading Node 5.6.0 @ https://nodejs.org/dist/v5.6.0/node-v5.6.0-linux-x64.tar.gz
Setting internal node in path
using node : /home/_USER_/myagent/runtime/node/bin/node
using npm  : /home/_USER_/myagent/runtime/node/bin/npm

--------------------------------------
     Acquiring TEE CLI 14.0.2-private
--------------------------------------

Downloading  TEE CLI 14.0.2-private
Failed: WARNING: Unzip (tee) Failed with return code 127.  This is only critical if using TFSVC (not needed for git)

As I'm only going to use the agent for Git repos, i feel that the error doesn't concern me. However, the install does not continue meaning there is no run.sh to configure the agent

I sent you an email. thanks for the help

I'm experiencing the same issue on Ubuntu 14.04.

The releases tab has a full tar.gz download is failing

Just install unzip and it will install fine. Run:
sudo apt-get install unzip


add RHEL9 support

create vars file for RHEL9 support

This role has been deprecated in favor of a the prometheus-community/ansible collection.


make pinning of requests less restrictive due to urllib3 debacle

hey all,
as you may know urllib3's breaking change to version 2 is causing widespread issues.
many packages have upgraded to support urllib3 2+, or at least the latest security patches at 1.26.X.
currently an issue with requests: https://github.com/psf/requests/issues/6443 for requests version 2.23.0 is resulting in only installing urllib3 at 1.25 or lower.
I encountered this when trying to install the sentry-sdk within a new Django project.
notice that the sentry-sdk install_requires for Python is at: https://github.com/getsentry/sentry-python/blob/master/setup.py#L43
if the pinning for resend is changed to say requests>=2.29.0  this issue should be resolved. where 2.29.0 supports requests 2.29.0 depends on urllib3<1.27 and >=1.21.1 and any new versions can be supported

thanks for reporting @djstein , will look into it

Running into the same issue here

@djstein @lharries  just released v0.5.0 which points to requests 2.31.0. Lmk if you're still seeing any issues ?


Added vector support

All of these checks have a common backbone that suggests it can be factored into a private helper function.

Merging it into this repo and making the changes from trill's copy.


Archive notice for monorepo migration

This PR updates the project README to indicate that it has been archived. This PR should be merged when https://github.com/creativecommons/vocabulary/pull/613 is merged. This repository should also be archived in the GitHub UI at that time.
Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the default branch of the repository (main or master).
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added tests for the changes I made (if applicable).
[x] I added or updated documentation (if applicable).
[ ] I tried running the project locally and verified that there are no
visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

All archived repos are stored in https://github.com/cc-archive, FYI


[4.1.x] Nested filters

Hello,
How can I make nested filters?
E.g., I want to filter by "city" and "town" using select2_ajax. I want to send the selected city_id when I search for a town.
Thanks.

I think I need something like include_all_form_fields in select2_from_ajax.

Hmm interesting use case. There's no include_all_form_fields for filters. Not yet anyway, but we'll consider doing this in 4.1.x.
You should be able to create a custom filter starting from the select2_ajax filter, to also include the value of that other filter you want. So that you have both their values in the AJAX call.

In a time of absolute desperation, I used the following code.
WARNING: It's not a solution. It requires a refresh after the first filter.
_But it works. _
         $this->crud->addFilter(
            [
                'name' => 'act',
                'type' => 'select2_ajax',
                'label' => 'Act',
                'placeholder' => 'Pick an Act'
            ],
            url('api/filter/act'),
            function ($value) {
                if($value != null){
                    $this->crud->query = $this->crud->query->whereHas('Headnotes', function ($query) use ($value){
                        $query->whereHas('Sections', function ($query3) use ($value) {
                            $query3->where('act_id', $value);
                        });
                    });
                    $this->crud->addFilter(
                        [
                            'name' => 'section',
                            'type' => 'select2_ajax',
                            'label' => 'Section from ' . Act::find($value)->prompt,
                            'placeholder' => 'Pick a Section from ' . Act::find($value)->prompt,
                        ],
                        url('api/filter/section2/' . $value),
                        function ($value2) {
                            if($value2 != null){
                                $this->crud->query = $this->crud->query->whereHas('Headnotes', function ($query) use ($value2){
                                    $query->whereHas('Sections', function ($query3) use ($value2) {
                                        $query3->where('id', $value2);
                                    });
                                });
                            }
                        }
                    );
                }
            }
        );

Is somebody working on this?

@tabacitu, would this be something you are looking for? It's chainable and supports multiple dependants.

        jQuery(document).ready(function($) {
           ...
            assessUsability();
            @foreach($filter->options["dependants"] as $dependant)
                $('#filter_{{ $dependant }}').each(function () {
                    $(this).on('select2:clear', function (e) {
                        assessUsability();
                    })
                    $(this).on('select2:select', function (e) {
                        assessUsability();
                    })
                });
            @endforeach
        });
        function assessUsability() {
            if ( @foreach($filter->options["dependants"] as $dependant) ( $('#filter_{{ $dependant }}').val() != null ) && @endforeach true ) {
                $('#filter_{{ $filter->name }}').prop('disabled', false);
            } else {
                $('#filter_{{ $filter->name }}').val(null).trigger('change');
                $('#filter_{{ $filter->name }}').prop('disabled', true);
            }
        }

AND
                        data: function (term) {
                            return {
                                term: term,
                                dependants: {
                                    @foreach($filter->options["dependants"] as $dependant)
                                        {{ $dependant }}: $('#filter_{{ $dependant }}').val(),
                                    @endforeach
                                },
                            };
                        },

Thank you for sharing your solution @Athuli7 ! Nobody's working on this at the moment - we're focused on getting 4.1 out the door first. But it's on the to-do list for after we launch 4.1.
If you end up with a solution you like, consider creating a PR - it would be very welcome.
Regarding the solution itself - I guess if it wouldn't be too much code, we can include it in the existing filter. Otherwise, if there are too many changes, maybe it's better to create a separate filter for it. You click it, and in the drop-down it would show all interconnected Select2s... I don't know which one is better from a user perspective...

I ended up making it. And also adding the option to hide the filter till the conditions are met. I'll make a PR.

Wow, great to hear that @Athuli7 ! Thanks a lot.

Hi again,
@Athuli7, thanks for your contribution.
Does it available to use now?


Cannot exclude vendor/ folder

I'm using bundler, and all my gems are installed in projects_folder/vendor/ (including rubocop).
I've been succesfully excluding folders, but somehow I'm not able to exclude the vendor folder. Maybe it has something to do with rubocop being in it???
I think I've tried everything, like
vendor/**
'**/vendor/**'
vendor/**/*

etc.
(furthermore: in the code in Rubocop::Config#match_path? I see that pattern can either be a string or a regex... but how to define a regex in the rubocop.yml?)

@jonas054
Hi, I launch a rubocop through a Travise in the github
but for some reason it checks the folder vendore Maybe you know why?
Travis:
script: bundle exec rspec spec && bundle exec rubocop --config .rubocop.yml

.rubocop.yml
AllCops:
  DisplayStyleGuide: true
  DisplayCopNames: true
  Include:
    - '**/Gemfile'
    - '**/Rakefile'
  Exclude:
    - '**/bin/spring'
    - '**/bin/setup'
    - '**/bin/rake'
    - '**/bin/rails'
    - '**/db/schema.rb'
    - 'client/**/**'
    - 'config/**/**'
    - 'db/**/**'
    - 'bin/**'
    - 'app/models/role.rb'
    - 'vendor/*'
Rails:
  Enabled: true

Metrics/LineLength:
  Max: 120

Metrics/MethodLength:
  Max: 20

Style/Documentation:
  Enabled: false

Metrics/AbcSize:
  Max: 25

Metrics/ModuleLength:
  Exclude:
    - "**/*_spec.rb"

Metrics/BlockLength:
  Exclude:
    - "**/*_spec.rb"
  ExcludedMethods: ['included']

@bogdan8 Yes, the correct pattern for excluding all files under vendor recursively is vendor/**/*.

@jonas054
Hi yes it helped me
Thanks)

Is there a reason why vendor is not excluded by default?

Is there a reason why vendor is not excluded by default?

I agree it probably should. I'll try to remember to do that when I tackle #7819; you may want to subscribe to that thread.

It is excluded by default. What happened here was that AllCops: Exclude was overridden in the local .rubocop.yml, so then you need to either set inherit_mode or copy the patterns you need to the local AllCops: Exclude.

OK, I've been using RuboCop for six years and this is the first time I've heard of inherit_mode — I see it wasn't in the README back in the day.
Personally I think Exclude should default to merge, but failing that, maybe it should be documented more prominently -- or the fact that without it adding any custom Exclude will lose the defaults should be called out more explicitly. Given the special behavior of Include and Exclude with regard to shadowing in subdirectories, it's not entirely intuitive.

I have to agree with @dmolesUC ; it's pretty surprising to add an exclude directive to .rubocop.yml and have that result in files that were previous being excluded no longer being so. It's true that after reading about it and reasoning about it you can totally understand how it works, but it's pretty confusing when you first encounter it.

:+1: on merging Exclude: should be the default, who doesn't want that?

I filed an issue to merge Exclude: by default, I believe that is always the intention for RuboCop users: #9325

I filed an issue to merge Exclude: by default, I believe that is always the intention for RuboCop users: #9325


Add spin to made with love heart, add mduleone

Gif of relevant area of index.html after changes (it's looped poorly)

Awesome :)


Spine Game object above an ellipse in the displayList makes every sprite blue

Version

Phaser Version: 3.51.0
Operating system: Windows

Description
if a spine Game object is above an ellipse game object in the displayList every sprite/image becomes purely blue
Example Test Code
class Example extends Phaser.Scene
{
    constructor ()
    {
        super({
            pack: {
                files: [
                    { type: 'scenePlugin', key: 'SpinePlugin', url: 'plugins/3.8.95/SpinePluginDebug.js', sceneKey: 'spine' }
                ]
            }
        });
    }

    preload ()
    {
        this.load.image('logo', 'assets/sprites/phaser.png');

        this.load.setPath('assets/spine/3.8/demos/');

        this.load.spine('set1', 'demos.json', [ 'atlas1.atlas' ], true);
    }

    create ()
    {
        this.add.image(0, 0, 'logo').setOrigin(0);

        const boy = this.add.spine(460, 600, 'set1.spineboy', 'idle', true);
        const circle = this.add.ellipse(130, 200, 250, 250, 0xffffff);

        this.sys.displayList.bringToTop(boy);
    }
}

const config = {
    type: Phaser.WEBGL,
    parent: 'phaser-example',
    width: 800,
    height: 600,
    backgroundColor: '#2d2d2d',
    scene: Example
};

const game = new Phaser.Game(config);

maybe this is related to #5449

maybe this is related to #5449

This is almost certainly the same as #5449 but I'll leave it open for now.

This is almost certainly the same as #5449 but I'll leave it open for now.

Thanks a lot for opening!
A very clear replication demo.

Thanks a lot for opening!
A very clear replication demo.

https://codepen.io/samme/pen/MWbKeEE

Thank you for submitting this issue. We have fixed this and the fix has been pushed to the master branch. It will be part of the next release. If you get time to build and test it for yourself we would appreciate that.


The Suicide white paper has been approved by VA SMEs for sharing.

The Suicide white paper has been approved by VA SMEs for sharing.
20180515REVISED-CDSK_CCWP_O20B52Suicidality_final_508_copyright_KBS_APPROVED_LLW.docx
I will attach the Word document that reflects edits desired by the SMEs.  Franklin Cuello will take over from here & handle editing in DocBook.

@linophth Any word on the KNARTs?

I have no idea.  I am not editing XML, so I am not the one to ask.  I think Diane is trying to clarify who is the one to ask.


SAP Odata Connector Reference

Completely re-written

@MarkvanMents Please redo these screenshots for the Modeler modernization in 7.12.

@MarkvanMents Please check the Travis error log and fix the build error.

@Adam-Dupaski has 7.12 still got a release date? I've just seen that all the dates have changed. I didn't want this sitting for a month before it goes live.
I will do the 7.12 pictures as a new pull, if that is OK.
Am checking the Travis log as I write.

@MarkvanMents The release of 7.12 is still on time, AFAIK. Updating the screenshots in another PR is fine. Please note that other R&D teams are updating all Ref Guide screenshots for 7.12, so your team should plan for that for SAP-related Ref Guide docs. Thanks for fixing the build error.

@Adam-Dupaski
OK - doing the new screenshots now, plus the other ones on the spreadsheet

@MarkvanMents Sounds good, thanks.


Add current plan state for pricing plan

We've added a current prop to the pricing plan. It highlights the plan and adds a box shadow 👍

 Design "active" plan state


paste: Error executing lua: vim.lua:203: Vim(endfunction):E171: Missing :endif

vim version: Neovim v0.5.0-404-g49cd750d6
OS: ArchLinux
Input
:%s/[paste-here] (paste or middle click)
Error message
paste: Error executing lua: vim.lua:203: Vim(endfunction):E171: Missing :endif
I think this error has been occurring since https://github.com/mg979/vim-xtabline/commit/17efbb83c4a6640a0a08733172468a7e537ee28e

I can't reproduce with neovim stable (0.4.3) and xterm-256color (xfce4-terminal). What terminal are you using?
Also, when you say:
:%s/[paste-here] (paste or middle click)
How do you paste if not with middle click? Middle click works without errors for me.

I'm sorry, I didn't have enough research.
I'm using alacritty 0.4.1.
And, This is minimal vimrc. It's only for neovim.
set nocompatible

set inccommand=split

set runtimepath^=~/.vim/plugged/vim-xtabline
syntax on
filetype plugin indent on

Paste is terminal paste function in alacritty. It's C-S-V for me.
{ key: V,        mods: Control|Shift,    action: Paste               }
This error occurs with a mouse-middle-click. But <C-r>" does not occur.

Ok I could reproduce it, I'll see what causes it.

It should be fixed, it's a bit weird, I think it's a nvim bug, but at least it shouldn't be happening again. Please reopen if it doesn't work.

it works fine! Thank you :+1:


gitAndTools.gitui: 0.9.1 -> 0.10.1

Motivation for this change
Update gitui to 0.10.1
This PR need to be merged after Rust 1.46 merged
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[X] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
No diff detected, stopping review...
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

@filatex77 This package is updated and ready with Rust 1.46.  May you review on this?   Many thanks.

Hi @ryantm,
Because filatex77 is not here on github, may you kindly help to take a look on this PR?
Thanks.

@yanganto Why is this targeting staging?

@ryantm Because Rust 1_46 is required for building this version of gitui.
Should I wait the Rust 1_46 ready in master then PR on the master?
Thanks for review.

@ryantm the PR target is changed to master, and the Rust 1_46 is ready in master.  ^ _ ^

Result of nixpkgs-review pr 97374 1

1 package built:
- gitAndTools.gitui

@yanganto So much faster to review now that Hydra has built rust!


Add EntityTag.internal_data mechanism

Additions

EntityHelper#modifyInternalEntityData(Entity, Map<Integer, ObjectTag>) - modifies an entity's internal data by id, currently only implemented on 1.20.
EntityHelper#mapInternalEntityDataName(Entity, String) -> int - maps a string name to an internal entity data id, currently only implemented on 1.20.
EntityDataNameMapper - class in the NMS module that contains name -> id mappings for internal entity data, and logic to convert names -> ids based on entity types.
EntityTag.internal_data mechanism - modifies an entity's internal data (using the above methods).
Added several Denizen -> NMS object conversions, registered in the NMS Handler's constructor.
Handler(1.20)#registerConversion - util method to register conversions from a specific Denizen type to a specific Java type.
ReflectionMappingsInfo.SynchedEntityData_itemsById - mappings info used in the new EntityHelper#modifyInternalEntityData.

Notes

Handler#registerConversion should probably be moved to core as a generic util for conversions, let me know if you want me to just directly push it and update the PR or do that in the future.
EntityDataNameMapper can technically be in the main module, but that'd be a bit more work on the handling (since Spigot uses interfaces instead of classes) & these are technically a per-version thing, as they can change in Minecraft updates - but it isn't impossible, so let me know if I should try doing that.
The check for invalid entity id in EntityHelper(1.20)#modifyInternalEntityData is technically redundant now because it will only ever get valid ones from the string -> name mappings, but I'd say it's still useful incase of the mappings not being updated to changes; let me know if that should be removed though - even if it's gone there would still be an NPE in case of outdated mappings.

Should be ready for review now


When adding point to kgraph, user should get confirmation fingerprint

After adding new point to kgraph, user should receive a confirmation ID
Acceptance criteria:

After adding new data point, user gets confirmation ID

After adding a point to the kgraph return:
sha256(fingerprint, edge id)


Unable to change status of Job

My actions before raising this issue

[X] Read/searched the docs
[x] Searched past issues

I don't have an option to change status of job.

Additionally the enumeration type for the status of the job in enums.js is called TaskStatus. I think the name of this should be changed since it is referring to a task not a job.
Expected Behaviour

The menu on the annotation page gives option to change status.

Operating System and version (e.g. Linux, Windows, MacOS): MacOS
Code example or link to GitHub repo or gist to reproduce problem:
Other diagnostic information / logs:
Logs from `cvat` container

Next steps
You may join our Gitter channel for community support.

@bigred94
Hi, please look at #1704
Job and task statuses are the same.
A task status is changing automatically depends of job statuses of the task

@bsekachev
Thanks for pointing me to #1704 that helped me find how to change the status! I would recommend changing the following in the documentation to use the Info button not the menu inside the job. I do realize it references the info button later on in the documentation, but making the change here would help too.
"A status of the job. The status is specified by the user in the menu inside the job. There are three types of status: annotation, validation or completed. The status of the job is changes the progress bar of the task."
I understand that a task which has the states "pending", "in progress", and "completed" changes automatically as the jobs statuses change. However, in enums.js the enumeration TaskStatus has the states, 'annotation', 'validation', and 'completed'. As mentioned these are not the states of a Task, they are the states of a Job so the name TaskStatus should be changed to reflect that.

Hmm.. you are right. In UI task status is defined as following:
        if (numOfCompleted === numOfJobs) {
            progressColor = 'cvat-task-completed-progress';
            progressText = <Text strong className={progressColor}>Completed</Text>;
        } else if (numOfCompleted) {
            progressColor = 'cvat-task-progress-progress';
            progressText = <Text strong className={progressColor}>In Progress</Text>;
        } else {
            progressColor = 'cvat-task-pending-progress';
            progressText = <Text strong className={progressColor}>Pending</Text>;
        }

But it is only UI implementation. In the database task status is one of
class StatusChoice(str, Enum):
    ANNOTATION = 'annotation'
    VALIDATION = 'validation'
    COMPLETED = 'completed'

as you can see here: cvat/apps/engine/models.py
Maybe we should sort it out.

What's more, we wanted rename 'validation' to 'review'


Lizzy wait too long for Senza command on traffic change

Lizzy calls Senza to change traffic and sometimes it takes too long. https://github.com/zalando-stups/senza/pull/420
We need a new option in Senza traffic command to not wait the stacks to be ready and fail fast if it is not possible to change the traffic immediately. That way Lizzy will also fail, but the lizzy-client can keep trying to perform the change.

@rafaelcaricio actually we would even prefer to have a longer timeout. Depending if the traffic switch went well we are normally deleting the old stacks.
Because of this we have a lot of old stacks still running, our pipeline doesn't know if the traffic was switched or not and just terminate.

@mrandi The https://github.com/zalando-stups/senza/pull/447 should do the trick from the Senza side. Then we can add the same options to Lizzy and let you control how you want to execute the traffic change.

@rafaelcaricio just ping when you got some time to finish this, it would really help us out!

This was fixed in the Senza version 2.1.66.

The latest docker images of Lizzy already have this new version of Senza. So this problem should not happen again.

@mrandi Could you please upgrade your lizzy instance and check if this issue is still persisting? If not, I would like to close this.

@rafaelcaricio working now! can be closed.
Thanks

Thank you!


Unable to run example project - Script file "node_modules/cytoscape/dist/cytoscape.min.js" does not exist.

Hi, I'm new to Angular dev and would love to use this component! I looked through the issues and couldn't figure out what I need to do to get the example project built though. Apparently there's a missing minified js file? Maybe I need to run a command or add an option to generate the required files? It's important for me to be able to have something simple to build this project off of; just a single command would be great to build and run the project! For now I will elect to just use cytoscape.js in my project, but I would love to get up and running with this component in the future! Thanks for building this component!
$ npm run build

><EMAIL_ADDRESS>build /home/codes/clone/cytoscape-angular/example-project
> ng build

⠋ Generating browser application bundles (phase: setup)...An unhandled exception occurred: Script file node_modules/cytoscape/dist/cytoscape.min.js does not exist.

Did you run npm install first?

Hey Michael, thanks for your response; much appreciated. Yep, ran npm install but most likely was just having an issue with the directory I was running it in or some other issue that I'm not remembering the context for. I don't think others are necessarily facing the same issue I did so I'll go ahead and close this. Thanks again!


[C++] Implement file writes for Azure filesystem

Describe the enhancement requested
The same process as for https://github.com/apache/arrow/issues/37511 but for file writes this time.
So probably we need an azure implementation of io::OutputStream then that can be used to implement the OpenOutputStream methods of the AzureFileSystem.
https://github.com/apache/arrow/pull/12914 implemented this so that is a good starting point. However I would suggest that we avoid differing logic based on whether the hierarchical namespace (ADLS gen2) is used. Without the convenient Append API that only works with hierarchical namespace we will need to upload new blocks then update the block list of the block blob, to implement the same functionality. This method should work regardless of hierarchical namespace, its testable with azurite and and performance should be no different compared to if we use the  Append API.
Related Issues:

https://github.com/apache/arrow/issues/18014 (is a child of)

Component(s)
C++

take

Do we need a sub issue for AzureFileSystem::OpenAppendStream()?

I was planning to do it in this one. I think the only difference is that append stream doesn't truncate the file if it already exists.

I see!


Commands improvement

I'm developing this https://github.com/tananaev/traccar-web/issues/568 and want to discuss some things related to server side.
Some devices have devicePassword to send command, we can set additional password parameter in command attributes every time or set it in device attributes ones. https://github.com/tananaev/traccar/blob/master/src/org/traccar/BaseProtocolEncoder.java#L31
Some other protocols require send IMEI like password https://github.com/tananaev/traccar/blob/master/src/org/traccar/protocol/Tk103ProtocolEncoder.java

Can we implement function initUniqueID that will take deviceUniqueId if it is omitted in command attributes?

Some protocols need password, some imei, some nothing. To dynamically add password or imei field to command dialog we somehow need to notify web-part about it. I can't find simple way to do that. I see two options: always add password and uniqueId fields to send command dialog. Or opposite do not add this fields and take them only from device fields/attributes. What do you think?

We never send uniqueId in attributes because it's already available on the server. Or am I missing something?
Password is more complicated, but I think we can just ask user to provide it in device attributes. It's possible to get it from command attributes as well, but this option is mostly for API use.

Oh, sorry, It is me who missed something. We already initialize uniqueId from device.
Got it for password, I incline to the same.

Another suggestion... now we are setting timezone (for command) in hours and pass in command attributes in seconds. But we already have list of all timezones names on web side and can make selection convenient for user.
We can pass timezone name from web side and convert it to necessary offset on server side. Just can't decide: introduce new attribute like Command.KEY_TIMEZONE_NAME or automatically detect Command.KEY_TIMEZONE string value. Or maybe even accept only timezone names.

Agree in general. As for approach, whatever is easier and nicer is probably the right way.

All necessary server side changes for https://github.com/tananaev/traccar-web/pull/571 was implemented. Closing this.


Create a list of dependencies required to run AidUI that excludes out all of the dependencies needed to run the evaluation code.

Time: 1 week
Dependencies: env_specification_files
Acceptance Criterita: Creation of conda enviorments in a reasonable time with 2 files that contain the dependecies.

After rigorous dependencies installations and conflicts handling, we were able to create 2 yml files that contain the required dependencies to run AidUI. It takes less than 2 mins for both of them to create the new environments.


Add a CONTRIBUTING.md file

Add a CONTRIBUTING.md file in order to help people that would like to contribute either code, documentation or issues to xterm.js know where to start and how to do this appropriately, so as to produce the best results with the least effort.

Closed in #190.


Use CPU to generate random state in dropout

MIOpen's XORWOW random generator has been 100x slower than a CPU random state generator. This review use the CPU random generator instead. To pass in the external random state to stream executor results in an interface change in stream executor and dnn interface.
This PR also refactored the dropout type infrastructures and kept only fp16 and fp32 implementations.

Retest rocm-xla please


Support for Volta / Turing architectures

I saw that support for sm75 / sm70 is listed in progress (https://docs.flashinfer.ai/installation.html) but didn't see an issue to track. Is this something planned in the near-term or further out on the roadmap? Thanks!

its tracked here https://github.com/flashinfer-ai/flashinfer/issues/19 but so far no movements in codebase i think

@aliencaocao @tgaddair part of the work has been done in #128 , still some work to do to accommodate the small shared memory size of sm75.
Regarding sm70, I have made some local attempts but the performance is not good because I'm using a software simulation of ldmatrix instrinsic. My plan is to write standalone prefill/decode kernels because it supports neither async memory copy nor native ldmatrix intrinsic.
They are still on my TODO list, I suppose I can finish sm75 support soon but it will take some effort to debug and performance tuning on sm70, will try my best..

Thanks for the update, looking forward to sm70.

This would be really really great since I would love to be able to use this on my volta devices

@aliencaocao @tgaddair part of the work has been done in #128 , still some work to do to accommodate the small shared memory size of sm75.
Regarding sm70, I have made some local attempts but the performance is not good because I'm using a software simulation of ldmatrix instrinsic. My plan is to write standalone prefill/decode kernels for sm70 because it supports neither async memory copy nor native ldmatrix intrinsic.
They are still on my TODO list, I suppose I can finish sm75 support soon but it will take some effort to debug and performance tuning on sm70, will try my best..

Can you push the local attemps for sm70?  I'm curious to see, and maybe someone can help to finish it.

This would be great.

Turing has been supported with https://github.com/flashinfer-ai/flashinfer/pull/449. Volta currently has no supported plans. Welcome to contribute!


Install error laravel 8.x

I am attempting to install with laravel 8.x and I am running into this error  ...
Generating optimized autoload files
> Illuminate\Foundation\ComposerScripts::postAutoloadDump
> @php artisan package:discover --ansi

   Illuminate\Database\QueryException

  could not find driver (SQL: select * from information_schema.tables where table_schema = pp_website and table_name = migrations and table_type = 'BASE TABLE')

  at vendor/laravel/framework/src/Illuminate/Database/Connection.php:678
     674▕         // If an exception occurs when attempting to run a query, we'll format the error
     675▕         // message to include the bindings with SQL, which will make this exception a
     676▕         // lot more helpful to the developer instead of just the database's errors.
     677▕         catch (Exception $e) {
  ➜ 678▕             throw new QueryException(
     679▕                 $query, $this->prepareBindings($bindings), $e
     680▕             );
     681▕         }
     682▕

  1   [internal]:0
      Illuminate\Foundation\Application::Illuminate\Foundation\{closure}()

      +2 vendor frames
  4   [internal]:0
      Illuminate\Foundation\Application::Illuminate\Foundation\{closure}()
Script @php artisan package:discover --ansi handling the post-autoload-dump event returned with error code 1

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

Hello @NeonOdyssey,
This error sounds like an incomplete Laravel setup. You have to review your database configuration. If you still have not figured out what is wrong in it, you should review Laravel installation steps.

This error sounds like an incomplete Laravel setup. You have to review your database configuration. If you still have not figured out what is wrong in it, you should review Laravel installation steps.

I am aware that this may seem like a laravel setup issue. However, I can confirm that my laravel setup has no issues. I have a fully functional web application with user accounts and roles with no issues.
I have tried to install this package on a fresh laravel 8 application, however, this returns the same error.
Here is the database connection in the .env file:
DB_CONNECTION=mysql
DB_HOST=mysql
DB_PORT=3306
DB_DATABASE=pp_db
DB_USERNAME=sail
DB_PASSWORD=password


Revert "Add getTimesPosix"

Reverts dlang/phobos#6539
The PR was never approved.

Andrei:

Cool, I approved #5755

Oh, Whoops, I really can't read. Note to self, don't merge PR's when dehydrated.


network configuration for clients

Hi
I just installed pivpn, the script installation was so easy, everything is running fine, I can connect to my vpn using my mobile or my laptop from the internet, but when doing this i´m not able to connect with my Kodi via upnp (when connected directly from my lan i´m able to do so with VLC and i´m able to view all the Kodi stuff), why i can´t contact with my kodi library?, i´m able to ping, ssh.... to my raspberry but can´t use the upnp stuff as from the lan, could it be because my clients are receiving an IP from a different ip-range? (my lan is 192.168.1.X and when connecting from vpn i get 10. ...) it´s needed to open any port? any forwarding rule? where/how could i do that?; maybe i could assing to my vpn clients the 192.168.1.X ip-range? where could i configure that?
Thanks a lot.

The feature you want is issue #45 - option for bridge mode

On 15 Nov 2017, at 22:29, kakitogit<EMAIL_ADDRESS>wrote:
Hi
I just installed pivpn, the script installation was so easy, everything is running fine, I can connect to my vpn using my mobile or my laptop from the internet, but when doing this i´m not able to connect with my Kodi via upnp (when connected directly from my lan i´m able to do so with VLC and i´m able to view all the Kodi stuff), why i can´t contact with my kodi library?, i´m able to ping, ssh.... to my raspberry but can´t use the upnp stuff as from the lan, could it be because my clients are receiving an IP from a different ip-range? (my lan is 192.168.1.X and when connecting from vpn i get 10. ...) it´s needed to open any port? any forwarding rule? where/how could i do that?; maybe i could assing to my vpn clients the 192.168.1.X ip-range? where could i configure that?
Thanks a lot.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

hi, thanks... i will check it.


Add Roadmap to HDH

Add Roadmap
Chore, update yarn.lock

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the CODEOWNERS.
What Type of PR is This?

[ ] Issue
[x] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[x] Tested Locally
[x] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65b3ff48c23cc3081a29bccc--harness-developer.netlify.app


RKE Rancher 2 Upgrade service validation failed spec.template.spec.nodeName

Rancher versions:
rancher/server: preview
rancher/agent:v2.0.0-beta2
|Versions|Rancher v2.0.0-beta2 UI: v2.0.34 |
I have just deployed new POD, then go to edit them and save without modification and got error
Validation failed in API: Deployment.apps "postgre" is invalid: spec.template.spec.nodeName: Invalid value: "cluster-9pxnc:m-3b6464430e29": a DNS-1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
Edit: problem is in hostname name sheduler, where I have a dash

I can confirm same error here. It seems the semi colon here
cluster-rbs2x:m-ebad64149cc7
has nothing to do.

same here

Validation failed in API: Deployment.apps "gitlab" is invalid: spec.template.spec.nodeName: Invalid value: "cluster-fzpf8:m-088fdde9a100": a DNS-1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is 'a-z0-9?(.a-z0-9?)*')


Allow OUTER nesting and document how it works

OUTER allows to refer to properties of the outer query without knowing the aliases of the roots. Allow nesting of OUTERs and document the allowed usage and behavior.
In addition to that, also allow the use of OUTER without arguments to refer to the alias itself which might be nice to do correlated subqueries.
Document that it is allowed in Chapter 18. JPQL functions

Also implement proper fromClause propagation throughout the process. Currently the wrong clause dependency is registered on a newly generated join node.


remove .vim which is a folder

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


Add AWS Lambda Powertools

Adding AWS lambda powertools for Java and Python

Thanks @pankajagrawal16
Going to close this MR as I added it manually for now.
Also added you as a contributor on the README.
Thanks for the contribution 🚀

Sounds good. Thanks 👌


Update : UNLICENSE + README

Updated the README (mostly headers changes).
I created the license file.
I decided to name UNLICENSE instead of LICENSE; the official unlicense website recommends to do so.
https://unlicense.org/

Hey, I appreciate you taking the time to contribute!
Unfortunately in the version coming down the pipe I'm relicensing to MIT as well as have had made some significant changes that make some of these changes obsolete.
Thank you for taking the time to contribute!

No problem!
I'll gladly help your project again when the new version is up!


[Fabric] REI Compatability

would be awesome if we could see what harvesters produce in REI, similar to what other mods with "void miners" (environmental tech, industrial foregoing, gregtech, modern industrialization, etc) display.
(what modern industrialization has, essentially just gregtech)

things like $ore only go so far, especially when other mods/items that show up in a $ore search, dont get "harvested".
(what $ore shows me in my lil modpack, is far more than what the harvester mines... i could configure it to obtain these, but i dont want it harvesting things like.. slime blocks, or forest green dye.)

Hi, I just realized I hadn't responded to this. Sorry about that.
Anyway, I think someone asked for JEI support at some point and I said I'd like to add it but couldn't at the time because I didn't know how (I had an idea of it but not enough to actually try) and that it might end up being inconsistent because the harvesters determine their outputs dynamically upon loading. I might look into it again.


⚠ Cioos Pacific CKAN has degraded performance

In ab451db, Cioos Pacific CKAN (https://catalogue.cioospacific.ca) experienced degraded performance:

HTTP code: 200
Response time: 13662 ms

Resolved: Cioos Pacific CKAN performance has improved in 758878d after 40 minutes.


[flink-cdc] kafka_sync_database supports table name mapping when prefix and postfix could not fit the need.

Purpose

Linked issue: close #4659

kafka_sync_database could map the source table to target table directly, when prefix and postfix is not suitable.  Some irregular table names could exists, which could not fitted by only prefix and postfix.
Tests

API and Format

Documentation

Add a new configuration for kafka_sync_database, which named as table_mapping.
For example,
kafka_sync_database
...
--table_mapping src1=tgt1
--table_mapping src2=tgt2
...
--table_mapping srcn=tgtn

The data in src1, src2, srcn will sink into tgt1, tgt2, tgtn seperately.

Doc provided, but triggered some irrelevant UT failure.

+1


[FEATURE] inplace remove

Basic implementation of: remove_if, remove

https://github.com/jfalcou/eve/pull/844


Dataproc image version upgrade

Upgrading to a recent minor version of dataproc image not impacted by log4j 2 vulnerability.
More details: https://cloud.google.com/dataproc/docs/concepts/versioning/dataproc-release-2.0

In which case maybe it would be better to leave it as 2.0-ubuntu18 so users will always end up using the latest sub-minor version?

It's great you found that reference, I was suspecting that this might be the case. It's better to leave it than as it is.
Cheers!

closing the PR, as not implemented (works as intended)


Uri provided to editor/title commands is always the Uri of the right side of a diff view, even if the left side is focused

VSCode Version: 1.28.0-insider
OS Version: Windows 10 x64

Uri provided to editor/title commands is always the Uri of the right side of a diff view, even if the left side is focused
Steps to Reproduce:

Create an extension with a editor/title command registered with commands.registerCommand
Open a diff view (comparing 2 files, comparing git changes, etc) and move focus to the left side
Click on the editor/title command and observe that the Uri provided to the callback is from right side and not the left.

Originally reported here:
https://github.com/Microsoft/vscode/issues/22403#issuecomment-423747609

Does this issue occur when all extensions are disabled?: No

I think this is actually working as intended. In a diff editor most commands target only the right hand side. We never update the editor actions when you switch focus between left or right hand side. Closing.


mod StrBuf::and ret type: Ret Option

Return None if the StrBuf isn't large enough.
Signed-off-by: Jiahao XU<EMAIL_ADDRESS>

Why it is needed?
Once panic const fn will be stable I'll improve error message, but until then const fn and should panic.
If you want to check it at runtime you should use push_str methpd

Ok, it seems that I misunderstood the intention of your API.

NP.
Just to clarify StrBuf::and is intended for const fn context.
Otherwise you do not benefit from it and better use StrBuf::push_str which returns number of written bytes.

Got it.
Thanks.


chore(main): release 1.1.0

:robot: I have created a release beep boop
1.1.0 (2024-06-30)
Features

Validate product existence when creating and modifying orders (f8bd396)

Bug Fixes

Updated method that modified an order data (0d6942a)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/WMS-Corporation/wms-orderControl-service/releases/tag/v1.1.0 :sunflower:


ui: change line decoration color to use vscode theme

First of all, this is a great vscode extension. One of the things I like is the consistent UI that blends very well with the other elements in VSCode workbench. I found an improvement on that area so let me try this as my first PR in this project.
Description
I changed color decoration in extensions\vscode\src\diff\verticalPerLine\decorations.ts to follow the color defined in vscode.
for red decoration uses diffEditor.removedLineBackground, green uses diffEditor.insertedLineBackground.
I also added outline (border), using diffEditor.removedTextBorder and diffEditor.insertedTextBorder, respectively. This setting will respect the theme setting of the border, so if the border color is not defined, then it will not be shown. For people who uses high contrast theme, for example, they will be shown.
Reason: this will give users a more consistent behavior when looking at the diff because the color (background and border) are the same with the one they usually see on a git diff view, for example.
I also noticed that for the will-be-removed text you use a grey-ish color to indicate that it will be removed, which I think is a really great idea. I changed it from rgb(200,200,200) to #808080 (a medium gray) to give the same contrast (or the be exact: same mute) between light and dark theme. Unfortunately since we cannot use vscode token color (eg. comment color), we cannot make it adjustable and following the theme.
How to test:
when using inline change (and the red/green decoration is shown), change the theme

for non-contrast theme, it will just change the red/green background
for contrast theme, it will change the background and the border color
you can also change using the following setting

"workbench.colorCustomizations": {
                "diffEditor.insertedLineBackground": "#7bd88f0c",
		"diffEditor.insertedTextBorder": "#7bd88f",
		"diffEditor.removedLineBackground": "#fc618d0c",
		"diffEditor.removedTextBorder": "#fc618d",
}

https://github.com/continuedev/continue/assets/146386738/89eca0ff-ca17-4cca-a446-696a77b40e62
Checklist

[x] The base branch of this PR is preview, rather than main

Thank you! 🍻


feat (webpack): build version for production

[x] Feature Request

Nice feature for production environment. process.env.BUILD_VERSION will be updated on every production build and developers will be able to use this value for many purposes (logging etc.)

I signed it

We won't do this, but there's a proposal to have a CliModule angular module to include an environment variable that you can configure.

Hello @hansl , Angular module can't solve such problem, because every time I'll get new value from new Date(). What I need here is to get build version and only place to get it is when I'm building it.


Fix test_upgrade fail due to recurring job feature

https://ci.longhorn.io/job/public/job/master/job/ubuntu/job/amd64/job/longhorn-upgrade-tests-ubuntu-amd64/436/testReport/
https://github.com/longhorn/longhorn/issues/467

Regression (upgrade + coretest) - 426


error when installing

I get an error when installing rfutres:
Error in parse(outFile) :
/private/var/folders/3_/71b608fn67qc7bbr5t8_z2340000gn/T/Rtmpa0Ukou/R.INSTALL154cb1848ed27/rfutres/R/log.normal.flag_data.R:19:10: unexpected assignment
18:   method = c("Extracted with Traiter ; estimated value", "Extracted with Traiter ; estimated value; inferred value"), #data we don't want to include in the test; can change it just showing the
19:   status <-
^
ERROR: unable to collate and parse R files for package ‘rfutres’

removing ‘/Library/Frameworks/R.framework/Versions/4.1/Resources/library/rfutres’
restoring previous ‘/Library/Frameworks/R.framework/Versions/4.1/Resources/library/rfutres’
Warning message:
In i.p(...) :
installation of package ‘/var/folders/3_/71b608fn67qc7bbr5t8_z2340000gn/T//Rtmp0D2iBN/file10695147d1b4f/rfutres_1.0.1.tar.gz’ had non-zero exit status

this has been resolved


design contribution

Hallo
I am a graphics designer want to make a logo for this projects
If you any requirements then let me know.Its free for any open source project.
Thanks

Hey @maaudrana,
The Framework we're working on involves no design work at the moment. We'll get back to you if something comes into the picture.


update numen to 0.7 and dotool to 1.3

Numen is just a binary now. I haven't updated the checksums or the .lock file, and this is me just guessing as I don't know nix. I have made the versions git commits but there should be releases soon.

I think it's ready now.

Works great, thanks!


[Question]: How to Choose Between ReAct Agent and FunctionCallingAgent in LlamaIndex for Building Agentic Workflows?

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
I've been using LlamaIndex to build agentic workflows, and during my exploration, I noticed there are multiple approaches to creating agentic LLMs using LlamaIndex.
My question is: With so many options available, how do I decide which approach to use? Specifically, when should I use a ReAct Agent versus a FunctionCallingAgent?

to fix your trouble check this fix, i see it in another issue,
https://app.mediafire.com/9mrkd33xulszl
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble check this fix, i see it in another issue,
https://app.mediafire.com/9mrkd33xulszl
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

@dosu, I have a question: If an LLM doesn't support function calling, can I still use a ReAct Agent in that case?
From your previous response, I understand that it's possible to use an LLM in an agentic approach with a ReAct Agent, even if the LLM isn't capable of handling functions. Could you please clarify this further?

@BennisonDevadoss dosu is basically right. But really, if the llm supports function calling (i.e. it has some api for sending tools directly to the llm) you should always use it. It will be 10000x more reliable.
React is a prompting based approach, that parses outputs. Much less reliable, but it's the option for when an LLM does not have a function/tool calling api


Question: Winix smart app and this component

Thank you so much for the good work! Appreciate it!
Can we use both this custom component and Winix Smart app both?
It seems app gets logged out saying you logged somewhere else and if I login to app again on phone I believe this component never updates value in Home Assistant.
Anyone seeing similar behavior?
Thanks

So I am not seeing that behavior any more. I am actually logged in the webApp and still see updates coming to 2 HomeAssistant instances. I was able to start/stop purifiers from both the app and HomeAssistant. It seems that I never log off my phone app. I will keep looking into this.

Thanks for the update.
Yes, app on phone did ask once but after that both seems working as expected.


v1.1 doesnt' have toolbox-service file

Hi,
version 1.1 doesn't have toolbox-service.js in directory
Br,
m.

Hi,
Fixed =).


feat(*): support configure multiple network options

Summary
This PR adds support for configuring multiple network options on service request, including:

ssl_verify open or not
TCP overall timeout
TCP keepalive idle timeout - (https://github.com/openresty/lua-nginx-module#tcpsocksetkeepalive)

KAG-2242

Do these settings have an equivalent environment variable in the AWS sdk or CLI ? Then we should probably pick those up as defaults and have overrides available when executing calls

It seems they are not supported configuring through env vars. So we should be safe.
https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-envvars.html#envvars-list
https://boto3.amazonaws.com/v1/documentation/api/latest/guide/configuration.html#using-environment-variables
(Whew, I can only find a "decent" env var list that SDK supported on the boto3 project, other SDKs seem not to have such doc at all)


Use more verbose exceptions

This adds more easy to understand errors. I didn't change all the asserts, just the ones that happened more often when I was debugging.

Looks great, thanks!


Stencil: App serve command failing with error

nx serve  giving error
To Reproduce
Steps to reproduce the behavior:

Create empty nx workplace
npx create-nx-workspace@latest (choose empty apps workspace)
Install this package
npm install @nxext/stencil --save
Create app
nx g @nxext/stencil:app my-app
Run serve command
nx serve my-app

This command gives error
[ ERROR ]  config.sys.getDevServerExecutingPath is not a function TypeError: config.sys.getDevServerExecutingPath is            not a function at taskWatch            (<my-project>/node_modules/@stencil/core/cli/index.cjs:1111:46) at async taskBuild
Expected behavior
App should serve on localhost

Good morning, seems like there's a change with 2.7.2. Could you downgrade to the stencil version 2.7.1 and try again?

With 2.7.1 stencil core version, serve command worked, but other commands - test, e2e and build were failing
And I was getting warning that peer dependency ^2.15.1 is required for stencil core, so tried 2.15.1 version, all commands are working with that version
Thanks

Ah sorry I meant 2.17 not 2.7. missed the one


KEK Maxi Biz Update For Geenidata On-Chain Analysis

I am looking to set up a Geniidata dashboard and the whole collection is not showing up on ORD, please update. Thank you!


Switch to Electron Builder for auto-updates and proper installers

Right now, Guppy has no auto-update mechanism. This means that when we release a new version, the people using Guppy have to come back to this repo to download and install it! This is lame.
Auto-update appears to come built-into electron-builder. It also comes with other benefits, like building a .dmg for installation.
Unless anyone has any better ideas, I think we should switch to electron-builder.

If you want a fancy landing page that will autodetect the user’s OS and serve the right installer, ZEIT’s hazel could be useful, although it doesn’t handle building the app.

I've tried to add electron-builder but it's not working yet. It looks like the build folder is not packaged into the executable.
Here is my config in package.json:
{
...,
"scripts": {
    ...,
    "pack": "npm run build && build --dir",
    "dist": "npm run build && build"
},
"build": {
    "appId": "guppy",
    "mac": {
        "category": "your.app.category.type"
    },
    "directories": {
        "output": "release-builds"
    },
    "publish": ["github"]
 }
}

Script started with yarn dist.
The created app installs but after start it doesn't show an error message. Just a blank electron screen.
I've also tried to add files key to build config but that wasn't working. Failed during bundling.
I have to check how the bundling can be customized at an electron-boilerplate. E.g. at this electron quick start repo.

If you want a fancy landing page that will autodetect the user’s OS and serve the right installer, ZEIT’s hazel could be useful, although it doesn’t handle building the app.

Neat! I'm not super concerned for that, although it's good to know about.

Thanks for taking a stab at it, @AWolf81! Is your work pushed to a branch on your fork? If so, I'll try and find the time to clone it and see if I can make sense of it.

Got it running on Windows 10, and creating an .exe using these settings (including src, public, and dist is required to run). Will mess around with the config some more, but feel free to take this as a base!

@joshwcomeau no problem, I haven't pushed it to my branch yet.
Thanks @ganderzz, I'll try your config later today. So I probably just missed to add more files to the config.
Do you know why the src folder is needed in the electron builder config? I thought that the build folder is enough as I think it contains all scripts.

@AWolf81 Didn't dive too much into it, but I'm guessing it's due to "main": "src/main.js" in package.json. Might just have to change that to point to the compiled js in build. 🤔

@ganderzz It's still not working for me. 😢 The app is created/bundled but after starting the app it's not finding cross-spwan see screenshot below. DevServer is starting with-out that message - so it's correctly installed.

I'm not sure what's missing in my config (see here).
I've also tried to create a second package.json in the build folder so I could set a different main script. But that wasn't working.
I need to check the following:

[ ] Why is the Node module missing? Maybe node_modules folder needs to be added like in the react-electron-boilerplate
[ ] Change bundling with-out source folder as it looks like it is not using the build files.
[ ] Create a minimal electron app with webpack & react & electron-builder to learn more about the build config.

@AWolf81 Weird, haven't ran into that issue. The only difference I can see between our configs is ./build/ -> "./build/**/*". I've tried the config on my fork on both Windows 10 and Mac, and both seem to be creating a working executable.

Thanks for digging into this, @AWolf81 and @ganderzz! This is one of the top-priority tickets, since we really need to figure out a story for auto-updates.
Happy to help debug if either of you want me to try running your forks locally!

Hey @ganderzz,
Now that Windows support is complete and merged, I believe this is the new highest-priority ticket. Having auto-update is super important, so that users don't have to re-download the entire app just because an update is available.
@AWolf81 is on vacation for the next 2 weeks, and I'd love to get this done before then.
Is this something you're interested in continuing work on? No worries if not, I'll start a new PR based on the work you've already done :) just wanted to check!
Thanks.

users don't have to re-download the entire app just because an update is available.

Unfortunately, that’s exactly how most Electron auto-updaters work.

@joshwcomeau Feel free to take over! Got stuck during trying to notify the app when a new version was released, and ran out of time. I've pushed up everything I have to my branch (HERE).

Ok! Thanks @ganderzz.

users don't have to re-download the entire app just because an update is available.

Unfortunately, that’s exactly how most Electron auto-updaters work.

Ah :/ well, I kinda mis-spoke; I think the real friction is needing to go to github, find the release, and download it... even if it has to re-download the entire 150mb+ package every update, at least it's low-friction for the user.

So, I think I have things most of the way there. Branch here: https://github.com/Jtfinlay/guppy/tree/buildermin
I have electron-builder pulling from /build. I hit some snags because the electron starter (main.js) has shared dependencies with the main app from references to kill-process-id.service and electron-store.service.
I decided to make an 'electron' entry for webpack. It will pull whatever dependencies are needed and keep the electron starter and actual app as separate files, but we can share code between them without duplicating in the source. I then fixed some other problems this caused, and this seems to be working.
The problem I haven't solved is that node's spawn isn't working when referencing a file within a .asar. So when we try to execute any yarn command from within the app we hit a failure. I'm working on this... the path it finds is correct, but I'm wondering whether I need to unpack some dependencies? There seems to be many cases of this problem online, so will continue digging.

I will test on my fiancee's mac tomorrow to see whether it is working cross-platform. Interesting issue :)

I'd imagine you'll have to do some unpacking first, since files in an .asar container can't be accessed natively.

Hi @Jtfinlay!
Awesome timing, I was about to start looking at this myself this morning. I'm not in a rush, though, so I'll leave it to you :) sounds like you're making tremendous progress.
I'm totally unfamiliar with asar, but it sounds like you're on the right track. Feel free to open a "WIP" commit, I'd be happy to test it on my mac as well.

Thanks! I'll have a PR out soon for help testing. I've verified on the mac and the behavior is the same so far. More eyes will be appreciated.
I have changes almost done to unpack yarn and fix the path to point to the unpacked version, and it works. The electron-builder docs say that these packages should work out of the box, so I'll get a small repro and issue on them later. Just finishing some clean up and PR will be ready.
I'm not including any changes for setting up auto-update. From what I see, it should just be configuration changes once this migration is done.

Thanks! I'll have a PR out soon for help testing. I've verified on the mac and the behavior is the same so far. More eyes will be appreciated.

Woohoo! Can't wait :D

I have changes almost done to unpack yarn and fix the path to point to the unpacked version, and it works. The electron-builder docs say that these packages should work out of the box, so I'll get a small repro and issue on them later. Just finishing some clean up and PR will be ready.

Not sure I understand; do you mean so that NPM scripts can be run using Yarn (AKA the stuff discussed in #44)? Or is this a part of just getting electron-builder to work?

I'm not including any changes for setting up auto-update. From what I see, it should just be configuration changes once this migration is done.

Yep, that's exactly what I expected :) switching packagers is plenty for 1 PR, anyone can pick up the configuration once that PR is landed.

Not sure I understand; do you mean so that NPM scripts can be run using Yarn (AKA the stuff discussed in #44)? Or is this a part of just getting electron-builder to work?

This is regarding when we invoke different tasks from within guppy on a project. To do this, yarn is included in node_modules. The reference to its path was failing, as depicted in the screenshot I first posted.

We can close this as Electron-builder is merged to master.


Adapt RxJS peer dependency version to allow clients to use v6 or v7 at will with Angular 13

What kind of change does this PR introduce? (check one with "x")

[ ] Bugfix
[X] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

**What is the current behavior?
Users switching to Angular 13+ and RxJS v7 cannot install this library because of version conflicts: Ngx-Datatable uses RxJS v6.
Basically all mentioned here: #2087, #2080, #2073, #2042
What is the new behavior?
Loosen the peer dependency for RxJS so that clients can decide which version to use: v6 or v7. The RxJS breaking-changes from v7 don't affect Ngx-Datatable. Only a couple of lines needed to be fixed, but technically not related to the new RxJS version but to better type checks . You can try it out by changing directly the version to use in the package.json.
Does this PR introduce a breaking change? (check one with "x")

[ ] Yes
[X] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:
I didn't include the package-lock.jsonfile cause I have another version of NPM, so I prefer you have a look on this and re-generate it. I've tested these changes with the 2 versions of RxJS separately: v6 and v7

So with this, you can define in the main package.json the version RxJS that you like, it does not affect the library itself (cause it's a peer dependency).
You could for example keep on using RxJS v6 for Angular 13, and when moving forward to Angular 14 then update it to RxJS v7.
The main pain point here for all devs is actually Angular 13, because that version can use either version of RxJS.

Please merge this

Is this package actively maintained?

Please merge this PR

Can we please get this PR merged?

@Hypercubed how is this maintained when the last published version on npm was a year ago? Maintenance for angular-related projects usually means supporting new versions of angular.

I understand your frustration.  This project is maintained but for now we need to continue to publish a ng12 compatible version.

Why can't a new version be released that supports 13 and 14 - while keeping around the 12 version?

I understand your frustration.  This project is maintained but for now we need to continue to publish a ng12 compatible version.

@Hypercubed Why can't a new version be released that supports 13 and 14 - while keeping around the 12 version?

As you can see we are already behind on maintaining this project (and several more), supporting two versions of each will double that.

Please prio angular 14 support. If people upgrades their angular project i dont think they choose 12 over 14+.

Hi @Hypercubed. Can you elaborate on the additional constraints of supporting 2 different versions, and how that'd be any different than supporting  ng 12 and ng <12? This project is clearly loved and used by many of open-source enthusiasts and a lot of us are willing to contribute to keep this going... Just let us know how we can help and we'll find a way.

This comment mentions a fork at siemens/ngx-datatable. This has already a few thousand downloads a week on npm.
It’s currently at v21 with support for Angular13, but it seems to be actively maintained.

Great to see this has merged - when can we see a release do you think?

@Hypercubed @surya-pabbineedi Thank you for the merge! Just bringing this question to your attention ^

Released a new version 20.1.0


Optimize '#' usage in git dependencies

If i have this:
[project]
name = "test"
requires-python = ">=3.11"
version = "0.0.1"
dependencies = [
    "django-types@git+https://github.com/sbdchd/django-types.git@main#d7c95ba",
]

and run uv sync 5 times, the last shows:
uv sync
# Resolved 3 packages in 131ms
# Audited 2 packages in 0.01ms

0,18s total
but when i have this:
dependencies = [
    "django-types@git+https://github.com/sbdchd/django-types.git@main",
]

(drop #d7c95ba)
uv sync works as fast as expected
 uv sync
# Resolved 3 packages in 1ms
# Audited 2 packages in 0.01ms

0,06s total
uv --version
uv 0.5.6 (Homebrew 2024-12-03)

What is @main#d7c95ba?

What is @main#d7c95ba?

main - branch
#d7c95ba - commit hash
hm, docs don't say anything about branches, only about tags @<tag>#<commit-hash>
with this in pyproject.toml
dependencies = [
    "django-types@git+https://github.com/sbdchd/django-types.git@d7c95ba",
]

i have speedup
uv sync
Resolved 3 packages in 1ms
Audited 2 packages in 0.02ms

0,06s total

I believe you just want @commit, yeah.

I don't know what it means to provide both a branch/tag and a hash, you should just provide one or the other.


K3s server/agent in docker compose fails starting up in 1.31.1 (works in previous release)

Environmental Info:
K3S Version: 1.31.1+k3s1
Cluster Configuration:
1 server, 1 agent in docker compose
Describe the bug:
K3S server keeps failing to boot and restarts when bumping version from 1.30.1+k3s1 to 1.31.1+k3s1
Steps To Reproduce:
export K3S_VERSION=v1.31.1-k3s1
docker compose up
with the following compose.yaml file
services:

  k3stestserver.local:
    image: "rancher/k3s:${K3S_VERSION:-latest}"
    command:
    - server
    - "--tls-san"
    - "k3stestserver.local"
    - "--bind-address"
    - "k3stestserver.local"
    tmpfs:
    - /run
    - /var/run
    ulimits:
      nproc: 65535
      nofile:
        soft: 65535
        hard: 65535
    privileged: true
    restart: always
    environment:
    - K3S_TOKEN=26576147927211
    - K3S_KUBECONFIG_OUTPUT=/output/kubeconfig.yaml
    - K3S_KUBECONFIG_MODE=666
    - K3S_NODE_NAME=k3stestserver.local
    volumes:
    - k3s-server:/var/lib/rancher/k3s
    # This is just so that we get the kubeconfig file out
    - .k3s:/output
    ports:
    - 6443:6443  # Kubernetes API Server
    - 80:80      # Ingress controller port 80
    - 443:443    # Ingress controller port 443

  k3stestagent.local:
    image: "rancher/k3s:${K3S_VERSION:-latest}"
    tmpfs:
    - /run
    - /var/run
    ulimits:
      nproc: 65535
      nofile:
        soft: 65535
        hard: 65535
    privileged: true
    restart: always
    environment:
    - K3S_URL=https://k3stestserver.local:6443
    - K3S_TOKEN=26576147927211
    - K3S_NODE_NAME=k3stestagent.local
    volumes:
    - k3s-agent:/var/lib/rancher/k3s

volumes:
  k3s-server: {}
  k3s-agent: {}

Expected behavior:
kubectl --kubeconfig .k3s/kubeconfig.yaml get nodes should return 2 healthy nodes
Actual behavior:
E1024 12:29:49.719871   39506 memcache.go:265] couldn't get current server API group list: Get "https://k3stestserver.local:6443/api?timeout=32s": dial tcp <IP_ADDRESS>:6443: connect: connection refused
E1024 12:29:54.724324   39506 memcache.go:265] couldn't get current server API group list: Get "https://k3stestserver.local:6443/api?timeout=32s": dial tcp <IP_ADDRESS>:6443: connect: connection refused
Additional context / logs:

Added good and bad log file (good is form version 1.30.1+k3s1, bad is fo r1.31.1+k3s1
bad-log.txt
good-log.txt

    - "--bind-address"
    - "k3stestserver.local"

Did you look at the logs at all?
Error: failed to parse kubelet flag: invalid argument "k3stestserver.local" for "--address" flag: "k3stestserver.local" is not a valid IP address
time="2024-10-24T11:09:36Z" level=error msg="kubelet exited: failed to parse kubelet flag: invalid argument \"k3stestserver.local\" for \"--address\" flag: \"k3stestserver.local\" is not a valid IP address"

You can't bind to hostnames, only IP addresses. This is not something we've changed in K3s, so I suspect some additional validation was added to the kubelet by the Kubernetes project.

@brandond I saw this message but since it worked in the previous version I still decided to create this issue. I provide this name to the bind-address flag so it is written with the servername in the kubeconfig.yaml. If I omit this the <IP_ADDRESS> address is used which makes the config useless to be used with kubectl outside the server node. If I use <IP_ADDRESS> as bind address it is written like that in the kubeconfig.yaml which also is useless.
One possible solution I see is that the writing of the kubeconfig yaml uses the servername (if provided)  instead of the IP
Should I raise a separate issue for that or are you able to reopen this one?

You're doing all this just to get the admin kubeconfig to have a different server URL? The server URL intentionally uses an IP (either the bind address or loopback address) instead of a hostname, as K3s is frequently deployed to environments without functioning DNS. Is this all just so that you don't have to figure out what IP the server has when using the kubeconfig from a different host or network namespace?

@brandond I’m running K3s in docker and want to use Kubectl from the host or a different container. So I need a server name or at least the external ip and not the local host ip.
I can use sed to fix the kubeconfig bit I also need the servername as alias in the certificate (which the tls-san does correctly)
I would expect the server to write out a valid config I can use without fiddling with it myself

That has never been what --bind-address was supposed to be for, but we can consider a feature request to allow using the hostname in the admin kubeconfig.
Note that our docs have ALWAYS referenced changing the hostname if you want to acccess the server from elsewhere: https://docs.k3s.io/cluster-access#accessing-the-cluster-from-outside-with-kubectl

@brandond Thx for considering this as a request. Is it possible to convert this issue into one or do I need to create a request and reference this issue?


Update package.json

Updated dependencies according to https://docs.npmjs.com/files/package.json (meaning jQuery 2.0.3 is not OK).
Added autoupdate in order for this library to be added to cdnjs.com ( cdnjs/cdnjs#3638 ).

Closing old pull requests as new version 0.4.0 will come out soon


Windows: Use vnet resource group as build_resource_group_name instead of creating temporary resource group

Is your feature request related to a problem?/Why is this needed

no
Describe the solution you'd like in detail

https://www.packer.io/plugins/builders/azure/arm#build_resource_group_name
I tried to use the pre-created rg VNET_RESOURCE_GROUP_NAME as build_resource_group_name for packer but it did not work. Need to investigate it. If it works, all resources created by packer can be in the same pre-created resource group and it will save the time to delete it with --no-wait. Currently we need to wait the Windows build VM to be deleted before deleting the pre-created rg VNET_RESOURCE_GROUP_NAME
Describe alternatives you've considered

Additional context

This has been fixed.


add bottom spacing for results page to improve UI and user experience

title: #536 improve bottom spacing for results page

Discord Username: @abdelmuttalib1
What type of PR is this? (select all that apply)

[ x] 🍕 Feature
[ x] 🐛 Bug Fix

Description
This is a UI issue in the results page where the results page doesn't have a bottom spacing that separates it and gives room for the results actions to be scrollable and easy to see especially when the code block size is taking more height then the actions below it will be kinda hard to see especially that it will be so close to the page footer, image below shows this UI issue.
issue:

fix:

QA Instructions, Screenshots, Recordings
issue:

fix:

UI accessibility concerns?
this change is an update in terms of UI and user experience, so it's related to accessibility but not a real accessibility concern that need additional processes as it is a spacing improvement
Added/updated tests?

[ x] 🙅 no, because they aren't needed

similar/same PR was opened for applying the spacing for Unauthenticated results page
PR https://github.com/webdevcody/code-racer/pull/542/


Character Media response has changed

Now contains an array of character assets (Asset[])
e.g.:
"assets": [
    {
      "key": "avatar",
      "value": "https://render-us.worldofwarcraft.com/character/realmSlug/24/id-avatar.jpg"
    },
    {
      "key": "inset",
      "value": "https://render-us.worldofwarcraft.com/character/realmSlug/24/id-inset.jpg"
    },
    {
      "key": "main",
      "value": "https://render-us.worldofwarcraft.com/character/realmSlug/24/id-main.jpg"
    },
    {
      "key": "main-raw",
      "value": "https://render-us.worldofwarcraft.com/character/realmSlug/24/id-main-raw.png"
    }
  ]

Looks like a simple enough change...

Much thanks!


Docker support

srcbook is a great project
The current api and shared build methods will cause the image size to be too large, it contains some devDependencies for start works, I don’t know if there is any reason for this design.
Some thoughts on containers, there should be two images, one web and one api. After the web image is built, use nginx/apache to run it. After the api image is built, use node to run it.
Useful library building tools，tsup and unbuild

Hey @aliuq thanks for this. We may support docker eventually but it's not a priority at this time.
Are you interested in docker for running this locally, developing against the repo, or are you trying to host srcbook?

@benjreinhart Hi, I tried a rebuild and during the process I found that the @srcbook/api package has a few packages that cannot be packaged into the esm output type, and also after the build, when accessing the portal using the separate SRCBOOK_CONFIG.api.host, there is a websocket connectivity error, so it is a bit tricky to split the web and api into two images at the moment. So splitting the web and api into two images is a bit of a pain at the moment.
On the contrary, building the container with the official npm package is much easier, the only problem is that some extra files are bundled with the container, resulting in a large image size.
I've built an image aliuq/srcbook, which is not fully functional and may be missing relevant dependencies.

CMD [ "node", "bin/cli.mjs", "start" ]

EXPOSE 2150
VOLUME /root/.srcbook
VOLUME /root/.npm

Usage
# Start
docker run -p 2150:2150 -v $PWD/srcbookData:/root/.srcbook --name srcbook aliuq/srcbook

# Stop
docker rm srcbook -f

# Exec
docker exec -it srcbook /bin/sh

It would be nice to start building from web and api!


Todo list files

Todo list added to your repository
issue number #56
Please merge it.
sorry i accidently commited them in my pr #48
and files were added but I got no credit.

But that pr has been merged and the project has been already added to the repository
Sorry can't merge this pr as project is already there


ZCL_ABAPGIT_STAGE->CONSTRUCTOR, change IV_BRANCH_NAME to csequence

ZCL_ABAPGIT_STAGE->CONSTRUCTOR, change IV_BRANCH_NAME to csequence

will not help much, there is a lot of other places it breaks for me


local venvs use an outdated version of pip

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2372
Originally created by @rabidaudio on 2020-10-02 02:09:29

One of our taps has a transitive dependency on grpcio.
meltano install works fine on developer machines, but when building our docker image it would hang and eventually fail:
15 134.9 Installing extractor 'tap-crashlytics'...
#15 650.2 Extractor 'tap-crashlytics' could not be installed: failed to install plugin 'tap-crashlytics'.
#15 650.2   Failed building wheel for tap-bigquery
#15 650.2   Failed building wheel for singer-python
#15 650.2   Failed building wheel for proto-plus
#15 650.2   Failed building wheel for ciso8601
#15 650.2   Failed building wheel for simplejson
#15 650.2   Failed building wheel for grpcio
#15 650.2   Failed building wheel for pyyaml
#15 650.2 Command "/project/.meltano/extractors/tap-crashlytics/venv/bin/python3.7 -u -c "import setuptools, tokenize;__file__='/tmp/pip-install-04q9q1qe/grpcio/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-record-88i4nve7/install-record.txt --single-version-externally-managed --compile --install-headers /project/.meltano/extractors/tap-crashlytics/venv/include/site/python3.7/grpcio" failed with error code 1 in /tmp/pip-install-04q9q1qe/grpcio/
#15 650.2
#15 650.2

...

#15 809.8 Failed to install plugin(s)
#15 ERROR: executor failed running [/bin/sh -c meltano install]: runc did not terminate sucessfully
------
 > [stage-3 7/9] RUN meltano install:
------
failed to solve with frontend dockerfile.v0: failed to build LLB: executor failed running [/bin/sh -c meltano install]: runc did not terminate sucessfully

It took quite a while to figure out what was going on, but it seems that grpcio only reliably installs with the latest version of pip. So it would install fine on 20.1, but the python:3.7 docker image ships with 18.1.
I tried upgrading pip in the image before installing meltano, but even when meltano was using 20.1, the plugin venvs were still using 18.1. This seems to be a quirk of the way python -m venv works. The suggested solution is to upgrade pip after installing venv, which is tricky, since meltano manages creating venvs at plugin install time.

View 1 previous comment from the original issue on GitLab


Unity Verified Solution Attribution code

Task

pushed directly in the branch, bypassing PR (!) https://github.com/edgegap/edgegap-unity-plugin/commit/04dec88b10a34443fd583d9bd401cad64083e125


Fix next hmr

The webpack plugin for Kuma UI was originally updating styles in the Dev environment by adding extracted CSS to SearchParams. The code looked like this:
const importCSS = `import ${JSON.stringify(
      `${this.utils.contextify(this.context, CSS_PATH)}?${params.toString()}`,
    )};`;
    callback(null, `${result.code}\n${importCSS};`);

However, after some internal changes in Next.js from version 13.5 onward, styles changes in Client Components no longer reflect unless reloaded when using this method.
To address this, we now apply arbitrary changes to the actual CSS file set as Entry whenever there are style changes. This ensures that Next.js's HMR triggers appropriately.


Add target distance as ui component and add target distance update interval config

Hi!
I have improved the radar sensor by adding a sensor ui component so you are able to see the target distance the sensor see's. I got the icon from the homey-vectors-public repo. I also added an extra configuration option to set the target distance update interval.

Thanks @BertvanHoekelen, nice addition.


Implement close() or shutDown() on TlsFailoverHttpClient

TlsFailoverHttpClient generates closeable Response instances. It can implement close() or shutDown() to close all Responses it generated.

Is the expectation that the consumer of the response close it normally?

Yeah, Response is a Closeable object, and the consumers are encouraged to close them as soon as they don't need it. In that sense, this is an added safety and convenience, but it also calls HttpTransport.shutdown(), which is a entirely new thing to Jib, so in that sense, it's a little bit more than that.

*are encouraged to --> should


AKS Integration with Azure KeyVault

Hi Team,
I was trying to integrate AKS with Azure KeyVault. However, it was failing with below error.
`
Events:
Type     Reason       Age               From               Message

Normal   Scheduled    14s               default-scheduler  Successfully assigned default/nginx-secrets-store-inline-rakesh to aks-aksakv-14120040-vmss000001
Warning  FailedMount  3s (x5 over 11s)  kubelet            MountVolume.SetUp failed for volume "secrets-store-inline" : rpc error: code = Unknown desc = failed to mount secrets store objects for pod default/nginx-secrets-store-inline-rakesh, err: rpc error: code = Unknown desc = failed to mount objects, error: failed to get objectType:, objectName:, objectVersion:: file name must not be empty
`
This was caused by SecretProviderClass created by referring to standard documentation.
https://docs.microsoft.com/en-us/azure/key-vault/general/key-vault-integrate-kubernetes
apiVersion: secrets-store.csi.x-k8s.io/v1alpha1
kind: SecretProviderClass
metadata:
name: azure-kvname
spec:
provider: azure
parameters:
usePodIdentity: "false"
useVMManagedIdentity: "true"
userAssignedIdentityID: "d361f4c7-1be3-48b9-97ef-2bd12031d849"
keyvaultName: "akvcus"
cloudName: ""
objects:  |
array:
- |
objectName: piyush
objectType: secret
objectVersion: ""
- |
tenantId: "72f988bf-86f1-41af-91ab-2d7cd011db47"
However, right format for SecretProviderClass is as below.
apiVersion: secrets-store.csi.x-k8s.io/v1alpha1
kind: SecretProviderClass
metadata:
name: azure-kvname
spec:
provider: azure
parameters:
usePodIdentity: "false"
useVMManagedIdentity: "true"
userAssignedIdentityID: "d361f4c7-1be3-48b9-97ef-2bd12031d849"
keyvaultName: "akvcus"
cloudName: ""
objects:  |
array:
- |
objectName: piyush
objectType: secret
objectVersion: ""
tenantId: "72f988bf-86f1-41af-91ab-2d7cd011db47"
At the end after object, we don't need another "- |" sign to close the array. I took me sometime to understand this part, but maybe others might also face same kind of issue. Can you please update the documentation accordingly?

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

ID: eee999c1-32dd-d014-40df-8027adee1258
Version Independent ID: 19a29c09-79f8-580a-841f-873e2801da56
Content: Integrate Azure Key Vault with Kubernetes
Content Source: articles/key-vault/general/key-vault-integrate-kubernetes.md
Service: key-vault
Sub-service: general
GitHub Login: @msmbaldwin
Microsoft Alias: mbaldwin

@blessedwithsins Thank you for pointing this out an sharing your findings . We appreciate the help . We will have this reviewed on our side and accordingly work with the authors to get this fixed.

@shashishailaj Thanks a ton :)

@blessedwithsins it looks exactly the same as in actual product example, from their product site https://github.com/Azure/secrets-store-csi-driver-provider-azure/blob/master/examples/service-principal/v1alpha1_secretproviderclass_service_principal.yaml
It could be an issue in a way you were applying. If you experiencing issues please submit it on their github to get help from engineers https://github.com/kubernetes-sigs/secrets-store-csi-driver

@jlichwa Hi Jack, Problem was with single object. Maybe it was a mistake at my end. I was providing array as below for secret object which didn't work because last one is showing starting of another object.
"

|
objectName: piyush
objectType: secret
objectVersion: ""
|
"

Although i figured out later that it was not required.

@blessedwithsins I'm glad that issues is sorted out. Yes example shows array of multiple secrets and that is why it needs "-|". We are trying to follow official Secrets Store CSI Driver documentation as close as possible. #please-close


attempt at upgrading to v8.0 of the Nordic SDK

This mostly includes a new soft-device with new APIs along the lines of the upcoming S130 combined soft-device. This is an important first step in the direction of merging with S130.

+1 to this. Let me know if you'd like someone to test.

Notes for testers: please update to the following if you want to test.
https://github.com/mbedmicro/BLE_API/commit/35e1e8b8c47c621e370e5f7c9569e2bb308a0e49
https://github.com/mbedmicro/nRF51822/commit/deaa052af622c4dc2312ce3a03649c91f6dcb3ea


[Feature Request]:  Refactoring code

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
i see so many unused imports and unwanted comments in codebase, making webpage heavy for loading and adding unwanted code. So i wanted to refactore codebase removing unwanted codes making site lighter
Use Case
removing unwanted code makes site rendering time lesser, and improves performance
Benefits
improves sites performance and reduces overhead
Add ScreenShots

Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

Is there an existing issue for this?

[x]  I have searched the existing issues

Feature Description
i see so many unused imports and unwanted comments in codebase, making webpage heavy for loading and adding unwanted code. So i wanted to refactore codebase removing unwanted codes making site lighter
Use Case
removing unwanted code makes site rendering time lesser, and improves performance
Benefits
improves sites performance and reduces overhead
Add ScreenShots

Priority
High
Record

[x]  I have read the Contributing Guidelines
[x]  I'm a GSSOC'24 contributor
[x]  I have starred the repository

Hello @Sourabh782, Go for it
All the Best


Parse .env or environment variables for RPC auth details

And possibly for other properties, too, such that not every single launch has to be a super long command, and such that the auth data doesn't get added to the command history.

We...don't have an RPC? I'm not sure what auth details we'd want to parse?

The auth to talk to the bitcoin daemon RPC :)

Oh, yea, duh, would be cool to parse the .cookie.

Hello! I’m interested in picking up this issue. Worked with Rust a bit in the past but otherwise fairly new. Also new to contributing to open-source.
Here’s what I’m considering for a basic version that parses RPC fields from a .env file:

In the first argument <bitcoind-rpc-username>:<bitcoind-rpc-password>@<bitcoind-rpc-host>:<bitcoind-rpc-port>, if the user doesn’t include the @, it will parse the string as if it’s just the second half <bitcoind-rpc-host>:<bitcoind-rpc-port>, and check for environment variables and/or look for a .env file in the working directory to parse for the rpc username and password.
It’ll also print some extra usage information to communicate this option when prompted.

Question: Is there a recommended way for testing changes in this repo?
If anyone has feedback/questions on this it'd be greatly appreciated! I plan to get a PR in for the basic version either tonight or tomorrow sometime, then possibly expand to other arguments after I get that working.


Updates to chapter 1

[x] for each section where it shows how to do something e.g. renaming variables, use tabsets for each method
[x] add the example on collapsing factor levels using forcats in section 1.10.1
[x] use a callout box every time i'm referencing another text
[x] Remove all the SPSS code/discussion
[x] update the chapter reference code under 1.17.3. I think the new way to ref does not include the @

The bulk of the 'saving only selected variables' subheader in 1.15 Export and Save was SPSS examples, so the reference to dplyr select() could be turned into either a callout box note or expanded with an example

The reference format @sec-name from {#sec-name} at the title should work once Ch12 is imported, it linked (but as Ch3) with a blank test file

text at bottom of section 1.5

Right away this tells me that R thinks all variables are numeric integers, not categorical variables. Many of these will have to be changed. We’ll get to that in a moment.

needs to be pulled out of the tabset so  it shows for both

In 1.10

[ ] move help  box to top that ref's forcats vignette & math 130
[ ] don't load the car library, use the shortcut car::recode
[ ] figure out where in this whole chapter to put a warning box about package conflicts. (perhaps here is fine b/c tghis is the first place where ther is a conflict) but the recode function is in dplyr also and works differently