in FE Price-Filter is not applied (in BE seems all fine)

Hey,
in BE all the documented options are available.
But in FE it seems, the module is ignored. My Price Navigation shows like without your module:
it shows "0-10 €" and "10 and above".
My Products have a Pricerange like this:
1,20 €
1,75 €
2,30 €
3,53 €
...
10,33 €
What i do so far:
i clean megento caches and rebuild indexes
here my layered navigation block in admin > system > config > catalog:
show Product count: yes
price nav. step calc: manual
default price nav step: 1
maximum number of price intervals: 40
Price Ranges: -2;2-4;4-20
Substract 0.01: no
logs are enabled, all fine, no errors
Magento CE <IP_ADDRESS>
no other Modules
Article/Category Flat Data activated (deactivated same behavior)
How can i approach a Price Navigation like
0-2 €
2-4 €
4-20 €
Thank you!

hello
FE / BE = EE / CE?
but who's who?
I don't have any EE licence to test my module with
can only help with CE if it's the version that does not work for you

module works fine on CE 1.9, can't test on EE


fix: Select field breaks forms in safari

Fixes #5111
Summary
When a Select is present on a form rendered on Safari (both iOS and Mac tested), every change in ANY input (even others than the Select) causes the screen to focus on the select input and loses focus on the changing input.
This PR aims to fix #5111 . There's a minimal reproduction of the problem this PR solves in this issue.

Good catch! This should also be applied to Input component.

Any chance that this can be merged, please? I'm having to use an old version of native-base because of this bug and this PR fixes it.


Bug 2002420: making sure stage labels are added to running pods only

Skip adding stage labels to pods that are not in running state

This fixed the test case mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=2002420 for me. ACK

@JaydipGabani if you have IBM ROKS clusters around, would be good to test the same TC on your end in case there is different PVC behavior there. Thinking about the scenario where a completed app Pod and running stage Pod both reference the same PVC.

Re-tested after recent change set, still works 👍


Maybe TextureType should be optional in Texture:newView

It could default to the parent texture's type if the first argument is a number?
Also, ugh, it would be nice to put both counts at the end so you can just say :newView(layer, mip) but that's a breaking change.

Added a new variant for creating single slice/level views, with the 2D type implied.  I think this should cover most of the annoying cases.


ElmahIoTarget - Changed to AsyncTaskTarget with support for CreateBulk

See also: https://github.com/NLog/NLog/wiki/How-to-write-a-custom-async-target

This is absolutely AWESOME, @snakefoot! Bulk and async was on the TODO list for sure. Thank you very much.

@snakefoot do I need to do anything else to trigger NLog to log now? When running the Elmah.Io.NLog.Console sample, WriteAsyncTask is never invoked.

Have updated Elmah.Io.NLog.Console-project to use NLog 4.6.5

Ahh, of course 👍 Do I need to do anything to make sure that all messages are stored before exiting the process. Serilog has a Log.CloseAndFlush(); that must be called before exit and wondering if there is a similar construct in NLog?

NLog has automatic flush on shutdown, but it is not reliable for network-based-targets, but is more for console and file-targets.
There are the following methods in NLog:
NLog.LogManager.Flush();  // Flushes the current messages without closing down
NLog.LogManager.Shutdown();  // Flushes and closes all targets


Corrected annotation ex signin-url to auth-url

Example was wrong, had to dig through code to find the correct annotation.

This change is

/lgtm

@olvesh thanks!

Coverage decreased (-0.05%) to 46.901% when pulling 4e94069bb9b7e6484a287aca1f228aef5117efcd on olvesh:master into 37abed3f8490dc5c57010b4d40045bf09acf48ae on kubernetes:master.


refactor(web): image endpoints

Add image http endpoints
Remove image grpc endpoints

Codecov Report
Patch coverage: 0.95% and project coverage change: -0.14 :warning:

Comparison is base (832cb39) 14.05% compared to head (c721016) 13.92%.

: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             @@
##           develop     #512      +/-   ##
===========================================
- Coverage    14.05%   13.92%   -0.14%
===========================================
  Files           58       61       +3
  Lines         6195     6257      +62
===========================================
  Hits           871      871
- Misses        5296     5358      +62
  Partials        28       28

Impacted Files
Coverage Δ

golang/api/v1/deploy.go
80.61% <ø> (ø)

golang/internal/label/label.go
0.00% <0.00%> (ø)

golang/pkg/cli/cli.go
0.00% <0.00%> (ø)

golang/pkg/cli/config_file.go
0.00% <0.00%> (ø)

golang/pkg/cli/container_defaults.go
0.00% <0.00%> (ø)

golang/pkg/cli/runner.go
0.00% <0.00%> (ø)

golang/pkg/dagent/utils/docker.go
8.71% <0.00%> (-0.15%)
:arrow_down:

golang/pkg/dagent/utils/dockerhelper.go
0.00% <0.00%> (ø)

golang/pkg/dagent/utils/init_container.go
0.00% <0.00%> (ø)

golang/pkg/dagent/utils/volume.go
0.00% <0.00%> (ø)

... and 2 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Did you checked the Swagger Objects?

Added missing labels, next time please add them.


[Snyk] Upgrade org.slf4j:slf4j-log4j12 from 1.5.0 to 1.7.36

This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade org.slf4j:slf4j-log4j12 from 1.5.0 to 1.7.36.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 56 versions ahead of your current version.

The recommended version was released 2 years ago, on 2022-02-08.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs
Note: This is a default PR template raised by Snyk. Find out more about how you can customise Snyk PRs in our documentation.

🎉 Snyk hasn't found any issues so far.
✅ security/snyk check is completed. No issues were found. (View Details)
✅ license/snyk check is completed. No issues were found. (View Details)


1.6 release?

I've been using head for a few weeks now and have not run into anymore bugs. I think we are good to go.

Do the more recent bug fixes have release notes?

Fixes I've been involved in are all documented :-)

Great.  What about the other fixes?

Done


Added drop-out-of-header logo styling

Added CSS such that the logo "hangs" out of the menu bar.
Closes #45
Closes #9

