If git isn't installed, send a message that Git needs to be installed in order to use this version of QPM

Title says it all.
Old QPM doesn't need git, this one does. When migrating from the versions, some people don't know that git is a requirement, and so the title

Assuming this would just go
qpm-rust restore
->
Seems like you do not have git installed! make sure to install it from <insert link here> and then try again!

?

Yes, something like that.

Implemented in https://github.com/RedBrumbler/QuestPackageManager-Rust/commit/c5d678dec7f3d8965b550b94f08e106e97df64ae
Still panics but it now tells you to install git


es_ES.lang

-Protección (claim) was being used as a femenine and as a masculine
-some accents
-some missclicks
-click>clic
-more translation on untranslated words

Terms to be traduced:
-Flag: on spanish programming the term flag is "bandera" but people might not undertand, so I left if as flag
-Parent claim: maybe "Protección progenitora"?
-Child claim:  ¿?

Spanish here ✋. Can confirm all looks great

The messages economy-claim-rented-no-cancel and tax-expired are duplicates

will take a look and correct it. Although this is for GD 1.X, not GD 2.X. This translation will never be merged.


Setup Model registry

Acceptance criteria

Set Up a private registry for building and storing the models

Technical Notes

Use Docker

Acceptance Criteria :

Have the start point and endpoint of the registry set up.
Proper documentation of how to insert different models into the registry and expected input and output from the model code.

Technical Notes :

Docker for containerizing the registry
Python for creating the required framework to insert and delete models.


Enable object-shorthand linting rule and fix issues

This is https://caniuse.com/mdn-javascript_grammar_shorthand_object_literals , right? Anything post-2016 seems to support it natively. I'm OK with the change.

Yeah, it is. I think we can safely target ES2020, perhaps even ES2021.


Use of C++11

Background Information
The packages rosbag and  rosbag_store includes headers from this package when the minimal installation from source is attempted. ROS assumes C++98, not C++11 and so the CMakeLists.txt don't have
set(CMAKE_CXX_STANDARD 11) # or 14 or 17, but 11 suffices for compilation

Issue
This package uses several new features of C++11 (and newer) including std::shared_ptr<T>, std::unique_ptr<T>, nullptr despite boost being the default standard in ROS.
This causes compilation error (which is easily fixed).
Solution
Either

The CMakeLists.txt file of dependencies need to be changes and sacrifice portability for compilers not supporting C++11 or later

OR

Changes need to be made in this repository to accommodate the compatibility issue.

After the discussion, I'd be happy to send PR to whatever solution is deemed as the correct one.

Can you please clarify what version (or branch) of class_loader you are compiling as well as what version of ROS you are using ? Thanks

Oops, sorry for forgetting that. Melodic from rosinstall_generator ros_comm --rosdistro melodic --deps --tar > melodic-ros_comm.rosinstall

Melodic targets only platforms that have c++14 as their default compiler option:
https://github.com/ros-infrastructure/rep/blob/master/rep-0003.rst#melodic-morenia-may-2018---may-2023
And assumes C++14 not C++98: https://github.com/ros-infrastructure/rep/blob/master/rep-0003.rst#melodic
Could you clarify your use case / setup?

There's no harm in adding the c++ standard required.

This will force users to compile the code with the standard hard-coded in the package. If users have compiler defaulting to a higher standard I don't think we should force a downgrade on them

In that case, should I go ahead with a PR on the rosbag repository for adding the definition explicitly?

The policy applies to the entire distribution, I don't think submitting patches to specific packages is a desired approach as this will introduce inconsistencies between packages of the same distribution.

Our default compiler has c++14 support but not by default...

Then I recommend you to pass the c++ standard explicitely to your build tool (or in its configuration if it supports it). e.g. MacOS users currently build by passing -DCMAKE_CXX_STANDARD=14 to their build tools
You can find a similar discussion at https://github.com/ros/catkin/issues/936


Ah2: Desktop Looping & Switching + Other Feature Regression from Commit ee2f54f626914273f00853306c1daaf803f756cb

If I revert to before ee2f54f626914273f00853306c1daaf803f756cb I don't have the issues.
Looping works for a bit but if the gui window is deselected it stops working in a few seconds and I can't even navigate using Ctrl+Win+ArrowKey. If I close the gui it breaks all functionality immediately.

I am on Win 11 btw.

I finally figured out that for some reason the changes after that commit I posted above using the Arrow Keys not work. E.g.
^#left::VD.goToDesktopNum(1)
^#down::VD.goToDesktopNum(2)
^#right::VD.goToDesktopNum(3)
^#up::VD.goToDesktopNum(4)
does not work.
So I substituted
^#J:: VD.goToDesktopNum(1)
^#K:: VD.goToDesktopNum(2)
^#L:: VD.goToDesktopNum(3)
^#I:: VD.goToDesktopNum(4)
and now they're working fine.


DO NOT LAND feat: use PartySocket when connecting via room.parties

This uses PartySocket when connecting why room.parties, whcih gives you reconnection/buffering logic without any extra effort. Non-breaking change, existing code should still just work.

closing for https://github.com/partykit/partykit/pull/395


Systems Engineer

Hi, although this document covers 32/64 bit Office applications, it fails to describe settings for 64/32 Bit Operating Systems. It is also very dated in that it describes a Hotfix for Office 2007 which is irrelevant given the document was supposedly created in 2017. I think it is important that dates are included so readers ascertain the relevance of the information provided. Not mentioning the Registry differences for the 64/32 bit OS is just plain dumb. Thanks

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

ID: c26ff2bd-2b95-2a91-2479-69fc63c07239
Version Independent ID: 738a7001-8809-4bbf-73fa-8c45ab56534a
Content: Registry entries for VSTO Add-ins - Visual Studio
Content Source: docs/vsto/registry-entries-for-vsto-add-ins.md
Product: visual-studio-dev15
GitHub Login: @TerryGLee
Microsoft Alias: tglee

@DRussell555 Thanks for your feedback! Yes, we're aware that this page needs updating. It's on our backlog to fix.

@DRussell555 the article does mention the Wow6432Node for 64bit OS's.  It's not clear to what you believe is missing. Could you please give an example?  The article may have been written a while ago but the article should still be relevant.

@DRussell555 Any updates?

Hi,
IMHO the information of the registry entries is incomplete because there are 3 and not just 2 cases and wrong because the Configuration Path is mixed up. I guess it should be like this:

OS version 32 bit + Office version 32 bit: Root\Software\Microsoft\Office\application name\Addins\add-in ID
OS version 64 bit + Office version 32 bit: Root\Software\Wow6432Node\Microsoft\Office\application name\Addins\add-in ID
OS version 64 bit + Office version 64 bit: Root\Software\Microsoft\Office\application name\Addins\add-in ID

The same for Visio accordingly.
Please verify and correct when indicated,
Thank you

The document has been updated to mention installing on 64-Bit Windows Thanks for the feedback.


Updated footer to contain current year

Changed 2016 to 2017 in page footer

It is updated to the latest year by some other change.


Fix line wrapping for confirmation questions

Uses the promt toolkit default breaking implemented in shortcuts._split_multiline_prompt. Works in the same way the normal promt does, properly wrapping long lines.
Fixes  #21

@tmbo Thanks for this, I'll surely look at it

I have tested it with various length of text. This is nice. I'll be merging this PR.

@CITGuru do you mind creating a bugfix release?

@tmbo You should expect it by tomorrow. Is that fast enough?

Yes that would be perfect. Thanks a lot :rocket:


Bug unable to see DropDown Menu Arrow in Darkmode

Please verify that this bug has NOT been raised before.

[X] I checked and didn't find a similar issue

Describe the bug*
When loading the sub-sub BOM of an assembly in darkmode, you are not able to see the arrow to open the loaded BOM.
Steps to Reproduce

Enable Dark Reader
Have an Assembly with at least one other assembly as sub-part which also contains an other assembly
open the BOM
Try to load the BOM of the sub-sub part

Expected behaviour
You should be able to see the arrow, which shows the extended BOM.
Deployment Method

[ ] Docker
[X] Bare metal

Version Information
Version Information:
InvenTree-Version: 0.10.0 dev
Django Version: 3.2.16
Commit Hash: e730b5c24
Commit Date: 2023-01-10
Database: postgresql
Debug-Mode: True
Deployed using Docker: False
Active plugins: False
Relevant log output
No response

@Fluxus00 sounds exactly like https://github.com/inventree/InvenTree/issues/4455 - did you check the issues before submitting like instructed on top of the bug report?

Ah sorry my bad, yes i checked it, but it seems like I need new glasses. I will close this right away.


[BUILD][NDI] Problem with the file "NdiMediaEditorModule.cpp"

Hi,
I got to use this plugin on Linux and Windows.
On both platforms i got the same kind of errors. When I included the plugin into my cpp project, unreal asked me to build the plugin. Then, on both platform, i got the same problem, there is the output log on windows :

C:\Users\Alexandre\Documents\Unreal Projects\MyProjectCPP_01\Plugins\NdiMedia\Source\NdiMediaEditor\Private\NdiMediaEditorModule.cpp(22): error C2061: syntax error: identifier 'NdiMediaEditor'
C:\Users\Alexandre\Documents\Unreal Projects\MyProjectCPP_01\Plugins\NdiMedia\Source\NdiMediaEditor\Private\NdiMediaEditorModule.cpp(22): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int

The same kind of error occurs on Linux, saying that this line has a problem:
 IMPLEMENT_MODULE(FNdiMediaEditorModule, NdiMediaEditor);
On linux, the error log is as follows :

In file included from /media/jacques/home/jacques/EpicGames/UnrealEngine/Engine/Plugins/Media/NdiMedia/Intermediate/Build/Linux/B4D820EA/UE4Editor/Development/NdiMediaEditor/Module.NdiMediaEditor.cpp:2:
/media/jacques/home/jacques/EpicGames/UnrealEngine/Engine/Plugins/Media/NdiMedia/Source/NdiMediaEditor/Private/NdiMediaEditorModule.cpp:22:41: error: unknown type name 'NdiMediaEditor'
IMPLEMENT_MODULE(FNdiMediaEditorModule, NdiMediaEditor);
^
/media/jacques/home/jacques/EpicGames/UnrealEngine/Engine/Plugins/Media/NdiMedia/Source/NdiMediaEditor/Private/NdiMediaEditorModule.cpp:22:1: error: C++ requires a type specifier for all
declarations
IMPLEMENT_MODULE(FNdiMediaEditorModule, NdiMediaEditor);
^~~~~~~~~~~~~~~~
2 errors generated.

The two tests were done with the latest SDK version we could get on the NewTek website, and the latest version of your plugin, with the latest version of Unreal engine 4.13 (Linux), and 4.13.1 (Win).
Thanks for reading.
Regards,
Alexandre ADAM

Hmm... did you run /UE4/GenerateProjectFiles.bat after cloning the GitHub repository into your project?

