ng serve does not detect changes in routes

Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
Windows 8.1

Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:

angular-cli: 1.0.0-beta.26
node: 6.9.5
os: win32 x64
@angular/common: 2.4.5
@angular/compiler: 2.4.5
@angular/core: 2.4.5
@angular/forms: 2.4.5
@angular/http: 2.4.5
@angular/platform-browser: 2.4.5
@angular/platform-browser-dynamic: 2.4.5
@angular/router: 3.4.5
@angular/compiler-cli: 2.4.5
Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.

Added a new route in a working module:
const routes: Routes = [
{path: 'travesses', component: TravessesComponent},
{path: 'peres', component: TravessesComponent} <= this is the new one
];
The log given by the failure.

Normally this include a stack trace and some more information.

webpack: Compiling...
Hash: 1cb8464dd62798771354
Time: 476ms
chunk    {0} main.bundle.js, main.bundle.map (main) 11.4 kB {2} [initial] [rendered]
chunk    {1} styles.bundle.js, styles.bundle.map (styles) 9.96 kB {3} [initial]
chunk    {2} vendor.bundle.js, vendor.bundle.map (vendor) 3.16 MB [initial]
chunk    {3} inline.bundle.js, inline.bundle.map (inline) 0 bytes [entry]
webpack: Compiled successfully.
Accessing the route gets:
EXCEPTION: Uncaught (in promise): Error: Cannot match any routes. URL Segment: 'peres'
Error: Cannot match any routes. URL Segment: 'peres'
at ApplyRedirects.noMatchError (http://localhost:4200/vendor.bundle.js:85516:16) [angular]
at CatchSubscriber.selector (http://localhost:4200/vendor.bundle.js:85485:29) [angular]
at CatchSubscriber.error (http://localhost:4200/vendor.bundle.js:68724:31) [angular]
at MapSubscriber.Subscriber._error (http://localhost:4200/vendor.bundle.js:6711:26) [angular]
at MapSubscriber.Subscriber.error (http://localhost:4200/vendor.bundle.js:6685:18) [angular]
at MapSubscriber.Subscriber._error (http://localhost:4200/vendor.bundle.js:6711:26) [angular]
at MapSubscriber.Subscriber.error (http://localhost:4200/vendor.bundle.js:6685:18) [angular]
at MapSubscriber.Subscriber._error (http://localhost:4200/vendor.bundle.js:6711:26) [angular]
at MapSubscriber.Subscriber.error (http://localhost:4200/vendor.bundle.js:6685:18) [angular]
at LastSubscriber.Subscriber._error (http://localhost:4200/vendor.bundle.js:6711:26) [angular]
at LastSubscriber.Subscriber.error (http://localhost:4200/vendor.bundle.js:6685:18) [angular]
at MergeAllSubscriber.OuterSubscriber.notifyError (http://localhost:4200/vendor.bundle.js:48223:26) [angular]
at InnerSubscriber._error (http://localhost:4200/vendor.bundle.js:91572:21) [angular]
at InnerSubscriber.Subscriber.error (http://localhost:4200/vendor.bundle.js:6685:18) [angular]
Mention any other details that might be useful.
After stopping ng serve and launching it again the route works as expected.

Thanks! We'll be in touch soon.

Same as #4338

DUP of #4338 as stated above:
Please install<EMAIL_ADDRESS>to fix this issue.

It doesn't work with<EMAIL_ADDRESS>With<EMAIL_ADDRESS>it works fine.

By me its not detecting changes to all .ts files.
Solved with installing<EMAIL_ADDRESS>

Did anyone try the fix "installing<EMAIL_ADDRESS>with hot module reloading?
It doesnt work well for me.. it refreshes the page anyway..

i tried, but it crashed the project, also tried "exclude": "node_modules" in the config...
i did not try the inotify thing, as my memory is already almost at its limit (webstorm taking 1-2gb).


#54 implement CDDP  AI assistant over Streamlit page

Implement CDDP  AI assistant over Streamlit page, added below features.

Generate tables for given industry.
Generate sample data for given table.
Generate data processing logic for transformation and serving zones.

This PR has been outdated, please check below latest one instead.
https://github.com/Azure/config-driven-data-pipeline/pull/62


Scale missing transform property

Version
@nuxtjs/tailwindcss: 4.2.0
nuxt: 2.15.7
Reproduction Link
https://codesandbox.io/s/frosty-forest-rohzeb?file=/pages/index.vue
Steps to reproduce

Add scale-0 to any div
What is Expected?
transform: translate(var(--tw-translate-x), var(--tw-translate-y)) rotate(var(--tw-rotate)) skewX(var(--tw-skew-x)) skewY(var(--tw-skew-y)) scaleX(var(--tw-scale-x)) scaleY(var(--tw-scale-y));
What is actually happening?
transform property is missing in
.scale-0 class
and also in other scale classes

Closing this issue as it is believed to be resolved/stale now - please feel free to comment if it is still an issue in the latest version of the module.


Deploy coar-notify-inbox kustomization to the prod environment

Available at: https://inbox-sciety-prod.elifesciences.org/

To limit access, the nginx.ingress.kubernetes.io/whitelist-source-range annotation for Ingresses might be too strong.
nginx.ingress.kubernetes.io/configuration-snippet could give us flexibility such as stopping POST requests only.

Possible solution using the nginx access module, see also https://serverfault.com/questions/840342/allowing-post-requests-from-a-single-ip-address-only-on-nginx?


Support Pydantic v2.x and up

Proposed Changes
This PR addresses the warnings generated by any software using python-tailscale with Pydantic v2 or newer, and prepares it for Pydantic v3, by replacing usages of the (deprecated and will be removed in v3) @validator(..., pre=True) decorator with the replacement, @field_validator(..., mode="before").
Pydantic v2 support was added automatically by dependabot but I assume no new release was issued on PyPI due to the warnings it generated. The current version of python-tailscale on PyPI does not support Pydantic v2.
Related Issues
Pydantic v2 was included via PRs #367, #369, #370, #377, #384, #393 and (open) #396

Codecov Report

Merging #400 (fca8a2c) into main (a34c1c1) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #400   +/-   ##
=======================================
  Coverage   91.74%   91.74%
=======================================
  Files           4        4
  Lines         109      109
  Branches        8        8
=======================================
  Hits          100      100
  Misses          8        8
  Partials        1        1

Files Changed
Coverage Δ

src/tailscale/models.py
92.15% <100.00%> (ø)

I need to support v1 as well 👍

I'll see if I can maintain v1 compatibility with this. I noticed there are other changes in Pydantic v2 that cause real-world usage of python-tailscale to break, which aren't covered by unit tests, so I'll also sort that out in this PR.


Install in laravel 5.3

Laravel Version: 5.3.31
PHP Version:5.6.3

Description:
I want to install voyager in my laravel project, but it installed fail.
It always return error message: Installation failed, reverting ./composer.json to its original content.
How do I do?
Steps To Reproduce:

@devil19891025 this package is for only compatible with Laravel 5.4 and above. There's even a note before the installation steps that clearly says so.
Laravel Admin & BREAD System (Browse, Read, Edit, Add, & Delete), supporting Laravel 5.4 and newer!


User Payload in workflow step edit

Description
Describe your issue here.
Trying to restrict app steps to specific users in their workflows.
Following the Legacy workflow steps : https://slack.dev/bolt-js/concepts#adding-editing-steps , the documentation suggests "your app will receive a workflow_step_edit event" but when i debug the step variable in the edit method, only the workflow_step object and output array is returned.
How can I get user information in this method?
What type of issue is this? (place an x in one of the [ ])

[ ] bug
[ ] enhancement (feature request)
[x] question
[ ] documentation related
[ ] example code related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

I want to use the user info as logic in my function in production, would this still help and how do i do it?

@himanshu1sharma - I see, thanks for that clarification! Are you able to use the body argument within your edit callback for that purpose? I believe that you should see the more full event body that is shown here that way as opposed to just the workflow step object.
const ws = new WorkflowStep('add_task', {
  edit: async ({ ack, step, body, configure }) => {
    await ack();

// use the body here!
...
```

This works...Many thanks @srajiang!

The Solution was to add the body param to the function, like @srajiang suggest above :
`const ws = new WorkflowStep('add_task', {
edit: async ({ ack, step, body, configure }) => {
await ack();
// use the body here!`


Store QueryState in Query as a Cow and remove distinct QueryLens type

Objective
The QueryLens type is basically a Query, except it stores the QueryState itself rather than a reference to it. We can unify Query and QueryLens by allowing Query to hold either a reference or a value, which Cow provides. As a byproduct, we can also now also return Querys from World::query, rather than QueryStates.
Solution
The following changes have been made:

QueryState can now be Cloned (required by Cow)

All WorldQuery::State types are now required to be Clone.

Functions on Query returning 's have been replaced with '_.
The current World::query/World::query_filtered functions have been renamed to World::query_state/World::query_state_filtered.
New World::query/World::query_filtered functions have been added that return Query instead of QueryState.
New type conversions have been added:

Query<D, F>::into_state(self) -> QueryState<D, F> (clones the state if it was borrowed)
QueryState<D, F>::as_query(&mut self, &mut World) -> Query<D, F>
QueryState<D, F>::as_readonly_query(&self, &World) -> Query<D::ReadOnly, F>
QueryState<D, F>::into_query(self, &mut World) -> Query<D, F>
QueryState<D, F>::into_readonly_query(self, &World) -> Query<D::ReadOnly, F>
QueryState<D, F>::into_readonly(self) -> QueryState<D::ReadOnly, F>

Similar to QueryState::as_readonly, but by value instead of by reference.

The QueryLens type has been removed. Query can function exactly like it.

Query::transmute_lens_filtered(&mut self) -> QueryLens changed to Query::transmute_filtered(&mut self) -> Query
Query::transmute_lens(&mut self) -> QueryLens changed to Query::transmute(&mut self) -> Query
Query::join(&mut self, other: &mut Query) -> QueryLens changed to Query::join(&mut self, other: &mut Query) -> Query
Query::join_filtered(&mut self, other: &mut Query) -> QueryLens changed to Query::join_filtered(&mut self, other: &mut Query) -> Query

The state structs for QueryData/QueryFilter derives now impl Clone.

Testing

Current tests pass.
TODO: change compile fail test for query lens.

Showcase
TODO?
Migration Guide

QueryLens usages should be replaced with Query.

Query::transmute_lens_filtered(&mut self) -> QueryLens changed to Query::transmute_filtered(&mut self) -> Query
Query::transmute_lens(&mut self) -> QueryLens changed to Query::transmute(&mut self) -> Query
Query::join(&mut self, other: &mut Query) -> QueryLens changed to Query::join(&mut self, other: &mut Query) -> Query
Query::join_filtered(&mut self, other: &mut Query) -> QueryLens changed to Query::join_filtered(&mut self, other: &mut Query) -> Query

All WorldQuery::State types are now required to implement Clone.
The old World::query and World::query_filtered functions were renamed to World::query_state and World::query_state_filtered, respectively.
Query functions returning data with a 's now return '_, i.e. the query state lifetime is now bound by the Query instance rather than the contained QueryState.

The old World::query and World::query_filtered functions were renamed to World::query_state and World::query_state_filtered, respectively.

It's probably worth moving this change to a separate pr. Makes this pr a bit hard to review.

Going to take a different approach to merging Query and QueryLens instead after I finish up some other stuff, if nobody else gets to it first.


Minimize to tray on startup.Fix issue #565

What's this PR do?
This commit fixes issue #565 by choosing to hide window instead of minimize when asked.Also 2 process were checking whether to minimize the app on start or not.This PR also removes one of the function.
You have tested this PR on:

[X] Windows
[ ] Linux/Ubuntu
[ ] macOS

@ThePiyushGupta looks good though you should follow the commit guidelines. For an example, the commit message could be -

setting: Minimize to tray on startup.
Fixes: #565.

For inspirations, check out other commit messages here -
https://github.com/zulip/zulip-electron/commits/master
https://github.com/zulip/zulip/commits/master

Merged. Thanks, @ThePiyushGupta.

@akashnimare Thanks for advice I'll keep it in mind next time.


Full repo review

Attempting to create a review of the entire repo in one go with all files added.
(probably following the same recipe as PR #6 but on that one I can only see some files added, not all)

I don't see a LICENSE file on this repo, but it is Public so right now anyone can grab it and claim it as their own... or something...
Do we know what license this should eventually be? If not, then perhaps we should slap something on it until we can hand it over - since we own the copyright entirely (only OSL contributions) we can always change it later to whatever the client want.

OK, I think that's me done code-reviewing 😅
In summary my above comments can probably be distilled down to a few points:

use asynPrint in the asyn driver and avoid printf, cout, etc. unless you have no other choice (i.e. before asyn port is created)
Use epicsEvent to signal/wait for synchronisation between threads instead of while(boolean)
Consistent error handling: either return error codes OR throw exception, not both. Bonus point for error codes that have meaning...

Finally, I think a refactor is in order: right now everything is the asynPortDriver class. However, many functions really only deal with handling, parsing, or in some form working with the PLC tags and have no EPICS or asyn in them. These would benefit from being pulled out into a separate class PlcTagParsingAndManipulationOrSomething - which could then benefit from going through unittesting since these functions are nontrivial.
I'm thinking these functions might all not need to be in the asynPortDriver class:
  asynStatus loadStructFile(const char * portName, const char * filePath);
  asynStatus createStructMap(std::unordered_map<std::string, std::vector<std::string>> rawMap);
  std::vector<std::string> expandStructs(std::unordered_map<std::string, std::vector<std::string>> const& rawMap, std::string structName);
  size_t findOffsetsRecursive(std::unordered_map<std::string, std::vector<std::string>> const& rawMap, std::unordered_map<std::string, std::vector<std::string>> const& expandedMap, std::string structName, std::unordered_map<std::string, std::vector<int>>& structMap, std::string parentNextDtype);
  std::string findNextDtype(std::unordered_map<std::string, std::vector<std::string>> const& rawMap, std::string structName);
  std::unordered_map<std::string, std::string> drvInfoParser(const char *drvInfo);


SIM800 GSM module

Can this be ported to use on a SIM800 GSM module, to send directly to the cloud using GSM?

https://github.com/knolleary/pubsubclient/issues/88


Support linguijs

Is best if this can support https://lingui.dev/
Thanks author.

I'm not sure I understand. Is there an issue you're running into specifically when trying to use lingui?
This library is agnostic to what i18n library you use. It doesn't matter if you want to use react-intl, lingui, i18next, etc... The next-i18n-router library simply provides internationalized routing. Nothing more. If lingui.js works in Next.js, then you can certainly use it with this library.
I know right now we only have an example for react-intl integration, but we will be adding more examples for other i18n libraries in the near future! We also welcome anyone to make a PR into our examples folder with other library integrations.

Going to close this one since all i18n libraries are inherently supported.


Keyboard shortcuts

Is your feature request related to a problem? Please describe.
Obsidian gives you hints on commands (Ctrl+N for a new document!) but there are no keyboard shortcuts, making navigating less optimal than on Desktop
Describe the solution you'd like
I am not sure if a Alt+Shift+Key format is ideal or something custom akin to Github's keyboard shortcuts https://docs.github.com/en/get-started/using-github/keyboard-shortcuts

https://github.com/k0kubun/xremap ?


Add PVTv2 backbone to RetinaNet

This PR adds Pyramid Vision Transformer v2 backbone to the RetinaNet model.
Configs and weights from mmdet repo
https://github.com/open-mmlab/mmdetection/tree/master/configs/pvt

Hey @dnth,
I just wanted to confirm this PR is aligned with the structure that we design during our call.
I have the impression the answer is Yes. In that case, I can merged it!

Hey @dnth,
I just wanted to confirm this PR is aligned with the structure that we designed during our call.
I have the impression the answer is Yes. In that case, I can merged it!

Now it is!

COCO Metric for RetinaNet with PVTv2 B3 backbone

To use PVT backbone we must update to mmdet==2.20.0. However this causes a problem with VFNet models.


Improve token search performance

Description

Removed extraneous loading prop
First keypress on search input caused UI to freeze for ~3 seconds. Removed nested loops from mapTokenListTokens.

Type of change

[x] Code refactor / cleanup

How should this be tested?
Please provide instructions so we can test. Please also list any relevant details for your test configuration.

Go to home page
Click "Filter by token" button
Start typing to token search
Token list should update immediately

Visual Context
First keypress event run time dropped from 3.38s to 43ms

Before
Now

Checklist:

[x] I have performed a self-review of my own code
[x] I have requested at least 2 reviews (If the PR is significant enough, use best judgement here)
[x] I have commented my code where relevant, particularly in hard-to-understand areas
[x] If package-lock.json has changes, it was intentional.
[x] The base of this PR is master if hotfix, develop if not

@sssmi In terms of the performance improvement – this is outstanding!


[Housekeeping] Namespace Testing Library

Description
This renames the namespace from com.hello.curiosity to io.github.hellocuriosity in preparation for publishing on maven central #94.
Review checklist

[x] PR is split into meaningful commits for the ease of reviewing
[ ] Tests have been written
[ ] Screenshots added (where applicable)
[x] Appropriate labels have been applied

Codecov Report

Merging #106 (e2e798b) into main (5cfd71b) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##            main    #106   +/-   ##
=====================================
  Coverage   76.3%   76.3%
=====================================
  Files         45      45
  Lines       1344    1344
  Branches     386     386
=====================================
  Hits        1026    1026
  Misses       118     118
  Partials     200     200


Change to Swift 2.2

Hello,i notice there are some codes that may be out of date.So i change to the swift 2.2.

Out of date, closing.


ops.deform_conv2d causes CUDA illegal memory access

🐛 Bug
I try to test the speed of deformable conv2d. But always encountered memory error.
To Reproduce
$ ipython
Python 3.8.5 (default, Jul 27 2020, 08:42:51)
Type 'copyright', 'credits' or 'license' for more information
IPython 7.17.0 -- An enhanced Interactive Python. Type '?' for help.

In [1]: import torch
   ...: import torchvision as tv
   ...: weight = torch.randn(9,9,3,3).cuda()
   ...: weight.requires_grad = True
   ...: img = torch.randn(8, 9, 1000, 110).cuda()
   ...: def test():
   ...:     offset = torch.randn(8,18,1000,110).cuda()
   ...:     out = tv.ops.deform_conv2d(img, offset, weight, padding=1)
   ...:     out.mean().backward()
   ...:

In [2]: import os

In [3]: os.environ["CUDA_LAUNCH_BLOCKING"] = "1"

In [4]: timeit test()
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
<ipython-input-4-a1086d7a4706> in <module>
----> 1 get_ipython().run_line_magic('timeit', 'test()')

/usr/lib/python3.8/site-packages/IPython/core/interactiveshell.py in run_line_magic(self, magic_name, line, _stack_depth)
   2324                 kwargs['local_ns'] = self.get_local_scope(stack_depth)
   2325             with self.builtin_trap:
-> 2326                 result = fn(*args, **kwargs)
   2327             return result
   2328

<decorator-gen-60> in timeit(self, line, cell, local_ns)

/usr/lib/python3.8/site-packages/IPython/core/magic.py in <lambda>(f, *a, **k)
    185     # but it's overkill for just that one bit of state.
    186     def magic_deco(arg):
--> 187         call = lambda f, *a, **k: f(*a, **k)
    188
    189         if callable(arg):

/usr/lib/python3.8/site-packages/IPython/core/magics/execution.py in timeit(self, line, cell, local_ns)
   1171                     break
   1172
-> 1173         all_runs = timer.repeat(repeat, number)
   1174         best = min(all_runs) / number
   1175         worst = max(all_runs) / number

/usr/lib/python3.8/timeit.py in repeat(self, repeat, number)
    203         r = []
    204         for i in range(repeat):
--> 205             t = self.timeit(number)
    206             r.append(t)
    207         return r

/usr/lib/python3.8/site-packages/IPython/core/magics/execution.py in timeit(self, number)
    167         gc.disable()
    168         try:
--> 169             timing = self.inner(it, self.timer)
    170         finally:
    171             if gcold:

<magic-timeit> in inner(_it, _timer)

<ipython-input-1-a97200bb984a> in test()
      5 img = torch.randn(8, 9, 1000, 110).cuda()
      6 def test():
----> 7     offset = torch.randn(8,18,1000,110).cuda()
      8     out = tv.ops.deform_conv2d(img, offset, weight, padding=1)
      9     out.mean().backward()

RuntimeError: CUDA error: an illegal memory access was encountered

In [5]:

Environment
PyTorch version: 1.6.0
Is debug build: False
CUDA used to build PyTorch: 11.0
OS: Arch Linux (x86_64)
GCC version: (GCC) 10.1.0
Clang version: 10.0.1
CMake version: version 3.18.1
Python version: 3.8 (64-bit runtime)
Is CUDA available: True
CUDA runtime version: 11.0.2
GPU models and configuration: GPU 0: GeForce GTX 1050 Ti
Nvidia driver version: 450.57
cuDNN version: Probably one of the following:
/usr/lib/libcudnn.so.8.0.2
/usr/lib/libcudnn_adv_infer.so.8.0.2
/usr/lib/libcudnn_adv_train.so.8.0.2
/usr/lib/libcudnn_cnn_infer.so.8.0.2
/usr/lib/libcudnn_cnn_train.so.8.0.2
/usr/lib/libcudnn_ops_infer.so.8.0.2
/usr/lib/libcudnn_ops_train.so.8.0.2
Versions of relevant libraries:
[pip3] numpy==1.19.1
[pip3] torch==1.6.0
[pip3] torch-cluster==1.4.5
[pip3] torch-geometric==1.3.2
[pip3] torch-scatter==1.4.0
[pip3] torch-sparse==0.4.3
[pip3] torchvision==0.7.0a0
[conda] Could not collect

Hi,
Thanks for the report.
I just tried your snippet on my machine (using PyTorch 1.7.0.dev20200727 and torchvision from source id 0.8.0a0+1aef87d) and it worked fine.
Can you double-check that the version of PyTorch and torchvision that you are using in your Python interpreter are indeed 1.6.0 and 0.7.0 ? The 0.7.0a0 is a bit suspicious, and is maybe an RC candidate for torchvision.

That's weired.
I changed a machine and used a nightly build. But still has the same problem.
Collecting environment information...
PyTorch version: 1.7.0.dev20200819
Is debug build: False
CUDA used to build PyTorch: 10.2
OS: Arch Linux (x86_64)
GCC version: (GCC) 10.1.0
Clang version: 10.0.1
CMake version: version 3.18.1
Python version: 3.8 (64-bit runtime)
Is CUDA available: True
CUDA runtime version: 11.0.194
GPU models and configuration: GPU 0: GeForce GTX 1080 Ti
Nvidia driver version: 450.57
cuDNN version: Probably one of the following:
/usr/lib/libcudnn.so.8.0.2
/usr/lib/libcudnn_adv_infer.so.8.0.2
/usr/lib/libcudnn_adv_train.so.8.0.2
/usr/lib/libcudnn_cnn_infer.so.8.0.2
/usr/lib/libcudnn_cnn_train.so.8.0.2
/usr/lib/libcudnn_ops_infer.so.8.0.2
/usr/lib/libcudnn_ops_train.so.8.0.2
Versions of relevant libraries:
[pip3] numpy==1.19.1
[pip3] torch==1.7.0.dev20200819
[pip3] torch-cluster==1.4.5
[pip3] torch-geometric==1.3.2
[pip3] torch-scatter==1.4.0
[pip3] torch-sparse==0.4.3
[pip3] torchvision==0.8.0.dev20200820
[conda] Could not collect

However, if i set the Batch size of test data to 1, everything is fine.

This is what I tried. The only difference was that I set requires_grad inside tensor creation (this was an experiment on CPU, I also tried one on CUDA)
In [1]: import torch

In [2]: import torchvision as tv

In [3]: weight = torch.randn(9,9,3,3, requires_grad=True)

In [4]: img = torch.randn(8, 9, 20, 30)

In [5]: def test():
   ...:     offset = torch.randn(8,18,20,30)
   ...:     out = tv.ops.deform_conv2d(img, offset, weight, padding=1)
   ...:     out.mean().backward()
   ...:

In [6]: test()

In [7]: test()

In [8]: test()

In [9]: test()

In [10]: test()

In [11]: test()

@vfdev-5 can you try seeing if you can reproduce this issue?

@fmassa @godspeed1989 I could reproduce the exception on CUDA by calling twice test()
import torch
import torchvision as tv

print(torch.__version__, tv.__version__, torch.version.cuda)

weight = torch.randn(9,9,3,3).cuda()
weight.requires_grad = True
img = torch.randn(8, 9, 1000, 110).cuda()

def test():
    offset = torch.randn(8,18,c).cuda()
    out = tv.ops.deform_conv2d(img, offset, weight, padding=1)
    out.mean().backward()

import os
os.environ["CUDA_LAUNCH_BLOCKING"] = "1"

test()
test()

> 1.6.0 0.7.0 10.2
> RuntimeError: CUDA error: an illegal memory access was encountered

Seems like error is input size dependent (no error with 110x110 input) and if we comment out out.mean().backward() code runs without any issue event with timeit.

@ngimel thanks a lot for the example of how to fetch max grid size !

I use the latest torchvision and compliled it as torchvision-0.8.0a0+ac3ba94-cp38-cp38-linux_x86_64.whl.
But I still encounter the illegal memory access problem after several hours of training.

The training of my model is fine before I modified several traditional conv layers to deform conv.
Can anyone provide some advice to deal with such a problem?

@godspeed1989 maybe some Nans appeared... It is difficult to say like that. Can you give more details and maybe a repreducible code snippet ? That would help

@vfdev-5 Thanks for replying. I trained the model last night again and encountered the same issues that happened in optimizer.step().

Here is the code snippet about how i use deform conv
class MASConv_deform(nn.Module):
    # Convolution layer for sparse data
    def __init__(self, in_channels, out_channels, stride=1, bias=True):
        super(MASConv_deform, self).__init__()
        self.stride = stride

        self.off_conv = nn.Conv2d(in_channels, 18, 3, 2, 1, bias=False)
        nn.init.constant_(self.off_conv.weight, 0)
        self.off_conv.register_backward_hook(self._set_lr)

        self.conv = tv.ops.DeformConv2d(in_channels, out_channels, 3,
            stride=stride, padding=1, dilation=1, bias=False)

    @staticmethod
    def _set_lr(module, grad_input, grad_output):
        grad_input = (grad_input[i] * 0.1 for i in range(len(grad_input)))
        grad_output = (grad_output[i] * 0.1 for i in range(len(grad_output)))

    def forward(self, x):
        offset = self.off_conv(x)
        x = self.conv(x, offset)
        return x

I think it is hard to reproduce as it happens after several hours of training.
And can you provide some advice about how to avoid Nans in training?

@godspeed1989 can you provide more info about what model(s) and how you are training with which hyperparameters (lr, lr scheduling etc) ? If I could have this info I could try to launch the training from my side and reproduce the issue ...
What is the purpose of
    @staticmethod
    def _set_lr(module, grad_input, grad_output):
        grad_input = (grad_input[i] * 0.1 for i in range(len(grad_input)))
        grad_output = (grad_output[i] * 0.1 for i in range(len(grad_output)))

According to the images you provided, it looks like the error can happen on 0th or 1st epoch ? So, it could go over the complete dataset without any issue, right ?

I sorry I can't provide the model to you as it is related to an unpublished paper and still under development.
The learning_rate is 1e-3, optimizer is Adam, the weight_decay is 0.
It can go over the dataset at my 2nd attempt.
Now, I am trying to detect if the NaN happens to loss by torch.isnan(). It still fine now.

I sorry I can't provide the model to you as it is related to an unpublished paper and still under development.

@godspeed1989 no worries about that. The dataset is something knowm I assume and there is no corrupted data etc...
Can you check a training mode like overfitting 1-2 batches to see if you model converges etc ?

Unfortunately, the program still crashed at the 2nd epoch with the same issue. :(
The evaluation is performed after each epoch on validation set, the model seems converged fine.
May be i should switch to SGD to train it.

Unfortunately, the program still crashed at the 2nd epoch with the same issue. :(
The evaluation is performed after each epoch on validation set, the model seems converged fine.

@godspeed1989 No, I mean reduce the size of your training dataloader to 1-2 batches and try to overfit the model during ~1000 iterations and let's see if it also crashes somewhere and whether it is related to the data somehow...

I reduce the size of your training dataloader to 1 batch and train 20000 iterations. The program has finished fine now.

Is there any plan to fix this bug? I'm still seeing it above a certain batch size. I assumed this was a manifestation of an out of memory error but I can see that at the largest batch size that works I'm only using 50% of the available GPU memory.

@Queuecumber can you provide a code snippet to reproduce your bug ?
Original bug with deform_conv2d was fixed. Thanks

This is what I'm using:
class ModulatedDeformConvPack(DeformConv2d):
    def __init__(self, *args, **kwargs):
        super(ModulatedDeformConvPack, self).__init__(*args, **kwargs)

        self.deformable_groups = 1

        self.conv_offset = Conv2d(
            self.in_channels,
            self.deformable_groups * 3 * self.kernel_size[0] * self.kernel_size[1],
            kernel_size=self.kernel_size,
            stride=_pair(self.stride),
            padding=_pair(self.padding),
            dilation=_pair(self.dilation),
            bias=True,
        )

        self.init_offset()

    def init_offset(self):
        self.conv_offset.weight.data.zero_()
        self.conv_offset.bias.data.zero_()

    def forward(self, x):
        out = self.conv_offset(x)
        o1, o2, mask = torch.chunk(out, 3, dim=1)
        offset = torch.cat((o1, o2), dim=1)
        mask = torch.sigmoid(mask)
        return deform_conv2d(input=x, offset=offset, weight=self.weight, stride=_pair(self.stride), padding=_pair(self.padding), dilation=_pair(self.dilation), mask=mask)

I can try to make a minimal reproduction, it sounds like it wasnt really fixed because the last reporter had to use a batch size of 1

@Queuecumber any updates on producing a minimal reproduction code ?

I havent had a change to try it yet

I did manage to track down the exact error by using blocking execution:
  File "/home/mehrlich/.cache/pypoetry/virtualenvs/fvr-_yTNPG6U-py3.8/lib/python3.8/site-packages/torchvision/ops/deform_conv.py", line 89, in deform_conv2d
    return torch.ops.torchvision.deform_conv2d(
RuntimeError: CUDA error: CUBLAS_STATUS_EXECUTION_FAILED when calling `cublasSgemm( handle, opa, opb, m, n, k, &alpha, a, lda, b, ldb, &beta, c, ldc)`

It's not particularly informative, I'll try to put together some kind of reproduction today but does this give you any clues about the bug?

It's not particularly informative, I'll try to put together some kind of reproduction today but does this give you any clues about the bug?

Please share your pytorch, torchvision and cuda versions. Will wait for the reproducible code :)

The following script produces an error but not the exact error from above (although it appears related)
torchvision_bug.py
from typing import Any

import torch
from torch.nn import Conv2d, LeakyReLU
from torch.nn.modules.utils import _pair
from torchvision.ops import DeformConv2d, deform_conv2d

class ModulatedDeformConvPack(DeformConv2d):
    def __init__(self, *args, offset_channels, deformable_groups: int = 1, post_activation: Any = None, **kwargs):
        super(ModulatedDeformConvPack, self).__init__(*args, **kwargs)

        self.deformable_groups = deformable_groups

        self.conv_offset = Conv2d(
            offset_channels,
            self.deformable_groups * 3 * self.kernel_size[0] * self.kernel_size[1],
            kernel_size=self.kernel_size,
            stride=_pair(self.stride),
            padding=_pair(self.padding),
            dilation=_pair(self.dilation),
            bias=True,
        )

        self.init_offset()

        self.post_activation = post_activation()

    def init_offset(self):
        self.conv_offset.weight.data.zero_()
        self.conv_offset.bias.data.zero_()

    def forward(self, x, m):
        out = self.conv_offset(m)
        o1, o2, mask = torch.chunk(out, 3, dim=1)
        offset = torch.cat((o1, o2), dim=1)
        mask = torch.sigmoid(mask)
        res = deform_conv2d(input=x, offset=offset, weight=self.weight, stride=_pair(self.stride), padding=_pair(self.padding), dilation=_pair(self.dilation), mask=mask)

        if self.post_activation is not None:
            res = self.post_activation(res)

        return res

device = torch.device("cuda")

bs = 23

test_in = torch.randn(bs, 160, 256, 256, device=device)
test_offset = torch.randn(bs, 64, 256, 256, device=device)
dfc = ModulatedDeformConvPack(160, 64, 3, 1, 1, offset_channels=64, deformable_groups=8, post_activation=LeakyReLU).to(device)

print(f"Total memory used before DFC call: {(torch.cuda.max_memory_allocated() / torch.cuda.get_device_properties(device).total_memory) * 100}%")

test_out = dfc(test_in, test_offset)

print(f"Total memory used after DFC call: {(torch.cuda.max_memory_allocated() / torch.cuda.get_device_properties(device).total_memory) * 100}%")

print(test_out.cpu()[0, 0, 0, 0])

To reproduce run:
CUDA_LAUNCH_BLOCKING=1 python torchvision_bug.py
Note the variable bs. On my test machine I can reproduce at bs=23 or higher, i.e., bs=22 works fine, bs=23 reproduces the error.
I am using a Tesla V100 for testing, this may be related to how much memory the card has, which is why I'm printing the max allocated memory as reported by pytorch. Note that in the working case (22) it's only ~38% on my card so there should be plenty of headroom, although I dont know for sure how accurate that is.
pytorch version: 1.9.0
torchvision version: 0.10.0
cuda version (as reported by nvidia-smi let me know if thats not right): 11.2

I also tried on a gtx1080ti but that runs out of memory before I can reproduce the error (I can only get bs up to 18 before it doesn't have enough memory to run the op), it definitely seems related to the way bs is set though, it's not something about how much or fraction of free memory. I think that's all the GPUs I have access to.
Also note this was three different machines and two different IT departments so it's not like its constrained one particular setup (although if you think the bug is in my code that would make things easy to fix)

Turns out I do have access to another set of machines with A100 cards, same error, same bs setting, cuda version is 11.4 from the driver this time though and memory usage us only ~15% after the DFC call.

Thanks for the code snippet, let me check it from my side and probably we have to open another issue about that. Will get back in a couple of minutes.

BTW I think it's not the batch dimension that's the issue but the size of the tensor itself somehow, in my main codebase I was able to reproduce by just using larger images

Did you check https://github.com/pytorch/vision/issues/4269
Summary is try the nightly and see if it's fixed


The deleted emulator blobs do not show under 'Active and delete blobs' view with Soft Delete enabled

Storage Explorer Version: 1.14.0-dev
Build: 20200604.2
Branch: master
Platform/OS: Windows 10
Architecture: ia32
Azurite Version: 3.7.0
Regression From: Not a regression
Steps to reproduce:

Install and run Azurite -> Launch Storage Explorer.
Expand Local & Attached -> Storage Accounts-> (Emulator - Default Ports) (Key).
Right click the Blob Containers node -> Select 'Configure Soft Delete Policy...' -> Check the option 'Enable Soft Delete' -> Click 'Save'.
Create a new blob container -> Upload one file.
Delete the uploaded file -> Switch to 'Active and deleted blobs' view.
Check whether there shows the deleted blob or not.

Expect Experience:
Show the deleted blob.
Actual Experience:
No deleted blob shows.

I have confirmed with Azurite team that soft delete isn't supported even though it is responding to soft delete policy related requests.

Hi @JasonYeMSFT Got it. Thanks for your sharing.


function to get the current order list

Hello this plugin looks great,however is there any doco related to getting
the order list,
Just need to know in the following cases.
Once the dragtable is applied to a table - how can i get the current order list.?

@mmjamal have you solved your issue? i have a similar one, i'm tring to solve looking here http://akottr.github.io/dragtable/
see
$('#localStorageTable').dragtable({
    persistState: function(table) {
      if (!window.sessionStorage) return;
      var ss = window.sessionStorage;
      table.el.find('th').each(function(i) {
        if(this.id != '') {table.sortOrder[this.id]=i;}
      });
      ss.setItem('tableorder',JSON.stringify(table.sortOrder));
    },
    restoreState: eval('(' + window.sessionStorage.getItem('tableorder') + ')')
});

@ainglese it's not working for large tables.


Update fractal_server/app/schemas/json_schemas to handle both v1 and v2

Expected behavior:
RENAME fractal_server/app/schemas/json_schemas/manifest.json to manifest_v1.json
CREATE fractal_server/app/schemas/json_schemas/manifest_v2.json

Ref tests/v1/01_unit/test_unit_json_schemas.py.


CancellationToken not used/registered

Hi.
Thanks for working on this. I have been exploring this repository since I wanted to do something similar, and I noticed that even when manually passing in a cancellation token, it is not directly acted upon. So for example
let consumeManually (enumerable: IAsyncEnumerable<int>) (token: CancellationToken) = task {
    do! Task.Yield()
    let mutable hasRead = false
    use enumerator = enumerable.GetAsyncEnumerator(token)
    let! canRead = enumerator.MoveNextAsync()
    hasRead <- canRead
    while hasRead do
        let _here = enumerator.Current
        let! canRead = enumerator.MoveNextAsync()
        hasRead <- canRead

    return ()
}

let infinite () = taskSeq {
    while true do
        yield 1
}

[<Fact>]
let usesCancellationToken () = task {
    use src = new CancellationTokenSource()
    let readToEnd = consumeManually (infinite()) src.Token
    do! Task.Delay(100)
    src.Cancel()
    do! readToEnd
}

will run forever. However, if something like Async.Sleep() is bound inside the taskSeq, it will end with an exception, since the token is actually passed to the async when it is bound.
Do you think it would make sense to set the promiseOfValueOrEnd to a cancelled exception (which seems to be the ideomatic dotnet way) or complete(false) when the token is cancelled? I.e, using the CancellationTokenRegistration to abort MoveNextAsync on cancellation?

I could've sworn I answered this a while ago, while I was still out sailing. Anyway, I am back now and I will pick this up again after some housekeeping and fixing some low hanging fruit.

I had the idea to make a registration on the cancellation token, and setting an exception on promiseOfValueOrEnd there. There would be some book-keeping with disposing the registration, but nothing too big.

Note that your example is currently not using a cancellation check. While we are working on better support for cancellation tokens (see, for instance, #133 and #184 for some background), these won't solve your issue, as inside your implementation you will need to decide how often and when you will check for the cancellation token.
let infinite () = taskSeq {
    while true do
        yield 1  // this is essentially a synchronous loop, and there's no check on cancellation here
}

Now, we could certainly consider checking for the cancellation token inside the CE, for instance during MoveNext, but tbh, I am not certain it is wise to abort that way.
For instance, consider a scenario where you need to pull pairs of data, and you coded that such that after pulling each two items, you check for cancellation. If then this library would throw in the middle of these two MoveNext operations because someone canceled, it would break your application. Perhaps we could support this scenario optionally, though.
All that said, we do need to make the cancellation token accessible from inside the CE, which currently isn't the case.

approach with ConfiguredCancelableAsyncEnumerable

This is in the pipeline, see #167.

Or maybe merge with IcedTasks, as I have seen suggested elsewhere.

Merge, no, these libraries support very different use cases. Support, yes. It was indeed discussed, see #188.

that can accept a cancellation token when bound

All functions that consume the input sequence will get an overload to accept a cancellation token. We will also update the Async<'T> support such that we will pick its cancellation token, plus add more overloads to support Async (not to be confused with Task) out of the box.
My point in the previous comment, however, is that none of this will change your use case: your code is impossible to cancel, because you didn't write cancellation support in your own code. Now, that's understandable, given that you currently cannot access the cancellation token from within the taskSeq computation expression, and that's yet another change that is very much in the pipeline.


Extension of the current FFT capabilities

Possible extensions of the current FFT capabilities include :

[ ] Sine / cosine transforms
[ ] Possibility to handle array with different sizes

Temporarily closed, to be re-opened when the version 2.0 is available


[safari / ios] Error: Before calling any methods on the analytics, you first need to call the 'init' function with appId and apiKey parameters

Description
Hey 👋 !
I'm using the Algolia for Shopify app to power the sites main search bar.
Everything works perfectly on every browser apart from safari.
Essentially, when a user types in the search box then clicks on a suggestion, they should be taken to the correct / relevant page. Currently on safari the expected behaviour only works 30% of the time. When a user clicks a search suggestion on safari, the error message gets logged and the search item fills the search bar, leaving the user to manually hit enter and submit the form.
Error: Before calling any methods on the analytics, you first need to call the 'init' function with appId and apiKey parameters
Although this isn't technically breaking the site, its leading to a drop in click through and conversion analytics, especially on ios.
I've followed the docs through here about adding conversions, and made a few modifications.
In algolia_autocomplete.js.liquid:
   // Pass the Algolia anonymous cookie as the unique User Token to run personalisation on each search

   function getCookie(cookieName) {
    let cookie = {};
    document.cookie.split(';').forEach(function(el) {
      let [key,value] = el.split('=');
      cookie[key.trim()] = value;
    })
    return cookie[cookieName];
  }

 var searchOpts = {
      clickAnalytics: true,
      enablePersonalization: true,
      userToken: getCookie('_ALGOLIA'),
      hitsPerPage: params.hitsPerPage,
      highlightPreTag: '',
      highlightPostTag: '',
    };

...
// On clicking a search suggestion, reroute to the correct page

// Event listeners
  autocompleteInstance.on('autocomplete:selected', function(obj, datum, name) {
    if (algolia.config.analytics_enabled) {
      var clickData = {
        index: datum._index,
        eventName: 'click',
        queryID: datum._queryID,
        objectIDs: [datum.objectID],
        positions: [datum._position],
        userToken: getCookie('_ALGOLIA'),
        appId: 'MB13IY345Y',
        apiKey: '5a50c24f3e92ae83f808068a942a1f3b'
      };

      // Send the click event
      //aa.clickedObjectIDsAfterSearch(clickData);
      window.aa('clickedObjectIDsAfterSearch', clickData);
      /**
       * Uncomment the following function call to start storing data in
       * local storage for conversion tracking
       */
      algolia.saveForConversionTracking(clickData);
    }
    switch (name) {
      case 'products': {
        var addVariantId =
          !algolia.config.show_products && datum.objectID !== datum.id;
        window.location.href =
          '/' +
          name +
          '/' +
          datum.handle +
          (addVariantId ? '?variant=' + datum.objectID : '');
        break;
      }
      case 'articles':
        window.location.href =
          '/blogs/' + datum.blog.handle + '/' + datum.handle;
        break;
      default:
        window.location.href = '/' + name + '/' + datum.handle;
    }
  });

The site runs a custom instantSearch approach with Algolia recommend but uses the default autocomplete search bar integration with personalisation from the Algolia shopify app.
Reproduction
View here →
Steps
Must be using Safari

Go to the main search bar and start typing to see suggestions
Click on any suggestion
Open console to see error
If the clicked suggestion takes you to the correct page, and doesn't just fill the search bar, repeat until the error occurs

Expected behavior
Clicking on a search suggestion will automatically take the user to the relevant page - either Product page or collection page.
Visit the website link on any browser apart from safari to see perfect behaviour.
Environment

OS: macOS / iOS
Browser: Safari
Autocomplete version: 1.7.1
Algolia for Shopy version: 2.11.7

I think the issue could also be somewhere in here:
In algolia_autocomplete.js.liquid:
// Hack to handle buggy onclick event on iOS
  autocompleteInstance.each(function(i) {
    var data = autocompleteInstance.eq(i).data('aaAutocomplete');
    var suggestionClass =
      '.' +
      data.dropdown.cssClasses.prefix +
      '-' +
      data.dropdown.cssClasses.suggestion;
    var onSuggestionClick = data.dropdown._onSuggestionClick.bind(
      data.dropdown
    );

    var touchmoved;
    data.dropdown.$menu
      .on('touchend', suggestionClass, function(e) {
        if (touchmoved === false) {
          e.preventDefault();
          e.stopPropagation();
          onSuggestionClick.apply(this, arguments);
        }
      })
      .on('touchmove', function() {
        touchmoved = true;
      })
      .on('touchstart', function() {
        touchmoved = false;
      });
  });

Since the console looks to be reffering back to the _onSuggestionClicked function

But i'm still struggling to see why i'm getting the error in the first place since the init function has been called already

Hello @SidNewman!
The error is related to the Algolia search-insights library and not to Autocomplete.
Following the documentation of the search-insights library, you should first initialize it with your Algolia application ID and search API key and provide the user token: https://github.com/algolia/search-insights.js#browser
Hope that help!

Hello @SidNewman!
The error seems to be related to the Algolia search-insights library and not to the Autocomplete library.
I'm not getting the error on Safari, did you make any changes?

Hiya @FabienMotte
Yeah i've already pushed the changes!
Thank you, legend 🙏

Glad you find a fix! 💯


exposeFunction fails to serialize arguments correctly when toJSON is overridden

Hello,
today I encountered an interesting issue where a specific website would cause page.exposeFunction() to stop working properly. The issue lies in arguments being incorrectly serialized or deserialized. See the code examples below.
Steps to reproduce
Tell us about your environment:

Puppeteer version: 1.14.0
Platform / OS version: MacOS, Linux
URL: http://erasmus-databaze.naep.cz/modules/erasmus/index.php?page=1
Node.js version: LTS/Dubnium

What steps will reproduce the problem?
const puppeteer = require('puppeteer');

(async function main() {
    const browser = await puppeteer.launch({ headless: true });
    const page = await browser.newPage();
    await page.exposeFunction('myFunction', async (...args) => {
        console.log(...args);
        for (arg of args) {
            console.log(typeof arg);
        }
    });
    await page.goto('http://erasmus-databaze.naep.cz/modules/erasmus/index.php?page=1');
    await page.evaluate(async () => {
        await myFunction({ x: 1 })
    });

    await browser.close();
})();

What is the expected result?
{ x: 1 }
object

What happens instead?
[ { " x " :   1 } ]
string
string
string
string
string
string
string
string
string
string

Further findings
It seems that some environment change in the website itself causes the parameters to be incorrectly serialized. It can be seen in the event.data variable in WebSocketTransport.
{"method":"Runtime.bindingCalled","params":{"name":"myFunction","payload":"{\"name\":\"myFunction\",\"seq\":1,\"args\":\"[{\\\"x\\\": 1}]\"}","executionContextId":3}, "sessionId": "D74A031C993D759D5EA29C38C002400F"}

The args are a string, but it should be an Array.
When the code above is called for http://example.com or mostly any other website, it runs fine.
Conclusion
I assume that the problem is caused by the website itself, but I'd expect Puppeteer not to rely on the website's environment to do serialization. I'll try to dig more into how serialization is done in Puppeteer the meantime.
Thank you for your time.

Ok, quick update. It's most probably due to the Object.toJSON function that's in the page's environment. Deobfuscated using jsnice.org
'use strict';
/**
 * @param {!Object} b
 * @return {?}
 */
function K(b) {
  /** @type {string} */
  var type = typeof b;
  switch(type) {
    case "undefined":
    case "function":
    case "unknown":
      return;
    case "boolean":
      return b.toString();
  }
  if (b === null) {
    return "null";
  }
  if (b.toJSON) {
    return b.toJSON();
  }
  if (H(b)) {
    return;
  }
  /** @type {!Array} */
  var cache = [];
  var prop;
  for (prop in b) {
    var A = K(b[prop]);
    if (!E(A)) {
      cache.push(prop.toJSON() + ": " + A);
    }
  }
  return "{" + cache.join(", ") + "}";
}
;

Perhaps just an omission from https://github.com/GoogleChrome/puppeteer/pull/1098 ?

I think this is a problem on the Chromium side.
Checking values on _onBindingCalled, we are getting a pure JSON array when we send simple objects.
"{"name":"compute","seq":1,"args":[3,5]}"

But when we send a complex object. The arguments are being stringified.
"{"name":"myFunction","seq":1,"args":"[{\"x\": 1}]"}"

We could also do something like this on `_onBindingCalled``
    let {name, seq, args} = JSON.parse(event.payload);
    let expression = null;

    if (helper.isString(args))
      args = JSON.parse(args);

    try {
      const result = await this._pageBindings.get(name)(...args);
      expression = helper.evaluationString(deliverResult, name, seq, result);
    } catch (error) {
      if (error instanceof Error)
        expression = helper.evaluationString(deliverError, name, seq, error.message, error.stack);
      else
        expression = helper.evaluationString(deliverErrorValue, name, seq, error);
    }

@kblok Thanks for looking into this.
I don't necessarily think that the whole serialization process is wrong, because it works fine for other websites. Here, for example.com, serializing nested objects produces correct results:
const puppeteer = require('puppeteer');

(async function main() {
    const browser = await puppeteer.launch({headless: true});
    const page = await browser.newPage();
    await page.exposeFunction('myFunction', async (...args) => {
        console.log(...args);
        for (arg of args) {
            console.log(typeof arg);
        }
    });
    await page.goto('http://example.com');
    await page.evaluate(async () => {
        await myFunction(1, 'string', {
            one: 1,
            obj: {
                nested: 'str',
                arr: [
                    1,
                    2,
                    {hello: 'world'}
                ]
            }
        })
    });

    await browser.close();
})();

1 'string' { one: 1, obj: { nested: 'str', arr: [ 1, 2, [Object] ] } }
number
string
object

@aslushnikov Any update on this please? I just tested with 1.16 and the issue still persists. I understand that it's an edge case, I just want to know if we should be looking for workarounds on our side because this will not land anytime soon. Thanks.

I just want to know if we should be looking for workarounds on our side because this will not land anytime soon

@mnmkng this won't land any time soon.

@aslushnikov Thank you.

This is certainly still an issue in puppeteer 21.1.0


Blackrock interface updated kwargs

Motivation
This is related to PR https://github.com/SpikeInterface/spikeextractors/pull/659
To handle the above problem, the same arguments (nsx_override/nev_override) provided by neo.BlackrockIO should also be exposed at the blackrockdatainterface arguments.
Checklist

[x] Have you checked our Contributing document?
[x] Have you ensured the PR description clearly describes the problem and solutions?
[x] Is your contribution compliant with our coding style? Read about PEP8 and black.
[x] Have you checked to ensure that there aren't other open or previously closed Pull Requests for the same change?
[x] Have you included the relevant issue number using #XXX notation where XXX is the issue number?

Seems fine to me, but I don't work with Blackrock data atm. @luiztauffer Look good to you?


Plugin is freezing

Issue description

Additional information
Zigbee2MQTT version:  version 1.17.0 (commit #07cdc9d)
Python version:  docker
Domoticz version: 2020.2 (build 12738)
Plugin version:  name="Zigbee2MQTT" version="0.2.1"
Logs
Attach any additional logs here which might be useful: mqtt, domoticz, plugin logs
No logs

This happen to me also, is happens because Domoticz starts before the Zigbee2MQTT instance is taking much longer to start. After 1 minute after reboot I disable the Zigbee2MQTT plugin and enable it. After that everything works as normal!

This happen to me also, is happens because Domoticz starts before the Zigbee2MQTT instance is taking much longer to start. After 1 minute after reboot I disable the Zigbee2MQTT plugin and enable it. After that everything works as normal!

Turned off Zigbee2mqtt plugin and turned on it after 5 min.
The same picture.

Turned off Zigbee2mqtt plugin and turned on it after 5 min.
The same picture.

With Zigbee2mqtt 1.17.0 you should use v3 of the domoticz-Zigbee2mqtt-plug-in.
First remove adapter from domoticz hardware than upgrade to v3, and add adapter again.
Z2M 1.17.0 uses a new api, one of the new things is that the functions of unknown devices are now exposed. Also the path which gets the devices list is changed to what it should always have been...this is why v 0.2.1 does not show the devices list, because it is still looking in the old path.
Version v3 is updated for this.
v3 also should automatically expose new devices instead of asking support for a new device, but it has still errors for several device types.
Already supported devices are still recognized by v3, so if all your devices are configured in the adapter folder, then most of them should work properly.
But v3 has still some errors which need to be solved to make it work properly with Z2M 1.17.0
Sadly the plug-in developer is not often online lately

With Zigbee2mqtt 1.17.0 you should use v3 of the domoticz-Zigbee2mqtt-plug-in.
First remove adapter from domoticz hardware than upgrade to v3, and add adapter again.
Z2M 1.17.0 uses a new api, one of the new things is that the functions of unknown devices are now exposed. Also the path which gets the devices list is changed to what it should always have been...this is why v 0.2.1 does not show the devices list, because it is still looking in the old path.
Version v3 is updated for this.
v3 also should automatically expose new devices instead of asking support for a new device, but it has still errors for several device types.
Already supported devices are still recognized by v3, so if all your devices are configured in the adapter folder, then most of them should work properly.
But v3 has still some errors which need to be solved to make it work properly with Z2M 1.17.0
Sadly the plug-in developer is not often online lately

Used the latest version of the plugin
git clone https://github.com/stas-demydiuk/domoticz-zigbee2mqtt-plugin.git zigbee2mqtt

Used the latest version of the plugin
git clone https://github.com/stas-demydiuk/domoticz-zigbee2mqtt-plugin.git zigbee2mqtt

And did you remove first the plug-in from the hardware page...and then a clean install? That appears to be quite evident

And did you remove first the plug-in from the hardware page...and then a clean install? That appears to be quite evident

Yes. Removed, deleted plugin's folder and installed a new one from scratch.
The situation became even worse than it was before.

Yes. Removed, deleted plugin's folder and installed a new one from scratch.
The situation became even worse than it was before.

Strange, on which hardware and operating system are you running Z2M and Domoticz?

Strange, on which hardware and operating system are you running Z2M and Domoticz?

debian 10, intel celeron, official docker from docker hub.

debian 10, intel celeron, official docker from docker hub.

I have a Rpi with raspbian Buster, so I can’t compare.
And Z2M is running stable?
Did you enable the web frontend in the configuration.yaml?

I have a Rpi with raspbian Buster, so I can’t compare.
And Z2M is running stable?
Did you enable the web frontend in the configuration.yaml?

Tested Z2M on HASS. Even delays have gone. So starting to migrate to HA from Domoticz.

Did you enable the web frontend in the configuration.yaml?
No. Even didn't hear that they have one.

Tested Z2M on HASS. Even delays have gone. So starting to migrate to HA from Domoticz.

Did you enable the web frontend in the configuration.yaml?
No. Even didn't hear that they have one.

This happen to me also, it happens because Domoticz starts before the Zigbee2MQTT instance which is taking much longer to start. After 1 minute after reboot I disable the Zigbee2MQTT plugin and enable it. After that everything works as normal!

I also had this problem, but solved it by delaying the startup of domoticz with 20 seconds in domoticz.sh
https://www.domoticz.com/forum/viewtopic.php?t=30846
sudo nano /etc/init.d/domoticz.sh

This happen to me also, it happens because Domoticz starts before the Zigbee2MQTT instance which is taking much longer to start. After 1 minute after reboot I disable the Zigbee2MQTT plugin and enable it. After that everything works as normal!

I also had this problem, but solved it by delaying the startup of domoticz with 20 seconds in domoticz.sh
https://www.domoticz.com/forum/viewtopic.php?t=30846
sudo nano /etc/init.d/domoticz.sh

Tested Z2M on HASS. Even delays have gone. So starting to migrate to HA from Domoticz.

Did you enable the web frontend in the configuration.yaml?

No. Even didn't hear that they have one.

https://www.zigbee2mqtt.io/information/frontend.html
Such a nice feature!

Tested Z2M on HASS. Even delays have gone. So starting to migrate to HA from Domoticz.

Did you enable the web frontend in the configuration.yaml?

No. Even didn't hear that they have one.

https://www.zigbee2mqtt.io/information/frontend.html
Such a nice feature!

Tested Z2M on HASS. Even delays have gone. So starting to migrate to HA from Domoticz.

This might be working without delays because you have installed HA after Z2M, and domoticz probably before Z2M, this is why I have a startup delay for domoticz

Tested Z2M on HASS. Even delays have gone. So starting to migrate to HA from Domoticz.

This might be working without delays because you have installed HA after Z2M, and domoticz probably before Z2M, this is why I have a startup delay for domoticz

'probably' is a keyword that leads to a completely wrong conclusion.
I think it's a time to leave Domoticz. They stuck in the past and stay behind HA if we take a look at supported integrations.
Z2M is just a last drop. I guess my issue is also related to Domoticz itself.

'probably' is a keyword that leads to a completely wrong conclusion.
I think it's a time to leave Domoticz. They stuck in the past and stay behind HA if we take a look at supported integrations.
Z2M is just a last drop. I guess my issue is also related to Domoticz itself.

Closing the thread as I moved from Domoticz to Home Assistant and don't have the issue anymore.

Closing the thread as I moved from Domoticz to Home Assistant and don't have the issue anymore.


Bug report: Created date not automatically added when list contains - [ ]

Please check that this issue hasn't been reported before.

[X] I searched previous Bug Reports didn't find any similar reports.

Expected Behavior
Per my settings to "Set created date on every added task" (see screenshot) and the documentation on created date, I expect a created date to be added automatically when I use the ‘Create or edit Task’ Modal.

Current behaviour
✅  The expected behavior occurs when I create a new task on a line that does not start with - [ ].
❌  However, the expected behavior fails to occurs when I create a new task on a line that starts with - [ ]. This occurs when I enter a task below another task.
This video shows the expected and unexpected behavior:
https://www.loom.com/share/29fce02dbc884283af2de94ac65fad63
Steps to reproduce
See video
Which Operating Systems are you using?

[ ] Android
[ ] iPhone/iPad
[ ] Linux
[X] macOS
[ ] Windows

Obsidian Version
1.3.5
Tasks Plugin Version
3.10.0
Checks

[ ] I have tried it with all other plugins disabled and the error still occurs

Possible solution
I believe the issue is that the line already starts with - [ ]

Thanks for using Tasks.
There is content in your video that is not provided as text for me to copy, and it does not show me your settings. So for reasons explained in the following post, I am unable to investigate:
https://publish.obsidian.md/tasks/Support+and+Help/Report+a+Bug
If you can provide full text, and full numbered steps for a reproduction, as per the above, I will willingly have a look when I have time.
Thank you.

Closing as 'not planned' due to insufficient information.
Will happily re-open when/if the question above is answered...

Hello! I'm running into this issue as well and can provide additional detail. I am running into the issue in Obsidian v1.3.5 using Tasks v4.0.1 on Windows 10 Home 22H2. I have not tested on any other platforms, and I have confirmed the behavior in a fresh Vault with nothing else going on, as mentioned in my reproduction steps:

Create new Vault.
Install and enable Tasks.

There are no other active non-Core Plugins or Themes.

In Task's Settings, toggle "Set created date on every added task" to ON.
Close and reopen Obsidian into the empty Vault.
Create a new note.

Note title does not seem to matter. In this instance, I just left it as "Untitled."

Use the Command Palette to invoke the "Create or edit Task" modal and create a task.

This functions as expected. The created task has a [created:: ] inline field. (Actually an emoji, but whatever.)
This is the expected behavior.

From the end of the line containing the newly-made Task, press [Return].

Obsidian predictively prefills the new line with - [ ].

Use the Command Palette to invoke the "Create or edit Task" modal on the line with the prefilled - [ ].
The opened "Create or edit Task" modal does not have a created date, and any task created from this instance of the modal will not have a [created:: ] inline field, though it can be manually created after closing the modal.

This is not the expected behavior.

I have subscribed to the thread, so let me know if there's anything else you need!

Thank you very much for the reproduction. It has given me an idea for a possible fix - to treat a task as new and add the creation date of the description was empty.
I have reopened the issue.
For a workaround for now, I suggest using auto-suggest to add the creation date.

For a workaround for now, I suggest using auto-suggest to add the creation date.

A better/easier workaround is to delete all the characters in the second line before opening the Edit Task modal, so that it behaves the same as the first time.

For anyone who wants to look at this, the relevant code:
https://github.com/obsidian-tasks-group/obsidian-tasks/blob/79bbf1eb4702ca134411c4133cac3111a8ead1a7/src/Commands/CreateOrEditTaskParser.ts#L24-L35
What's happening is:

on lines 24 to 38, the current line in the file is read.
on lines 30 to 32: if the current line represented a task (that is, it has a checkbox), then the line is treated as an existing task, so is used.

This means the code sees the task as already created, and therefore the creation date is not added

on lines 34:35: we are now creating a new task, so if the user setting is to add created date, it gets the current date (via window.moment() to use in the to-be-created task.

So the fix will be to add some code at line 29 that says

if it was a task already - with a checkbox
and if the description is empty,
and it does not already have a creation date....
then add the creation date before returning the task on line 31.

The main work in implementing this will be to ensure that all that logic is fully covered in the tests:

tests/Commands/CreateOrEditTaskParser.test.ts

I've added the help wanted label as this is not something I am going to get to any time soon, due to the sheer volume of work already in progress.
This confirms that it is enough to delete the checkbox characters on a new line before opening the modal, in order to get the creation date added.

I've just released the fix for this in Tasks 4.7.1.

@maia-sh Thanks for reporting the bug.
@Takarias Thanks very much for reporting the steps to reproduce, which enabled me to fix it (and provide a workaround until then...)

For a workaround for now, I suggest using auto-suggest to add the creation date.

A better/easier workaround is to delete all the characters in the second line before opening the Edit Task modal, so that it behaves the same as the first time.

Now, when editing a task line like the following, Created Date will be added automatically (if it is enabled)
- [ ]

So it's no longer necessary to delete the [ ] before editing in order to get the Created date.


[SPK] Extend service smoke test to test a single application repository

As a:
Developer
I want:
SPK automated tests to test the single application repository use case.
So that:
I can be confident that behavior changes will be tested
Describe the solution you'd like:
Add a single application repository test to the smoke tests. It should:

[ ] Be a single application repository
[ ] Deploy variable groups as needed
[ ] deploy the lifecycle and build pipelines for this service, pointing to the same HLD and ACR as the current tests.
[ ] Validate code changes and builds for this service.

Acceptance Criteria:
The tests run and validate changes.
Does this require updates to documentation?:
Yes

@mtarng I increased the time estimate


cpplint and other code cleanups

and thanks for facd8a2203e848af6b0d26bcabdf29fb4d324b5a by the way ;-)

Note: tried to get rid of the -runtime/references filter, but the different usages of esp_timer_handle_t &timer makes it complicated.

Thanks Mathieu.  All good suggestions.  I will admit, navigating github is not one of my strong points, so I have manually implemented your points directly into the repository files in main branch.  Cheers.


ceph giant used total_avail_bytes/total_used_bytes as output of ceph df

@thesues closing this as a fix is being tested in #78

I just applied the patch locally and rebuild calamari-clients. Disk usage is still not displayed properly. unfortunately. I'm not sure whether I am missing something that I have overlooked.


Other notes being pinned as well as Daily Note

I've noticed recently that when the current Daily Note is opened (and pinned), then other notes that are opened are also pinned.

Can you please provide screenshots or a video? Usually only the daily note of the current day should be pinned, others should get unpinned.

I'll try to catch it. It only happened in the workspace with the current Daily Note. I suddenly find all the notes are pinned. I'll let you know when I find what triggers it and try to reproduce it.
Thanks for the plugin by the way. It's a great idea.

Thanks @kmaustral!


Allow command runner to retry on network exit with custom retry

This PR addresses a small bug introduced in https://github.com/apache/incubator-openwhisk/pull/3694 which prevents a test from dictating that it does not care about the exit code. Using the common.retry method which requires the retries function to throw an exception makes it difficult to restore the previous behavior while also allowing for retry on network hiccups.
Related issue and scope

[ ] I opened an issue to propose and discuss this change (#????)

I did not open an issue but there is extensive discussion in this PR https://github.com/apache/incubator-openwhisk-cli/pull/327.
My changes affect the following components

[ ] API
[ ] Controller
[ ] Message Bus (e.g., Kafka)
[ ] Loadbalancer
[ ] Invoker
[ ] Intrinsic actions (e.g., sequences, conductors)
[ ] Data stores (e.g., CouchDB)
[x] Tests
[ ] Deployment
[ ] CLI
[ ] General tooling
[ ] Documentation

Types of changes

[x] Bug fix (generally a non-breaking change which closes an issue).
[ ] Enhancement or new feature (adds new functionality).
[ ] Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

[x] I signed an Apache CLA.
[x] I reviewed the style guides and followed the recommendations (Travis CI will check :).
[ ] I added tests to cover my changes.
[ ] My changes require further changes to the documentation.
[ ] I updated the documentation where necessary.

I've added a test for this change here https://github.com/apache/incubator-openwhisk/commit/d92f09e2201c09d1552044fce4dd5ebff519918f. But this commit depends on https://github.com/apache/incubator-openwhisk/pull/3741.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #3776   +/-   ##
=======================================
  Coverage   74.93%   74.93%
=======================================
  Files         132      132
  Lines        6188     6188
  Branches      392      392
=======================================
  Hits         4637     4637
  Misses       1551     1551

Impacted Files
Coverage Δ

...ommon/scala/src/main/scala/whisk/utils/Retry.scala
100% <ø> (ø)
: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 4f59433...589fff7. Read the comment docs.

@rabbah, makes sense. Thanks for refactoring!


RM-23161 Add Simple Graph Implementation/tests

Hello -- This repository has been very helpful to me as I'm beginning to learn Go. With the dual purpose of getting practice and contributing back in some small way, I have added a Simple Graph implementation. A Simple Graph is an undirected graph without parallel edges or self loops. Let me know what you think.

Raven

Number of Findings: 0

Once the docstrings are added, lgtm

@JulianGriggs You mind adding some docstrings?

Sorry I forgot about this PR. I just added the requested docstrings.

+1

+1


[Question] Frame stacking hasn't been applied to AtariPreprocessing wrapper

Question
As I saw the AtariPreprocessing wrapper implemented in gymnasium.wrappers.atari_preprocessing, I cannot figure out the code for frame stacking.
Docstring described that AtariPreprocessing follows Machado et al. (2018), and the paper mentioned that they used frame stacking in section 2.1 Setting.
But I'm not sure about this yet. Can you check it out?
If this is the case, I can try PR. If it was intentionally taken out, can you tell me the reason?

Hey, the frame stacking wrapper is provided separately, gymnasium.wrappers.FrameStackWrapper I believe

We can update the docstring, for the reason, I believe because it can be sub-optimal for replay buffers, therefore, google dopamine libraries does the frame stacking within the agent rather than environment

I see. Thank you for your answer.


add new feature

@HereHaveTheseFlowers , would you mind pulling this branch down and letting me know if this change is working for you? You can use the .aseprite-extension file provided in the root folder for testing.


Using a lot of memory and not doing anything

I am getting the next issue when doing the command php artisan ide-helper:models
$ php artisan ide-helper:models

 Do you want to overwrite the existing model files? Choose no to write to _ide_helper_models.php instead? (Yes/No):  (yes/no) [no]:
 > no

PHP Fatal error:  Allowed memory size of<PHONE_NUMBER> bytes exhausted (tried to allocate 20480 bytes) in C:\Code\reaweb\vendor\laravel\framework\src\Illuminate\Database\Eloquent\Model.php on line 904
PHP Fatal error:  Allowed memory size of<PHONE_NUMBER> bytes exhausted (tried to allocate 32768 bytes) in C:\Code\reaweb\vendor\symfony\debug\Exception\FatalErrorException.php on line 1

So my guess is that it has a loop that keeps repeating. I just don't know how to debug this.

Are there any progress?

Nop, the issue is still there and haven't found what causes it

@DrowningElysium I found. One of the my model crashed, but I don't know why ) I add it to ignore and all works fine

I found a reason of crash. I have created a relation with the same name as teble column and it crashed at 468 ($relationObj = $model->$method();) in ModelsCommand.php

I have checked all my. Models. I don't have a u relations with the same name as the model they are in

Try debug step by step generator )))
It helps me

I was having the same problem as well. xDebug was my savior, since it stops execution after a certain level of recursion is reached and outputs a trace log. The issue for me was that I had overridden Model::getAttribute() in such a way that caused an infinite recursive loop. I was able to fix it with the info I gleaned from xdebug.

@DrowningElysium is this still an issue?

Haven't tried this since anymore. Currently not working on any projects or having access to.

I was having the same problem as well. xDebug was my savior, since it stops execution after a certain level of recursion is reached and outputs a trace log. The issue for me was that I had overridden Model::getAttribute() in such a way that caused an infinite recursive loop. I was able to fix it with the info I gleaned from xdebug.

infinite recursive loop 🔥


Start the kernel in a read only mode with execution capabilities

The kernel control the channels to the backend server, hence it is required to see the evolution of the charts.
However, it wasn't started in read only mode, which was making the notebooks static, but too much.
Now, the kernel is stared but in read only mode, so that, the session controls what can be done (reject all execution and save actions).
Now, we can have active and passive notebooks
PS: this is helpful for demos, training and other things
/cc @vidma @meh-ninja

so as I understand the read only mode is supposed not to start spark-context, right?

[ ] still can't see new cell output/results
[ ] it forever shows kernel starting, please wait, if kernel/spark context wasn't started before

you're right, the REPL isn't started nor the sparkContext (as a consequence of course). Then, we are approaching a offline mode for the notebook => I'm thinking to rework the SBT and the configuration so that the spark-notebook could start in a reald-only mode... only :-)
I saw that the output aren't all shown, but the chart yes, it seems that the output stream is cleared out after showing (to be checked).
We need to fix this message kernel starting, this will occur in the case you're opening a notebook in read-only mode and there is no other notebook started in executable mode.
The chat  requires a kernel to work, specially, it requires the channels to be opened which are (wrongly IMHO) relying on the kernel! So again, this will happen and remains until a executable notebook will be opened (and refreshing the page!). To fix that, I guess we'll have to create a kernel on the server side too (which isn't the case right now, see getSession), but this kernel wouldn't be started (won't spawn a JVM and the REPL) unless a executable notebook is opened
I'll create an issue to remind us to fix those!
thanks for checking and reviewing, pretty good catches actually (as always ^^)


Android Studio auto complete shows Protobuff package too

When I try to auto-complete the classes most of the times it shows me same classes with two packages one is actual and another is protobuf class, this multiple package could possibly confuse the user on which one to select, I don't remember seeing this in any of other libs.

There's not a lot we can do about this, the protocol buffer messages have the same name as the "utility" wrappers that we defined for programmer convenience by design. If you like, you can add an exclusion for auto imports from org.openyolo.protocol.Protobuf in your project:

Or, to do it manually, create a codeInsightSettings.xml file under the .idea directory of your project, with contents like the following:
<?xml version="1.0" encoding="UTF-8"?>
<project version="4">
  <component name="JavaProjectCodeInsightSettings">
    <excluded-names>
      <name>org.openyolo.protocol.Protobufs</name>
    </excluded-names>
  </component>
</project>

This repo is being archived. Closing issue.


error on dial: x509: certificate signed by unknown authority

Hello folks,
We need this framework to wrap a graphite POC that we are doing, works fine however the tunnel is failing with this error:
Showed where the ghostunnel client is running
error on dial: x509: certificate signed by unknown authority
Showed where the ghostunnel server is running
error on TLS handshake from <IP_ADDRESS>:39980: remote error: tls: bad certificate
I get the issue is likely related to the certificate, I have tried self signed and a .cer generated by a known authority, but I am missing something, if you guys could put me in the right direction, I would appreciate it.

You need to provide a CA certificate in PEM format to the client which the server's certificate is signed by.  If the server has a self-signed certificate, then it's just the server's certificate
the flag to use is --cacert=


fix: adding data-theme to tailwind config

I had a similar issue using the dark: prefix. Ended up fixing it by adding the darkMode selector to the tailwind config. https://tailwindcss.com/docs/dark-mode
Fixes #288
PS @satnaing, love this template!

@rachelslurs
Thanks for your contribution and your kind words about the template!
It's always great to hear positive feedback.


not working on M1 mac mini with macOS 12.6

Application not working on my M1 mac mini with macOS 12.6.
After reboot nothing change - indicator is still in corner :(

Based on your feedback, I've improved Recording Indicator Utility to be more reliable. Can you download the latest update and try again?

In macOS Sonoma 14.4 or later, you can hide the recording indicator on external displays without using Recording Indicator Utility. Learn more ↗


[CLOSED] Fix for tool binary paths

 Issue by akutz
Tuesday Mar 22, 2016 at 19:56 GMT
Originally opened as https://github.com/emccode/libstorage/pull/13

This patch fixes an issue where the go tools gocyclo and golint are not being executed using the full paths.

akutz included the following code: https://github.com/emccode/libstorage/pull/13/commits

 Comment by codecov-io
Tuesday Mar 22, 2016 at 20:00 GMT

Current coverage is 36.44%

Merging #13 into master will not affect coverage as of cb66a77

@@            master     #13   diff @@
======================================
  Files            7       7
  Stmts          354     354
  Branches        12      12
  Methods          0       0
======================================
  Hit            129     129
  Partial         12      12
  Missed         213     213

Review entire Coverage Diff as of cb66a77

Powered by Codecov. Updated on successful CI builds.


MNOWFREE Jelly Bean Viral Leaks Video On Social Media X Twitter[2080K]

1 minute ago Jelly Bean, MNOWFREE Jelly Bean Viral Leaks Video On Social Media X Twitter[2080K]

Jelly Bean's latest video has rapidly gained traction across various social media platforms, captivating audiences and igniting extensive discussions. This talented digital creator has garnered significant attention for her engaging content, particularly her recent Spiderman-themed video, which has gone viral. Viewers are actively seeking out where to watch the full video, with many turning to platforms like Instagram, Twitter (X), and Discord for access.
As the excitement surrounding Jelly Bean continues to build, fans are sharing their reactions and enthusiasm online. The viral success of her video underscores the influential role social media plays in elevating creators to prominence. With her distinctive style and innovative approach, Katherinne has quickly established herself as a noteworthy figure in the digital arena, leaving audiences eager to learn more about her upcoming projects and content.

FG

vf

ggf

FG

vf

ggf


feat: process metric for macos

Signed-off-by: tabVersion<EMAIL_ADDRESS>I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
PLEASE DO NOT LEAVE THIS EMPTY !!!
Please explain IN DETAIL what the changes are in this PR and why they are needed:
as title, this pr can help collect stats for current process on macos
inspired by https://github.com/robotty/simple-process-stats

Summarize your change (mandatory)
How does this PR work? Need a brief introduction for the changed logic (optional)
Describe clearly one logical change and avoid lazy messages (optional)
Describe any limitations of the current code (optional)

Checklist
- [ ] I have written necessary rustdoc comments
- [ ] I have added necessary unit tests and integration tests

[x] All checks passed in ./risedev check (or alias, ./risedev c)

Refer to a related PR or issue link (optional)
close #5129

when I do clippy check on my M1 mac, I get the dependency warning. I don't know if it matters.

Looks like https://github.com/robotty/simple-process-stats is cross-platform. Can we use a single library (like this) to collect metrics for all platforms? cc @Little-Wallace @skyzh

Looks like https://github.com/robotty/simple-process-stats is cross-platform. Can we use a single library (like this) to collect metrics for all platforms? cc @Little-Wallace @skyzh

I'd prefer using some unified crates instead of implementing everything on our own 🤣

when I do clippy check on my M1 mac, I get the dependency warning. I don't know if it matters.

Has this been resolved?

when I do clippy check on my M1 mac, I get the dependency warning. I don't know if it matters.

Has this been resolved?

I almost forgot the issue. Will look into this

when I do clippy check on my M1 mac, I get the dependency warning. I don't know if it matters.

Has this been resolved?

I almost forgot the issue. Will look into this

cc @skyzh Could you please help to take a look?

You've got a typo.
recv = "a502be24bd0971463f5bcbfe035a248d8ba503b7"

should be
rev = "a502be24bd0971463f5bcbfe035a248d8ba503b7"

Feel like drunk-coding 🤣


docs: correct case for Copilot

Why:
Correct case for Copilot
Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[x] For content changes, I have completed the self-review checklist.

@setchy Thanks so much for opening a PR with this fix! I'll update the branch and get this merged once tests are passing 🍏


Data-reciever

In many situations, there is a need to copy data elements and content in several places in the form, as well as make lookups and calculations based on data in one place, which will have consequences in another place.
A complicating factor that must be taken into account are repetitive elements. For example, a resident states various allergies or medicines, and you want these copied to another field in a summary for healthcare personnel.
Examples:
HSØ needs some key data to be copied into a separate summary for healthcare personnel, so that they can read relevant data that is critical to get a quick overview of.
HV has a need that corresponds to that of HSØ. In addition, it is desired that a number of calculations are made across the form, where different fhir-path expressions are used.


Added code for checksum verification

issue #54

@h0x0er can you please create a PR into the rcbranch? I need to run integration tests before merging into main

@h0x0er can you please create a PR into the rcbranch? I need to run integration tests before merging into main

@varunsh-coder I had created PR into rcbranch


SimpleHostRoutingFilter doesn't honor Zuul timeouts anymore

In Camden.SR5, SimpleHostRoutingFilter used to set the socket and connection timeouts based on the properties zuul.host.socket-timeout-millis and zuul.host.connect-timeout-millis, respectively. In Dalston.RELEASE, these properties have no effect, and the default values in the code are used.

Can you point to where the change occurred?  Quickly looking at the code it looks like we are still using those properties.

@ryanjbaxter I didn't try and find out the code but simply putting a breakpoint in the class with before and after upgrade showed that the default values are picked up afterwards. I suppose it won't be terribly difficult to create a project to demonstrate this issue. Do you've any tests that test this feature?

There was no test. 7425f974cb2e45ea86effe15779d8ad3e5b366a1 added one. Can you describe your situation more than "these properties have no effect"? What is your configuration? Anything else that changed between Camden.SR5 and Dalston.RELEASE?

@spencergibb

Anything else that changed between Camden.SR5 and Dalston.RELEASE?

If you mean in Zuul, that affected us other than this, https://github.com/spring-cloud/spring-cloud-netflix/issues/1874#issuecomment-301621558
I've attached a Gradle project that reproduces the timeout issue. There are 2 tests (one for https://github.com/spring-cloud/spring-cloud-netflix/issues/1988), all you've to do is run the ZuulTimeoutTest.
demo.zip

@ryanjbaxter Is this ticket still waiting for feedback?

Ding!

Working on a fix. It's a combination of early initialization and archaius. Moving to @ConfigurationProperties.

Thanks @spencergibb. Like I suspected, it's not a question but a bug, so probably should fix the tag.

Closed via e08a6e8a486ada974da9754a4264650e17eefea6

@spencergibb This defect is because of the same root cause. Can you comment whether https://github.com/spring-cloud/spring-cloud-netflix/commit/e08a6e8a486ada974da9754a4264650e17eefea6 will fix this too?

I clearly commented above that e08a6e8 closed this issue and the commit comment says "fixes gh-1950". I'm confused about what you are asking.

I'm asking about a different issue (forgot to put the link initially, sorry). I've now updated my comment.

I'd say no.

@spencergibb What direction would you recommend taking? The reporter of the other bug is importing ArchaiusAutoConfiguration and then injecting it to force initialization. That seems like a bad hack to me. If  https://github.com/spring-cloud/spring-cloud-netflix/commit/e08a6e8a486ada974da9754a4264650e17eefea6 didn't fix https://github.com/Netflix/Hystrix/issues/1428, should I give up on Javanica @HystrixCommand and create a HystrixCommand manually using a @ConfigurationProperties (basically putting Archaius out of the picture)? That seems like a lot of work.

By putting a breakpoint in com.netflix.hystrix.contrib.javanica.aop.aspectj.HystrixCommandAspect.methodsAnnotatedWithHystrixCommand(), I can see the Hystrix command being executed with the expected threadpool values. So in my case, the ArchaiusAutoConfiguration being initialized later is not an issue because the AOP is executed for every request.

@spencergibb Will this fix be available in Dalston SR2? I think along with the component version, a label for the platform release will also be very helpful in tickets.

Yes as well as camden.


Again, OpenCL only works as root

A program running as regular user does not start. Error:
ocl.getPlatformIDs returned error=-1001 and 0 platforms
but it starts when run as root.

Valerie,
can you pls let us know what application were you running ?
Moreover, Could you retry installing rocm/OpenCL and check ?

First, my name is Valerio.
Second, ROCm already installed.
Application: https://github.com/preda/gpuowl

Valerio,
We will come back to you post checking this internally.
Vasu

Thanks.

This is a real problem with some batch systems that do not allow jobs to run as root.

Valerio,
Did you add the user to video group by issuing this command : “sudo usermod -a -G video  $LOGNAME”
Pls confirm. We have checked internally without adding the user to this group and we see the same issue that has been raised.
Thanks,
Vasu

Yes, I have added all users to the video group. I would not post this issue if it was so simple to resolve.

I have found how to resolve the issue partially.
The file /etc/OpenCL/vendors/amdocl64.icd has owner root and group root. Assigning this ownership to a regular user makes that user able to run OpenCL applications.

I am closing this issue because after a full month there is no feedback. Will reopen new issue if needed.


Unreachable code and possibly wrong order.

This function in src/index.js :
https://github.com/phamann/rollup-plugin-hash/blob/master/src/index.js#L30-L32
function generateManifest(input, output) {
	return JSON.stringify({[input]: output});
}

ends up in
node_modules/rollup-plugin-hash/dist/rollup-plugin-hash.js
node_modules/rollup-plugin-hash/dist/rollup-plugin-hash.es.js
as :
function generateManifest(input, output) {
	return JSON.stringify(( obj = {}, obj[input] = output, obj ));
	var obj;
}

The var obj statement looks like unreachable code to me, and should have come before the return statement, I think.

:wave: I @BobbyBabes, thank you for submitting the issue.
The output you're viewing in node_modules/rollup-plugin-hash/dist/rollup-plugin-hash.js is the compiled output from the Rollup build process defined here, which in turn uses the JavaScript compiler Bublé and therefore bot an issue of the source code in this project but just a matter of style for the Bublé compiler.
This is still valid JavaScript and doesn't throw errors at runtime, as even though the variable declaration is after the return statement, it will get hoisted at execution time. You can read more about variable hoisting in JavaScript on MDN: https://developer.mozilla.org/en-US/docs/Glossary/Hoisting
As this isn't an issue for this project I'm going to close.

I realise that it's not an issue with the source code of this repo. That's why I wrote : ends up in as.
I just pointed it out. Hoisting of variable declarations is something that should be removed from JavaScript.
But if you don't care how (ugly) your code comes out of a build tool. It's of course OK. ;) Peace!


V2 migration

Fixes #N/A
Description
How was this change tested?
Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[x] No

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

Pull Request Test Coverage Report for Build<PHONE_NUMBER>9
Details

58 of 154 (37.66%)  changed or added relevant lines in 4 files are covered.
8 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-1.0%) to 82.03%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/providers/instanceprofile/instanceprofile.go
17
20
85.0%

pkg/errors/errors.go
10
14
71.43%

pkg/operator/operator.go
0
34
0.0%

pkg/fake/iamapi.go
31
86
36.05%

Files with Coverage Reduction
New Missed Lines
%

pkg/errors/errors.go
4
55.56%

pkg/fake/iamapi.go
4
58.74%

Totals

Change from base Build<PHONE_NUMBER>7:
-1.0%

Covered Lines:
5569

Relevant Lines:
6789

💛  - Coveralls


SSL AsyncConnection

I'm using an older version of hiredis with ssl and async, but I'm unsure where is correct place to call redisSecureConnection, as it always return REDIS_OK even if redis-server is down. I've tried immediately after creating the redisAsyncContext, in the onConnectCallback, and finally before sending a redisAsyncCommand. Since it's always return REDIS_OK, there is no way to catch errors until a command is sent, but at that point it's difficult to figure out if redis-server was down or if it was an error in the command.
This does not happen for synchronous connection, redisSecureConnection will return REDIS_ERR if redis-server is down.
Thanks for the help!
loop = aeCreateEventLoop(64);

redisAsyncContext *c = redisAsyncConnect("<IP_ADDRESS>", 6379);
redisSecureConnection(&c.c, ....) // always return REDIS_OK
redisAeAttach(loop, c);
redisAsyncSetConnectCallback(c,connectCallback);
redisAsyncSetDisconnectCallback(c,disconnectCallback);
redisAsyncCommand(...);

There's actually a good example of this in the Redis Sentinel code.
Your instinct is correct.  If redisAsyncConnect returns you a non-null context but relay is down, you can handle that in your connect callback normally.  If the connection does succeed then hiredis will attempt to secure the connection (which of course can also fail).
All that really happens under the hood is that hiredis stores the SSL_CTX internally and overrides the various read/write callbacks to use that context for SSL.

Going to close this as it's not a bug with hiredis but feel free to ask more questions if you have them and I'll do my best to answer.


Upload Form Not Working

When you click "choose file", nothing happens. In the debugger it says only "D/skia: --- Failed to create image decoder with message 'unimplemented'"
It works on Android 9, but not on 10 and 11.
This is the debugger.

I have the same problem


Custom close button/ add a custom button into datetimepicker form

I am fairly new to Github so please forgive me - should I be in violation of the etiquette with my question. This isn't really an issue but more of a problem I am having. I try to custom close button, i want remove "x" icon and change it into text like "OK", but i cant find how to do that. Please tell me is it possible to do that, and if it possiable,  it would be great if somebody could tell me how to do that.
Thank you very much and keep up the good work!

Hi, there are two ways.

If you have an icon with an 'OK' sign It can be do it quite easy it's just change the class
Do this workaround that is when the widget is how

Both option are based on this documentation

thank you for support, your solution work perfect. And i have 1 more question, can i custom hovering color of button in form? And how to do that?

Hi, if you mean to change the hovering color of the 'OK' button, is quite simple just add this rule to your css
.OK:hover { background: whatever color !important} the important is necessary to overwrite the css of the widget
if it's for all the buttons
this rule
.bootstrap-datetimepicker-widget table td span:hover {
	background: #eeeeee;
}

change the background and add !important on your own css that way you don't need to change anything of the css of the widget

thank you so much :)


Only show latest minor K8s version when editing K3s cluster

This PR addresses https://github.com/rancher/dashboard/issues/4543 by making it so that only the latest version (i.e., only one 1.21.x version, and only one 1.22.x version etc) are shown as options when editing K3s clusters.
Nancy already did this PR https://github.com/rancher/dashboard/pull/4154 which limits the versions when editing K3s clusters in the dashboard UI. However, this PR needed to make the same change to Ember. When you edit a K3s cluster, you are shown either the dashboad OR the Ember UI depending on whether the cluster was imported into Rancher or provisioned by Rancher. If you provisioned the K3s cluster in Rancher, you would see the new RKE2/K3s dashboard edit form. However, if you import a K3s cluster into Rancher, you will see the error reported in the above linked issue. Vince said the reason we still use Ember for editing imported K3s clusters is because there are some extra capabilities for imported K3s clusters that have not been forward ported to the dashboard UI.
To test this PR,

I set up a node on Digital Ocean
I installed K3s on the node by running:

curl -sfL https://get.k3s.io | INSTALL_K3S_VERSION="v1.20.13-rc2+k3s2" sh -

I intentionally used an older version so that more version options would be displayed when editing the cluster.
3. I imported the cluster into Rancher
4. From Cluster Manager, I went to the imported cluster and clicked Edit Config
5. I confirmed that the current Kubernetes version was shown in the K8s dropdown by default, and the other choices were limited to one for each K3s minor version

Hello @catherineluse . Although I couldn't run this scenario (my noobice), don't spot anything wrong with your code so I would say it looks good to me.
If you would like to give me a tutorial on how to run this properly, I would be interested. Just reach out if you wanna schedule something.
Thanks!