I think it needs just a little more (so a bit more padding at the top of the page content

Maybe we should now also add drop shadow to the menu bar

By the way, does clicking the logo do anything now? Maybe it would be fun to add some javascript to let the logo spin 360 degrees or something (does not need to be in this PR obviously)

By the way, does clicking the logo do anything now? Maybe it would be fun to add some javascript to let the logo spin 360 degrees or something (does not need to be in this PR obviously)

Nice idea!


feat: fix repositories table responsiveness bug

What type of PR is this? (check all applicable)

[ ] 🍕 Feature
[x] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Description

Related Tickets & Documents

Fixes: #724

Mobile & Desktop Screenshots/Recordings

Added tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[ ] 📕 storybook
[x] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

@payn33 will you post before and after screenshots so we can see what the applied changes look like

Thanks for a great PR, the wrapping extra div class should be used on the parent, that should make this good for merging! 👍

That would be the table parent right? because adding the wrapper to the main div would include the table header in the horizontal scroll  @0-vortex

Thanks for a great PR, the wrapping extra div class should be used on the parent, that should make this good for merging! 👍

That would be the table parent right? because adding the wrapper to the main div would include the table header in the horizontal scroll @0-vortex

If the new wrapper limits only lg sizes, we have just moved the problem from "looking ugly on small screen" to "looking ugly on big screens". If the parent spans to full width, the child component cannot be a fixed width if that makes sense. Removing the child component or adjusting the w-full parent, the idea is to not break visual cohesion solving a bug (fixing a bug with a new bug) ❤

IMHO, you should catch this breakpoint 1020px and 1285px and slice the columns, what column to be shown, and what column would be hidden.
something like that ( just pseudo code )
state = { windowWith: window.innerWidth }
handleResize = (event) => {
    this.setState({ windowWith: window.innerWidth })
}

componentDidMount() {
    window.addEventListener(‘resize’, this.handleResize)
}

Good PR.

IMHO, you should catch this breakpoint 1020px and 1285px and slice the columns, what column to be shown, and what column would be hidden.
something like that ( just pseudo code )
state = { windowWith: window.innerWidth }

handleResize = (event) => {

    this.setState({ windowWith: window.innerWidth })

}

componentDidMount() {

    window.addEventListener(‘resize’, this.handleResize)

}

Good PR.  👍

That is not the expected or intended behaviour since we are using tailwind: https://tailwindcss.com/docs/responsive-design
Please refrain from suggesting anti-patterns!!!

IMHO, you should catch this breakpoint 1020px and 1285px and slice the columns, what column to be shown, and what column would be hidden.
something like that ( just pseudo code )
state = { windowWith: window.innerWidth }

handleResize = (event) => {

    this.setState({ windowWith: window.innerWidth })

}

componentDidMount() {

    window.addEventListener(‘resize’, this.handleResize)

}

Good PR.  👍

That is not the expected or intended behaviour since we are using tailwind: https://tailwindcss.com/docs/responsive-design
Please refrain from suggesting anti-patterns!!!

With this approach, we have something to implement

Tailwind, is just for CSS, to make more easy to work with CSS and avoid some diff approaches to about CSS. But in IMO in this PR he must manage the columns.  To hide or show... But if you are not ok with this approach, please forget this intervention.
But for a moment it is not possible, I understand.

Thanks for a great PR, the wrapping extra div class should be used on the parent, that should make this good for merging! 👍

That would be the table parent right? because adding the wrapper to the main div would include the table header in the horizontal scroll @0-vortex

If the new wrapper limits only lg sizes, we have just moved the problem from "looking ugly on small screen" to "looking ugly on big screens". If the parent spans to full width, the child component cannot be a fixed width if that makes sense. Removing the child component or adjusting the w-full parent, the idea is to not break visual cohesion solving a bug (fixing a bug with a new bug) ❤

Hi @0-vortex this is the current behaviour

In the proposed fix the child component is only a fixed width on lg  sizes which causes an overflow due to the parent element having the overflow-x-auto property at the min responsive width 1150px  excluding the table header from the horizontal scroll
https://user-images.githubusercontent.com/66219025/212764413-530c306b-bbf7-481e-86c5-7ad527c2c61e.mp4
Removing the child component and adding  the overflow-x-auto property to the w-full parent  includes the table header, is this what you mean by not breaking visual cohesion ?
https://user-images.githubusercontent.com/66219025/212765254-b543140a-9aa1-4c81-91ad-268f29f83324.mp4


cpython: cleanup, refactoring, unpin openssl-legacy, use our own libmpdecimal

Description of changes
Somewhat overdue maintenance work on CPython.
There should be no substantial changes to the overall API.
See the individual commits for a summary of what was done.

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Thank you for cleaning up the expression.

The lib tests complete for me locally.


fogs, absterging

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 100
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[a,f]

/trunk merge


[MRG] check section lengths match L-parameter

Closes #330 by adding a test to check sec.L matches the difference in sec.z3d(1) - sec.z3d(0).
I added a few lines to Cell based on the NEURON docs for pt3dadd:
h.pt3dconst(0, sec=sec)
...
h.define_shape()

Codecov Report

Merging #373 (ad1a73c) into master (9b95ae8) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #373   +/-   ##
=======================================
  Coverage   89.81%   89.81%
=======================================
  Files          15       15
  Lines        2895     2897    +2
=======================================
+ Hits         2600     2602    +2
  Misses        295      295

Impacted Files
Coverage Δ

hnn_core/cell.py
97.38% <100.00%> (+0.02%)
:arrow_up:

Continue to review full report at Codecov.

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

Thanks @cjayb !


ADSError: timeout elapsed (1861) @ plc.del_device_notification

Dear all,
I get the following error when calling plc.del_device_notification(*handles).
Exception in thread Thread-1: Traceback (most recent call last):   File "C:\ProgramData\Anaconda3\envs\CLM_test\lib\threading.py", line 916, in _bootstrap_inner     self.run()   File "C:\ProgramData\Anaconda3\envs\CLM_test\lib\threading.py", line 864, in run     self._target(*self._args, **self._kwargs)   File "c:/temp/Workspaces/clm_demo_application/communication_with_Siemens_controller/DAQ_application/DAQ_GUI/clm_tc_daq_gui.py", line 210, in producer     self.plc.del_device_notification(*handles)   File "C:\ProgramData\Anaconda3\envs\CLM_test\lib\site-packages\pyads\ads.py", line 1179, in del_device_notification     self._port, self._adr, notification_handle, user_handle   File "C:\ProgramData\Anaconda3\envs\CLM_test\lib\site-packages\pyads\pyads_ex.py", line 1189, in adsSyncDelDeviceNotificationReqEx     raise ADSError(err_code) pyads.pyads_ex.ADSError: ADSError: timeout elapsed (1861).
In the following you can find the code section, where this Timeout is thrown.
<< beginning of code section
   def producer(self):
        self.PLC_LOC = 'GVL_DataOutput'
        self.STRUCTURE_NAME = 'strTimeSeries_OS10_5_Output'
        self.PY_DUT_TYPE = PY_DUT_TC_CLM40_munich_10_OS
        self.PYADS_STRUCT_NAME = self.PLC_LOC + '.' + self.STRUCTURE_NAME
        self.PYADS_STRUCT_SIZE_INT = pyads.size_of_structure(self.PY_DUT_TYPE)
        self.PYADS_STRUCT_SIZE = pyads.ads.c_ubyte*self.PYADS_STRUCT_SIZE_INT

    @self.plc.notification(self.PYADS_STRUCT_SIZE)
    def callback(handle, name, timestamp, value):
        print(
            '{1}: received new notification for variable "{0}"'
            .format(name, timestamp)
        )
        self.q.put(pyads.dict_from_bytes(value, self.PY_DUT_TYPE))

    notAttrib = pyads.NotificationAttrib(self.PYADS_STRUCT_SIZE_INT)
    handles = self.plc.add_device_notification(self.PYADS_STRUCT_NAME, notAttrib, callback)

    while True:
        if self.acquire.is_set():
            time.sleep(0.0001)
        else:
            if self.notification_delete == 0:
                print("delete handles: ", self.notification_delete)
                self.plc.del_device_notification(*handles)
                time.sleep(10)
                self.notification_delete = self.notification_delete + 1
            else:
                break

>> ending of code section
After this Timeout the ADS communication still works fine. I use "Write by name" method subsequently and the Value is changed in Twincat.
System description:

Windows 10 PC
TwinCAT 3
Pyads 3.3.4
tested with Python 3.6.13 and 3.8.4

I would appreciate your help! Is this an API issue or is it my code which causes the problem? Do you have any suggestion for solving this issue?
Is it possible that this is a multi threading issue? When I debug my code, this Timeout is not raised. Therefore, it is hard to understand the issue.
Thank you very much!

Hi, I've not had a chance to fully review and test this. But I suspect this is a multthreading issue, especially as you can't replicate during debug. In my experience when using another thread I always create a plc connection per thread. So that any interactions to the PLC from the main thread do not interfere with the other thread. There may be a case where ADS is trying to delete the notification and do something else.
You also get timeout issues when trying to make an an ads call from within a callback function but I think that is a separate issue.

Thank you very much for your answer the hint to create a seperate plc connection per thread.
I do agree with your pereception that this is a multi threading issue, because I was able solve the problem by a different order when stopping the various threads. But I think a more robust way is to use the separate plc connections. Thanks!

Thank you very much for your answer and the hint to create a seperate plc connection per thread.
I do agree with your pereception that this is a multi threading issue, because I was able solve the problem by a different order when stopping the various threads. But I think a more robust way is to use the separate plc connections. Thanks!


first go at preprocessors

First go is just using shell commands, e.g.
package.json:
{
  "oc": {
    "preprocessors": [
      {
        "name": "babel",
        "command": "babel"
      }
    ]
  }
}

Downside is that it requires the babel cli to be installed, and it doesn't support commands that don't stream. The order matters.
coffeescript can be done using the following:
{
  "oc": {
    "files": {
        "data": "server.coffee"
    },
    "preprocessors": [
      {
        "name": "coffee-script",
        "command": "coffee",
        "args": ["-sc"]
      }
    ]
  }
}

It raises the question of whether we

continue spawning the cli (yuck)
push the responsibility onto the component to run arbitrary code as a preprocessor (e.g. babel.compile(...))
explicitly support common things like babel, coffeescript, browserify inside the oc cli

Very cool. I also really need this :dancer:

Maybe what we really need to do is preprocess the lot using something like webpack. This would let us just plugin webpack plugins to do the transforms and should also allow arbitrary requires rather than only allowing requiring of json files

The original plan for this was to have something like the prepublish step on npm, so, something very simple, equivalent of having any grunt watcher doing stuff, but somehow hooked to the oc dev watcher.
So, @andyroyle, I like the idea of OC being un-opinionated but having optional functionalities to make your life easier.

This is the plan but keeping it simple enough to be something easy to maintain :+1:
So, you can run a command :+1: , you can specify the order :+1: , but nothing more than that I would say. And if the command fails it's up to you to fix it (for example taking care of installing globally babel before running it).
I still want to allow the components' creators to be able to do this especially for advanced functionalities. So, running a grunt watcher or anything else :+1:
That's what I wanted to do in the first place...problem is to keep the cli's dependency tree small. I wanted to integrate babel, for example, then after looking at its dependency tree I changed my mind :( I already have built-in javascript and css bundling and minification and I am kind of regretting it because the cli has too many dependencies :cry:

@stevejhiggs the idea of not allowing require for js on the server-side part of components is actually for simplicity. Allowing it opens so many scenarios to handle in terms of complexity, security and robustness that we just don't have the resources to handle it (yet?).
Also, enforces simplicity and modularity in the OC way:

components nesting in case it makes sense from a domain point of view
moving to a separate service server-side complexity and keeping your server.js just a proxy - which is actually something that shouldn't heavily load (computationally speaking) the registry's runtimes and something where node.js is actually quite decent in terms of scalability.

In case you want to modularise your code just for the sake of readability, testability etc, I would say that as soon as it stays simple with a preprocessor you should be able to achieve it anyway. Something like:
// standard node.js
// a.js
module.exports = ...
// server.js
var a = require('./a');
...

// Alternative - client-side kind of way
// a.js
...
// b.js
...
// preprocessor
cat a.js b.js > server.js

What do you think?

taken a different tactic with grunt-oc


xcode 10 & Swift 4.2

Still to do:

[x] update tests to run in all the Swift 4.x variants

Xcode 10 is now available on CircleCI.

I believe this is good to go - just waiting on CircleCI to update to the Xcode 10 GM.

CircleCI now has Xcode 10.0 GM on it. @Imperiopolis @KingOfBrian should be good for final review and merge.

Can you please release  a new version with this merge? Thank you

This has now been released in version 5.3. If you run into any issues with Xcode 9 or 10, please file a bug!


record_summaries_every_n_global_steps() should not execute code unless global_step % n == 0

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Ubuntu 18.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
No
TensorFlow installed from (source or binary):
Source
TensorFlow version (use command below):
b'v1.12.0-5845-g764109a352' 1.12.0
Python version:
3.6.7
Bazel version (if compiling from source):
Invocation ID: 42251854-036f-415c-8a52-76aac8520ea0
Build label: 0.21.0
Build time: Wed Dec 19 12:58:44 2018<PHONE_NUMBER>)
GCC/Compiler version (if compiling from source):
gcc (Ubuntu 7.3.0-27ubuntu1~18.04) 7.3.0
CUDA/cuDNN version:
Cuda compilation tools, release 10.0, V10.0.130
GPU model and memory:
GTX 1060 Max Q, 6gb VRAM

Describe the current behavior
tf.contrib.summary.record_summaries_every_n_global_steps(n, global_step) may not be recording summaries unless global_step % n == 0, HOWEVER, it is running the code within its block anyways. In my opinion this is a huge waste of resources, especially when image logging is being done and transformations are required. Furthermore, there is no information of this behaviour on the documentation. Finally, it defeats the purpose of the function.
https://www.tensorflow.org/api_docs/python/tf/contrib/summary/record_summaries_every_n_global_steps
Describe the expected behavior
It should not run the code within its "with" block when global_step % n != 0, or documentation should be added that describes the current behaviour. It defeats the purpose of it when I can combine an if statement with tf.contrib.summary.always_record_summaries(): to produce better results.
Code to reproduce the issue
global_step = tf.train.get_or_create_global_step()
writer = tf.contrib.summary.create_file_writer('./test')
writer.set_as_default()

images = []
for i in range(100):
        images.append(np.random.uniform(0, 255, (32, 32, 3)).astype(np.float32))
images = np.array(images)
data = tf.data.Dataset.from_tensor_slices((images))

for i in range(10000):
        batch = data.batch(len(images))
        for image in batch:
                with tf.contrib.summary.record_summaries_every_n_global_steps(100, global_step):
                        print(global_step.numpy())
                        tf.contrib.summary.image('image', image)
        global_step.assign_add(1)

Other info / logs
0
1
2
3
4
5
6
....
9999

The images were still logged every global_step % n == 0 iterations, yet as can be seen here, the code within the block still executed every global_step. I shouldn't need to add an if global_step % n == 0: outside of the with tf.contrib.summary.record_summaries_every_n_global_steps(n, global_step): function. It literally defeats the purpose of it, as I might as well just use with tf.contrib.summary.always_record_summaries(): inside of an if global_step % n == 0:.

@jpatts This is more related to tensorboard Repo. Please post the issue here and the Tboard Team will take care of that issue. Thanks!

It has been 14 days with no activity and the awaiting response label was assigned. Is this still an issue?

Closing due to lack of recent activity. Please update the issue when new information becomes available, and we will open a new issue. Thanks!


Configure a remote VS Code devcontainer for GCP deployments

We have the vs code devcontainers for local development, and it would be super cool if we could have something similar for debugging in GCP.  I'm not sure how that would intersect with our current deployment mechanisms, but it looks like it's possible to do: https://code.visualstudio.com/docs/remote/containers-tutorial

So in order to have a setup in GCP environment, will need access to a project and to create a development VM (found that Ubuntu as the base os works best).
Once that is set up, using vscode, SSH into the GCE VM, some instructions here: https://cloud.google.com/compute/docs/instances/ssh
Once SSH into GCE VM, follow the exact steps in develop-vscode.md docs but skip Step 4 and go to Step 5 - GCP hybrid Turbinia setup.
The config file will also have to be updated post set up to SHARED_FILESYSTEM=False to allow turbiniactl to accept google cloud images.
Once done, you should be able to spin up a server/worker and send a request to process a googleclouddisk which allows for googleclouddisk to process.
Also this PR exposes /dev path for googleclouddisk to be seen by pod

Also run gcloud compute config-ssh to setup gcloud ssh

@wajihyassine Looks like we can close this as completed?

Yes this should still work although probably makes sense to have a GKE equivalent so that in realtime can help debug a few of those race condition issues we've been seeing. Will mark this as closed and we can open another issue to track that work


Vulnerability RSA PublicKey

Hello, i see this old article  when seggest add an algorithm parameter to their verification function how verify(string token, string algorithm, string verificationKey) for prevent attack with RSA publicKey but i not see the param algorithm or similary is required on verify function.
This vulnerabilities ir resolved on node-jsonwebtoken library??
How i prevent this problem on this library if not verified the used algorithm
Best reegards

If you don't pass any algorithm to the verify function, the library will try to infer which one it is based on the secret/public-key you passed to it:
https://github.com/auth0/node-jsonwebtoken/blob/master/verify.js#L67


Documentation: Is it possible to have multiple code editors running side by side?

I'm looking for a way to configure Sandpack to have one or more code editors visible side-by-side, similar to VSCode's split view.
Currently, SandpackProvider only appears to be able to accept a single activeFile, is it possible to have two via props or nested contexts?
Here's the code I have at the moment. Both transform + target should be shown side by side, however only the active file is shown in both views.
<SandpackProvider
  template="node"
  customSetup={{
    entry: "index.js",
    dependencies: {
      jscodeshift: "latest",
    },
  }}
  options={{
    showTabs: false,
    editorHeight: 1000,
    autoReload: true,
    activeFile: "/transform.js",
  }}
  files={{
    "/index.js": transformerFile,
    "/target.js": targetFile,
    "/transform.js": transformFile,
  }}
  >
  <SandpackLayout>
    <SandpackCodeEditor fileName="/transform.js" showTabs={false} />
    <SandpackCodeEditor fileName="/target.js" showTabs={false} />
    <SandpackPreview ref={previewRef} showOpenInCodeSandbox={false} />
  </SandpackLayout>
</SandpackProvider>

Disregard, i found the information on this page: https://sandpack.codesandbox.io/docs/quickstart#preview
See: Multiple Editors in the layout section


Contingency table updates

Summary of Changes to contingency_table Function

Error Handling for Columns:

Added a check to ensure at least one column is specified.
Updated the function to accept a single column as a string or multiple columns as a list.
Updated the function to raise a ValueError if no columns are provided or if cols is not correctly specified.

Function Parameters:

Changed the parameters from col1 and col2 to a single parameter cols which can be either a string or a list.

Error Handling for SortBy:

Renamed SortBy to sort_by to standardize nomenclature.
Added a check to ensure sort_by is either 0 or 1.
Updated the function to raise a ValueError if sort_by is not 0 or 1.

Sorting Logic:

Updated the sorting logic to handle the new cols parameter structure.

Handling Categorical Data:

Modified the code to convert categorical columns to strings to avoid issues with fillna("").

Handling Missing Values:

Added df = df.fillna('') to fill NA values within the function to account for missing data.

Improved Function Documentation:

Updated the function documentation to reflect the new parameters and error handling.

Excellent work!


Add testing mock providers for PFI + util for data provider

What type of PR is this? (check all applicable)

[ ] ♻ Refactor
[ ] ✨ New Feature
[ ] 🐛 Bug Fix
[x] 📝 Documentation Update
[ ] 👷 Example Application
[ ] 🧑💻 Code Snippet
[ ] 🎨 Design
[ ] 📖 Content
[ ] 🧪 Tests
[ ] 🔖 Release
[ ] 🚩 Other

Description
Add the following test classes:

MockDataProvider
MockExchangesApiProvider
MockOfferingsApiProvider

Also substitute them in where they should be used. Asserts are not added yet and will be reserved for follow-up
This PR [adds/removes/fixes/replaces] this [feature/bug/etc].
Related Tickets & Documents

Resolves #
Mobile & Desktop Screenshots/Recordings

Added code snippets?

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

Added tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

No tests? Add a note

Added to documentation?

[ ] 📜 readme
[ ] 📜 contributing.md
[x] 📓 general documentation
[ ] 🙅 no documentation needed

No docs? Add a note

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

build failures...will ping OSP in Discord

Build failing
Error: Can"t resolve<EMAIL_ADDRESS>in "/opt/build/repo/site/docs/tbdex/pfi"

Fixed


how to get group chat message?

hi. i can get personal chat message, but i can`t in group chat.
how can i get group chat message?

you probably need change the privacy settings of your bot. to do this you have to send '/setprivacy' to the telegram botfather and set it to 'Disable'.

@realestninja  thank you! it works.


Create a gradio based GUI to compare different approaches

Initially brought up in #8 having a GUI would make it easier to visualize and compare different approaches.

I have not fully tested, but it seems to be working. Have a look. I'll be adding a log of everything the approach is doing later this evening when i have a minute.

Hi @codelion I liked this project very much and want to work on this issue. I will be grateful for any specific guidance from your side.

Hi @AdityaPandeyCN for the UI we can have a simple chat-like interface that connects with the optillm proxy and allows users to choose the approaches and try out queries. Something similar to https://huggingface.co/spaces/codelion/optillm


Error on Human detected

Getting an error on latest version when a human is detected by amcrest doorbell.
25/03/2022 22:06:09 [INFO] App Version: 1.0.16
25/03/2022 22:06:09 [INFO] Fetching camera details...
25/03/2022 22:06:14 [INFO] Device type: AD410
25/03/2022 22:06:14 [INFO] Serial number: REDACTED
25/03/2022 22:06:14 [INFO] Software version: 1.000.0000000.7.R (2021-02-20)
25/03/2022 22:06:14 [INFO] Device name: Front Door
25/03/2022 22:06:15 [INFO] Writing Home Assistant discovery config...
25/03/2022 22:06:15 [INFO] Fetching storage sensors...
25/03/2022 22:06:15 [INFO] Listening for events...
25/03/2022 22:08:46 [INFO] {'Code': 'TimeChange', 'action': 'Pulse', 'index': '0', 'data': {'BeforeModifyTime': '2022-03-25 05:08:46', 'ModifiedTime': '2022-03-25 05:08:46'}}
25/03/2022 22:08:46 [INFO] {'Code': 'NTPAdjustTime', 'action': 'Pulse', 'index': '0', 'data': {'Address': '<IP_ADDRESS>', 'Before': '2022-03-25 05:08:45', 'result': True}}
25/03/2022 22:09:41 [INFO] {'Code': 'VideoMotionInfo', 'action': 'State', 'index': '0'}
25/03/2022 22:09:41 [INFO] {'Code': 'VideoMotion', 'action': 'Start', 'index': '0', 'data': {'Id': [0], 'RegionName': ['Region1']}}
25/03/2022 22:09:42 [INFO] {'Code': 'NewFile', 'action': 'Pulse', 'index': '0', 'data': {'File'<EMAIL_ADDRESS>'Size': 39803, 'StoragePoint': 'NULL'}}
an error occurred during closing of asynchronous generator <async_generator object AsyncClient.stream at 0x7f9eb4040820>
asyncgen: <async_generator object AsyncClient.stream at 0x7f9eb4040820>
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/usr/local/lib/python3.9/asyncio/base_events.py", line 647, in run_until_complete
    return future.result()
  File "/app/amcrest2mqtt.py", line 426, in main
    elif code == "CrossRegionDetection" and payload["data"]["ObjectType"] == "Human":
KeyError: 'ObjectType'

During handling of the above exception, another exception occurred:

RuntimeError: aclose(): asynchronous generator is already running
an error occurred during closing of asynchronous generator <async_generator object Http.async_stream_command at 0x7f9eb3c9e4c0>
asyncgen: <async_generator object Http.async_stream_command at 0x7f9eb3c9e4c0>
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/usr/local/lib/python3.9/asyncio/base_events.py", line 647, in run_until_complete
    return future.result()
  File "/app/amcrest2mqtt.py", line 426, in main
    elif code == "CrossRegionDetection" and payload["data"]["ObjectType"] == "Human":
KeyError: 'ObjectType'

During handling of the above exception, another exception occurred:

RuntimeError: aclose(): asynchronous generator is already running
an error occurred during closing of asynchronous generator <async_generator object Http._async_stream_command at 0x7f9eb4040790>
asyncgen: <async_generator object Http._async_stream_command at 0x7f9eb4040790>
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/usr/local/lib/python3.9/asyncio/base_events.py", line 647, in run_until_complete
    return future.result()
  File "/app/amcrest2mqtt.py", line 426, in main
    elif code == "CrossRegionDetection" and payload["data"]["ObjectType"] == "Human":
KeyError: 'ObjectType'

During handling of the above exception, another exception occurred:

RuntimeError: aclose(): asynchronous generator is already running
Traceback (most recent call last):
  File "/app/amcrest2mqtt.py", line 440, in <module>
    asyncio.run(main())
  File "/usr/local/lib/python3.9/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/usr/local/lib/python3.9/asyncio/base_events.py", line 647, in run_until_complete
    return future.result()
  File "/app/amcrest2mqtt.py", line 426, in main
    elif code == "CrossRegionDetection" and payload["data"]["ObjectType"] == "Human":
KeyError: 'ObjectType'

I'm getting the exact same error since yesterday. Same versions, same doorbell.
I don't know what changed.

Same, reverting to previous version of container fixes the issue.

image: dchesterton/amcrest2mqtt:1.0.15 is the version I'm running
On Thu, May 5, 2022 at 10:48 AM SMAW @.***> wrote:

Same, reverting to previous version of container fixes the issue.
@tehbra1n https://github.com/tehbra1n To which version did you revert?
I have the same issue...
—
Reply to this email directly, view it on GitHub
https://github.com/dchesterton/amcrest2mqtt/issues/67#issuecomment-1118647692,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEEATPH3PZCDA3C3D7ZUESLVIPNU5ANCNFSM5RVN3TAA
.
You are receiving this because you were mentioned.Message ID:
@.***>

I had a very similar issue and contacted Amcrest for the current firmware. ...R.20210712 is current for the AD110 and solves these issues. I understood from them that the phone app has a bug and will not show the current firmware, so it has to be manually pushed.

I changed this line in the Docker Container  in  /app/amcrest2mqtt.py (Not the Image... not really a Docker Guru or a Python Programmer for that matter) (I know if I do another pull it'll overwrite it)
           elif code == "CrossRegionDetection" and payload["data"]["Object"]["ObjectType"] == "Human":

added the ["Object"] and that seems to keep it from crashing. I think the JSON that comes from the Device might have changed in a Firmware update on the AD410
I had to move the Debugger line that Dumps the JSON to before the above line so I could Parse it and figured out they lump all the info about the "Object" in the camera into an Object Array  Object:{ ... } which has the ObjectType Node
Hope that Helps

I'm seeing the same thing with my Amcrest 410
amcrest2mqtt    | an error occurred during closing of asynchronous generator <async_generator object Http._async_stream_command at 0x7fa9d3adee50>
amcrest2mqtt    | asyncgen: <async_generator object Http._async_stream_command at 0x7fa9d3adee50>
amcrest2mqtt    | Traceback (most recent call last):
amcrest2mqtt    |   File "/usr/local/lib/python3.9/asyncio/runners.py", line 44, in run
amcrest2mqtt    |     return loop.run_until_complete(main)
amcrest2mqtt    |   File "/usr/local/lib/python3.9/asyncio/base_events.py", line 647, in run_until_complete
amcrest2mqtt    |     return future.result()
amcrest2mqtt    |   File "/app/amcrest2mqtt.py", line 426, in main
amcrest2mqtt    |     elif code == "CrossRegionDetection" and payload["data"]["ObjectType"] == "Human":
amcrest2mqtt    | KeyError: 'ObjectType'
amcrest2mqtt    |
amcrest2mqtt    | During handling of the above exception, another exception occurred:
amcrest2mqtt    |
amcrest2mqtt    | RuntimeError: aclose(): asynchronous generator is already running

And thanks btw for publishing a multi-architecture docker image, I'll be able to run it in k3s without restricting it to specific nodes.

I changed this line in the Docker Container in /app/amcrest2mqtt.py (Not the Image... not really a Docker Guru or a Python Programmer for that matter) (I know if I do another pull it'll overwrite it)
           elif code == "CrossRegionDetection" and payload["data"]["Object"]["ObjectType"] == "Human":

added the ["Object"] and that seems to keep it from crashing. I think the JSON that comes from the Device might have changed in a Firmware update on the AD410
I had to move the Debugger line < log(str(payload)) > that Dumps the JSON to before the above line so I could Parse it and figured out they lump all the info about the "Object" in the camera into an Object Array Object:{ ... } which has the ObjectType Node
Hope that Helps

Thanks ! this worked perfectly.

Thanks to jweston2112 , i just created a pull request..
https://github.com/dchesterton/amcrest2mqtt/pull/91

If anyone cares, I've updated this and added an option to capture IVS events. The image is available at myeager1967/amcrest2mqtt:1.0.17.
I also updated the amcrest library and slugify. The mqtt client (paho) is a bit more involved. I will eventually put this up on my GitHub page.


Add options cli

Add some options to the command line:

--verbose
--version
--logname

This PR also make a little refactor of the command line and its (sub)parsers.
Closes #123

Hello @mdiazmel! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file clinicadl/clinicadl/__init__.py:

Line 17:1: W391 blank line at end of file

In the file clinicadl/clinicadl/cli.py:

Line 233:43: W291 trailing whitespace
Line 234:13: E128 continuation line under-indented for visual indent
Line 234:28: W291 trailing whitespace
Line 235:13: E128 continuation line under-indented for visual indent
Line 236:13: E128 continuation line under-indented for visual indent
Line 237:13: E126 continuation line over-indented for hanging indent
Line 239:13: E128 continuation line under-indented for visual indent
Line 240:13: E128 continuation line under-indented for visual indent
Line 241:13: E128 continuation line under-indented for visual indent
Line 242:5: E265 block comment should start with '# '
Line 257:5: E265 block comment should start with '# '
Line 272:5: E265 block comment should start with '# '

In the file clinicadl/clinicadl/main.py:

Line 21:8: E111 indentation is not a multiple of four
Line 23:8: E111 indentation is not a multiple of four

I'll merge this one!


Project status

@vitalets the project seems static since a while, can we have an update on what's its status? The code is top quality and it's a shame to see it unmantained.

@eugef I think this can be closed.


tronAdapter OKX Bug

I'm using tronAdapter with OKX Wallet. There's something really strange happening. In the mobile OKX DApp browser, when I call await sendRawTransaction, the code does not proceed to the next line. I don't know the reason for this.
When I call sendRawTransaction, it transitions to the contract interaction screen of the OKX Wallet, but even after accepting, the code does not move to the next line. This code works fine in the PC web extension.
`const functionSelector = 'transfer(address,uint256)';
const parameter = [{type: 'address', value: to}, {type: 'uint256', value: amount}]//to Address
// @ts-expect-error:test
const tx = await tronweb.transactionBuilder.triggerSmartContract('-------', functionSelector, {}, parameter);//Contract Address
const signedTx = await tronweb.trx.sign(tx.transaction);
  // @ts-expect-error:test
  const result = await tronweb.trx.sendRawTransaction(signedTx)
  //???????????????????????????????????????????????????????????????????????????????????????
  //It does not proceed past this line.

//???????????????????????????????????????????????????????????????????????????????????????
return result.transaction.txID;`

According to the Okx Development Document , you should use okxwallet.tronLink.tronWeb to create transaction:
const tronWeb = okxwallet.tronLink.tronWeb;
const tradeobj = await tronWeb.transactionBuilder.sendTrx("TNo9e8MWQpGVqdyySxLSTw3gjgFQWE3vfg", 100,"TM2TmqauSEiRf16CyFgzHV2BVxBejY9iyR",1);
const signedtxn = await tronWeb.trx.sign(tradeobj, privateKey);
const receipt = await tronWeb.trx.sendRawTransaction(signedtxn);
console.log(receipt)

Also you can use vConsole or something else to debug your website and see if there are some errors.


[Forwardport] Add support for scored named queries (version updates)

Description
Forward port of https://github.com/opensearch-project/OpenSearch/pull/12427 to main
Related Issues
N/A

Check List

[X] New functionality includes testing.

[X] All tests pass

[X] New functionality has been documented.

[X] New functionality has javadoc added

[X] Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
[X] Commits are signed per the DCO using --signoff
[X] Commit changes are listed out in CHANGELOG.md file (See: Changelog)
[X] Public documentation issue/PR created

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

❌ Gradle check result for 3b1dccb: FAILURE

java.lang.IllegalStateException: failed to obtain node locks, tried [[/var/jenkins/workspace/gradle-check/search/server/build/testrun/internalClusterTest/temp/org.opensearch.search.suggest.SuggestSearchIT_D86CA15E412A03DB-001/tempDir-003/node_s0]] with lock id [0]; maybe these locations are not writable or multiple nodes were started without increasing [node.max_local_storage_nodes] (was [1])?

❌ Gradle check result for 3b1dccb: FAILURE

java.lang.Exception: Test abandoned because suite timeout was reached.
	at __randomizedtesting.SeedInfo.seed([C67BBC8BDFFCAB4E]:0)


Fix Japanese translation of "Double Faults"

Fix #1126

Thanks for the PR!
@garasubo Could you do a quick review?

Thanks!


Document needed versions of pytorch and numpy

I'm unsuccesfully trying to get pykeen runing since some time.
So far I figured out that it needs pytorch == 0.4.1 but it still fails with PyTorch was compiled without NumPy support even through I had numpy installed before installing pytorch. What version of numpy do I need for pykeen?

Hi @Nudin,
in case you use Python 3.6, PyTorch 0.4.0 is required for PyKEEN, and for Python 3.7, PyTorch 0.4.1 is needed. We didn't define any restrictions for Numpy (the current version of Numpy works fine for PyKEEN).
Are you using Windows, Linux or MacOS?
We recommend to use a separate virtual environment inside a Linux or MacOS system:
virtualenv -p python3.6/3.7 envname
If you install PyKEEN, all dependent packages will be automatically installed:
pip install pykeen
If you use Windows, please also check https://github.com/SmartDataAnalytics/PyKEEN/issues/57

Hi @Nudin , @mali-git
#63 seems to solve the this issue.

Thanks @mberr!
@Nudin The corresponding pull request (https://github.com/SmartDataAnalytics/PyKEEN/pull/63) has been merged with the master branch.

#63 did indeed fix the issue. Thanks!

When using pykeen as a library the error still persists. Because the fix #63 is not included in pykeen 0.0.25.

When using pykeen as a library the error still persists. Because the fix #63 is not included in pykeen 0.0.25.

Hi @BonaBeavis,
we just released pykeen 0.0.26 (2df826ab895f7bca422452459c77de6611717350) which solves the issue.
Meanwhile we are working on PyKEEN 0.1.0, which will be released soon.


Improve error messages and logging for WCOW

Improves some code in hcsoci to clean up logging, and improve error
messages. Mostly focused on improving diagnostics for WCOW, but some of
the changes impact LCOW container paths as well.
Signed-off-by: Kevin Parsons<EMAIL_ADDRESS>

@kevpar can you rebase this?

@kevpar what's the status of this? looks like we just need it to be rebased and then merged


Follow up projects

Extend the time-scale of forecasts out to 25-30 years (extra few years of NDVI + only training on 5-10 yrs)
Select the sites with the most rapid/directional environmental change and see if they are more forecastable (involve Allen Hurlbert if he's interested since this came in part from him)
Compare influence of using forecast instead of known environmental variables (@sdtaylor's idea)

I think all three of these are both pretty important and should be doable pretty quickly once we get the first paper out the door.

1 & 2 could probably be combined effectively into a single paper.


Cell debugging hangs forever

Environment data

VS Code Version: 1.93.0 (user setup)
Commit: 4849ca9bdf9666755eb463db297b69e5385090e3
Date: 2024-09-04T13:02:38.431Z
Electron: 30.4.0
ElectronBuildId: 10073054
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: <IP_ADDRESS>-electron.0
Jupyter Extension version (available under the Extensions sidebar): v2024.8.1
Python Extension version (available under the Extensions sidebar): v2024.14.0
OS (Windows | Mac | Linux distro) and version: Windows_NT x64 10.0.22631
Python and/or Anaconda version: 3.10.9
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
Jupyter server running: Local

Expected behaviour
Able to debug cell code.
Actual behaviour
Forever hangs
Steps to reproduce:

create test.ipynb
debug cell
hang

Logs

Output for Jupyter in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Jupyter)

22:16:14.534 [debug] Disposing kernel associated with ~\Downloads\Jupyter\test.ipynb, isClosed=true
22:16:14.534 [info] Dispose Kernel '~\Downloads\Jupyter\test.ipynb' associated with '~\Downloads\Jupyter\test.ipynb'
22:16:14.536 [debug] Shutdown session aabbb88a-ba1b-44d1-8e09-c0721c71620a, .jvsc74a57bd037c14770eaeddcb100369fbe6426aa9a25d7edf158a9b0cd731a11ba86e125ae.c:\Users\~\miniconda3\python.exe.c:\Users\~\miniconda3\python.exe.-m#ipykernel_launcher - start called from Error:
    at R_.shutdown (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2024.8.1-win32-x64\dist\extension.node.js:304:1140)
    at R_.dispose (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2024.8.1-win32-x64\dist\extension.node.js:304:623)
    at bs (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2024.8.1-win32-x64\dist\extension.node.js:115:867)
    at e (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2024.8.1-win32-x64\dist\extension.node.js:285:31789)
    at n_.dispose (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2024.8.1-win32-x64\dist\extension.node.js:285:32034)
    at fy.disposeOldKernel (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2024.8.1-win32-x64\dist\extension.node.js:285:23341)
    at fy.<anonymous> (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2024.8.1-win32-x64\dist\extension.node.js:285:21548)
    at i.value (c:\Users\~\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:171:28704)
    at r.B (c:\Users\~\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:90:732)
    at r.C (c:\Users\~\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:90:802)
    at r.fire (c:\Users\~\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:90:1018)
    at g.$acceptDocumentAndEditorsDelta (c:\Users\~\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:166:9528)
    at y.S (c:\Users\~\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:158:5968)
    at y.Q (c:\Users\~\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:158:5734)
    at y.M (c:\Users\~\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:158:4767)
    at y.L (c:\Users\~\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:158:3823)
    at i.value (c:\Users\~\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:158:2297)
    at r.B (c:\Users\~\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:90:732)
    at r.fire (c:\Users\~\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:90:949)
    at a.fire (c:\Users\~\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:115:14463)
    at i.value (c:\Users\~\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:184:8635)
    at r.B (c:\Users\~\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:90:732)
    at r.fire (c:\Users\~\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:90:949)
    at a.fire (c:\Users\~\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:115:14463)
    at MessagePortMain.<anonymous> (c:\Users\~\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:184:6761)
    at MessagePortMain.emit (node:events:519:28)
    at Object.MessagePortMain._internalPort.emit (node:electron/js2c/utility_init:2:2619)
22:16:14.536 [debug] Dispose Kernel process 34812.
22:16:14.541 [info] Process Execution: c:\Windows\System32\taskkill.exe /F /T /PID 34812
22:16:14.541 [debug] Kernel got disposed, hence there is no longer a kernel associated with ~\Downloads\Jupyter\test.ipynb
22:16:14.542 [debug] Notebook document ~\Downloads\Jupyter\test.ipynb got closed
22:16:14.702 [debug] Disposed Kernel process 34812.
22:16:14.702 [debug] Shutdown session aabbb88a-ba1b-44d1-8e09-c0721c71620a, .jvsc74a57bd037c14770eaeddcb100369fbe6426aa9a25d7edf158a9b0cd731a11ba86e125ae.c:\Users\~\miniconda3\python.exe.c:\Users\~\miniconda3\python.exe.-m#ipykernel_launcher - shutdown complete
22:16:14.707 [debug] KernelProcess Exited 34812, Exit Code - 1
22:16:27.660 [debug] KernelProvider switched kernel to id = .jvsc74a57bd037c14770eaeddcb100369fbe6426aa9a25d7edf158a9b0cd731a11ba86e125ae.c:\Users\~\miniconda3\python.exe.c:\Users\~\miniconda3\python.exe.-m#ipykernel_launcher
22:16:27.661 [debug] start the kernel, options.disableUI=true for ~\Downloads\Jupyter\test.ipynb
22:16:27.661 [debug] Controller selection change completed
22:16:27.662 [info] Starting Kernel (Python Path: ~\miniconda3\python.exe, Conda, 3.10.9) for '~\Downloads\Jupyter\test.ipynb' (disableUI=true)
22:16:27.662 [trace] Creating raw notebook for resource '~\Downloads\Jupyter\test.ipynb'
22:16:27.664 [trace] Registering commtarget jupyter.widget
22:16:27.668 [debug] Interpreter for Pylance for Notebook URI "~\Downloads\Jupyter\test.ipynb" is ~\miniconda3\python.exe
22:16:27.679 [info] Process Execution: ~\miniconda3\python.exe -c "import ipykernel; print(ipykernel.__version__); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.__file__)"
22:16:27.760 [debug] Launching kernel .jvsc74a57bd037c14770eaeddcb100369fbe6426aa9a25d7edf158a9b0cd731a11ba86e125ae.c:\Users\~\miniconda3\python.exe.c:\Users\~\miniconda3\python.exe.-m#ipykernel_launcher for ~\Downloads\Jupyter\test.ipynb in ~\Downloads\Jupyter with ports 9001, 9000, 9004, 9002, 9003
22:16:27.765 [trace] Got a response of 2568 for INITIALIZE_INTERRUPT:8
22:16:27.775 [info] Process Execution: ~\miniconda3\python.exe -m ipykernel_launcher --f=c:\Users\~\AppData\Roaming\jupyter\runtime\kernel-v317ea9843585b871a85eebe13c5475e1967cd4aba.json
    > cwd: ~\Downloads\Jupyter
22:16:27.775 [debug] Kernel process 22020.
22:16:28.145 [trace] ipykernel version & path 6.28.0, ~\miniconda3\lib\site-packages\ipykernel\__init__.py for ~\miniconda3\python.exe
22:16:29.000 [debug] Kernel output 22020: To connect another client to this kernel, use:
--existing c:\Users\~\AppData\Roaming\jupyter\runtime\kernel-v317ea9843585b871a85eebe13c5475e1967cd4aba.json
22:16:29.035 [debug] Waiting for Raw Session to be ready in postStartRawSession
22:16:29.035 [debug] Waiting for Raw session to be ready, status: connected
22:16:29.035 [trace] Raw session connected
22:16:29.036 [debug] Waited for Raw session to be ready & got status: connected
22:16:29.036 [debug] Successfully waited for Raw Session to be ready in postStartRawSession
22:16:29.036 [debug] Kernel status is 'unknown' before requesting kernel info and after ready
22:16:29.036 [debug] Sending request for kernelInfo
22:16:29.048 [trace] Got response for requestKernelInfo
22:16:29.048 [debug] Successfully completed postStartRawSession after 1 attempt(s) in 12ms
22:16:29.050 [trace] Executing silently Code (idle) = import sys as _VSCODE_sys\nprint(_VSCODE_sys.executable); del _VSCODE_sys
22:16:29.076 [trace] Executing silently Code (completed) = import sys as _VSCODE_sys\nprint(_VSCODE_sys.executable); del _VSCODE_sys with 1 output(s)
22:16:29.076 [trace] Started running kernel initialization for ~\Downloads\Jupyter\test.ipynb
22:16:29.077 [trace] Executing silently Code (idle) = try:\nimport ipywidgets as _VSCODE_ipywidgets\nprint("e976ee50-99ed-4aba-9b6b-9dcd5634d07d:IPy
22:16:29.166 [trace] Executing silently Code (completed) = try:\nimport ipywidgets as _VSCODE_ipywidgets\nprint("e976ee50-99ed-4aba-9b6b-9dcd5634d07d:IPy with 1 output(s)
22:16:29.167 [trace] Determined IPyWidgets Version as 8
22:16:29.168 [trace] Version of IPyWidgets 8 determined after 1.502s
22:16:29.168 [trace] Version of IPyWidgets 8 determined after 1.279s
22:16:29.168 [trace] Executing silently Code (idle) = def __VSCODE_inject_module():\ndef __VSCODE_call_function(function, callback, data=None):
22:16:29.198 [trace] Executing silently Code (completed) = def __VSCODE_inject_module():\ndef __VSCODE_call_function(function, callback, data=None): with 0 output(s)
22:16:29.198 [debug] Requesting Kernel info
22:16:29.198 [trace] Got Kernel info
22:16:29.199 [trace] End running kernel initialization, now waiting for idle
22:16:29.199 [trace] Waiting for idle on (kernel): 48cc9acf-4980-4feb-ae4d-2cf8d12c9cc0 -> idle
22:16:29.200 [trace] Finished waiting for idle on (kernel): 48cc9acf-4980-4feb-ae4d-2cf8d12c9cc0 -> idle
22:16:29.200 [trace] End running kernel initialization, session is idle
22:16:29.202 [trace] Registering Kernel Completion Provider from kernel base (Python 3.10.9) for language python
22:16:29.202 [trace] IPyWidgetScriptSource.initialize
22:16:29.203 [info] Kernel successfully started
22:16:29.701 [trace] Web view is ready to receive widget messages
22:16:29.706 [trace] Widget Message: Received IPyWidgets_kernelOptions in ScriptManager
22:16:29.707 [trace] Widget Message: Received IPyWidgetMessages.IPyWidgets_kernelOptions
22:16:29.719 [trace] Widget Message: data-base-url set to https://file%2B.vscode-resource.vscode-cdn.net/c%3A/Users/~/.vscode/extensions/ms-toolsai.jupyter-2024.8.1-win32-x64/temp/scripts/39893d3df7c95028d68b530c4b6bbc6aa1a2e11e22e22fec53101146ec7be797/jupyter
22:16:29.720 [trace] Widget Message: Received IPyWidgets_kernelOptions in ScriptManager
22:16:29.721 [trace] Widget Message: Received IPyWidgetMessages.IPyWidgets_kernelOptions
22:16:29.722 [trace] Widget Message: data-base-url set to https://file%2B.vscode-resource.vscode-cdn.net/c%3A/Users/~/.vscode/extensions/ms-toolsai.jupyter-2024.8.1-win32-x64/temp/scripts/39893d3df7c95028d68b530c4b6bbc6aa1a2e11e22e22fec53101146ec7be797/jupyter
22:16:39.217 [info] Starting debugging with mode 1
22:16:39.217 [trace] Executing silently Code (idle) = import builtins\nimport ipykernel\nbuiltins.print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d" + ipykernel._
22:16:39.234 [trace] Executing silently Code (completed) = import builtins\nimport ipykernel\nbuiltins.print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d" + ipykernel._ with 1 output(s)
22:16:39.279 [debug] [Debug] to kernel: {"command":"initialize","arguments":{"clientID":"vscode","clientName":"Visual Studio Code","adapterID":"Python Kernel Debug Adapter","pathFormat":"path","linesStartAt1":true,"columnsStartAt1":true,"supportsVariableType":true,"supportsVariablePaging":true,"supportsRunInTerminalRequest":true,"locale":"en","supportsProgressReporting":true,"supportsInvalidatedEvent":true,"supportsMemoryReferences":true,"supportsArgsCanBeInterpretedByShell":true,"supportsMemoryEvent":true,"supportsStartDebuggingRequest":true},"type":"request","seq":1}
22:16:39.280 [debug] [Debug] to kernel, mapped: {"command":"initialize","arguments":{"clientID":"vscode","clientName":"Visual Studio Code","adapterID":"Python Kernel Debug Adapter","pathFormat":"path","linesStartAt1":true,"columnsStartAt1":true,"supportsVariableType":true,"supportsVariablePaging":true,"supportsRunInTerminalRequest":true,"locale":"en","supportsProgressReporting":true,"supportsInvalidatedEvent":true,"supportsMemoryReferences":true,"supportsArgsCanBeInterpretedByShell":true,"supportsMemoryEvent":true,"supportsStartDebuggingRequest":true},"type":"request","seq":1}
22:16:39.615 [debug] [Debug] event: {"header":{"msg_id":"ee1acb62-6643481e261decbbdf60ed9a_22020_40","msg_type":"debug_event","username":"username","session":"ee1acb62-6643481e261decbbdf60ed9a","date":"2024-09-11T14:16:39.611714Z","version":"5.3"},"parent_header":{"date":"2024-09-11T14:16:39.280000Z","msg_id":"4b893507-9af2-424c-b3b9-d4b2959c14a2","msg_type":"debug_request","session":"14ad0216-2c3d-4fec-a9f8-c0830d394fc0","username":"a7fea785-4759-4878-9ff3-e78b019063b0","version":"5.2"},"metadata":{},"content":{"seq":1,"type":"event","event":"output","body":{"category":"telemetry","output":"ptvsd","data":{"packageVersion":"1.6.7"}}},"idents":[{"type":"Buffer","data":[107,101,114,110,101,108,46,98,54,97,51,52,54,101,57,45,48,54,55,54,45,52,52,55,52,45,57,51,102,98,45,51,50,49,55,53,102,51,50,102,102,100,48,46,100,101,98,117,103,95,101,118,101,110,116]}],"buffers":[],"channel":"iopub"}
22:16:39.616 [debug] [Debug] event: {"header":{"msg_id":"ee1acb62-6643481e261decbbdf60ed9a_22020_41","msg_type":"debug_event","username":"username","session":"ee1acb62-6643481e261decbbdf60ed9a","date":"2024-09-11T14:16:39.612719Z","version":"5.3"},"parent_header":{"date":"2024-09-11T14:16:39.280000Z","msg_id":"4b893507-9af2-424c-b3b9-d4b2959c14a2","msg_type":"debug_request","session":"14ad0216-2c3d-4fec-a9f8-c0830d394fc0","username":"a7fea785-4759-4878-9ff3-e78b019063b0","version":"5.2"},"metadata":{},"content":{"seq":2,"type":"event","event":"output","body":{"category":"telemetry","output":"debugpy","data":{"packageVersion":"1.6.7"}}},"idents":[{"type":"Buffer","data":[107,101,114,110,101,108,46,98,54,97,51,52,54,101,57,45,48,54,55,54,45,52,52,55,52,45,57,51,102,98,45,51,50,49,55,53,102,51,50,102,102,100,48,46,100,101,98,117,103,95,101,118,101,110,116]}],"buffers":[],"channel":"iopub"}
22:16:39.617 [debug] [Debug] response: {"seq":3,"type":"response","request_seq":1,"success":true,"command":"initialize","body":{"supportsCompletionsRequest":true,"supportsConditionalBreakpoints":true,"supportsConfigurationDoneRequest":true,"supportsDebuggerProperties":true,"supportsDelayedStackTraceLoading":true,"supportsEvaluateForHovers":true,"supportsExceptionInfoRequest":true,"supportsExceptionOptions":true,"supportsFunctionBreakpoints":true,"supportsHitConditionalBreakpoints":true,"supportsLogPoints":true,"supportsModulesRequest":true,"supportsSetExpression":true,"supportsSetVariable":true,"supportsValueFormattingOptions":true,"supportsTerminateRequest":true,"supportsGotoTargetsRequest":true,"supportsClipboardContext":true,"exceptionBreakpointFilters":[{"filter":"raised","label":"Raised Exceptions","default":false,"description":"Break whenever any exception is raised."},{"filter":"uncaught","label":"Uncaught Exceptions","default":true,"description":"Break when the process is exiting due to unhandled exception."},{"filter":"userUnhandled","label":"User Uncaught Exceptions","default":false,"description":"Break when exception escapes into library code."}],"supportsStepInTargetsRequest":true,"supportsRestartRequest":true}}
22:16:39.622 [debug] [Debug-Reset] attach: Continuing paused kernel threads if needed
22:16:39.623 [debug] [Debug] to kernel: {"command":"debugInfo","type":"request","seq":3}
22:16:39.623 [debug] [Debug] to kernel, mapped: {"command":"debugInfo","type":"request","seq":3}
22:16:39.627 [debug] [Debug] response: {"type":"response","request_seq":3,"success":true,"command":"debugInfo","body":{"isStarted":true,"hashMethod":"Murmur2","hashSeed":3339675911,"tmpFilePrefix":"C:\\Users\\~\\AppData\\Local\\Temp\\ipykernel_22020\\","tmpFileSuffix":".py","breakpoints":[],"stoppedThreads":[],"richRendering":true,"exceptionPaths":["Python Exceptions"],"copyToGlobals":true}}
22:16:39.646 [debug] [Debug] to kernel: {"command":"attach","arguments":{"type":"Python Kernel Debug Adapter","name":"test.ipynb","request":"attach","justMyCode":false,"__mode":1,"__cellIndex":0,"__notebookUri":"file:///c%3A/Users/~/Downloads/Jupyter/test.ipynb","__sessionId":"4931f3c5-85a7-4c0b-85fb-28de701cbb8c"},"type":"request","seq":2}
22:16:39.646 [debug] [Debug] to kernel, mapped: {"command":"attach","arguments":{"type":"Python Kernel Debug Adapter","name":"test.ipynb","request":"attach","justMyCode":false,"__mode":1,"__cellIndex":0,"__notebookUri":"file:///c%3A/Users/~/Downloads/Jupyter/test.ipynb","__sessionId":"4931f3c5-85a7-4c0b-85fb-28de701cbb8c"},"type":"request","seq":2}
22:16:39.653 [debug] [Debug] event: {"header":{"msg_id":"ee1acb62-6643481e261decbbdf60ed9a_22020_48","msg_type":"debug_event","username":"username","session":"ee1acb62-6643481e261decbbdf60ed9a","date":"2024-09-11T14:16:39.649737Z","version":"5.3"},"parent_header":{"date":"2024-09-11T14:16:39.646000Z","msg_id":"b8d29f1f-584f-4d91-8af5-d6c4c7fffe38","msg_type":"debug_request","session":"14ad0216-2c3d-4fec-a9f8-c0830d394fc0","username":"a7fea785-4759-4878-9ff3-e78b019063b0","version":"5.2"},"metadata":{},"content":{"seq":4,"type":"event","event":"debugpyWaitingForServer","body":{"host":"<IP_ADDRESS>","port":9706}},"idents":[{"type":"Buffer","data":[107,101,114,110,101,108,46,98,54,97,51,52,54,101,57,45,48,54,55,54,45,52,52,55,52,45,57,51,102,98,45,51,50,49,55,53,102,51,50,102,102,100,48,46,100,101,98,117,103,95,101,118,101,110,116]}],"buffers":[],"channel":"iopub"}
22:16:39.660 [debug] [Debug] event: {"header":{"msg_id":"ee1acb62-6643481e261decbbdf60ed9a_22020_49","msg_type":"debug_event","username":"username","session":"ee1acb62-6643481e261decbbdf60ed9a","date":"2024-09-11T14:16:39.658745Z","version":"5.3"},"parent_header":{"date":"2024-09-11T14:16:39.646000Z","msg_id":"b8d29f1f-584f-4d91-8af5-d6c4c7fffe38","msg_type":"debug_request","session":"14ad0216-2c3d-4fec-a9f8-c0830d394fc0","username":"a7fea785-4759-4878-9ff3-e78b019063b0","version":"5.2"},"metadata":{},"content":{"seq":5,"type":"event","event":"initialized"},"idents":[{"type":"Buffer","data":[107,101,114,110,101,108,46,98,54,97,51,52,54,101,57,45,48,54,55,54,45,52,52,55,52,45,57,51,102,98,45,51,50,49,55,53,102,51,50,102,102,100,48,46,100,101,98,117,103,95,101,118,101,110,116]}],"buffers":[],"channel":"iopub"}
22:16:39.664 [debug] [Debug] response: {"seq":7,"type":"response","request_seq":2,"success":true,"command":"attach"}
22:16:39.668 [debug] [Debug] event: {"header":{"msg_id":"ee1acb62-6643481e261decbbdf60ed9a_22020_52","msg_type":"debug_event","username":"username","session":"ee1acb62-6643481e261decbbdf60ed9a","date":"2024-09-11T14:16:39.664003Z","version":"5.3"},"parent_header":{"date":"2024-09-11T14:16:39.646000Z","msg_id":"b8d29f1f-584f-4d91-8af5-d6c4c7fffe38","msg_type":"debug_request","session":"14ad0216-2c3d-4fec-a9f8-c0830d394fc0","username":"a7fea785-4759-4878-9ff3-e78b019063b0","version":"5.2"},"metadata":{},"content":{"seq":8,"type":"event","event":"process","body":{"name":"c:\\Users\\~\\miniconda3\\lib\\site-packages\\ipykernel_launcher.py","systemProcessId":22020,"isLocalProcess":true,"startMethod":"attach"}},"idents":[{"type":"Buffer","data":[107,101,114,110,101,108,46,98,54,97,51,52,54,101,57,45,48,54,55,54,45,52,52,55,52,45,57,51,102,98,45,51,50,49,55,53,102,51,50,102,102,100,48,46,100,101,98,117,103,95,101,118,101,110,116]}],"buffers":[],"channel":"iopub"}
22:16:39.668 [debug] [Debug] event: {"header":{"msg_id":"ee1acb62-6643481e261decbbdf60ed9a_22020_53","msg_type":"debug_event","username":"username","session":"ee1acb62-6643481e261decbbdf60ed9a","date":"2024-09-11T14:16:39.664003Z","version":"5.3"},"parent_header":{"date":"2024-09-11T14:16:39.646000Z","msg_id":"b8d29f1f-584f-4d91-8af5-d6c4c7fffe38","msg_type":"debug_request","session":"14ad0216-2c3d-4fec-a9f8-c0830d394fc0","username":"a7fea785-4759-4878-9ff3-e78b019063b0","version":"5.2"},"metadata":{},"content":{"seq":9,"type":"event","event":"thread","body":{"reason":"started","threadId":1}},"idents":[{"type":"Buffer","data":[107,101,114,110,101,108,46,98,54,97,51,52,54,101,57,45,48,54,55,54,45,52,52,55,52,45,57,51,102,98,45,51,50,49,55,53,102,51,50,102,102,100,48,46,100,101,98,117,103,95,101,118,101,110,116]}],"buffers":[],"channel":"iopub"}
22:16:39.669 [debug] [Debug] event: {"header":{"msg_id":"ee1acb62-6643481e261decbbdf60ed9a_22020_54","msg_type":"debug_event","username":"username","session":"ee1acb62-6643481e261decbbdf60ed9a","date":"2024-09-11T14:16:39.665002Z","version":"5.3"},"parent_header":{"date":"2024-09-11T14:16:39.646000Z","msg_id":"b8d29f1f-584f-4d91-8af5-d6c4c7fffe38","msg_type":"debug_request","session":"14ad0216-2c3d-4fec-a9f8-c0830d394fc0","username":"a7fea785-4759-4878-9ff3-e78b019063b0","version":"5.2"},"metadata":{},"content":{"seq":10,"type":"event","event":"thread","body":{"reason":"started","threadId":2}},"idents":[{"type":"Buffer","data":[107,101,114,110,101,108,46,98,54,97,51,52,54,101,57,45,48,54,55,54,45,52,52,55,52,45,57,51,102,98,45,51,50,49,55,53,102,51,50,102,102,100,48,46,100,101,98,117,103,95,101,118,101,110,116]}],"buffers":[],"channel":"iopub"}
22:16:39.669 [debug] [Debug] event: {"header":{"msg_id":"ee1acb62-6643481e261decbbdf60ed9a_22020_55","msg_type":"debug_event","username":"username","session":"ee1acb62-6643481e261decbbdf60ed9a","date":"2024-09-11T14:16:39.665002Z","version":"5.3"},"parent_header":{"date":"2024-09-11T14:16:39.646000Z","msg_id":"b8d29f1f-584f-4d91-8af5-d6c4c7fffe38","msg_type":"debug_request","session":"14ad0216-2c3d-4fec-a9f8-c0830d394fc0","username":"a7fea785-4759-4878-9ff3-e78b019063b0","version":"5.2"},"metadata":{},"content":{"seq":11,"type":"event","event":"thread","body":{"reason":"started","threadId":3}},"idents":[{"type":"Buffer","data":[107,101,114,110,101,108,46,98,54,97,51,52,54,101,57,45,48,54,55,54,45,52,52,55,52,45,57,51,102,98,45,51,50,49,55,53,102,51,50,102,102,100,48,46,100,101,98,117,103,95,101,118,101,110,116]}],"buffers":[],"channel":"iopub"}
22:16:39.669 [debug] [Debug] event: {"header":{"msg_id":"ee1acb62-6643481e261decbbdf60ed9a_22020_56","msg_type":"debug_event","username":"username","session":"ee1acb62-6643481e261decbbdf60ed9a","date":"2024-09-11T14:16:39.665002Z","version":"5.3"},"parent_header":{"date":"2024-09-11T14:16:39.646000Z","msg_id":"b8d29f1f-584f-4d91-8af5-d6c4c7fffe38","msg_type":"debug_request","session":"14ad0216-2c3d-4fec-a9f8-c0830d394fc0","username":"a7fea785-4759-4878-9ff3-e78b019063b0","version":"5.2"},"metadata":{},"content":{"seq":12,"type":"event","event":"thread","body":{"reason":"started","threadId":4}},"idents":[{"type":"Buffer","data":[107,101,114,110,101,108,46,98,54,97,51,52,54,101,57,45,48,54,55,54,45,52,52,55,52,45,57,51,102,98,45,51,50,49,55,53,102,51,50,102,102,100,48,46,100,101,98,117,103,95,101,118,101,110,116]}],"buffers":[],"channel":"iopub"}
22:16:39.670 [debug] [Debug] event: {"header":{"msg_id":"ee1acb62-6643481e261decbbdf60ed9a_22020_57","msg_type":"debug_event","username":"username","session":"ee1acb62-6643481e261decbbdf60ed9a","date":"2024-09-11T14:16:39.666001Z","version":"5.3"},"parent_header":{"date":"2024-09-11T14:16:39.646000Z","msg_id":"b8d29f1f-584f-4d91-8af5-d6c4c7fffe38","msg_type":"debug_request","session":"14ad0216-2c3d-4fec-a9f8-c0830d394fc0","username":"a7fea785-4759-4878-9ff3-e78b019063b0","version":"5.2"},"metadata":{},"content":{"seq":13,"type":"event","event":"thread","body":{"reason":"started","threadId":5}},"idents":[{"type":"Buffer","data":[107,101,114,110,101,108,46,98,54,97,51,52,54,101,57,45,48,54,55,54,45,52,52,55,52,45,57,51,102,98,45,51,50,49,55,53,102,51,50,102,102,100,48,46,100,101,98,117,103,95,101,118,101,110,116]}],"buffers":[],"channel":"iopub"}
22:16:39.670 [debug] [Debug] event: {"header":{"msg_id":"ee1acb62-6643481e261decbbdf60ed9a_22020_58","msg_type":"debug_event","username":"username","session":"ee1acb62-6643481e261decbbdf60ed9a","date":"2024-09-11T14:16:39.666001Z","version":"5.3"},"parent_header":{"date":"2024-09-11T14:16:39.646000Z","msg_id":"b8d29f1f-584f-4d91-8af5-d6c4c7fffe38","msg_type":"debug_request","session":"14ad0216-2c3d-4fec-a9f8-c0830d394fc0","username":"a7fea785-4759-4878-9ff3-e78b019063b0","version":"5.2"},"metadata":{},"content":{"seq":14,"type":"event","event":"thread","body":{"reason":"started","threadId":6}},"idents":[{"type":"Buffer","data":[107,101,114,110,101,108,46,98,54,97,51,52,54,101,57,45,48,54,55,54,45,52,52,55,52,45,57,51,102,98,45,51,50,49,55,53,102,51,50,102,102,100,48,46,100,101,98,117,103,95,101,118,101,110,116]}],"buffers":[],"channel":"iopub"}
22:16:39.696 [debug] [Debug] to kernel: {"command":"setBreakpoints","arguments":{"source":{"name":"test2.ipynb","path":"vscode-notebook-cell:/c%3A/Users/~/Downloads/Jupyter/test2.ipynb#X23sZmlsZQ%3D%3D"},"lines":[3,18,24,27,47],"breakpoints":[{"line":3},{"line":18},{"line":24},{"line":27},{"line":47}],"sourceModified":false},"type":"request","seq":5}
22:16:39.696 [debug] [Debug] to kernel, mapped: {"command":"setBreakpoints","arguments":{"source":{"name":"test2.ipynb","path":"vscode-notebook-cell:/c%3A/Users/~/Downloads/Jupyter/test2.ipynb#X23sZmlsZQ%3D%3D"},"lines":[3,18,24,27,47],"breakpoints":[{"line":3},{"line":18},{"line":24},{"line":27},{"line":47}],"sourceModified":false},"type":"request","seq":5}
22:16:39.696 [debug] [Debug] to kernel: {"command":"setBreakpoints","arguments":{"source":{"name":"test2.ipynb","path":"vscode-notebook-cell:/c%3A/Users/~/Downloads/Jupyter/test2.ipynb#W0sZmlsZQ%3D%3D"},"lines":[2],"breakpoints":[{"line":2}],"sourceModified":false},"type":"request","seq":6}
22:16:39.696 [debug] [Debug] to kernel, mapped: {"command":"setBreakpoints","arguments":{"source":{"name":"test2.ipynb","path":"vscode-notebook-cell:/c%3A/Users/~/Downloads/Jupyter/test2.ipynb#W0sZmlsZQ%3D%3D"},"lines":[2],"breakpoints":[{"line":2}],"sourceModified":false},"type":"request","seq":6}
22:16:39.697 [debug] [Debug] to kernel: {"command":"setBreakpoints","arguments":{"source":{"name":"test2.ipynb","path":"vscode-notebook-cell:/c%3A/Users/~/Downloads/Jupyter/test2.ipynb#W2sZmlsZQ%3D%3D"},"lines":[7],"breakpoints":[{"line":7}],"sourceModified":false},"type":"request","seq":7}
22:16:39.697 [debug] [Debug] to kernel, mapped: {"command":"setBreakpoints","arguments":{"source":{"name":"test2.ipynb","path":"vscode-notebook-cell:/c%3A/Users/~/Downloads/Jupyter/test2.ipynb#W2sZmlsZQ%3D%3D"},"lines":[7],"breakpoints":[{"line":7}],"sourceModified":false},"type":"request","seq":7}
22:16:39.697 [debug] [Debug] to kernel: {"command":"setFunctionBreakpoints","arguments":{"breakpoints":[]},"type":"request","seq":8}
22:16:39.697 [debug] [Debug] to kernel, mapped: {"command":"setFunctionBreakpoints","arguments":{"breakpoints":[]},"type":"request","seq":8}
22:16:39.698 [debug] [Debug] to kernel: {"command":"setExceptionBreakpoints","arguments":{"filters":["uncaught"]},"type":"request","seq":9}
22:16:39.698 [debug] [Debug] to kernel, mapped: {"command":"setExceptionBreakpoints","arguments":{"filters":["uncaught"]},"type":"request","seq":9}
22:16:39.710 [debug] [Debug] response: {"seq":15,"type":"response","request_seq":5,"success":true,"command":"setBreakpoints","body":{"breakpoints":[{"verified":false,"id":0,"message":"Breakpoint in file that does not exist.","source":{"name":"test2.ipynb","path":"vscode-notebook-cell:/c%3A/Users/~/Downloads/Jupyter/test2.ipynb#X23sZmlsZQ%3D%3D"},"line":3},{"verified":false,"id":1,"message":"Breakpoint in file that does not exist.","source":{"name":"test2.ipynb","path":"vscode-notebook-cell:/c%3A/Users/~/Downloads/Jupyter/test2.ipynb#X23sZmlsZQ%3D%3D"},"line":18},{"verified":false,"id":2,"message":"Breakpoint in file that does not exist.","source":{"name":"test2.ipynb","path":"vscode-notebook-cell:/c%3A/Users/~/Downloads/Jupyter/test2.ipynb#X23sZmlsZQ%3D%3D"},"line":24},{"verified":false,"id":3,"message":"Breakpoint in file that does not exist.","source":{"name":"test2.ipynb","path":"vscode-notebook-cell:/c%3A/Users/~/Downloads/Jupyter/test2.ipynb#X23sZmlsZQ%3D%3D"},"line":27},{"verified":false,"id":4,"message":"Breakpoint in file that does not exist.","source":{"name":"test2.ipynb","path":"vscode-notebook-cell:/c%3A/Users/~/Downloads/Jupyter/test2.ipynb#X23sZmlsZQ%3D%3D"},"line":47}]}}
22:16:39.720 [debug] [Debug] response: {"seq":16,"type":"response","request_seq":6,"success":true,"command":"setBreakpoints","body":{"breakpoints":[{"verified":false,"id":5,"message":"Breakpoint in file that does not exist.","source":{"name":"test2.ipynb","path":"vscode-notebook-cell:/c%3A/Users/~/Downloads/Jupyter/test2.ipynb#W0sZmlsZQ%3D%3D"},"line":2}]}}
22:16:39.722 [debug] [Debug] to kernel: {"command":"dumpCell","arguments":{"code":"print()"},"type":"request","seq":10}
22:16:39.722 [debug] [Debug] to kernel, mapped: {"command":"dumpCell","arguments":{"code":"print()"},"type":"request","seq":10}
22:16:39.734 [debug] [Debug] response: {"seq":17,"type":"response","request_seq":7,"success":true,"command":"setBreakpoints","body":{"breakpoints":[{"verified":false,"id":6,"message":"Breakpoint in file that does not exist.","source":{"name":"test2.ipynb","path":"vscode-notebook-cell:/c%3A/Users/~/Downloads/Jupyter/test2.ipynb#W2sZmlsZQ%3D%3D"},"line":7}]}}
22:16:39.740 [debug] [Debug] response: {"seq":18,"type":"response","request_seq":8,"success":true,"command":"setFunctionBreakpoints","body":{"breakpoints":[]}}
22:16:39.744 [debug] [Debug] response: {"seq":19,"type":"response","request_seq":9,"success":true,"command":"setExceptionBreakpoints"}
22:16:39.747 [debug] [Debug] response: {"type":"response","request_seq":10,"success":true,"command":"dumpCell","body":{"sourcePath":"C:\\Users\\~\\AppData\\Local\\Temp\\ipykernel_22020\\3397078413.py"}}
22:16:39.842 [debug] [Debug] to kernel: {"command":"setBreakpoints","arguments":{"source":{"name":"test.ipynb","path":"vscode-notebook-cell:/c%3A/Users/~/Downloads/Jupyter/test.ipynb#W0sZmlsZQ%3D%3D"},"lines":[1],"breakpoints":[{"line":1}],"sourceModified":false},"type":"request","seq":4}
22:16:39.842 [debug] [Debug] to kernel, mapped: {"command":"setBreakpoints","arguments":{"source":{"name":"test.ipynb","path":"C:\\Users\\~\\AppData\\Local\\Temp\\ipykernel_22020\\3397078413.py"},"lines":[1],"breakpoints":[{"line":1}],"sourceModified":false},"type":"request","seq":4}
22:16:39.850 [debug] [Debug] to kernel: {"command":"threads","type":"request","seq":11}
22:16:39.850 [debug] [Debug] to kernel, mapped: {"command":"threads","type":"request","seq":11}
22:16:39.852 [debug] [Debug] response: {"seq":20,"type":"response","request_seq":4,"success":true,"command":"setBreakpoints","body":{"breakpoints":[{"verified":true,"id":7,"source":{"name":"test.ipynb","path":"vscode-notebook-cell:/c%3A/Users/~/Downloads/Jupyter/test.ipynb#W0sZmlsZQ%3D%3D"},"line":1}]}}
22:16:39.858 [debug] [Debug] response: {"seq":21,"type":"response","request_seq":11,"success":true,"command":"threads","body":{"threads":[{"id":1,"name":"MainThread"},{"id":2,"name":"Tornado selector"},{"id":3,"name":"Tornado selector"},{"id":4,"name":"Tornado selector"},{"id":5,"name":"IPythonHistorySavingThread"},{"id":6,"name":"Thread-4"}]}}
22:16:39.878 [trace] Executing silently Code (idle) = import debugpy\ndebugpy.debug_this_thread()
22:16:39.930 [trace] Executing silently Code (completed) = import debugpy\ndebugpy.debug_this_thread() with 0 output(s)
22:16:39.934 [debug] [Debug] to kernel: {"command":"dumpCell","arguments":{"code":"print()"},"type":"request","seq":13}
22:16:39.934 [debug] [Debug] to kernel, mapped: {"command":"dumpCell","arguments":{"code":"print()"},"type":"request","seq":13}
22:16:39.943 [debug] [Debug] response: {"type":"response","request_seq":13,"success":true,"command":"dumpCell","body":{"sourcePath":"C:\\Users\\~\\AppData\\Local\\Temp\\ipykernel_22020\\3397078413.py"}}
22:16:39.966 [debug] [Debug] to kernel: {"command":"configurationDone","type":"request","seq":12}
22:16:39.966 [debug] [Debug] to kernel, mapped: {"command":"configurationDone","type":"request","seq":12}
22:16:39.971 [debug] [Debug] response: {"seq":12,"type":"response","request_seq":12,"success":true,"command":"configurationDone"}
22:16:39.981 [debug] Handle Execution of Cells 0 for ~\Downloads\Jupyter\test.ipynb
22:16:39.982 [trace] Execute Notebook ~\Downloads\Jupyter\test.ipynb. Step 1
22:16:39.982 [trace] Connect to Kernel ~\Downloads\Jupyter\test.ipynb. Step 2
22:16:39.983 [trace] Connected to Kernel ~\Downloads\Jupyter\test.ipynb. Step 3
22:16:39.983 [trace] executeCell 0. Step 4
22:16:39.983 [trace] Cell Index:0 sent to kernel
22:16:39.989 [trace] Start cell 0 execution @<PHONE_NUMBER>989 (clear output)
22:16:39.990 [debug] Kernel acknowledged execution of cell 0 @<PHONE_NUMBER>989
22:16:39.991 [debug] [Debug] to kernel: {"command":"threads","type":"request","seq":14}
22:16:39.991 [debug] [Debug] to kernel, mapped: {"command":"threads","type":"request","seq":14}

Please could you enable logging as follows:

Open settings & go into Jupyter->Logging
Change the value to trace
Reload VS Code,
Attempt to repro the issue & then copy the output from the Jupyter output panel (use the command Jupyter: Show Output to get to the logs).

Please share all of the logs and ensure you minimize activity to just the repro steps.


[Fix] flip_ratio in RandomAffine pipeline is inverted

original: flip_ratio=1. means always no flip and flip_ratio=0. means always flip
after:      flip_ratio=1. means always flip and flip_ratio=0. means always no flip

Because flip is used as a multiplier in line 479 and 480, so -1 stands for flip and 1 stands for no flip. Thus flip should be an 'inverse' flag as the result of the comparison.
Is it correct?

Because flip is used as a multiplier in line 479 and 480, so -1 stands for flip and 1 stands for no flip. Thus flip should be an 'inverse' flag as the result of the comparison.
Is it correct?

Yes, it is.

It seems there is another error. When flipping, the center is shifted.
I made some modifications and added some unit tests, you can have a test to verify.

It seems there is another error. When flipping, the center is shifted. I made some modifications and added some unit tests, you can have a test to verify. I am not sure whether it is related to version of opencv
@wdmwhh, if the modification works, please let me know and I will clean the code and merge this PR.

Yes, it makes sense. Thanks for your kindness.


CSS Units

Problem Statement

There is currently not a CSS unit calculator or any conversions available. You have to use some other tool or website to convert CSS units or to view a reference table. Or use equivalent values to calculate yourself. My first thought was to check to see if the calculator could do these since I know it can perform other unit conversions.
Having this functionality could also be an attraction for designers/developers as a native unit conversion/calculator tool. It certainly would be nice to have instead of using an obscure method to get the conversion/calculation.
Evidence or User Insights

When needing convert point units to pixels because some other design tool doesn't currently support point for whatever reason.
Or if you are working in design software that doesn't support REM and EM units and want to get 1.875rem of 16px. I know you can just do this as a 16*1.875=30. But that is only for relative units. For absolute units you have to convert PT to a common unit value like IN and then convert that value to PX.
Proposal

Have a converter for all of the absolute CSS units
Have a calculator for all of the relative CSS units
https://developer.mozilla.org/en-US/docs/Learn/CSS/Building_blocks/Values_and_units#numbers_lengths_and_percentages
Example tool: https://pixelsconverter.com/px-to-rem
Goals

User can convert PT to IN
User can convert PT to PX
And everything in-between
Non-Goals

Low-Fidelity Concept

Requested Assignment

I'm just suggesting this idea.  I don't want to implement it.

This is your friendly Microsoft Issue Bot. I've seen this issue come in and have gone to tell a human about it.


fluxcd: 0.8.1 -> 0.8.2

Motivation for this change
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

Result of nixpkgs-review pr 113698 at 8fbe61b9 run on x86_64-linux 1

1 package built:

fluxcd

1 suggestion:

error: no-flags-array
buildFlagsArray is only intended to be used in Bash, not as a Nix attribute.
Near pkgs/applications/networking/cluster/fluxcd/default.nix:22:3:
   |
22 |   buildFlagsArray = [ "-ldflags=-s -w -X main.VERSION=${version}" ];
   |   ^


Count nodes during search

Moves made
Transposition table hits
Evaluate calls
Add nodes (moves made) to UCI info output

Codecov Report

Merging #80 (4eca1cd) into main (886f6fc) will decrease coverage by 0.11%.
The diff coverage is 87.50%.

@@            Coverage Diff             @@
##             main      #80      +/-   ##
==========================================
- Coverage   97.00%   96.89%   -0.12%
==========================================
  Files          61       62       +1
  Lines        6272     6336      +64
==========================================
+ Hits         6084     6139      +55
- Misses        188      197       +9

Impacted Files
Coverage Δ

search/src/node_counter.rs
73.52% <73.52%> (ø)

search/src/alpha_beta.rs
100.00% <100.00%> (ø)

search/src/negamax.rs
97.36% <100.00%> (+0.30%)
:arrow_up:

search/src/search.rs
82.75% <100.00%> (+3.59%)
:arrow_up:

search/tests/search.rs
83.19% <100.00%> (+0.14%)
:arrow_up:

uci/src/uci_out/info.rs
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Classification evaluation for LLaVA

Hi, currently, the code throws a NotImplementedError for LLaVA, but I believe the paper demonstrates zero-shot classification on LLaVA. When will the code be updated to include this feature? Alternatively, could you point out the main parts that would need significant changes to incorporate LLaVA?
Thank you.

Hi, thanks for asking. We demonstrate zero-shot classification only for the CLIP models on their own and consider LLaVA and OpenFlamingo for captioning/VQA tasks.

Thank you for the clarification. I have another question: Why is the batch size hardcoded to 1? Is it just to avoid padding text tokens?

You're right, it should definitely be possible to run with larger batch sizes, it's just hardcoded to batch_size 1 in a few places since we couldn't fit much more on our devices anyway for adversarial evaluations

Hi, thank you so much for clarifying everything. Just one last question: does the code use beam search to generate the outputs?

Hi, thank you so much for clarifying everything. Just one last question: does the code use beam search to generate the outputs?

No problem :) We basically stick to how the models are evaluated in their respective papers, so greedy decoding without beam-search for LLaVA, and beam search with 3 beams for OpenFlamingo.


Add typing info

https://docs.python.org/3/library/typing.html

https://mypy.readthedocs.io/en/stable/stubs.html
https://mypy.readthedocs.io/en/stable/command_line.html#report-generation
https://typing.readthedocs.io/en/latest/source/stubs.html#syntax
https://typing.readthedocs.io/en/latest/source/quality.html
https://github.com/microsoft/pyright/blob/main/docs/typed-libraries.md

https://github.com/emacs-lsp/lsp-pyright/issues/80

https://github.com/emacs-lsp/lsp-pyright/issues/85


Group related issues: solutions about incremental development in MetaGPT

Issues

#1436
#1379
#1210
#1095
#972
#871
#333

Bug solved method
The previous incremental software development method based on SOP has several issues:

Inconvenient human-computer interaction. New user requirements, technical demands, bug fixes, and added design constraints are difficult to directly correspond to the relevant SOP steps for operation.
Inflexible programming languages. The same design cannot be easily switched to different programming languages, mixed-language programming is not supported, and design solutions cannot be reused.

To address this, we propose a more practical solution.
It is an upgraded version of DI (Data Interpreter) called RoleZero, which will be released soon. It adopts the following methods to handle software development issues with real-time human-computer interaction:

Generate sequence diagrams from requirements. This compresses the content size of requirement descriptions and supports flexible changes in requirements and switching between programming languages.
Generate code from sequence diagrams rather than directly from user requirements. This approach supports design outputs reuse, can flexibly generate code in different languages, allows for additional technical requirements during code generation (such as which packages must be used, how interfaces should be utilized, etc.), and supports mixed programming languages.
Bug modifications can be implemented through human-computer interaction, directly targeting specific files.
Regarding the coding of the UI, you can use RoleZero to convert UI pictures into code, and then merge them into the backend code generated based on the sequence diagrams through human-computer interaction.

Design Outputs Demo
Here is an example of a sequence diagram generated by RoleZero based on real software development requirements giving a user requirement PDF file and an external system interface usage PDF file, to help everyone understand RoleZero's capabilities in interpreting requirements.

Subsequent issues related to new requirements or bug fixes will be consolidated under this issue for further follow-up.

although PDF is a awesome file/document format, I personally think a json or etc would be better.
Because I am scared that the pdf parser could be too complex to use/maintain (especially compatibility).
PDF is originally by adobe,so i think we must make sure the save format is https://www.iso.org/standard/75839.html
But,it's at least better than docx or .yaml.
I think we are heading to the right direction.But, this seems to only showcase the legal SOP situation with systeminterfaceusage..pdf ?

We choose to use PDF because in reality, most software requirements are archived and transferred using docx or PDF documents, so this is an adjustment based on the real-world situation.

although PDF is a awesome file/document format, I personally think a json or etc would be better.
Because I am scared that the pdf parser could be too complex to use/maintain (especially compatibility).
PDF is originally by adobe,so i think we must make sure the save format is https://www.iso.org/standard/75839.html
But,it's at least better than docx or .yaml.
I think we are heading to the right direction.But, this seems to only showcase the legal SOP situation with systeminterfaceusage..pdf ?

i see. will wait for the release and test it out.


New procedures needed in Codeunit 730 "Copy Item"

Hi Team,
The new Copy Item function with page 729 and codeunit 730 are pretty cool and easy to increase with own tables. But I need the possibility to copy an item out from own al-code and in my opinion two global procedures are missing in the codeunit 730:
    // First function to fill in all needed information to the CopyItemBuffer
    procedure SetCopyItemBuffer(var NewCopyItemBuffer: Record "Copy Item Buffer" temporary)
    begin
        CopyItemBuffer := NewCopyItemBuffer;
        SourceItem.Get(CopyItemBuffer."Source Item No.");
    end;

    // Second function to get the item numbers of the created items out from the codeunit, after the procedure CopyItem() was called
    procedure GetNewItemNo(var NewFirstItemNo: Code[20]; var NewLastItemNo: Code[20])
    begin
        NewFirstItemNo := FirstItemNo;
        NewLastItemNo := LastItemNo;
    end;

Thanks in advance!

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.