Hi,
Thanks for your help. Generating the project files did not change the build errors but we finally managed to build the plugin by including "Editor.h" in the file NdiMediaEditorModule.cpp
I don't know why we have to do this though, we are exploring the Unreal Engine since 2 weeks only...
Does this include make sense for you ? Is there a better solution ?
Anyway, the plugin works on Windows and also Linux after some minor modifications :)
We are now eagerly waiting for the NDI output plugin ! Do you have an ETA by any chance ?
Thank you.

We are now eagerly waiting for the NDI output plugin ! Do you have an ETA by any chance ?

Newtek has an implementation for output, but I haven't seen it yet. Video output from UE4 is something I'd like to add to the Media Framework API, but I haven't had time yet. I will probably be able to finish it for 4.15 though (and in the Master branch likely before the end of the year).

we finally managed to build the plugin by including "Editor.h"

I think the problem is that ModuleManager.h was missing. I fixed this in the new version (which isn't on GitHub yet).

Anyway, the plugin works on Windows and also Linux after some minor modifications

The next version should work much better and out of the box. It will include the pre-compiled libraries and DLLs for Windows, macOS, iOS, and Linux.

Adding "Editor.h" to NdiMediaEditorModule.cpp also fixed the compile error on my end.
However, I am still having trouble launching the project where the 'NdiMedia' module could not be loaded.

Ah sorry, just need to manually copy the .dll, as described in the ReadMe. All good! :)

Yep. The next version will contain the required DLLs.


Is tile aggregation count operation available?

Question
Is the count operation available for tile aggregation feature? In this section of the carto.js v4 repository, it looks like it isn't. However, I've managed to use the count operation on a Named map and carto.js v3.15
Context
When creating a Named Map, I'm using the new tile aggregation operations to try to create a cluster map, I managed to do it by using the count aggregation in the next named map template:
{
    "template": {
        "auth": {
            "method": "open"
        },
        "version": "0.0.1",
        "name": "tile_agg_test",
        "layergroup": {
            "version": "1.5.0",
            "layers": [
                {
                    "type": "mapnik",
                    "options": {
                        "cartocss_version": "2.1.1",
                        "cartocss": "#layer { marker-fill: red; marker-width: [total];}",
                        "sql": "select * from stormevents_locations_2014",
                        "aggregation": {
                            "placement": "centroid",
                            "columns": {
                                "total": {
                                    "aggregate_function": "count",
                                    "aggregated_column": "cartodb_id"
                                }
                            },
                            "resolution": 2,
                            "threshold": 10000
                        }
                    }
                }
            ]
        },
        "view": {
            "zoom": 3,
            "center": {
                "lng": 0,
                "lat": 0
            }
        },
        "placeholders": {}
    }
}

And when using the template of the named map with Carto.js v3.15 it renders correctly.
However, if I add labels to the CartoCSS of the template using the result of the aggregation for the text-name parameter, CARTO returns an error because it can't find the aggregation column.
"#layer { marker-fill: red; marker-width: [total];}",
#layer::labels {text-name: [total]; text-face-name: 'DejaVu Sans Book'; text-size: 10; text-fill:
 #FFFFFF; text-label-position-tolerance: 0; text-halo-radius: 1; text-halo-fill: #6F808D; text-allow-
overlap: true; text-placement: point; text-placement-type: dummy; }

The same problem happens when I use the aggregation, SQL query and CartoCSS of the template tile_agg_test with CARTO.js v4. CARTO can't instantiate the map because it can't find the resulting field of the aggregation using the count operation.
However, if I use the sum operation the aggregation works in both Carto.js v4 and Named map with carto.js v3.15. Here you can find the example of using the sum operation of the tiles aggregation to create a cluster map.

Showing the docs https://carto.com/developers/maps-api/guides/tile-aggregation/ it seems not possible.
Valid aggregate functions are sum, avg (average), min (minimum), max (maximum) and mode (the most frequent value in the group).

The carto.js v4 checks the value of the aggregation function and if it does not exist, returns an error
https://github.com/CartoDB/carto.js/blob/master/src/api/v4/layer/aggregation.js#L140
But in the same page of the documentation you can see:
The aggregated rows always contain at least a column, named _cdb_feature_count, which contains the number of the original points that the aggregated point represents.

So, dont need to make a count, because it is already done (column _cdb_feature_count)
I am going to check it in the code

Yes, the column that you are looking for is _cdb_feature_count

Thanks for the detailed information @oleurud ! :)


How to read the Input passed from workflow in Code

Hi,
I need to read the input data (in below code, JobType :3) in code . Please help in reading the data in onExecute in the code.
{
"name": "TestWorkFlow13",
"version": 2,
"correlationId": "meaningful_unique_correlationId",
"input":
{
"JobType": "3"
}
}
Thanks,
Jegadeesh

Hi @jegadjame,
The ConductorTask model has a property InputData which contains that information.
Best,
Erik

Thank You Erik... I am able to get data now by accessing using this.InputData


set WARNING to 5.4.1.RELEASE(en)

Please review #204 .
Set WARNING for old guidelines to 5.4.1.RELEASE(en).
relates to TSF4J5-2950.

Sorry, No warning was needed for 5.4.1.RELEASE(en).


https://catalog.ldc.upenn.edu/LDC2013S09 try apply here

https://catalog.ldc.upenn.edu/LDC2013S09 try apply here

How to apply for data access once login is done as guest ?
Originally posted by @Vatsal3631 in https://github.com/bryanlimy/rnn-lie-detector/issues/1#issuecomment-899446191

have you download the dataset yet? I can't download it when registered as a guest. what should I do now?


Improve currency context

Proposal
Currency context will simply map a currency string ('ETH' or 'USD') to the integer they use in the contracts (0, 1 or 2). Then throughout the app we can just use the strings everywhere, only using the currency context at the point we interact with the contracts, where we need the currency integer

Will this allow for 'ETH' and 'USD' to be strongly typed? Right now currency context allows accidentally misspelling currencyEth or currencyUsd since the object keys are just string type. I don't mind keeping the dictionary pattern, something like
const { currencies: { ETH, USD } } = useContext(CurrencyContext)

as long as currencies is typed, so that { currencies: { ETHH } } would show an error


Class for ems

consolidating on name class_by_name
followup to https://github.com/ManageIQ/manageiq/pull/21496
Sorry, was still working on comments from you all. But maybe I'm just bike shedding. 🏠
Also, looking at the use cases and inherit is overkill and passing in a class does not make sense.
I do notice that the 2 use cases are for create/raw_create and for supports?
Lots of boiler plate around that but maybe we should punt for now.

@kbrock A conflict occurred during the backport of this pull request to morphy.
If this pull request is based on another pull request that has not been marked for backport, add the appropriate labels to the other pull request. Otherwise, please create a new pull request direct to the morphy branch in order to resolve this.
Conflict details:
diff --cc app/models/manageiq/providers/cloud_manager/template.rb
index 31ced4f466,249efda189..0000000000
--- a/app/models/manageiq/providers/cloud_manager/template.rb
+++ b/app/models/manageiq/providers/cloud_manager/template.rb
@@@ -55,6 -57,41 +55,44 @@@ class ManageIQ::Providers::CloudManager
      klass.raw_create_image(ext_management_system, options)
    end

