Feature: TriggerAsync with entities and/or returning a result

Hi Basti,
i've implemented three new TriggerAsync methods to be able to trigger events on an API containing a body/entity and/or returning a result.
Example:
/api/send
TriggerAsync<EmailMessage,Status>(mailMessage);
Cheers,
Andy

Hi Andy,
I really like the idea of a TriggerEndpoint that also takes and/or returns an entity. But perhaps it would be better to implement this in a separate TriggerEndpoint<TEntity> class? This way the consumer of the class would be forced to pass in the correct/expected entity type, rather than allowing different different type values for each call to .TriggerAsync<TEntity>(...). What do you think?
Regards
Bastian

Hi Basti,
well, that's a good point. But what about TriggerEndpoints which are only returning an entity but don't accept entities?
Cheers,
Andy

Good point! How about this:
No input entity:

TriggerEndpoint (no result entity)
TriggerEndpoint<TResult> (with result entity)

With input entity:

ProcessEndpoint<TInput> (no result entity)
ProcessEndpoint<TInput, TResult> (with result entity)

Hi Basti,
i think your solution would be the best one. But i'm not sure whether ProcessEndpoint is a good name, because a Trigger triggers a process, right? That can be confuse the consumer.
Maybe we just name the ProcessEndpoint -> TriggerEndpointWithEntity?
Cheers,
Andy

My thinking was that a ProcessEndpoint processes an entity (like processing an order) while a TriggerEndpoint is only triggered without any additional parameters (like pulling a trigger).
But you are right, the name Process by itself could be confusing. Maybe ProcessingEndpoint<T>?

Hi Basti,
IMHO it'll be still confusing as for the same reason as i already mentioned:

A TriggerEndpoint triggers a process which is processing some workflow.

and on the other side:

A ProcessingEndpoint triggers a process with an entity which is processing some workflow.

As i have no other idea than naming it TriggerEndpointWithEntity, you as the owner have to decide ;-)
Cheers,
Andy

I think I've finally come up with the "perfect" solution. ;)

ActionEndpoint for no input/output, like .NET's Action delegate type, replacing TriggerEndpoint
ActionEndpoint<TEntity> for input-only, like .NET's Action<T> delegate type
FunctionEndpoint<TResult> for output-only, like .NET's Func<TResult> delegate type
FunctionEndpoint<TEntity, TResult> for input and output, like .NET's Func<T, TResult> delegate type

Awsome!
If it's ok for you, i'll implement it.
Cheers,
Andy

Would be cool if you can make a release after this merge, so that i'm able to use from nuget in my project.
Thank you for your support.
Cheers,
Andy

Thanks a lot. I have merged your changes and did some additional refactoring.
I just pushed out v<IP_ADDRESS> to NuGet.


Provide clientId and clientSecret for testing

The documentation at https://spotware.github.io/open-api-docs/protocol-buffers/
says using
demo.ctraderapi.com:5035 for demo accounts
and live.ctraderapi.com:5035 for live accounts.
But meanhile my application submission gets approved, can you provide a clientId and clientSecret to test the API? With accountId and token as well.
Regards,
Vasile.

We will approve your application today, and after it got approved you can start using Open API.
Regarding trading accounts, you can create as many trading accounts as you want to for free easily on Spotware cTrader beta, which you can download it from here: http://ctrader.com/download/


Add tool use and majorly upgrade the README file

I know I went crazy on the README, but this is a great library and I want others to be able to take full advantage of it.

Just wanted to confirm I am using this in production and it's working well for me 👌


Consistency for rancher_password default value

Update rancher_password default value to be consistent between all recipes, also reduces the number of required variables to use a recipe

I removed the two-password approach while making these consistent amongst recipes/modules, if we'd still prefer an option for a separate password for the helm install, and bootstraping rancher I can revert to keeping both variables


ENHANCEMENT : Tabung > Cetak - Pagination (ReactJS + Go)

Perlu pagination by month

@adamjanin ada contoh di sini https://github.com/Dev4w4n/e-masjid.my/pull/156

done https://github.com/Dev4w4n/e-masjid.my/pull/161


Complete Rework

A complete innovation from yane to make multiprocessing and crossover easier. Some features will also be simplified.
Should also solve some underlying problems, such as the fact that sometimes neurons exist that shouldn't be there.
For the sake of clarity, the firing rate will be left out for the time being until yane is reasonably stable. Although the purpose of the firerate is to allow yane to think about inputs, this is not a priority for the time being. With the new implementation, it should be relatively easy to add it anyway.
Connections between neurons can still be created in all directions. However, the neural network will no longer know its connections, but will only be able to access them via the neurons.
In future, I will also use the word genome for a neural network. Or rather, a genome contains a neural network and should therefore represent the agent.
In addition, the way in which the population is managed has been redesigned. Instead of setting a maximum population and removing half of the lower population after evaluation, a reference value is now used. This means that genomes are only removed from the population if the population is above the reference value. This also gives more genomes the opportunity to develop.
Each gene (neuron/connection) now has a unique ID when it is created. With the help of this ID, it is now also possible to perform crossovers. A conscious decision was made against speciation and instead genomes should have the opportunity to live as long as their fitness allows. In the future, consideration was also given to giving individual genes a score in order to better decide which genes are favorable.
Another problem in the past was that the entire population was constantly re-evaluated. Now, only newly created genomes have to be assessed once. An evaluation list is now used for this, which contains genomes that do not yet have any fitness. The population is therefore only a collection of genomes for the creation of new genomes, while the genomes with poor fitness are gradually removed.
For the most part, the mutations function identically as in the past. The weight shift direction for the weight shift mutation will continue to exist, but the weights of the genomes will no longer be "optimized" as far as possible. In the future, as soon as yane is stable, we could consider testing whether it makes sense to optimize genomes that have been eliminated from the population as much as possible and try to reintroduce them into the population.
The size of the neural network is now also included in the fitness. The extent to which a genome is influenced by this can be set in the config. In principle, a genome receives a small penalty for each additional connection. Although it is possible that a offspring loses fitness and needs time to adapt, a large population allows a genome enough time.
Let's see how the rework goes.

For now, I will neglect multiprocessing and stay with multithreading instead.
Testing the fitness will be the only part that needs to be performant anyway. Although multiprocessing would improve the current implementation, the calculation will later be done via NumPy anyway, which should then run faster.
When GIL becomes optional, multiprocessing will no longer be needed anyway: https://peps.python.org/pep-0703/
I would not like to use multiprocessing as such, as the memory is not shared. I also need the possibility that a thread can also remove elements from a list that another thread is using. Although I could send messages to another process about which element should be removed, this is not the aim of the task distribution.
Alternatively, I may offer the option of managing the genomes on the hard drive in an SQLite database, which should work quite well with multiprocessing. Especially if the genomes need some time for evaluation anyway, the hard drive access should not have too much influence, as the next genomes are usually already being prepared during the evaluation. You can also be sure that the population is always saved.
Of course, the creation of new genomes in particular will be slower, as they have to be extracted from the database beforehand, but this process takes place independently in a separate process. It can therefore be assumed that creating new genomes will always be faster than evaluating genomes. Of course, there could be the exceptional case when you have a very small data set that is run through quickly. However, you also have to bear in mind that the training time should not be particularly long anyway. Should therefore be acceptable.
It might also be possible to agree on a hybrid solution, whereby the population itself is in the database and only the genomes to be trained are in the working memory. This could also work relatively well with multiprocessing, as the processes would only have to send the genomes to each other and not process the list itself.
This means that the processes that access the population do not have to communicate with each other and only have to send data to the process that takes care of evaluating the genomes and sends it back after evaluation.
Apart from multiprocessing, I would still have to think about how I want to enable the evaluation of several genomes at the same time. Currently, this is handled by overwriting the custom fitness function, in which you should also take care of the input data and output data.
It might be possible to use an additional parameter in which you can specify the number of simultaneous genomes. So, if you need several instances, it would be best to start the instance within the fitness function. It should also be possible for the user to use a lock if the genomes access the same data. For example, if read and write accesses are made to files. It might be possible to enable the use of a lock via the main class. In other words, you could just create yane = NeuroEvolution() and then use yane.get_lock().acquire() to secure the important part. Or you could use yane.acquire_lock() and yane.release_lock() instead. Or even better, the user can create any number of locks and then access them as an array, since there could also be cases where the user accesses two different files, but you don't want to lock both files when they are accessed. yane.create_lock(), yane.get_locks()[0].acquire() and yane.get_lock() or yane.acquire_lock() would always refer to the last lock element.


Remove rules for icmp messages already covered by conntrack

Some icmp message types are covered by the conntrack rule under the related-category.
https://github.com/torvalds/linux/blob/c1084b6c5620a743f86947caca66d90f24060f56/net/netfilter/nf_conntrack_proto_icmp.c#L106

Thanks!


Flutter engine doesn't clean up when closing on Windows Desktop

Flutter leaves several threads and resources up after closing.
This can be acceptable for many applications because the close operation will close the executable and rely on Windows to clean up all the threads and memory. However, if I want to open a new FlutterWindow after the previous one is closed, the existing threads cause the program to crash.
I see that flutter does not support multiple windows. I'm not trying to run multiple windows simultaneously. I am trying to open a window after another one is closed. However, the flutter_windows.dll remains loaded and the services it created don't get cleaned up. Is there an API for me to tell flutter_windows.dll to clean up?
Steps to Reproduce
I created a simple windows app using flutter create. Running the app, you will see before the engine is started, there are not many threads:

Now with the engine running, many threads are created:

After closing the app, the engine is left running in the dll and all the threads are still up.

