Controlling multiple devices

When I follow the tutorial about controlling multiple devices, hyperion wont work anymore :/
How does controlling multiple devices work? I am trying to control an apa102 led strip and secondly pwm output via pi-blaster. Could someone please help me, I would appreciate it very much.
Thank you for your time!

When I follow the tutorial about controlling multiple devices

Which tutorial? You should ask that person for help?

This tutorial: https://github.com/tvdzwan/hyperion/wiki/Controlling-multiple-devices

Could you start at least one hyperion? What happen if you start the second? Could you start the second?
Note: there is no external grabber support for both at the same time

you must loop the video0(usb grabber) to for example video1, on that virtual videosource you can start multiple times hyperion. i have the exact same problem
found somthing, but couldnt start it
/usr/bin/gst-launch-1.0 v4l2src device=/dev/video0 io-mode=2 ! video/x-raw,format=UYVY, framerate=25/1,width=240,height=192 ! deinterlace ! v4l2sink device=/dev/video1
may it helps you a little bit

Before I followed the steps in the wiki the first one worked fine. Now hyperion isn't workiln at all and to be honest I don't really know why. I have to admit, I am not a professional :/ if I try to start it, it says: "Job for hyperion.service failed. See 'systemctl status hyperion.service' and 'journalctl -xn' for details."
systemctl gives:

hyperion.service - SYSV: Hyperion daemon
Loaded: loaded (/etc/init.d/hyperion)
Active: failed (Result: exit-code) since Thu 2016-02-18 00:52:30 CET; 37s ago
Process: 497 ExecStart=/etc/init.d/hyperion start (code=exited, status=203/EXEC)

I think I might have to start over and reconfigure the first one. (I backed up the config file before I started.) But nevertheless I still need both of them to work.
The grabber is not a problem, for these two I don't really need it, I just want to control the lights via the smartphone app for now.
btw thank you for your quick replies, thats very nice to see :)

yes, people are waiting up to 12 months for feedback ;)
For the moment i could not help you. Cause i never tested. Will see if i could gather more information

Could this be a problem: in the wiki it says where to put the second config file and init.d file. But the files for the first hyperion are actually located somewhere else and there are just links to their locations.
also, I think the command to create a hardlink in the wiki has the source switched with the destination.
Sorry, I am not really that good at these things, but I would love to have it work.
Maybe the author of the wiki article, @ro8in could also help?

@vratixan
Please have a look here, the wiki method is deprecated now
https://github.com/tvdzwan/hyperion/issues/486
Please close this issue, if this fit your needs. We could not.

The pull request #518 regarding issue #486 have also hints how to setup multi led devices

thanks, I'll look into that in a few days. Thank you!

@vratixan   Are you using pi-blaster ?
The code looks buggy to me and im considering fixing it

Yeah, I am using it.
Would be cool if you'd work on that :) keep me up to date if you have any improvements.
thanks

#600
I've made some improvements


Tab support incorrectly copies callouts from other blocks

Overview
As mentioned in https://github.com/spring-projects/spring-framework/issues/29505 and https://github.com/spring-projects/spring-framework/commit/ac7d428a627e6dabbde500266eaeed4670e37bfb, tabs incorrectly include callouts from other blocks within a section of the generated documentation if some blocks use callouts and others do not.
Related Issues

https://github.com/spring-projects/spring-framework/issues/29505

As a side note, I have discovered two workarounds for this.

Include callouts for every pair of primary/secondary blocks within the same section of the documentation (which is what I did for Spring Framework).
Enclose any pair of primary/secondary blocks that do not use callouts in a double-underscore block, like below.

--
[source,java,indent=0,subs="verbatim,quotes",role="primary"]
.Java
----
	@PutMapping("/accounts/{account}")
	public String save(@ModelAttribute("account") Account account) {
		// ...
	}
----

[source,kotlin,indent=0,subs="verbatim,quotes",role="secondary"]
.Kotlin
----
	@PutMapping("/accounts/{account}")
	fun save(@ModelAttribute("account") account: Account): String {
		// ...
	}
----
--

That was a very quick turnaround. Thanks, @wilkinsona! 👍


/net/textproto/reader.go alter c/CanonicalMIMEHeaderKey

Each header field consists of a case-insensitive field name
followed by a colon (":"), optional leading whitespace, the
field value, and optional trailing whitespace.
This PR will be imported into Gerrit with the title and first
comment (this text) used to generate the subject and body of
the Gerrit change.
Please ensure you adhere to every item in this list.
More info can be found at https://github.com/golang/go/wiki/CommitMessage

The PR title is formatted as follows: net/http: frob the quux before blarfing

The package name goes before the colon
The part after the colon uses the verb tense + phrase that completes the blank in,
"This change modifies Go to ___________"
Lowercase verb after the colon
No trailing period
Keep the title as short as possible. ideally under 76 characters or shorter

No Markdown
The first PR comment (this one) is wrapped at 76 characters, unless it's
really needed (ASCII art, table, or long link)
If there is a corresponding issue, add either Fixes #1234 or Updates #1234
(the latter if this is not a complete fix) to this comment
If referring to a repo other than golang/go you can use the
owner/repo#issue_number syntax: Fixes golang/tools#1234
We do not use Signed-off-by lines in Go. Please don't add them.
Our Gerrit server & GitHub bots enforce CLA compliance instead.
Delete these instructions once you have read and applied them

@googlebot  thanks，I signed it!


add logging, docstrings, and process explanation in newMatrics

for logging:

adjust "info" to "warning" or "error" where needed
add "info" for the completion of long tasks like getting the blob data using azcopy

for docstrings:

add simple docstrings for classes and class methods

for readme:

for the processes that you're creating, provide very very brief explanation in the readme explaining what it does, inputs, and outputs

adding arguments and returns to the docstrings and add comments to complex dataframe operations


A Token was not found in the TokenStorage

Im doing an API in Symfony 5 and php 7.4.2
The logi_check works perfect, but when I use the token from my Angular front i have this issue:
[2021-04-09T18:13:40.409817+00:00] security.DEBUG: Guard authenticator does not support the request. {"firewall_key":"api","authenticator":"Lexik\Bundle\JWTAuthenticationBundle\Security\Guard\JWTTokenAuthenticator"} []
[2021-04-09T18:13:40.410123+00:00] security.INFO: An AuthenticationException was thrown; redirecting to authentication entry point. {"exception":"[object] (Symfony\Component\Security\Core\Exception\AuthenticationCredentialsNotFoundException(code: 0):A Token was not found in the TokenStorage . at /Users/rubensanzrosa/PhpstormProjects/GestoriaPastorAPI/vendor/symfony/security-http/Firewall/AccessListener.php:70)"} []
[2021-04-09T18:13:40.410145+00:00] security.DEBUG: Calling Authentication entry point. [] []
Im sending the token in Headers Authentication : Bearer token.
Note: Im not using Apache , im using symfony serve command to run the project from phpStorm .
My security.yaml:
security:
encoders:
    App\Entity\User:
        algorithm: auto
providers:
    user_provider:
        id: App\Security\Core\User\UserProvider
firewalls:

    login:
        pattern:  /api/users/login
        stateless: true
        anonymous: true
        provider: user_provider
        json_login:
            check_path: /api/users/login_check
            success_handler: lexik_jwt_authentication.handler.authentication_success
            failure_handler: lexik_jwt_authentication.handler.authentication_failure
            require_previous_session: false

    api:
        pattern: ^/api
        stateless: true
        guard:
            authenticators:
                - lexik_jwt_authentication.jwt_token_authenticator

access_control:
    - { path: ^/api/users/login, roles: IS_AUTHENTICATED_ANONYMOUSLY }
    - { path: ^/api/, roles: IS_AUTHENTICATED_FULLY }

Your token is either not correctly passed as authorization header to your request, or stripped at some point.

Yes , CORS problems. Is solved Thanks!


White space

Some bits and pieces of white-space and comment things that I noticed.

In commits 2-5 I added changes that I saw in bootstrap that are actually not bootstrap-related but should appear in master regardless. That will reduce the fluff diffs between bootstrap and master for the etc/inc code.

I did a merge to master after the recent thousands of changes in master. It has left this PR with a couple of weird "File mode changed" entries down the end that are certainly not supposed to be there.
I will resubmit the actual relevant stuff in a new clean PR that does not have the long list of commits.

Closed in favor of https://github.com/pfsense/pfsense/pull/1897


Module not found: Can't resolve 'react' in '...node_modules/create-react-context/lib'

I've had isssue:

Module not found: Can't resolve 'react' in '...node_modules/create-react-context/lib'

when trying to import something from 'react-router-dom' package.
I am using also create-react-app with npm.
OS: Linux Mint 19
npm: 6.9.0
node: v10.15.3

Problem solve by remove yarn.lock. We can not have both (package-lock.json and yarn.lock)


Validation Error

I am getting the following error in the validation step: AssertionError: Wrong input shape torch.Size([3, 768, 1024]), expected [1, rgb, H, W]
In marigold_trainer.py function validate_single_dataset(), the input image is being squeezed to a 3 dimensional shape: rgb_int = batch["rgb_int"].squeeze()  # [3, H, W], but in marigold_pipeline.py, it doesn't change the shape if the input is a tensor:
elif isinstance(input_image, torch.Tensor):
            rgb = input_image
else:
            raise TypeError(f"Unknown input type: {type(input_image) = }")
input_size = rgb.shape
assert (
    4 == rgb.dim() and 3 == input_size[-3]
), f"Wrong input shape {input_size}, expected [1, rgb, H, W]"