++<<<<<<< HEAD
++=======
+   # Queue import of image with an id 'options[:image_id]' from a provider
+   # with an id 'options[:provider_id]' into current provider
+   #
+   def self.import_image_queue(userid, ext_management_system, options = {})
+     task_opts = {
+       :action => "Importing Cloud Template for user #{userid}",
+       :userid => userid
+     }
+
+     queue_opts = {
+       :class_name  => name,
+       :method_name => 'import_image',
+       :role        => 'ems_operations',
+       :zone        => ext_management_system.my_zone,
+       :queue_name  => ext_management_system.queue_name_for_ems_operations,
+       :args        => [ext_management_system.id, options]
+     }
+
+     MiqTask.generic_action_with_callback(task_opts, queue_opts)
+   end
+
+   def self.raw_import_image(_ext_management_system, _options = {})
+     raise NotImplementedError, "raw_import_image must be implemented in a subclass"
+   end
+
+   def self.import_image(ems_id, options)
+     raise ArgumentError, _("ems cannot be nil") if ems_id.nil?
+
+     ext_management_system = ExtManagementSystem.find(ems_id)
+     raise ArgumentError, _("ems cannot be found") if ext_management_system.nil?
+
+     klass = ext_management_system.class_by_ems(:Template)
+     klass.raw_import_image(ext_management_system, options)
+   end
+
++>>>>>>> 5abee31b65 (Merge pull request #21501 from kbrock/class_for_ems)
    # Update a cloud template as a queued task and return the task id. The queue
    # name and the queue zone are derived from the EMS, and a userid is mandatory.
    #
* Unmerged path app/models/host_initiator_group.rb

https://github.com/ManageIQ/manageiq/pull/22238

Backported to morphy via https://github.com/ManageIQ/manageiq/pull/22238

Skipping backport to najdorf, because it is already in the branch.


gulp4 install issue on ubuntu 14.04

Hi,
I'm having an issue installing gulp4 as it is required by angular-strap.  I ran:
sudo npm install gulpjs/gulp-cli#4.0 -g
This is what I got in the log file.  Anyone got an ideas how to get this installed?
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/nodejs',
1 verbose cli   '/usr/bin/npm',
1 verbose cli   'install',
1 verbose cli   'gulpjs/gulp-cli#4.0',
1 verbose cli   '-g' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose cache add [ 'gulpjs/gulp-cli#4.0', null ]
5 verbose cache add name=undefined spec="gulpjs/gulp-cli#4.0" args=["gulpjs/gulp-cli#4.0",null]
6 verbose parsed url { protocol: null,
6 verbose parsed url   slashes: null,
6 verbose parsed url   auth: null,
6 verbose parsed url   host: null,
6 verbose parsed url   port: null,
6 verbose parsed url   hostname: null,
6 verbose parsed url   hash: '#4.0',
6 verbose parsed url   search: null,
6 verbose parsed url   query: null,
6 verbose parsed url   pathname: 'gulpjs/gulp-cli',
6 verbose parsed url   path: 'gulpjs/gulp-cli',
6 verbose parsed url   href: 'gulpjs/gulp-cli#4.0' }
7 silly lockFile dd154dca-gulpjs-gulp-cli-4-0 gulpjs/gulp-cli#4.0
8 verbose lock gulpjs/gulp-cli#4.0 /home/graeme/.npm/dd154dca-gulpjs-gulp-cli-4-0.lock
9 info maybeGithub Attempting gulpjs/gulp-cli#4.0 from git://github.com/gulpjs/gulp-cli#4.0
10 silly lockFile b7be6e36-t-github-com-gulpjs-gulp-cli-4-0 git://github.com/gulpjs/gulp-cli#4.0
11 verbose lock git://github.com/gulpjs/gulp-cli#4.0 /home/graeme/.npm/b7be6e36-t-github-com-gulpjs-gulp-cli-4-0.lock
12 verbose addRemoteGit [ 'git://github.com/gulpjs/gulp-cli', '4.0' ]
13 silly lockFile fb042cb1-git-github-com-gulpjs-gulp-cli git://github.com/gulpjs/gulp-cli
14 info maybeGithub Attempting gulpjs/gulp-cli#4.0 from git+ssh://git@github.com:gulpjs/gulp-cli#4.0
1,1           Top

Don't install things with sudo, your environment is messed up if you are using sudo
Update your node and npm.  Your node is out-of-date, even on the 0.10 branch and your npm is insanely out of date.
Installation isn't a gulp issue, it is almost always your environment, and if it isn't your environment then it is an npm issue.


DatePicker ArgumentOutOfRange

When opening DatePicker, an ArgumentOutOfRange exception occurs when formatting DateTimePickerPanelType.Month. The exception occurs due to the month having a value of 2 and FormatDate.Day being 30. I suspect this only occurs on Dates 30 & 31

@amrx

@amwx

@Oxc3 Can you provide a little more context on how this occurred (i.e. code)?
Normal behavior won't allow invalid days based on the month/year in .net DateTime/DateTimeOffset and there is some logic to ensure if you switch from the 31st in one month to February, for example, that the date is moved correctly to avoid this, but I may have missed something. I'll take a look and see what's going on...

Sorry for the late response. I tested it today and it is working again, which added to my speculation it was the day causing the error. When opening the DatePicker in debug with a system date of 30 or 31st the exception occurs on line 491 of DateTimePickerPanel.cs.
return new DateTime(FormatDate.Year, value, FormatDate.Day).ToString(ItemFormat); where FormatDate.Year = current date, value = 2 and FormatDate.Day = current day (30 or 31). Because the moth = February(2) and the day is 30 or 31 DateTime throws the range exception

this only happens when you click the DatePicker to open the scroll list. The display is fine.

Was able to repro it, and I think I fixed it. Something seemingly minor that I overlooked.

That was it. I tried the changes and I cannot break it. Thanks.


Include video tutorial pls

I wanted u to have a video tutorial on how to use the program

may be later

may be later


[Feature Request] Autocomplete with ability to add custom item

Is your feature request related to a problem? Please describe.
N/A
Describe the solution you'd like
As a user I would like to be able to add an item to the autocomplete list if the item is not found
Describe alternatives you've considered
Alternate library
Screenshots or Videos
No response

Isn't it this feature ?
https://nextui.org/docs/components/autocomplete#custom-value

Isn't it this feature ?
https://nextui.org/docs/components/autocomplete#custom-value

Not really; the custom value just allows users to write any value they want, but NextUI doesn't provide any way to add that custom item to the list of items.

I ended up using https://react-select.com/creatable
I will keep this feature request open for now to get more feedback

Wow, I'd really appreciate such kind of functionality! Also using some strange alternatives to achieve this thing!

+1 need this, also for multi-select

+1

+1

+1

This how I managed to make it work , a generic example and I'm using react-hoook-form as well :
const items = [   { label: "Option 1" },   { label: "Option 2" },   { label: "Option 3" }, ];
`<Controller
name="selectedItem"
control={control}
render={({ field }) => {
const [itemList, setItemList] = useState(items);
const [inputValue, setInputValue] = useState("");
const handleSelectionChange = (selected) => {
  const selectedItem = itemList.find((item) => item.label === selected);
  if (!selectedItem && selected) {
    const newItem = { label: selected };
    setItemList((prev) => [...prev, newItem]);
    field.onChange(selected);
  } else {
    field.onChange(selected);
  }
};

return (
  <div className="col-span-6">
    <Autocomplete
      className="text-black"
      aria-label="Select Item"
      placeholder="Select Item"
      defaultItems={itemList}
      onInputChange={(value) => setInputValue(value)}
      selectedKey={field.value}
      onSelectionChange={handleSelectionChange}
    >
      {(inputValue !== "" &&
        itemList.some((item) =>
          item.label.toLowerCase().includes(inputValue.toLowerCase())
        )) ||
      inputValue === "" ? (
        (item) => (
          <AutocompleteItem className="text-black" key={item.label}>
            {item.label}
          </AutocompleteItem>
        )
      ) : (
        <AutocompleteItem className="text-black" key={inputValue}>
          {inputValue}
        </AutocompleteItem>
      )}
    </Autocomplete>
  </div>
);

}}
/>
`
It shows the list of items , and when one item is not included , it allows you to add it to the list , could be improved for each use case


feat: add alt methods for multi-arg params for prefixed cmds

Pull Request Type

[x] Feature addition
[ ] Bugfix
[ ] Documentation update
[ ] Code refactor
[ ] Tests improvement
[ ] CI/CD pipeline enhancement
[ ] Other: [Replace with a description]

Description
This PR adds in alternative methods for "multi-argument parameters" for prefixed command. More specifically, it allows using ConsumeRest[...] over *, arg and tuple[...] over *arg. Some people may find this improvement better.
For hybrid command users, this finally allows making an argument a consume rest argument for the prefixed command variant. Variable argument support was not added because... well, slash commands don't do anything like variable arguments at all.
Changes
...see the description for the most part. The documentation for prefixed commands were updated too to show the new methods for declaring these types of variables.
Related Issues

Test Scenarios
@prefixed_command()
async def test(ctx: PrefixedContext, args: tuple[str, ...]):
    await ctx.reply(f"{len(args)} arguments: {', '.join(args)}")

@prefixed_command()
async def test(ctx: PrefixedContext, arg: ConsumeRest[str]):
    await ctx.reply(arg)

@hybrid.hybrid_slash_command(name="info")
@interactions.slash_option(
    name="arg",
    description="The argument to send",
    opt_type=interactions.OptionType.STRING,
    required=True,
)
async def cmd(ctx: hybrid.HybridContext, arg: interactions.ConsumeRest[str]):
    await ctx.reply(arg)

Python Compatibility

[ ] I've ensured my code works on Python 3.10.x
[x] I've ensured my code works on Python 3.11.x

Checklist

[x] I've run the pre-commit code linter over all edited files
[x] I've tested my changes on supported Python versions
[ ] I've added tests for my code, if applicable
[x] I've updated / added  documentation, where applicable

Interesting, are we using the ellipsis placeholder constant as a reference for consume marker?

No, the ellipses have zero effect on anything. It's the tuple that has an affect, the ellipses just make it proper typehinting.

Also, this new title is inaccurate. Support was already there, it's literally just adding alternative means to use it.

Oh, i just now see that. My apologies. I'll take the L 😔

Req review from sil - she uses this part of the lib far more than me, and iirc she was asking about this a bit ago


3.1.1 Image Fluid Error SVG

Hello,
Thanks for your last update. Unfortunately it created another issue:
It create this issue for all .svg files.
invalid json response body at https://images.prismic.io/showcase-dev%2F49f04ea2-c355-40ea-a0b7-77221cea5a7a_customize-top.svg?auto=compress%2Cformat&fm=json reason: Unexpected token < in JSON at position 0

> 36 |             fluid(maxWidth: 2000) {
     |             ^
  37 |               ...GatsbyPrismicImageFluid
  38 |               src
  39 |             }

I removed cache and public directory to test.
Thanks

@RobinHerzog Could you try v3.1.2?
I would recommend using the GatsbyPrismicImageFluid_noBase64 fragment if you know the image will be an SVG. The resulting placeholder URL will be fairly large if given a detailed SVG like the one in your example.


Font sizes

I'm using latest version of room card with latest version of HA core.
Tried to change font sizes of room name an entity names in entities list with styles and card-mod without success.
Could you please provide an example on how to do it correctly?

What do you have so far?
Btw, this isnt a bug, please ask your question in discussions next time


Plugs No Longer Showing Up In Homekit

What issue do you have? Please be as thorough and explicit as possible.

Plugs are no longer showing up in homekit

Details of your setup.

Do you use Homebridge (with config-ui?) or HOOBS?

-HOOBS

Which version of Homebridge/HOOBS do you have?

4.0.104

Which version of this plugin (homebridge-govee) do you have? Has the issue started since upgrading from a previous version?

-4.18

Which Govee devices do you have that are causing issues? Please include product models if applicable.

Dual and single WiFi plugs

Hi,
Can you restart the govee bridge and paste here all the logs from the plugin setting up?

On a side note, i would also recommend updating to the latest version of hoobs (v4.1). If it’s not showing as an update in the hoobs ui, you can use a terminal to ssh into the box and run this command:
curl -sk https://dl.hoobs.org/fix | sudo bash -


Use IEnumerable<KeyValuePair<string, object>> for Log() methods (again)

In v0.10.0 we used Log(IEnumerable<KeyValuePair<string, object>> fields). With our big java parity-change in v0.11.0 we changed the signature to Log(IDictionary<string, object> fields). This was an attempt to translate Java's Map<K, V> interface.
Java's Map interface does not implement any other interfaces. But in C# IDictionary<K,V> implements ICollection<KeyValuePair<K, V>> and ICollection<T> implements IEnumerable<T> so moving back to IEnumerable<KeyValuePair<string, object>> would be the most general type and a reasonable deviation from Java.
Using IDictionary does not give any guarantees regarding uniqueness anyway as people could call Log() with the same key multiple times or they could also use a non-unique implementation of IDictionary. This means that tracers have to deal with duplicate keys anyway and define their own behavior (e.g. last wins)
This change would also make it easier to use more efficient data structures (e.g. linked lists).
This is a breaking change for tracers, but it will NOT break instrumentation code as it will just use a more general interface.

@ndrwrbgs thanks for the review.

Only concern would have existed before anyway - in that IDictionary.GetEnumerator and IEnumerable.GetEnumerator are not performance optimal methods (both use a CallVirt and allocate objects, even if the enumerator is a struct since it has to be boxed into IEnumerator).

As noted here, it would be great if you could provide proof/a benchmark about the impact of CallVirt. I included a few links there that indicate that CallVirt is used almost always anyway.

However, I doubt we'd be able to gain consensus on using Dictionary or KeyValuePair[] which implement more efficient access options.

What would be your ideal signature?

Oi, I lost track of the other thread, I'm sorry. I cannot speak to the theory of this but I know first hand from measuring actual programs and improving performance of them at work that CallVirt is used for interface calls, but not (¿always?) concrete object calls.
For the first link - I'm thinking it must just be outdated.
For the second two - SO is down for my area so I can't comment :P
It's worth noting though that call and callvirt aren't really the question - both require a control flow jump. The question is more on what can be inlined and what cannot - a CallVirt can never be inlined because it does not know where the call will go.
My "ideal" signature would be to use interfaces as you've done, because they're better "code style". However if I were tasked with performance here then the story changes, as I've learned that for the sake of performance a lot of nice code (like interfaces) has to go away in C# :(
If we were to take perf as a top most important thing, then I probably would've avoided interfaces altogether for the types being passed around (ISpan and such) and tried to make a concrete sealed data-only-type implementation that could be handed off to a tracer only on write events (like Finish) so that a call like using (startSpan) { /* code */ } can be almost fully inlined (omitting of course that final call to something like tracer.LogSpan(span)). As it is today there has to be quite a few program jumps to instrument any piece of code which means performance wise (if we want tracing to be less costly than the code it's tracing) it's best suited only for code that already is containing jumps. The jumps today required by the interfaces:

ITracer.BuildSpan
ISpanBuilder.StartActive
IScope.Dispose

This is too big a change to make just for C# though, and given the language interop I don't think OT will progress down such a route any time soon. Thus far I've been holding hope that it doesn't matter in the end, and the usage characteristics of users make it so that it's unimportant (they only instrument high enough granularity).
All in all, I didn't expect to write a book here but seems I have. It's been something I've wanted to bring up for a while not to suggest change - since I think that'll be too hard - but to at least in the back of your mind when working on the API as perf concerns are something I neglected completely when porting over the java code.

^ I got a little off subject here. To answer the question more directly...
In terms of style and proper design, my ideal would be ISpan Log(IEnumerable<KeyValuePair<string, object>> fields); - it's the most permissive and doesn't prevent the implementation from taking Dictionary even if it so chose.
In terms of performance, something more like ISpan Log(KeyValuePair<string, object>[] fields); would be best. Dictionary (and I think even List) override GetEnumerator with a non-interface implementation that returns a struct (thereby avoiding the CallVirt because you can only actually access their virtual interface method implementation via casting - and avoiding allocation by using a struct) but if I were designing an API I would rather tie people to array (a primitive) than a specific class implementation (even if that class is from the BCL).

@ndrwrbgs We should definitely have a general performance-related discussion in a separate issue. I think it's important to discuss the goals and non-goals of this API and how it relates to other tracing APIs like ETW.
My concern with forcing an array type is that this will lead to people doing stuff like myFieldList.ToArray() (which will copy the whole list) because they are too lazy to deal with arrays. Using IEnumerable<...> will allow performance-sensitive instrumentation code to pass arrays while still supporting the "user friendly" lists. Tracers could optimize for the array-case by checking the type (at the cost of one cast of course) and then doing a regular for-loop instead of using the enumerator.
@opentracing/opentracing-c-maintainers More feedback would be appreciated so that we can include this in the next release. thank you :)

@cwe1ss I think this PR makes lots of sense (and I've always wondered why wasn't this the preferred way in Java, as opposed to using Maps).

I'll merge this on/after Friday (May 18th) if there's no objections.

I'll merge this now. I want to do an RC-release anyway so if there's any concerns, feel free to create a new issue!


Colorbars don't display correctly as SVG

Is it possible to export directly to pdf? Matplotlib can do this.

We haven't been supporting pdf as it doesn't display inline in the browser, i.e in our HTML tags. Generally, we would recommend SVG over PDF export for a couple of reasons:

Open XML standard (as opposed to a binary file)
Vector format supported natively in browsers.
Excellent tools for editing SVG (namely Inkscape)
There are packages adding SVG support to LaTex (e.g the svg package)
Easily converted to PDF later.

For these reasons, I doubt we will support PDF output in general unless all browsers start supporting it properly. That said, we could consider PDF support using the explicit, pure-python interface for saving output, described here. In particular I think we could support something like:
renderer = Store.renderer.instance(fig='pdf', holomap='gif')
renderer.save(obj, 'example')

This would only be available through this explicit interface though...

Now I discovered my real question: Colorbars are exported uggly to svg, the steps are to big. The png backend is fine. Exporting from matplotlib to pdf also results in nice colorbars.

So I came across this Stackoverflow post, which explains what's  going on here. matplotlib doesn't draws colorbars as a bunch of individual segments instead one image with smooth shading. In some SVG renderers this seems to cause issues. I can implement the fix they advise but if the colorbar has any alpha in it this will cause other issues, so I'll at least make it conditional on the alpha style option being disabled.

I've now implemented the fix suggested in the Stackoverflow post, so let me know if that fixes it for you. This issue is related to https://github.com/matplotlib/matplotlib/issues/1188 in matplotlib. So hopefully we can remove our workaround if anyone ever gets around to fixing that.

Should be fixed now so I'll close the issue. If you find any problems please reopen.

For people who care about reproducible modelling, not supporting easy export to PDF is problematic, since PDF is what can be easily imported directly into document preparation systems.  E.g. in LaTeX, the svg package simply uses Inkscape to convert SVG to PDF on the fly, which seems inefficient and likely to cause problems (e.g. just yesterday I had to give up getting a good PDF out of an Inkscape SVG file I was working with; I had to use PNG!).  It's certainly true that SVG has big advantages, but I don't think it's true that PDF would be bad to support.  That said, if it's difficult to support, that's a different matter.  If it's easy to support, I think it would help people have a clean reproducible workflow without requiring Inkscape trickery behind the scenes.

I think PDF support in the notebook itself (i.e for display) is out of the questions unless browsers support it better. Honestly, I can add even more reasons I think SVG is superior in all cases:

XML can be easily parsed and manipulated by Python code in the standard library. For instance in the GCAL paper, my whole system of embedding figures into a larger figure worked because I could write code to automate such steps. This is much, much harder with PDF (even using report lab).

You don't know what format journals accept and SVG is an excellent intermediate format. For instance, Journal of Neuroscience only accept PDFS in the initial submission and then only EPS or TIFF after that. Converting from SVG to either of those is something I trust much more than PDF to anything.

Related to the point above, many journals aren't going to let you typeset anything with LaTex anyway - they will ask for separate figure files and not a PDF generate by LaTex.

SVG is going to be better if you want to present and communicate your work on a webpage, whether you do so with IPython Notebook or not.

I have a lot of experience with Inkscape exporting to PDF and in general it is excellent. The one issue I have noticed is that some versions of Inkscape apply unwanted interpolation to raster images.  The safest thing in all cases is to output the raster at a high resolution because scaling down rarely causes the same bad artifacts as scaling up.

Different renderers will be used for SVG and PDF which means the output might not always be consistent due to issues in the renderer implementations. I would much rather treat SVG as the 'gold-standard' for our vector output than try to support PDF and have to keep trying to iron out inconsistencies between the two (if this is even possible!).

So I agree that for some people working with LaTeX and publishing on arXiv for instance might benefit from PDF output. There are possible conversion issues as you mentioned and I can imagine supporting PDF in the explicit save interface on MPLRenderer. Even if we can support it like this, I just don't want to encourage PDF output for the many reasons listed above!

Those are all good reasons for using SVG, and for recommending and endorsing SVG as our suggested best practice.  But the thing about a reproducible pipeline is that all the bits need to connect up for any of it to work, and SVG may or may not connect up to the other parts of the pipeline for other users.  Not everyone on the planet has even heard of SVG, but everyone knows what PDF is, and I've not found many journals who don't accept it, while I don't recall ever seeing one who would accept SVG.
In case it's of interest, the figure I had problems with yesterday was part of one of yours:

No idea why Inkscape won't save it as PDF, but I ended up exporting as a huge PNG instead.

For me a major drawback is the difference in color bar drawing. This is pixeled information, mostly next to a imshow object, which is pixeled.
When I make a presentation in inkscape, and import a svg-file with a colorbar, this adds 100kb of xml to my svg file, making inkscape slow (especially after importing multiple plot). When first exporting to PDF and then importing to inkscape, does not have this drawback, while all the lines are still lines, while the pixeled information is still pixeled. Export to PDF, or better colorbar support would help. Do I have to file an issue for matplotlib to imporve the svg output of colorbars?

Export to PDF, or better colorbar support would help. Do I have to file an issue for matplotlib to imporve the svg output of colorbars?

As I said there's an existing issue https://github.com/matplotlib/matplotlib/issues/1188 for this in matplotlib but it's almost three years old and I doubt anyone will reimplement colorbar as a smooth gradient rather than a bunch of individual segments at this point. If you look at the recent discussion, they've been suggesting implementing the fix I made manually in our code to avoid the white lines between individual segments but no one has proposed actually re-implementing the whole thing.
Overall I'd be happy if our MPLPlotRenderer could export to PDF, I'm also not sure if we should support it but I did just get inline rendering of pdf working but it'll be pretty browser dependent.

@jbednar Please don't mangle my figures like this! It took me literally 30 seconds to do it right:

I put a lot of effort generating proper vector graphics for my paper and I never want to see such horrible output ever. If you need PDFs, it takes absolutely no time to get it right:
Inkscape -> Export -> PDF

Whatever tools/versions/process you are using, something has gone horribly wrong and the output is completely unacceptable. Do not accept such bad output and please don't generate huge PNGs either! That screenshot is utterly hideous and revolting!
If you want to know where I got the figure, I just imported the paper at the appropriate page into Inkscape. Again, a 5 second process.
@vascotenner I think Philipp has had a look at color bars and has found some approaches that seem to work (not sure if it is committed yet though). I think filing an issue with matplotlib would be a very useful thing to do nonetheless! Thanks!
I don't mind allowing files to be saved PDF as long as we make it crystal clear that:

Any rendering or backend problems regarding PDF export need to be directed to matplotlib and not us!
Our gold-standard for vector output remains SVG.

Philipp and I have looked into getting PDF working properly in general, even for display in the browser. We've come up with a solution that is reasonable for modern browsers that integrates properly without having to make PDF a special case.
It is far from a perfect solution because browsers don't work that well with PDFs that well and we are making use of iframes! For this reason, we are adding a warning so that users know this is very experimental, may not work for them and may change in future.

I hope that solving this issue also makes the PDF export not necessary to obtain good colorbars:
https://github.com/matplotlib/matplotlib/issues/4480

@vascotenner Thanks for posting to matplotlib! Hopefully, they will fix it this time around. :-)

If you need PDFs, it takes absolutely no time to get it right:
Inkscape -> Export -> PDF

Actually, it's:
Inkscape->File->Save As->PDF

But in any case, that's precisely how I obtained that horrible and unusable output!  It usually does work, but I've had to do things like this at least 30 times more than you, and so I've encountered at least 30 times more problems.
In this particular case I started with the .eps file in your paper's source code, since the PDF was generated from the EPS, and it's nearly always better to start from the source figure, not the final generated PDF.  I'm glad that it works when starting from the final PDF, but that doesn't seem relevant to the point, which is that Inkscape isn't always able to generate decent PDF (it certainly didn't in the above example), and so it is not a no-brainer simply to assume that because you have some file readable by Inkscape, you can just assume you'll be able to have decent conversion to PDF.