Expected results:
I would expect a call to the flutter_windows.dll API to stop the engine and destroy all the resources.
Actual results:
All the resources remain as shown in the image above.
In a more complex example where I open a new window, I will sometimes get the following exception:
Exception thrown at 0x00007FFB796AEB5E (flutter_windows.dll) in example.exe: 0xC0000005: Access violation reading location 0x000001E9C33E4260.

I have not been able to recreate this in a simple example. However, I'm confident that if I could clean up the engine when/after it is closed, then recreation of a new one would not crash.

Hello @kenfred. Sorry but I cannot find a sample app linked with your original comment. Could you please provide either a public repository that can be cloned and run directly or alternatively, detailed reproduction steps so that I may verify the issue?

Hello @exaby73. Thanks for your reply.
What I'm referring to is the default app that is created with flutter create -t app example. To observe the issue, you can place a breakpoint at the end of main, like pictured above, and see all of the threads still running. This seems to be the root cause of my failure.
For my use case, I am opening another FlutterWindow after closing the first one. You could simulate this by putting your main function in a loop. However, this alone does not trigger the exception. I have tried, but I'm unable to make a small app to trigger the exception I mentioned. It seems to be timing-dependent within one of the threads in flutter_windows.dll. It happens only occasionally when a) I am opening a new FlutterWindow after closing the previous one and b) the variable time it takes to load my particular app happens to line up at a bad time with something inside flutter_windows.dll.
I believe this exception would not be possible if the root issue was solved, which is to ensure that all the threads are cleaned up when closing down a FlutterWindow.

@kenfred Unfortunately, without a reproducible sample, this issue is not actionable. I am not too familiar with C++ so I wouldn't be able to create the sample on my own. Could you provide a public repo as a sample for example? Even if it doesn't occur reliably, if it's at all reproducible, the issue can be taken forward. Thanks

Thanks @exaby73 I will try again to make a small example project. I will get back to you in a few days.

This sounds like the Windows version of the issue mentioned here for macOS: https://github.com/flutter/flutter/issues/96487
On macOS the lack of cleanup doesn't result in crashing, but in a memory leak.
If there was some way to manually fully clean up the engine, it would allow for some workarounds until full multi-window support is implemented.

@exaby73 I have created a simple example to demonstrate this issue on Windows. Please see this repo.
Note, the program seems to recover in Debug builds, but crashes in Release configuration.
To make it happen, I simply add a loop in main.cpp to create a new project and flutter window after the previous one is closed and destroyed.
Do you have any advice to clean up the flutter engine when the FlutterWindow is closed? For now, I'd be satisfied with a big hammer for a quick workaround. Any help you could give would be appreciated!
Thanks!

Could you guide me on how to check the status of the dll file, whether it's loaded or not?

@exaby73 I have been using Visual Studio to see the threads that are running. Here are the steps:

Open up the visual studio solution:

Make sure flutter_reopen_crash is set as the active project

Set a breakpoint ion line 21 of main.cpp

Hit F5 to start debugging. When it breaks on line 21 the first time (before it has opened the FlutterWindow for the first time) you will see there are only a few threads running:

Hit F5 again, then close the flutter app window. The DartProject and FlutterWindow are destroyed when they go out of scope at the end of the loop. When the loops starts again and breaks agaisnt at line 21, you will see that there are many threads left over from the dll.

Hit F5 again and it will attempt to create a new DartProject and FlutterWindow. However, if you did this in a release build, you would crash because of an access violation in one of those threads left over inside flutter_windows.dll. (I'm not sure why it does not crash in a Debug build).

This leak doesn't affect most users because they intend for the executable to end when the app is closed. In my case, I want to open a new FlutterWindow.
IMO, a proper fix would be to do one of:

Neatly tear down the flutter engine when the FilterWindow is destroyed
Make the flutter engine robust and handle the case when a new window is opened

The repo you provided, doesn't include the solution.

Triage report
I can reproduce this issue. After closing the window the first time, I can observe a few threads that remain. The number of threads don't increase as I keep opening and closing new windows though. Labelling this issue for further insights from the team.

Hi @exaby73. Any updates on this issue? Is there an API for me to manually destroy the engine and all of its threads?

Hey @kenfred. The team would have to look at the issue and assign a priority. It takes a bit of time sometimes due to the amount of issues and other higher priority issues. You can look at Issue hygiene to find out more about the prioritization process

Flutter Desktop apps (Windows) are not executing dispose methods when closing via exit(0).
Is that the correct way to close the app?


Fix deprecation warning about prune

When you deploy on new versions you can see this deprecation:
W0723 20:57:03.499655    2113 prune.go:71] Deprecated: kubectl apply will no longer prune non-namespaced resources by default when used with the --namespace flag in a future release. To preserve the current behaviour, list the resources you want to target explicitly in the --prune-allowlist flag.

This is not an issue right now, but it should be fixed for the future.

Related:
https://github.com/kubernetes/kubernetes/pull/110907

Based on this comment we can probably just ignore the warning (no code changes needed in this gem).


Flat message doesn't have transparent background

When setting the flat property on a message, the background isn't getting set to transparent (like it does on notify).
Photos describing the behavior:
What it should look like:

What's actually happening:

Using the following code:
      this.$dialog.message.error('This should be flat', {
        flat: true,
        position: 'bottom',
        timeout: 0
      })

UPDATE:
I've noticed the class theme--light is still set for message, but it should be theme--dark (like it is in notify).