Fixed.


Initial guesses, minor tweak

removes guessing based on previous angle which could make the results dependent on the input
stabilizes results for small angles (0 degree upwind at high TWS results in negative speed :) )

stabilizes results for high TWS

Unfortunately the solver clearly fails to converge at some angles (not only small ones), and that can't be resolved by the initial guess.

Changed from hybrid to Levenberg-Marquardt algorithm. Convergence seems much more robust.


tf.train.Saver and saver.restore do not work when data_augmentation_options rgb_to_gray and random_vertical_flip are configured in the pipeline config file

Please make sure that this is a bug. As per our
GitHub Policy,
we only address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No (but added a workaround to overcome first issue which will be explained)
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): CentOS Linux 7
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): source
TensorFlow version (use command below): 1.13.2 (also with 1.14.0)
Python version: 3.6.4
Bazel version (if compiling from source): 0.20.0
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:

Describe the current behavior
I am using object detection api and training my model using faster_rcnn_resnet152. Training and evaluation worked fine until I added below data augmentation options in the pipeline config file. The evaluation script (I am using old eval.py on purpose) fails with below error. The error seems to be due to rgb_to_gray option. Pipeline config file has also subtract_channel_mean  and random_horizontal_flip options, however they work fine until the other two configurations are added. To overcome the error I added "reshape=True" argument to saver = tf.train.Saver(variables_to_restore) line in the legcy/evaluator.py line 270 and it started to work if only saver.restore(sess, latest_checkpoint) is commented out in the line 274. When the line is enabled this time it throws the second exception given below. Could you propose a solution/workaround without having to upgrade tensorflow/python etc versions?
data_augmentation_options {
rgb_to_gray {
}
}
data_augmentation_options {
random_vertical_flip {
}
ERROR:1
Assign requires shapes of both tensors to match. lhs shape= [7,7,3,64] rhs shape= [7,7,1,64]
[[node save/Assign_780 (defined at /truba/home/iuzun/Tensorflow/models/research/object_detection/legacy/evaluator.py:270) ]]
Caused by op 'save/Assign_780', defined at:
File "legacy/eval.py", line 149, in
tf.app.run()
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/platform/app.py", line 125, in run
_sys.exit(main(argv))
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/util/deprecation.py", line 324, in new_func
return func(*args, **kwargs)
File "legacy/eval.py", line 145, in main
graph_hook_fn=graph_rewriter_fn)
File "/truba/home/iuzun/Tensorflow/models/research/object_detection/legacy/evaluator.py", line 270, in evaluate
saver = tf.train.Saver(variables_to_restore)
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/training/saver.py", line 832, in init
self.build()
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/training/saver.py", line 844, in build
self._build(self._filename, build_save=True, build_restore=True)
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/training/saver.py", line 881, in _build
build_save=build_save, build_restore=build_restore)
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/training/saver.py", line 513, in _build_internal
restore_sequentially, reshape)
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/training/saver.py", line 354, in _AddRestoreOps
assign_ops.append(saveable.restore(saveable_tensors, shapes))
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/training/saving/saveable_object_util.py", line 73, in restore
self.op.get_shape().is_fully_defined())
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/ops/state_ops.py", line 223, in assign
validate_shape=validate_shape)
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/ops/gen_state_ops.py", line 64, in assign
use_locking=use_locking, name=name)
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/framework/op_def_library.py", line 788, in _apply_op_helper
op_def=op_def)
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/util/deprecation.py", line 507, in new_func
return func(*args, **kwargs)
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 3300, in create_op
op_def=op_def)
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 1801, in init
self._traceback = tf_stack.extract_stack()
InvalidArgumentError (see above for traceback): Restoring from checkpoint failed. This is most likely due to a mismatch between the current graph and the graph from the checkpoint. Please ensure that you have not altered the graph expected based on the checkpoint. Original error:
Assign requires shapes of both tensors to match. lhs shape= [7,7,3,64] rhs shape= [7,7,1,64]
[[node save/Assign_780 (defined at /truba/home/iuzun/Tensorflow/models/research/object_detection/legacy/evaluator.py:270) ]]
ERROR:2
Traceback (most recent call last):
File "legacy/eval.py", line 154, in
tf.app.run()
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/platform/app.py", line 125, in run
_sys.exit(main(argv))
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/util/deprecation.py", line 324, in new_func
return func(*args, **kwargs)
File "legacy/eval.py", line 150, in main
graph_hook_fn=graph_rewriter_fn)
File "/truba/home/iuzun/Tensorflow/models/research/object_detection/legacy/evaluator.py", line 302, in evaluate
eval_export_path=eval_config.export_path)
File "/truba/home/iuzun/Tensorflow/models/research/object_detection/eval_util.py", line 519, in repeated_checkpoint_run
process_metrics_fn=process_metrics_fn)
File "/truba/home/iuzun/Tensorflow/models/research/object_detection/eval_util.py", line 314, in _run_checkpoint_once
restore_fn(sess)
File "/truba/home/iuzun/Tensorflow/models/research/object_detection/legacy/evaluator.py", line 280, in _restore_latest_checkpoint
saver.restore(sess, latest_checkpoint)
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/training/saver.py", line 1312, in restore
err, "a mismatch between the current graph and the graph")
tensorflow.python.framework.errors_impl.InvalidArgumentError: Restoring from checkpoint failed. This is most likely due to a mismatch between the current graph and the graph from the checkpoint. Please ensure that you have not altered the graph expected based on the checkpoint. Original error:
Input to reshape is a tensor with 3136 values, but the requested shape has 9408
[[node save/Reshape_780 (defined at /truba/home/iuzun/Tensorflow/models/research/object_detection/legacy/evaluator.py:270) ]]
Caused by op 'save/Reshape_780', defined at:
File "legacy/eval.py", line 154, in
tf.app.run()
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/platform/app.py", line 125, in run
_sys.exit(main(argv))
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/util/deprecation.py", line 324, in new_func
return func(*args, **kwargs)
File "legacy/eval.py", line 150, in main
graph_hook_fn=graph_rewriter_fn)
File "/truba/home/iuzun/Tensorflow/models/research/object_detection/legacy/evaluator.py", line 270, in evaluate
saver = tf.train.Saver(var_list=variables_to_restore,reshape=True)
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/training/saver.py", line 832, in init
self.build()
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/training/saver.py", line 844, in build
self._build(self._filename, build_save=True, build_restore=True)
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/training/saver.py", line 881, in _build
build_save=build_save, build_restore=build_restore)
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/training/saver.py", line 513, in _build_internal
restore_sequentially, reshape)
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/training/saver.py", line 354, in _AddRestoreOps
assign_ops.append(saveable.restore(saveable_tensors, shapes))
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/training/saving/saveable_object_util.py", line 68, in restore
restored_tensor = array_ops.reshape(restored_tensor, restored_shapes[0])
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/ops/gen_array_ops.py", line 7179, in reshape
"Reshape", tensor=tensor, shape=shape, name=name)
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/framework/op_def_library.py", line 788, in _apply_op_helper
op_def=op_def)
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/util/deprecation.py", line 507, in new_func
return func(*args, **kwargs)
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 3300, in create_op
op_def=op_def)
File "/truba/home/iuzun/anaconda3/envs/tensorflow_cpu1/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 1801, in init
self._traceback = tf_stack.extract_stack()
InvalidArgumentError (see above for traceback): Restoring from checkpoint failed. This is most likely due to a mismatch between the current graph and the graph from the checkpoint. Please ensure that you have not altered the graph expected based on the checkpoint. Original error:
Input to reshape is a tensor with 3136 values, but the requested shape has 9408
[[node save/Reshape_780 (defined at /truba/home/iuzun/Tensorflow/models/research/object_detection/legacy/evaluator.py:270) ]]
Executed command:
python legacy/eval.py --logtostderr --pipeline_config_path=training/faster_rcnn_resnet152_coco.config --checkpoint_dir=training/ --eval_dir=eval/
Thanks in advance

@smeyg,
TensorFlow 1.x is not actively supported. Could you please update TensorFlow to v2.4 and check if you are facing the same issue. Thanks!


Can't select/change Owner/Schema when Change DB-Connenction in Script

When I open a Script and change the connetion from the Toolbar:
I can change the Schema:

Now I change the connetion inside the Script:
I can't chose the schema from the other connetions.

I have filters on the schemas.
Please fix it.
Thank you

Thanks for report


Tool doesn't work

Hi guys,
I downloaded the tool, entered the pity tracker token and started Hearthstone.
I opened two packs, but the tool still only says "Watching for packs..." but not uploading any results.
It doesn't recognize any pack openings.
HS is at C:\Games\Hearthstone\ under Windows 10 x64.
I had to allow the tool in smartscreen, but the firewall didn't aks. Could this be an issue?
Another idea: my environment is German, but I play HS in English.
Is there a log I can inspect?

I guess it is the default path.
I saw this hardcoded in your code: "C:\Program Files (x86)\Hearthstone\Logs\"
You should really put that into a settings file. ;)

Ok I tested my theory and moved HS to C:\Program Files (x86)\Hearthstone
Now its working fine!
You should really put the HS path into a settings file. ;)
I'd like to move it back in my games folder.
And you could test for the path and warn the user, if the expected path/file is not found.

Thank you for the feedback. You identified the problem correctly. It's on our list of things to improve. I'm glad you got it to work.

Can you reopen this as a feature request, so users can track when you've implemented setting the Hearthstone path in the pack-o-bot settings?  Thanks for the great tool by the way.