Sounds to me like the problem was EPS which doesn't surprise me at all. I only ever touched EPS because I was forced to by Journal of Neuroscience  and yes, exporting those files was a truly miserable process! EPS is an outdated format and doesn't support even simple things (such as alpha channels) soI would never use by choice.
As HoloViews outputs SVG and not EPS, I don't think this would be a problem and I will still work exclusively with SVG until a PDF is requested (and export from Inkscape). Anyhow, since commit 1e8a59b we now have experimental support for PDF so I the whole point is probably moot.

Hi,
I am not sure if my question is related to this thread, but I have been trying out to export to pdf format ( which works) but it has lost the alpha setting of my plot
renderer = hv.plotting.mpl.MPLRenderer.instance(fig='pdf') renderer.save(plt, "hist")
And I also tried to use matplotlib backend but that didnt work as well.
import holoviews.plotting.mpl hv.Store.renderers['matplotlib'].save(plt, "hist_m", 'pdf')
Any help will be greatly appreciated. Thank you.
(Sorry if I have posted my question in a wrong thread, or formatted it wrongly)

These days you can use the save function:
hv.save(plt, 'hist.pdf', backend='matplotlib')

That said the disappearing alpha could be a limitation of matplotlib itself OR the fact that you specified the option for another backend (e.g. bokeh). When switching backends your options don't persist, so you have to apply them with .opts(..., backend='matplotlib') or switch to the matplotlib backend before you set the options.

These days you can use the save function:
hv.save(plt, 'hist.pdf', backend='matplotlib')

That said the disappearing alpha could be a limitation of matplotlib itself OR the fact that you specified the option for another backend (e.g. bokeh). When switching backends your options don't persist, so you have to apply them with .opts(..., backend='matplotlib') or switch to the matplotlib backend before you set the options.

Hi,
Thank you for your prompt response.
I have tried your suggestion, but it still doesn't work. Is it because I had plotted my graphs in bokeh?


请问参数怎么填？How to fill in the parameters?

PS D:\serverless\demo> sls --debug
位于命令管道位置 1 的 cmdlet Select-String
请为以下参数提供值:
Path[0]:

Hey @StiffFy thanks for opening :+1:
Could you share the serverless.js file, serverless.yml file or project setup you're using? You can find the list of parameters you can provider here.

Closing this issue since it got stale. Feel free to re-open if this problem still persists.


ray write lance error

ref: https://github.com/ray-project/ray/issues/49211

It looks like release 2.38 refactored how ray.data.Datasink works and this broke our integration.
In version 2.37 and below each call to write was allowed to return some output:

A user-defined output. Can be anything, and the returned value is passed to on_write_complete().

However, in version 2.38, the signature for write changed to return None.
We were relying on this feature because, in each call to write, we create a "fragment" and return the fragment metadata (a small JSON string).  In on_write_complete we would take these fragments and commit them as a single transaction, completing the write.
I suppose we will need to figure out some other way to store temporary state in version 2.38.  Maybe we can we store it on the datasink itself?  My hunch is that this will not work because the write calls will run on a different worker than the call to on_write_complete.