Please describe me how do you connect this module to your project, and version of module. Because I checked and this works fine for me.
You have to put your app vuetify instance  in the dialog context (if you don't use nuxt module)
Vue.use(VuetifyDialog, {
context: {
vuetify <- this is important
}
})


more command line options?

Hi!
we are using tomcat here and no reload plugin worked except this one!
I´m really excited about that but I miss 2 features.
I'm using the cmd and integrated it into my IDE.
My questions are now:

Is it possible to specify more than one directory with the cmd?
I saw a -d parameter on the original node-livereload plugin...

Can I change the default extensions with the cmd?
We are using .jsp instead of .html and it's not in the list.

Thanks!

I just discovered Browsersync, which satisfies both

more than one directory
specify extensions from command line

... and much, much more. I'm not sure if command line supports multiple directories, but you can pass the proper options via Gulp or Grunt.
npm install -g browser-sync
browser-sync start --server --directory --files '**/*'


Update to ACK runtime 0.7.1

Brings in ACK runtime 0.7.1 and updates the generator to support adopting Backups.
By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license.

/retest

/retest dynamodb-kind-e2e

Waiting for https://github.com/aws-controllers-k8s/runtime/pull/34 to fix status issues in e2e tests

/lgtm


StatusPanel's buttons renaming

according to https://github.com/DevExpress/testcafe-studio/issues/1446
Little changes in docs are required

@testcafe-build-bot \retest


Add copyrights

Our JS files were missing copyrights. I think they're... important, yes?

@kevmoo @RedBrogdon do you know if these are needed? Is it kosher to just slap "2021" on all of them?

🤷  won't hurt, I guess


Turbolinks 5 Support

Added turbolinksShim to support older versions of Turbolinks.
Updated dummy to use Turbolinks 5

I came up with two options to getting Turbolinks 5 in; update the event listeners or add a shim so we can have support for both the classic and Turbolink 5 events. I decided on the latter, based on the one in the Turbolinks 5 docs, that translates the classic events to the new Turbolinks 5 events giving support for classic and Turbolinks 5.
https://github.com/turbolinks/turbolinks#should-i-use-turbolinks-5-or-turbolinks-classic
https://github.com/turbolinks/turbolinks/blob/master/src/turbolinks/compatibility.coffee

@aaronvb my gut tells me that we want to detect which version of turbolinks is in use, rather than using a shim. Did you have a PR for doing the non-shim way?

@justin808 That was my initial idea but I haven't found an easy way to detect the javascript version of Turbolinks. I can see there are completely new functions between classic and 5, and I can do a comparison with that, but that seems hacky. Do you know of a way to figure out the version of Turbolinks loaded in the DOM?

@justin808 Forgot to note that the shim is based on https://github.com/turbolinks/turbolinks/blob/master/src/turbolinks/compatibility.coffee

You should be able to determine this in 2 ways:

On the ruby side, check the VERSION in the gem
On the JS side, there's probably some function names on the Turbolinks object that differ between v2 and v5.

@justin808 since this is being handled in the npm_module I'll have to use the second option. I'll make another PR with the version check method. Thanks for the feedback!

See https://github.com/turbolinks/turbolinks/issues/6

Closed in favor of #270


PECL release command

Adding a PECL release command to fetch and modify package.xml for a new extension version.
Moving some reusable code from ReleaseCommand into an abstract function to share with PeclCommand.

Codecov Report

Merging #5 (d6790a4) into main (bfd73a5) will decrease coverage by 6.29%.
The diff coverage is 0.66%.

:exclamation: Current head d6790a4 differs from pull request most recent head 5e41a6f. Consider uploading reports for the commit 5e41a6f to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files

@@             Coverage Diff              @@
##               main       #5      +/-   ##
============================================
- Coverage     78.01%   71.72%   -6.29%
- Complexity      348      365      +17
============================================
  Files            36       38       +2
  Lines          1046     1139      +93
============================================
+ Hits            816      817       +1
- Misses          230      322      +92

Flag
Coverage Δ

7.4
71.70% <0.66%> (-6.29%)
:arrow_down:

8.0
71.70% <0.66%> (-6.29%)
:arrow_down:

8.1
71.70% <0.66%> (-6.29%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...Console/Command/Release/AbstractReleaseCommand.php
0.00% <0.00%> (ø)

src/Console/Command/Release/PeclCommand.php
0.00% <0.00%> (ø)

src/Console/Command/Release/ReleaseCommand.php
0.00% <0.00%> (ø)

src/Console/Application/Application.php
100.00% <100.00%> (ø)

Continue to review full report in Codecov by Sentry.

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


Making the upgrade more specific

Calling full system upgrade without even asking the user is a horrible idea.
Several rather difficult to set up things just got broken for me, since I specifically use selected versions of some software and I have to manually override some dependencies. I doubt that I am the only one in the wild who does this and this is a public repo.
I suggest this change - specifically upgrade what we need. Alternatively, remove the -y, so that the user is at least informed.

I agree that this was not "polite". However, I would advise making your system work with the up-to-date packages. So when the time comes to, e.g., reinstall you Ubuntu, you will not be in huge trouble.

If you need a specific version of a package and still want to be able to upgrade your system I recommend holding the package using apt-mark hold <package>.

Thanks. In ideal world, having everything up-to-date would be the best possible setup. In reality, however, this is not always possible. Case in point - Cuda and Nvidia graphics drivers are always paired version-wise. However, some versions of the NVidia drivers break my X11 on my laptop, and these are typically the new (untested) ones that are paired with a Cuda version that I need. @petrlmat can I do the hold system-wide?

Oh, apt-mark hold, I did not know that. That is great! We should probably "hold" our Mavros since its new version will immediately cause a compilation error of the uav_core.


[BUG] Complete Sales Order Without Refreshing Page

Describe the bug
Upon completing all shipments associated a sales order in the pending shipments menu, the page needs to be refreshed before the order can be completed using the "Complete Order" button. If the page is not refreshed, the button is slightly faded and cannot be clicked.
Additionally the value shown in the "Completed Line Items" is not updated after allocating stock or removing line items.
The "Completed Shipments" field also experiences the same issue when creating, deleting or completing a shipment (regardless of whether it is a partial or complete shipment of the SO).
Steps to Reproduce
Steps to reproduce the behavior:

Ship last pending shipment in SO.
View "Complete Order" button at top right of screen.

Expected behavior

The "Completed Line Items" and "Completed Shipments" fields should be updated and the "Complete Order" button should be clickable. (Minor quality of life improvement).
Screenshots

Before Refresh:

After Refresh:

Deployment Method

[x] Docker
[ ] Bare Metal

Version Information
InvenTree-Version: 0.6.2
Django Version: 3.2.12
Commit Hash: 950d185
Commit Date: 2022-03-10
Database: mysql
Debug-Mode: True
Deployed using Docker: True

Thanks @maksimstojkovic

Can you please assign this issue to me

@pulimoodan any progress on this? Let us know if we should assist

We also have the same behaviour on other pages ("header" does not refresh automatically to show uptodate information):

build order (badges on the left, completed quantity on the right)
purchase order (order status on the left, completed line items and dates on the right)

@rkalman you are right, a lot of pages could be updated to be more "reactive" and make use of the API rather that being rendered statically. This will require a bit of work

I am reluctant to spend heaps of effort on a patch fix given we are intending to move to a API-heavy framework anyway.

Sorry for the long time to reply, I had been into something else.
I tried playing around this issue. As it is Django static template we have to refresh the page or implement it with Ajax and JS. But Ajax will look more complex when we have to work over it for more feature.
Like @matmair  said, it's good to implement this feature in React or Vue and it's easy to do that. Are we moving to any API framework. If the front-end is going to be build in React, I can help you.

I think everyone can live with this behaviour, I just mention them because they are all similar to the first one.

It's probably a little primitive in the context of robust software implementation, but it's possible to make the Shipment Completion form (and all other offending forms) automatically reload the page on submission, effectively automating the page refresh.
Given that it is not currently worth everyone commiting time to a large-scale change with an upcoming release and future updates already in the dev pipeline, is this a sufficient fix in the mean time, or is it likely to cause problems in the future?

@maksimstojkovic I'm happy with the proposed fix as a "bandaid" pending UI overhaul.


search icon and hidden icon disappear

search icon and hidden icon disappear,who can help me?

Could you provide us with a jsfiddle with your setup, based on one of these?

react-instantsearch: https://jsfiddle.net/ar80rgpc/6/
instantsearch.js: https://jsfiddle.net/vvoyer/0wm3donb/4/

Also it's useful to know which version of instantsearch.js you're using.
Hope we can help!

I think you're missing the import of font-awesome, you can link it like this:

@Haroenv thank you,i fix this bug with you suggestion.


removed failed connections from the pool

Attempted fix for issue:
https://github.com/basho/riak_repl/issues/723
the pid of the dead process was being left in the 'pending' list.
i haven't figured out the original scenario that put it into this state but this bug would have been responsible for the repetitive retries and 'noproc' crashes.

Does the fail_request/3 call in L401 not remove the request from the pending list https://github.com/basho/riak_repl/blob/develop-3.0/src/riak_core_connection_mgr.erl#L654?


Make it easier for users to track the environment build being used

Context
I have a desire as an end user, to specify the build rather than the environment that a notebook or script uses.
One possible workflow for this (though there are others):

I have a notebook that uses a conda-store environment. As an end user, I have no visibility into which build is loaded in my notebook.
Over time, I rebuild the environment several times, the latest build becomes the "active" build.
Notebooks still points to previous build from step 1, but I want to use the updated env.
Load a different env in the notebook
Load the original environment (effectively switching to the "active" build)
Realize that my notebook no longer works and decide to rollback.
Attempt to recall the date of the build that worked for the notebook and make it the "active" build.
Repeat steps 4-7 until I figure out the build that worked.

Rolling back to different builds of environments is "easy" in conda-store but the practical usage of it in Jupyter Notebooks (or python scripts) is less clear. It is handy to just say "this runs in this environment" and let conda-store handle which environment is active. But in reality, its often really useful to say "run this in this environment build" which is much more explicit. And if not that, then just make it easier for me to know which build I'm currently using.
I believe there are symlinks which are obfuscating the environment name from the build hash. I'm wondering if its possible for me as an end user to point to the build hash itself?
Or maybe we could add a symlink that adds part of the build hash to the env name? The same hash could be shown in the conda-store UI for easy visibility and cross reference. That would cause a LOT of noise so I'm sure that would take some effort to control.
Value and/or benefit
Improved practical usage of conda-store
Anything else?
No response

This is what is jupyterlab can currently work with:
{
    "default": "python3",
    "kernelspecs": {
        "conda-env-nebari-git-nebari-git-dashboard-py": {
            "name": "conda-env-nebari-git-nebari-git-dashboard-py",
            "spec": {
                "argv": [
                    "python",
                    "-m",
                    "nb_conda_kernels.runner",
                    "/opt/conda",
                    "/home/conda/nebari-git/envs/nebari-git-dashboard",
                    "/home/conda/nebari-git/b41bf223-1727131653-101-dashboard/bin/python",
                    "-m",
                    "ipykernel_launcher",
                    "-f",
                    "{connection_file}"
                ],
                "env": {},
                "display_name": "nebari-git-nebari-git-dashboard",
                "language": "python",
                "interrupt_mode": "signal",
                "metadata": {
                    "debugger": true,
                    "conda_env_name": "nebari-git-nebari-git-dashboard",
                    "conda_env_path": "/home/conda/nebari-git/envs/nebari-git-dashboard",
                    "conda_language": "Python",
                    "conda_raw_kernel_name": "python3",
                    "conda_is_base_environment": false,
                    "conda_is_currently_running": false
                }
            },
            "resources": {
                "logo-64x64"<EMAIL_ADDRESS>                "logo-32x32"<EMAIL_ADDRESS>                "logo-svg"<EMAIL_ADDRESS>            }
        }
    }
}

And this is what user sees in the conda-store-ui:

To me it looks like this issue cannot be resolved on jupyterlab-conda-store side just yet, because the kernelspecs do not include the required information.
I see two potential way forward:

a) reviving https://github.com/Quansight/nb_conda_store_kernels and providing more conda-store specific metadata in kernelspecs, as discussed in https://github.com/conda-incubator/conda-store-ui/issues/428#issuecomment-2374124525
b) making this jupyterlab extension into a full-blown client of the conda-store API with bespoke logic for synchronizing environment state and metadata


TypeScript file using dom type definitions despite tsconfig instructing against that.

VSCode Version: 1.30.2
OS Version: Windows 10

Steps to Reproduce:

Create a folder and add in two files named node.ts and tsconfig.json

node.ts
window.console.log("hello world");

tsconfig.json
{
    "compilerOptions": {
        "types": []
    }
}

Open folder in vscode then open node.ts file.

expected behavior
A problem should appear regarding the type of window being unknown.
actual behavior
The definition of window is being resolved from C:\Program Files\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\lib.dom.d.ts.
This is inconsistent with TypeScript's documentation on how it reads tsconfig.json. See https://www.typescriptlang.org/docs/handbook/tsconfig-json.html

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

I think this is more of a problem with my understanding of tsconfig.
Changing the file to
{
    "compilerOptions": {
        "lib": [],
        "types": []
    }
}

causes the expected behavior.


Made the routingHelper functions publicly available

Description
By making the current two implemented routingHelper() functions in the router publicly available it allows a bit more abstraction by the user in terms of implementing generics if desired, by leveraging the use of the already public RouterMethod struct:
Instead of router.get('endpoint', handler:) I can now alternatively call router.routingHelper(.get, 'endpoint', handler:) if desired.
How Has This Been Tested?
-
Checklist:

[ ] If applicable, I have updated the documentation accordingly.
[ ] If applicable, I have added tests to cover my changes.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Sander de Koning seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
Sander de Koning seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

