The lidar_centerpoint package can not download model automatically due to LIB_TORCH NOT FOUND

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I'm convinced that this is not my fault but a bug.

Description
lidar_centerpoint model can not download model automatically due to LIB_TORCH NOT FOUND
Expected behavior
lidar_centerpoint model can download model automatically
Actual behavior
lidar_centerpoint model can not download model automatically due to LIB_TORCH NOT FOUND
Steps to reproduce
ros2 launch tier4_perception_launch perception.launch.xml mode:=lidar
output is :
[WARNING] [launch_ros.actions.node]: Parameter file path is not a file: /autoware/install/lidar_centerpoint/share/lidar_centerpoint/config/default.param.yaml
Versions
ROS2
Possible causes
No response
Additional context
No response

Thank you for reporting this, but please wait for https://github.com/autowarefoundation/autoware.universe/pull/480 to be merged.

@xczhanjun https://github.com/autowarefoundation/autoware.universe/pull/480 is merged, but the detected objects of lidar_centerpoint isn't published because of other problem.
Please try the link, to use lidar_centerpoint.


publish<EMAIL_ADDRESS>

Requested by: @relaxolotl
Merge target: (default)
Quick links:

View changes
View check runs

Assign the accepted label to this issue to approve the release.
Leave the #retract comment under this issue to retract the release (original issuer only).
Targets

[ ] github
[ ] registry
[ ] gcs

Targets marked with a checkbox have already been executed.  Administrators can manually tick a checkbox to force craft to skip it.

- Uploading asset "sentry-native.zip" to getsentry/sentry-native:0.4.17
[debug] POST /repos/getsentry/sentry-native/releases/65043191/assets?name=sentry-native.zip& - 500 in 231ms

Hm, is the upload failing? Or craft not retrying it or just getting stuck?

Filed https://github.com/getsentry/craft/issues/384


Document missing Callable methods

Documents:

Callable.hash()
Callable.is_custom()
Callable.is_null()
Callable.is_standard()

I updated the descriptions and added the remaining as well.

applied suggestions and rebased.

I forgot to stage my changes 🤦. It's done now.

Thanks!


Doesn't disappear 'No records' when have a data

Describe the bug
I have a data from server or from client but this 'No records' doesn't disappear
To Reproduce

Just very light component
Expected behavior
Need to disappear 'No records' when have a data
Screenshots

Desktop (please complete the following information):

OS: Macos
Browser Arc

Hey, @hitfm00, this can happen if you forgot to import the CSS.
See this discussion in Q&A here: https://github.com/icflorescu/mantine-datatable/discussions/456
And the docs page here: https://icflorescu.github.io/mantine-datatable/styling/

Hey, @hitfm00, I'm going to close this for now as I suspect it's just a matter of forgetting to import the CSS.
Please feel free to reopen if the problem persists after you've made sure to properly import the styles (see my comment above).

Hey, @icflorescu, I will check later, thx for the answer