@nikil We have a pull request already, just haven't had a chance to test it fully. #5

Great - thanks!


doom//update hangs on Proceed?

Here are some things you should try before filing a bug report:
Observed behavior
I tried to run update from inside emacs. I did :doom//update, it started doing its thing, and then it asked me about updating some packages, Proceed? (y or n) and then emacs hangs.
Expected behavior
To update without hanging.
Steps to reproduce

Open Emacs.app
Type : to enter a command
Enter doom//update and hit enter
When Proceed? comes up, try to type y, it doesn't work

System information

Click to expand
- OS: darwin (x86_64-apple-darwin14.5.0)
- Emacs: 26.1 (May 31, 2018)
- Doom: 2.0.9 (develop e497df4a2883d01440e18715d0797f1491a51e95)
- Graphic display: t (daemon: nil)
- System features: NOTIFY ACL GNUTLS LIBXML2 ZLIB TOOLKIT_SCROLL_BARS NS MODULES THREADS
- Details:
  ```elisp
  elc count: 0
  uname -a:  Darwin cyan.fritz.box 18.2.0 Darwin Kernel Version 18.2.0: Thu Dec 20 20:46:53 PST 2018; root:xnu-4903.241.1~1/RELEASE_X86_64 x86_64
  modules:   (:feature eval (evil +everywhere) file-templates (lookup +docsets) snippets :tools flyspell flycheck :feature workspaces :completion company (helm +fuzzy) :ui doom doom-dashboard modeline doom-quit evil-goggles hl-todo nav-flash treemacs (popup +all +defaults) pretty-code vc-gutter vi-tilde-fringe window-select :editor multiple-cursors rotate-text :emacs dired electric :editor fold :emacs imenu vc :tools macos magit rgb :lang data emacs-lisp javascript markdown (org +attach +babel +capture +export +present) (sh +zsh) :config default)
  packages:  n/a
  exec-path: (/usr/local/bin/ /usr/bin/ /bin/ /usr/sbin/ /sbin/ /Library/TeX/texbin/ /usr/local/MacGPG2/bin/ /opt/X11/bin/ /Applications/Emacs.app/Contents/MacOS/bin-x86_64-10_10/ /Applications/Emacs.app/Contents/MacOS/libexec-x86_64-10_10/ /Applications/Emacs.app/Contents/MacOS/libexec/)

</details>

doom//* commands are highly experimental, however, bb9cbfe and ca9a2c8 should resolve this issue. Please update and let me know if that isn't the case and I'll reopen this. Thanks for bringing this to my attention!

fixed indeed. thanks.


Update general.php

I made a mistake in my previous commit 57a331c.
Sorry. I saw that too late. Fixed that.

Thanks. No problem!


Sourceforge error compiling

gsoap seems to have removed it's old versions from sourceforge. I tried replacing the version number with the newer but it still throws the same error. Any ideas?
make[1]: Leaving directory '/root/yi-hack-Allwinner-v2/src/onvif_srvd/onvif_srvd/openssl-1.0.2u'
--2021-02-22 14:34:10--  https://sourceforge.net/projects/gsoap2/files/gsoap-2.8/gsoap_2.8.92.zip/download
Resolving sourceforge.net (sourceforge.net)... <IP_ADDRESS>
Connecting to sourceforge.net (sourceforge.net)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2021-02-22 14:34:11 ERROR 404: Not Found.

--2021-02-22 14:34:11--  https://sourceforge.net/projects/gsoap2/files/oldreleases/gsoap_2.8.92.zip/download
Resolving sourceforge.net (sourceforge.net)... <IP_ADDRESS>
Connecting to sourceforge.net (sourceforge.net)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2021-02-22 14:34:12 ERROR 404: Not Found.

--2021-02-22 14:34:12--  https://master.dl.sourceforge.net/project/gsoap2/oldreleases/gsoap_2.8.92.zip
Resolving master.dl.sourceforge.net (master.dl.sourceforge.net)... <IP_ADDRESS>
Connecting to master.dl.sourceforge.net (master.dl.sourceforge.net)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://downloads.sourceforge.net/project/gsoap2/oldreleases/gsoap_2.8.92.zip [following]
--2021-02-22 14:34:13--  https://downloads.sourceforge.net/project/gsoap2/oldreleases/gsoap_2.8.92.zip
Resolving downloads.sourceforge.net (downloads.sourceforge.net)... <IP_ADDRESS>
Connecting to downloads.sourceforge.net (downloads.sourceforge.net)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2021-02-22 14:34:13 ERROR 404: Not Found.

make: *** [Makefile:223: generated/onvif.h] Error 8

`

Check the last commit:
https://github.com/roleoroleo/yi-hack-Allwinner-v2/commit/f40a94cf68946fb092abac326ef2b0576bbe3c35


[CardRenderer] Memory leaks

Describe the bug
There are 3 spots that are causing memory leaks in the addons library around the CardRenderer.
These are happening because there is state being set without knowledge of whether that parent component is still mounted or not.
To Reproduce
Steps to reproduce the behavior:

Go to full implementation of Dashboard where cards are being rendered and fetching data asynchronously
Unmount the dashboard before the data fully loads
See the errors below

Example of this error here: https://dashboard-dev.connectedproducts.internetofthings.ibmcloud.com/explore/ACME_Robot/summary/ACME_Robot
Expected behavior
There should be no memory leak warnings and the component should first check if the parent components are still mounted before attempting to call the setState's
Environment/versions:

OS: [e.g. MacOS, Windows]
Browser: [e.g. chrome, safari]
carbon-addons-iot-react version: [e.g. v2.60.0]

Additional context

More specifically, these lines are causing the errors:
CardRenderer.jsx https://github.com/IBM/carbon-addons-iot-react/blob/747c6311e0978398a24cb19758c7038b7d8c26d3/src/components/Dashboard/CardRenderer.jsx#L48

Dashboard.jsx https://github.com/IBM/carbon-addons-iot-react/blob/747c6311e0978398a24cb19758c7038b7d8c26d3/src/components/Dashboard/Dashboard.jsx#L310

Specific timeline issues / requests
Do you want this work within a specific time period? Is it related to an
upcoming release?
No specific timeline
NB: The core contributors will try to work with your timeline, but it's not
guaranteed. The earlier you make a request in advance of a desired delivery
date, the better!