I have signed the CLA, will the CLAssistant pick up on that automatically to resolve the pending status?

Hi @sdekoning0, can you elaborate a bit on your use-case for this?
The name routingHelper is not something I think we'd want to expose as public API, we'd want to rename that to something more descriptive if we do decide this should be public.
Regarding the CLA, it looks like your commit was pushed with an id that Github hasn't linked to your account, so the CLA assistant doesn't know the contribution is yours.


Higher current shunt issue

I’m using an external 40A 75mV shunt with the ina226. When I input the values to the ina.setMaxCurrentShunt(40.0, 0.001875) I’m unable to measure any current.
Interestingly, if I use 20a I am able to read small currents (200-400mA) fairly accurately. I’ve yet to setup a test to pull larger currents.
Is having such a large max current reducing the A/mV too much that it’s unable to register any current or something else?

Thanks for reporting,
As I am quite busy with some other libraries it might take some days before I can investigate.
Think I need to reread the datasheet carefully for this one.

which platform do you use?  UNO / ESP?
can you post a schema of your setup?

Thank you.
Im using an esp32.
I will try to put a drawn schema together.
I’m using the same breakout board your were using for testing in issue #2 but when I first didn’t get any readings, I decided to remove the surface mounted R002 resistor from the board, thinking since both resistances were in parallel, it may cause issues.
I will try to get together a drawn schema for you. I’m using the same breakout module you were testing with in issue #2. Vin connected to one side of shunt. Vout connected to other side. Using a switch mode power supply positive connected with Vin at shunt and an led strip connected to with vout at shunt which then goes to ground of power supply.
Voltage readings are fairly decent (seems to be out +/- 350mV but that could also be my dmm as I need new leads) and as mentioned earlier, fairly accurate current readings at <1A with 20A setting but feel that might start to swing away with higher currents.

ina.setMaxCurrentShunt(40.0, 0.001875)
I had a quick look in the code and it is limited to 20Amps. The call should return false because params are out of range. You could test that.
Note for myself: check documentation.

I was worried about that. Call seemed to return just 0.00A.
Is the limit changeable?

You are free to change the code as it is open source, I do not know without further investigation if and how well that will work.
Remember that the sensor has a physical limitation. Advice read the datasheet, twice
Keep me informed of your insights, might help to improve the library and documentation.

After posting I realised I can just go to the .cpp and change so I will try that and report back.
I looked through the data sheet and didn’t see anything about a current limit. I suppose it’s not really measuring current, just the voltage drop. There is a max voltage between vin and vout of 81mV so if shunt resistance * max current was above that, I suspect chip might let the smoke out. But mine should only be 75mV at 40A

you may uncomment line 194  #define printdebug true to get some numbers.

I changed line #198 to max current > 40 and all has worked fine. I’m yet to confirm accuracy of current but will get to that.

mmm, the limit of 20 A was because the sensor can handle 20 A.
Code calculates the accuracy - LSB - from this value.
There might be no reason to prevent the math if current is "too high", just return a warning if the value is above 20 A.
This way the user can see if and where setting the internals failed.
Must dive into the datasheet and code to recall the details.
Just to hold my "current" thoughts, I'm thinking of this.
int INA226::setMaxCurrentShunt(float maxCurrent, float shunt, bool normalize)
{
  // #define printdebug true
  uint32_t calib = 0;
  uint32_t factor = 1;

  if (maxCurrent < 0.001) return INA_ERR_MAXCURRENT_LOW;
  if (shunt < 0.001) return INA_ERR_SHUNT_LOW;

  // do al the math

  if (maxCurrent > 20) return INA_ERR_MAXCURRENT_HIGH;
  return INA_ERR_NONE;
}

@Juicy-AUS
Sorry it took so long to respond,

But I think the breakout board, due to size of tracks, shunt resistor type etc is limited though.

That is definitely true
I'm going to create a develop branch without the limit check, will set a warning or so,  and update the documentation to reflect these new insights.

@Juicy-AUS
Created a develop branch for 0.4.0 which includes a 80 mV shuntVoltage check instead of a maxCurrent check

https://github.com/RobTillaart/INA226/tree/develop

If you have time could you check if it works for you?

@Juicy-AUS
This new version should work for you, otherwise reopen the issue.
If there are other problems, please open a new issue.

Thank you @RobTillaart. I’ve been a little busy but will put in this version and test when I can. I appreciate your work sir.


[AERIE-1738] Put/Get expansion_set, auto-update expansion_set_to_rule join table

Tickets addressed: AERIE-1738
Review: By commit
Merge strategy: Merge (no squash)

Description

Verification

Documentation

Future work

The issue with this one is that we’ll have to template in at least the $num in order to parameterize it appropriately unless you have a sneaky way to do that too
Sent from my iPhone
On Mar 8, 2022, at 17:54, patkenneally @.***> wrote:

@patkenneally commented on this pull request.

In command-expansion-server/src/app.tshttps://urldefense.us/v3/__https://github.com/NASA-AMMOS/aerie/pull/83*discussion_r822223489__;Iw!!PvBDto6Hs4WbVuu7!Y30CzeMRp7A2P70h_YwTxX4sI1Mm5juYllGzJusXXA2PM5s3Xf67et8rba-qBRD9K8W3cC3vNyJ5$:

});

return;
}

const { rows } = await db.query(`
WITH expansion_set_id AS (

 INSERT INTO expansion_set (command_dict_id, mission_model_id)

 VALUES (${commandDictionaryId}, ${missionModelId})

 RETURNING id

)
INSERT INTO expansion_set_to_rule (set_id, rule_id) VALUES

 ${expansionIds

   .map((expansionId: number) => `((SELECT id FROM expansion_set_id), ${expansionId})`)

   .join(",\n      ")}

RETURNING (SELECT id FROM expansion_set_id);
`);

Let's use parameterized queries as a general rule of thumb.
—
Reply to this email directly, view it on GitHubhttps://urldefense.us/v3/__https://github.com/NASA-AMMOS/aerie/pull/83*discussion_r822223489__;Iw!!PvBDto6Hs4WbVuu7!Y30CzeMRp7A2P70h_YwTxX4sI1Mm5juYllGzJusXXA2PM5s3Xf67et8rba-qBRD9K8W3cC3vNyJ5$, or unsubscribehttps://urldefense.us/v3/__https://github.com/notifications/unsubscribe-auth/ADFK2QY3LLHIYVZZEWXN5A3U7AAE7ANCNFSM5P4HMUVQ__;!!PvBDto6Hs4WbVuu7!Y30CzeMRp7A2P70h_YwTxX4sI1Mm5juYllGzJusXXA2PM5s3Xf67et8rba-qBRD9K8W3cFYrqYHV$.
You are receiving this because you authored the thread.Message ID: @.***>

The issue with this one is that we’ll have to template in at least the $num in order to parameterize it appropriately unless you have a sneaky way to do that too

Templating in a sequence of $1, $2 etc. isn't particularly problematic, since you have control over all data going into that process (and this is a very well-defined, localized kind of expansion). As long as the user data itself isn't getting interpolated, it's okay.

The issue with this one is that we’ll have to template in at least the $num in order to parameterize it appropriately unless you have a sneaky way to do that too

Templating in a sequence of $1, $2 etc. isn't particularly problematic from a security perspective, since you have control over all data going into that process (and this is a very well-defined, localized kind of expansion). As long as the user data itself isn't getting interpolated, it's okay.

To be fair - technically these apis are all behind hasura which is ensuring the values are Integers, so sql injection isn't really a risk. But I agree that parameterizing and templating in the $num is the more correct form and we should definitely do it

To be fair - technically these apis are all behind hasura which is ensuring the values we use here are Integers, so sql injection isn't really a risk.

True! But it feels like a latent bug -- if ever these endpoints get exposed for one reason or another, over the evolution of Aerie, we don't want to suddenly have SQL injection vulnerabilities crop up. Local properties are easier to verify than global ones!

I dwelt on sharing this same thought for the last hour... Assuming that one uncoupled/independent module is secure based on the presence of another nominally uncoupled module seems incorrect. I think that each Aerie module should be secure at it's boundary, regardless of our deployment configuration.

@Twisol @patkenneally
I mostly but don't entirely agree. I would think that Hasura is less of a service than an api layer that necessarily is coupling to our services. I would consider each of the services uncoupled from each other, but the API layer I would expect is something we can rely on. We change the form of our service endpoints to suit it after all.
But if that IS the position we want to take, then we need to do input validation on the apis as we can't rely on graphql for it, so let's add an issue for that.


Unable to convert Open API 3 of multipart/form-data requestBody to Swagger 2

I'm attempting to convert from Open API 3 to Swagger 2.
But I realized the converted schema has a few errors for requestBody multipart/form-data parameters.
My original schema is
      requestBody:
        required: true
        content:
          multipart/form-data:
            schema:
              type: object
              properties:
                name:
                  type: string
                image:
                  type: string
                  format: binary

and converted schema is
      consumes:
        - multipart/form-data
      parameters:
        - in: formData
          name: body
          required: true
          type: object

Actually in Swagger 2, form data parameters schema should be defined individually, like
      parameters:
        - in: formData
          name: name
          type: string
        - in: formData
          name: image
          type: file

See Also:

https://swagger.io/docs/specification/describing-request-body/file-upload
https://swagger.io/docs/specification/2-0/file-upload

Maybe, because it doesn't convert the params schema in multipart/form-data case.
I think MUTIPLART_FORM_DATA needs same converting with APPLICATION_X_WWW_URLENCODED one.
https://github.com/LucyBot-Inc/api-spec-converter/blob/master/lib/converters/openapi3_to_swagger2.js#L149-L153