add known issue for 1.5.4 [#166766934]

Signed-off-by: Jeremy Alvis<EMAIL_ADDRESS>

Thank you!


为什么生成的视频经常是动画风格？Why are generated videos often animated?

I am using Comfyui with cogvideoX-Wrapper node to generate video，the prompt is 'A monkey and a tiger are driving a roadster,realistic style.'，however，the result is anime style. the model I use is CogVideo 5B
I expect the video is realistic style, could you give me a favor?

I believe you need refine the prompt, as mentioned in the convert_demo.py from the repository. Here’s an example:
“In a scene that defies reality, a realistic portrayal unfolds of a monkey, donning a classic driver’s cap and goggles, at the wheel of a sleek, red roadster. Beside him, a majestic tiger, with its striking stripes and a pair of aviator sunglasses, sits coolly in the passenger seat. The unlikely duo cruises down an open coastal highway, the wind ruffling their fur as the sun casts a golden glow over the horizon. The level of detail in their fur, the shine of the car’s paint, and the realistic scenery around them bring an extraordinary sense of realism to this whimsical and captivating tableau.”
I believe this approach can more effectively solve your problem.

I believe you need refine the prompt, as mentioned in the convert_demo.py from the repository. Here’s an example:
“In a scene that defies reality, a realistic portrayal unfolds of a monkey, donning a classic driver’s cap and goggles, at the wheel of a sleek, red roadster. Beside him, a majestic tiger, with its striking stripes and a pair of aviator sunglasses, sits coolly in the passenger seat. The unlikely duo cruises down an open coastal highway, the wind ruffling their fur as the sun casts a golden glow over the horizon. The level of detail in their fur, the shine of the car’s paint, and the realistic scenery around them bring an extraordinary sense of realism to this whimsical and captivating tableau.”
I believe this approach can more effectively solve your problem.

it worked, thanks for your help! I understand how to write prompt.

a

Supposed I would like to do the opposite i.e. using an anime style or let's say a cinematic style, what is the guidance?


sw_engine: rearrange the blending mechanism.

Revised the blending mechanism by rearrange alpha value range from 0 to 256.
This is more clear than previous 255 alpha value range approach
because tvg uses bit-operation for faster results.
In the sequence, it divides alpha values by 256, it'd have chance to lose the value by 1
during 255 / 256. And then accumulated result brings the a bit different coloring.

@hermet In this branch I still see the difference in color, that I mentioned in #231, so I'm not sure how much do we gain by these changes.
It's a bit hard to read, because we have alpha and opacity, both in the range 0-255, but later we change the range only for the alpha to be 1-256 (_colorAlpha always returns values > 0).
I think that the lower value of this range (1 instead of 0) is problematic. Lets take alpha mask - we need to call the ALPHA_BLEND(destination, 256-alpha). This alpha is always at least 1, so in result this acts as before, when it was 255-alpha.
Also please notice, that if the arguments of the ALPHA_MULTIPLY are: one in the range 0-255 and the second one 1-256, then the result, after dividing by 256, is still in the range 0-255, and when this value goes to the ALPHA_BLEND, nothing really changes and it works as before this patch.

closed by this https://github.com/Samsung/thorvg/pull/231


Enable 'termbidi' for gnome-terminal 3.34

Gnome terminal in gnome 3.34 supports bidi text rendering/typing. It'd be nice if 'termbidi' is enabled on it automatically.

Hedayat Vatankhah wrote:

Gnome terminal in gnome 3.34 supports bidi text rendering/typing. It'd
be nice if 'termbidi' is enabled on it automatically.

Does this terminal always work in this mode, or is it something that can
be enabled and disabled?
How do we check the terminal is at this version?
--
A hamburger walks into a bar, and the bartender says: "I'm sorry,
but we don't serve food here."
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

It always works. Or... at least in Fedora it is enabled by default as far as I see (I've not done any special configuration).
But I don't know how to check the version or if it is possible at all; but I hope so. :( ...
OK, I found it! It is actually not about gnome-terminal alone, it is about any VTE based terminal (I'm not aware of any other though :P). Anyway, you can check VTE_VERSION environment variable.
My VTE_VERSION is 5800, (vte version 0.58.0). But according to https://mail.gnome.org/archives/gnome-announce-list/2019-July/msg00003.htmlhttps://mail.gnome.org/archives/gnome-announce-list/2019-July/msg00003.html, it should work on vte >= 0.57.3, which is probably VTE_VERSION >=  5730.

More generally, I think this feature request falls under the title of "Automatic detection for termbidi". Vim Arabic shaping support via :set arabicshape is currently enabled by default regardless of the terminal. This causes the problems explained in https://github.com/vim/vim/issues/9761.
It made sense to set this option the default when most terminals did not have shaping support and it was up to the console applications to provide proper rendering. Currently, however, most terminals already support Unicode shaping, so it would be better for Vim to be smarter instead of assuming the default.
I think there should be some library function (perhaps wcwidth?) that could inform Vim whether the terminal has letter shaping capabilities.

I found a workaround for this issue: https://github.com/neovim/neovim/discussions/29227
It needs some manual work, but makes vim automatically detect whether to set termbidi or not. It has a strange side effect.

Please share the essential settings to enable this here. The neovim issue talks about some lua configurations that are not valid for Vim.

It's super simple. It basically moves setting the termbidi choice from Vim to an environment variable TERMBIDI.
if !empty($TERMBIDI)
    set termbidi
endif

And that variable is set within the launcher for the terminal. E.g: by adding something like this in /usr/share/applications/gnome-terminal.desktop
Exec=env TERMBIDI=1 /bin/gnome-terminal

@chrisbra If this is to be implemented, then the clean way is to query the terminal Bidi support info the same way terminal color support is queried (vim uses ncurses I presume?)
@tonymec answer here https://github.com/vim/vim/issues/7116 suggests that Vim already has this autodetection functionality and it is applied when TERM=mlterm is set. This makes vim :set termbidi by default when mlterm is detected.
There are more Bidi capabilities explained by Freedesktop BiDi in Terminal Emulators proposal, and I sent a request to ncurses mailing list to include them.


Apply MagicMethodTypeHintsPass to interfaces

Resolves #661
Just expanded on the work done in #585 by making sure that MagicMethodTypeHintsPass looks at interfaces as well as the class and modifying the tests to look at both the class and the interface cases.

Coverage increased (+0.04%) to 76.016% when pulling 6f28ec8c814e6d07cb680c17984d84e3c327ec23 on nCrazed:master into 89f77081d6eba6274b290c3fcc09f58be94d3a8a on padraic:master.

Coverage increased (+0.04%) to 76.016% when pulling ebf4cbec8bc177213d55ebf22b7789b046e24e14 on nCrazed:master into 89f77081d6eba6274b290c3fcc09f58be94d3a8a on padraic:master.

Looks great, thank you.


Embeddings Not Matching

I am extracting embeddings using the image-data and their corresponding embeddings, but when I compare these embeddings they are very similar to each other even if faces are different

@sbmalik did you do face alignment before extracting? If not, please follow readme to do alignment and try again. :-)

Should I have to change nvinfer to something else for main.py to use your custom plugin?

@sbmalik  nope,  just compile the custom plugin and make install it. It is modified on the top of nvinfer, so it is basically the same as nvinfer. make install will replace nvidia official nvinfer.

I tried but it is not working, I'll check further and let you know

@zhouyuchong it's still not working, I've to change
NvDsMetaList * l_user = object_meta->frame_user_meta_list;
to
NvDsMetaList * l_user = object_meta->obj_user_meta_list;
to compile custom plugin in gstnvinfer.cpp:2223 as the error was object_meta has no member 'frame_user_meta_list'. But still not working
all the embeddings still output distance/similarity with very minor difference

@sbmalik  Hi, I've add some new codes in 'custom-nvinfer' to support license plate recognition. So maybe there are some errors. Can you try using retinaface as pgie and remove yolov5? My current pipeline looks like this: retinaface->tracker->arcface, I've tested locally and it works fine:
root@huanxu:/opt/nvidia/deepstream/deepstream-6.1/sources/python_apps/kbds/test# python3 cal_sim.py
[[0.04977836]]
[[0.22057416]]
[[-0.04537255]]
[[0.35562442]]
[[0.01244287]]
[[1.]]
[[0.05409411]]
[[0.25204449]]
[[0.06085228]]
[[0.26436458]]

Or you can wait some time, I'm still working on this. I'll get you noticed when done.
Sorry for all these matters, I have to say it is a tough job since I'm working on my own. :crying_cat_face:

okay I'll try on it, can you please confirm if make is still working on custom plugin. without error of object_meta has no member frame_user_meta_list

@zhouyuchong I checked after removing the yolov5 and it's working a lot better now...

@zhouyuchong I checked after removing the yolov5 and it's working a lot better now...

glad to hear that.
because the *custom-gst-nvinfer' now can do alignment correctly if the landmarks are generated by a pgie, where lmks are in frame meta. There are some problems if lmks in object_meta, I'm trying to find out the reason.

@zhouyuchong Thank you for your help, kindly tell me one thing, for face verification which distance metric you are using?

I'm using the same method as tensorrtx, here

Thank you for solving this issue. Kindly let me know when you resolve issue for lmrk in sgie...

hey shifu @zhouyuchong i make file sucessfully and then i have libnvdsgst_infer.so. How to use gst-infer-custom of you for face-align on deepstream-face-recognition ?
I run file main.py , i get an problem: Unknown or legacy key specified 'alignment' for group [property]
Unknown or legacy key specified 'user-meta' for group [property]

after compile it, use
make install

to replace the old one. However, I strongly recommend to have a backup for original gst-nvinfer.


clementine: added switches for optional dependences

Added switches for ipod, mtp, cd and cloud support.
The switch for ipod support, specifically, allows users to build it without libplist, wich is marked as insecure.
Motivation for this change
issue #23696
Things done

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

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

I have actually Tested using sandboxing and using nix-shell -p clementine --run "clementine-review wip", but these methods seem to ignore nixpkgs.config.clementine.ipod = false; in my configuration.nix, so i get the same result i got before my changes, an error stating that libplist-1.12 is marked as insecure.

Good approach, I'd like to reinstall clementine. Trying it out ...
BTW, have you tried setting the config into your ~/.nixpkgs/config.nix?

Could you set the default for clementine.ipod to false? Since that's what's breaking the build, currently.

No problem, i didn't know if it was better to maintain the defaults to current values, i'll change it.
Thanks to you!

I tested it again with clementine.ipod = false; in ~/.nixpkgs/config.nix, and sandboxig works as expected, but nix-shell -p clementine --run "clementine-review wip" still complains about libplist-1.12, even with false as the default value.
I wonder if i'm doing something wrong there.
Also, the build is still not working, and i have no idea why.

That's because nix-shell -p clementine tries to shell into the clementine package, which still comes from your system profile.
You probably wanted nix-shell -p nox ... to shell into the nox package, where you can run e.g. nox-review wip in a nixpkgs checkout, to audit uncommited changes.

Lol thanks, i completely misunderstood it. i'm going to read about it and try it, thanks!


TimeoutError: There are still unapplied migrations after 60 seconds

Hi,
I have done the setup of airflow 2.0.2 using helm chart in AKS. (https://artifacthub.io/packages/helm/airflow-helm/airflow).
I have configured external postgresql with airflow, but after the connection of external DB pods are not coming up.
NAME                                                                READY   STATUS
pod/apache-airflow-scheduler-5c9f99cbf7-d798b   0/1     Init:1/2
pod/apache-airflow-scheduler-7d4859d696-r4ljg   0/1     Init:1/2
pod/apache-airflow-web-798656c9ff-75fhf         0/1     Init:CrashLoopBackOff
pod/apache-airflow-web-7d7d9ddf8-mc542          0/1     Init:CrashLoopBackOff
I am getting below logs from wait-for-db-migrations container,
[2021-05-27 16:43:39,574] {migration.py:163} INFO - Context impl PostgresqlImpl.
[2021-05-27 16:43:39,575] {migration.py:170} INFO - Will assume transactional DDL.
[2021-05-27 16:43:43,947] {providers_manager.py:299} WARNING - Exception when importing 'airflow.providers.microsoft.azure.hooks.wasb.WasbHook' from 'apache-airflow-providers-microsoft-azure' package: No module named 'azure.storage.blob'
[2021-05-27 16:43:44,566] {providers_manager.py:299} WARNING - Exception when importing 'airflow.providers.microsoft.azure.hooks.wasb.WasbHook' from 'apache-airflow-providers-microsoft-azure' package: No module named 'azure.storage.blob'
[2021-05-27 16:43:45,655] {db.py:601} INFO - Waiting for migrations... 1 second(s)
[2021-05-27 16:43:46,661] {db.py:601} INFO - Waiting for migrations... 2 second(s)
[2021-05-27 16:43:47,668] {db.py:601} INFO - Waiting for migrations... 3 second(s)
[2021-05-27 16:43:48,674] {db.py:601} INFO - Waiting for migrations... 4 second(s)
[2021-05-27 16:43:49,680] {db.py:601} INFO - Waiting for migrations... 5 second(s)
[2021-05-27 16:43:50,688] {db.py:601} INFO - Waiting for migrations... 6 second(s)
[2021-05-27 16:43:51,697] {db.py:601} INFO - Waiting for migrations... 7 second(s)
[2021-05-27 16:43:52,703] {db.py:601} INFO - Waiting for migrations... 8 second(s)
[2021-05-27 16:43:53,708] {db.py:601} INFO - Waiting for migrations... 9 second(s)
[2021-05-27 16:43:54,714] {db.py:601} INFO - Waiting for migrations... 10 second(s)
[2021-05-27 16:43:55,722] {db.py:601} INFO - Waiting for migrations... 11 second(s)
[2021-05-27 16:43:56,730] {db.py:601} INFO - Waiting for migrations... 12 second(s)
[2021-05-27 16:43:57,736] {db.py:601} INFO - Waiting for migrations... 13 second(s)
[2021-05-27 16:43:58,742] {db.py:601} INFO - Waiting for migrations... 14 second(s)
[2021-05-27 16:43:59,747] {db.py:601} INFO - Waiting for migrations... 15 second(s)
[2021-05-27 16:44:00,752] {db.py:601} INFO - Waiting for migrations... 16 second(s)
[2021-05-27 16:44:01,758] {db.py:601} INFO - Waiting for migrations... 17 second(s)
[2021-05-27 16:44:02,763] {db.py:601} INFO - Waiting for migrations... 18 second(s)
[2021-05-27 16:44:03,768] {db.py:601} INFO - Waiting for migrations... 19 second(s)
[2021-05-27 16:44:04,773] {db.py:601} INFO - Waiting for migrations... 20 second(s)
[2021-05-27 16:44:05,785] {db.py:601} INFO - Waiting for migrations... 21 second(s)
[2021-05-27 16:44:06,800] {db.py:601} INFO - Waiting for migrations... 22 second(s)
[2021-05-27 16:44:07,807] {db.py:601} INFO - Waiting for migrations... 23 second(s)
[2021-05-27 16:44:08,812] {db.py:601} INFO - Waiting for migrations... 24 second(s)
[2021-05-27 16:44:09,818] {db.py:601} INFO - Waiting for migrations... 25 second(s)
[2021-05-27 16:44:10,824] {db.py:601} INFO - Waiting for migrations... 26 second(s)
[2021-05-27 16:44:11,829] {db.py:601} INFO - Waiting for migrations... 27 second(s)
[2021-05-27 16:44:12,834] {db.py:601} INFO - Waiting for migrations... 28 second(s)
[2021-05-27 16:44:13,838] {db.py:601} INFO - Waiting for migrations... 29 second(s)
[2021-05-27 16:44:14,844] {db.py:601} INFO - Waiting for migrations... 30 second(s)
[2021-05-27 16:44:15,849] {db.py:601} INFO - Waiting for migrations... 31 second(s)
[2021-05-27 16:44:16,856] {db.py:601} INFO - Waiting for migrations... 32 second(s)
[2021-05-27 16:44:17,860] {db.py:601} INFO - Waiting for migrations... 33 second(s)
[2021-05-27 16:44:18,869] {db.py:601} INFO - Waiting for migrations... 34 second(s)
[2021-05-27 16:44:19,898] {db.py:601} INFO - Waiting for migrations... 35 second(s)
[2021-05-27 16:44:20,909] {db.py:601} INFO - Waiting for migrations... 36 second(s)
[2021-05-27 16:44:21,915] {db.py:601} INFO - Waiting for migrations... 37 second(s)
[2021-05-27 16:44:22,920] {db.py:601} INFO - Waiting for migrations... 38 second(s)
[2021-05-27 16:44:23,936] {db.py:601} INFO - Waiting for migrations... 39 second(s)
[2021-05-27 16:44:24,942] {db.py:601} INFO - Waiting for migrations... 40 second(s)
[2021-05-27 16:44:25,947] {db.py:601} INFO - Waiting for migrations... 41 second(s)
[2021-05-27 16:44:26,952] {db.py:601} INFO - Waiting for migrations... 42 second(s)
[2021-05-27 16:44:27,956] {db.py:601} INFO - Waiting for migrations... 43 second(s)
[2021-05-27 16:44:28,961] {db.py:601} INFO - Waiting for migrations... 44 second(s)
[2021-05-27 16:44:29,967] {db.py:601} INFO - Waiting for migrations... 45 second(s)
[2021-05-27 16:44:30,972] {db.py:601} INFO - Waiting for migrations... 46 second(s)
[2021-05-27 16:44:31,977] {db.py:601} INFO - Waiting for migrations... 47 second(s)
[2021-05-27 16:44:32,982] {db.py:601} INFO - Waiting for migrations... 48 second(s)
[2021-05-27 16:44:33,987] {db.py:601} INFO - Waiting for migrations... 49 second(s)
[2021-05-27 16:44:34,992] {db.py:601} INFO - Waiting for migrations... 50 second(s)
[2021-05-27 16:44:35,999] {db.py:601} INFO - Waiting for migrations... 51 second(s)
[2021-05-27 16:44:37,004] {db.py:601} INFO - Waiting for migrations... 52 second(s)
[2021-05-27 16:44:38,009] {db.py:601} INFO - Waiting for migrations... 53 second(s)
[2021-05-27 16:44:39,021] {db.py:601} INFO - Waiting for migrations... 54 second(s)
[2021-05-27 16:44:40,027] {db.py:601} INFO - Waiting for migrations... 55 second(s)
[2021-05-27 16:44:41,032] {db.py:601} INFO - Waiting for migrations... 56 second(s)
[2021-05-27 16:44:42,038] {db.py:601} INFO - Waiting for migrations... 57 second(s)
[2021-05-27 16:44:43,043] {db.py:601} INFO - Waiting for migrations... 58 second(s)
[2021-05-27 16:44:44,048] {db.py:601} INFO - Waiting for migrations... 59 second(s)
[2021-05-27 16:44:45,052] {db.py:601} INFO - Waiting for migrations... 60 second(s)
Traceback (most recent call last):
File "/home/airflow/.local/bin/airflow", line 8, in
sys.exit(main())
File "/home/airflow/.local/lib/python3.6/site-packages/airflow/main.py", line 40, in main
args.func(args)
File "/home/airflow/.local/lib/python3.6/site-packages/airflow/cli/cli_parser.py", line 48, in command
return func(*args, **kwargs)
File "/home/airflow/.local/lib/python3.6/site-packages/airflow/cli/commands/db_command.py", line 54, in check_migrations
db.check_migrations(timeout=args.migration_wait_timeout)
File "/home/airflow/.local/lib/python3.6/site-packages/airflow/utils/db.py", line 598, in check_migrations
raise TimeoutError(f"There are still unapplied migrations after {ticker} seconds.")
TimeoutError: There are still unapplied migrations after 60 seconds.

@nike4122 Is the post-install XX-upgrade-db job finishing successfully?
You check the status of the job resources with kubectl get jobs --namespace XX.
Otherwise, its possible that your DB is really slow (and the migration is taking a while) so we might need to increase the timeout passed to airflow db upgrade -t XX.

Same issue here. Chart version 8.1.3. default values.yaml file
Looks like the job is never created:
➜ k get jobs -n airflow
No resources found in airflow namespace.

In my case I had to set helmWait: true
https://github.com/airflow-helm/charts/blob/main/charts/airflow/values.yaml#L3

@thesuperzapper  Somehow this issue resolved after I removed existing DB then connected to a fresh airflow setup.
But now I am facing a different issue, when I trigger a DAG job worker pod is failed to start and throwing an error
$ kubectl get po -n airflow
NAME                                                   READY   STATUS    RESTARTS   AGE
apache-airflow-scheduler-5c9f99cbf7-457pb              1/1     Running   103        16h
apache-airflow-web-7d7d9ddf8-8hbpf                     1/1     Running   3          16h
helloworldhellotask.757795a7562d4ed5b6feb5821d3fa0d5   0/1     Error     0          10h
$ kubectl logs helloworldhellotask.757795a7562d4ed5b6feb5821d3fa0d5 -n airflow
/entrypoint: line 109: BACKEND: unbound variable
I am using
CHART_VERSION=8.1.3
KubernatesExecutor
Airflow - 2.0.2

@nike4122 what are your values?

@thesuperzapper This issue has been resolved after we put '%40' instead of @ in the username,
the user of the external database

user: airflow_user%40postgres
Thank you for your support!

I am facing the same issue after updating from airflow image 2.0.1-py3.8 to 2.1.2-py3.8.

[2021-07-20 12:19:18,815] {db.py:619} INFO - Waiting for migrations... 58 second(s)
[2021-07-20 12:19:19,818] {db.py:619} INFO - Waiting for migrations... 59 second(s)
[2021-07-20 12:19:20,821] {db.py:619} INFO - Waiting for migrations... 60 second(s)
Traceback (most recent call last):
File "/home/airflow/.local/bin/airflow", line 8, in
sys.exit(main())
File "/home/airflow/.local/lib/python3.8/site-packages/airflow/main.py", line 40, in main
args.func(args)
File "/home/airflow/.local/lib/python3.8/site-packages/airflow/cli/cli_parser.py", line 48, in command
return func(*args, **kwargs)
File "/home/airflow/.local/lib/python3.8/site-packages/airflow/cli/commands/db_command.py", line 54, in check_migrations
db.check_migrations(timeout=args.migration_wait_timeout)
File "/home/airflow/.local/lib/python3.8/site-packages/airflow/utils/db.py", line 613, in check_migrations
raise TimeoutError(
TimeoutError: There are still unapplied migrations after 60 seconds. Migration Head(s) in DB: {'82b7c48c147f'} | Migration Head(s) in Source Code: {'a13f7613ad25'}

There is no job listed in the namespace for the db upgrade. I am using an external postgres db, not the one baked into the airflow image.

I check the check-db init container and it shows a successful connection to the postgres db.

After trying to figure this out, it finally resolved. I use fluxcd for helm installs. I did a rollback and at some point it successfully ran the db migration. I then made an update, rollback, etc. And after the last update it was successful. I also tried an update to chart 8.4.1, but helm barfed on not being able to update the clusterip spec in one of the deployments, or sts'. I revertedf to 8.0.9 since it has been successful in the past. SMH.

@cocampbe I am planning to remove the upgrade-db Job altogether, and replace it with a Deployment, the Job has caused many issues, see issue https://github.com/airflow-helm/charts/issues/317 for more the proposal.

@nike4122, I never considered a special character in the db username, but I have raised an issue https://github.com/airflow-helm/charts/issues/318, to automatically encode it for users.
But be warned, you will need to revert it to its un-encoded form in externalDatabase.user once this update happens (I will put a warning in the changelog).

@cocampbe BTW, the unpatchable issue with the upgrade-db Job is fixed in 8.5.0, as we have replaced the (unpatchable) Job with a (patchable) Deployment called db-migrations.
I am interested to see if your other issues are resolved.
PS: it's also worth looking into 8.5.0 for PgBouncer

@cocampbe BTW, the unpatchable issue with the upgrade-db Job is fixed in 8.5.0, as we have replaced the (unpatchable) Job with a (patchable) Deployment called db-migrations.
I am interested to see if your other issues are resolved.
PS: it's also worth looking into 8.5.0 for PgBouncer

I finally got to use 8.5.1 today. And I upgraded to airflow 2.2.2. The update went well. I did not enable pgbouncer, but will look into that later. The only issue I had was that some data in one of the  tables apparently had bad data. I  think that is an airflow feature, not the helm chart. I just wanted to get back to you on this. Thanks for your help.


Accept salt keys before orchestration will start

After change, bsc#1043592 Add support for accepting nodes
all salt keys for nodes have to be accepted, we don't auto accept
them any more.

I've tested it with
kubic:~/terraform # export LATEST_IMAGE=true; export FLAVOUR=caasp; contrib/libvirt/k8s-libvirt.sh apply

with changes from https://github.com/kubic-project/terraform/pull/68/commits/6309e3080339640b32c376c9186f39a8c102079b


Support using extension behind proxy server

Repro steps:

Action: appService.Deploy
Error type: ECONNRESET
Error Message: read ECONNRESET
Version: 0.9.0
OS: win32

As of right now we don't support being behind a proxy.
We would have to add support for these properties:
http.proxy
http.proxyStrictSSL
http.proxyAuthorization

Extension support for proxies has been recently added in VS Code insiders. You're welcome to try it out. See here for more info: https://github.com/Microsoft/vscode-azure-account/issues/27#issuecomment-441998815
I'll leave this open for tracking

Closing this as VS Code released proxy support for extensions:
https://code.visualstudio.com/updates/v1_31#_network-proxy-support-for-extensions


Accessibility traits + labels

There are two open pull requests that never made it into master:

https://github.com/xmartlabs/XLPagerTabStrip/pull/323
https://github.com/xmartlabs/XLPagerTabStrip/pull/410

I improved on the work that has been done there by making the accessibility traits work for all components/configurations included in the framework. Additionally I added the label as a property to IndicatorInfo, so that users can set accessibility labels when they are using only icons. If they are not specifying a an accessibility label, it will default to the title.

@CodeStage Thanks for contributing!


You should consider adding at least one example and/or codepen

"The in-view attribute must contain a valid AngularJS expression to work" ->
<any in-view="doShit($inview)"></any>

?

+1

I kind of agree but there are examples in the examples folder of the repository.

This is test line #{{$index}}


Can't find enum type!

Thank you for this fantastic template.
I'have defined a enum but can't find at client side. I have tried all possible solution suggested on this forum.
I'm using visual studio 2015 update 2. Serene version <IP_ADDRESS>
TS file is also created after "transfer All T4 tempaltes" but still cant find enum.
Can some one please help.
Thanks.

see https://github.com/volkanceylan/Serenity/issues/1131

Check that the namespace is set correctly for the enum, then go ahead and rebuild followed by transform. At times, it's just that the namespace is misspelled or such.

Thanks.
It was a name space issue. By applying correct name space and enum key fixed issue.

I have the same issue.  I am using Serenity report template to build report criteria screen.  One of the control on the screen would be the combo box that uses enum for the dropdown list.  However, I cannot get this enum key set right.  throws an error saying cannot find the enum key.  I am assuming its the path that it cannot find.  But I cannot figure out the correct path.
How did you set the path?

I am getting the same error!  Not able to figure out what's going on.  Trying to use the enum type for the combo box dropdown list on a report criteria screen that uses the Serenity report template.
Followed the same procedure as in the tutorial to create the .cs file where I define the enums.  However, I am using their report template and not sure what else I have to do to make it work with the template.  I transformed ALL T4 templates and rebuilt the project as well.  No luck.
Would appreciate any clue on this!
Thanks.

I'm not sure about report template as I used only for form dialog type script and on forms.


Migrate wiki to markdown files as part of the repository

The idea is to migrate the wiki to markdown files, so they are included as part of other websites cloning this repository, such as Software Heritage.

wiki is not used in this repository


api: fix offline dependency goherokuname

goherokuname is no longer used by api then you can safely remove from glide


Add upgrade info to counter extension

You might have already been doing this, but if not, here's a pass at it.

Codecov Report

Merging #394 into @invertase/scheduledcounter will not change coverage.
The diff coverage is n/a.

@@                     Coverage Diff                      @@
##           @invertase/scheduledcounter     #394   +/-   ##
============================================================
  Coverage                        39.96%   39.96%
============================================================
  Files                               19       19
  Lines                              633      633
  Branches                            84       84
============================================================
  Hits                               253      253
  Misses                             378      378
  Partials                             2        2

@Ehesp I just noticed that the "billingRequired" field is set to false, it should be changed to true when we make this change.


swift/2.0

Thanks @CalmMartin

It looks like this merge failed. Could you provide a description of what you are changing. Thanks!


Proxy problem

Description
In my environment, an http proxy is used to access external websites, while docker is inside my network.
My jvm automatically setup proxy system properties and then docker-client try to use proxy to access docker.
How to reproduce
Setup http.proxyHost system property to a proxy that cannot access docker (or to a wrong address)
What do you expect
I'd like to decide if proxy has to be used or not, using for example http.nonProxyHosts system property.

Looks like Jersey's ClientProperties doesn't have anything corresponding to a "non-proxy hosts" property.
See #771 for how the proxy support was implemented. Perhaps one solution here could be to add a method to the DefaultDockerClient.Builder to disable the proxy behavior that is enabled if http.proxyHost is set.

fixed by https://github.com/spotify/docker-client/pull/819


luci-mod-system: add config option to invert heartbeat trigger

Depends on https://github.com/openwrt/openwrt/pull/10358
Fixes #5911

With inverted as flag, compared to invert that you had in your first branch (which I initially used :p) it obviously didn't work; however naturally, with the proper flag, it works perfectly. So we just need to get https://github.com/openwrt/openwrt/pull/10358 merged. However, it needs still 6 reviewers :S

is now merged; so this can go in too :)

@oliv3r done


does i18n with named parameters work in .vue template?

Hey,
I just tried something like this:
<EText>{{ $t('email.verify.greeting', { username: 'abc' }) }}</EText>

And the greeting message is something like Hi, {username}, and I expect the result would be Hi, abc, but I can only get Hi, .
It seems the $t with named parameters is not work in vue template?

what library ? nuxt ? or compiler ?

what library ? nuxt ? or compiler ?

Hey @Flowko, thanks for your reply. I tried both nuxt and compiler, and the results are the same.
And I also tried the same message outside of vue template:
const t = await useTranslation(event);
console.log(t('email.verify.greeting', { username: 'abc' }));

It works fine in this way.

okay thanks, will take a look


Add search bar in loot tracker plugin

I would like to see a search bar in the loot tracker plugin to search/filter on specific monsters.

Really nice feature, hope PR #11042 can get an update, it used to work well at one point
Useful when your mate asks how'd you get so many nature runes, for example


Fix redirect after deleting org

What does this PR do?
Fixes https://github.com/appwrite/appwrite/issues/7736, https://github.com/appwrite/console/issues/1030
Test Plan
Deleting an org with another org:
https://github.com/appwrite/console/assets/1477010/baf46c82-5993-4d38-9b4a-df36db257c06
Deleting an org without any other orgs:
https://github.com/appwrite/console/assets/1477010/0261fbb0-8718-46ab-afb0-b4ba7f70951d
Related PRs and Issues

https://github.com/appwrite/appwrite/issues/7736
https://github.com/appwrite/console/issues/1030

Have you read the Contributing Guidelines on issues?
(Write your answer here.)

For the case where there's still another org, there's a flash (most noticeable on the org user avatar) , is it possible to avoid that?

@abnegate, what did you mean by:

the org user avatar

The avatar at the top right of the console?

Oh, you mean the avatar at the bottom left of the organization card?
Probably not because it's an image that needs to load

@stnguyen90 Looks like it loads, disappears, then loads again, and the placeholder is not in the same position as the loaded image


TEST-#0000: use custom Distributed

What do these changes do?

In the custom version of this Distributed, we remove the call of self._get_computation_code(), which is called in submit->_graph_to_futures. _get_computation_code takes about 75% of the total call time of submit function and it looks like it's just collecting additional information that might not be collected in a non-debug mode. With this change, Dask tests are faster than Ray tests. It is interesting to try to propose to implement a mechanism that disables the call to this function in Distributed library itself.

[x] first commit message and PR title follow format outlined here

NOTE:  If you edit the PR title to match this format, you need to add another commit (even if it's empty) or amend your last commit for the CI job that checks the PR title to pick up the new PR title.

[ ] passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
[ ] passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
[ ] signed commit with git commit -s
[ ] Resolves #?
[ ] tests added and passing
[ ] module layout described at docs/development/architecture.rst is up-to-date

@anmyachev this looks very promising. Should we try contributing this to dask?

@anmyachev this looks very promising. Should we try contributing this to dask?

@mvashishtha I think we should at least suggest introducing an environment variable that would regulate the collection of information using _get_computation_code function. For Modin, this could only be enabled in debug mode.
I don't have time yet, but if someone has the opportunity, then he can start doing right now :)

Okay, I filed https://github.com/dask/distributed/issues/7740 with dask/distributed

@anmyachev how did you measure how long _get_computation_code took? Some dask tests, like  MODIN_ENGINE=DASK python -m pytest -n 2  modin/pandas/test/dataframe/test_indexing.py, are excruciatingly slow in CI as well as on my laptop.

@anmyachev how did you measure how long _get_computation_code took? Some dask tests, like  MODIN_ENGINE=DASK python -m pytest -n 2 modin/pandas/test/dataframe/test_indexing.py, are excruciatingly slow in CI as well as on my laptop.

IIRC ran a full set of tests on Dask with https://pypi.org/project/pytest-profiling/.


Broken color on mat-button when using a variable

Describe the bug
Hi guys, I'm Matt currently working on IPM 2.
I've got a bug to report.
When passing the color of a mat-button as variable [color]="warnAsVariavle", the style is not applied as the attribute is not present in the dom.  This does not occur when passing directly a string to the attribute.
What is the expected behavior?
What are the steps to reproduce?
Demo on stackblitz
Environment
Reproduced with the latest BLUI version (6.3.0)
Anything else to add?
BTW, the stackblitz demo in the readme is currently broken, the style is not applied correctly.

Looking more into this issue, it seems to be a limitation of angular.  Here's a code snippet that I've been playing around with:
<button mat-button [color]=" condition ? 'accent' : 'primary'"></button>

I've read on stack overflow that it should be possible to pass in color as an @Input just like in the example above, but I've never seen it working.
I would suggest as an alternative to have multiple buttons (e.g. one for 'primary' and another for 'warn').


Consider specifying optional dependency on MsQuic

URL(s)
https://packages.microsoft.com/
Description
Since .NET 7, we officially support HTTP/3 (it's by default turned on). Our implementation of QUIC and HTTP/3 depends on https://github.com/microsoft/msquic. This dependency must be manually installed in Linux machines from packages.microsoft.com,  see https://learn.microsoft.com/en-us/dotnet/fundamentals/networking/quic/quic-overview#linux.
I suggest we specify this dependency (as optional) in the published dotnet runtime packages on packages.microsoft.com.
cc @rzikm @wfurt @CarnaViire @karelz

is there such thing as optional dependency? Is there precedent you are aware of @ManickaP ?

https://www.debian.org/doc/debian-policy/ch-relationships.html#binary-dependencies-depends-recommends-suggests-enhances-pre-depends 'Suggests' would fit the bill.
https://docs.fedoraproject.org/en-US/packaging-guidelines/WeakDependencies/#_weak_dependencies 'Weak' dependency, or even just a 'Hint'.


feat(component): Add a mean for components to access raw key events

Description
This adds an is_editing method to components for whether they should receive all key inputs or just the regular actions.
Why
Currently, there is no way for a component to take user input.

Sure! I'm building a markdown tasks parser and manager. I wanted to add a search bar and therefore needed to get user input.
Here is how it turned out =)
https://github.com/user-attachments/assets/a8c7cf3e-4efc-4443-a32e-5e25395ad8c8

that looks pretty! looking forward to the new releases, I want to package it for Arch 🐻

I defer to @kdheepak for whether this is the right idea. I'm not too familiar with this template.

I think this is a good reference PR! Thanks for making it. I'm not sure if we should merge it though, because the component template is already more complex than I'd like for a template and severely under-documented.

Your review was correct, I think this new version is cleaner. It allows a component to set specific actions to be escaped in editing mode.

I think this is a good reference PR! Thanks for making it. I'm not sure if we should merge it though, because the component template is already more complex than I'd like for a template and severely under-documented.

I agree with you, I'm happy with the template and did not have to change it a lot beside this "can't access raw keys" issue. But it was not a "ready to jump in" template for me, especially for a first Ratatui app, it took me some time to get comfortable with it.


README: rewrite to explain design better

Codecov Report

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

@@           Coverage Diff           @@
##           master       #9   +/-   ##
=======================================
  Coverage   93.11%   93.11%
=======================================
  Files           4        4
  Lines         334      334
=======================================
  Hits          311      311
  Misses         23       23

Continue to review full report at Codecov.

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


adding ALEDA Coin token.

Please note: This repository is being rebuilt to accept the new volume of token additions and modifications. PR merges will be delayed.

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address:
Token Name:
Token Symbol:
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token:
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Auto merge requirements
Your pull request will be automatically merged if the following conditions are met:

Your pull request only adds new tokens to the list. Any modification to existing
tokens will require manual review to prevent unwanted modifications.

Your pull request does not touch unrelated code. In particular, reformatting changes to unrelated
code will cause the auto merge to reject your PR.

Any asset files added correspond to the token address you are adding. Asset files
must be PNG, JPG or SVG files.

Your change is valid JSON and conforms to the schema. If your change failed validation,
read the error message carefully and update your PR accordingly.

No other tokens shares the same name, symbol or address.

For example, this change would be rejected due to unrelated changes:

The bot runs every 60 minutes and bulk-merges all open pull requests to prevent conflicts.
This means that you need to wait up to 60 minutes for your pull request to be merged or reprocessed.

@AlexDanielC can you take a look at your current entry?
When you view the file, the <3 you used is now displayed as a \u003c3
Now when anyone else decides to update the token-list via Node API (writeFile) it converts your entry to the <3 as well, blocking the automerge since now we have an edited line (and it does not belong to us)

Can you please update this entry? You can use an emoji heart probably.


test(integration): re-enable some tests by renaming their filename

Summary
It seems some of the test files are not ending with a _spec suffix in their file names.
Thus maybe they're not tested for a long time...
Checklist

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

Full changelog

re-enable some tests by renaming their filename

Rename the following spec files as they seems useful:

spec/01-unit/19-hybrid/04-negotiation_spec.lua
spec/02-integration/04-admin_api/12-plugins-conf_spec.lua
spec/02-integration/09-hybrid_mode/08-lazy_export_spec.lua
spec/02-integration/11-dbless/03-config_persistence_spec.lua
spec/03-plugins/26-prometheus/06-hybrid-mode_metrics_spec.lua

Delete one spec file as it seems deprecated

spec/02-integration/04-admin_api/18-worker-events.lua (There was an age when worker-events is a plugin? interesting)

Add an action step in Lint, Doc and Unit tests to check spec files spelling.
Check for a preview result here: https://github.com/Kong/kong/actions/runs/3640443596/jobs/6145235361

Not merging quite this moment because CI is currently :x: for master, but as far as I'm concerned it's good to merge once that is taken care of.


Integration Test - Release - 2018/11/21 08:10:39

Auto create for integration test. AnotherAuthorUpdatedArticleFlow

@PRMergerTest1 : Thanks for your contribution! The author, @v-caxian, has been notified to review your proposed change.


Some new paths can be unavailable

Some new paws in function createNewDirForFile from Paths.h. Can be unavailable.
Example:
file = /home/utbot/.opam/4.08.0/share/sail/lib/sail.c
oldBase = /home/utbot/sail-riscv/c_emulator/SoftFloat-3e/build
newBase = /home/utbot/tmp/UnitTestBot/sail-riscv
result = home/.opam/4.08.0/share/sail/lib/sail.c
result not in temp directory.
Problem arise because we use relative paths to build a temporary directory structure.

linked with issue-52

createNewDirForFile has not been touched in issue-52


Could not read path<EMAIL_ADDRESS>

[x] Review the documentation: https://facebook.github.io/react-native
[x] Search for existing issues: https://github.com/facebook/react-native/issues
[x] Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment
Run react-native info in your terminal and paste its contents here.
React Native Environment Info:
    System:
      OS: Windows 10
      CPU: x64 Intel(R) Core(TM) i3-2310M CPU @ 2.10GHz
      Memory: 1.43 GB / 7.91 GB
    Binaries:
      Yarn: 1.12.1 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
      npm: 6.4.1 - C:\Program Files\nodejs\npm.CMD
    IDEs:
      Android Studio: Version  <IP_ADDRESS> AI-181.55<IP_ADDRESS>56338

Description
I want to build APK release from React Native project. Unfortunately, I got this error.
Starting a Gradle Daemon, 1 incompatible and 3 stopped Daemons could not be reused, use --status for details

FAILURE: Build failed with an exception.

* What went wrong:
Failed to capture snapshot of input files for task ':app:bundleReleaseJsAndAssets' property '$1' during up-to-date check.
> Could not read path<EMAIL_ADDRESS>
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Reproducible Demo
Create new React Native project with react-native-cli, for example:
react-native init sampleApp
cd sampleApp/android && gradlew assembleRelease

I assume you tried ./gradlew clean and restarting your computer? I find Gradle's caches can cause strange behavior often not worth debugging without trying the above.

I just execute gradlew clean only, not restart the computer, Mr @bartolkaruza .

Not yet @YanmaY .

<EMAIL_ADDRESS>
This bit looks wrong, but I can't figure out where that path is configured. The variable is not substituted and I think the parser should be at \node_modules\.bin\parser instead of inside @babel.  Could you post a log of ./gradlew assembleRelease --info?

I solved the problem by revert yarn to version 1.9.4 just now @YanmaY

I also encountered this. Seems to be a problem with newer Yarn versions on Windows.

<EMAIL_ADDRESS>is OK @achmadk @thomanau

I have downgraded yarn version to 1.10.1 then it works. Thank you @YanmaY .

I think this problem has been fixed at yarn v1.12.3. You can update to recent version or keep installed yarn version to 1.10.1.

@achmadk why did you re-open this issue? Is there something on React Native side that still needs to be changed? If not, you can close this as resolved; people will find your solution (upgrade yarn) through Google regardless of the issue being closed.

sorry for inconvenience @bartolkaruza . I will close this issue.

@achmadk  @tronginc  How to install yarn version 1.10.1

I have the same issue when i run ./gradlew assembleRelease

Could not read path<EMAIL_ADDRESS>


LSTM numerical gradient check

Haven't been able to figure out what's going on here... With the new LinearBias I can get one step to give the correct gradient, but as soon as I have multiple steps weird stuff starts happening. The numerical gradients are generally much, much larger (1e3 vs. 1e-3). Any ideas as to what is happening?
nn = require 'nn'
require 'rnn'
require 'optim'

hiddenSize = 2
nIndex = 2
r = nn.LSTM(hiddenSize, hiddenSize)

rnn = nn.Sequential()
rnn:add(r)
rnn:add(nn.Linear(hiddenSize, nIndex))
rnn:add(nn.LogSoftMax())

criterion = nn.ClassNLLCriterion()

function f(x)
  parameters:copy(x)
  -- Do the forward prop
  rnn:zeroGradParameters()
  -- With or without fastBackward doesn't matter
  r.fastBackward = false
  local err = 0
  for i = 1, inputs:size(1) do
     local output = rnn:forward(inputs[i])
     err = err + criterion:forward(output, targets[i])
     local gradOutput = criterion:backward(output, targets[i])
     rnn:backward(inputs[i], gradOutput)
  end
  r:backwardThroughTime()
  r:forget()
  return err, grads
end

parameters, grads = rnn:getParameters()

-- This works:
-- targets = torch.Tensor{1}:resize(1, 1)
-- inputs = torch.randn(1, 2)

targets = torch.Tensor{1, 2}:resize(2, 1)
inputs = torch.randn(2, 2)
local err, dC, dC_est = optim.checkgrad(f, parameters:clone())
-- Print the exact and numerical gradients side by side
print(torch.cat(dC:view(dC:size(1), 1), dC_est:view(dC_est:size(1), 1), 2))
assert(err < 0.0001, "failed")
print("passed")

So strangely enough I'm finding that the forward prop of the LSTM contains significant randomness for steps greater than one. I added print statements in LSTM's updateOutput function, printing input and self.output, and some runs I get things like this:
in      -1.6971157419033        0.95369546810918
out     -0.0532725412628        -0.0054331652498848

in      -1.6971157419033        0.95369546810918
out     -0.025895731412077      -0.080890936582261

in      -1.6971157419033        0.95369546810918
out     0.0056107106875066      -0.14574601642533

in      -1.6971157419033        0.95369546810918
out     0.040373904069399       -0.19490861696476

in      -1.6971157419033        0.95369546810918
out     0.077159274808694       -0.22729154300181

in      -1.6971157419033        0.95369546810918
out     0.1144576942613 -0.24500315026035

in      -1.6971157419033        0.95369546810918
out     0.15065190802246        -0.25149433081713

in      -1.6971157419033        0.95369546810918
out     0.18422582030134        -0.25013744368497

in      -1.6971157419033        0.95369546810918
out     0.21395535997402        -0.24362335530009

in      -1.6971157419033        0.95369546810918
out     0.23902601951548        -0.23389435289547

in      -1.6971157419033        0.95369546810918
out     0.25905572514095        -0.22228419312076

Found it, was actually my bad :) https://github.com/Element-Research/rnn/pull/32

Awesome. Thanks.


Consider adding a version of DHT spec being used in the DNS records for a document

If there is ever a need for another version of the spec, then it would be useful for users to differentiate between them.
DKIMs and SPF do this. See https://www.cloudflare.com/learning/dns/dns-records/dns-dkim-record/ and https://www.cloudflare.com/learning/dns/dns-records/dns-spf-record/
For DHT, I would suggest adding it as an additional property in the _did. TXT record. The first example in https://did-dht.com/#dids-as-dns-records would become the following:
v=1;vm=k0,k1,k2;auth=k0;asm=k1;inv=k2;del=k2;srv=s0,s1,s2

Sounds like a good addition and a simple monotonically increasing integer version seems like a good idea.


Reduce power consumption...................?

I am using a ble nano to transmit the state of three sensors in which one is digital and other two are analog.
Here i want to reduce the power consumption as much as low.
for that i need to disable the  uart.  and i have already  adjusted Tx power and Tx interval.Now the current in the whole setup is approx to my desired range without connecting any central to ble nano. So if i disable uart the current will be in my desired range.
But when a central is connected then the current will increase 4times as my range. So my question is
how can i disable uart in bleperipheral library and  can i transmit my sensor data through device local name repeatedly without connecting any central to it.
Or can i transmit my sensor data to my destination (central) without connecting them each other............?

for that i need to disable the uart.

That question is not related to this library, I suggest to ask about RedBearLab about this: https://github.com/RedBearLab/nRF51822-Arduino
Please only open issues specifically related to this library here, it is not a place for general questions regarding the board etc.


rna-seq transcript_assembler: cufflinks run instead of sailfish and partition_gtf error

Hi,
I tried the analysis as in https://github.com/chapmanb/bcbio-nextgen/issues/2162 with also transcript_assembler activated.
I used this yaml file
# Template for  RNA-seq using Illumina prepared samples
---
details:
  - analysis: RNA-seq
    genome_build: BGI_Solexa_pseudochr_2_0
    algorithm:
      aligner: star
      trim_reads: read_through
      adapters: [truseq, polya]
      strandedness: unstranded
      transcript_assembler: sailfish
      variantcaller: gatk-haplotype
upload:
   dir: ../final

The alignment with STAR worked and then a single invocation of cufflinks instead of the specified sailfish was run detect new transcripts.  I expected sailfish to be run, and also a sailfish run per sample.  See these log statements and also the final error message.
[2017-11-17T17:03Z] node18: [bam_sort_core] merging from 30 files and 10 in-memory blocks...
[2017-11-17T17:10Z] node6.be.bayercropscience: Index BAM file: SAMPLE_744069.bam
[2017-11-17T17:11Z] node18: Index BAM file: SAMPLE_744068.bam
[2017-11-17T17:15Z] gquest: Resource requests: cufflinks, samtools; memory: 3.00, 3.00; cores: 10, 10
[2017-11-17T17:15Z] gquest: Configuring 10 jobs to run, using 10 cores each with 30.1g of memory reserved for each job
[2017-11-17T17:15Z] gquest: Timing: disambiguation
[2017-11-17T17:15Z] gquest: Timing: transcript assembly
[2017-11-17T17:15Z] gquest: ipython: cufflinks_merge
[2017-11-17T17:16Z] node24: Merging the following transcript assemblies with Cuffmerge:
[2017-11-17T17:16Z] node24: [Fri Nov 17 18:16:00 2017] Beginning transcriptome assembly merge
[2017-11-17T17:16Z] node24: -------------------------------------------
[2017-11-17T17:16Z] node24: [Fri Nov 17 18:16:00 2017] Preparing output location /data/run/Projects/DA-1051/DA_1051-merged/work/bcbiotx/tmpdkNLZq/cuffmerge/
[2017-11-17T17:16Z] node24: [Fri Nov 17 18:16:01 2017] Converting GTF files to SAM
[2017-11-17T17:16Z] node24: [Fri Nov 17 18:16:01 2017] Quantitating transcripts
[2017-11-17T17:16Z] node24: Warning: Could not connect to update server to verify current version. Please check at the Cufflinks website (http://cufflinks.cbcb.umd.edu).
[2017-11-17T17:16Z] node24: Command line:
[2017-11-17T17:16Z] node24: cufflinks -o /data/run/Projects/DA-1051/DA_1051-merged/work/bcbiotx/tmpdkNLZq/cuffmerge/ -F 0.05 -g /workspace/my_user/tmp_bcbio_stable_1.0.6/data_dir/genomes/BGI_Solexa_pseudochr_2_0/BGI_Solexa_pseudochr_2_0/rnaseq/ref-transcripts.gtf -q --overhang-tolerance 200 --library-type=transfrags -A 0.0 --min-frags-per-transfrag 0 --no-5-extend -p 10 /data/run/Projects/DA-1051/DA_1051-merged/work/bcbiotx/tmpdkNLZq/cuffmerge/tmp/mergeSam_filepkr1Dv
[2017-11-17T17:16Z] node24: [bam_header_read] EOF marker is absent. The input is probably truncated.
[2017-11-17T17:16Z] node24: [bam_header_read] invalid BAM binary header (this is not a BAM file).
[2017-11-17T17:16Z] node24: File /data/run/Projects/DA-1051/DA_1051-merged/work/bcbiotx/tmpdkNLZq/cuffmerge/tmp/mergeSam_filepkr1Dv doesn't appear to be a valid BAM file, trying SAM...
[2017-11-17T17:16Z] node24: [18:16:01] Loading reference annotation.
[2017-11-17T17:16Z] node24: [18:16:02] Inspecting reads and determining fragment length distribution.
[2017-11-17T17:16Z] node24: Processed 22423 loci.
[2017-11-17T17:16Z] node24: > Map Properties:
[2017-11-17T17:16Z] node24: >       Normalized Map Mass: 0.00
[2017-11-17T17:16Z] node24: >       Raw Map Mass: 0.00
[2017-11-17T17:16Z] node24: >       Fragment Length Distribution: Truncated Gaussian (default)
[2017-11-17T17:16Z] node24: >                     Default Mean: 200
[2017-11-17T17:16Z] node24: >                  Default Std Dev: 80
[2017-11-17T17:16Z] node24: [18:16:02] Assembling transcripts and estimating abundances.
[2017-11-17T17:16Z] node24: Processed 22423 loci.
[2017-11-17T17:16Z] node24: [Fri Nov 17 18:16:14 2017] Comparing against reference file /workspace/my_user/tmp_bcbio_stable_1.0.6/data_dir/genomes/BGI_Solexa_pseudochr_2_0/BGI_Solexa_pseudochr_2_0/rnaseq/ref-transcripts.gtf
[2017-11-17T17:16Z] node24: Warning: Could not connect to update server to verify current version. Please check at the Cufflinks website (http://cufflinks.cbcb.umd.edu).
[2017-11-17T17:16Z] node24: [Fri Nov 17 18:16:21 2017] Comparing against reference file /workspace/my_user/tmp_bcbio_stable_1.0.6/data_dir/genomes/BGI_Solexa_pseudochr_2_0/BGI_Solexa_pseudochr_2_0/rnaseq/ref-transcripts.gtf
[2017-11-17T17:16Z] node24: Warning: Could not connect to update server to verify current version. Please check at the Cufflinks website (http://cufflinks.cbcb.umd.edu).
[2017-11-17T17:17Z] node24: Cleaning features with an unknown strand from the assembly.
[2017-11-17T17:19Z] node24: Unexpected error
Traceback (most recent call last):
  File "/workspace/my_user/tmp_bcbio_stable_1.0.6/data_dir/anaconda/lib/python2.7/site-packages/bcbio/distributed/ipythontasks.py", line 51, in _setup_logging
    yield config
  File "/workspace/my_user/tmp_bcbio_stable_1.0.6/data_dir/anaconda/lib/python2.7/site-packages/bcbio/distributed/ipythontasks.py", line 499, in cufflinks_merge
    return ipython.zip_args(apply(rnaseq.cufflinks_merge, *args))
  File "/workspace/my_user/tmp_bcbio_stable_1.0.6/data_dir/anaconda/lib/python2.7/site-packages/bcbio/pipeline/rnaseq.py", line 246, in cufflinks_merge
    samples[0][0])
  File "/workspace/my_user/tmp_bcbio_stable_1.0.6/data_dir/anaconda/lib/python2.7/site-packages/bcbio/rnaseq/cufflinks.py", line 258, in merge
    data)
  File "/workspace/my_user/tmp_bcbio_stable_1.0.6/data_dir/anaconda/lib/python2.7/site-packages/bcbio/rnaseq/annotate_gtf.py", line 15, in annotate_novel_coding
    ref_fasta, data)
  File "/workspace/my_user/tmp_bcbio_stable_1.0.6/data_dir/anaconda/lib/python2.7/site-packages/bcbio/rnaseq/cpat.py", line 22, in classify_with_cpat
    cutoff, hexamer, logit = get_coding_potential_cutoff(ref_gtf, ref_fasta, data)
  File "/workspace/my_user/tmp_bcbio_stable_1.0.6/data_dir/anaconda/lib/python2.7/site-packages/bcbio/rnaseq/cpat.py", line 112, in get_coding_potential_cutoff
    coding_gtf = gtf.partition_gtf(train_gtf, coding=True)
  File "/workspace/my_user/tmp_bcbio_stable_1.0.6/data_dir/anaconda/lib/python2.7/site-packages/bcbio/rnaseq/gtf.py", line 161, in partition_gtf
    biotype = biotype_lookup(feature)
TypeError: 'NoneType' object is not callable

In between the single cufflinks invocation and the final error  cuffmerge is also run according to the command log.
Strange thing is also that the cufflink command is written to the debug log and the cuffmerge command  to the command log.
[2017-11-17T17:16Z] node24: cuffmerge -o //data/run/Projects/DA-1051/DA_1051-merged/work/bcbiotx/tmpdkNLZq/cuffmerge --ref-gtf /workspace/my_user/tmp_bcbio_stable_1.0.6/data_dir/genomes/BGI_Solexa_pseudochr_2_0/BGI_Solexa_pseudochr_2_0/rnaseq/ref-transcripts.gtf --num-threads 10 --ref-sequence /workspace/ggher/tmp_bcbio_stable_1.0.6/data_dir/genomes/BGI_Solexa_pseudochr_2_0/BGI_Solexa_pseudochr_2_0/seq/BGI_Solexa_pseudochr_2_0.fa /tmp/16251568.9.main/tmpJsUDqs
I can find output in the assembly directory
assembly/
assembly/cuffmerge
assembly/cuffmerge/logs
assembly/cuffmerge/logs/run.log
assembly/cuffmerge/merged.clean.gtf
assembly/cuffmerge/merged.dirty.gtf
assembly/cuffmerge/merged.clean.clean.fixed.gtf
assembly/cuffmerge/merged.gtf

The final error that I get is in the def partition_gtf function on the biotype = biotype_lookup(feature): line here:
https://github.com/chapmanb/bcbio-nextgen/blob/aa5b67efb78ba0d92d1b621a581c927206ea77ba/bcbio/rnaseq/gtf.py#L161
I am not sure what exactly is going wrong and right here, and how the final error (state) is reached.
And if this might be related to issue https://github.com/chapmanb/bcbio-nextgen/issues/2162
Could you please advice on how to debug and how  to get sailfish and or cufflinks working for transcript assembly?
Thank you very much.

Hi Neil,
Thanks-- I see you're using a custom genome installation; could you pass along what the ref-transcripts.gtf file is for me? I think what is happening is there are is no coding/non-coding annotation for CPAT to predict coding/non-coding status from and so this part is failing. It would be helpful to have a GTF file to check with.

Hi Rory,
Below are the first genes from the gft file.
Chr_01  BGI_GENES       exon    2952    3377    .       -       .       transcript_id "Csa1M000010.1"; gene_id "Csa1G000010"; gene_name "Csa1G000010";
Chr_01  BGI_GENES       exon    3837    4040    .       -       .       transcript_id "Csa1M000010.1"; gene_id "Csa1G000010"; gene_name "Csa1G000010";
Chr_01  BGI_GENES       exon    4131    4284    .       -       .       transcript_id "Csa1M000010.1"; gene_id "Csa1G000010"; gene_name "Csa1G000010";
Chr_01  BGI_GENES       CDS     3324    3377    .       -       0       transcript_id "Csa1M000010.1"; gene_id "Csa1G000010"; gene_name "Csa1G000010";
Chr_01  BGI_GENES       CDS     3837    4040    .       -       0       transcript_id "Csa1M000010.1"; gene_id "Csa1G000010"; gene_name "Csa1G000010";
Chr_01  BGI_GENES       CDS     4131    4199    .       -       0       transcript_id "Csa1M000010.1"; gene_id "Csa1G000010"; gene_name "Csa1G000010";
Chr_01  BGI_GENES       exon    5474    5957    .       -       .       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       exon    6447    6824    .       -       .       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       exon    8299    8493    .       -       .       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       exon    8572    8649    .       -       .       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       exon    8716    8904    .       -       .       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       exon    8976    9209    .       -       .       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       exon    9320    9670    .       -       .       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       exon    9747    9944    .       -       .       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       exon    10071   10241   .       -       .       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       exon    10601   10708   .       -       .       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       exon    10775   10990   .       -       .       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       exon    11082   11288   .       -       .       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       exon    12362   12466   .       -       .       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       exon    12553   12666   .       -       .       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       exon    12787   12861   .       -       .       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       exon    13223   13403   .       -       .       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       exon    13922   14089   .       -       .       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       CDS     5772    5957    .       -       0       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       CDS     6447    6824    .       -       0       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       CDS     8299    8493    .       -       0       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       CDS     8572    8649    .       -       0       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       CDS     8716    8904    .       -       0       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       CDS     8976    9209    .       -       0       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       CDS     9320    9670    .       -       0       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       CDS     9747    9944    .       -       0       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       CDS     10071   10241   .       -       0       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       CDS     10601   10708   .       -       0       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       CDS     10775   10990   .       -       0       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       CDS     11082   11288   .       -       0       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       CDS     12362   12466   .       -       0       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       CDS     12553   12666   .       -       0       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       CDS     12787   12861   .       -       0       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       CDS     13223   13384   .       -       0       transcript_id "Csa1M000020.1"; gene_id "Csa1G000020"; gene_name "Csa1G000020";
Chr_01  BGI_GENES       exon    18684   19104   .       +       .       transcript_id "Csa1M000030.1"; gene_id "Csa1G000030"; gene_name "Csa1G000030";
Chr_01  BGI_GENES       exon    19747   20005   .       +       .       transcript_id "Csa1M000030.1"; gene_id "Csa1G000030"; gene_name "Csa1G000030";
Chr_01  BGI_GENES       exon    20244   20438   .       +       .       transcript_id "Csa1M000030.1"; gene_id "Csa1G000030"; gene_name "Csa1G000030";
Chr_01  BGI_GENES       exon    20992   21806   .       +       .       transcript_id "Csa1M000030.1"; gene_id "Csa1G000030"; gene_name "Csa1G000030";
Chr_01  BGI_GENES       CDS     19013   19104   .       +       0       transcript_id "Csa1M000030.1"; gene_id "Csa1G000030"; gene_name "Csa1G000030";
Chr_01  BGI_GENES       CDS     19747   20005   .       +       1       transcript_id "Csa1M000030.1"; gene_id "Csa1G000030"; gene_name "Csa1G000030";
Chr_01  BGI_GENES       CDS     20244   20438   .       +       0       transcript_id "Csa1M000030.1"; gene_id "Csa1G000030"; gene_name "Csa1G000030";
Chr_01  BGI_GENES       CDS     20992   21387   .       +       0       transcript_id "Csa1M000030.1"; gene_id "Csa1G000030"; gene_name "Csa1G000030";
Chr_01  BGI_GENES       exon    22969   23663   .       -       .       transcript_id "Csa1M000040.1"; gene_id "Csa1G000040"; gene_name "Csa1G000040";
Chr_01  BGI_GENES       exon    24572   24813   .       -       .       transcript_id "Csa1M000040.1"; gene_id "Csa1G000040"; gene_name "Csa1G000040";
Chr_01  BGI_GENES       exon    24940   25328   .       -       .       transcript_id "Csa1M000040.1"; gene_id "Csa1G000040"; gene_name "Csa1G000040";
Chr_01  BGI_GENES       exon    27352   27457   .       -       .       transcript_id "Csa1M000040.1"; gene_id "Csa1G000040"; gene_name "Csa1G000040";
Chr_01  BGI_GENES       CDS     23150   23663   .       -       1       transcript_id "Csa1M000040.1"; gene_id "Csa1G000040"; gene_name "Csa1G000040";
Chr_01  BGI_GENES       CDS     24572   24813   .       -       0       transcript_id "Csa1M000040.1"; gene_id "Csa1G000040"; gene_name "Csa1G000040";
Chr_01  BGI_GENES       CDS     24940   25328   .       -       2       transcript_id "Csa1M000040.1"; gene_id "Csa1G000040"; gene_name "Csa1G000040";

Let me know if you need the url to the public gff3 file. This public gff3 file was cleaned and corrected a bit and then converted to gft format via the gffread command below.
gffread -g sequences.fa -T -o-  genes.gff  > genes.gtf

@roryk  Is the above information enough for you to trouble shoot this issue. Or do you need the link to the public gff3 file.
It would be nice if CPAT is skipped if the necessary annotation is not present in the genome gtf file.
Or is there an easy way to add this coding/non coding annotation?

@roryk  Also I am still wondering why cufflinks is run instead of sailfish for discovering new transcripts. And why cufflink is only run for a single sample, and not all 23 samples.

Hi @NeillGibson,
Thanks, yes it is enough to troubleshoot, I'll push a fix soon. sailfish doesn't do transcript discovery, it just does quantification so we need to use something else other than sailfish for that. Cufflinks for transcript discovery is run on each sample individually and then the assemblies are merged at the end; this is the setup recommended by the Cufflinks and Stringtie folks.

Thanks @NeillGibson, I fixed the issue with CPAT. The problem was we were not handling the case where no features labelled as protein_coding to use to try to train the classifier. I added a check for that prior to running CPAT so it should be all set now.

Thank you @roryk .


Question: usage of webpack for non-JS environment

Hi @sokra ,
I am interested to use webpack for asset management along with its hot reloading capabilities. Is this possible to integrate with non-node backends? For instance, django / flask?

You can use a node.js server to serve the assets along with any other http server (development). The built assets are server independend (production).
http://webpack.github.io/docs/webpack-dev-server.html#combining-with-an-existing-server

But how does this work with cache-busted assets? Since I couldn't predict the md5 hashes, I can't hardcode a script source to point to the generated assets (build.xxxx.js)

On 27 Jan 2015, at 4:33 pm, Tobias Koppers<EMAIL_ADDRESS>wrote:
You can use a node.js server to serve the assets along with any other http server (development). The built assets are server independend (production).
http://webpack.github.io/docs/webpack-dev-server.html#combining-with-an-existing-server
—
Reply to this email directly or view it on GitHub.

You could write the generated stats into a stats.json file and read that with python. It contains all the necessary information.
For instance: Try webpack --json >> stats.json (about --json)

cool yeah i think that is possible :)

@geeky I've recently written a webpack plugin to do this, you might be interested:
https://github.com/nickjj/manifest-revision-webpack-plugin
Here's a way to implement the file it produces into Flask. It would be pretty easy to make it work with Django too. https://github.com/nickjj/flask-webpack


updated puml plugin definition

Description
Updated the puml plugin definition file for a plugin that generates PlantUML output
Linked Items:
Closes/Fixes/Resolves #775
Checklist:

[N/A ] I updated project documentation to reflect my changes.
Rationale: Plugin code functionality not yet implemented.
[x] My changes generate no new warnings.
[N/A ] I updated new and existing unit tests to account for my changes.
Rationale: Plugin code not yet implemented.
[x] I linked the associated item(s) to be closed.
[N/A] I bumped the version.
Rational: (not yet executable. No change to user-facing functionality)
[x] I added the labels corresponding to my changes.

Yes, mainly just looking for input on gen_puml.aac . I ran the gen_plugin command to check that the .aac file is valid, and it generated the stub .py files, so I kept them as a starting point for the next task. I'll be migrating the logic from the existing plugin .py code to the new stubs.

Why do you want to get rid of the option to output to console? That seems important for automation purposes, to be able to pipe the output of the aac command to other tools.

Why do you want to get rid of the option to output to console? That seems important for automation purposes, to be able to pipe the output of the aac command to other tools.

The logic for output to the console does not seem to be there any longer, as demonstrated in the original removal request comments, so that portion of the definition was not properly updated. Using the legacy aac-puml functionality does not output to the console any longer. It only outputs to a file, so that is what the definition needs to reflect because that is the current status of the plugin operations.
Right now, no users are piping anything nor have piped anything previously when AaC once did dump puml output to console, they just utilize the files output.
Agree, the piping output is a potential use case. But it is not currently something requested and was not often used when it did exist. So, we do not need to currently spend the effort to incorporate it.
This was discussed with end users and stakeholders to confirm usage to help determine if removing those portions of the acceptance in the definition would be problematic before the original removal request was made on this PR. It was agreed among end users and stakeholders that maintaining the file output was the priority.

changed as requested to support status quo with older version.


README.md site source link is not working

The hyperlink provided in the README.md file is currently non-functional. This hyperlink is located within the Documentation section, and it corresponds to the Overview (site source), as illustrated in the image below:

when you go into that folder we can see that workbox is not available.
So I hope we need to update the link.

Closed via https://github.com/GoogleChrome/workbox/commit/a30d1aa683da2efd9e2ad4b0df17853b99e23aa6.


Smooth animation?

Hi,
for some reason the animation is not so smooth on my Windows 10 PC when a new app is opened. Is this a graphic limitation?

It was never perfect, UIAutomation doesn't update fast enough to match frame for frame and the animation is really just trying to keep up with center calculation through the standard windows animation
You can increase your framerate potentially by adding a number after your command line argument, try running CenterTaskbar.exe 200 for example

Ok. Thanks for the tip
El 6 ago 2021, a las 22:32, Michael Higgins @.***> escribió:

Closed #35https://github.com/mdhiggins/CenterTaskbar/issues/35.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/mdhiggins/CenterTaskbar/issues/35#event-5124489079, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAGJAYXAI7HGTPGVVESPO33T3Q2CLANCNFSM5BVIII4Q.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email.


support for keeping track of KG triplet sources

This PR adds support for keeping track of which exact triplets were used to find answers to knowledge-graph queries. (https://github.com/jerryjliu/gpt_index/issues/463)
Previously, this was only accessible through tricky text parsing. Now, one can simply use response.source_nodes
Furthermore, this should support future "external sources", where the text used to compute an answer does not come directly from the source documents.
Happy to make any improvements to the code!

Thanks for merging this @jerryjliu, I totally agree with the changes you made! 💪 (I was just asleep hah)


Consider restricting leakier no-cors requests to not use these headers

If Firefox or Safari were to adopt these headers for top-level cross-site fetches that are no-cors (e.g. a regular <img>) it would make it possible to leak information that I think is not currently leak-able.
I am not certain what the right decision is here, but given that Safari and Firefox do not have positions or implementations on requestStorageAccessFor, this is an expansion in where storage access can be used, not just an ergonomic improvement.
The most direct translation of this proposal to  strictly ergonomic improvement would be to restrict the Sec-Fetch-Storage-Access headers to [i]frame fetches only.

it would make it possible to leak information that I think is not currently leak-able

Given that the ability to load subresources (i.e. not just iframes, but images, scripts, etc.) seems like a significant part of this proposal, it would be good to understand the leak concerns better to see if we can instead address these.
Do you mean that if we were to add the Origin header to no-cors requests eligible for retrying a load with credentials then we would disclose the origin of the requesting document to servers hosting the resource? (This assumes that the requesting page or the user intentionally removes the Referer header via Referrer Policy or similar.)

No, I'm still thinking about a leak akin to the typical no-cors leakiness. Although I suppose the case I am thinking of only applies if the embeddee is not careful about sending these headers only in framed contexts.
Consider: a third party has storage access for an embed. Then they send the header for all of its images in the frame, some of which have varying size based upon profile details. If the embedder wants to read those profile details they can load those images in the top level. (I see now that this only works if the embeddee does not validate that the image is going into the iframe.

I think this ties in quite nicely with https://github.com/cfredric/storage-access-headers/issues/7 - i.e. I agree that this is a concern, but IMHO the origin allowlisting mechanism discussed in that issue might be a reasonable solution. (It can still be a footgun if developers use the * wildcard to allow credentialed requests from anywhere, but depending on how we name the value it should at least nudge developers to think about a tighter allowlist).

Sorry for the late response here - I believe I see the attack/leak you're describing @bvandersloot-mozilla, and I agree with @arturjanc that the allowed-origin=... addition should give the third-party the ability to ensure that they're protected (provided they don't use the wildcard as a "please just work" option). I'll close this since I merged #14, but please reopen if you think there's more to discuss here.


Compute shaders: Add support for external (video)  textures

See https://forum.babylonjs.com/t/compute-shader-videotexture-input/43864

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.


web issue

"file:///C:/Users/mjd/Desktop/New%20folder%20(2)/index.html" how to change <IP_ADDRESS>:8080 (localhost)

Sorry, what is your question? But on first glance your question doesn't seem to be related to the lib...


how can i get the video duration

how can i get the video duration, I do not find the function. Anyone can help me?

Hi,
Have you find how to it ?
Thanks.

$video = $ffmpeg->open($movie);
$format = $video->getFormat();
$duration = $format->get('duration');// you get it

ok thanks


[Bug]: redirect inside handle_event/3 causes "Not Connected" issue on IOS

What happened?
redirect/2 navigation is not working inside of a handle event.
I've got a simple example that will reproduce the issue. I've defined the "/home" and the "/about" routes and have identical HomeLive and AboutLive liveviews.
defmodule Mix4Web.HomeLive do
  use Mix4Web, :live_view
  use LiveViewNative.LiveView

  def mount(_params, _session, socket) do
    {:ok, redirect(socket, to: "/about")}
  end

  def render(%{platform_id: :web} = assigns) do
    ~H"""
    <.button phx-click="home">Home</.button>
    <.button phx-click="about">About</.button>
    """
  end

  def render(%{platform_id: :swiftui} = assigns) do
    ~SWIFTUI"""
    <Text>HOME</Text>
    <Button phx-click="home">Home</Button>
    <Button phx-click="about">About</Button>
    """
  end

  def handle_event("home", _params, socket) do
    {:noreply, redirect(socket, to: "/home")}
  end

  def handle_event("about", _params, socket) do
    {:noreply, redirect(socket, to: "/about")}
  end
end

Interestingly, navigation works fine when the redirect occurs in the mount/3 callback, but not in the handle_event/3 callback.
Library Version
main
XCode Version
14.3.1
Swift Version
No response
On which device or simulator are you running into the problem?
iPhone
Target Device Operating System Version
IOS 16.4
Relevant log output
No response

@BrooklinJazz I believe you need to use push_navigate
redirect is intended for non-liveview apps. It will kill the socket and if you happen to redirect to another liveview route in the same app it will establish a new socket connection

Thank you, I'll give that a go

Sorry, my note was incorrect. I believe push_navigate may stil be correct depending on your use-case but accoridng to the docs it will still shut down the socket https://hexdocs.pm/phoenix_live_view/Phoenix.LiveView.html#push_navigate/2

Neither redirect, push_patch, or push_navigate appear to work for me.

I just want to confirm that these are liveview endpoints you're navigating to?

Here's my router:
  scope "/", Mix4Web do
    pipe_through :browser

    live "/", HomeLive
    live "/home", HomeLive
    live "/about", AboutLive
  end

And my handlers
  def handle_event("home", _params, socket) do
    {:noreply, push_navigate(socket, to: "/home")}
  end

  def handle_event("about", _params, socket) do
    {:noreply, push_navigate(socket, to: "/about")}
  end

is this reproducible, or only an issue on my machine?

I can take 10-15 mins and set up a barebones project so other folks can see if it works for them.

Did you enable navigation in your Swift project?

@carson-katri is that something in our library? If so why wouldn't we have navigation enabled by default?

Yes, it’s part of the session configuration: https://liveview-native.github.io/liveview-client-swiftui/documentation/liveviewnative/livesessionconfiguration/navigationmode-swift.property
I’m not sure what the reasoning behind disabled being default was. I think the navigation mode API was added before I joined the project.

navigation shouldn't even be an option, it should just be always on. @carson-katri I'm going to create an issue to remove the configuration option entirely

@carson-katri are there any more opt-into configurations? Applications should be fully functional without any flipping of switches. If there are other options like navigation we need to remove those make them always on.

Sorry for the tardy response @carson-katri. I had wondered if that was the issue, because I noticed the config option in the Navigation tutorial, but thought perhaps it was only for the NavigationLink component.
I'll try to add it in to confirm if that's the problem but I do agree with Brian here that it would be nice if it wasn't necessary.

Hmm, @carson-katri I'm not sure I'm configuring it correctly. The navigation is being triggered but I still get a "Not Connected" issue. Here's my ContentView.
import SwiftUI
import LiveViewNative

struct ContentView: View {
    @StateObject private var session: LiveSessionCoordinator<EmptyRegistry> = {
        var config = LiveSessionConfiguration()
        config.navigationMode = .enabled
        return LiveSessionCoordinator(URL(string: "http://localhost:4000/")!, config: config)
    }()

    var body: some View {
        LiveView(session: session)
    }
}

https://github.com/liveview-native/liveview-client-swiftui/assets/14877564/2a41906d-9134-431c-b453-00e22799e606

Adding the issue #1110 to this convo for tracking purposes.

I've had a couple bumps in the road with Navigation and @BrooklinJazz - I have been able to reproduce your "Not Connected" issue, but I am not sure exactly what solved it.
Do you have any other scope "/", Mix4Web in your router?  Possibly Authentication routes?
For example with this router setup I get the "Not Connected" error on the /users/register & /users/log_in routes:
router.ex
  scope "/", RealmsWeb do
    pipe_through :browser

    live "/", HomeLive, :index
    live "/counter", CounterLive, :index
  end

  ## Authentication routes

  scope "/", RealmsWeb do
    pipe_through [:browser, :redirect_if_user_is_authenticated]

    # get "/", PageController, :home

    live_session :redirect_if_user_is_authenticated,
      on_mount: [{RealmsWeb.UserAuth, :redirect_if_user_is_authenticated}] do
      live "/users/register", UserRegistrationLive, :new
      live "/users/log_in", UserLoginLive, :new
      live "/users/reset_password", UserForgotPasswordLive, :new
      live "/users/reset_password/:token", UserResetPasswordLive, :edit
    end

    post "/users/log_in", UserSessionController, :create
  end

But moving all the routes under the live_session scope the Navigation works without the "Not Connected" error, so maybe has something to do with multiple scopes?  I cannot figure it out
  scope "/", RealmsWeb do
    pipe_through :browser
  end

  ## Authentication routes

  scope "/", RealmsWeb do
    pipe_through [:browser, :redirect_if_user_is_authenticated]

    # get "/", PageController, :home

    live_session :redirect_if_user_is_authenticated,
      on_mount: [{RealmsWeb.UserAuth, :redirect_if_user_is_authenticated}] do
      live "/", HomeLive, :index
      live "/counter", CounterLive, :index
      live "/users/register", UserRegistrationLive, :new
      live "/users/log_in", UserLoginLive, :new
      live "/users/reset_password", UserForgotPasswordLive, :new
      live "/users/reset_password/:token", UserResetPasswordLive, :edit
    end

    post "/users/log_in", UserSessionController, :create
  end

Interesting. I have a pretty simple router:
  scope "/", Mix4Web do
    pipe_through :browser

    live "/", MenuLive
    live "/game/:game_id", GameLive
  end

I tried putting them in a live_session, but the issue persists.
scope "/", Mix4Web do
  pipe_through :browser

  live_session :mix4 do
    live "/", MenuLive
    live "/game/:game_id", GameLive
  end
end

@BrooklinJazz could you provide the commit that your app is depending on, or run Packages > Update to Latest Package Versions? I'd like to ensure you have the latest navigation fixes made in #1019, #1055, and #1081

After updating packages I was able to reproduce the issue on @ivanhoe's machine.

@BrooklinJazz Are you using push_navigate?

Yup, I also reproduced this after updating packages on my machine. Ivan was using Swiftui NavigationLink components, I'm using push_navigate. I also tried push_patch and redirect. All had the "Not connected" issue.

We fixed the handle_event/3 issue (or it was already fixed and I updated packages)
However, there's still an issue with handle_info. @carson-katri and I narrowed this down to: handle_info/3 will not navigate when we call push_navigate.


Hyperparameter training command for protonet with WRN backbone on miniImagenet dataset

Hi,
I appreciate your very insightful work as well as providing source code. Slightly related to Issue #24, I have been trying to recreate WRN pre-trained weights for miniImagenet that you had provided here for the protonet but can't seem to get the 61.4% performance you obtained in those results. Would you be willing to provide the command you used to train that protonet WRN model?
Thank you

Hello,
For WRN, I use --batch_size 128 --lr 0.1 --dp_rate 0.3 --gamma 0.1 in pre-training. While in meta-training it uses the same command as with the ResNet backbone.
Given the pre-trained weights of WRN, please use the --fix_bn option to set the backbone to evaluation mode during training (which closes the dropout and stops updating the BN statistics) during the meta-training phase. We find --fix_bn is important for WRN.

Thank you, that is very helpful.


Add example output in documentaion for az cli commands

Related command
All az storage blob related commands
Is your feature request related to a problem? Please describe.
There is no example output or error  in documentation (e.g. https://learn.microsoft.com/en-us/cli/azure/storage/blob/metadata?view=azure-cli-latest#az-storage-blob-metadata-show).
This cause inconvenience to developer who dont have azure cli in local environment.
Describe the solution you'd like
Add at least one example output for each command.
Additional context
A comparison on aws s3 ls commands documentation: https://docs.aws.amazon.com/cli/latest/reference/s3/ls.html

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


The experimental lcm function gives wrong result

Click to expand!
Issue Type
Bug
Source
source
Tensorflow Version
2.9.2
Custom Code
Yes
OS Platform and Distribution
Linux (Google Colab)
Mobile device
No response
Python version
3.7.15
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
Hi. The code below shows the lcm for 21 and 7 is output as 15 for TensorFlow while it should clearly be 21. NumPy and JAX give the correct result of 21. This is the case for int8 although the output value is certainly not high enough to be causing any overflows etc. The result in case of int16 or higher is accurate (21). However, if the values were 2100 and 70 the result would be inaccurate for int16 in tensorflow again as opposed to np and jax.

Standalone code to reproduce the issue
import tensorflow as tf
import numpy as np

at = tf.constant([21], dtype=tf.int8)
bt = tf.constant([7], dtype=tf.int8)

an = np.array([21], dtype=np.int8)
bn = np.array([7], dtype=jnp.int8)

print("tensorflow: ", tf.experimental.numpy.lcm(at, bt))
print("numpy: ", np.lcm(an,bn))

Relevant log output
tensorflow:  tf.Tensor([15], shape=(1,), dtype=int8)
numpy:  [21]

@sushreebarsa
I was able to  reproduce the issue on Colab by using TF-nightly, TF v2.9.2 and TF v2.10.1. Please find the gist here for reference.
Thank you!

Hi @SuryanarayanaY. Thank you for the reply.
I don't think this adresses the issue accurately. In the code I provided above, there is no dtype argument for lcm API anyways. Its the input arrays that have their dtype specified.
As for the provided gist, the first tensor has been modified to have int16 while my code specifies int8. This change is not a fix but rather a diversion from the actual issue.
Please correct me if am missing something here or kindly take a more serious and thorough look at this. Thank you.

@Ishticode ,
The API tf.experimental.numpy.lcm has only two arguments that are X1 & X2 which is not supporting argument  dtype,because TF converts them into suitable dtypes based on inputs.Providing explicit dtype not being supported currently. Hence if you won't mention any dtype at all it works fine.I did some exercise here and found that without explicit dtype the results are inline with numpy.Request you also do some exercise and confirm the same.
Otherway is mentioning suitable dtype same as numpy.But please note that it is my assumption that it should work with same dtype as numpy argument. Here i found that with int8  as dtype the results are not same for TF and Numpy which needs to be checked. But for other dtype like int32 the results are same.
Please refer the attached revised gist.
We will definitely bring the issue to notice of Development team and also requests them to clarify about what exactly the unsupported arguments meant in this API doc.
Until then we shall assume that the dtype argument not supported as mentioned in Documentation and also as it is giving inconsistent results.
Thankyou!

Hi @SuryanarayanaY
lcm does not have dtype argument. That's been clear from the start and is not the point of discussion here.
Could I maybe get a look from @hawkinsp or any other senior memeber so this can be resolved comprehensively.
The result for int32 dtypes are not same sometimes either. Check this:
Copy and run this example.
import tensorflow as tf
import numpy as np
print(tf.__version__)

at = tf.constant([700000],tf.int32)
bt = tf.constant([21000000],tf.int32)

an = np.array([700000], dtype=np.int32)
bn = np.array([21000000], dtype=np.int32)

print("tensorflow: ", tf.experimental.numpy.lcm(at, bt))
print("numpy: ", np.lcm(an,bn))

You will see that it produces incosistent results (numpy being correct and tensorflow incorrect) as such
2.9.2
tensorflow:  tf.Tensor([2390], shape=(1,), dtype=int32)
numpy:  [21000000]

I was able to break it for int64 too. It happens for all int types where the corresponding numpy call gives correct result and tensorflow miscalculates.

Hi @Ishticode ,
Yes I cross checked and agree to you.Even without dtype argument also the results are inconsistent and wrong as per gist attached.Thanks for bring this to us.Sure the issue will be escalated to developer team.

Hi @Ishticode ,
The issue is fixed now in tf-nightly. I have tested the code that failed earlier and found its working fine now with tf-nightly and please refer to attached gist.
Could you please check and confirm whether issue resolved and can be closed? Thanks!


D3 v3 is going to be deleted. Please migrate to v4 ASAP.

D3 v3 is going to be deleted. Please migrate to v4 ASAP.
See go/d3v4 for details and resources on migration.
I am guessing that the widget just needs a quick update on the library(s) that it is referencing.

I am having the same issue, unable to find where it is referenced to change it :(

I will look into this.

I managed to upgrade the google charts library, however the sankey chart is broken and I can't seem to fix it. I pushed the changes to the master branch. There a compiled widget file is available to download. Please let me know if it works for you guys.


Group term variants by affixes variations

v1: horizontal-axis wind turbine
v2: horizontal axis wind turbine
affixes : "horizontal axis" and "horizontal-axis" are variants, v1 and v2 should be grouped together.

See #79


Template: {{hash}} vs. {{hashFull}}

Within your template (initially provided with your plugin) you use the following:
{{hash}}
The generated link does not work since bitbucket uses the full hash instead of the shortened one (BTW: even your shortened one is to long in comparison to the hash used in bitbucket: bitbucket use only 6a5ab0e96393 instead of 6a5ab0e96393ca7 you use ...)
I looked in documentation on https://github.com/tomasbjerre/git-changelog-lib and found there a value {{hashFull}} - but this does not work within your modified template:
{{hash}}
{{hashFull}} is expanded into an empty string.

Superb!

Its released in 1.12 now. Open issue again if not working.

Works as expected - see #23. Thanks for the fast fix