I think we can solve the CardRenderer issue with some additional state. Add new boolean isMounted, false by default. Set to true inside the useEffect, set back to false in the cleanup function of the useEffect.
Then wrap the setCard({  in a condition, only setting the state if isMounted === true

Also it would be good to first get a unit test written that reproduces this condition and fails, then we can implement changes with some assurance that the problem is fixed.

Monitor can actually take on this issue if we still plan to deprecate CardRenderer. Can close and I'll reopen on our side


Upcoming deactivation from sensoApp, multiMATIC

I think this is bad for us - correct?
GER:
Mit 31.03.2024 werden alle aktuellen Vaillant-Apps (sensoApp, multiMATIC) deaktiviert.   Sollten Sie nicht bis zum 31.03.2024 umsteigen und ab dem 01.04.2024 ihre Anlage wieder mit dem Internet verbinden wollen, ist eine kostenpflichtige Neuschaffung einer aktuellen Internet-Kommunikations-Box (VR-940f) notwendig.
ENG:
All current Vaillant apps (sensoApp, multiMATIC) will be deactivated on 31.03.2024. After this date, it will no longer be possible to migrate to the myVaillant app. The linked Internet communication box (VR-9XX) of your Vaillant product can then also no longer be updated to the latest firmware and will lose its function. If you do not change over by 31.03.2024 and want to reconnect your system to the Internet from 01.04.2024, you will need to purchase a new, up-to-date Internet communication box (VR-940f).

Any source ?
It's not bad as long as they offer the possibility to migrate before the deadline

https://www.vaillant.at/privatanwender/produkte/mobile-apps/myvaillant-app/

I have gateway VR920 and Multimatic VRC700/6  with app Multimatic and still no get upodate to myVaillant. When i contact with Poland suppoert Vaillant , he tell me that Multimatic should be upgrade also to end 31.03.2024

Yes... i also have the same info.... But first info about update was that should be to 31.12.2023.... now the date was move to 31.03.2024..... ehhhhh Vaillant. In my opinion Multimatic works very very bad.... big loags ans other problems.,

Are you able to get data from your System at the Moment via the Smartphone App? My System is offline... Support dont know why😔

Yes now i have access to get info... But from yesterday i also dont have and have offline,. Today i power off and nthen power on my gateway and works ok.

Thx m8. i made a Reboot again today and now it works...

^^ i know them... lets hope the integration will work after 31.3 :/

I belive that before :)

That will piss me a lot. I just installed a new system and the technician suggested me to use the module Internet VR921. I hope this one will become compatible with the new app.

Does switching to the new app affect this integration in any way?

Does switching to the new app affect this integration in any way?
Btw, even though their wizard clams so, it didn't migrate my existing account. I had to create a new one in the new app. So I guess, I at least need to remove and readd the integration with the new credentials?

did you receive the invitation to migrate? I did not receive anything yet.

Does switching to the new app affect this integration in any way?
Btw, even though their wizard clams so, it didn't migrate my existing account. I had to create a new one in the new app. So I guess, I at least need to remove and readd the integration with the new credentials?

did you receive the invitation to migrate? I did not receive anything yet.

Yeah, I did, but declined it initially, since I was afraid it will mess up this integration.
Now I have a permanent warning in the sensoApp telling me to migrate.
It brings up this wizard, which says it will create a new account... but it doesn't.
First time I clicked "Start update" it just goes to the play store and downloads the new app.
Every subsequent time I click it, it does nothing, flashes something for a second and closes it immediately.
I can create a new account in the new app, and add the device there, with the serial number. But I'm not sure if that is the proper way to do it. And I'd still like to know what will happen with this integration if I switch?

Does switching to the new app affect this integration in any way?
Btw, even though their wizard clams so, it didn't migrate my existing account. I had to create a new one in the new app. So I guess, I at least need to remove and readd the integration with the new credentials?

did you receive the invitation to migrate? I did not receive anything yet.

Yeah, I did, but declined it initially, since I was afraid it will mess up this integration.
Now I have a permanent warning in the sensoApp telling me to migrate. It brings up this wizard, which says it will create a new account... but it doesn't.
First time I clicked "Start update" it just goes to the play store and downloads the new app. Every subsequent time I click it, it does nothing, flashes something for a second and closes it immediately.
I can create a new account in the new app, and add the device there, with the serial number. But I'm not sure if that is the proper way to do it. And I'd still like to know what will happen with this integration if I switch?

I believe I don't receive the invitation because I am using ambisense and it looks it is not yet supported.  Maybe if you migrate you need to use a different plugin in HA:
https://github.com/signalkraft/mypyllant-component

Btw, answer from Vaillant about my question on this subject:
Good morning,
Please note that all our customers will have to migrate to the new myVAILLANT application.
Which means that you too will have to migrate from old (slower) servers to new (faster) servers.
The migration should be completed by the end of January, unless the process is delayed.
You will receive, automatically in the current application, a pop-up message asking you to migrate.
Sincerely,
Technical Helpdesk,
Valiant

Btw, answer from Vaillant about my question on this subject:

How did you contact them?
I've sent an email to<EMAIL_ADDRESS>but got no reply.

Btw, answer from Vaillant about my question on this subject:

How did you contact them? I've sent an email to<EMAIL_ADDRESS>but got no reply.

using their contact form: https://www.vaillant.be/particuliers/contact/question-technique/

Btw, answer from Vaillant about my question on this subject:
Good morning,
Please note that all our customers will have to migrate to the new myVAILLANT application. Which means that you too will have to migrate from old (slower) servers to new (faster) servers. The migration should be completed by the end of January, unless the process is delayed. You will receive, automatically in the current application, a pop-up message asking you to migrate.
Sincerely, Technical Helpdesk, Valiant

Did you ask about Ambisense?

Btw, answer from Vaillant about my question on this subject:
Good morning,
Please note that all our customers will have to migrate to the new myVAILLANT application. Which means that you too will have to migrate from old (slower) servers to new (faster) servers. The migration should be completed by the end of January, unless the process is delayed. You will receive, automatically in the current application, a pop-up message asking you to migrate.
Sincerely, Technical Helpdesk, Valiant

Did you ask about Ambisense?

Yes, waiting their reply

FYI: I got a response from Vaillant on how to migrate.
The instructions in the app are wrong (or at least I misinterpreted them). There is no automatic account creation.
Here are the instructions:
0. There will be an email and App notification when your system is ready to be migrated (I got those already)

Create a new Account in the myVAILLANT app
Login to the myVAILLANT APP
SET up Home (name the gateway and add the gateway serial number
Input the USERNAME and PASSWORD from the OLD SensoAPP account (so the new server can access the old account to transfer the data)
After this the system and gateway firmware will update for 5 to 20 minutes to make the account and system compatible for the new system

Btw, answer from Vaillant about my question on this subject:
Good morning,
Please note that all our customers will have to migrate to the new myVAILLANT application. Which means that you too will have to migrate from old (slower) servers to new (faster) servers. The migration should be completed by the end of January, unless the process is delayed. You will receive, automatically in the current application, a pop-up message asking you to migrate.
Sincerely, Technical Helpdesk, Valiant

Did you ask about Ambisense?

Yes, waiting their reply

Original answer:
je tiens a vous rassurer tout de suite, ca sera compatible avec une passerelle internet qui va devoir migrer vers la nouvelle application.
Si vous acheter une passerelle fonctionnant sur la nouvelle application SANS devoir migrer, ......la ca ne fonctionnera pas.
Les installations ambisense seront les dernières a migrer.
Google translated:
I want to reassure you straight away, it will be compatible with an internet gateway which will have to migrate to the new application.
If you buy a gateway running on the new application WITHOUT having to migrate,......it will not work.
Ambisense installations will be the last to migrate.

I got this response for the Ambisense support from Vaillant

Het klopt dat er voor 31/3/2024 gemigreerd zal worden naar de MyVaillant app.
Er was voorzien dat de Ambisense vanaf eind vorig jaar zichtbaar gingen zijn in de MyVaillant app.
Maar door een aantal problemen is dit nu voorzien voor ten laatste eind februari.
Een exacte datum hebben we momenteel nog niet doorgekregen.

Google translated:

It is true that migration to the MyVaillant app will take place before 31/3/2024.
It was planned that the Ambisense would be visible in the MyVaillant app from the end of last year.
But due to a number of problems, this is now scheduled for the end of February at the latest.
We have not yet received an exact date.

I've successfully migrated to the MyVaillant app.
The SensoApp stops working immediatelly, therefore this integration as well.
I've switched to https://github.com/signalkraft/mypyllant-component, which seems to work fine. Has even more sensors and controls.
However, I do not have any consumption data now!? In the myVaillant app or the mypyllant integration.
I see screenshots online that the myVaillant app should have this, but all that I see on that screen are water pressure and flow temperatures. Did anyone have the same issue? Do I need to do something do enable it, or is this Vaillant punishing migrating customers for some reason?

I switched yesterday. So i could tell something about the problems after the switch-Process.
My Components are: Vaillant VC 15 CS/1-7 ecoTEC exclusive and Vaillant sensoNET VR 921. Until yesterday i´d used this integration. In the Switch-Progress i´d click the update-Button and i think my VR921 got a new software-version only compatible with myvaillant. So... since yesterday i only can use the myvaillant-App. This Integration und the myphyllant-Integration for homeassistant are both not working for me. This integration don´t show my Vaillant-Components anymore and myphyllant don´t show them too. Perhaps a Problem so short after the switch and vaillant has to make some clicks.
I think, i had to the switch to myvaillant... but i´m not happy that my ha-automations don´t work anymore. I hope the best for the future...

I am still waiting for this news from Vaillant. What is a topis this email which you recived ?

I am still waiting for this news from Vaillant. What is a topis this email which you recived ?

First e-mail contained information that migration will be soon, and second e-mail next day announcing that migration was available + notification in the Multimatic app.

FYI: I got a response from Vaillant on how to migrate. The instructions in the app are wrong (or at least I misinterpreted them). There is no automatic account creation.
Here are the instructions:

There will be an email and App notification when your system is ready to be migrated (I got those already)
Create a new Account in the myVAILLANT app
Login to the myVAILLANT APP
SET up Home (name the gateway and add the gateway serial number
Input the USERNAME and PASSWORD from the OLD SensoAPP account (so the new server can access the old account to transfer the data)
After this the system and gateway firmware will update for 5 to 20 minutes to make the account and system compatible for the new system

Btw @thomasgermain do you have any intentions of updating this integration to the new api, or should we all just switch to https://github.com/signalkraft/mypyllant-component? As I've mentioned in another thread, I'm reluctant to do radical changes like these in the middle of the heating season. Really poor timing by Vaillant

myPyllant does not currently support Multimatic 700.

FYI: I got a response from Vaillant on how to migrate. The instructions in the app are wrong (or at least I misinterpreted them). There is no automatic account creation.
Here are the instructions:

There will be an email and App notification when your system is ready to be migrated (I got those already)
Create a new Account in the myVAILLANT app
Login to the myVAILLANT APP
SET up Home (name the gateway and add the gateway serial number
Input the USERNAME and PASSWORD from the OLD SensoAPP account (so the new server can access the old account to transfer the data)
After this the system and gateway firmware will update for 5 to 20 minutes to make the account and system compatible for the new system

Btw @thomasgermain do you have any intentions of updating this integration to the new api, or should we all just switch to https://github.com/signalkraft/mypyllant-component? As I've mentioned in another thread, I'm reluctant to do radical changes like these in the middle of the heating season. Really poor timing by Vaillant

myPyllant does not currently support Multimatic 700.

Could be.
I've made the switch to the new app and myPlyiant, without any issues, with this setup:

boiler ecoTEC plus 30/36CS
main circuit thermostat sensoComfort VRC 720
secondary circuit thermostat VR 92
sensoNET VR 921 module

Everything works fine, had no issues. 2 heating circuits and dhw.
All the controls and sensors are working immidiately.
The consumptions sensors take some time to start pulling data. So either wait a little between switching to the new app (until it populates consumption data) and myPyllant. Or reload myPyllant if you set it up before the data is populated.

I contacted Vaillant last week by email and this is their response:

The sensoAPP and 700 apps are in the process of being upgraded to the myVAILLANT app on a new server.

The migration to the myVAILLANT app currently underway in batches and will be phased in by invitation only.

The app migration should be complete by early 2024, basic system setups first and complex systems (including ambiSENSE and 700 systems from late January to March 24).

As I have ambiSENSE valves I will probably have to wait until March 2024.

The above discussion is not a Home Assistant discussion
Maybe I am wrong. However, is this the right place to discuss the Vaillant App upgrade? I don't think so. This is a Home Assistant bug report place. Saying that, here is my problem:

I upgraded from multiMATIC app to myVAILLANT app.
The Home Assistant Multimatic integration seems not to work anymore.


Last known value is not displayed when time range from grafana does not include the data point when it was created, giving wrong impression

The issue is being faced by many customers in Indiana Mfg Industries. The diagram is self explanatory with two examples.

Hello @kkmeghan: This looks like a potential bug report. Would you be able to provide the below information to help us better troubleshoot?
By providing as much info as possible you help us understand the issue, reproduce it and resolve it for you quicker. Therefore, take a couple of extra minutes to make sure you have provided all info needed.
PROTIP: record your screen and attach it as a gif to showcase the issue.

Use query inspector to troubleshoot issues: https://bit.ly/2XNF6YS
How to record and attach gif: https://bit.ly/2Mi8T6K

What happened:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):

Screenshots

Anything else we need to know?:
Environment:

Grafana version:
Plugin version:
OS Grafana is installed on:
User OS & Browser:
Others:

What happened:
Data not displayed , please see gif file
What you expected to happen:
Data should be displayed
How to reproduce it (as minimally and precisely as possible):
See gif file for a work flow. Data is created on sitewise using MQTT protocal and if the query window does not have data points it is not displayed.
Screenshots
Included
Anything else we need to know?:
Environment:
Grafana version: 8.2.5
Plugin version: 1.3.0
OS Grafana is installed on: Linux
User OS & Browser: Windows and any browser (example chrome)
Others: Issue is already discussed with aws team in length in different meetings. Issue is related to the MQTT protocal and how the data is stored versus how it needs to be visualized

v1.4.0 was just released with a Last Observation toggle in the query editor, which will fall back to the last known value if no data is available in the current time range.

@toddtreece This will work only when atlease one data point is available in the time range selected. Please look into the above screen shot for two below time ranges
1/ 15.22.02 to 15.22.04, there is no data point stored in the back end.
2/ 15.22.13 to 15.32.11,there is no data point stored in the back end.

This will work only when atlease one data point is available in the time range selected

@kkmeghan Sorry, I'm not following what you mean here. The toggle enables a feature that will query for the last known point before the selected time range if the current time range is empty. Could you record a screen capture of the 1.4.0 release with the Last Observation toggle enabled so I could see how that differs from what you were expecting?

@toddtreece @taleena
Please find the link to explore the problem. The below link has sitewise link under 'MeghaAI Features' panel.
https://d33leu70kunhgx.cloudfront.net/d/eSdByEGVk/meghaai-home?orgId=1
Alternatively following link will take you to that particular sitewise dashboard directly.
https://d33leu70kunhgx.cloudfront.net/d/hbfewPnVk/sitewise?orgId=1
This dashboard has two panels , one for historical data and one for aggregated data from sitewise.  Please follow the picture posted  in the beginning with this issue, this picture reflects how the data is populated into the sitewise. DARK blue cell reflect that the data is populated for that time instance and cyan cell reflect the data should be taken from the last known good value.
Please make a note last observation is selected for these two panels.
1/ Time range selected is
from 2022-07-01 15:22:02  To 2022-07-01 15:22:04 , this case works as it fetches two points each with value 220 and Straight line can be seen.
2/ Time range selected is
from 2022-07-01 15:22:02  To 2022-07-01 15:22:08, this case does not work as it only brings '221' in the panel. What should happen is that this query should bring
220(15:22:02), 221(15:22:05), 221(15:22:08)
3/ Please explore different testing cases similarly
will be happy to help in generating and testing new cases

@toddtreece  Hope the above is clear. Please let me know if help needed from our end.

@taleena i think this is similar to #139 and also needs feedback from the AWS SiteWise team

There are more details from discussions logged in #139, closing this as it will be handled in that issue.


[Settings] Changing UI order for File Explorer Add-ons

Changing the order of SettingsCard/SettingsExpander to resolve: #31024
Before:

After:

Before:

After:

PR Checklist

[x] Closes: #31024
[ ] Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
[ ] Tests: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Dev docs: Added/updated
[ ] New binaries: Added on the required places

[ ] JSON for signing for new binaries
[ ] WXS for installer for new binaries and localization folder
[ ] YML for CI pipeline for new test projects
[ ] YML for signed pipeline

[ ] Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments

Validation Steps Performed

Just thinking; a novice contributor might not be aware of the reason. A simple comment would be nice, to prevent this in the future?


Bump version to 4.0

@swift-ci smoke test and merge

You're welcome to go to 3.2 for now, but we need a little more staging to get to 4.0 by default.


TSServer Should Mark Const Arrow Function with 'Function' Kind

From https://github.com/Microsoft/vscode/issues/19401
TypeScript Version:  2.2.1
Code
export var abc = () => x;

abc|

Run completions at the |
Expected behavior:
In completions, abc is marked as a function
Actual behavior:
abc has a const kind:
[Trace - 4:11:51 PM] Sending request: completions (46). Response expected: yes. Current queue length: 0
Arguments: {
    "file": "/Users/matb/projects/sand/c.js",
    "line": 3,
    "offset": 4
}
[Trace - 4:11:51 PM] Response received: completions (46). Request took 2 ms. Success: true
Result: [
    {
        "name": "abc",
        "kind": "const",
        "kindModifiers": "export",
        "sortText": "0"
    }

This differs from navtree which marks abc as a function:
Trace - 4:12:25 PM] Sending request: navtree (57). Response expected: yes. Current queue length: 0
Arguments: {
    "file": "/Users/matb/projects/sand/c.js"
}
[Trace - 4:12:25 PM] Response received: navtree (57). Request took 1 ms. Success: true
Result: {
    "text": "\"c\"",
    "kind": "module",
    "kindModifiers": "",
    "spans": [
        {
            "start": {
                "line": 1,
                "offset": 1
            },
            "end": {
                "line": 3,
                "offset": 4
            }
        }
    ],
    "childItems": [
        {
            "text": "abc",
            "kind": "function",
            "kindModifiers": "export",
            "spans": [
                {
                    "start": {
                        "line": 1,
                        "offset": 18
                    },
                    "end": {
                        "line": 1,
                        "offset": 25
                    }
                }
            ]
        }
    ]
}

I think we are tying to be too smart with the nav-tree. abc is a const, and not a function. the fix here i would say is to undo the nav-tree categorizing variables as functions.

The same goes for const + function expression: const abc = function () { ... }
For tooling usability, able to detect them as functions is valuable.

We don't seem to return function as the kind for export var abc = () => x; any more. However, for export var abc = function f() {}, we will return an item for the function but not for the var. Don't think there's any work to do here.

Related issue that was closed: #25126


wheel: switch to packaging.tags for checking PEP 425 tags

Summary of changes
Update setuptools vendored packaging so the wheel code can be switched to packaging.tags for checking PEP 425 tags compatibility.
Supersede #1822.
Pull Request Checklist

[ ] Changes have tests
[ ] News fragment added in changelog.d. See documentation for details

WIP until a new version of packaging including https://github.com/pypa/packaging/pull/179 is released.

Updated now that packaging 19.2 has been released and ready for merge.


(node:3481) UnhandledPromiseRejectionWarning: TypeError: Cannot read property '1' of null

When trying to download any episode and/or series, crunchyroll-dl crashes with this error:
crunchyroll-dl --quality 1080p --input https://www.crunchyroll.com/kaguya-sama-love-is-war
i crunchyroll-dl v2.0.1
i Attempting to fetch series...
(node:3601) UnhandledPromiseRejectionWarning: TypeError: Cannot read property '1' of null
at main (/usr/local/lib/node_modules/crunchyroll-dl/index.js:588:44)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
(node:3601) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:3601) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
I saw some similar issues posted here, but they were all different, sorry if this is still a duplicate.
I tried downloading just the Crunchyroll link (no quality options etc.), and also logging in with a username and password (successfully logged in), but still get the same error. It happens on any show I try, not just this one. The weird part is that it worked a few weeks ago with no problems, and I haven't changed anything since then.
Here's a screenshot in case I missed anything:

This is caused by the regex that gets de series Id. A quick fix is replacing on index.js, line 586:
    const idDivRegex = /
<\/div>/ // search for a div with an id

with:
const idDivRegex = /<div class="show-actions" group_id="(.*)"/ // search for a div with an id

...although this is also imperfect, as group_id is not necessarily next to the class. A more generic match would be better.

That fixed my issue, thanks so much! Kind of a novice at js so I had no idea what to do


Add social contact buttons in speaker detail page

Currently, the speaker detail page only shows the image, name, title and description. We should also show the Twitter and Website link. Additionally maybe also GitHub.

I have asked SuperSet for the latest version of the booklet so you can copy/paste the final content 👍


sed error

./homebridge.sh build
sed: -e expression #1, char 1: unknown command: `.'
as a consequence of that error, the build process does not install nodejs

I'm having the same issue when building on Linux Mint, I'd appreciate if anyone had a solution for this. Thanks!

Just found a comment in issue #6: removing '.bak' from the sed command in homebridge.sh seems to fix this issue.


Generate explicit build tags when building off of a non-tagged commit

+1 for package/distribution stuff.
Take a look at the changes we discussed to use '|| echo FAIL' on the eunit test case to make sure all tests are run.

One last minor tweak then +1 to merge.


New merge

I had opened the PR by accident.
Have been testing it for a while now, in Belgium we need to limit peak consumption below 2.5kW to avoid an extra cost.
It's been working well, it does "peak shaving" by discharging the battery if load prediction is above 2.5kW (so it makes sure to charge the batteries at the best times).
I can try to work on it during the weekend to merge the latest changes and open a new PR.

Thanks that would be great. Interesting use case for consumption peak shaving.
However, the asked feature request is about peak shaving but for energy production, ie. to limit the kW sent to the grid.
From what I see this is what you implemented in the modifications that you made.


treeNodeWrapperTemplate does not include templates in its ngOutletContext

The ngOutletContext in tree-node-wrapper.component.ts doesn't include the provided templates meaning that attempting to provide an ng-template for the tree node wrapper discards the tree node template.

Merged - will be published soon

Published in 5.2.0

I have same issue, when I apply custom #treeNodeWrapperTemplate my custom #treeNodeTemplate is gone.


[$250] Search - Inconsistency between No tag and No category filters

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: 9.0.56-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause - Internal Team
Action Performed:
Peconditions:
existing account with workspace created, tags are enabled for the workspace and the following expenses are created:

at least one expense with category selected and no tag
at least one expense with tag selected and no category
at least one expense with no tag and no category

Log in with account from preconditions
Click on Search icon in the bottom
Click on Filters, apply filters for 'No category', the tag from preconditions and view results
Verify that only expense matching both filters is displayed
Click on Filters, apply filters for the category from preconditions and 'No tag'
Verify expenses displayed

Expected Result:
Only expenses matching category selected in filters and without tags should be displayed
Actual Result:
All expenses without tags are displayed, category filter is omitted
Workaround:
Unknown
Platforms:

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

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

Screenshots/Videos

Add any screenshot/video evidence

https://github.com/user-attachments/assets/84878378-831e-42b5-ad1f-d4e56eadf76b
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021853546282413139923
Upwork Job ID:<PHONE_NUMBER>413139923
Last Price Increase: 2024-11-04

Issue OwnerCurrent Issue Owner: @jayeshmangwani

@slafortune  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 #wave-control

Either way - you can be left with options that don't pertain if you filter by tags then categories.  While it doesn't have a category, it also doesn't have the proper tag to be included in the filter -

This is a BE issue. The query that we send seems to me like it has the right data in it.
This is what we send to BE for a search wiht no tag but Advertising category type:expense status:all category:Advertising tag:none :
{
    "type": "expense",
    "status": "all",
    "sortBy": "date",
    "sortOrder": "desc",
    "filters": {
        "operator": "and",
        "left": {
            "operator": "eq",
            "left": "category",
            "right": "Advertising"
        },
        "right": {
            "operator": "eq",
            "left": "tag",
            "right": "none"
        }
    },
    "inputQuery": "sortBy:date sortOrder:desc type:expense status:all category:Advertising tag:none",
    "hash": 113990055,
    "offset": 0
}

Maybe we need to provide a different value instead of none when No Tag or No Category is selected?

Proposal
Please re-state the problem that we are trying to solve in this issue.
In Search, there is an inconsistency in the behavior when selecting "No Tag" or "No Category" filters.
What is the root cause of that problem?
1-
https://github.com/Expensify/App/blob/ad0f834b805b763fb5885d2003ca2bdd6e33ff64/src/pages/Search/SearchAdvancedFiltersPage/SearchFiltersCategoryPage.tsx#L20-L24
Initially, searchAdvancedFiltersForm returns "none" for the category when the user selects "No Category."
2-
https://github.com/Expensify/App/blob/afa7b33107747d0242acfd01d032d5339be390d9/src/libs/actions/Search.ts#L139-L141
The issue then arises due to the way jsonQuery is structured when passed to the SEARCH API. For example, the current jsonQuery looks like this:
{
    "type": "expense",
    "status": "all",
    "sortBy": "date",
    "sortOrder": "desc",
    "filters": {
        "operator": "and",
        "left": {
            "operator": "eq",
            "left": "category",
            "right": "Fees"
        },
        "right": {
            "operator": "eq",
            "left": "tag",
            "right": "none"
        }
    },
    "inputQuery": "sortBy:date sortOrder:desc type:expense status:all category:Fees tag:none",
    "hash": 46304472,
    "recentSearchHash":<PHONE_NUMBER>,
    "offset": 0
}

The backend does not interpret "none" consistently, whether it appears in filters or inputQuery.
Additionally, filter order affects the results.
Correct Results occur, for example, when "No Tag" is selected before "Fees" in the category:
type:expense status:all tag:none category:Fees
type:expense status:all category:none tag:"First Tag"
type:expense status:all tag:none merchant:m10

Incorrect Results are returned, for example, when "Fees" is selected before "No Tag":
type:expense status:all category:Fees tag:none
type:expense status:all tag:"First Tag" category:none
type:expense status:all merchant:m10 tag:none

This is the root cause of the inconsistent behavior with "No Tag" and "No Category" filters.
What changes do you think we should make in order to solve the problem?
https://github.com/Expensify/App/blob/afa7b33107747d0242acfd01d032d5339be390d9/src/libs/actions/Search.ts#L139
Replace with
const jsonQuery = JSON.stringify(removeNoneFromTagAndCategory(queryWithOffset));

and add the following function to replace "none" with empty string
function removeNoneFromTagAndCategory(queryObject) {
    if (queryObject.filters?.right) {
        const { left, right } = queryObject.filters.right;
        if ((left === "tag" || left === "category") && right === "none") {
            queryObject.filters.right.right = '';
        }
    }

    if (queryObject.inputQuery) {
        queryObject.inputQuery = queryObject.inputQuery
            .replace("tag:none", "tag:")
            .replace("category:none", "category:");
    }
    return queryObject;
}

What alternative solutions did you explore? (Optional)
Rather than replacing "none" with an empty string, we could reorder the jsonQuery properly before the API call to ensure consistent results. For example:
type:expense status:all tag:none category:Fees
type:expense status:all category:none tag:"First Tag"
type:expense status:all tag:none merchant:m10

Screenshot:

Videos:
Before Change: Correct Results
https://github.com/user-attachments/assets/2020a3cb-1cea-4aa9-ba99-7da481a86472
Before Change: Incorrect Results
https://github.com/user-attachments/assets/20018427-6ea4-48a3-aad4-ad52ef0a1b2c
After Change: All Results are Correct
https://github.com/user-attachments/assets/76785e1b-652a-49e5-b072-5ac7860204c3

@ijmalik Issue appears to be coming from the backend, so it seems internal for now. could you please confirm if the issue is from the FE or BE?

Hi
Front end issue
On Fri, Nov 8, 2024, 11:25 AM Jayesh Mangwani @.***>
wrote:

@ijmalik https://github.com/ijmalik Issue appears to be coming from the
backend
https://github.com/Expensify/App/issues/51828#issuecomment-2456815267,
so it seems internal for now. could you please confirm if the issue is from
the FE or BE?
—
Reply to this email directly, view it on GitHub
https://github.com/Expensify/App/issues/51828#issuecomment-2463875779,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQ6GVN7BPUVH6XHQCXNXITZ7RKN3AVCNFSM6AAAAABQ65FZHOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRTHA3TKNZXHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

@ijmalik I’ve tested filter a few times, and selecting "none" isn’t working correctly and I still think this should be handled on the backend, e.g. why we need to logic like removeNoneFromTagAndCategory in the FE

@jayeshmangwani
I agree, it would be more efficient to handle this on the backend instead of having logic like 'removeNoneFromTagAndCategory' in the frontend.

Issue has been switched to Internal. @slafortune, we’re waiting for an internal engineer to pick this issue, right?

Internal issue and is currently waiting to be pick
cc: @slafortune

Yes - internal hot pick - waiting for an engineer to pick this up

Issue not reproducible during KI retests. (First week)

Hi @mvtglobally,
The issue is still reproducible in specific cases, particularly when the filter order affects the results.
Incorrect Results are returned, for example, when "Fees" is selected before "No Tag":
type:expense status:all category:Fees tag:none
type:expense status:all tag:"First Tag" category:none

Correct Results occur, for example, when "No Tag" is selected before "Fees" in the category:
type:expense status:all tag:none category:Fees
type:expense status:all category:none tag:"First Tag"

Let me know if additional details are needed.
Wrong Filter Result:
https://github.com/user-attachments/assets/fa1e9fac-d02f-4d3b-a149-155e8b377464
Correct Filter Result:
https://github.com/user-attachments/assets/78273b2f-bd5b-4b79-986c-7d785f0f0b83

Waiting for an internal engineer to pick this up.

Same as this
cc: @slafortune

No new update from the last comment 😄

Internal hot pick - waiting for this to be picked up

I'll take a look

Sent PR for review


Adding accentuation (Spanish)

In this commit I add accentuation and I fix some more misspells I missed for the Spanish translation.

lgtm


Incompatible with mkdocs-gen-files plugin

mkdocs-static-i18n v1.0.6 is incompatible with mkdocs-gen-files plugin.
The following warning is emitted for every auto-generated page
WARNING -  mkdocs_static_i18n: Unhandled file case - connection-types-reference/juniper.md

and then, the page is removed from navigation and not being rendered at all.
The root of the problem is in reconfigure.py in the reconfigure_files function. Exactly, in this condition
            if is_relative_to(file.abs_src_path, mkdocs_config.docs_dir):

Files, generated by mkdocs-gen-file have abs_src_path in the temporary directory.  i.e.
File(
    src_uri='connection-types-reference/juniper.md',
   dest_uri='connection-types-reference/juniper/index.html',
   name='juniper',
   url='connection-types-reference/juniper/'
)
abs_src_path=/tmp/mkdocs_gen_files_cg_osgf4/connection-types-reference/juniper.md

As a result, the condition is not satisfied and the file is excluded.
I think we cannot rely on physical file location as the criteria. Maybe
file.is_documentation_page()

is a better criteria?

Just found the same bug affects the mkdocs-material blog plugin as well.


Add a CI test for Hypre Big Int [testing/bernede1/hypre-bigint]

This PR adds:

Build of MFEM with Hypre big int.
Build and run all the tests for that configuration.
Minor changes in the interface with MFEM GitHub actions, leading to a new version for those.

We may not want to run all the tests since most of them are not providing us with relevant information.
However, it seems useful to build all of them to catch potential incompatibilities with BigInt.

Just to check before I start the review -- is this adding a bigint hypre testing to the regular (non-bigint) hypre testing, or is it replacing it?
We want the former, not the latter.

Just to check before I start the review -- is this adding a bigint hypre testing to the regular (non-bigint) hypre testing, or is it replacing it?
We want the former, not the latter.

Confirmed, added a hypre bigint job in addition to the one existing.

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

This will require me to redo the "required" tests in GitHub, so while we are at it, can we change the names from e.g.

ubuntu-18.04-optim-parallel-make-hypre(basic)

to

ubuntu-18.04-make-opt-par-int32

Specifically:

debug ➡ dbg
optim ➡ opt
sequential ➡ ser
parallel ➡ par
basic ➡ int32
bigint ➡ int64

and
${{ matrix.os }}-${{ matrix.target }}-${{ matrix.mpi }}-${{ matrix.build-system }}-hypre(${{ matrix.hypre-target }})
➡
${{ matrix.os }}-${{ matrix.build-system }}-${{ matrix.target }}-${{ matrix.mpi }}-${{ matrix.hypre-target }}

Merged master in to see how the coverage will behave.
I don't get the sudden change of coverage.

Merged in next for testing...


Ports xenomedes' fusion rework

from base BeeStation/BeeStation-Hornet#2614
Dm side changes:
/proc/fusion_ball(datum/holder, reaction_energy, standard_energy)
	var/turf/open/location
	if (istype(holder,/datum/pipeline)) //Find the tile the reaction is occuring on, or a random part of the network if it's a pipenet.
		var/datum/pipeline/fusion_pipenet = holder
		location = get_turf(pick(fusion_pipenet.members))
	else
		location = get_turf(holder)
	if(location)
		if(prob(PERCENT(((PARTICLE_CHANCE_CONSTANT)/(reaction_energy-PARTICLE_CHANCE_CONSTANT)) + 1))) //Asymptopically approaches 100% as the energy of the reaction goes up.
			location.fire_nuclear_particle(customize = TRUE, custompower = standard_energy)
		radiation_pulse(location, max(2000 * 3 ** (log(10,standard_energy) - FUSION_RAD_MIDPOINT), 0))

note: this was actually merged with above


No call to unregisterReceiver() in 3 of 4 examples

A call to unregisterReceiver() is missing in UsbService.java onDestroy() of the following 3 examples:

example
exampleStreams
exampleSync

The 'examplemultipleports' does unregister for each of the detected ports.
I implemented this as shown below:
    @Override
    public void onDestroy() {
        super.onDestroy();
        unregisterReceiver(usbReceiver);
        UsbService.SERVICE_CONNECTED = false;
    }

Failure to unregister throws an exception:
   android.app.IntentReceiverLeaked: Service <snip>.UsbService has leaked IntentReceiver <snip>.UsbService$4@7f31a07 that was originally registered here. Are you missing a call to unregisterReceiver()?

@mws-rmain
Could you do a pull request?


[Bug] Crash on iOS7

i build this project on iOS7, when click button install in Popup, this app will crash, pls fix this

Hi,
could you please post stacktrace of the crash? I don't have any iOS 7 devices to test this.


Update itamaro workers configuration

Remove the fedora worker - with the AWS-hosted ubuntu worker, better stop relying on a laptop running in my home-office
Increase parallel tests for the ubuntu and Windows workers
Add missing branch exclusions to the MacOS worker

Merged


Handle Operation::Remove

Context
Whenever a token uses close action, the account balance row will be erased from the token contract
https://github.com/eosnetworkfoundation/eos-system-contracts/blob/8ecd1ac6d312085279cafc9c1a5ade6affc886da/contracts/eosio.token/include/eosio.token/eosio.token.hpp#L156-L160
Balance must be zero when using close
https://github.com/eosnetworkfoundation/eos-system-contracts/blob/8ecd1ac6d312085279cafc9c1a5ade6affc886da/contracts/eosio.token/src/eosio.token.cpp#L181
known Issue

Attempting to use tables.delete_row("Balance", &key) can result in GraphNode errors if not synced from genesis block since the row could not be created in the first place.

Ideally there is a delete_row_if_exists command that can be used which tells Graphnode to ignore the delete operation if the row exists.

If using create_row instead on Remove operations, can run into an issue of not having the token created in the first place
Precision value of Token doesn't exists on Remove operations since only code & symcode are available

To fix/implement
on Operation::Remove

[x] extract precision using old data
[x] create Token
[x] set balance value to 0
[x] set flag to isDelete true/false

implemented


Added support for payment intents

Backported Payment Intents from Vapor 4 version of StripeKit to support people who are still on Vapor 3 that need Payment Intents to comply with new SCA regulations.

Looks good to me!


Unmarshaling a "null" into a []byte results in an empty slice instead of "nil" (differs from encoding/json)

The following reproducer shows that unmarshaling of a "null" into a byte slice gives a different result than encoding/json. This was also the case with 4d51b8b (before https://github.com/goccy/go-json/pull/198) and does not change with https://github.com/goccy/go-json/pull/200
package main

import (
	"encoding/json"
	"fmt"
	"os"

	gojson "github.com/goccy/go-json"
)

type SomeStruct struct {
	Data []byte
}

func main() {
	original := []byte(`{"Data":null}`)

	validEncodingJSON := json.Valid(original)
	validGoJSON := gojson.Valid(original)

	fmt.Printf("%v vs %v\n", validEncodingJSON, validGoJSON)
	if validEncodingJSON != validGoJSON {
		fmt.Println("ERROR: Unequal \"Valid\" results")

		os.Exit(1)
	}

	var resultEncodingJSON SomeStruct
	if err := json.Unmarshal(original, &resultEncodingJSON); err != nil {
		panic(err)
	}
	resultEncodingJSONString := fmt.Sprintf("%#v", resultEncodingJSON)
	fmt.Println(resultEncodingJSONString)

	var resultGoJSON SomeStruct
	if err := gojson.Unmarshal(original, &resultGoJSON); err != nil {
		panic(err)
	}
	resultGoJSONString := fmt.Sprintf("%#v", resultGoJSON)
	fmt.Println(resultGoJSONString)

	if resultEncodingJSONString != resultGoJSONString {
		fmt.Println("ERROR: Unequal \"Unmarshal\" results")

		os.Exit(1)
	}
}

results in
true vs true
main.SomeStruct{Data:[]uint8(nil)}
main.SomeStruct{Data:[]uint8{}}
ERROR: Unequal "Unmarshal" results
exit status 1

This might be one of the last probems in our regular unit tests @symflower. I kind of think that this is related to https://github.com/goccy/go-json/issues/201 because i guess that there should be a fast-path for when the data is "null".
Since it do not know the code that well i will focus on reproducers for now. Let me know if i should take a deeper look though. Will now investigate a failure in our integration test suite which looks like a different problem.

One of our integration tests went from about ~260seconds to about 210seconds by switching from encoding/json to go-json. Need to further benchmark to get a reliable number but even a 10sec boost is a win on our side. 50seconds would be amazing :-)

@goccy don't know where to post this. I have a successful CI pipeline now with our monorepo. The integration tests where unfortunately not reliable. Improvement ranges in a few seconds. Looks like that we already merged a lot of improvements that migrate away from JSON. However, there are lots of JSON calls left so i added a small benchmark with two typical types of objects so we can track improvements with this package more reliable.
BenchmarkJSON/encoding/json/MarshalSymbol-8<PHONE_NUMBER> ns/op          302392 B/op       1107 allocs/op
BenchmarkJSON/encoding/json/UnmarshalSymbol-8<PHONE_NUMBER> ns/op         1074461 B/op       2529 allocs/op
BenchmarkJSON/encoding/json/MarshalDependency-8               24          45716376 ns/op        14760109 B/op      48882 allocs/op
BenchmarkJSON/encoding/json/UnmarshalDependency-8             16          68107645 ns/op        86285247 B/op     224862 allocs/op
BenchmarkJSON/go-json/MarshalSymbol-8                       1392            810509 ns/op          333393 B/op       1381 allocs/op
BenchmarkJSON/go-json/UnmarshalSymbol-8                     2688            461234 ns/op          493600 B/op       3949 allocs/op
BenchmarkJSON/go-json/MarshalDependency-8                     34          31824248 ns/op        16521427 B/op      61091 allocs/op
BenchmarkJSON/go-json/UnmarshalDependency-8                   28          43814366 ns/op        33977350 B/op     350604 allocs/op
BenchmarkJSON/segmentio/encoding/json/MarshalSymbol-8<PHONE_NUMBER> ns/op          296858 B/op       1106 allocs/op
BenchmarkJSON/segmentio/encoding/json/UnmarshalSymbol-8     1222            945775 ns/op         1073735 B/op       2520 allocs/op
BenchmarkJSON/segmentio/encoding/json/MarshalDependency-8     24          44625790 ns/op        13598500 B/op      48856 allocs/op
BenchmarkJSON/segmentio/encoding/json/UnmarshalDependency-8   19          62479233 ns/op        86288995 B/op     224841 allocs/op

As you can see there is a good improvement and it adds up

@goccy please let me know if you need anything else. I think the changes of  the last days are worth issuing a new release. I will then move the changes into testing on our side. Will let you know if some problem turns up.

Thank you. I'm planning to make a new release today.


More realistic Gravity

The Gravity compontent in crafty seems needlessly crude and unrealistic.

True gravity is a force which works on your velocity but this "gravity" works directly on this._y. This means, no matter what speed you are moving up gravity instantaneously starts moving you down instead of slowing you down.

True gravity works from below. My tests have shown my player will stick to platforms from below, apparently from the side and even inside. I am not using the standard movement components but my own Motion component which has a simple speed method.

Improving item 1 is really simple, 2 perhaps less so. Before I go off and re-invent the wheel, is there a better set of components I should be using for motion and why is Crafty so cra..., I mean crude out of the box in this respect?

fixed with #708 .


Update pixelit to 1.1.3

Please update my adapter ioBroker.pixelit to version 1.1.3.
This pull request was created by https://www.iobroker.dev c0726ff.

1.1.3 created 6.11.2023


GCP Cloud Storage Bucket with Laravel Spatie

Discussed in https://github.com/austintoddj/canvas/discussions/1373

Originally posted by ABC2015 November  1, 2023
Hi Community:
Wanted to confirm that use the GCP storage bucket using Laravel Spatie for GCP cloud storage works as expected.  Having some trouble getting images to POST based on the network request we are seeing.
//Config below**
'storage_disk' => env('CANVAS_STORAGE_DISK', 'gcs'),
'storage_path' => env('CANVAS_STORAGE_PATH', 'public/canvas'),

'upload_filesize' => env('CANVAS_UPLOAD_FILESIZE', 1048576),

//General Storage Bucket
'gcs' => [
'driver' => 'gcs',
'key_file_path' => env('GOOGLE_CLOUD_KEY_FILE', null), // optional: /path/to/service-account.json
'project_id' => env('GOOGLE_CLOUD_PROJECT_ID', 'your-project-id'), // optional: is included in key file
'bucket' => env('GOOGLE_CLOUD_STORAGE_BUCKET', 'your-bucket'),
'path_prefix' => env('GOOGLE_CLOUD_STORAGE_PATH_PREFIX', ""), // optional: /default/path/to/apply/in/bucket
'storage_api_uri' => env('GOOGLE_CLOUD_STORAGE_API_URI', null), // see: Public URLs below
'visibility' => 'private', // optional: public|private
'metadata' => ['cacheControl' => 'public,max-age=86400'], // optional: default metadata
],
ISSUE:
Essentially the application post request to google cloud apis does not seem to be placing the file in the right path.

Video of Issue
https://app.screencast.com/dFyxElAfDPBvB
https://app.screencast.com/a1GGu1I3FpL2j
Any suggestions would be helpful.

Hi @austintoddj - hope the week is progressing well - Just wanted to confirm whether it's the intention to have gcp spatie OOTB (https://github.com/spatie/laravel-google-cloud-storage) integrated - unless we missed something in the docs) - or should we do the wiring ourselves?  We have done this in our other Laravel applications - just wanted to get confirmation one way or the other - thanks in advance.

Hi @ABC2015. I haven't tried integrating that package and Canvas. It seems like it should work out of the box, given that it's a pretty generic storage driver.
The URL being returned is that path to the uploaded file, as seen in the upload method here:
public function store()
{
    $payload = request()->file();

    if (! $payload) {
        return response()->json(null, 400);
    }

    // Only grab the first element because single file uploads
    // are not supported at this time
    $file = reset($payload);

    $path = $file->store(Canvas::baseStoragePath(), [
        'disk' => config('canvas.storage_disk'),
    ]);

    return Storage::disk(config('canvas.storage_disk'))->url($path);
}

What's the payload of the first screenshot (POST request to /api/uploads) above?

Hi @austintoddj
https://app.screencast.com/Ft01eBio64W1j  (Parsed)
 (Sourced Payload)

@austintoddj uploaded the payload - in this case - the path for the uploads vs what's the actual gcp storage does not match from our test - which results in the image not being found.

@austintoddj we ended implementing it in a different manner.  So we'll close this out.

No worries - all good.


Cleaning

I'll probably revert the alignment changes in the import area but other than that this looks good. Thanks for the improvements. I'm guessing I'll be needing to get in the habit of using hlint.

@noprompt >I'll probably revert the alignment changes in the import area
That's mechanical output. I recommend getting in the habit of using a tool like stylish-haskell to do your indentation. Takes less time. Like go fmt.

@bitemyapp I just noticed I forgot to merge this today. My apologies. If you haven't already deleted the branch I'd like to merge it.


Complete test for Asn.1

Add tests to increase coverage, import (and adapt where necessary) the unit tests from ext/openssl for the ASN.1 class.

May I take this?

May I take this?

Yes, please, knock yourself out ;)

Yes, sir!

Hmm... I'm not sure, but in the light that our spec suite is much more exhaustive than OpenSSL's unit tests, I think we can close this issue. Please reopen it if you think otherwise.


[CLI]: UserWarning: The torch.cuda.*DtypeTensor constructors are no longer recommended

Describe the bug

Using wandb 0.15.9 on python 3.10.12 with torch 2.1.0.dev20230825+cu118, I get the following notice. (It's not an exception: the program continues running.)

wandb.init(
    project=f'{PROJECT}',
    sync_tensorboard=True,
    notes=MODEL_PREFIX,
    config={
        'lr': LEARNING_RATE,
        'model_version': net.VERSION,
    }
)
tbwriter = SummaryWriter(f'runs/{MODEL_PREFIX}') # Must come after wand init

#[training loop]
tbwriter.add_scalar('training_loss', training_loss, epoch)

/opt/conda/lib/python3.10/site-packages/wandb/wandb_torch.py:193: UserWarning: The torch.cuda.*DtypeTensor constructors are no longer recommended. It's best to use methods such as torch.tensor(data, dtype=*, device='cuda') to create tensors. (Triggered internally at ../torch/csrc/tensor/python_tensor.cpp:83.)
  check = torch.cuda.FloatTensor(1).fill_(0)

Additional Files
No response
Environment
WandB version:
0.15.9
OS:
Debian 11
Python version:
3.10.12
Versions of relevant libraries:
torch 2.1.0.dev20230825+cu118
Additional Context
No response

@carbocation Thanks for opening the issue, will be fixed for the next release!

WandB Internal User commented:
kptkin commented:
@carbocation Thanks for opening the issue, will be fixed for the next release!

UserWarning: The torch.cuda.*DtypeTensor constructors are no longer recommended. It's best to use methods such as torch.tensor(data, dtype=*, device='cuda') to create tensors.
I still got the warning with wandb-0.16.1.

UserWarning: The torch.cuda.*DtypeTensor constructors are no longer recommended. It's best to use methods such as torch.tensor(data, dtype=*, device='cuda') to create tensors.
I still got the warning with wandb-0.16.1.

@Hambaobao could you please provide a small repro. based on the reporting the line that was emitting the warning was removed in 0.15.10


configure torrentio

How to configure torrentio utility, when I click on configure but it keeps asking to open stremio client application

ask torrentio how to configure it. not sure why you are asking here.


upgrade http link to https

No response from author for over 30 days. Closing.
Please feel free to reopen.
/close


[nodejs] Add test cases for roisensor

Impacted tests(approved): new 20, update 0, delete 0
Unit test platform: Ubuntu 16.04
Unit test result summary: pass 20, fail 0, block 0

@haoyunfeix PTAL


create a mockup for the entire app

As there are no mockups for the app. Please create mockups for the app.
Its better to include the following pages for  UI
Login
Home
Signup
Events

I want to work on this issue. I am intetested in designing pages for the app @algokun

I would also like to work on this. @algokun

what is  mockups?

@smaranjitghose could you please check this issue?

@algokun if you can collab with the others who are making the  Home,Events,Achievements,Team  and Contact Us page and the mentors for some insight  into the actual  content..i don't  mind having this as a official  issue


Extend Text tool by bold, italic, subscript and superscript support

It is necessary to enhance current plain text editor tool by adding the following functionality:

There is a possibility to change a style to bold and italic, make subscript and superscript
User can change the styles while text typing or/and by select a substring and applying styles

Issue blocked by #144

Either subscript or superscript button should be selected at the same time.
Current behavior:


Add entity version number to trails schema

Since OpenTrailMap now fetches the current OSM feature when you select something, we need to know if the current feature matches the one in the tiles. The way to do this would be to include the OSM entity version number as an attribute, but I'm not sure if this possible in Planetiler.
https://github.com/osmus/OpenTrailMap/issues/21

Done over at osmus/tileservice.


Fix Linux tests of Travis

@msabramo Any idea what would be a good way to resolve this? Now we're getting nasty failures. Example of a failure: https://travis-ci.org/bebraw/pypandoc/jobs/52296424 . Pandoc is giving pandoc: Unknown reader: markdown+strikeout.
Can we benefit from http://docs.travis-ci.com/user/build-configuration/#Installing-Packages-Using-apt ?

Oups, this is now handled in #45 and fixed in PR #46

Yeah, safe to close.
I'll have a look at those failing Pyflakes cases.

Awesome! I would've suggested downloading a new pandoc and @JanSchulz did it, which is awesome!