(sorry, didn't realize you had created a PR when I wrote that comment)
Let me try out your PRs today

yes, i have fixed it

Might be practical to support this as well: https://github.com/lancedb/lance/issues/3308

@andrijazz right now this issue is waiting on https://github.com/ray-project/ray/pull/49251 but it looks like that may merge soon and I'll take another look at Ray soon :crossed_fingers:

我已经处理好了这个 @westonpace ，可以查看下 https://github.com/lancedb/lance/pull/3230对应的PR


Publish the library as a thin jar to avoid baking in log4j and other dependencies

Hi Pawel. Sorry for inconvenience. Currently we have another priorities, but I will try to look at it next sprint.

Fixed in release v0.0.25 , see: https://github.com/oddin-gg/javasdk/pull/13


where are the worlds located when i save and quit?

in retromcp

In v1.0.0+, minecraft/game/saves.
In pre-releases, jars/saves
Next time, take a look for 5 seconds before putting up an issue.


cmd/link,runtime: unused fields in inlinedCall

runtime.inlinedCall fields parent (parentPc is used instead), file (pcfile in the parent is used), and line (pcln in the parent is used) seem to be completely unused. They are a reflection of fields in goobj.InlTreeNode, which are used within the toolchain, but the runtime itself doesn't need them.
If I did the math right, cmd/go contains 431KB of inlineTree objects (2.8% of the binary size). With those fields gone it would drop to 258KB.

Neat. Originally these were important because we didn't have parentPc or the marker NOPs to attach file/line to, so the only source of that metadata was the inline tree. I believe you're right that they are no longer necessary.


Backoffice: Customer Requirements

Goal
Deliver a simple way of managing customers including but not limited to searching, editing, removing.
Section
Use the customer section for this feature, it will have to subsections.
Search
A search screen that allows to search for ID, name, last name, and email. At the moment, this is an AND-search (for all fields filled in) and will produce a list (table) underneath the search screen as result. The list is pageable.
List
Another screen directly offers a list of all customers without the need to search for. It will deliver a list of customers (pageable) by last name, first name.
Lists
All table lists will list id, last name, first name, email, status, and offer a VIEW, EDIT. DELETE buttons.
VIEW
The view button takes us to a listing which is nicely formatted and displays all important information attached to the customer, such as basic data, addresses, and more.  An additional button allows to jump to all orders of the customer (which is basically a search by customer id using the order search module and we really jump to it).
DELETE
You can delete a customer after confirmation BUT it won't delete the customer's orders(!). Important, make sure that the data such as addresses and credit cards is copied to the order when placing the order and not referenced!
EDIT
Here you can edit all customer information including assigning a new password (that is not really security conform but this a demo store and we don't have email support yet).
Addresses
Addresses will be listed on the EDIT screen and you have to use a separate edit step. You an also delete an address.
Credit Cards
CC can be removed or edited but you can only enter the number, name, and expiration date, not the CVV. This will be asked in the storefront again when ordering and will never ever be stored.
Removing
You can remove an address or a credit card but you have to of course confirm that.
Navigation
For most of the screen, a back navigation in the browser should work nicely and produce the screen expected. Especially important for searches and paging.

Currently after the table updates the List View looks like this. Interestingly we have same views for Customer Search View and List View atm. Would require separate controller methods for that.
Question: Is it possible we just have one List view for Customers with the ability to search through it? Instead of having a simple List view and a search-able List View.

Is it possible we just have one List view for Customers with the ability to search through it? Instead of having a simple List view and a search-able List View.
The implementation details are up to you. Choose the best path. One only one list view is likely a wise decision.

Cannot, as of yet, delete a customer without affecting customer's Orders. Currently the database and its tables do not permit this flexibility. It requires an independent issue #245 . Closing this issue as remaining objectives have been achieved.


[example] Hybrid Rendering

You can see a demonstration in this video
This example shows how you can render a single frame using both rasterization and ray marching.
It does this by manually calculating the depth of each pixel and writing it into the depth buffer.
I tested this on PLATFORM_WEB and PLATFORM_DESKTOP on a Linux machine like my previous example.
Additionally I fixed indentation on the makefile. ifeq isn't supposed to be indented with tabs.

@BugraAlptekinSari This is a great example! Thank you very much for the addition!


Fix Opera support for background sync

It turns out Opera didn't enable support for background sync until v42, even though they could have done it since v36.
I tested it with this test. It's also in their changelog.

Thanks!


Moves instantiation of all cells from addSugarPeak() and addSpicePeak()…

…to Environment constructor, removes now unused placeCell() definition.
The Environment constructor currently fills grid with Nones, and addSugarPeak() and addSpicePeak() both have checks to instantiate default Cells outside of the peak shape if self.environment.findCell(i, j) == None. addSugarPeak() and addSpicePeak() should only add sugar and spice peaks as it says in their names, not create the empty grid cells too. It doesn't make sense to replace grid Nones with Cells in both addSugarPeak() and addSpicePeak(). It's more intuitive to instantiate the Cell objects in the Environment constructor.
*I did have to import cell to environment, but I think that makes sense given that grid stores Cells.

Great catch! This inspired me to write an alternative implementation which has the same complexity class but is a bit cleaner.


ignore is not working as expected

Found a bug? Maybe our Slack Community can help.

Describe the Bug
tash_definition ignore is not working as expected tf version 0.14.5
Expected Behavior
tash_definition should be ignored

It looks like it's forcing a replacement due to adding a load balancer. It only ignores the task_definition argument changes.

Hmm, could be, since I'm using CodeDeploy with blue green, each time, I need to flip target groups between blue and green. this could affect the way it worked.

I don't think this is a bug with the module. If you want to ignore a task definition based on the load balancer, you can now do this by passing in a task definition arn from outside the module.


Correction for raw affiliation UMR CBGP (INRA/IRD/Cirad/Montpellier SupAgro), Cirad, Montpellier, France

Correction needed for raw affiliation UMR CBGP (INRA/IRD/Cirad/Montpellier SupAgro), Cirad, Montpellier, France
raw_affiliation_name: UMR CBGP (INRA/IRD/Cirad/Montpellier SupAgro), Cirad, Montpellier, France
new_rors: 05kpkpg04;05q3vnk25;03rnk6m14;05h7ddb14
previous_rors: 05kpkpg04;05q3vnk25;03rnk6m14
works_examples: W4210972551
contact: 181fce5894c8fbea05ba1711d37255a0:0bae612fdcd75469c598a1aef01baccbecbd @ inrae.fr

This issue was accepted and ingested by the OpenAlex team on 2024-11-18. The new affiliations should be visible within the next 7 days.


(opera) don't create desktop shortcut or pin to taskbar

https://chocolatey.org/packages/Opera
Description
Added two command line arguments to the installer, one to stop it from creating the desktop shortcut, the other for pinning to the taskbar.
Motivation and Context
By default, the opera installer pins itself to the Windows Taskbar. This goes against the principles of how the taskbar should be used - Programs shouldn't pin themselves to the taskbar, Users should pin Programs to the Taskbar.
A Desktop shortcut is common practice, however for it to be re-added when updating the program is overriding the user's preference - If it's not there, it's because I deleted it, so don't readd it. Not creating the desktop shortcut on initial install is a small price to pay (it's preferable to me, but that's just personal opinion)
How Has this Been Tested?
I downloaded the 64bit installer and ran it with the silentargs.
Screenshot (if appropriate, usually isn't needed):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Migrated package (a package have been migrated from another repository)

Checklist:

[x] My code follows the code style of this repository.
[ ] My change requires a change to documentation (this mean usually the notes in the description of a package).
[ ] I have updated the documentation accordingly (this mean usually the notes in the description of a package).
[x] All files is up to date with the latest Contributing Guidelines
[ ] The added/modified package passed install/uninstall in the chocolatey test environment.
[x] The changes only affect a single package (not including meta package).

Thank you for your contribution, but could I ask you to change it a little.
Make these changes as an optional parameter instead of having them hard coded into the silent arguments.
It's easy enough to do with the use of the chocolatey-core.extension's Get-PackageParameters helper (just search for it in this repo to see how it is used).
As such it would also need to be documented under a Package Parameters sub header ## Package Parameters

@cpmcgrath have to agree with @AdmiringWorm here.  This would be better suited as a Package Parameter, rather than directly into the installation arguments.

Closing this due to no feedback.


[logging] Don't pass arbitrary string to NSLog

NSLog expects a format string, so don't pass it arbitrary log strings,
which may contain format specifiers.

@swift-ci please test


[langchain_community] Update/Insert texts to the Milvus vectorstore

Update/Insert texts to the Milvus vectorstore.
    Inserting data when the collection is already exists
    and need to insert data based on collection schema,
    Metadata keys will need to be present for all inserted values. At
    the moment there is no None equivalent in Milvus.
    This is based on upsert data based on add_text functionality

[ ] PR title: "package: description"

Where "package" is whichever of langchain, community, core, experimental, etc. is being modified. Use "docs: ..."  for template changes, "infra: ..." for CI changes.
Example: "community: add foobar LLM"

[ ] PR message: Delete this entire checklist and replace with

Description: a description of the change
Issue: the issue # it fixes, if applicable
Dependencies: any dependencies required for this change
Twitter handle: if your PR gets announced, and you'd like a mention, we'll gladly shout you out!

[ ] Add tests and docs: If you're adding a new integration, please include

a test for the integration, preferably unit tests that do not rely on network access,
an example notebook showing its use. It lives in docs/docs/integrations directory.

[ ] Lint and test: Run make format, make lint and make test from the root of the package(s) you've modified. See contribution guidelines for more: https://python.langchain.com/docs/contributing/

Additional guidelines:

Make sure optional dependencies are imported within a function.
Please do not add dependencies to pyproject.toml files (even optional ones) unless they are required for unit tests.
Most PRs should not touch more than one package.
Changes should be backwards compatible.
If you are adding something to community, do not re-import it in langchain.

If no one reviews your PR within a few days, please @-mention one of baskaryan, efriis, eyurtsev, hwchase17.

@hwchase17 Please review, Adding function to upsert text directly based on one of the field from metadata

cc @xiaofan-luan

@xiaofan-luan Pleas review

@baskaryanPleas review if this can we merged
cc:- @xiaofan-luan/
Thanks

@xiaofan-luan  Can you please suggest in this case,
Actually current upsert interface only works with IDs, what if some one want to delete some of the row and adding n ew row in-place of those rows.
Basically embedding of one file can be added to multiple rows, based on splitter. now just want to update embedding for the same file with updated content , so this time it may create more or less row based on content and splitter.
Please review this or can you please suggest any other another possible solution.

so far the best you can do is to query with expressions to find. Then upsert with primary keys.
We could think of add upsert with expression in the future

Ok thank you for your quick response.
But i cant get key also, no of key(row) may not be same for one expression, it depends on metadata .
Fo example for, one expression i got 3 rows, but i need to add 5 row in place of those embedding row as some of the document might be splitted to multiple chunks . and how can will handle those chunks.?
I just tried to extend this method with expression :- https://github.com/langchain-ai/langchain/blob/c769421aa4fc4783968e069d800ef85191ce87da/libs/community/langchain_community/vectorstores/milvus.py#L1037
One option i can think is, deleting data using pymilvus interface, and adding using langchain.

Ok thank you for your quick response @xiaofan-luan . But i cant get key also, no of key(row) may not be same for one expression, it depends on metadata . Fo example for, one expression i got 3 rows, but i need to add 5 row in place of those embedding row as some of the document might be splitted to multiple chunks . and how can will handle those chunks.?
I just tried to extend this method with expression :-
https://github.com/langchain-ai/langchain/blob/c769421aa4fc4783968e069d800ef85191ce87da/libs/community/langchain_community/vectorstores/milvus.py#L1037
One option i can think is, deleting data using pymilvus interface, and adding using langchain.

upsert can be used as insert as well. If no exsiting entity, you can simply add a new row while upsert


Add support for .find for attachments

Why: So that attachments can be directly accessed by ID rather than needing the ticket ID and comment ID to access it.

Hello @gingermusketeer! thanks for the PR, and so sorry I didn't see it sooner, because I could have used https://github.com/zendesk/zendesk_api_client_rb/pull/382/commits/6bbf2074f6a24f862ce9ca9fa0e6bf3447e7d597 to fix the rubocops errors, which I did in a different PR.
Re: find attachments by id, I do agree with you that is an operation we should support. Though ReadResource base class is not really meant for single resources (it does give you the find method, but it does not enforce passing an ID to it).
Let me investigate it a bit further and I will get back to you. thanks

@nogates thanks. Let me know if you want me to make any changes!

@gingermusketeer I have been thinking a bit more about this, and I am happy with using ReadResource as the base class for attachments. However, I am really concern about adding / changing some functionality here before having a more comprehensive test suite.
So, I am in the process of reviewing the status of the integration tests, and that should (hopefully) take me about a week or so. By then, I hope I've at least one test to check the current attachment functionality before we change it.
Thanks!

@gingermusketeer I finished adding some integration tests as part of https://github.com/zendesk/zendesk_api_client_rb/pull/392... could you please rebase this on master and fix the merge conflicts? If it passes, I would be more than happy to merge your PR

Many thanks!!


adopting rust lang

Rationale
Three main reasons for adopting rust language in the LBRY SDK:

Significant performance improvements.
Ability to share code with every other programming language; including in the browser.
Enthusiasm on the team to use rust.

Adoption Strategies Overview
Three independent, and parallel, paths can be taken towards this goal:

Change out the current pyinstaller packager used for making SDK releases for rust based PyOxidizer. This is expected to improve startup time. Currently with pyinstaller every invocation of the command line requires unzip'ing the entire SDK source before Python can parse and execute while with PyOxidizer some of this extra startup work can be eliminated.
Re-implement parts of the SDK wallet core code in rust and import it as modules; while also providing packages for JavaScript, Go, etc.
Re-implement parts of the SDK file / blob management & DHT core code in rust and import it as modules; while also providing packages for JavaScript, Go, etc.

Replacing Packager
Replacing pyinstaller with PyOxidizer should mostly be a well defined and self contained task; possibly even ripe for community contributions.
Wallet
Replacing parts of the core wallet code could follow the following logical progression of releasable phases (for Python, JavaScript and Go):

[optional] LBRY protobuf parser. (alternately, could require language specific bindings generated for better language ergonomics and then passing the protobuf data into the rust transaction creation code in the next phase)

https://github.com/stepancheg/rust-protobuf
https://github.com/tokio-rs/prost

LBRY blockchain transaction parser by forking an existing bitcoin rust project:

https://github.com/Congyuwang/Rusty-Bitcoin-Explorer (MIT license, relatively small code base)
https://github.com/rust-bitcoin/rust-bitcoin (possibly compatible license but large code base)
https://github.com/gcarq/rusty-blockparser (GPL)

Signing / verifying transactions.
Key & seed management.

File / Blob Management & DHT

[optional] Blob encryption/decryption (low priority as it is already fast)
Blob Manager (checking and accounting of blobs is currently very expensive, freezing SDK when it happens)
[optional] [raw idea, needs another issue] Fast blob reassembly from files (maybe we can stop using blobs)
DHT

Packet parsing/handling (just transport, so it doesn't become unresponsive on GIL lockups)
[optional] Investigate if DHT data store can use less memory

Kindly follow the step on this link to talk to the customer care service directly on your issues anyone asking you to DM is a scam
https://direct.lc.chat/14201763/

Fast blob reassembly from files (maybe we can stop using blobs)

This would be GREAT!


Update path APIs to resolve tokens

This change allows qtpath, qtbinpath, et al, to include tokens which can be useful in cases where the Premake context is important in determining those paths.
For example, the Qt SDK Installer installs each platform SDK to, say, <qt-install-dir>/<qt-version>/msvc2019_64. The information contained in premake's cfg object can be used to determine that at bake time, but it must be resolved as a token:
qtpath '%{getQtSdkDir(cfg)}'

Where getQtSdkDir(cfg) is a function in the global scope that can translate the context into the correct Qt SDK path.
While one could set QTDIR before running premake, this doesn't behave well with multi-arch Visual Studio workspaces, or when a custom build of the Qt SDK places shared/static runtime and debug/release builds into separate paths.

Hi,
I don't really understand what you want to achieve with this PR ? qtpath and qtincludepath, etc. already allow you to specify all paths per-configuration, so you could have multiple platforms in the same VS project mixed-in with multiple configuration (statically linked, dynamic, debug build, etc.)
Mind explaining a bit more precisely the problem you're having, which you're trying to solve with this PR ?

(I'll merge the PR by the way, I'm just curious why the need for tokens :p)

Heya! So my specific use case is resolving a path for shared custom builds of Qt that include information such as architecture and build config name. It may be my inexperience with Premake, but this specific change is how I got there. For example:
\\fileserver\qtbuilds\5.15.0\windows-vs2019-x86_64-dll-release
\\fileserver\qtbuilds\5.15.0\windows-vs2019-x86-static-debug

The only way I could find to reliably switch up the qtpath based on architecture, runtime, and config was with a token:
function getBuildName(cfg)
    local runtime = cfg.staticruntime ? 'static' : 'dll'
    return cfg.system .. '-' .. _ACTION .. '-' .. cfg.architecture .. '-' .. runtime .. '-' .. cfg.buildcfg
end
-- later, in a workspace with, say, a 2x2 config matrix of x86/x86_64 and staticruntime on/off:
qtpath('\\\\fileserver\\qtbuilds\\5.15.0\\%{getBuildName(cfg)}')
premake.extensions.qt.enable()

Ok I see now, it could probably be solved with filter but the code would have been a lot messier to handle all the combinations.

Yeah, exactly.

Merged, thanks for the pull request!


Added Load Time Page

Changes
Added Load Time page i.e When the page renders for the first time,it renders an image and a welcome message for the users
Closes #2

Changes
Added Load Time page i.e When the page renders for the first time,it renders an image and a welcome message for the users
Closes #2

Nice work! but haven't you added loader, like when the fetching will be going on for that time instant.?
In addititon to, please fix these

Changes
Added Load Time page i.e When the page renders for the first time,it renders an image and a welcome message for the users
Closes #2

Nice work! but haven't you added loader, like when the fetching will be going on for that time instant.? In addititon to, please fix these

Yes I am trying to fix this error

Created a new issue Pluto query is buggy  #10 in GitHub


How to use compression?

Trying to use this middleware: https://www.npmjs.com/package/compression.
Tried the following but no luck
import compression from 'compression'
import HyperExpress from 'hyper-express'

const server = new HyperExpress.Server()

function shouldCompress(request: HyperExpress.Request, response: HyperExpress.Response) {
  if (request.headers['x-no-compression']) return false
  return compression.filter(request, response)
}

// compress all responses
server.use((request, response, next) => {
  const compress = compression({ filter: shouldCompress })
  return compress(request as any, response, next)
})

Also tried following express guide, no luck:
import compression from 'compression'
import HyperExpress from 'hyper-express'

const server = new HyperExpress.Server()

function shouldCompress(request: HyperExpress.Request, response: HyperExpress.Response) {
  if (request.headers['x-no-compression']) return false
  return compression.filter(request, response)
}

// compress all responses
server.use(compression({ filter: shouldCompress }))

I'm testing it with curl --head

Hey, this middleware does not seem to be maintained anymore given by the last publish 5 years ago. I am assuming it is depending on an old compatibility method or behavior from Express. When you use it with hyper-express, what if any errors / stack traces do you see in the console?

@kartikk221
import HyperExpress from 'hyper-express'
import compression from 'compression'

const server = new HyperExpress.Server()

function shouldCompress(request: HyperExpress.Request, response: HyperExpress.Response) {
  if (request.headers['x-no-compression']) return false
  return compression.filter(request, response)
}

server.use((request, response, next) => {
  const compress = compression({ filter: shouldCompress })
  return compress(request, response, next)
})

server.all('/', (request, response, _) => response.send('Hello World'))

const PORT = Number(process.env.PORT ?? 3034)
server.listen(PORT)

curl http://localhost:3034 --head

# no compression headers
HTTP/1.1 200 OK
Date: Wed, 22 Nov 2023 03:34:49 GMT
Content-Length: 11

Type errors:
compression.filter request and response arguments types are incompatible with HE request type:
Argument of type 'Request<DefaultRequestLocals>' is not assignable to parameter of type 'Request<ParamsDictionary, any, any, ParsedQs, Record<string, any>>' with 'exactOptionalPropertyTypes: true'. Consider adding 'undefined' to the types of the target's properties.
  Type 'Request<DefaultRequestLocals>' is missing the following properties from type 'Request<ParamsDictionary, any, any, ParsedQs, Record<string, any>>': accepted, host, route, signedCookies, and 13 more.ts(2379)

So is the incompatibility just TypeScript types or is it a functional incompatibility? I notice that you said there are no compression headers added, so the middleware is just not running at all?

So is the incompatibility just TypeScript types or is it a functional incompatibility? I notice that you said there are no compression headers added, so the middleware is just not running at all?

Yes not running at all. It seems to have no effects

I see, that likely means there is some method / property which is incompatible under the hood. For now, HyperExpress has limited compatibility with Express.js and this would be one of the cases where this middleware is just not compatible. The likely reason is that the middleware is old and not maintained anymore so it likely depends on an older and more obscure property/method from Express that is not supported at the moment.
The next major version update will make some breaking changes to increase the compatibility with Express, so that might resolve your issue in the future but for now this middleware would be incompatible.

@o-az Looks like this is not an incompatibility with hyper-express (besides type errors).
The compression library seems to require the "Content-Type" header to properly understand if the content is compressible. See the compressible library for details. Here's excerpt from compressible's README explaining the filter logic:

The MIME is looked up in the mime-db and if there is compressible information in the database entry, that is returned. Otherwise, this module will fallback to true for the following types:

text/*
*/*+json
*/*+text
*/*+xml

Word of advice:
Next time you encounter an old Node.JS library you want to use with little documentation (it will happen), look at the source code. They are typically 1 short JS file with decently readable code, especially if they have multiple dependencies.


Does this support 5050 rgb strips or only the WS2812 that are addressable ?

Hi,
Does this support 5050 rgb strips or only the WS2812 that are addressable ?
donnib

Only addressable LED Strips.

On his Youtube page he links these:
https://www.youtube.com/watch?v=9KI36GTgwuQ&t=215s
https://www.amazon.com/gp/product/B01CNL6MNM/ref=as_li_ss_tl?tag=brau01-20&ie=UTF8&psc=1&linkCode=ll1&linkId=b171287418103cdf0b7b5029b77e8f6e
These appear to be both 5050SMD and Addressable, however I am also having an issue getting the Addressing to work.


Remove plug.dj link from Gitter / camperbot / elsewhere

http://plug.dj has sadly shut down for good. Lots of campers are confused as to why the link is not working.

@michael-krebs I don't see any good in shutting down plug.dj but I've filed an issue for removal in camperbot dcsan/gitterbot#180

Thanks @abhisekp , I forgot camperbot had its own repo. I will close this one.


fix: step cleanup not capturing current step

What this PR does / why we need it:
This PR fixes step cleanup not capturing the current step.
Without that, cleanup is only invoked with the last step pointer (called multiple times, one per step).

/lgtm

Does this PR close issues #397 and #253? Or would PR #402 address any of those?

Does this PR close issues #397 and #253? Or would PR #402 address any of those?

I bet it fixes #253, not sure about #397.

not sure about https://github.com/kudobuilder/kuttl/issues/397

From what I saw in the code base it should be correctly handled.


fix: regenerate timeline after routeset

About the Contributor
This pull request is posted on behalf of the BBC
Type of Contribution
This is a: Bug fix
New Behavior
Follow up to #1272
When toggling a routeset which affects ab-players, this should also regenerate the timeline so that the timeline is using the correct set of ab-players.
This will now check whether a routeset may affect the timeline, and will regenerate it if so.
This means it should have no additional cost for routesets which do not control an abplayer.
Testing

[ ] I have added one or more unit tests for this PR
[ ] I have updated the relevant unit tests
[x] No unit test changes are needed for this PR

Affected areas

Time Frame

Other Information

Status

[x] PR is ready to be reviewed.
[x] The functionality has been tested by the author.
[ ] Relevant unit tests has been added / updated.
[ ] Relevant documentation (code comments, system documentation) has been added / updated.

I've discovered a bug in this implementation, where the updateTimeline gets run with the old routeset values. I will submit a new PR with a fix for this soon


Generics in a method can't recognize proper return type

enum Bar {
  x
}
class Foo {
    E doSomething<E extends Enum>() {
      return Bar.x;
    }
}

This code doesn't compile.
It returns error A value of type 'Bar' can't be returned from the method 'doSomething' because it has a return type of 'E'., while clearly Bar is Enum

In your issue, please include:

Dart version and tooling diagnostic info (dart info) -> - Dart 3.0.0 (stable) (Thu May 4 01:11:00 2023 -0700) on "windows_x64"
Whether you are using Windows, macOS, or Linux (if applicable) -> Windows 10
Whether you are using Chrome, Safari, Firefox, Edge (if applicable) -> N/A

I'm not sure if this is the same issue, but this code:
E findEnum<E extends Enum>(
  final List<E> values,
  final String enumStr,
) =>
    values.asNameMap()[enumStr]!;

enum Bar<E extends Enum> {
  foo
}

class Foo {
  Bar<E> doSomething<E extends Enum>() {
    return findEnum(Bar.values, 'foo'); //this does not compile
    //return findEnum(Bar.values as List<Bar<E>>, 'foo'); //this works
  }
}

returns error: The argument type 'List<Bar<Enum>>' can't be assigned to the parameter type 'List<Bar<E>>'.dart[argument_type_not_assignable]

The example in the original posting is working as intended. Consider this variant:
enum Bar { x }
enum Baz { x }

class Foo {
  E doSomething<E extends Enum>() {
    return Bar.x;
  }
}

void main() {
  Baz value = Foo().doSomething<Baz>();
}

If it had not been an error for doSomething to return an object of type Bar when the return type is E extends Enum then we would be able to obtain a reference of type Baz to the object Bar.x. That would be a soundness violation. This is the basic reason why we can't have a type rule that allows this code.
At the level of concrete type rules, we can't prove that Bar is a subtype of E. To see why we can't prove that, just note that the value of E could be Baz, and we don't have a subtype relationship from Baz to Bar.

For the example here, it is confusing that Bar has a type argument E (it is never used). Anyway, you can have an unused type variable if you wish.
However, consider this variant of the example:
E findEnum<E extends Enum>(
  final List<E> values,
  final String enumStr,
) =>
    values.asNameMap()[enumStr]!;

enum Bar<E extends Enum> { foo }

class Foo {
  Bar<E> doSomething<E extends Enum>() {
    return findEnum(Bar.values as List<Bar<E>>, 'foo'); // Throws.
  }
}

void main() {
  var bar = Foo().doSomething<Never>();
}

We invoke doSomething with the type argument Never (we just need to satisfy E extends Enum, and any enum type will do, and so will Never, so we can call it like that). Then, at the type cast Bar.values as List<Bar<E>> in doSomething, we encounter a run-time error.
This shows that the type cast is necessary, we couldn't have a set of type rules where this would be allowed without a cast.
It follows that the version you're showing (where the type cast has been removed) must be a compile-time error.
This is all working as intended, so I'll close the issue.


feat: add all spdx license

ref to: https://spdx.org/licenses/
To make licenseId a valid java variable name, these symbols have been mapped.
- -> _
. -> _
+ -> PLUS
0 at line start -> Zero

@drakeet please review


Concept - Slice Boundaries & RFC1918

Solves a part of #5
Explains concept of slice boundaries and RFC1918 network addresses.

cc @divya-mohan0209
I know the explanations need a lot of improvement, so I'll be awaiting feedback. Also I was confused if there should be a heading over the concepts or they'll be a part of the overview section.

Hey @sayantani11, good day! I actually intended the Glossary section to be separate and not a part of the overview section since it will be like a reference guide.

Hi @divya-mohan0209
Sorry was unavailable for a few days!
I will be doing the changes asap.

We don't have a glossary and the latest version is v 1.2.
We have revamped the entire sidebar and we have taken the two glossary terms and see if we can add them in our docs. The tracker is https://avesha.atlassian.net/browse/AM-12896.
cc @narmidm


"Unknow file extension" error when running an empty project with Node 18.1.0

I use node 18.1.0 and I tried this tool by creating a sample project by running these commands :
./bin/tspico8.js init -d test-project
./bin/tspico8.js run -d ./test-project/

After Typescript is done compiling and uglify is done compressing, when ./node_modules/.bin/jspicl-cli is ran, it just hangs there so I ran the jspicl-cli command manually and this is what I got :
node:internal/errors:466
    ErrorCaptureStackTrace(err);
    ^

TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension "" for<EMAIL_ADDRESS>Loading extensionless files is not supported inside of "type":"module" package.json contexts. The package.json file<EMAIL_ADDRESS>caused this "type":"module" context. Try changing<EMAIL_ADDRESS>to have a file extension. Note the "bin" field of package.json can point to a file with an extension, for example {"type":"module","bin":{"cli":"./bin/cli.js"}}
    at new NodeError (node:internal/errors:377:5)
    at Object.getFileProtocolModuleFormat [as file:] (node:internal/modules/esm/get_format:80:11)
    at defaultGetFormat (node:internal/modules/esm/get_format:122:38)
    at defaultLoad (node:internal/modules/esm/load:21:20)
    at ESMLoader.load (node:internal/modules/esm/loader:431:26)
    at ESMLoader.moduleProvider (node:internal/modules/esm/loader:350:22)
    at new ModuleJob (node:internal/modules/esm/module_job:66:26)
    at #createModuleJob (node:internal/modules/esm/loader:369:17)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:328:34)
    at async Promise.all (index 0) {
  code: 'ERR_UNKNOWN_FILE_EXTENSION'
}

Node.js v18.1.0

I managed to get the tool working by renaming ./node_modules/jspicl-cli/bin/cli to cli.cjs and ./node_modules/jspicl-cli/bin/plugin to plugin.cjs.
I also needed to change the paths in cli.cjs and ./node_modules/.bin/jspicl-cli of course.

Looks like this issue exists already here since nearly two years 😕
https://github.com/jspicl/jspicl-cli/issues/5
@tmountain what node version do you use to not have this problem ?

Yes sorry, I saw your patch just now. It's still weird that removing the "type": "module" just doesn't work with node 18.
I'm working on a quick fix to update jspicl-cli, maybe I'll make a fork later as you said.

In my first message I told you everything I changed but I'll put the changes here so it's easier.

node_modules/.bin/jspicl-cli
 if [ -x "$basedir/node" ]; then
+  exec "$basedir/node"  "$basedir/../jspicl-cli/bin/cli.cjs" "$@"
else
  exec node  "$basedir/../jspicl-cli/bin/cli.cjs" "$@"
fi

Also, after succeeding in running the tool, I created a class in ts and everything broke.
I changed another thing in jspicl-cli to fix it, do you want me t make another issue to explain this maybe ?

In my first message I told you everything I changed but I'll put the changes here so it's easier.

Files to rename
- node_modules/jspicl-cli/bin/cli
+ node_modules/jspicl-cli/bin/cli.cjs

- node_modules/jspicl-cli/bin/plugin.js
+ node_modules/jspicl-cli/bin/plugin.cjs

node_modules/.bin/jspicl-cli
if [ -x "$basedir/node" ]; then
-  exec "$basedir/node"  "$basedir/../jspicl-cli/bin/cli" "$@"
+  exec "$basedir/node"  "$basedir/../jspicl-cli/bin/cli.cjs" "$@"
else
-   exec node  "$basedir/../jspicl-cli/bin/cli" "$@"
+   exec node  "$basedir/../jspicl-cli/bin/cli.cjs" "$@"
fi

node_modules/jspicl-cli/bin/cli.cjs
const yargs = require("yargs");
const rollup = require("rollup");
- const jspiclPlugin = require("./plugin.js");
+ const jspiclPlugin = require("./plugin.cjs");

const options = {

Also, after succeeding running the tool, I created a class in ts and everything broke.
I changed another thing in jspicl-cli to fix it, do you want me to make another issue to explain this maybe (if you want to patch this change too, or to discuss a potential fork) ?


install fails on windows

$ node --version
v6.9.1
$ npm --version
4.0.2
running from Git2.0 bash console and from standard cmd, both fails....
$ npm install libxml

<EMAIL_ADDRESS>preinstall C:\workspaces....\node_modules.staging\libxml-e08c8558
./build.sh

'.' is not recognized as an internal or external command,
operable program or batch file.
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\meebo\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "install" "libxml"
npm ERR! node v6.9.1
npm ERR! npm  v4.0.2
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>preinstall: ./build.sh
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>preinstall script './build.sh'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the libxml package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     ./build.sh
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs libxml
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls libxml
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     C:\workspaces\upm2-igate\iclose\npm-debug.log

See all the other issues about this for help.

Sorry i have probably reported to wrong project :-)


Sanitize URL before sending it to logs.

What are we going to do about this PR? Can I merge it?

I don't know. You said to me 1y or maybe two ago. That you do not like the solution and you will think about better one. I guess it never happened. The idea here is that security advisor is complaining (quite rightly), that malicious agent can break the logs by adding whitespace to url.
This is one way of dealing with it.

Found it. It should be https://pkg.go.dev/net/url#URL.ESCAPEDPATH.


added mboutrecht

Added the domain mboutrecht but to make it work for the students.
A subdomain student needs to be added

all sudbomains will be covered by adding this domain - including student.mboutrecht.nl


Add codecov workflow

Codecov Report

:exclamation: No coverage uploaded for pull request base (dev@f33c88b). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Current head 54deda9 differs from pull request most recent head 800b10a. Consider uploading reports for the commit 800b10a to get more accurate results

@@          Coverage Diff           @@
##             dev      #49   +/-   ##
======================================
  Coverage       ?   98.44%
======================================
  Files          ?       10
  Lines          ?      258
  Branches       ?        0
======================================
  Hits           ?      254
  Misses         ?        4
  Partials       ?        0

Continue to review full report at Codecov.

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


Update continuous integration

Problem: Publishing this project to pypi was manual, meaning I rarely published updates.
Solution: This changes to a new GH action for publishing to pypi automatically based on version increments in pyproject.toml. It also adds a build step so that tests and publishing work off the same build. Other changes:

Matrix testing across windows, mac and ubuntu and multiple python versions
Inlined units test into package to enable running them from the installed package (just run summit-tests)
Updated packages to fix #172
Fixed issue with readthedocs not working due to https://github.com/sphinx-doc/sphinx/issues/10291

Closed in favor of #174, #175, #176, #177


Determine and document BoxedUint widening arithmetic semantics

Arithmetic with BoxedUint needs to deal with values whose number of limbs don't match. This is true of Uint as well, but there everything is nicely type safe.
So far the internal BoxedUint::chain operation (which addition and subtraction are implemented in terms of) handles widening to the widest of the two inputs.
The wrapping_* and checked_* functions use the self/left-hand side argument as the overflow width.
The mul_wide operation widens to as many limbs as are in the sum of the number of limbs in the operands (though should perhaps be renamed to just BoxedUint::mul for consistency with Uint::mul, which is also a widening multiply.
This seems like a reasonable enough approach, but whatever one we take should be thoroughly documented, both as an overall policy and on the individual functions.
We should also ensure it's consistent with how Uint performs widening, where applicable.

I should probably add some context that these semantics are necessarily different from your typical num-bigint-style arbitrary precision library.
Notably in cryptographic cases we want all of the values to be the same precision, or if not that, then known/fixed precisions at every point in the program. In the case of an algorithm like RSA, that would be the number of bits of precision in the RSA modulus. This means preserving leading zero limbs in such cases, so that we don't wind up with value-dependent timing variability with respect to the number of limbs.

Automatic widening when instantiating BoxedMontyForm should also be considered here. BoxedMontyForm::new currently panics if integer and params have different precision, but I think it makes sense to automatically widen the integer if it is less precise than the params. I am not sure if we should consider widening the params since it has more moving parts.


Description panel's title text wrapping issue

Describe the bug
The description panel's title text sometimes overflows and covers the content text area.
(Reported by Max Wang)

Fixed via #8503


feat: remove Box and xstyled

Closes https://github.com/scaleway/scaleway-ui/issues/548

We should also remove xstyled from the keywords of the website:
https://github.com/scaleway/scaleway-ui/blob/83f4eba908d2ece825fa484320b459721a7c8c8e/website/src/pages/_document.tsx#L65


feat(ci): setup CI to push scorecard, bundle and spit tests

Welcome to Cryostat! 👋
Before contributing, make sure you have:

[x] Read the contributing guidelines
[x] Linked a relevant issue which this PR resolves
[x] Linked any other relevant issues, PR's, or documentation, if any
[x] Resolved all conflicts, if any
[x] Rebased your branch PR on top of the latest upstream main branch
[x] Attached at least one of the following labels to the PR: [chore, ci, docs, feat, fix, test]
[x] Signed all commits: git commit -S -m "YOUR_COMMIT_MESSAGE"

Fixes: #227, #493
Description of the change:

Add CI to push bundle and scorecard image (if not exists) to quay.io.
Add CI to run envtest and scorecard.
Update scorecard test to check for platform (i.e. add ingress configurations to Cryostat CR if on k8s).

Motivation for the change:
See #227, #493
How to manually test:
See CI job status:

https://github.com/tthvo/cryostat-operator/actions/runs/5042553727/jobs/9043312859
https://github.com/tthvo/cryostat-operator/actions/runs/5042639850/jobs/9043480603?pr=4

Push jobs on main push is failing on my repo since it does not have access to cryostat/cryostat but build steps seems to work fine.
Others
We also need to remove checks for build Expected — Waiting for status to be reported  as CI job name is changed.

I've seen this action before: https://github.com/helm/kind-action.

Thanks! We still need to pass in the path to config file. Tho, we can fix the version of kind and kubectl. Is there a version we want to set or whatever version (seems like latest) comes with ubuntu-latest is fine?

Sounds good! Thanks for that! Then we probably won't use that action as its pretty simple to launch kind.

We should push the operator image to ghcr.io and then pass that image to make bundle with OPERATOR_IMG.

Do u think we should patch the manager's pod template or the operator SA with the pullImageSecret?

Not the most intuitive way to patch imagePullSecrets but seems to work nicely:
Patch: https://github.com/cryostatio/cryostat-operator/pull/588/commits/46e6741382ecf68afcbeab0e7f4750a0025576db
Test run:  https://github.com/tthvo/cryostat-operator/actions/runs/5083194894/jobs/9133896077
How about that?

@ebaron Latest run after rebasing: https://github.com/tthvo/cryostat-operator/actions/runs/5083932753/jobs/9135558209

This is awesome, finally knocking off a major piece of that puzzle for doing CI in a k8s environment.

Niceee thanks you^^ Happy I could help with it :))


Don't warn about compatibility with urllib3 v1.23

Requests allows v1.23 in #4669, but the compatibility check at import
time still looks for 22. Bump the version to 23.
edit: I do wonder if these checks should just be removed since it's pinned in setup.py and pip doesn't let you install 23 anyway without #4669.
Signed-off-by: Jeremy Cline<EMAIL_ADDRESS>

Codecov Report

Merging #4675 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #4675   +/-   ##
=======================================
  Coverage   66.62%   66.62%
=======================================
  Files          15       15
  Lines        1564     1564
=======================================
  Hits         1042     1042
  Misses        522      522

Continue to review full report at Codecov.

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

FYI: similar patches at https://github.com/requests/requests/pull/4671 and https://github.com/requests/requests/pull/4674 were rejected.

Hey @jeremycline, thanks for putting this together. We’re aware the tip of master is inconsistent and merging #4669 was a bit premature. In order to prevent multiple follow up PRs for other things we missed, we (maybe just I) decided we’d just wait to do all of the upgrade steps at once with the 2.19 release as per our usual release process.
We’ve addressed this a few times in a few other PRs and issues (#4671, #4673, #4674).

Ah cool. I should have checked closed PRs, sorry for the noise.