Thanks for the report, I agree with your diagnosis. This is fixed in 2.7.21


Revert "Created java binary, library alias to third_party"

Reverts PolymerLabs/arcs#5789

This is not needed since we have native.oss.bzl rules in third_party/java/arcs.


Date converter does not work when running on Robolectric

Actually, this is not an issue of LoganSquare. I noticed that the DefaultDateConverter does not work when running on Robolectric.
Running on Android:
SimpleDateFormat accepts these format for the "Z" place holder: Z/ZZ/ZZZ:-0800 ZZZZ:GMT-08:00 ZZZZZ:-08:00
ref.) http://developer.android.com/reference/java/text/SimpleDateFormat.html
Running on Robolectric (JRE):
SimpleDateFormat only accepts "-0800" format for the "Z" place holder. Should use "X" place holder for ISO 8601 format.
ref.) http://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#rfc822timezone

Proposed fix:
Use +0000 in the DefaultDateFormatter.getFixedInputString() method. This works on both Android and JRE.
public class DefaultDateFormatter extends SimpleDateFormat {
    /** Replace ending Z's with +0000 so Java's SimpleDateFormat can handle it correctly */
    private String getFixedInputString(String input) {
        return input.replaceAll("Z$", "+0000");
    }
}

Sorry about the wait! I've made this change and will be merging into master over the weekend. I'll post another comment when it's in.

This has now been pushed to master in 7d6f2e6f6c0bd10e31b3fa9fce112e8cb0fb252c and is available on JCenter as version 1.1.0.


Merge pull request #1 from simple-lang/master

Merge upstream into appcypher/simple

This was a mistake

Ok.


Safari Only - Error: Requested keys of a value

I got an error on mobile browsers and Safari, the project works normally on chrome and firefox with 0 errors.
here is the error :
Error: Requested keys of a value that is not an object.keys @[native code]

i'm using the following modules
'checklist-model',
'ngRoute',
'ngCookies',
'ui.bootstrap'

i tried to remove file by file to determine the error but it's hopeless. here is a link for the project
http://matic.imenadigital.com/#/GetStarted
Thanks in advance

It's almost impossible to take action with at least the circumstances of the error. When does it happen? Is there a stacktrace?

I'm able to recreate this issue in Safari 7.1.4 at the provided url. Here is the stack trace:
Error: Requested keys of a value that is not an object.
keys@[native code]
sortedKeys@http://matic.imenadigital.com/bower_components/angular/angular.js:340:21
forEachSorted@http://matic.imenadigital.com/bower_components/angular/angular.js:344:24
buildUrl@http://matic.imenadigital.com/bower_components/angular/angular.js:9733:20
sendReq@http://matic.imenadigital.com/bower_components/angular/angular.js:9623:25
serverRequest@http://matic.imenadigital.com/bower_components/angular/angular.js:9383:23
processQueue@http://matic.imenadigital.com/bower_components/angular/angular.js:13248:29
http://matic.imenadigital.com/bower_components/angular/angular.js:13264:39
$eval@http://matic.imenadigital.com/bower_components/angular/angular.js:14466:28
$digest@http://matic.imenadigital.com/bower_components/angular/angular.js:14282:36
$apply@http://matic.imenadigital.com/bower_components/angular/angular.js:14571:31
done@http://matic.imenadigital.com/bower_components/angular/angular.js:9698:53
completeRequest@http://matic.imenadigital.com/bower_components/angular/angular.js:9888:15
requestLoaded@http://matic.imenadigital.com/bower_components/angular/angular.js:9829:24

There is a lot of JS in the files, a small jsfiddle or plunkr that reproduces the error would be useful.

That's an error in http's buildUrl function. It seem like something is passing params inside the config that are not an object - no idea why that makes Safari throw up, and not the others: https://github.com/angular/angular.js/blob/master/src/ng/http.js#L1145
That should help you try to reproduce the error.

