🐛 knip command hanging with an empty exported enum key

Prerequisites

[X] I'm using the latest version
[X] I've read the relevant documentation
[X] I've searched for existing issues
[X] I've checked the list of known issues
[X] I've read the issue reproduction guide

Reproduction url
https://codesandbox.io/p/sandbox/gracious-oskar-2kxcsc
Reproduction access

[X] I've made sure the reproduction is publicly accessible

Description of the issue
I found a very weird bug where knip get stuck at Analyzing source files... when there's an exported enum with an empty key:
export enum TestEnum {
  "" = "test",
}

Note that you can reproduce this bug only when the enum is exported and the key is empty. If you remove the export or you replace the empty key by something else it will work.

Dang, this is a tough one. Thanks for the report! I'm on it.

:rocket: This issue has been resolved in v5.32.0. See Release 5.32.0 for release notes.
Using Knip in a commercial project? Please consider becoming a sponsor.


Running storybook on my app's webpack or own route

Hello,
I am working with storybook right now, and my rails5 app already has webpacker. I want to be able to use the css in my app in the same storybook. I don't know how to hook it up so I am wondering if the storybook lived under my app instead on its own, maybe it would inherit the css.
So I guess my question is a to part. How do I get my app's css to go through to storybook dynamically like how the asset pipeline and webpack work so I don't have to import a ton of css files in my config?
Or
If that isn't possible can I run storybook on my rails server on its own route something like, example.com/styleguide?

Hi @ajnassar -- that's interesting; You can actually embed the preview iframe (the part of storybook that renders the stories) inside your app (I won't say easily, but it can be done, I have experimented with this a little).
However, I think rendering the full storybook (the "manager") may be a bit more difficult. This is due to the fact that the storybook having its own requirements for CSS etc. It really isn't intended to live inside another app.
It would be interesting to consider refactoring storybook in this way in the future but I'm not sure it would be easy!

Thanks for the quick reply and sounds interesting but I don't want to go that deep. I rather implement a styleguide a different way if it comes to doing too much work.
I think the main thing I need is I need my components that I am showing through storybook to be styled somehow and what better way to style them with the stylesheets you already have in your codebase. Is there a way I can do this?
I notice that in the examples all the components and stories are styled in some way or fashion, but I am not sure how they are styled. It might be my bad understanding of webpack or something else.
Any ideas?

It depends on how the styling for your app is setup.
Often it is just import-ed from a central frontend entry point in a global way. In such cases you just need to make the same imports in your .storybook/config.js.

@ajnassar - Did a quick search on github for some examples and found these.
https://github.com/tai2/webpacker-react-example
https://github.com/lbain/rise
https://github.com/assembleapp/assemble
I am not sure how good any of the implementations are, however it might point you in the right direction. Hope that helps.

Thanks all for the help. Going to try to reconcile my app's webpack.config.js with storybook's. Have them both resolve the directory where my styles are and then import them in my respective entrypoints. Not sure how to do this yet but I will figure it out with all the examples out there. The documentation isn't the best :(

Ok so an update here. On my rails app I upgraded to webpacker 3 and I have some resolved paths pointing to app/assets/stylesheets where my current css lives. Now what I need to do is do the same for storybook, but I can't figure out how to do it yet.
I have read all through the documentation and have tried all sorts of things but it just doesn't work.
Any thoughts/ideas?
currently my webpack.config.js in storybook looks like this:

module.exports = {
  module: {
    rules: [
      {
        test: /\.scss$/,
        loaders: ['style-loader', 'css-loader', 'sass-loader'],
        include: path.resolve(__dirname, '../')
      }
    ]
  }
}```

I thought I could just add

resolve: {
modules: ["node_modules", path.resolve(__dirname, '../app/assets/stylesheets')]
}

But ya that doesn't work.


File bug and wiki bug

File bug
in 4.0.5
Filename  and file are ok?
"mechanization_v2.0.5.zip"
Wiki bug
Machine Frames recipe may be old.

Fixed


Assert popups when running test from VS

Expected Behavior
Tests are run without popups
Actual Behavior
a lot of screens like that (about 12 failing tests)

NTVS Version:
Visual Studio Version:
Node.js Version:

Steps to Reproduce

Checkout NTVS
Run tests from VS

Thanks for the report. Could you provide the list of tests you are seeing these assertions for?
It looks likeWrapperSelfSet is running just fine in AppVeyor and I'm also able to run it locally. It's not a unit test (evidenced by its dependency on the file system) but it does seem to work.
How are you running the tests? Did you do a complete build before executing the tests?
The example test also seems pretty simple, so you should be able to debug it and see what is going wrong or investigate properly fixing the test. Let me know if you would like any help with that.
Thanks.

Closing as no repo / more info needed.
If this is still a problem, please provide the requested information and we can reopen this and continue the investigation. Thanks.


bst-here capabilities are too narrow

See original issue on GitLab
In GitLab by [Gitlab user @tlater] on Nov 15, 2017, 18:08
Currently bst-here runs docker only with CAP_SYS_ADMIN, although bwrap also explicitly requires CAP_SYS_CHROOT, CAP_NET_ADMIN, CAP_SETUID and CAP_SETGID for various purposes. Adding these permissions does not seem to be enough, however, presumably there are some permissions bwrap needs that it doesn't check for explicitly.
This causes errors when bwrap attempts to mount system directories. A test case that mimics what buildstream runs internally for example is:
/src> bwrap --ro-bind / / --unshare-user --unshare-pid --proc /proc /bin/bash
Can't mount proc on /newroot/proc: Operation not permitted

When running docker with --privileged this is not an issue, since all capabilities are granted. We should find the capabilities that are required beyond the above and change the script to provide them.

In GitLab by [Gitlab user @hashpling] on Nov 21, 2017, 16:29
I wonder why bwrap needs CAP_SYS_CHROOT, I thought it used pivot_root or is that controlled by the same capability - the documentation I read suggests that CAP_SYS_ADMIN is needed to use pivot_root?
pivot_root was definitely the first reason that I needed to add --security-opt seccomp=unconfined. If we were less lazy we could probably tighten this up with a custom seccomp profile.

In GitLab by [Gitlab user @tlater] on Nov 29, 2017, 10:44
mentioned in merge request !169

In GitLab by [Gitlab user @tlater] on Nov 29, 2017, 10:47
As a temporary measure !169 sets the default permissions for this to --privileged, since the script is otherwise broken. Obviously this is not a final solution, but we can mark this as an enhancement again when that lands.

In GitLab by [Gitlab user @dp0] on Apr 13, 2018, 16:59
This doesn't appear to be a capability issue (this can be verified by telling Docker to use the capability ALL). One thing that may be playing a role in this (or was for me, anyway) was not having pivot_root in my seccomp profile. After explictly whitelisting it in a custom profile and setting apparmor to be unconfined, all works as expected.

In GitLab by [Gitlab user @tlater] on Nov 29, 2019, 17:58
removed milestone


Added example of deep breathing timing tones

Added example of deep breathing timing tones.

I think I made a mistake when creating this pull request. I meant to only include the last commit (3360e57), but it seems to include my pull request from #6 as well.

Thanks! Merged: https://github.com/zacharydenton/wavebender/commit/c18c13818eb8aac11a2c31ef44b683989f5a1714


Something about installation

What's the Problem?
This is a great app, but for some reasons, my win10 can't install the uwp program, so I can't install it. Can we download the win64 installation package?
Solution/Idea
I very much hope that the app can provide the independent installation package of win64 version
Alternatives
I have no idea for the time being
Priorities

Capability
Priority

This proposal will allow developers to accomplish W
Must

This proposal will allow end users to accomplish X
Should

This proposal will allow developers to accomplish Y
Could

This proposal will allow end users to accomplish Z
Won't

Files Version
No response
Windows Version
No response
Comments
No response

Files can be downloaded from multiple sources
Microsoft Store: https://www.microsoft.com/store/apps/9NGHP3DX8HDX
Sideload version: https://files.community/download/stable
Offline installer: https://github.com/files-community/Files/releases

Files can be downloaded from multiple sources Microsoft Store: https://www.microsoft.com/store/apps/9NGHP3DX8HDX Sideload version: https://files.community/download/stable Offline installer: https://github.com/files-community/Files/releases

Thank you for your Lightning reply! Since I could not install through the Microsoft Store, I tried to download the installation package, but the sideload and offline versions prompted me: "remote procedure call failed" during installation.
I wonder if there will be exe or MSI executable packages?

Those are the available options. It's possible you're using too old of a version of Windows and there isn't anything to do other than update Windows.

Those are the available options. It's possible you're using an older version of Windows and there isn't anything to do other than update Windows.

I think I will try again on the new version of windows, thank you : )


puppeteer-firefox. { ignoreHTTPSErrors: true } triggers Protocol error (Browser.setIgnoreHTTPSErrors)

Steps to reproduce
Tell us about your environment:

puppeteer-firefox version: 0.5.0
Platform / OS version: Windows 10
Node.js version: 8.11.3
jest-environment-puppeteer: 4.3.0

What steps will reproduce the problem?
I have faced this issue while using 'jest-environment-puppeteer' package.
The .setup() method in 'jest-environment-puppeteer/lib/PuppeteerEnvironment.js' is trying to .resetBrowser() first by .disconnect() from the existing Browser and .connect() back to it again.
But this issue also occurs when I tried to reproduced this steps manually.
(This issue doesn't occurs when run with Puppeteer version 1.20.0)
Please check the code below:
const URL = 'https://google.com';
const pptrFirefox = require('puppeteer-firefox');

(async () => {
	const initialConfig = {
		headless: false,
		slowMo: 80,
		ignoreHTTPSErrors: true, // false doesn't trigers Protocol error (Browser.setIgnoreHTTPSErrors)
		args: [
			'--window-size=1280,1000',
			'--no-sandbox',
			'--disable-setuid-sandbox',
			'--ignore-certificate-errors',
			'--ignore-certificate-errors-spki-list',
			'--unsafe-eval',
			'--allow-running-insecure-content',
			'--disable-dev-shm-usage',
			'--user-agent="Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36"'
		]
	};

	let browser = await pptrFirefox.launch(initialConfig);
	const wsEndpoint = browser.wsEndpoint();

	const newConfig = Object.assign({}, initialConfig, {
		browserURL: undefined,
		browserWSEndpoint: wsEndpoint
	});

	await browser.disconnect();
	browser = await pptrFirefox.connect(newConfig);

	const page = await browser.newPage();
	await page.goto(URL, { waitUntil: 'load' });
	await page.waitFor(5000);
	await browser.close();
})();

What is the expected result?
Puppeteer (Firefox) is running with the { ignoreHTTPSErrors: true } param
What happens instead?
The following error occurs:
`(node:14716) UnhandledPromiseRejectionWarning: Error: Protocol error (Browser.setIgnoreHTTPSErrors): Component returned failure code: 0xc1f30100 (NS_ERROR_FACTORY_EXISTS) [nsIComponentRegistrar.registerFactory] register@chrome://juggler/content/InsecureSweepingOverride.js:60:7
setIgnoreHTTPSErrors@chrome://juggler/content/protocol/BrowserHandler.js:27:7
dispatch@chrome://juggler/content/protocol/Dispatcher.js:182:56
_dispatch@chrome://juggler/content/protocol/Dispatcher.js:102:28
  at Promise (...\tools\puppeteer\node_modules\puppeteer-firefox\lib\Connection.js:74:56)
    at new Promise (<anonymous>)
    at Connection.send (...\tools\puppeteer\node_modules\puppeteer-firefox\lib\Connection.js:73:12)
    at Launcher.connect (...\tools\puppeteer\node_modules\puppeteer-firefox\lib\Launcher.js:222:24)
    at <anonymous>
  -- ASYNC --
    at Puppeteer.<anonymous> (...\tools\puppeteer\node_modules\puppeteer-firefox\lib\helper.js:31:27)
    at ...\tools\puppeteer\direct-connection.js:31:30
    at <anonymous>`

Hi, Puppeteer team!
Did you have a chance to take a look at this issue?

Thanks for the report @Quo0
I'm closing this issue since the experimental puppeteer-firefox package is no longer maintained. A replacement will be available
later this year. You can learn more about Mozilla's work on this at https://wiki.mozilla.org/Remote
See also https://github.com/puppeteer/puppeteer/pull/5137


fix(aports): exponential backoff for WPA Supplicant

In certain cases, the wireless device is not created by the time when WPA Supplicant is launched.  Add an exponential backoff around the logic to the OpenRC script that tries to find the devices for the application.

Instead of using bc, how about:
backoff=$(("$backoff" * 2))

I think that does not work with floating-point numbers which I would like to use to represent subsecond delays.

Ah, you're right. The patch works.:)


Kata containers is not able to find containerd.service

Describe the bug
While trying to follow Kata containers instructions for Kubernetes I found that kata-deploy doesn't work, the logs report:
#!/bin/bash
KATA_CONF_FILE=/opt/kata/share/defaults/kata-containers/configuration.toml /opt/kata/bin/containerd-shim-kata-v2 $@
Failed to restart containerd.service: Unit containerd.service not found.

To Reproduce

Install a basic k3s
kubectl apply -f https://raw.githubusercontent.com/kata-containers/packaging/master/kata-deploy/kata-rbac.yaml
kubectl apply -f https://raw.githubusercontent.com/kata-containers/packaging/master/kata-deploy/kata-deploy.yaml
Check the logs for the error message: kubectl log <kata-deploy-pod-name> --namespace kube-system

Expected behavior
Kata containers deploy should not crash.

@bithavoc Even though we ship with containerd we do not set up or provide a systemd containerd.service. I was able to get it working by installing a containerd systemd servive with sudo apt-get install containerd.io (on ubuntu). I am not sure it is a great idea of kata to depend on systemd, and not sure if having two containerds running will cause a problem, but with that service started the error appears to go away:
erik@lubuntu:~/go/src/github.com/rancher/k3s$ kubectl logs -n kube-system kata-deploy-tglb7
time="2019-03-28T18:51:35Z" level=info msg="Preparing data dir /var/lib/rancher/k3s/data/9c715b28c65f6c2cc540939699c07d35e1bf3b42034370ed2f65c53e59423a1f"
copying kata artifacts onto host
Add Kata Containers as a supported runtime for containerd
[plugins]
  [plugins.cri]
   [plugins.cri.containerd]
     [plugins.cri.containerd.runtimes.kata]
warning: containerd-shim-kata-v2 already exists
        runtime_type = "io.containerd.kata.v2"
#!/bin/bash
KATA_CONF_FILE=/opt/kata/share/defaults/kata-containers/configuration.toml /opt/kata/bin/containerd-shim-kata-v2 $@
node/lubuntu labeled

@erikwilson thanks for the response.
Will k3s use a previously installed containerd runtime?

It should be, will probably need to install cri-o also, see rancher/k3s/issues/107

Thanks, I'm going to close this for now.


installation error: No library found under: /usr/local/cuda-11.1/targets/x86_64-linux/lib/libcudart.so.11.1

running that "python3 build.py --enable_cuda"
No library found under: /usr/local/cuda-11.1/targets/x86_64-linux/lib/libcudart.so.11.1
but what I have there is libcudart.so.11.0 and libcudart.so.11.1.74.
My cuda version is 11.1 and it passed the test.

I haven't tried building with cuda 11.1, only 11.0, so it's possible something's wrong with the build script. Can you post the full output of the build.py command?
Alternatively, if you can downgrade to cuda 11.0, then you can use our pre-built cuda wheels, or building from source may be easier.

Yes, of course:
Starting local Bazel server and connecting to it...
Bazel binary path: ./bazel-2.0.0-linux-x86_64
Python binary path: /usr/bin/python3
Python version: 3.6
MKL-DNN enabled: yes
-march=native: no
CUDA enabled: yes
CUDA compute capabilities: 3.5,5.2,6.0,6.1,7.0
Building XLA and installing it in the jaxlib source tree...
./bazel-2.0.0-linux-x86_64 run --verbose_failures=true --config=short_logs --config=mkl_open_source_only --config=cuda --define=xla_python_enable_gpu=true :install_xla_in_source_tree /home/reza/jax/build
INFO: Options provided by the client:
Inherited 'common' options: --isatty=0 --terminal_columns=80
INFO: Reading rc options for 'run' from /home/reza/jax/.bazelrc:
Inherited 'common' options: --experimental_repo_remote_exec
INFO: Reading rc options for 'run' from /home/reza/jax/.bazelrc:
Inherited 'build' options: --repo_env PYTHON_BIN_PATH=/usr/bin/python3 --python_path=/usr/bin/python3 --repo_env TF_NEED_CUDA=1 --action_env TF_CUDA_COMPUTE_CAPABILITIES=3.5,5.2,6.0,6.1,7.0 --distinct_host_configuration=false --copt=-Wno-sign-compare -c opt --apple_platform_type=macos --macos_minimum_os=10.9 --announce_rc --define open_source_build=true --define=no_aws_support=true --define=no_gcp_support=true --define=no_hdfs_support=true --define=no_kafka_support=true --define=no_ignite_support=true --define=grpc_no_ares=true --spawn_strategy=standalone --strategy=Genrule=standalone --cxxopt=-std=c++14 --host_cxxopt=-std=c++14
INFO: Found applicable config definition build:short_logs in file /home/reza/jax/.bazelrc: --output_filter=DONT_MATCH_ANYTHING
INFO: Found applicable config definition build:mkl_open_source_only in file /home/reza/jax/.bazelrc: --define=tensorflow_mkldnn_contraction_kernel=1
INFO: Found applicable config definition build:cuda in file /home/reza/jax/.bazelrc: --crosstool_top=@local_config_cuda//crosstool:toolchain --define=using_cuda=true --define=using_cuda_nvcc=true
Loading:
Loading: 0 packages loaded
INFO: Call stack for the definition of repository 'local_config_cuda' which is a cuda_configure (rule definition at /home/reza/.cache/bazel/_bazel_reza/a75292cea3133afbeddb51835094cc1e/external/org_tensorflow/third_party/gpus/cuda_configure.bzl:1407:18):

/home/reza/.cache/bazel/_bazel_reza/a75292cea3133afbeddb51835094cc1e/external/org_tensorflow/tensorflow/workspace.bzl:98:5
/home/reza/.cache/bazel/_bazel_reza/a75292cea3133afbeddb51835094cc1e/external/org_tensorflow/tensorflow/workspace.bzl:77:5
/home/reza/jax/WORKSPACE:46:1
ERROR: An error occurred during the fetch of repository 'local_config_cuda':
Traceback (most recent call last):
File "/home/reza/.cache/bazel/_bazel_reza/a75292cea3133afbeddb51835094cc1e/external/org_tensorflow/third_party/gpus/cuda_configure.bzl", line 1377
_create_local_cuda_repository(<1 more arguments>)
File "/home/reza/.cache/bazel/_bazel_reza/a75292cea3133afbeddb51835094cc1e/external/org_tensorflow/third_party/gpus/cuda_configure.bzl", line 1054, in _create_local_cuda_repository
_find_libs(repository_ctx, <2 more arguments>)
File "/home/reza/.cache/bazel/_bazel_reza/a75292cea3133afbeddb51835094cc1e/external/org_tensorflow/third_party/gpus/cuda_configure.bzl", line 599, in _find_libs
_check_cuda_libs(repository_ctx, <2 more arguments>)
File "/home/reza/.cache/bazel/_bazel_reza/a75292cea3133afbeddb51835094cc1e/external/org_tensorflow/third_party/gpus/cuda_configure.bzl", line 501, in _check_cuda_libs
execute(repository_ctx, <1 more arguments>)
File "/home/reza/.cache/bazel/_bazel_reza/a75292cea3133afbeddb51835094cc1e/external/org_tensorflow/third_party/remote_config/common.bzl", line 208, in execute
fail(<1 more arguments>)
Repository command failed
No library found under: /usr/local/cuda-11.1/targets/x86_64-linux/lib/libcudart.so.11.1
ERROR: Skipping ':install_xla_in_source_tree': no such package '@local_config_cuda//cuda': Traceback (most recent call last):
File "/home/reza/.cache/bazel/_bazel_reza/a75292cea3133afbeddb51835094cc1e/external/org_tensorflow/third_party/gpus/cuda_configure.bzl", line 1377
_create_local_cuda_repository(<1 more arguments>)
File "/home/reza/.cache/bazel/_bazel_reza/a75292cea3133afbeddb51835094cc1e/external/org_tensorflow/third_party/gpus/cuda_configure.bzl", line 1054, in _create_local_cuda_repository
_find_libs(repository_ctx, <2 more arguments>)
File "/home/reza/.cache/bazel/_bazel_reza/a75292cea3133afbeddb51835094cc1e/external/org_tensorflow/third_party/gpus/cuda_configure.bzl", line 599, in _find_libs
_check_cuda_libs(repository_ctx, <2 more arguments>)
File "/home/reza/.cache/bazel/_bazel_reza/a75292cea3133afbeddb51835094cc1e/external/org_tensorflow/third_party/gpus/cuda_configure.bzl", line 501, in _check_cuda_libs
execute(repository_ctx, <1 more arguments>)
File "/home/reza/.cache/bazel/_bazel_reza/a75292cea3133afbeddb51835094cc1e/external/org_tensorflow/third_party/remote_config/common.bzl", line 208, in execute
fail(<1 more arguments>)
Repository command failed
No library found under: /usr/local/cuda-11.1/targets/x86_64-linux/lib/libcudart.so.11.1
WARNING: Target pattern parsing failed.
ERROR: no such package '@local_config_cuda//cuda': Traceback (most recent call last):
File "/home/reza/.cache/bazel/_bazel_reza/a75292cea3133afbeddb51835094cc1e/external/org_tensorflow/third_party/gpus/cuda_configure.bzl", line 1377
_create_local_cuda_repository(<1 more arguments>)
File "/home/reza/.cache/bazel/_bazel_reza/a75292cea3133afbeddb51835094cc1e/external/org_tensorflow/third_party/gpus/cuda_configure.bzl", line 1054, in _create_local_cuda_repository
_find_libs(repository_ctx, <2 more arguments>)
File "/home/reza/.cache/bazel/_bazel_reza/a75292cea3133afbeddb51835094cc1e/external/org_tensorflow/third_party/gpus/cuda_configure.bzl", line 599, in _find_libs
_check_cuda_libs(repository_ctx, <2 more arguments>)
File "/home/reza/.cache/bazel/_bazel_reza/a75292cea3133afbeddb51835094cc1e/external/org_tensorflow/third_party/gpus/cuda_configure.bzl", line 501, in _check_cuda_libs
execute(repository_ctx, <1 more arguments>)
File "/home/reza/.cache/bazel/_bazel_reza/a75292cea3133afbeddb51835094cc1e/ext1e/external/org_tensorflow/third_party/remote_config/common.bzl", line 208, in execute
fail(<1 more arguments>)
Repository command failed
No library found under: /usr/local/cuda-11.1/targets/x86_64-linux/lib/libcudart.so.11.1
INFO: Elapsed time: 0.970s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)
ERROR: Build failed. Not running target
FAILED: Build did NOT complete successfully (0 packages loaded)
Traceback (most recent call last):
File "build.py", line 380, in
main()
File "build.py", line 375, in main
shell(command)
File "build.py", line 47, in shell
output = subprocess.check_output(cmd)
File "/usr/lib/python3.6/subprocess.py", line 356, in check_output
**kwargs).stdout
File "/usr/lib/python3.6/subprocess.py", line 438, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['./bazel-2.0.0-linux-x86_64', 'run', '--verbose_failures=true', '--config=short_logs', '--config=mkl_open_source_only', '--config=cuda', '--define=xla_python_enable_gpu=true', ':install_xla_in_source_tree', '/home/reza/jax/build']' returned non-zero exit status 1.

For some reason, I can not do the downgrade. Any suggestions on how to fix it?

Hey, sorry for the delay on this. I'm not sure what's going on with your build unfortunately, but I was able to build CUDA 11.1 jaxlib wheels in a docker container (via build_jaxlib_wheels.sh). Can you use the just-released prebuilt CUDA 11.1 wheel, or are you trying to build from source for other reasons?

I haven't updated the installation instructions in the README yet but you should be able to use this command:
pip install --upgrade jax jaxlib==0.1.56+cuda111 -f https://storage.googleapis.com/jax-releases/jax_releases.html

I think we can close this issue since there's been no activity for a long time, and there was no response to the suggestions about how to fix things.


Integration testing

Think it over. A test first flashing a node with an ID, then testing that against other CAN? Or maybe together with CanRelay somehow? But the number of flashes is limited per each chip, so this may be tricky

http://csdc.uvic.ca/wiki/index.php/Tutorial:Unit_Testing_in_MPLAB

Wont do


VK_Video

Description
This is a sample showing how to use Vulkan Video.  Developer's MUST have FFMPEG development libraries installed.  FFMPEG is used for demuxing duties only.  This sample attempts to make a generic library out of the NVIDIA Vulkan Video Sample to show how it can be used in a more generic way.  As this is a very complex sample, it likely will take many revisions before landing.
NB: Vulkan Video is only supported in desktop environments.  Also, it isn't required to ultimately use FFMPEG, one can use things like https://github.com/lieff/minimp4 or similar to handle the demuxing.  However; that would only support h264 while FFMPEG is well tested and supports all codecs.  Working on a demuxing solution is beyond the scope of this sample; but it is possible to do.
Tested in Linux on NVIDIA hardware.
General Checklist:
Please ensure the following points are checked:

[ ] My code follows the coding style
[ ] I have reviewed file licenses
[ ] I have commented any added functions (in line with Doxygen)
[ ] I have commented any code that could be hard to understand
[ ] My changes do not add any new compiler warnings
[ ] My changes do not add any new validation layer errors or warnings
[ ] I have used existing framework/helper functions where possible
[ ] My changes do not add any regressions
[ ] I have tested every sample to ensure everything runs correctly
[ ] This PR describes the scope and expected impact of the changes I am making

Note: The Samples CI runs a number of checks including:

[ ] I have updated the header Copyright to reflect the current year (CI build will fail if Copyright is out of date)
[ ] My changes build on Windows, Linux, macOS and Android. Otherwise I have documented any exceptions

If this PR contains framework changes:

[ ] I did a full batch run using the batch command line argument to make sure all samples still work properly

Sample Checklist
If your PR contains a new or modified sample, these further checks must be carried out in addition to the General Checklist:

[ ] I have tested the sample on at least one compliant Vulkan implementation
[ ] If the sample is vendor-specific, I have tagged it appropriately
[ ] I have stated on what implementation the sample has been tested so that others can test on different implementations and platforms
[ ] Any dependent assets have been merged and published in downstream modules
[ ] For new samples, I have added a paragraph with a summary to the appropriate chapter in the readme of the folder that the sample belongs to e.g. api samples readme
[ ] For new samples, I have added a tutorial README.md file to guide users through what they need to know to implement code using this feature. For example, see conditional_rendering
[ ] For new samples, I have added a link to the Antora navigation so that the sample will be listed at the Vulkan documentation site

Haven't had time to do a proper review yet, but it looks like this PR downgrades the asset submodule to a very old version, which would remove several assets used by some of the recent examples.

Any hint on how to get this to work on windows? When doing the CMake setup, the sample is skipped (not available in Visual Studio) because it can't find ffmpeg (which I have installed manually):
CMake Warning (dev) at C:/Program Files/CMake/share/cmake-3.26/Modules/FindPackageHandleStandardArgs.cmake:438 (message):
  The package name passed to `find_package_handle_standard_args` (FFMPEG)
  does not match the name of the calling package (FFmpeg).  This can lead to
  problems in calling code that expects `find_package` result variables
  (e.g., `_FOUND`) to follow a certain pattern.
Call Stack (most recent call first):
  samples/extensions/video/CMake/FindFFmpeg.cmake:191 (find_package_handle_standard_args)
  samples/extensions/video/CMakeLists.txt:20 (find_package)
This warning is for project developers.  Use -Wno-dev to suppress it.

In order to get it working I'd need to set a lot of paths in cmake:

Is there an alternative way? Like only having one ffmpeg path that needs to be set in cmake, and cmake picking up what it need from ffmpeg based on that single path?

It should hopefully only need avcodec avcore and avformat.  But I do need
to update ffmpeg to only need one path
On Sun, Dec 15, 2024, 3:47 AM Sascha Willems @.***>
wrote:

Any hint on how to get this to work on windows? When doing the CMake
setup, the sample is skipped (not available in Visual Studio) because it
can't find ffmpeg (which I have installed manually):
CMake Warning (dev) at C:/Program Files/CMake/share/cmake-3.26/Modules/FindPackageHandleStandardArgs.cmake:438 (message):
The package name passed to find_package_handle_standard_args (FFMPEG)
does not match the name of the calling package (FFmpeg).  This can lead to
problems in calling code that expects find_package result variables
(e.g., _FOUND) to follow a certain pattern.
Call Stack (most recent call first):
samples/extensions/video/CMake/FindFFmpeg.cmake:191 (find_package_handle_standard_args)
samples/extensions/video/CMakeLists.txt:20 (find_package)
This warning is for project developers.  Use -Wno-dev to suppress it.
In order to get it working I'd need to set a lot of paths in cmake:
image.png (view on web)
https://github.com/user-attachments/assets/13c0c1d9-b2f9-4af2-bb98-8fe26bf6e3e5
Is there an alternative way? Like only having one ffmpeg path that needs
to be set in cmake, and cmake picking up what it need from ffmpeg based on
that single path?
—
Reply to this email directly, view it on GitHub
https://github.com/KhronosGroup/Vulkan-Samples/pull/1245#issuecomment-2543841150,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA5IAY5GTTQPFW4IMNI3IXD2FVT33AVCNFSM6AAAAABTPUCXZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBTHA2DCMJVGA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Laravel 10 support

Goal
When installing the package with Laravel 10, a conflict arises:
Root composer.json requires cyberfusion/cluster-api-client ^1.91.0 -> satisfiable by cyberfusion/cluster-api-client[v1.91.0, v1.91.1].
    - Conclusion: don't install laravel/framework v10.2.0 (conflict analysis result)
    - cyberfusion/cluster-api-client[v1.91.0, ..., v1.91.1] require illuminate/support ^8.22 || ^9.0 -> satisfiable by illuminate/support[v8.22.0, ..., 8.x-dev, v9.0.0-beta.1, ..., 9.x-dev].

Additional information
Allowing illuminate/support ^10.0 in composer.json should do the trick! https://github.com/CyberfusionNL/cyberfusion-cluster-api-client/blob/main/composer.json#L15

https://github.com/CyberfusionNL/cyberfusion-cluster-api-client/releases/tag/v1.92.0

That's quick! Thanks 🙏


Scripted resources unable to serialize/deserialize aka save/load data successfully.

Godot version:
master (ed2f847)
OS/device including version:
Windows 10 Home Edition
Issue description:
Scripted resource's properties don't save. You can create and edit them, but if you attempt to actually save the file, the properties will reset to default values. This does not appear to happen with built-in properties (tested with a GradientTexture resource and it worked fine).
Steps to reproduce:

Create a data.gd Resource-extending script.

# data.gd
extends Resource
@export var count: int
@export var ratio: float

Create a new basic Resource in the Inspector using the new file icon.
Drag and Drop data.gd onto the resource's script property.
Set the count value to 42 and the ratio value to 3.14.
Perform any save operation. The data will reset to 0 / 0.0 respectively.

Also note that there are still a huge variety of export types that simply don't work properly yet (not generating the proper Inspector editor for the property). But that's a separate batch of issues.

The same issue applies for non-resource scripts. See #41690.

@mbrlabs Oh, then this is probably a duplicate then. Should probably be closed. Thanks!


Override fill methods in LongBasedGenerator to use nextLong

This PR overrides the fill methods in LongBasedGenerator (fillInts, fillShorts and fillBytes) to use nextLong and therefore only perform half the calls to the RNG.

I've used the RandomBenchmark to test this change on Lcg64.
[info]           benchmark    ms linear runtime
[info]       FillIntsLcg64 18.94 ==============================
[info]   FillIntsLcg64Fast  9.38 ==============
[info]     FillShortsLcg64  8.87 ==============
[info] FillShortsLcg64Fast  7.61 ============
[info]      FillBytesLcg64  5.98 =========
[info]  FillBytesLcg64Fast  7.58 ============
[info]

The results for fillBytes are interesting.

I reran the tests, and the MarsagliaGaussian is normal test fails consistently. @andrebeat can you check if this is related?

Indeed the test fails deterministically. The issue is related with the override of the fillBytes method but I can't seem to understand what the problem is. I'd like another pair of eyes to look at the fillBytes method to make sure I'm not doing something wrong.
Also, I traced the usage of the fillBytes method in that test to the UniformBigInt implicit defined in Uniform.scala. Again, I couldn't quite understand what's wrong with it but I'm not experienced with that code.

@andrebeat I'll take a look.

I figured this one out, and it's probably my fault.
We were using the LCG64 generator to power the gaussian test. For something like Double this is fine, but I think BigDecimal needed enough entropy that the limitations of LCG64 cause problems. The previous implementation was only using the upper 32-bits, which (I think) have a better distribution than the lower 32. This meant that once we stopped throwing away half the bits the test fails.
In other words, we want to do this:
  def checkMarsagliaGaussian[A: Field: NRoot: Trig: IsReal: Uniform: ClassTag] = {
    val gen = rng.Cmwc5.fromTime(42L) // replaces rng.Lcg64
    val gaussian = new MarsagliaGaussian[A]
    checkGaussian[A] { (mean, stdDev) =>
      gaussian(mean, stdDev)(gen)
    }
  }

Andre, would you mind adding this to your branch?
Also, given that the performance benchmark shows that filling bytes is faster with the "old" code, maybe we should remove this fillBytes override anyway?
Thanks for your work on this!

Nice catch! I actually tried replacing the hardcoded seed (42L) with other seeds as I also suspected that for some reason the Lcg64 was generating less entropy. I had no idea that the upper 32-bits had a better distribution. I've updated the checkMarsagliaGaussian as you suggested.
I ran the fillBytes benchmark again with all the LongBasedGenerator instances:
[info]                      benchmark    ms linear runtime
[info]                 FillBytesLcg64  6.08 ======
[info]             FillBytesLcg64Fast  7.88 ========
[info]                 FillBytesCmwc5 11.39 ============
[info]             FillBytesCmwc5Fast 11.85 ============
[info]     FillBytesMersenneTwister64 28.46 ==============================
[info] FillBytesMersenneTwister64Fast 18.20 ===================
[info]

I haven't looked at the generated code but I assume the JVM is doing something clever to make it faster in the "old" code. The override only pays off for complex RNGs so I agree with you that its probably not worth it, I'm just a bit afraid that this may lead to some inconsistencies. For example, in the case of Lcg64 if we remove the fillBytes override, generating bytes will lead to a better distribution than generating ints or shorts.

I think the reason is that the "byte logic" is complicated enough (and the LCG64 is fast enough) that just generating more longs is easier for the JIT to optimize. Anyway, why don't we merge this as-is, and follow up with performance stuff later.
:+1: Thanks!


[bazel] Auto-generate .pyi files in py_proto_library rule

With some delay, this is a PR for https://github.com/grpc/grpc/issues/32564 (and previously https://github.com/grpc/grpc/pull/31791).
I looked into adding a regular py_test for this change as suggested but I am not aware of any effect that the presence of a .pyi stub file would have at runtime and where some sort of type-checking in a .py script would be affected. Stub files are only for use by type checkers & IDE's. I mean, something like this would work:
import helloworld_pb2
py_file = helloworld_pb2.__file__
pyi_file = py_file + 'i’
self.assertTrue(os.path.exists(pyi_file))

But that seems really hacky to me. Instead I created a simple rule test for py_proto_library with Bazel Skylib which tests the declared outputs for an example py_proto_library  target. Indirectly, this also tests that the declared output files are actually generated. Please let me know if this is sufficient.

Friendly bump!

Unfortunately, it looks like adding a dependency on Bazel Skylib introduces a thorny issue:
(venv) rbellevi@rbellevi:~/dev/grpc/test/distrib/bazel/python$ tools/bazel test -c dbg //:py_proto_library_provider_contents_test
INFO: Running bazel wrapper (see //tools/bazel for details), bazel version 6.1.2 will be used instead of system-wide bazel installation.
ERROR: /usr/local/google/home/rbellevi/.cache/bazel/_bazel_rbellevi/6b245ae2ccca35fac920f4dfd855cf78/external/bazel_tools/platforms/BUILD:89:6: in alias rule @bazel_tools//platforms:windows: Constraints from @bazel_tools//platforms have been removed. Please use constraints from @platforms repository embedded in Bazel, or preferably declare dependency on https://github.com/bazelbuild/platforms. See https://github.com/bazelbuild/bazel/issues/8622 for details.
ERROR: /usr/local/google/home/rbellevi/.cache/bazel/_bazel_rbellevi/6b245ae2ccca35fac920f4dfd855cf78/external/bazel_tools/platforms/BUILD:89:6: Analysis of target '@bazel_tools//platforms:windows' failed
ERROR: /usr/local/google/home/rbellevi/dev/grpc/test/distrib/bazel/python/BUILD:160:24: While resolving toolchains for target //:py_proto_library_provider_contents_test: invalid registered toolchain '@bazel_skylib//toolchains/unittest:cmd_toolchain':
ERROR: Analysis of target '//:py_proto_library_provider_contents_test' failed; build aborted:
INFO: Elapsed time: 0.355s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded, 2 targets configured)
ERROR: Couldn't start the build. Unable to run tests

This only happens on Bazel 6+, but we need to run these tests against all supported Bazel versions, including 6+. We don't use platform constraints ourself, but several of our dependencies do:
(venv) rbellevi@rbellevi:~/dev/grpc$ grep -rn "bazel_tools//platforms"
third_party/bloaty/third_party/protobuf/third_party/googletest/BUILD.bazel:41:    constraint_values = ["@bazel_tools//platforms:windows"],
third_party/bloaty/third_party/googletest/BUILD.bazel:41:    constraint_values = ["@bazel_tools//platforms:windows"],
third_party/bloaty/third_party/abseil-cpp/absl/BUILD.bazel:47:        "@bazel_tools//platforms:osx",
third_party/bloaty/third_party/abseil-cpp/absl/BUILD.bazel:54:        "@bazel_tools//platforms:ios",
third_party/bloaty/third_party/abseil-cpp/absl/time/internal/cctz/BUILD.bazel:29:        "@bazel_tools//platforms:osx",
third_party/bloaty/third_party/abseil-cpp/absl/time/internal/cctz/BUILD.bazel:36:        "@bazel_tools//platforms:ios",

So fixing that issue would become a big yak shaving exercise.
Instead of using Bazel Skylib, could we do something more end-to-end? How are these .pyi files going to be consumed by you under Bazel builds? Presumably you also have a type checker like pytype or mypy integrated with your Bazel build? Could we just have a smoke check that a simple proto passes type check with this change?

Thanks for the reply, I can reproduce this problem. I was using Bazel 5.4.0 when creating this PR.
Currently we don't consume the .pyi files with Bazel (or a type checker integrated with Bazel) but with Pylance/VS Code to get import resolution and auto-completion. There is a bit more to our setup, but in a nut-shell we add Bazel's output paths such as bazel-bin/external/com_github_grpc_grpc/src/python/grpcio to the analysis paths for Pylance and then, of course, Pylance understands seeing foo.py next to foo.pyi.
I haven't worked with type checkers in Bazel but I could give it a shot. But before I do: would it be an option to simply update to a newer version of Skylib? It seems like Skylib migrated their use of platform constraints in this commit. All we'd need is Skylib version 1.0.3 instead of 1.0.2 in grpc_deps(). I tentatively updated this PR with the newer skylib version - just so you can try it out (if bumping the version is in fact an option). Tested successfully with Bazel 5.4.0 and 6.1.2.

would it be an option to simply update to a newer version of Skylib

Sure! As long as it works with all of our versions of Bazel. I just triggered CI so we can find out.

AFAICT the newer Skylib version seems to have solved the issue?!


add apoM and paraM

Nice!
Any chance you could add a quick test? Even if it's fairly trivial, I'll be nice to start increasing the test coverage.

I'm going to go ahead and approve/merge this now, but would love to get some tests (in a follow up PR) if you have the time.


Race condition in docker-compose startup

"depends_on" only specifies the startup order, no waiting for a container to be in a certain state is done. The server requests the database before it is initialized when creating a new database, so the restart property is set. There should be a better solution for this

This should be fixed now, because the number of restarts of the server is limited to 5 ;)


Fixed #32961 -- Added BitXor() aggregate to django.contrib.postgres.

ticket-32961
Currently PostgreSQL 14 is still in beta, so marking as a draft.

@pope1ni Thanks for this patch :+1: Just a note that PostgreSQL 14 will not be released before the Django 4.0 feature freeze, so I'm not sure if it's worth working on related features now :shrug:

@pope1ni Thanks for this patch  Just a note that PostgreSQL 14 will not be released before the Django 4.0 feature freeze, so I'm not sure if it's worth working on related features now

I know, hence my comment. It seems a shame that we might miss out by a matter of a week or two, especially as they're rather trivial. If they've already released, say, 14 RC2 then perhaps it could still be considered (with the potential to revert prior to beta)? Either way, this and the one for the SP-GiST additions are ready for post-freeze.
Also... Don't worry - I scanned the release notes and these were the only two things that really seemed significant for Django. There are unlikely to be more. 😄

@ngnpope Thanks :+1:

Merged in bd47b9bc816bf213b6d0027ed9a9a44955bb7694.


Client port ignored

Operating System: Alpine 3.7.0
Node Version: 10.6.0
NPM Version: 6.1.0
webpack Version: 4.15.1
webpack-hot-client Version: 4.1.0

Expected Behavior
Websocket client uses client port.
Actual Behavior
Websocket client try using server port.

Code
  $ webpack-serve docs/webpack.config.js

serve.config.js
module.exports = {
  clipboard: false,
  devMiddleware: {
    publicPath: '/pattern-library/dist/'
  },
  hotClient: {
    allEntries: true,
    host: {
      client: '*',
      server: '<IP_ADDRESS>'
    },
    port: {
      client: 8082,
      server: 8081
    }
  },
  host: '<IP_ADDRESS>'
}

How Do We Reproduce?
Set hotClient.port as an object with different ports for client and server.
I tracked the issue until modifyCompiler. options.webSocket changes between the function call and beforeCompile event. No idea why.

Maybe the culprit is https://github.com/webpack-contrib/webpack-hot-client/blob/v4.1.0/lib/socket-server.js#L107

Indeed. That and a few other spots. The logic is sneaky for that option.


Add community for Montenegro

for now it's telegram only

Should I do anything else to get a code review? :)

Should I do anything else to get a code review? :)

Your Pull Request is probably fine - this is just a "look at it once a month" kind of project.

@bhousel Thank you!


Setup instructions

Describe Your Problem:
Need help setting it up/ports etc
Logs:
11/8/2022, 1:24:49 PM] [Hikvision NVR Events] Could not load channels Error: connect ECONNREFUSED <IP_ADDRESS>:8080
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16) {
errno: -111,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '<IP_ADDRESS>',
port: 8080,
name: 'RequestError',
data: undefined,
path: '/ISAPI/System/Video/inputs/channels',
status: -1,
headers: {},
res: {
status: -1,
statusCode: -1,
statusMessage: null,
headers: {},
size: 0,
aborted: false,
rt: 234,
keepAliveSocket: false,
data: undefined,
requestUrls: [ 'http://<IP_ADDRESS>:8080/ISAPI/System/Video/inputs/channels' ],
timing: null,
remoteAddress: '',
remotePort: '',
socketHandledRequests: 1,
socketHandledResponses: 0
Show the Homebridge logs here, remove any sensitive information.

"dvr": true,
"host": "<IP_ADDRESS>",
"port": 8080,
"username": "xxxxxx",
"password": "xxxxxxxx",
"motionurl": "http://<IP_ADDRESS>:8080/motion",
"platform": "Hikvision NVR Events"

**Screenshots:**

**Environment:**

* **1.0.2**:
* **Homebridge Version**: 1.5.1 -->
* **Node.js Version**: < 16.18.0 -->
* **NPM Version**: <Unknown -->
* **Operating System**: Docker

<!-- Click the "Preview" tab before you submit to ensure the formatting is correct. -->

Hello, which model Hikvision do you have?

Hi,
It's a DVR which the cameras connect to. It's a DS-7608NI-K2/8P(D48434898)

http://<IP_ADDRESS>:8080/ISAPI/ContentMgmt/InputProxy/channels
http://<IP_ADDRESS>:8080/ISAPI/System/Video/inputs/channels
Can you try opening these links in a web browser on your network?

OK, I suspect that model is an NVR - rather than a DVR. So the issue may be DVR: true in your config.
If I'm right, the first link should work and the second won't.

http://<IP_ADDRESS>:8080/ISAPI/ContentMgmt/InputProxy/channels
http://<IP_ADDRESS>:8080/ISAPI/System/Video/inputs/channels
Can you try opening these links in a web browser on your network?

Those links did not work unfortunately on my local network

Ok, does http://<IP_ADDRESS>:8080 work?

No, but I can get to the web interface with port 443
Here's the ports if it helps you

I also tried port 8000
[11/10/2022, 9:01:59 PM] [Hikvision NVR Events] Could not load channels Error: read ECONNRESET
at TCP.onStreamRead (node:internal/stream_base_commons:217:20) {
errno: -104,
code: 'ECONNRESET',
syscall: 'read',
name: 'ResponseError',
data: undefined,
path: '/ISAPI/ContentMgmt/InputProxy/channels',
status: -1,
headers: {},
res: {
status: -1,
statusCode: -1,
statusMessage: null,
headers: {},
size: 0,
aborted: false,
rt: 1680,
keepAliveSocket: false,
data: undefined,
requestUrls: [
'http://<IP_ADDRESS>:8000/ISAPI/ContentMgmt/InputProxy/channels'
],
timing: null,
remoteAddress: '<IP_ADDRESS>',
remotePort: 8000,
socketHandledRequests: 1,
socketHandledResponses: 0

According to your config, your port should be 80.
Can you try that and let me know?

http://<IP_ADDRESS>:80/ISAPI/ContentMgmt/InputProxy/channels

Also - just a note: your ‘motion’ URL should point to your homebridge instance where you would like the motion alert to trigger ffmpeg, for example on mine it’s http://localhost:8080/motion

Okay - i'm getting somewhere, this is on Port 80, maybe the motion URL? homebridge is in a docker on a synology, so i'm using Localhost:8080, I'm not sure if it has to match?
[Hikvision NVR Events] Could not load channels TypeError: Cannot read properties of undefined (reading 'InputProxyChannel')
at /homebridge/node_modules/@modul8co/homebridge-hikvision-nvr-events/src/platform.ts:58:42
at Parser. (/homebridge/node_modules/@modul8co/homebridge-hikvision-nvr-events/node_modules/xml2js/lib/parser.js:304:18)
at Parser.emit (node:events:513:28)
at SAXParser.onclosetag (/homebridge/node_modules/@modul8co/homebridge-hikvision-nvr-events/node_modules/xml2js/lib/parser.js:262:26)
at emit (/homebridge/node_modules/@modul8co/homebridge-hikvision-nvr-events/node_modules/sax/lib/sax.js:624:35)
at emitNode (/homebridge/node_modules/@modul8co/homebridge-hikvision-nvr-events/node_modules/sax/lib/sax.js:629:5)
at closeTag (/homebridge/node_modules/@modul8co/homebridge-hikvision-nvr-events/node_modules/sax/lib/sax.js:889:7)
at SAXParser.write (/homebridge/node_modules/@modul8co/homebridge-hikvision-nvr-events/node_modules/sax/lib/sax.js:1436:13)
at Parser.exports.Parser.Parser.parseString (/homebridge/node_modules/@modul8co/homebridge-hikvision-nvr-events/node_modules/xml2js/lib/parser.js:323:31)
at Parser.parseString (/homebridge/node_modules/@modul8co/homebridge-hikvision-nvr-events/node_modules/xml2js/lib/parser.js:5:59)

Do you mind copying/pasting the output from this URL?
http://<IP_ADDRESS>:80/ISAPI/ContentMgmt/InputProxy/channels

Webpage displays “
Moved Temporarily
The document has moved herehttps://<IP_ADDRESS>/ISAPI/ContentMgmt/InputProxy/channels.
Webs at :: Port 80”
After login
Sent from Outlook for iOShttps://aka.ms/o0ukef

From: modul8co @.>
Sent: Friday, November 11, 2022 9:35:25 AM
To: modul8co/hikvision-nvr-events @.>
Cc: L0rdLogan @.>; Author @.>
Subject: Re: [modul8co/hikvision-nvr-events] Setup instructions (Issue #3)
Do you mind copying/pasting the output from this URL?
http://<IP_ADDRESS>:80/ISAPI/ContentMgmt/InputProxy/channels
—
Reply to this email directly, view it on GitHubhttps://github.com/modul8co/hikvision-nvr-events/issues/3#issuecomment-1311455892, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABG3JRAIUJN46IFN2ZTEBEDWHYHN3ANCNFSM6AAAAAAR2MNO74.
You are receiving this because you authored the thread.Message ID: @.***>

Under network > Advanced settings - can you confirm if you have SSL enabled or not?

I do have it enabled, shall I try turn it off?
Sent from Outlook for iOShttps://aka.ms/o0ukef

From: L0rd Logan @.>
Sent: Friday, November 11, 2022 11:07:52 AM
To: modul8co/hikvision-nvr-events @.>
Subject: Re: [modul8co/hikvision-nvr-events] Setup instructions (Issue #3)
I do have it enabled, shall I try turn it off?
Sent from Outlook for iOShttps://aka.ms/o0ukef

From: modul8co @.>
Sent: Friday, November 11, 2022 10:59:24 AM
To: modul8co/hikvision-nvr-events @.>
Cc: L0rdLogan @.>; Author @.>
Subject: Re: [modul8co/hikvision-nvr-events] Setup instructions (Issue #3)
Under network > Advanced settings - can you confirm if you have SSL enabled or not?
—
Reply to this email directly, view it on GitHubhttps://github.com/modul8co/hikvision-nvr-events/issues/3#issuecomment-1311548387, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABG3JRGLYXLX5ESZWY22MLTWHYRIZANCNFSM6AAAAAAR2MNO74.
You are receiving this because you authored the thread.Message ID: @.***>

Yes please. The redirect is expecting the access to be done via SSL which the plugin doesn't support as yet.

Okay, so with HTTPS off, I get this:

-
-
1
Front Right
-
HIKVISION
ipaddress
<IP_ADDRESS>
8000
1
admin
plugplay
auto

false
true
false
true

-
2
Front Left
-
HIKVISION
ipaddress
<IP_ADDRESS>
8000
1
admin
plugplay
auto

false
true
false
true

-
3
Rear Right
-
HIKVISION
ipaddress
<IP_ADDRESS>
8000
1
admin
plugplay
auto

false
true
false
true

-
4
Rear Left
-
HIKVISION
ipaddress
<IP_ADDRESS>
8000
1
admin
plugplay
auto

false
true
false
true

-
5
Garage
-
HIKVISION
ipaddress
<IP_ADDRESS>
8000
1
admin
plugplay
auto

false
true
false
true

-
6
Left Side gate
-
HIKVISION
ipaddress
<IP_ADDRESS>
8000
1
admin
plugplay
auto

false
true
false
true

OK, the plugin should work now with port 80 :-)

With HTTPS/SSL OFF, I get this:

Great idea, I'll add that to the readme. Happy you got it working :-)
To see the cameras, you need to configure them in FFMPEG
You also need to configure the ffmpeg listening port to say, 8080, and then http://localhost:8080/motion in the config for motion URL.
Eg, this is mine:
This plugin setup:
    {
        "host": "<IP_ADDRESS>",
        "port": 8080,
        "username": "",
        "password": "",
        "motionurl": "http://localhost:8080/motion",
        "platform": "Hikvision NVR Events"
    },

{
"name": "Camera-ffmpeg",
"porthttp": 8080,
"cameras": [
{
"name": "Lounge Terrace",
"motion": true,
"motionTimeout": 60,
"unbridge": true,
"videoConfig": {
"source": "-i<EMAIL_ADDRESS>"stillImageSource": "-i http://user:pass@<IP_ADDRESS>:8080/ISAPI/Streaming/channels/101/picture",
"maxWidth": 0,
"maxHeight": 0,
"maxFPS": 0
}
}
],
"platform": "Camera-ffmpeg"
},

You can find the IP addresses of your cameras in the extract you pasted above, and add them with matching names to FFMPEG.
Then, when the cameras detect motion, the correct motion sensor will be triggered.

You can find the IP addresses of your cameras in the extract you pasted above, and add them with matching names to FFMPEG.
Then, when the cameras detect motion, the correct motion sensor will be triggered.

Thank you very much, I will try that

For example, your first camera config in FFMPEG should look like this:
{
"name": "Front Right",
"motion": true,
"motionTimeout": 60,
"unbridge": true,
"videoConfig": {
"source": "-i<EMAIL_ADDRESS>"stillImageSource": "-i http://user:pass@<IP_ADDRESS>:80/ISAPI/Streaming/channels/101/picture",
"maxWidth": 0,
"maxHeight": 0,
"maxFPS": 0
}

This plugin works and I can see them live - I'll do more testing to ensure the motion triggering works. if it doesn't work, i'll manually configure each, following your example

Awesome! Happy we sorted it. Enjoy!


release: bump version to 0.33.0

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 66.77%. Comparing base (18209bd) to head (77c1466).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #479      +/-   ##
==========================================
- Coverage   70.06%   66.77%   -3.30%
==========================================
  Files          46       46
  Lines        2856     2856
  Branches      624      624
==========================================
- Hits         2001     1907      -94
- Misses        670      756      +86
- Partials      185      193       +8

Flag
Coverage Δ

unittests
66.77% <100.00%> (-2.81%)
:arrow_down:

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

Files
Coverage Δ

qgis_deployment_toolbelt/__about__.py
100.00% <100.00%> (ø)

... and 5 files with indirect coverage changes


好的，多谢


x/gamm: test that swap and LP events are emitted

Background
Currently, our tests are missing assertions about events. Moreover, it seems that some of our events are missing based on #1939
Therefore, this issue is twofold:

Investigate if / which events are missing and restore them
Add assertions in tests that events are being emitted in the correct places

Acceptance Criteria

all events are in the right places

[x] swap events:
[x] pool joined
[ ] pool exited
[ ] pool created
[ ] msg events

consider emitting all events from the message server
assertions in unit tests are added
all unit tests continue to pass

I have some progress started here: https://github.com/osmosis-labs/osmosis/tree/roman/gamm-events

@mattverse following up on your comment in one of the gamm event PRs. After doing some investigation, I think we should not move the logic for emitting swap and liquidity events to the message server.
The reason is that some gamm keeper methods might be called from other modules. For example, superfluid:
https://github.com/osmosis-labs/osmosis/blob/4970f165f439ad43c8a188e056b4ad69f54aebb4/x/superfluid/keeper/unpool.go#L60
If we were emitting events in the message server, the remove liquidity event would not be emitted.  Therefore, I think it makes sense to keep the locations as is and thoroughly test.

good point! Agreed 😎

Pretty sure this got completed!


Fix infinite loop in GET mentors endpoint

Purpose

The purpose of this PR is to fix #48
Goals

Fix infinite loop in GET mentors endpoint
Approach

Added JsonIgnoreProperties to the classes
Checklist

[x] This PR doesn't commit any keys, passwords, tokens, usernames, or other secrets.
[x] I have read and understood the development best practices guidelines ( http://bit.ly/sef-best-practices )
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation

Related PRs

#45
Test environment

Ubuntu 19.04
OpenJDK 1.8
MySQL
Learning

N/A

PS: I think there will be no negative consequences of removing mentees array from the mentor payload because we have a seperate endpoint to load mentees of a mentor.

PS: I think there will be no negative consequences of removing mentees array from the mentor payload because we have a seperate endpoint to load mentees of a mentor.


mWeb - LHN - Pay button on expense in WS changes back to Submit button

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.72-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4548968
Issue reported by: Applause - Internal Team
Action Performed:
Precondition: User has created a WS in ND

Open the WS chat and create an expense
Submit the expense
Click on Submit button
Go back to LHN
Click on WS chat

Expected Result:
The Submit button became Pay with Expensify/Pay Elsewhere button, and stays like that
Actual Result:
The Submit button becomes briefly Pay button, then reverses to submit button. If pressed again, it does the same thing in a couple seconds
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/3817d497-7fae-43f0-aa4e-6fc09b885fdd
View all open jobs on GitHub

@kadiealexander  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to #vip-vsp


[vite] Error when evaluating SSR module

If you find a security vulnerability, do NOT open an issue. Email<EMAIL_ADDRESS>instead.
Describe the bug
Error: [vite] Error when evaluating SSR module, vite_ssr_import_2.default is not a function.
I followed the guide for integrating Astro and Sanity but when I ran 'yarn dev' and this error happened. If I comment sanity integration code block in astro.config.mjs, the error is gone.
To Reproduce
Steps to reproduce the behavior:
Follow these steps from The official Sanity integration for Astro
REPO
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Which versions of Sanity are you using?
Run sanity versions in the terminal and copy-paste the result here.
sanity 3.18.1
What operating system are you using?
MacOS
Which versions of Node.js / npm are you running?
Run npm -v && node -v in the terminal and copy-paste the result here.
10.2.0
v18.18.0
Additional context
Add any other context about the problem here.
Security issue?
Any security issues should be submitted directly to [security@sanity.io](mailto:security@

sanity.io). In order to determine whether you are dealing with a security issue, ask yourself these two questions:

Can I access something that's not mine, or something I shouldn't have access to?
Can I disable something for other people? If the answer to either of those two questions are "yes", then you're probably dealing with a security issue. Note that even if you answer "no" to both questions, you may still be dealing with a security issue, so if you're unsure, just email us at [security<EMAIL_ADDRESS>

Same issue here! Downgrading to 2.1.1 seems to fix it for now.

Confirmed! It's worked 😁. Thanks so much. But I think this issue should not closed.

Same issue here! Downgrading to 2.1.1 seems to fix it for now.

Confirming that this worked for me as well.

@kmelve @stipsan have you had a chance to look at it? 👀

Same issue here! Downgrading to 2.1.1 seems to fix it for now.

Confirming that this worked for me as well, thanks!

Looks like sanityIntegration is not the default export anymore (seems to be a bug).
A workaround for the latest version (2.1.4) seems to be solving the issue

from import sanity from "@sanity/astro"
to import { sanityIntegration as sanity } from "@sanity/astro"

Any news about this?
still having the issue with:
"@sanity/astro": "^2.1.4",
"@sanity/client": "^6.8.0",
 "astro": "^3.5.2",
"sanity": "3.19.2",

Even after degrading it. Still not working
[vite] Error when evaluating SSR module /home/elamandeep/Desktop/Projects/newportfolio/src/pages/works.astro: failed to import "sanity:client"
|- Error: Cannot find module 'sanity:client' imported from '/home/elamandeep/Desktop/Projects/newportfolio/src/pages/works.astro'
   at nodeImport (file:///home/elamandeep/Desktop/Projects/newportfolio/node_modules/vite/dist/node/chunks/dep-bb8a8339.js:56088:25)
   at ssrImport (file:///home/elamandeep/Desktop/Projects/newportfolio/node_modules/vite/dist/node/chunks/dep-bb8a8339.js:55990:30)
   at eval (/home/elamandeep/Desktop/Projects/newportfolio/src/pages/works.astro:5:37)
   at async instantiateModule (file:///home/elamandeep/Desktop/Projects/newportfolio/node_modules/vite/dist/node/chunks/dep-bb8a8339.js:56052:9)

error   Cannot find module 'sanity:client' imported from '/home/elamandeep/Desktop/Projects/newportfolio/src/pages/works.astro'
Error: Cannot find module 'sanity:client' imported from '/home/elamandeep/Desktop/Projects/newportfolio/src/pages/works.astro'
   at nodeImport (file:///home/elamandeep/Desktop/Projects/newportfolio/node_modules/vite/dist/node/chunks/dep-bb8a8339.js:56088:25)
   at ssrImport (file:///home/elamandeep/Desktop/Projects/newportfolio/node_modules/vite/dist/node/chunks/dep-bb8a8339.js:55990:30)
   at eval (/home/elamandeep/Desktop/Projects/newportfolio/src/pages/works.astro:5:37)
   at async instantiateModule (file:///home/elamandeep/Desktop/Projects/newportfolio/node_modules/vite/dist/node/chunks/dep-bb8a8339.js:56052:9)

Using the named export worked for me on 2.1.4:
import { sanityIntegration } from '@sanity/astro'; // as opposed to `import sanity from '@sanity/astro';`
import { defineConfig } from "astro/config";

// https://astro.build/config
export default defineConfig({
  integrations: [
    sanityIntegration({
      projectId: "<YOUR-PROJECT-ID>",
      dataset: "<YOUR-DATASET-NAME>",
      // Set useCdn to false if you're building statically.
      useCdn: false,
    }),
  ],
});

@salv0
try to add this in your asto.config.mjs
import { sanityIntegration } from "@sanity/astro";
remove
sanity() from intergration
and add this
sanityIntegration({       projectId: "<project id>",       dataset: "<name of database>",       // Set useCdn to false if you're building statically.       useCdn: false,     }),

Should be solved in #149 – thanks for reporting! (Astro requires a default export for npx astro add installation)


No file specified: unexpected token

Describe the bug
√ Parse configuration

Generate outputs
Generate ./packages/graphql/types.tsx
√ Load GraphQL schemas
× Load GraphQL documents
→ Unexpected token (7:31)
Generate

Found 1 error
× ./packages/graphql/types.tsx
SyntaxError: Unexpected token (7:31)

My GraphQL schema:

N/A, this is happening in parsing documents

My GraphQL operations:

I have a bunch in different files

My codegen.yml config file:

schema: ../stream_graphql/packages/*/*.graphql
documents:
  - ./packages/*/*.js
overwrite: true
generates:
  ./packages/graphql/types.tsx:
    plugins:
      - add: '/* eslint-disable */'
      - typescript
      - typescript-operations
      - typescript-react-apollo
    # The combined options of all provided plug-ins
    # More information about the options below:
    # graphql-code-generator.com/docs/plugins/typescript-react-apollo#configuration
    config:
      withHOC: false
      withHooks: true
      withComponent: false

Expected behavior
expecting to see a filename of where the unexpected token was.

I figured out that the errors I was getting was because my files were named .js instead of .jsx.  Is that expected?  Is there a way to treat all files as JSX so I don't have to rename all my files?  Thanks.

@vonwao which version of the codegen do you use?
It was an issue with graphql-tag-pluck, but I think we already solved it.

@dotansimha I'm having the exact same error with the following versions:
    "@graphql-codegen/cli": "^1.4.0",
    "@graphql-codegen/introspection": "^1.4.0",
    "@graphql-codegen/typescript": "^1.4.0",
    "@graphql-codegen/typescript-graphql-files-modules": "^1.4.0",
    "@graphql-codegen/typescript-operations": "^1.4.0",
    "@graphql-codegen/typescript-resolvers": "^1.4.0",
    "graphql": "^14.4.2",
    "graphql-tag-pluck": "^0.8.3",

And my codegen.yml file (which worked before) is as follows:
overwrite: true
schema: 'server/src/schemas/**/*.gql'
documents: 'src/**/*.{ts,tsx}'
generates:
  src/models/generated.tsx:
    - typescript
    - typescript-operations
  server/models.ts:
    - typescript
    - typescript-resolvers
pluckConfig:
  modules:
    - name: 'babel-plugin-relay/macro'
      identifier: 'graphql'

@jedmao can you please share a reproduction in a repo?

Closing. @vonwao @jedmao feel free to reopen if you have a reproduction for this.

No need to reopen. I created a new issue #2387.


Work with DMTF to standardize boot/shutdown in DSP0249 PLDM Set State

based on https://github.com/opiproject/opi-prov-life/blob/main/boot/PLDM.md#comparison-of-pldm-dell-and-nvidia-proposals there is agreement on creating a new PLDM state sensor type that maps to states 0-11 in the Dell and Nvidia contributed NC-SI OEM commands.  Work with DMTF to get this incorporated in DSP0249 PLDM Set State.

see https://github.com/DMTF/PMCI-WG/issues/620 - Yuval posted DSP0249_1.2.0_draft7 in the DMTF workgroup with Embedded processor OS state

Dec 11th - Updated in draft 7 https://members.dmtf.org/wg/pmci/document/59388

DMTF issue marked as closed but 1.2 draft has not been published


Change drafts so it stores media URL instead of data

Storing and decoding media data is costly; drafts should store media URLs instead of data

Actually using Core Data for this instead!


Upgrade/thin skinny em

Update to thin 1.8 (will compile under Xcode 12) and event machine 1.2
Some of the changes to make this possible include.

Moving Process.daemon to before the the eventmachine loop
Handle signals in mailcatcher (changes in thin made this necessary)
Removed the explicit gem activations which I don't think are necessary (anymore?)
Removed the EventMachine monkey patch which should not be necessary anymore
Added some constraints on dependencies

Depends on https://github.com/sj26/skinny/pull/8
Should supersede https://github.com/sj26/mailcatcher/pull/431

Neat! What happens if you start mailcatcher and the port is in use?
Do websockets work? Last time I tried this it broke.

The only issue I have noticed is the console output is a bit messy - because control has returned to the shell.
If the port is in use it still print outs because it has not yet point the std io to /dev/null

The other option might be to test the ports ahead of time using another API of some kind. Unfortunately it seems like the Servers need to be called within the run loop. I'm happy to be wrong about that though.

Yeah I'd love to open the socket, handle failure, or hand the open IO to eventmachine after the fork, but I couldn't figure that quickly last time I tried.

Hi, is there anything that I can do to move this forward?
At the moment I'm using rvm ruby-2.4.9 do mailcatcher -f -v, but it would be nice to run mailcatcher on supported Ruby versions

I don't think there is anything super wrong with the way it currently is apart from the occasional console output formatting issue on startup.
I did look into fixing it the way suggested but it is a fair whack more work because it looks like it I would need to change the C part of eventmachine. I am C fluent but I haven't yet built up the momentum to tackle it.

I did look into fixing it the way suggested but it is a fair whack more work because it looks like I would need to change the C part of eventmachine. I am C fluent but I haven't yet built up the momentum to tackle it.

Actually I think I lied. I just spied a way to do it. I'll update this PR soon.

Yeah I'd love to open the socket, handle failure, or hand the open IO to eventmachine after the fork, but I couldn't figure that quickly last time I tried.

I think this has been achieved.

Thank you for this, but we're closing in favour of moving away from eventmachine, thin and skinny in #467.


Further improve error reporting

We should include the original error message if dispatching a command fails. ATM you need to debug the application to identify the root of the exception which is bad for beginners.

Solved in latest version


Added location to TestableReference

Short description 📝

Added LocationScenarioReference as an option for Test Targets. Images below show how these options are applied in both Xcode and .xcsheme file.

These changes are necessary for this issue in XcodeGen.

Hey All! Just wondering if there is anything more that I need do here on my end to help move this PR forward. This would be an awesome addition that our team could really use. (cc. @pepicrft)

Sorry for the late review @KrisRJack. Changes look good so as soon as CI is happy I'll go ahead, merge, and release a new version

@all-contributors add @KrisRJack for code

Awesome 🎉! No worries at all and thank you so much @pepicrft!

@KrisRJack here is the release with your changes. Again, thanks for your contribution 🚀


small unit test for deno check with watch arg

hey mate,
just a small unit test for your change 15325 ,
I now don't have time for writing integration test but seems this is fine as of now at-least

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

@VishnuJin Seem we should to remove it to check.rs.

all flag related tests stays in cli/args/flags.rs so better leave it there,

I messed up this PR, you can simply copy paste the test code to your branch or cherry-pick my commit from https://github.com/VishnuJin/deno/tree/fix/unit-test-for-14858
Pass C.I result - https://github.com/VishnuJin/deno/runs/7582159334?check_suite_focus=true

@VishnuJin Done. Thanks


COLLECTIONS-533 Add ArrayListValuedLinkedHashMap

Main and test code inspired by (largely copied from) ArrayListValuedHashMap.
Unit tests cover the product code for 100%.
Bumped coverage for ArrayListValuedHashMap also to 100%, coming from 88% previously due to an uncovered copy constructor.

FTR https://issues.apache.org/jira/browse/COLLECTIONS-533


Database download fails after 49% with error "fail: Size mismatch"

See attached log file:
lacells_gen_log.txt
Have tried to download the database multiple times but it fails every time. Any idea what the problem is?
Notice that the % complete changes from 049% to -49%.

oops, posted issue in wrong repository. Should have posted here: https://github.com/n76/Local-GSM-Backend


Optimization: pystr.isprintable() -> Py_UNICODE_ISPRINTABLE(pystr)

I think these should be equivalent, but the generated C I'm seeing doesn't appear to be using Py_UNICODE_ISPRINTABLE.

str.isprintable() does not exist in Py2, so applying this optimisation would turn a Python runtime exception into a C compile time error.
Can be done in Cython 3.1.


Convert pt file to csv or display database content

Hello
I need a solution to convert pt database to a csv file
or a tool to display the data in the pt database
A Windows or Android tool can be really useful
Especially if we want to convert data from a csv file to a pt file or vice versa
A tool for displaying database content or csv conversion
I hope you will show me your way

This is not recommended. However, you can do that when you have the the same classes available in JVM that has been used to write data to pt file. The answer to similar question is here https://github.com/pilgr/Paper/issues/207#issuecomment-1518119309


(GH-2555) Remove public-key, private-key params for pkcs7 plugin

This removes support for the public-key and private-key parameters
in the pkcs7 plugin. Previously, Bolt would change these parameters to
the correct public_key and private_key parameters.
!removal

Remove support for private-key, public-key parameters in pkcs7
plugin
(#2555)
Support for the private-key and public-key parameters in the pkcs7
plugin has been removed. Use the private_key and public_key
parameters instead.

Successfully does not recognize either key, and I can't find any other references in the codebase (at least for public-key, private-key is much harder to search for).

Successfully does not recognize either key, and I can't find any other references in the codebase (at least for public-key, private-key is much harder to search for).


Extra code

Delete code that isn't used
        // // For all urls, push a promise from the url to an array promises
        // for (let i = 0; i < urls.length; i++) {
        //     promises.push(getPokemon(urls[i]));
        // }

Removed the whole file because I didn't use it, thanks for the heads up!


add PVCName as data source

Now we can inject PVC as volume:

It seems that not cover the situation about two volumes

LGTM now


Bug displaying glossary popups (FIrefox)

I ran into two different problems with the glossary popups tonight. I'm on Firefox Version 97.0 (64-bit) on Windows 10, with adblockers disabled for the site.
On https://web3isgoinggreat.com/single/2022-02-08-1, the "gm" term displays a blank box:

On https://web3isgoinggreat.com/single/2022-02-04-3, clicking the "metaverse" term wipes the whole page and produces a Application error: a client-side exception has occurred (see the browser console for more information). message. Here are the relevant errors on the console:
TypeError: t is undefined
    NextJS 17
        T
        children
        b
        ro
        jo
        Hu
        Pi
        xi
        _i
        vi
        Ql
        unstable_runWithPriority
        $l
        Ql
        Hl
        Me
        Xt
framework-91d7f78b5b4003c8.js:1:82788

TypeError: t is undefined
    NextJS 17
        T
        children
        b
        ro
        jo
        Hu
        Pi
        xi
        _i
        vi
        Ql
        unstable_runWithPriority
        $l
        Ql
        Hl
        Me
        Xt
main-a56127814584ab09.js:1:11458
    NextJS 18
        ye
        fn
        value
        callback
        fa
        hu
        Li
        unstable_runWithPriority
        $l
        Ti
        vi
        Ql
        unstable_runWithPriority
        $l
        Ql
        Hl
        Me
        Xt

A client-side exception has occurred, see here for more info: https://nextjs.org/docs/messages/client-side-exception-occurred main-a56127814584ab09.js:1:11475
    NextJS 18
        ye
        fn
        value
        callback
        fa
        hu
        Li
        unstable_runWithPriority
        $l
        Ti
        vi
        Ql
        unstable_runWithPriority
        $l
        Ql
        Hl
        Me
        Xt

Sorry I can't debug any further than that (I'm barely competent at web1). Let me know if there are any more diagnostics I can provide...

Thank you! I think I've resolved both of these issues, but please reopen the issue if you see them again!

It is -- are you seeing issues on different popups now?

I tried the same ones as in the original report.
On https://web3isgoinggreat.com/single/2022-02-08-1, the "gm" popup now gives "Application error: a client-side exception has occurred (see the browser console for more information)." Console errors are
TypeError: t is undefined
    NextJS 17
        T
        children
        b
        ro
        jo
        Hu
        Pi
        xi
        _i
        vi
        Ql
        unstable_runWithPriority
        $l
        Ql
        Hl
        Me
        Xt
framework-91d7f78b5b4003c8.js:1:82788

TypeError: t is undefined
    NextJS 17
        T
        children
        b
        ro
        jo
        Hu
        Pi
        xi
        _i
        vi
        Ql
        unstable_runWithPriority
        $l
        Ql
        Hl
        Me
        Xt
main-a56127814584ab09.js:1:11458

On https://web3isgoinggreat.com/single/2022-02-04-3, same message when clicking on the "metaverse" popup. Console logs are:
TypeError: t is undefined
    NextJS 17
        T
        children
        b
        ro
        jo
        Hu
        Pi
        xi
        _i
        vi
        Ql
        unstable_runWithPriority
        $l
        Ql
        Hl
        Me
        Xt
framework-91d7f78b5b4003c8.js:1:82788
    NextJS 16
        uu
        callback
        fa
        hu
        Li
        unstable_runWithPriority
        $l
        Ti
        vi
        Ql
        unstable_runWithPriority
        $l
        Ql
        Hl
        Me
        Xt

TypeError: t is undefined
    NextJS 17
        T
        children
        b
        ro
        jo
        Hu
        Pi
        xi
        _i
        vi
        Ql
        unstable_runWithPriority
        $l
        Ql
        Hl
        Me
        Xt
main-a56127814584ab09.js:1:11458
    NextJS 18
        ye
        fn
        value
        callback
        fa
        hu
        Li
        unstable_runWithPriority
        $l
        Ti
        vi
        Ql
        unstable_runWithPriority
        $l
        Ql
        Hl
        Me
        Xt

(Hope that makes some sense to you; if there's a way to get more verbose logging, let me know)

Just to double check, have you reloaded the page since the fix was pushed?

Yes, definitely reloaded, and tried clearing cookies too. Haven't done a full cache wipe yet though.

Looks like this is working now. Thanks!


Respect XDG base directory specification

Description
Added support for ~/.config/betterlockscreen/betterlockscreenrc config file as a last resort.
Per specification, config files should be located at  $XDG_CONFIG_HOME/subdir/filename
Checklist:

[x] I have performed a self-review of my own code/checked that ShellCheck succeeds
[x] I have made corresponding changes to the documentation (if applicable)

It was the original plan to do this with the user-config, but I wasn't aware that the application-directory is also a requirement. From my POV as this is still backwards-compatible there is no real issue with adding it but I would consider adding a deprecation-warning if old user-config is used so for v5 can drop the old location.

Good point, I added it.
However, I can't find the reason of shellcheck failing. There are no errors for me locally.

Yeah I had the same issue and fixed it from the GitHub-action output (open MR) but will have to look deeper what's going on there...On 25. Dec 2022, at 20:57, Michael @.***> wrote:
Good point, I added it.
However, I can't find the reason of shellcheck failing. There are no errors for me locally.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

Update: Was related to the shellcheck-update v0.9.0 which introduced new checks.  So will go forward and merge #365 so you/I can rebase on it :)

Sorry again about the PR: is the duplication betterlockscren/betterlockscreenrc really sense-full? Should we if we do such a breaking change, witch to betterlockscreen/config or is there any standard/rfc we can follow?
I think we should add a second line after the error (info or something) with a oneliner mkdir .config/betterlockscreen/ && mv ~/.config/betterlockscreenrc ~/.config/betterlockscreen/config to make it as easy for the user as possible to migrate.

I had some time and combined your changes with my feedback and some changes i originally made in one bigger change-set (which I avoid this time) #293. I would appreciate your feedback/testing in #368 :)

From my experience, most programs duplicate program name in both directory and filename. But since betterlockscreen has a rather long name, it may be more convenient.
However I see potential downsides with this approach (although rather minor):

If you want to fuzzy find betterlockscreen config, you need to do so for the directory name, not file. This might be a problem if betterlockscreen directory had multiple files (you search for betterl... and get other files, you search for conf.. and get other configs). But in the case of one file searching for dir name should be good.
Usually text editors and IDE's show only file name in a tabline. So, when you see there config, it is not very informative.

I see your points there, also it's then consistent to the system-configuration introduced in my extended config-improvement PR. When you have time to I would appreciate your feedback/tests, after that I would merge it and make a beta release with the other finished PR #369  :)

As I had time going forward today I have merged my extended/enhanced version but still appreciate your feedback on this (in the PR) or with an extra PR if changes needed.
Will close this PR as resolved with #368, and try to release a new beta soon.


How to interact Google Spreadsheets with Chatbots?

I'm using Service Account's to manipulate my own spreadsheet, I know my script is working because I've tried it direct by Node (running node myScript.js)
My script is like this:
const { GoogleSpreadsheet } = require('google-spreadsheet');

async function start() {
	const creds = require('./creds-from-google.json');
	const sheetID = 'my spredsheets URL id here';
	const doc = new GoogleSpreadsheet(sheetID);

	await doc.useServiceAccountAuth({
		client_email: creds.client_email,
		private_key: creds.private_key,
	});

	await doc.loadInfo(); // loads document properties and worksheets
	console.log(doc.title);

	const sheet = doc.sheetsByIndex[0];
	console.log(sheet.title);

	const data = {
        	'Title': 'my title here',
        	'Content': 'my content here'
	};
	return sheet.addRow(data);
}
start();

But when I execute this code by Telegram bot, it's getting 401 error.
Error message:
Google API error - [401] Request is missing required authentication credential. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.

The issues is probably that the environment your bot is running in does not have the auth configured correctly. Going to close this but feel free to reopen if still an issue and you can post more context.


polling web sockets

Merge approved, can not execute myself.
On Fri, May 21, 2021 at 2:07 PM joramirezStackit @.***>
wrote:

@.**Stackit commented on this pull request.
In controllers/channels.js
https://github.com/shouse/metis/pull/7#discussion_r637161183:

@@ -277,6 +280,7 @@ module.exports = (app, passport, React, ReactDOMServer) => {
}
getPNTokensAndSendPushNotification(members, channelName, message.record.name);
} catch (e) {

   console.error('[Error sending messages]', e);

I fixed the console.log on the feature/logging branch
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/shouse/metis/pull/7#discussion_r637161183, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEIKXVMPFWJPBJWV74YAFTTO2VO5ANCNFSM45HHUGEQ
.


Add version_check config

The automatic version check makes the things a lot harder to script in non-attended environments -- such as CI, as it keeps waiting for a response if an updated version is found.
Also, I use my own tool to manage my updates system widely, which I run automatically.
Fixes #925

Hi, @felipecrs. To clarify, do you mean to prevent the self-update check from happening in a CI environment, or do I misunderstand your intent? If this is indeed the problem you are facing, we already have a config variable called sdkman_auto_selfupdate to cover this.

Hi, @marc0der. The sdkman_auto_selfupdate=false configuration makes the update not to install automatically. But still, sdk checks for updates in almost every command, and prompts for the user to update if a newer version is found.
The new configuration sdkman_version_check=false will prevent sdk from checking for updates automatically and thus, also prevent the update prompt from appearing as well.
Different things, right?

This issue can be replicated:
❯ docker run -it --rm mcr.microsoft.com/vscode/devcontainers/java:0.201.5-15 bash -c 'echo "sdkman_auto_selfupdate=false" > $SDKMAN_DIR/etc/config && touch -d 20120101 $SDKMAN_DIR/var/delay_upgrade && exec bash -ic "sdk version"'
We periodically need to update the local cache. Please run:

  $ sdk update

==== BROADCAST =================================================================
* 2021-06-18: mvnd 0.5.2 available on SDKMAN! https://git.io/Jn0Kl
* 2021-06-17: micronaut 3.0.0-M2 available on SDKMAN!
* 2021-06-15: micronaut 2.5.6 available on SDKMAN!
================================================================================

SDKMAN 5.11.2+698

ATTENTION: A new version of SDKMAN is available...

The current version is 5.11.5+713, but you have 5.11.2+698.

Would you like to upgrade now? (Y/n): ^C

Hey @felipecrs, I understand the problem now. Could we make the naming of this config a little clearer to reflect the what, not the how? How about calling the config sdkman_selfupdate_disable to make it very clear what the behaviour is? This will also require changes to be made in the sdkman-hooks service. I would also like to have a test to cover this if at all possible.

Sure! But isn't the existence of both sdkman_auto_selfupdate and sdkman_selfupdate_disable a bit confusing? Just a thought: what if we extend sdkman_auto_selfupdate to include what I'm introducing?

The name sdkman_auto_selfupdate implies that you are making the self-update automatic (or not). This is distinctly different from not doing a self-update at all. I prefer this as a separate configuration, and we should document both clearly on the website.
Incidentally, the associated changes in the sdkman-hooks service need to be made in the install and selfupdate scripts.

This is distinctly different from not doing a self-update at all

But the new configuration is not removing this ability, it's available there with sdk selfupdate command. Actually, it's disabling the "auto selfupdate", and that's why I think it would be less confusing to just extend its capabilities instead of creating a new config.

This really is quite different, and most certainly a feature used by many people. Think about developers who are using this on their machines (as opposed to in a CI environment) who don't want to be asked if the next update should/shouldn't be installed. For this very scenario, we have auto-update.

What about this existing config:
# make sdkman non-interactive, preferred for CI environments
sdkman_auto_answer=true|false

Should not it be respected? If it should, there would not be a point for sdkman_auto_selfupdate to exist.

So I believe the optimal solution would be to:

Extend sdkman_auto_answer=true to include the current capabilities of sdkman_auto_selfupdate=true
Change the sdkman_auto_selfupdate config to do what the new config being introduced in this PR would do.

I totally agree with what you are proposing, but the name of sdkman_auto_selfupdate is completely wrong and will confuse many people. What you are describing should be called sdkman_selfupdate_enable. So we should deprecate the old sdkman_auto_selfupdate, favouring the new config and behaviour you proposed.

@marc0der good! I will work on it.

BTW, the "auto" in sdkman_auto_selfupdate refers to the fact that it is an unattended update.

Well, it could be what it was intended to mean, but still auto tends to mean more automatic than unattended.
In context, you can turn on/off the sdkman automatic self-update (sdkman_auto_selfupdate) with true/false.
On the other hand: sdkman_selfupdate_enable has nothing to reference the "automatic" part of the process (and it needs to be referenced, as the normal selfupdate (sdk selfupdate command) will remain functional even though sdkman_selfupdate_enable=false.
Anyway, I'm just discussing to make sure we introduce a good config name to prevent future refactors/breaking changes.

I'm happy with sdkman_selfupdate_enable and will merge your PR once this is in place. However, remember that we need those two sdkman-hooks scripts updated before we can merge this one, and we will need appropriate changes made on the usage page of the website.

@felipecrs any update on this one?

@marc0der I believe all the changes are ready to review.

@marc0der I made the changes. Most of them was due to my lack of attention, while the others I replied you in their own conversation.

@marc0der all done.


Add Imgui-Howto to Wiki including developer notes

First draft: https://github.com/FUSEEProjectTeam/Fusee/wiki/ImGui


Fix a non-deterministic test failure in the task scheduler

We were calling TaskScheduler.schedule inside a Task in TaskSchedulerTests. This means that Swift concurrency could re-order the execution of those tasks and thus change the order in which tasks were enqueued to the TaskScheduler.
Caused by https://github.com/ahoppen/sourcekit-lsp/commit/e295a4e95a2014183f49c421f4f155f550f54230#diff-6a451b3244d65ded9386e2816360b7b1debbe6a519e3795d2046c7dbefa7a7d7R351

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test Windows

@swift-ci Please test Windows

@swift-ci Please test Windows

@swift-ci Please test macOS


Fabo/0.33.0

Closes #2103
Updates to SDK 0.33.0
Improves on local testnet generation and usage. Always sends tokens to a fixed address: "cosmos1ek9cd8ewgxg9w5xllq9um0uf4aaxaruvcw4v9e"
Needs the backend to be updated
Description:

Thank you! 🚀

For contributor:

[ ] Added entries in PENDING.md with issue # and GitHub username
[ ] Reviewed Files changed in the github PR explorer
[ ] Attach screenshots of the UI components on the PR description (if applicable)
[ ] Scope of work approved for big PRs

For reviewer:

[ ] Manually tested the changes on the UI

It's not. Merge conflict. I removed the file again.
Federico Kunze<EMAIL_ADDRESS>schrieb am Sa., 9. März 2019,
19:31:

@fedekunze commented on this pull request.
In app/src/renderer/components/transactions/TmLiAnyTransaction.vue
https://github.com/cosmos/voyager/pull/2225#discussion_r264009447:

@@ -0,0 +1,100 @@
+

We renamed this file to LiAnyTransaction. Why is this being changed ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cosmos/voyager/pull/2225#pullrequestreview-212571893,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFmO2U3DIPobRYRtOKy4c9NaAhMl1sr4ks5vU_4AgaJpZM4bmvpg
.

hmm I still get the error from undelegations:  Error fetching delegations: Cannot read property 'amount' of undefined

@fedekunze could you re-eval please?

none of the actions work

This is still failing: (re)delegation, unbonding, proposals, send, etc

This is still failing: (re)delegation, unbonding, proposals, send, etc

will fix this

Need to check version again. The commit stated 0.32.0. Maybe need to upgrade again.

Karoly was this manually tested ?

@sabau @faboweb this wasn't properly tested and it broke the transactions page


Remove .config.json dependency

This patch allows any user to specify the Google Client parameters via a static method, removing the need to create the .config.json file.
This allows the use of the library to be more dynamic, for instance you can now use it in conjunction with the official Google PHP API, using that one to authenticate instead of the php files included in this library

Looks greats. Thanks! :)


Register as a DRep page needs updating

https://docs.sanchogov.tools/how-to-use-the-govtool/using-govtool/register-as-a-drep Is the old design. Needs updating.

This is completed in gitbook by merge 129