I was able to reproduce the error,
$http({
        method: 'GET',
        url: 'http://website.com/api',
        headers: {
            'Authorization': 'Basic xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
        },
        params: 'limit=10, sort_by=created:desc'
    }).success(........

The error was in the params key , i removed it and it works fine now.
i think it's because these parameters are not supported in the API
Thanks very much guys.

I'm getting the same issue, but only on mobile safari and chrome!!! The stack call is the same as @andrewaustin:
[Error] Error: Requested keys of a value that is not an object.
keys@[native code]
sortedKeys@http://localhost:10006/vendor/angular/angular.js:340:21
forEachSorted@http://localhost:10006/vendor/angular/angular.js:344:24
buildUrl@http://localhost:10006/vendor/angular/angular.js:9733:20
sendReq@http://localhost:10006/vendor/angular/angular.js:9623:25
serverRequest@http://localhost:10006/vendor/angular/angular.js:9383:23
processQueue@http://localhost:10006/vendor/angular/angular.js:13248:29
http://localhost:10006/vendor/angular/angular.js:13264:39
$eval@http://localhost:10006/vendor/angular/angular.js:14466:28
$digest@http://localhost:10006/vendor/angular/angular.js:14282:36
$apply@http://localhost:10006/vendor/angular/angular.js:14571:31
done@http://localhost:10006/vendor/angular/angular.js:9698:53
completeRequest@http://localhost:10006/vendor/angular/angular.js:9888:15
requestLoaded@http://localhost:10006/vendor/angular/angular.js:9829:24
	(função anônima) (angular.js, line 11655)
	(função anônima) (angular.js, line 8596)
	processQueue (angular.js, line 13256)
	(função anônima) (angular.js, line 13264)
	$eval (angular.js, line 14466)
	$digest (angular.js, line 14282)
	$apply (angular.js, line 14571)
	done (angular.js, line 9698)
	completeRequest (angular.js, line 9888)
	requestLoaded (angular.js, line 9829)

Comment for future reference if anyone else comes here. Found the same error when using:
SomeService.update(some.id, some).$promise.then(...

Don't know why I wrote it like that, but the fix was simply:
SomeService.update(some).$promise.then(...


Correct README

Description

Correct README
Update badges and URLs

This PR fixes #7
Signed commits

[x] Yes, I signed my commits.

Thank you, @HeroicHitesh


test(oauth2): fix flaky test

Summary
In this PR, a flaky test which is caused by a conflict between routes with the same host field is fixed by change one of them to a local particular name
Checklist

[ ] The Pull Request has tests
[ ] There's an entry in the CHANGELOG
[ ] There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Full changelog

[Implement ...]

Issue reference

Fix #[issue number]

duplicates with https://github.com/Kong/kong/blob/530e4a7495ff502d6e4047e57e5fcd1fe48467b9/spec/03-plugins/25-oauth2/03-access_spec.lua#L402


Get mrenclave at build time

So far we have just loaded the enclave and have it compute the mrenclave by itself. But it would be good if we can get the mrenclave at build time. This would allow building a HW enclave on non-SGX-machine and get its mrenclave there. This could be used to build HW enclaves in GithubActions hosted runners and publish the mrenclave there for public verification.
This seems to be a feature of the SGX-tooling luckily: https://community.intel.com/t5/Intel-Software-Guard-Extensions/About-MR-ENCLAVE-and-MR-SIGNER-how-can-i-get-them/m-p/1154365

Our makefile can
Make mrenclave
Make mrsigner
But it may require an sgx machine, not sure

On my local machine non-sgx enabled machine, in our docker the following worked:
make clean
SGX_MODE=HW WORKER_FEATURES=dcap make
make mrenclave
Succeed.
MRENCLAVE: d823e37cc26b9d1f7da1fce3d7a66027da697d7037105ce593e8147ee01b18e5
make mrsigner
Succeed.
MRSIGNER: 83d719e77deaca1470f6baf62a4d774303c899db69020f9c70ee1dfc08c7ce9e

So I assume that this just works also on the GithubActions CI.

As the above seems very well possible, the question is how we integrate the enclave info into the CI artifacts:

create a metadata.txt, which contains mrenclave and mrsigner of all the generated binaries.
update our binary names, which are already very verbose, to include the mrenclave and mrsigner in the name, e.g., integritee-worker-sidechain-mr-<mrenclave>-ms-<mrsigner>-githubsha

Very soon, mrsigner will be of no interest anymore (once we change sealing to mrenclave and enable enclave updates)
Including mrenclave with the filename doesn't seem intuitive to me because the service binary could also use another enclave build without noticing a difference. Therefore, this may be misleading
A digest file would be my favorite. Maybe extract mrsigner and mrenclave directly into
Mrenclave.hex
Mrsigner.hex
?


Exposing a new JSRT method to get additional information about exceptions

This information includes the source file and line/column position of where the exception
came from, as well as the actual source content of the line.
The motivation for this method is for node to print it out on uncaught exceptions.

Is it possible to add a test under test/native-tests using this new interface? or using it from CH and a test touching it somehow? ATM CI doesn't test this new interface and if we break it later, we won't know.

I've extended one of the tests in JsRTApiTest.cpp to cover the new method.

@MSLaguana A thought of API design. Instead of this, how about keep using the existing JsGetAndClearException, but add a new API like JsGetExceptionMetaData(exception) in which to populate the info you needed? That'll avoid deprecating API and duplicating code.

How do you see that flow working? The additional information that we need is accessed through the JavascriptExceptionObject which is cleared and forgotten in JsGetAndClearException. It isn't a javascript value so I don't believe that I can attach it to the exception object, which is a javascript value (and may be any javascript value since it is whatever was thrown).

How do you see that flow working? The additional information that we need is accessed through the JavascriptExceptionObject which is cleared and forgotten in JsGetAndClearException. It isn't a javascript value so I don't believe that I can attach it to the exception object, which is a javascript value (and may be any javascript value since it is whatever was thrown).

Indeed that is a problem. I can only think of an ugly workaround that may have problems (use an InternalProperty to store the exceptionRecord in the thrownObject. Give up, or do ToObject on thrownObject if it is a tagged number.)
Your approach seems fine.

What's the difference in behavior between JsGetAndClearExceptionWithMetadata and JsGetAndClearException? Is the former exactly same as latter except for extra metadata info in the returned object?

@liminzhu JsGetAndClearException returns the thrown object from an exception while also clearing the current exception, and exposes no other information. JsGetAndClearExceptionWithMetadata has the same side effect of clearing the current exception, but returns a javascript object which has the thrown object as a property (the exception property) as well as other information: line number, column number, length, line of source code, and script name.

@MSLaguana gotcha. Is there any reason to use the old API when the new one's added? From an API design perspective, how do you feel about using and old API instead and piling new properties on the returned err object?

If you only care about the thrown object, then it's slightly cheaper to invoke the original method, but once this is accepted then I'll be changing node-chakracore to use only the new method since it always wants the additional information.
I would have preferred to re-use the previous method, but that's not possible. The object returned in the original method is the thrown javascript object, which can be any javascript object including a number, so it may not be something with properties (e.g. it may be a number).

@MSLaguana makes sense. Thanks for the explanation.

:shipit:

Added API reference in wiki. Please update them if needed in the future.
https://github.com/Microsoft/ChakraCore/wiki/JsGetAndClearExceptionWithMetadata


After 0.57.8 → 0.57.9, provider registry Locked

Describe the bug
We are using v0.57.5 in our environment and now preparing upgrade to v0.57.9 however run-all plan is failing on some modules with following error:
time=2024-04-26T06:09:46Z level=info msg=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_dev/github-runner-admin] ╷
[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_dev/github-runner-admin] │ Error: Failed to install provider
[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_dev/github-runner-admin] │
[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_dev/github-runner-admin] │ Error while installing snowflake-labs/snowflake v0.89.0: could not query
[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_dev/github-runner-admin] │ provider registry for registry.terraform.io/snowflake-labs/snowflake: 423
[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_dev/github-runner-admin] │ Locked
[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_dev/github-runner-admin] ╵
[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_dev/github-runner-admin]

We are using terragrunt provider cache and with current version we've never seen this issue.
Steps To Reproduce
I don't really have some minimalistic reproducer becuase on simple configuration it works fine on my laptop. This maybe has something to do with different lockfiles in different folders and how dependencies are used (e.g. I see this error on all modules using snowflake provider).
Expected behavior
Should work as before.
Nice to haves

[x] Terminal output
[ ] Screenshots

Versions

Terragrunt version: 0.57.9
OpenTofu/Terraform version: 1.8.2
Environment details (Ubuntu 20.04, Windows 10, etc.):

Update: 0.57.8 is working fine so something is broken in 0.578.9

Hi @ignatenkobrain,
We changed the approach to caching providers in version 0.57.9.
Previously we used terrafrom providers lock -platfrom=xxx_xxx to start caching and then terrafrom init, now we use the same terrafrom init command twice but with different CLI configuration files. The new approach has many advantages, so rollback is not considered.
The error you mentioned
│ Error: Failed to install provider
│
│ Error while installing snowflake-labs/snowflake v0.89.0: could not query
│ provider registry for registry.terraform.io/snowflake-labs/snowflake: 423
│ Locked

is always returned the first time  terraform init is run, which means Terragrunt Provider Cache started caching. so it is ignored and hided from the logs. The second run we use different CLI config where Terragrunt Provider Cache acts as a proxy and does not return a such error.
I'll try to make a minor improvement in the log parsing and the way to pass of the CLI config file. But I can’t say for sure that this will help until I can reproduce this error.

@levkohimins I don't mind some clutter in logs however what should I do to our configuration to avoid this error? I mean, the run-all plan here helps so should I fix / update lockfile or run some commands differently or? Sadly our configuration is not public so I can't share but I am happy to test any patches.

@levkohimins Hope this helps to gather more info:
8_terragrunt run-all.txt

This is happenning only for snowflake provider, all others are completely fine.... which brings me to a point... it uses Pascal-Case (or whatever it is called) in the URL (= Snowflake-Labs), can it be somehow problematic for terragrunt to cache it?

I can't reproduce it locally but easily reproducible in our gh actions

I've tried also with parallelism=1 and it still behaves like that.

Relevant logs
2024-04-27T05:53:24.3993991Z time=2024-04-27T05:53:24Z level=debug msg=Found locals block: evaluating the expressions. prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.4000122Z time=2024-04-27T05:53:24Z level=debug msg=Evaluated 1 locals (remaining 0): common_vars prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.4008994Z time=2024-04-27T05:53:24Z level=debug msg=Found locals block: evaluating the expressions. prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.4017449Z time=2024-04-27T05:53:24Z level=debug msg=Evaluated 1 locals (remaining 2): account_vars prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.4019885Z time=2024-04-27T05:53:24Z level=debug msg=Evaluated 2 locals (remaining 0): account_name, state_config prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.4023675Z time=2024-04-27T05:53:24Z level=debug msg=[Partial] Included config /runner/_work/iac/iac/snowflake/cloud.hcl has strategy shallow merge: merging config in (shallow). prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.4289655Z time=2024-04-27T05:53:24Z level=debug msg=terraform version: 1.8.2 prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.4293494Z time=2024-04-27T05:53:24Z level=debug msg=Reading Terragrunt config file at /runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin/terragrunt.hcl prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.4296590Z time=2024-04-27T05:53:24Z level=debug msg=Found locals block: evaluating the expressions. prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.4317754Z time=2024-04-27T05:53:24Z level=debug msg=Evaluated 1 locals (remaining 0): common_vars prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.4332597Z time=2024-04-27T05:53:24Z level=debug msg=Found locals block: evaluating the expressions. prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.4341270Z time=2024-04-27T05:53:24Z level=debug msg=Evaluated 1 locals (remaining 2): account_vars prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.4344472Z time=2024-04-27T05:53:24Z level=debug msg=Evaluated 2 locals (remaining 0): state_config, account_name prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.4348119Z time=2024-04-27T05:53:24Z level=debug msg=[Partial] Included config /runner/_work/iac/iac/snowflake/cloud.hcl has strategy shallow merge: merging config in (shallow). prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.4352090Z time=2024-04-27T05:53:24Z level=debug msg=Found locals block: evaluating the expressions. prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.4365800Z time=2024-04-27T05:53:24Z level=debug msg=Evaluated 1 locals (remaining 0): common_vars prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.4374505Z time=2024-04-27T05:53:24Z level=debug msg=Found locals block: evaluating the expressions. prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.4406792Z time=2024-04-27T05:53:24Z level=debug msg=Evaluated 1 locals (remaining 2): account_vars prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.4408593Z time=2024-04-27T05:53:24Z level=debug msg=Evaluated 2 locals (remaining 0): account_name, state_config prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.4412807Z time=2024-04-27T05:53:24Z level=debug msg=Included config /runner/_work/iac/iac/snowflake/cloud.hcl has strategy shallow merge: merging config in (shallow) for dependency. prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.4425854Z time=2024-04-27T05:53:24Z level=debug msg=Found locals block: evaluating the expressions. prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.4430552Z time=2024-04-27T05:53:24Z level=debug msg=Evaluated 1 locals (remaining 2): account_vars prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.4433346Z time=2024-04-27T05:53:24Z level=debug msg=Evaluated 2 locals (remaining 0): account_name, state_config prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.4439481Z time=2024-04-27T05:53:24Z level=debug msg=Found locals block: evaluating the expressions. prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.4444479Z time=2024-04-27T05:53:24Z level=debug msg=Evaluated 1 locals (remaining 2): account_vars prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.4446308Z time=2024-04-27T05:53:24Z level=debug msg=Evaluated 2 locals (remaining 0): account_name, state_config prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.4451851Z time=2024-04-27T05:53:24Z level=debug msg=Included config /runner/_work/iac/iac/snowflake/cloud.hcl has strategy shallow merge: merging config in (shallow). prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.4466983Z time=2024-04-27T05:53:24Z level=info msg=Downloading Terraform configurations from git::ssh://git@github.com/gooddata/terraform-snowflake-modules.git?ref=v0.2.4 into /runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin/.terragrunt-cache/5nYGFbkTH1ifyBpoT7oX6Dxsycw/joswRRlSlNjBCU0tFdPnMPkAZrU prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.8179643Z time=2024-04-27T05:53:24Z level=debug msg=Copying files from /runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin into /runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin/.terragrunt-cache/5nYGFbkTH1ifyBpoT7oX6Dxsycw/joswRRlSlNjBCU0tFdPnMPkAZrU/github-runner-admin prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.8185933Z time=2024-04-27T05:53:24Z level=debug msg=Setting working directory to /runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin/.terragrunt-cache/5nYGFbkTH1ifyBpoT7oX6Dxsycw/joswRRlSlNjBCU0tFdPnMPkAZrU/github-runner-admin prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:53:24.8190028Z time=2024-04-27T05:53:24Z level=info msg=Caching terraform providers for /runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin/.terragrunt-cache/5nYGFbkTH1ifyBpoT7oX6Dxsycw/joswRRlSlNjBCU0tFdPnMPkAZrU/github-runner-admin
2024-04-27T05:53:25.2160435Z time=2024-04-27T05:53:25Z level=debug msg=Acquiring lock file /home/runner/.cache/terragrunt/archives/registry.terraform.io-snowflake-labs-snowflake-0.89.0-linux_amd64.lock
2024-04-27T05:53:25.2162491Z time=2024-04-27T05:53:25Z level=debug msg=Fetching provider snowflake-labs/snowflake v0.89.0
2024-04-27T05:53:25.2205676Z time=2024-04-27T05:53:25Z level=error msg=Module /runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin has finished with an error: 1 error occurred:
2024-04-27T05:53:25.2207607Z 	* [/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin/.terragrunt-cache/5nYGFbkTH1ifyBpoT7oX6Dxsycw/joswRRlSlNjBCU0tFdPnMPkAZrU/github-runner-admin] exit status 1
2024-04-27T05:53:25.2208865Z
2024-04-27T05:53:25.2209364Z  prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]

2024-04-27T05:59:57.2760865Z time=2024-04-27T05:53:24Z level=debug msg=Generated file /runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin/.terragrunt-cache/5nYGFbkTH1ifyBpoT7oX6Dxsycw/joswRRlSlNjBCU0tFdPnMPkAZrU/github-runner-admin/_provider.tf. prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:59:57.2762370Z time=2024-04-27T05:53:24Z level=debug msg=Generated file /runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin/.terragrunt-cache/5nYGFbkTH1ifyBpoT7oX6Dxsycw/joswRRlSlNjBCU0tFdPnMPkAZrU/github-runner-admin/_backend.tf. prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:59:57.2763187Z time=2024-04-27T05:53:24Z level=debug msg=Running command: /home/runner/.local/bin/terraform init prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:59:57.2763629Z [/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin] ╷
2024-04-27T05:59:57.2764290Z [/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin] │ Error: Failed to install provider
2024-04-27T05:59:57.2764696Z [/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin] │
2024-04-27T05:59:57.2765429Z [/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin] │ Error while installing snowflake-labs/snowflake v0.89.0: could not query
2024-04-27T05:59:57.2766148Z [/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin] │ provider registry for registry.terraform.io/snowflake-labs/snowflake: 423
2024-04-27T05:59:57.2766581Z [/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin] │ Locked
2024-04-27T05:59:57.2767032Z [/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin] ╵
2024-04-27T05:59:57.2767409Z [/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:59:57.2768928Z time=2024-04-27T05:53:25Z level=error msg=terraform invocation failed in /runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin/.terragrunt-cache/5nYGFbkTH1ifyBpoT7oX6Dxsycw/joswRRlSlNjBCU0tFdPnMPkAZrU/github-runner-admin prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]
2024-04-27T05:59:57.2770905Z time=2024-04-27T05:53:25Z level=debug msg=Copying lock file from /runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin/.terragrunt-cache/5nYGFbkTH1ifyBpoT7oX6Dxsycw/joswRRlSlNjBCU0tFdPnMPkAZrU/github-runner-admin/.terraform.lock.hcl to /runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin prefix=[/runner/_work/iac/iac/snowflake/hqltkfn-aws_eu_west_1_prod/github-runner-admin]

I am actually able to reproduce it locally too now. It is due to the --terragrunt-include-module-prefix

no-prefix.txt
with-prefix.txt

-               cmdStderr := io.MultiWriter(withPrefix(errWriter, prefix), &stderrBuf)
+               cmdStderr := io.MultiWriter(withPrefix(errWriter, ""), &stderrBuf)

in the shell/run_shell_cmd.go fixes the issue.

https://github.com/gruntwork-io/terragrunt/pull/3105 fixes the issue.

Resolved in v0.57.13 release.


Feat(RingTheory/Flat): add localization of flat module is flat

add that localization of a flat module is flat.
Co-authored-by: Florent Schaffhauser and Andrew Yang
This contribution was created as part of the AIM workshop "Formalizing algebraic geometry" in
June 2024.

Can you provide a version with IsLocalizedModule? Should be straightforward.

Taking into account the comment about IsLocalizedModule LGTM, thanks!
bors d+

I've added a version for IsLocalizedModule. Could you check the naming of the theorems, and comment on which universes the variables should live in (line 153). Thanks

Thanks!
bors merge


Add syntax highlighting to readme

Preview: https://github.com/HappyFacade/CoreLib/blob/patch-1/README.md

looks awesome, thanks!

looks awesome, thanks!


Feature/tsp

Pull Request
Checklist

[X ] Have you read Digital Catapult's Code of Conduct?
[X ] I have performed a self-review of my own code.
[ X] I have commented my code, particularly in hard-to-understand areas.
[ X] I have made corresponding changes to the documentation.
[ X] My changes generate no new warnings.
[ X] I have added tests that prove my fix is effective or that my feature works.
[ X] New and existing unit tests pass locally with my changes.

PR Type
Please delete options that are irrelevant.

[ X] Bug Fix
[X] Feature
[X ] Documentation Update
[ ] Code style update (formatting, local variables)
[ ] Breaking Change (fix or feature that would cause existing functionality to change)

Linked tickets
N/A- no linked tickets
High level description
Addition of Travelling Salesman Problem (TSP) code, Git Actions for Unit testing, and README updates.
Detailed description

TSP Jupyter Notebook TSP_final added
Helper functions module added with Unit Test cases.
Unit testing achieved by adding unit_test.yaml to new workflow folder.  This triggers running the Unit Test cases
README updated.

Describe alternatives you've considered
Other Continuous Integration such as TRAVIS was considered.  Senior developers explained that Digital Catapult use Git Actions as standard, and this has sufficient functionality for the testing.
Operational impact
n/a - no impact
Additional context
This work is to support a paper on the TSP.  The user will need to install the ORCA SDK.  That is outside the scope of this pull request.

Merged / squashed and deleted branch


Compaction

Description
Adds new feature #98 . :raised_hands: Compaction of small files is coming!
Type of change
In this PR, we present a new feature: compaction of small files.
These changes include a new command to produce the compaction:
val qbeastTable = QbeastTable.forPath(spark, "/tmp/qbeast_table")
qbeastTable.compact()

Under the hood, Qbeast will find the files larger than spark.qbeast.compact.minFileSize and small than spark.qbeast.compact.maxFileSize and compact them into single files within cubeSize number of records.
Checklist:
Here is the list of things you should do before submitting this pull request:

[x] WIP
[x] New feature / bug fix has been committed following the Contribution guide.
[x] Add comments to the code (make it easier for the community!).
[ ] Change the documentation.
[ ] Add tests.
[x] Your branch is updated to the main branch (dependent changes have been merged).

How Has This Been Tested? (Optional)
Still needs to be tested! I will keep updates on this Pull Request.
Test Configuration:

Spark Version:
Hadoop Version:
Cluster or local?

I put you both @Jiaweihu08 and @polsm91 as reviewers to give me feedback if you can :) If you need an explanation on something, please let me know.

Changes explained:

IndexedTable would have a .compact() method that would follow the same pipeline as the write: Compact data (group info into "bins" for each cube), write data, and commit.
DataWriter would also have a .compact() method that would be in charge of writing the data into files and outputting the necessary file actions (Add the compacted files and remove the small ones)
A case class Compactor is created. Since the process is more parallelizable and simpler than the BlockWriter, I added a new process to be in charge of writing the parquet file and adding the proper tags.
MetadataManager would commit the information to the Log.


SCIM2/me endpoint ignores primary attribute in descriptive email format

Describe the issue:
The emails marked as primary in the "emails" field of scim2/me post request are not recognised as primary emails. The following actions are allowed due to this issue

multiple emails allowed to be marked as primary in the emails list
users created with no primary email if no non-descriptive format email is included in the emails list

How to reproduce:
Create a user by sending a POST request to scim/me endpoint with descriptive emails that are marked as primary.
eg :
"curl --location --request POST 'https://localhost:9443/t/iam.com/scim2/Me'
--header 'accept: application/scim+json'
--header 'authorization: Basic YWRtaW5AaWFtLmNvbTpQYXNzQDEyMw=='
--header 'Content-Type: application/scim+json'
--data-raw '{
""userName"": ""kim1"",
""password"": ""abc123"",
""emails"": [
{
""type"": ""home"",
""value""<EMAIL_ADDRESS>""primary"": true
},
{
""type"": ""work"",
""value""<EMAIL_ADDRESS>}
]
}'"
Expected behavior:
Emails marked as primary are recognised as primary emails. Multiple primary emails are not allowed.
Environment information

Product Version: IS 6.0.0 M1
OS: Windows 2019
Database: PostgreSQL
Userstore: JDBC

Other notes
non-descriptive email format example:
{
...,
emails: [
<EMAIL_ADDRESS>]
}
descriptive email format example:
{
...,
emails: [
{
"type": "work",
"value": "kim2wso2.com",
"primary": true
}
]
}

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Use tooling to ease the backport of PR to branches

Is your enhancement related to a problem? Please describe
following some reports of developers, it would be handy if the backport of the PR to other branches could be achieved automatically
Describe the solution you'd like
Axel suggested https://github.com/marketplace/actions/backport-merged-pull-requests-to-selected-branches
Needs to check if app (rather than Github action exists)
Looks like mergify app also provides it:
https://docs.mergify.com/commands/backport/
(more handy than adding labels) and we could use it for other tasks (automatic merge, request reviews, rebase PR, etc)
Describe alternatives you've considered
No response
Additional context
No response

mergify has been setup


Bug: Background color only applied to the first cell after dragging table cells

This pull request is related to #5255

update the handleCellBackgroundColor function to apply the background color to each selected cell

I made the base branch wrong. I will send the new PR. Thank you :)


Update webpack

Update webpack to version 4. Allow debugging with the inline source map of build:dev.
Resolves #71

Nice! Looks good to me 💃


[azeventhub] Batched sending

Event Hubs, much like Service Bus, supports sending messages in a batch. This should be able to leverage the same code, as it uses the same encoding.

Implemented in #18694


Slow down of the performance_indices due to xesmf>=0.8 version

Although the tests are passed on CI, I am noticing an unclear slowdown of the code for the performance indices on Wilma. Some of tests are taking ages to conclude. This might related to the issue with #88, but it is impossible to pinpoint where the problem is coming from

After a lot of digging, found that the problem is due to the new release of xesmf. This is why we are having this strange behaviour only in the performance indices. They made some update in dask https://xesmf.readthedocs.io/en/stable/changes.html#id3 which probably affect some of our internal operation


Support multiple sessions at once

distant-lua has no problem managing multiple sessions. The majority of distant.nvim could also function against multiple sessions, but for ease of use maintains a single active session that is extracted from distant.state.session.
Easiest option would be to have state represent an active session, maintain a list of sessions within state that are mapped by id, and provide a mechanism to switch between sessions when desired. The switch would then affect all fn calls, although maybe we also want to provide the option for fn calls to take an optional session as an argument?
The session id should be embedded within each buffer so we don't have to figure out which session is applicable at that point. This also means that distant.nav.actions would extract the session from the buffer before acting upon it.

Supported in upcoming v0.3 branch.


Moving documentation images to specific repository

As we are building the documentation and adding images, the repository size increases. If we rename/move these images, they still stay in the repository history. Since we want to keep the repos as small as possible, I suggest moving the images to another specific repository: https://github.com/ivadomed/doc-figures
We adopted the same strategy for SCT.
If everyone agrees with this approach, we need to:

Document this new practice in our internal documentation
Give credentials to dev team for the new repos (@alexfoias can you please do that)
Move documentation images to this new repos (@alexfoias)
For ongoing PR, we need to make this change before the PR and make sure to do a "squash and merge" so the images don't end up in the repos history. Example https://github.com/ivadomed/ivadomed/pull/502/commits/bb0f5477cec0ecd95f904fd06bfaaf14dc3234bd

Thumbs up!

I granted permissions to team.
I'm working on moving the images, I'll open a PR soon.

Already done in https://github.com/ivadomed/doc-figures/pull/1 . This issue can be closed.

Already done in https://github.com/ivadomed/doc-figures/pull/1 . This issue can be closed.


Upgrade to arrow 13

Related to https://github.com/apache/arrow-rs/issues/1623
This PR is a WIP while I work on releasing arrow 13.0.0 -- and making sure datafusion works with arrow 13.0.0 is part of my pre-release testing 👍
Will turn this into a proper PR once arrow 13.0.0 is released (sometime next week)

arrow 13 has been released to crates.io and I have updated this PR's code, so it is now ready for review
cc @WinkerDu

There is a minor clippy failure

Thanks @alamb
It's cool to go after fixing the minor clippy failure

It's cool to go after fixing the minor clippy failure

🤦  sorry about that -- fixed and will merge when green


Fixes #123

Change order of width>height in component classes

We decided to change the signature to (x, y, w, h, ...) so this change is not needed at this time.


indent-blankline not calling setup

Plugin affected: indent-blankline
Nixpkgs channel: unstable
Description
I tried using the indent-blankline plugin but it did not work.
Looking at the file
https://github.com/nix-community/nixvim/blob/main/plugins/utils/indent-blankline.nix
I see that require("ibl").setup() is not called, see
https://github.com/lukas-reineke/indent-blankline.nvim

You can run it manually:
  config = {
    plugins.indent-blankline =
      {
        enable = true;
      };
    options = {
      list = true;
      listchars = "space:⋅";
    };
    extraConfigLua = ''
      require("ibl").setup()
    '';
  };

With that config I'm getting the default behavior of ident-blankline version 3.
It seems that when the ident-blankline plugin was introduced into nixvim, version 3 of the plugin was still not released, that's why require("ibl").setup() is not called.
Here is the migration guide, the options in nixvim should probably be updated.

We have planned to update to the latest version: https://github.com/nix-community/nixvim/pull/650

Should be fixed as #650 has been merged.
Please, re-open this issue if some problems remain.

Thanks! :)


{arcappliance} HTML tags aren't allowed in published reference content

Describe the bug
Problem to solve:
HTML tags in source code are causing build warnings in MicrosoftDocs/azure-docs-cli. More importantly, customer-facing reference docs are not instantiating properly -- parameter values formatted with `<>` are missing. Here's an example:

Requested solution:
These values should be escaped with a backtick. Here's an example from az webpubsub.

Related GitHub issues:
This is the same issue as these GitHub issues.
List of HTML tag instances that need update:

File name
Build error

latest/docs-ref-autogen/arcappliance/create.yml
HTML tag 'resourceName' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/create.yml
HTML tag 'resourceName' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/create.yml
HTML tag 'resourceName' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/createconfig.yml
HTML tag 'BridgeName' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/createconfig.yml
HTML tag 'URL' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/createconfig.yml
HTML tag 'PORT' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/createconfig.yml
HTML tag 'URL' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/createconfig.yml
HTML tag 'PORT' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/createconfig.yml
HTML tag 'URL' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/createconfig.yml
HTML tag 'PORT' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/createconfig.yml
HTML tag 'URL' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/createconfig.yml
HTML tag 'PORT' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/createconfig.yml
HTML tag 'URL' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/createconfig.yml
HTML tag 'PORT' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/createconfig.yml
HTML tag 'URL' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/createconfig.yml
HTML tag 'PORT' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/delete.yml
HTML tag 'resourceName' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/delete.yml
HTML tag 'BridgeName' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/delete.yml
HTML tag 'resourceName' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/delete.yml
HTML tag 'resourceName' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/deploy.yml
HTML tag 'resourceName' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/deploy.yml
HTML tag 'BridgeName' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/deploy.yml
HTML tag 'resourceName' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/deploy.yml
HTML tag 'resourceName' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/logs.yml
HTML tag 'BridgeName' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/prepare.yml
HTML tag 'resourceName' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/prepare.yml
HTML tag 'BridgeName' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/prepare.yml
HTML tag 'resourceName' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/prepare.yml
HTML tag 'resourceName' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/run.yml
HTML tag 'BridgeName' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/troubleshoot/command.yml
HTML tag 'BridgeName' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/update-infracredentials.yml
HTML tag 'BridgeName' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/validate.yml
HTML tag 'resourceName' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/validate.yml
HTML tag 'BridgeName' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/validate.yml
HTML tag 'resourceName' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/arcappliance/validate.yml
HTML tag 'resourceName' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

Related command
az arcappliance
Errors
n/a
Issue script & Debug output
n/a
Expected behavior
n/a
Environment Summary
This GitHub issue was created at the time of Azure CLI 2.62.0
Additional context
No response

Thank you for opening this issue, we will look into it.


Extra newlines when importing from HTML

Description
If I import the following HTML content, the resulting Obsidian document has extra newlines between every item.
Tested on a MacBook Pro with MacOS 14.3.1 (23D60).
HTML
<!DOCTYPE html>

  <title>Test</title>

Scintillating: Animated, brilliant, or highly skilled.

Acrimonious: Bitter and sharp in language or tone; rancorous.

Specious: superficially plausible, but actually wrong.

Demur: to voice opposition.

Anathema: in common usage, is something or someone detested or shunned. In its other main usage, it is a formal excommunication.

Reticent: not revealing one's thoughts or feelings readily.

Obsidian

Expected
No extra newlines in between HTML elements.

@joeriddles The Obsidian display is correct. Adjacent HTML `  blocks are typically displayed with extra space in between them. By default, browsers add some margin around  elements to visually separate paragraphs. This can usually be seen as a vertical space above and below each paragraph. Here's how e.g. a Chrome browser displays your text:


class NeuSCustomModelConfig and SDFCustomFieldConfig which import from sdfstudio to SelfOcc were not finded

When I ran train code or eval code, it needed to 'import model'. Then, two classes named NeuSCustomModelConfig and SDFCustomFieldConfig were not finded. I also encountered a problem "ImportError: cannot import name 'jacrev' from 'functorch' (unknown location)". Could you kindly help me with that? Many thanks to your code sharing~

For the second question, functorch 0.2.1 is required.

Can I ask how to generate pkl files for other datasets? Like v1.0-mini :)

About the first question, I think your installation of sdfstudio was not completed or you installed the official sdfstudio repo.
Also, I will release the code for generating the pkl files today.

Thank you


closeOnSelect not working

Even on your demo here: https://vue-treeselect.js.org/#more-features the close-on-select option does nothing - the menu stays open after selecting an option.
I've managed to implement myself using:
<treeselect ref="searchCat" multiple @select="$refs.searchCat[0].closeMenu()" ...

I use :closeOnSelect="true" in mode :async="true", but not working. I think problem is :async="true".


aliasByNode() -> allowing colon(:) and hash(#) in node names

this fixes https://github.com/grafana/grafana/issues/1524
(it also adds the # as I'm using it in my metrics language)

Thanks @zeph!

u r welcome @brutasse  :)


String Palindrome

Wrote the code to check if the string is palindrome or not.

Hey @riteshsoni123 !
Excellent.
You can follow me and star this repository for further updates.
Have fun 🙌🏻


HUGE lesson update!!!!!

[x] changed subtitle from... uh... I forgot

Brilliant pull request. Manifest programming!


MAT draft only displays aftermath cards

The tool only displays the few aftermath cards and not cards from the base set.

Use version 3.09