Crashes on keyboard input right after selection

This is fantastic by the way.
When a search string is entered and the return key is hit there is a moment when results are being gathered prior to populating the UI. During this time if keyboard input is hit it will crash the application. Please disable keyboard input during this time or fix the issue so that there is no effect. Thank you

Can you please provide me with the generated crash report, because I can't seem to reproduce this error. Thanks!

Thank you. I have more information:
I have built with cargo 1.51 and 1.58-nightly -- same result. I have also upgraded the cursive crate to "0.17.0-alpha.0" and fixed the resultant errors. Same result. I have also replaced all panic calls with returns and unwraps with match statements to see if it fixes it. Was a pain but still get the same issue. Of course then I don't get the message. So I grabbed a fresh one and reproduced the error. This is what I see:
[INFO] Loading the config
[INFO] The config directory is /home/n00b/.config
[INFO] The config file doesn't exist
[WARN] Failed loading the config file at the location:
Caused by:
No such file or directory (os error 2)
Well, this is embarrassing...
wiki-tui had a problem and crashed spectacularly. To help us diagnose the problem, you can send us a crash report.
We have generated a report file at "/tmp/crash_report-f4118003-8e5b-4932-8865-8d3e27bae93a.log". Submit an issue with the subjet of "wiki-tui Crash Report"
and describe what you did before the crash. Also include the report as an attachment.
Github: https://github.com/Builditluc/wiki-tui
Standing by for guidance and run some more tests of my own.

This is what the log says:
Name: wiki-tui
Version: 0.3.4
Operating System: Linux
Cause: index out of bounds: the len is 0 but the index is 0.
Panic occurred in file 'src/main.rs' at line 123
0:     0x5599b06a1d8a - backtrace::backtrace::libunwind::trace::hda10e0459f43c4c8
at /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.62/src/backtrace/libunwind.rs:93:5
backtrace::backtrace::trace_unsynchronized::h726d9731cc48ab36
at /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.62/src/backtrace/mod.rs:66:5
1:     0x5599b06a1d02 - backtrace::backtrace::trace::ha89d983f9340cb07
at /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.62/src/backtrace/mod.rs:53:14
2:     0x5599b069bf56 - backtrace::capture::Backtrace::create::hc62617836433e5c4
at /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.62/src/capture.rs:176:9
3:     0x5599b069bead - backtrace::capture::Backtrace::new::h1b257574325daa52
at /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.62/src/capture.rs:140:22
4:     0x5599afed6c39 - wiki_tui::error::create_hook::{{closure}}::h6d5d6c781ee27e00
at /home/user/wiki-tui/src/error.rs:81:13
5:     0x5599b0886059 - std::panicking::rust_panic_with_hook::h01febc308b2b313b
at /rustc/e99963c554e4d12010c2dea9f46d7bbd41dc1271/library/std/src/panicking.rs:607:17
6:     0x5599b0885b10 - std::panicking::begin_panic_handler::{{closure}}::h24a6d13f5560b71f
at /rustc/e99963c554e4d12010c2dea9f46d7bbd41dc1271/library/std/src/panicking.rs:499:13
7:     0x5599b0884374 - std::sys_common::backtrace::__rust_end_short_backtrace::h3e2917f0da9fbc5c
at /rustc/e99963c554e4d12010c2dea9f46d7bbd41dc1271/library/std/src/sys_common/backtrace.rs:139:18
8:     0x5599b0885a79 - rust_begin_unwind
at /rustc/e99963c554e4d12010c2dea9f46d7bbd41dc1271/library/std/src/panicking.rs:495:5
9:     0x5599afdf3671 - core::panicking::panic_fmt::h7b8580d81fcbbacd
at /rustc/e99963c554e4d12010c2dea9f46d7bbd41dc1271/library/core/src/panicking.rs:106:14
10:     0x5599b02c651a - core::panicking::panic_display::he14d5ca416c36a61
at /rustc/e99963c554e4d12010c2dea9f46d7bbd41dc1271/library/core/src/panicking.rs:62:5
11:     0x5599afed56d7 - core::panicking::panic_str::h650d48e154117f53
at /rustc/e99963c554e4d12010c2dea9f46d7bbd41dc1271/library/core/src/panicking.rs:54:5
12:     0x5599afe09697 - wiki_tui::start_application::h8f51fc1cf8e4c606
at /home/user/wiki-tui/src/main.rs:123:9
13:     0x5599afe08791 - wiki_tui::main::h8587876e23280ff6
at /home/user/wiki-tui/src/main.rs:64:5
14:     0x5599afe3043b - core::ops::function::FnOnce::call_once::h64f1fc9e96332f1c
at /rustc/e99963c554e4d12010c2dea9f46d7bbd41dc1271/library/core/src/ops/function.rs:227:5
15:     0x5599afe856de - std::sys_common::backtrace::__rust_begin_short_backtrace::h0dea82e76318dccf
at /rustc/e99963c554e4d12010c2dea9f46d7bbd41dc1271/library/std/src/sys_common/backtrace.rs:123:18
16:     0x5599afec0591 - std::rt::lang_start::{{closure}}::h6eee828d6f5c8ff8
at /rustc/e99963c554e4d12010c2dea9f46d7bbd41dc1271/library/std/src/rt.rs:146:18
17:     0x5599b0883761 - core::ops::function::impls::<impl core::ops::function::FnOnce for &F>::call_once::h6743157f0325d450
at /rustc/e99963c554e4d12010c2dea9f46d7bbd41dc1271/library/core/src/ops/function.rs:259:13
std::panicking::try::do_call::hc65378359d322d46
at /rustc/e99963c554e4d12010c2dea9f46d7bbd41dc1271/library/std/src/panicking.rs:403:40
std::panicking::try::h52b83ca0140efb28
at /rustc/e99963c554e4d12010c2dea9f46d7bbd41dc1271/library/std/src/panicking.rs:367:19
std::panic::catch_unwind::h0ba25f4b0d3448dc
at /rustc/e99963c554e4d12010c2dea9f46d7bbd41dc1271/library/std/src/panic.rs:133:14
std::rt::lang_start_internal::{{closure}}::ha65f28100c5ad390
at /rustc/e99963c554e4d12010c2dea9f46d7bbd41dc1271/library/std/src/rt.rs:128:48
std::panicking::try::do_call::h5db5edfaf5b749d9
at /rustc/e99963c554e4d12010c2dea9f46d7bbd41dc1271/library/std/src/panicking.rs:403:40
std::panicking::try::h62409771d6cd0419
at /rustc/e99963c554e4d12010c2dea9f46d7bbd41dc1271/library/std/src/panicking.rs:367:19
std::panic::catch_unwind::h386261fb8f018fab
at /rustc/e99963c554e4d12010c2dea9f46d7bbd41dc1271/library/std/src/panic.rs:133:14
std::rt::lang_start_internal::h699f3530566c1833
at /rustc/e99963c554e4d12010c2dea9f46d7bbd41dc1271/library/std/src/rt.rs:128:20
18:     0x5599afec0560 - std::rt::lang_start::h0092a6bbcb72e774
at /rustc/e99963c554e4d12010c2dea9f46d7bbd41dc1271/library/std/src/rt.rs:145:17
19:     0x5599afe09b8c - main
20:     0x7f0dd78b30b3 - __libc_start_main
21:     0x5599afdf3e2e - _start
22:                0x0 -

If I simply enter the search string, hit return, and wait, it loads just fine after some time. It's specifically if I hit return and then hit any other key during that critical period of wait time

Thanks for the detailed Information. While I couldn't reproduce your error by pressing keys while searching, I got the exact same error when opening the article 'Washington' and pressing any key.
This is very weird.
Can you please set the log level to Debug and send me the log. Then I can further understand what wiki-tui was doing/trying to do when it crashed.

Name: wiki-tui
Version: 0.3.4
Operating System: Mac OS
Cause: index out of bounds: the len is 0 but the index is 0.
Panic occurred in file 'src/ui/article/view.rs' at line 409
0:        0x1096dbdd7 - backtrace::backtrace::libunwind::trace::h35cd47f1b26b5edc
at /Users/builditluc/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.62/src/backtrace/libunwind.rs:93:5
backtrace::backtrace::trace_unsynchronized::hd2721de6faef7767
It looks like the error occurs when the ArticleView tries to get the current link while no article is even loaded.

index cdd7d47..3c37677 100644
--- a/src/ui/article/view.rs
+++ b/src/ui/article/view.rs
@@ -406,6 +406,11 @@ impl View for ArticleView {
             Event::Key(Key::Up) => self.move_focus(Directions::UP),
             Event::Key(Key::Down) => self.move_focus(Directions::DOWN),
             Event::Key(Key::Enter) => {
+                if self.content.link_handler.links.len() >= self.content.link_handler.current_link {
+                    log::error!("Failed trying to access an invalid link");
+                    return EventResult::Consumed(None);
+                }
+
                 let target = self.content.link_handler.links
                     [self.content.link_handler.current_link]
                     .destination

Adding these few lines fixes the error for me. Can you please try out if it fixes the error for you?

Roger that. It's fixed for me now with that patch. Thank you for such a quick fix and such an awesome application

Great! I'll upload it onto the experimental branch.


virtctl: use basename when printing help

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind enhancement

What happened:
When used as a krew plugin, kubectl virt [help] prints virtctl instead of kubectl virt
What you expected to happen:
This is how it should be:
$ kubectl virt
Available Commands:
...
  vnc          Open a vnc connection to a virtual machine instance.

Use "kubectl virt <command> --help" for more information about a given command.
Use "kubectl virt options" for a list of global command-line options (applies to all commands).

How to reproduce it (as minimally and precisely as possible):
$ kubectl virt
Available Commands:
...
  vnc          Open a vnc connection to a virtual machine instance.

Use "virtctl <command> --help" for more information about a given command.
Use "virtctl options" for a list of global command-line options (applies to all commands).

Anything else we need to know?:
from krew-index PR

Also a piece of feedback, when you run kubectl virt the help message shows virtctl instead of kubectl virt (you can look at os.args[0] to detect whether running as a plugin or not, the basename would be kubectl-virt[.exe]).

Environment:

KubeVirt version (use virtctl version): Client Version: version.Info{GitVersion:"v0.17.0", GitCommit:"c0f960702dce718419a767f3913669f539229ff0", GitTreeState:"clean", BuildDate:"2019-05-05T08:09:14Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
Kubernetes version (use kubectl version): Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.5", GitCommit:"51dd616cdd25d6ee22c83a858773b607328a18ec", GitTreeState:"archive", BuildDate:"2019-03-05T13:36:50Z", GoVersion:"go1.12", Compiler:"gc", Platform:"linux/amd64"}
VM or VMI specifications: -
Cloud provider or hardware configuration: -
OS (e.g. from /etc/os-release): any
Kernel (e.g. uname -a):
Install tools:
Others:

/assign


Possibility to ignore elements in a list when mapping goes wrong for one element

I'd like to convert lets say a list
final listA = [correctObject, mappingGoesWrongObject, correctObject]
into a list
final listB = [correctMappedObject, correctMappedObject]
where i can ignore all elements where the mapping goes wrong.
I hope you can get the idea - i haven't seen the possibility to do this in the current implementation.

Hi @Windisch94, good idea, we might do it somehow as part of already proposed updates in #204.

Hi @Windisch94 new version just landed with safeMapping. You should be able to filter-out failed mappings.
Closing now, feel free to repoen if you think that safeMapping doesn't cover your needs.


Further nested folder causes crash (instead of being ignored)

Hi,
I have a folder achitecture that mostly match what fussel expects, but there are a few exceptions (subfolder within some albums). I thought they would be ignored as mentioned in the README but they appear to have caused the app to crash instead:
 > Importing album /mnt/Photos/160617 - Photos bedaine Cap-Rouge as '160617 - Photos bedaine Cap-Rouge'
 --> Processing /mnt/Photos/160617 - Photos bedaine Cap-Rouge/JosianneLapierrePhotographie-78.jpg...
 ----> Copying to '/home/fussel/app/fussel/web/public/static/_gallery/albums/160617 - Photos bedaine Cap-Rouge/original_JosianneLapierrePhotographie-78.jpg'
Traceback (most recent call last):
  File "./fussel.py", line 57, in <module>
    generator.generate_site(output_photos_path, output_data_path, http_root)
  File "/home/fussel/app/fussel/generator/generate.py", line 288, in generate_site
    faces, photo_data = self.process_photo(external_path, photo_file, album_folder)
  File "/home/fussel/app/fussel/generator/generate.py", line 28, in process_photo
    shutil.copyfile(photo, new_original_photo)
  File "/usr/lib/python3.6/shutil.py", line 120, in copyfile
    with open(src, 'rb') as fsrc:
FileNotFoundError: [Errno 2] No such file or directory: '/mnt/Photos/160617 - Photos bedaine Cap-Rouge/JosianneLapierrePhotographie-78.jpg'

The picture above is in fact located under: /mnt/Photos/160617 - Photos bedaine Cap-Rouge/Chambre - s_lection
...but then I realized I had not set my locale correctly, and there are french accents in there. So I fixed my locale and will retry. The error might go away.

Unfortunately it still fails:
 > Importing album /mnt/Photos/160617 - Photos bedaine Cap-Rouge as '160617 - Photos bedaine Cap-Rouge'
 --> Processing /mnt/Photos/160617 - Photos bedaine Cap-Rouge/JosianneLapierrePhotographie-78.jpg...
 ----> Copying to '/home/fussel/app/fussel/web/public/static/_gallery/albums/160617 - Photos bedaine Cap-Rouge/original_JosianneLapierrePhotographie-78.jpg'
Traceback (most recent call last):
  File "./fussel.py", line 57, in <module>
    generator.generate_site(output_photos_path, output_data_path, http_root)
  File "/home/fussel/app/fussel/generator/generate.py", line 288, in generate_site
    faces, photo_data = self.process_photo(external_path, photo_file, album_folder)
  File "/home/fussel/app/fussel/generator/generate.py", line 28, in process_photo
    shutil.copyfile(photo, new_original_photo)
  File "/usr/lib/python3.6/shutil.py", line 120, in copyfile
    with open(src, 'rb') as fsrc:
FileNotFoundError: [Errno 2] No such file or directory: '/mnt/Photos/160617 - Photos bedaine Cap-Rouge/JosianneLapierrePhotographie-78.jpg'

From the start it seems to think that the picture is in /mnt/Photos/160617 - Photos bedaine Cap-Rouge/, but it isn't. Since this isn't meant to be supported (sub-albums), a simple try & except FileNotFoundError would be a simple fix (band-aid style). A better fix would be to completely ignore images in subfolders. A suggested future feature (not critical) would be to support subalbums (subfolders).

Thanks for the report. I will fix the bug and also I think a message "skipping" is appropriate.
WRT the nested albums, definitely it is a possibiltiy, however it is a non-starter to show folders/albums + photos in the same space, because the album view doesn't work that way.
However, a setting perhaps that tells the generator to make all folders it finds into albums and just places them alongside all the other albums is definitely do-able.

WRT the nested albums, definitely it is a possibiltiy, however it is a non-starter to show folders/albums + photos in the same space, because the album view doesn't work that way.
A setting perhaps that tells the generator to make all folders it finds into albums and just places them alongside all the other albums is definitely do-able. (as opposed to supporting a hierarchichal album system in the app itself)

That would work, perhaps also using the root album title as the flattened album title's prefix? For ex.:
.../House
.../House/Garden
.../House/Stairs

...could be shown as:
House - Garden
House - Stairs

I expect users would at least want these subfolders grouped together in the album view.
P.S.: Thanks for your responsiveness!

The tricky part with grouping things together is how do you display a folder that has both photos and folders/albums directly inside it?
The component that shows the photos cannot show folders, and vice versa.

I see, but in my example, if .../House included photos as well as its subfolders, you could generate 3 albums:
House
House - Garden
House - Stairs

Sorry it was ambiguous, but by "grouped together in the album view" I only meant that I'd like them to be adjacent when albums are sorted alphabetically. Using the root album as a prefix for the "subalbum" would accomplish that automatically. They don't actually need to be nested; a flattened album structure is absolutely fine IMO.
A potential error would be if there's already a "root" album with the same name, i.e.:
.../House
.../House/Garden
.../House/Stairs
.../House - Garden

But then I'd simply fuse .../House/Garden and .../House - Garden under the same album in the generated site. That'd be the expected behavior IMHO.

That makes sense, and I'm open to that for sure.

@miek770 I'm implemented new logic for directory scanning.
You will find two new configuration options in the env file.
# Recursively process sub-folders as albums
RECURSIVE_ALBUMS="true"

# Pattern for album name creation of sub albums
# Following substitutions are available:
# - {parent_album} will be replaced with the parent album
# - {album} will be replaced with the album name
RECURSIVE_ALBUMS_NAME_PATTERN="{parent_album} > {album}"

Sub folders will now be scanned and albums created for them based on the pattern you specify. The above pattern will create child albums with the names:

top
top > middle
top > middle > bottom
...and so on

Code is on master branch.

As a followup there is now also the following settting:
# Setting to true will force a full rebuild of the gallery photos.
# Setting to false will only generate files which are missing or added
OVERWRITE="false"

Album generator will now ignore copying and generating thumbnails for those that already exist. Caveat: face detection still needs to happen as the data maps still need to be rebuilt. Generation is  significantly faster now though.
For my sample album:
OVERWRITE="true"    - Took 1m30.625s
OVERWRITE="false"   - Took 11.523s

Sorry I missed your responses, I'll try that ASAP and report back. Thanks.

As a followup there is now also the following settting:
# Setting to true will force a full rebuild of the gallery photos.
# Setting to false will only generate files which are missing or added
OVERWRITE="false"

Album generator will now ignore copying and generating thumbnails for those that already exist. Caveat: face detection still needs to happen as the data maps still need to be rebuilt. Generation is significantly faster now though.
For my sample album:
OVERWRITE="true"    - Took 1m30.625s
OVERWRITE="false"   - Took 11.523s

That's awesome, and also seems to be working on my end. Will close #18 once the scan completes and I get to test a rescan with no new photo.

@miek770 I think this ticket is done? I've created another ticket to handle the locale issues.

Yeah I'm pretty sure it is, I'll close it and reopen it if not. Sorry, got another error and lacked time to pursue further, got a few minutes now.

No worries. I only have bursts of time too. I usually have a couple quiet hours Sunday morning so you get a flurry from me haha.


cannot change the output dir for stringtie merge

After running stringtie for each sample, I want to merge the gtf by stringtie merge. But the output was written to a SRR folder, not the working folder, and the name has SRR1573523_hisat2_sorted_stringtie prefix, which cannot change
st.stringtie_merge(*tuple(gtfList),out_suffix="maizeMerged",**{"-p":"16"})

I have now added the parameter out_dir to the stringtie_merge function. If no out_dir is specified, merged file will be written in the same directory as the first input file. 51e27aaafce2c0833b9142636c112587e87f98a8


 I was waiting on tests to pass. I'll follow up on the comments.

I think that will still not jump to the fragment, made similar fix in my local branch initially, but it only solved url.

np :) In general, it's probably best if we all wait to get at least one :+1: from another collab before merging.

@aszwemin Jumping to the fragment is a scrolling problem, which is a separate issue.

It's because the URL is being constructed the wrong way. The hash fragment and query string are out of order. I'm going to submit an issue on history about it.

Do we need any sanity checks here when using hash history?

Well, we're now testing another aspect of it (I'd love to get some coverage reports generated...) but I think it's warranted.
But once they bug in history is fixed, this line:
expect(spy).toHaveBeenCalledWith({ you: 'doing?' }, '/hello#world?how=are')

changes to:
expect(spy).toHaveBeenCalledWith({ you: 'doing?' }, '/hello?how=are#world')

So, it's not so much of a sanity check. It's actually testing the valid construction of a URL.

@mjackson I hacked something like this locally, not sure if it's a good enough solution though:
 87         if (this.props.hash) {
 88             container = _react2['default'].findDOMNode(this);
 89             element = document.getElementById(this.props.hash.slice(1));
 90             if (element) window.scrollTo(container.offsetLeft, element.offsetTop);
 91         }

Happy to make a pr if this is what you had in mind, but not sure how generic it would be


Add cloudscale.ch driver

Add cloudscale.ch driver

The feature is verified with Rancher server rancher\rancher:master-head version master-3385-head
After enabling cloudscale in Node Drivers:

Able to deploy a cluster, scale up and down nodes, and deploy workloads:


Fix for issue #16 (deleting ignores allowDelete setting)

Added check for allowDelete before removing tag when clicking on 'X' button; added check for allowDelete before adding the 'X' button.

See my comment in Issue #16. This seems to be some kind of misunderstanding.


Use noexcept as advise by gcc -Wnoexcept

@toregge PR

Note that some existing noexcept specifiers for vespalib::small_string might have to be revisited (i.e. do we want to keep them or do we want to match std::string semantics).


when use img condition，set  do_rgbd_loss = False ，why the result is nothing？

Description
zero123 use sjc loss，but in this repo we use sds loss（img condition）.when i set do_rgbd_loss = False, the result is nothing.
Steps to Reproduce
use img condition ,and set do_rgbd_loss = False
Expected Behavior
why the result is nothing
Environment
torch=1.8.0,python=3.7,cuda=11.6

Without an rgbd_loss from the img condition, and without any text prompt, the results would be nothing.


[Blog] Spotlight for k8s upstream training in Japan

xref. https://github.com/kubernetes/website/pull/48039
see https://github.com/kubernetes/website/pull/48039#pullrequestreview-2380578582
Description
We are the organizing team for k8s upstream training in Japan. see https://github.com/kubernetes-sigs/contributor-playground/tree/master/japan for more details
We would like to feature our efforts in k/website blog!
Deploy preview: https://deploy-preview-541--kubernetes-contributor.netlify.app/blog/2024/10/28/k8s-upstream-training-japan-spotlight/
Important Date

We plan to move this PR out of draft status by early October
We would like to publish this blog post within October early November (November 10?)

Let me know if you’d like any adjustments!
Issue
Closes: #

/cc @sftim @shu-mutou @ziyi-xie @atoato88

/hold
pending an agreed publication date being set
OK to unhold if the publication date is agreed and in the future

This changes can be made in a different PR though.
/lgtm

[IMPORTANT NOTE] When you review, please comment on the https://github.com/kubernetes/website/pull/48039 to avoid discussing across multiple PRs.

Actually we prefer to have the comments on the PR that adds the primary / original copy. So, this PR.

Suggesting 28th October as publication date, right after the weekend. There's nothing against publishing it during the weekend, but it's not generally done due to traffic being less outside of the work week.

Thank you all for the great reviews and supports!!
Based on @sandeepkanabar 's comments on k/website and @fsmunoz ’s feedback, I’ve made some changes.
Do we need a bit more consensus regarding the publication date?
This PR is somewhat time-sensitive, but the event is still over a month away. However, if it could be published by 10/28, that would be great.
I understand that there are PRs in the review queue and that reviewer resources are limited, thank you
/cc fsmunoz

/lgtm

/assign @sftim @natalisucks
for approval

The author information looks a little odd; the article is attributed to:
Junya Okabe (University of Tsukuba) Organizing team of Kubernetes Upstream Training in Japan
which could mean that Junya Okabe _is _ the organizing team, or is part of the team, or that the article has two coauthors: Junya Okabe and the organizing team.
It would be good to clarify which was meant.
Anyway:
/approve
I will unhold shortly. Please bear with me.

/hold cancel
The mirror article has LGTM and approval, too.

Thanks! I'll fix some nits later :)


Support mixer control to provide statistics.

What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #132
Special notes for your reviewer:
Release note:

Support mixer control to provide statistics.

/approve


Remove IdMap from source file.

The id-map grows with the code rapidly, and even reducing its size won't help much; still, the id-map tends to take 100x more space than the code it describes. But perhaps we don't need to store them in file at all.
Main idea
Instead of storing id-map in source file, we could exchange it using Language Server API.
The id-map purpose is to make an identification of particular AST nodes, what in turn is needed to:

Assign node metadata (like position, color, etc.) and - in the future - widget metadata (like which widget was directly picked by the user).
#10182 identify expressions in messages between GUI and Engine (where visualization is attached, what is the type of expression, etc.) Because of execution contexts and visualizations, these identifications should be persistent.

The second point do not require AST IDs persistence, while the first point may be handled by storing direct spans instead of IDs in the source file.
Further ideas and optimizations

To avoid initial exchange and reduce id-map size, we could assume some deterministic way of assigning IDs to nodes without id-map entry, for example: for every node with assigned ID from map, we assign increments of this ID to its children in DFS order (of course, if we meet another node with already assigned ID, we skip the entire subtree).
or, we could resign from exchanging IDs, and just add list of span pairs (A, B) meaning, that old code's span A's identity should be passed to new code's span B. Both parties then should manage updating their information about visualizations, execution stacks etc.

### Gui Tasks
- [ ] Add a draft title or issue reference here

### Engine Tasks
- [ ] https://github.com/enso-org/enso/issues/10182

The Truffle instrumentation is built around SourceSectionFilter, not UUIDs. The filter uses ranges (offset, line, column) and tags. It would be great if we adhered more closely to the capabilities offered by Truffle when eliminating the IdMap usage.

Let's assume the following is implemented: #7954

Then the AST is hosted in the same process as the engine and its instrumentation. Assuming y.js is efficient in synchronizing AST modifications, we don't need UUIDs to keep element identities. The AST elements themselves represent identity. Visualizations shall become part of the AST - attaching/removing them modifies some attribute of clearly identified AST element.  When there is an AST change that modifies the source code we need to traverse the AST and recompute ranges (offset, line, column) of elements that require instrumentation. A change in the source code always comes with new ranges. All of that is done inside of a single process without any need for network communication via a special protocol.
Longer term future vision: with the AST being in the same process as Truffle we should make a connection between the AST elements and Truffle nodes and avoid reparsing the whole .enso file when only a subtree is changed.

I have rephrased the strategic vision in a separate document. An essential part of it still remains the sharing of ASTs among peers via y.js server.

#10182 will add an optional IdMap parameter in the text/applyEdit request.
I propose to simplify the serialized IdMap elements format from the current
[[{"index":{"value":0},"size":{"value":4}},"bfae92f7-07d0-4886-b37b-a26e17ee943f"],...]

to an array of 3 elements: index, size and uuid
[[0,4,"bfae92f7-07d0-4886-b37b-a26e17ee943f"],...]

#10182 will add an optional IdMap parameter in the text/applyEdit request.
I propose to simplify the serialized IdMap elements format from the current
[[{"index":{"value":0},"size":{"value":4}},"bfae92f7-07d0-4886-b37b-a26e17ee943f"],...]

to an array of 3 elements: index, size and uuid
[[0,4,"bfae92f7-07d0-4886-b37b-a26e17ee943f"],...]

I'm ok, but perhaps we should support both formats for some time.

I propose to simplify the serialized IdMap elements format from the current
to an array of 3 elements: index, size and uuid
[[0,4,"bfae92f7-07d0-4886-b37b-a26e17ee943f"],...]

the format change has been tracked as #7989

I'm ok, but perhaps we should support reading both formats for some time.

Yes, being able to read previous node positions in new IDE is essential.

I'm not going to change the parser. I was talking about the JSON-RPC text/applyEdit parameter

#10283 adds an optional idMap parameter to text/applyEdits that overrides/complements the IdMap in the file
interface TextApplyEditParameters {
  /** The file edit. */
  edit: FileEdit;

  /**
   * A flag indicating whether we should re-execute the program after applying
   * the edit. Default value is `true`, indicating the program should be
   * re-executed.
   */
  execute?: boolean;

  /**
   * An identifiers map associated with this file as an array of
   * index, length, uuid triples. The old id map format that was used in the
   * source file is also supported.
   */
  idMap?: [number, number, UUID][];
}

@farmaazon the next step could be to keep in the file only the IDs that are used in the second metadata line (with node positions, etc.) and send the rest of the IDs with the text/applyEdit request. This should reduce the size of the IdMap section in the file metadata. If you're ok with the idea, I'll implement it as a followup PR.

@farmaazon the next step could be to keep in the file only the IDs that are used in the second metadata line (with node positions, etc.) and send the rest of the IDs with the text/applyEdit request. This should reduce the size of the IdMap section in the file metadata. If you're ok with the idea, I'll implement it as a followup PR.

Looks good, I'm ready to help with ydoc-server code if needed.


Check cache store support for tags

The issue arises when using a cache driver which doesn't support cache tags, therefore if the tags method wasn't explicitly called and the current cache driver doesn't support tags it shouldn't be invoked by default on all calls to mitigate any unwanted "This cache store does not support tagging." exception.
This solves the issue for cache drivers which doesn't support tags such as the "file" driver.

But this would result in the cache calls not being scoped at all (on non-redis drivers) when users expect them to be scoped, wouldn't it?

It would if the driver supports it. It doesn't change the default behavior of the package, the changes only mitigate the exception if the driver doesn't support it and I don't think it'd be beneficial to restrict developers to drivers that support tags only.
It should be documented to let developers make an educated decision since the modified CacheManager intercepts all cache calls by default.

I don't think it'd be beneficial to restrict developers to drivers that support tags only

Simply disable the CacheTenancyBootstrapper in the config.
If I'm not misunderstanding, this PR would lead to developers expecting the scoping to take place (cache bootstrapper enabled), but it wouldn't do anything if a non-Redis driver is being used.

I don't think it'd be beneficial to restrict developers to drivers that support tags only

Simply disable the CacheTenancyBootstrapper in the config.

Sorry, I didn't know about this, I will apply the recommended solution instead.


external GeoNode reference uses GPL

cc @kalxas
The code at https://github.com/geopython/pycsw/blob/master/pavement.py#L313 references what is now https://github.com/GeoNode/geonode/blob/master/pavement.py#L598 (i.e. pavement.py, def kill).
GeoNode is GPL

Good catch!
Yes this is an issue. We can not re-license this code to MIT.

@kalxas I can remove that code and replace with this instead:
def kill_process(procname, scriptname):
    """kill WSGI processes that may be running in development"""

    # from http://stackoverflow.com/a/2940878
    import subprocess, signal
    p = subprocess.Popen(['ps', 'aux'], stdout=subprocess.PIPE)
    out, err = p.communicate()

    for line in out.splitlines():
        if procname in line and scriptname in line:
            pid = int(line.split()[1])
            info('Stopping %s %s %d' % (procname, scriptname, pid))
            os.kill(pid, signal.SIGKILL)

Would that work?  Will apply to master and 1.10.

Fixed in master and 1.10.


Some improvements for the windows plugin PS script

Need to make the following improvements for the windows plugin installer script (install-vdvs.ps1):

Support uninstallation
Support Get-Help
Make uri parameter optional, set default value to the latest version

All issues are addressed except that there's no default value of the download URL of the windows plugin right now. We can add the default value any time once it's available.


Pin / Address sharing with Web Share Api

feat: add share button by using navigator.share & navigator.chanShare for mobile-friendly sharing

ne durumdayız? @demirhancosku


Add celery_queue_length, celery_active_consumer_count gauge metrics for exporter

close #100
Hi Dani, as promised I am making a PR to add queue_length metric for exporter.
The implementation is simple. A daemon thread will start with main thread and it will scrape length of queues which declare by developer.
Developer can add concerned queues to exporter by --track-queue option. e.g. celery-exporter --broker-url=amqp://guest:guest@host.docker.internal:5672/ --track-queue celery --track-queue my_queue
Default queue length scrape interval is 30s and it can be customized by --queue-track-interval option. e.g. celery-exporter --broker-url=amqp://guest:guest@host.docker.internal:5672/ --track-queue celery --queue-track-interval 60
Then the exporter will export broker queue length metrics like this
celery_queue_length{queue_name="celery"} 3.0
celery_queue_length{queue_name="my_queue"} 0.0

Looking forward to your opinions.
Thx.

Looking good. Are there any other metrics we can get from .queue_declare() ?

According to kombu API Refrence, queue_declare returns

A named tuple representing the declared queue as a named tuple. The tuple values are ordered as queue, message count, and the active consumer count.

We can add Gause(active_consumer_count){label=queuename} metric to exporter if it's necessary.

Could you add the active consumer count? That would be awesome :)

celery_active_consumer_count is added.

Would it be possible to get the queue length and consumer count for all queues, without having to specify them as options in the exporter cli?

Would it be possible to get the queue length and consumer count for all queues, without having to specify them as options in the exporter cli?

The reasons for doing this are as follows:

The lower kombu API have to declare queue first and then fetch the information of queue. So the specify of queues from developer is required.
Maybe there is a way to auto discover queues in broker. But I think not every queue in broker is used by celery or by celery of "current developer". There is possible that the broker is used by many developer's celery instance so the data of every queues in the broker may cause confused. e.g. Celery will create queues like celeryev.xxxx to transport worker's event message, and these queues should not be concerned by developer.

So, I think the specify from developer is more reasonable and Explicit.

Could you have a second look that it works? I believe the test should also show a consumer count of 1.

Sure. I have checked the source code of kombu and the documentation of rabbitmq, this metric does reflect the number of consumers. And I also check it on my host. It's really works. It's there any possible that the consumer process is already down when you read the metrics?

Perhaps we could scrape queue length before building the output:

Yep. But after that, the pull request will become a non-constant complexity operation. It will affect by the length of queues which is O(n) complexity. It's acceptable?

The lower kombu API have to declare queue first and then fetch the information of queue. So the specify of queues from developer is required.

I managed to run a breakpoint() in the test suite to inspect the celery app. The app has an inspect utility for listing queues. This seems to work for Redis, but you can try it for RabbitMQ to see if it shows the same data. I set the breakpoint() here https://github.com/danihodovic/celery-exporter/blob/master/src/exporter.py#L201
self.app.control.inspect().active_queues()

{
	'gen89100@x1': [
		{
			'name': 'celery',
			'exchange': {'name': 'celery', 'type': 'direct', 'arguments': None, 'durable': True, 'passive': False, 'auto_delete': False, 'delivery_mode': None, 'no_declare': False},
			'routing_key': 'celery',
			'queue_arguments': None,
			'binding_arguments': None,
			'consumer_arguments': None,
			'durable': True,
			'exclusive': False,
			'auto_delete': False,
			'no_ack': False,
			'alias': None,
			'bindings': [],
			'no_declare': None,
			'expires': None,
			'message_ttl': None,
			'max_length': None,
			'max_length_bytes': None,
			'max_priority': None
		}
	]
}

This should give us a list of queues for each worker. We can flatten the list and then get the length for each.

Sure. I have checked the source code of kombu and the documentation of rabbitmq, this metric does reflect the number of consumers.

In that case shouldn't the unit test you added show 1 consumer instead of 0? https://github.com/danihodovic/celery-exporter/pull/118/files#diff-fb60222581054c3ac15e1981679b0a596c22dfeb483873337979183826f559ffR76. In any case this is not a deal breaker.

Yep. But after that, the pull request will become a non-constant complexity operation. It will affect by the length of queues which is O(n) complexity. It's acceptable?

That's fine. Given that there is a finite set of queues (usually less than 10) I don't think reading queued data for all queues will have an outsized performance impact. If it does, we can cache the values:

If a metric is particularly expensive to retrieve, i.e. takes more than a minute, it is acceptable to cache it. This should be noted in the HELP string.

https://prometheus.io/docs/instrumenting/writing_exporters/#scheduling

Thanks for your advice.
According to the previous discussion, I will make the following modification:

Remove --track-queue and --queue-track-interval option and fetch track queue list by celery_app.inspect().active_queues.
Remove daemon thread. celery_queue_length and celery_active_consumer_count  metrics scrape only perform at metrics pulling
Add non-zero celery_active_consumer_count metrics unit test case.

Those modifications will be committed ASAP.

Something unexpected happened while I was adding non-zero celery_active_consumer_count metrics unit test case.
It seems the memory://localhost broker type does not support follow the amqp protocol so the queue_declare method can not get the correct celery_active_consumer_count.
So I also verified it with redis as broker and can not get the correct celery_active_consumer_count too.
Should we keep the celery_active_consumer_count metric?

Something unexpected happened while I was adding non-zero celery_active_consumer_count metrics unit test case.
It seems the memory://localhost broker type does not follow the amqp protocol so the queue_declare method can not get the correct celery_active_consumer_count.
So I also verified it with Redis as broker and can not get the correct celery_active_consumer_count too.
Should we keep the celery_active_consumer_count metric?

I dig into the kombu implementation and find some clue.
queue_declare will raise amqp.exceptions.ChannelError: Channel.queue_declare: (404) NOT_FOUND - no queue 'celery' in vhost '/' when there is no message in Redis broker because the "queue" in Redis is a list and it seems not durable. (The key will be deleted when the queue is empty)

If the queue is empty there is no active consumer, have I understood this right? In that case we could set it to zero.

If the queue is empty there is no active consumer, have I understood this right? In that case we could set it to zero.

Yep, but I also test with non-empty Redis queue and alive worker. The queue_declare method didn't raise but celery_active_consumer_count is still 0.
So, I guess only broker that support amqp protocol will return consumer count.

What is your preference? Keep if for RabbitMQ or remove it so that it's uniform for all brokers?

What is your preference? Keep if for RabbitMQ or remove it so that it's uniform for all brokers?

I think we can keep the metric as long as we explain the limit of broker type in the doc.

Sounds good, maybe we can make a PR to Kombu to add the functionality for Redis.

Is the PR ready for review?

Yes

Nice work @homholueng :clap: 伟大的工程工作

Released as danihodovic/celery-exporter:0.5.0
Can you update README.md to add the new metrics? https://github.com/danihodovic/celery-exporter#metrics

https://github.com/danihodovic/celery-exporter#metrics

Sure


[3.2.11] Project Browser preferences menu should be on console

All the options on this menu, except the Package List Visible and Package Group Visible, apply to every browser everywhere and all future opened browsers.  This menu belongs on the console, it makes very little sense where it is.
Package List Visible and Package Group Visible only apply to a specific tab, which is two degrees narrower (see issue #887)
I'm not saying this is critical for 2022,...

Since the Package list visible and Package groups visible menu items now apply to all browsers, I believe those menu options should stay put. @LisaAlmarode thoughts?

If you have two separate project browser windows open (not tabs in one windows, but actually separate windows), changing Package List Visible on of them, one modifies all of them.
The preference menu item source styler, makes changes that apply only to the current browser windows (all tabs in that window), but it doesn't have the side-effect of modifying other project browser windows.  This is the expected behavior for a browser-specific preference.  The implication of having the menu item on the project browser, is that you could have some project browsers showing the pane, and another one not showing it, but that's not possible.
Also anything in the preferences file should be on the Jadeite menu, that's a clear clue that something is system-wide and belongs on the console.

Moved browser preferences to transcript Jadeite menu since they are universal browser settings.


Do not require JCommander when run via Ant

See #255.  I can't currently use TestNG because we are doing Ant builds, and fetching dependencies from a private maven repository that does not contain JCommander.

Well, this is probably going to cause me to switch back to JUnit. JCommander is not available via our private dependency management system and it serves up the maven jar for testng (and no others).
It's unclear why to me why the ant task needs a command-line processor.

I'm not sure what the problem is...

I'm using ant, but I am unable to require JCommander as a dependency -- it's not available from the build servers that only have access to our private maven repository.  So, due to the ant task requiring a command-line processor (huh?) I am unable to use TestNG.
For now, I am continuing to use JUnit.  I mainly left the comment to prevent myself from trying TestNG again until after we switch build systems away from Ant.

I don't see any dependency of TestNGAntTask on JCommander, what am I missing?
Besides, can't you bring JCommander into your private Maven repo?

When I run the testng ant task without including JCommander in the class path, I get the same error listed in #255:
[testng] java.lang.NoClassDefFoundError: com/beust/jcommander/ParameterException [testng] Caused by: java.lang.ClassNotFoundException: com.beust.jcommander.ParameterException [testng] at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
As far as adding it to the maven repo, our project doesn't have authorization to do that, but it is something I've considered for the future.

Note that it's a NoClassDefFound, not a ClassNotFound, so JCommander is on the class path.

It's both.  NoClassDefFoundError was caused by "java.lang.ClassNotFoundException: com.beust.jcommander.ParameterException"

Currently and as I understand, TestNGAntTask is just building a command line for TestNG which will be parsed by JCommander then.
So, JCommander is mandatory for the ant task.
I should be possible to remove the dependency but won't be an easy task (and not a priority IMO).


Remove CAS attributes from snippets

Fixes https://github.com/dotnet/docs/issues/29143.

Oops, nevermind!

Oops, closed the wrong PR.

This is good to go. The remaining snippets 5000 errors are either for 2 C++ snippets (which I have no idea how to add a project file for), or are false positives (I believe this is a bug in snippets 5000).
dotnet-desktop-guide/samples/snippets/cpp/VS_Snippets_Winforms/System.Windows.Forms.KeyboardInputForm/cpp/form1.cpp
dotnet-desktop-guide/samples/snippets/cpp/VS_Snippets_Winforms/System.Windows.Forms.WebBrowser/CPP/form1.cpp
dotnet-desktop-guide/samples/snippets/csharp/VS_Snippets_Wpf/InvokePatternApp/CSharp/snippets.5000.json
dotnet-desktop-guide/samples/snippets/visualbasic/VS_Snippets_Wpf/InvokePatternApp/VisualBasic/My Project/Application.Designer.vb
dotnet-desktop-guide/samples/snippets/visualbasic/VS_Snippets_Wpf/InvokePatternApp/VisualBasic/My Project/Resources.Designer.vb
dotnet-desktop-guide/samples/snippets/visualbasic/VS_Snippets_Wpf/InvokePatternApp/VisualBasic/My Project/Settings.Designer.vb
dotnet-desktop-guide/samples/snippets/visualbasic/VS_Snippets_Wpf/InvokePatternApp/VisualBasic/snippets.5000.json

Thanks for the help! Looks like we're down to just the two C++ files now.


Incompatibility with numpy 2.0 not written in pyproject.toml

Describe the bug
As discussed in https://github.com/cvxpy/cvxpy/issues/2389, cvxpy is not yet compatible with numpy 2.0. However, in pyproject.toml, this is not clearly stated as there is no upper cap on numpy's version.
dependencies = [
    ...
    "numpy >= 1.15",
    ...
]

Now that numpy 2.0 is released, this breaks some installations. In my case, pdm tries to install cvxpy 1.5.1 alongside numpy 2.0, which then leads to the error described in https://github.com/cvxpy/cvxpy/issues/2389.
Expected behavior
If it requires significant work to make cvxpy compatible with numpy 2.0, I suggest to release a patch of cvxpy (1.5.2) in which the pyproject.toml is updated to reflect the incompatibility:
dependencies = [
    ...
    "numpy >= 1.15, <2.0.0",
    ...
]

The compatibility could then be provided in a future release, and the upper cap on numpy's version could then be removed.

Hello @ValerianRey thanks for bringing this issue up. We did in fact plan for the NumPy release by updating the swig interface which caused these build errors.
I just made a PR updating the pyproject.toml to reflect those changes. The issue should be resolved quite soon with a new minor release.
In the meantime, you can try to build cvxpy from source into your env, then once you try to install pdm it should be smooth sailing from there :)

We just released CVXPY 1.5.2, which is compatible with NumPy >= 2.0 (and also backward compatible!).
You might still see installation issues, as we are waiting for SCS and OSQP to do the same.
In the meantime, instead of cvxpy, you can add cvxpy-base + your solver of choice (assuming it is compatible with the new NumPy release).
I'll leave this issue open as a status tracker:

[x] CVXPY (https://github.com/cvxpy/cvxpy/pull/2475)
[ ] OSQP (https://github.com/osqp/osqp-python/pull/146)
[ ] SCS (https://github.com/bodono/scs-python/pull/99)
[x] ECOS (https://github.com/embotech/ecos-python/pull/54)

You might still see installation issues, as we are waiting for SCS and OSQP to do the same.

Note that OSQP is now compatible with NumPy 2.0 as of 0.6.7.post0. The PR linked above is actually not for the stable release of OSQP, it was made to the 1.0 beta tree. PR https://github.com/osqp/osqp-python/pull/147 implemented the NumPy 2.0 compatibility for the stable version.

I'm using latest cvxpy 1.6.0 and numpy 2.2.0, and it still cause this error in my M1,
AttributeError                            Traceback (most recent call last)
AttributeError: _ARRAY_API not found

(CVXPY) Dec 21 05:11:24 PM: Encountered unexpected exception importing solver ECOS:
ImportError('numpy.core.multiarray failed to import')

A module that was compiled using NumPy 1.x cannot be run in
NumPy 2.2.0 as it may crash. To support both 1.x and 2.x
versions of NumPy, modules must be compiled with NumPy 2.0.
Some module may need to rebuild instead e.g. with 'pybind11>=2.12'.

If you are a user of the module, the easiest solution will be to
downgrade to 'numpy<2' or try to upgrade the affected module.
We expect that some modules will need time to support NumPy 2.

Using numpy==1.26.4, every just works.
Can you help with this?


Rotate/Deconflict labels

From @joebayles on August 10, 2016 18:50
Offer the option to rotate longitudinal labels, and deconflict labels that overlap in the corners (see below).

@kgonzago
Copied from original issue: ArcGIS/Grid-Overlay#4

This is what it looks like now:

This is the exact spot that was identified in the first version.

To fix the view of a specific location pan the map to center the area of interest to be the center point on the map.


Problem with ObjectHydrator

I've just noticed this weird behaviour:
Considering I have an entity "area" which contains a collection of "badges".
With "area" ID1 contains (Badge ID2, Badge ID3, Badge ID4)

I make a request to find a list of objects with a specific Item in collection (areas with badge id 2).
I make a second request to find an object (which was in the previous list) with all the linked badge.

But when I get the badge entity, I only the badge id 2 in collection. Is it a known behavior (cache in Object hydratator) or a bug? For me, as the query is different, we can't reuse the same object, so it seems to be an issue but can you please confirm.
Example:
$areas = $this->entityManager->createQueryBuilder()
    ->select('a, b')
    ->from('PTCNoventoBundle:Area', 'a')
    ->join('a.badges', 'b', 'WITH', 'b.id = :badgeId')
    ->setParameter('badgeId', 2)
    ->getQuery()->useResultCache(false)->getResult();

dump($areas);

Result:
array:8 [▼
  0 => Area {#2646 ▶}
  1 => Area {#2676 ▶}
  2 => Area {#2681 ▶}
  3 => Area {#2686 ▶}
  4 => Area {#2691 ▶}
  5 => Area {#2696 ▶}
  6 => Area {#2701 ▶}
  7 => Area {#2706 ▶}
]

$area = $this->entityManager->createQueryBuilder()
    ->select('a, b')
    ->from('PTCNoventoBundle:Area', 'a')
    ->join('a.badges', 'b')
    ->where('a.id = :id')
    ->setParameter('id', 1)
    ->getQuery()->expireResultCache()->getSingleResult();

dump($area);

Area {#2646 ▼
  -id: 1
  -name: "RED"
  -color: "FF0000"
  -badges: PersistentCollection {#2620 ▼
    -snapshot: array:1 [ …1]
    -owner: Area {#2646}
    -association: array:21 [ …21]
    -em: EntityManager {#1066 …11}
    -backRefFieldName: null
    -typeClass: ClassMetadata {#449 …}
    -isDirty: false
    #collection: ArrayCollection {#2640 ▼
      -elements: array:1 [▼
        2 => Badge {#2653 ▶}
      ]
    }
    #initialized: true
  }
  #createdAt: DateTime {#2649 ▶}
  #updatedAt: DateTime {#2648 ▶}
  -logEnabled: true
}

You are filtering on a fetch-join (a and b are both selected), which will break hydration.
While this is supported, it is a risky operations, and you shouldn't do it, ever.
The problem is that a entries will only have a subset of b entries it actually references, and by hydrating the results this way you are also keeping this inconsistent state in memory.
See also http://stackoverflow.com/questions/13603054/doctrine-fetch-join

Ok thanks for your reply.


Remove HTTPS from Revel

As mentioned by @pushrax, Revel is currently handling functionality that it doesn't need to, such as HTTPS.
We need to consider what Revel could do without to enhance separation of concerns and increase the focus of Revel.
@revel/core Thoughts?

https://github.com/revel/revel/issues/918#issuecomment-89431129 @jniltonho wants to keep HTTPS support.

Server engine allows this to be done


[ContainerInstance]Generated the track 2 SDK for ContainerInstance.

Description
Generated code and wrote test cases.
Work Content details

Generated track 2 SDK code.
Wrote test cases and successfully record.
Modified assembly version(1.0.0-beta.1) and namespace(ContainerInstance to Microsoft.ContainerInstance ).

/azp run

Should the pipeline config be updated to pick up this new SDK project in CI and how?

Should the pipeline config be updated to pick up this new SDK project in CI and how?

The previous Pipeline CI PR should be merged before this one: #18349

/check-enforcer reset

/azp run net - containerinstance - ci

HI @allenjzhang,
For fix swagger issue, I used the specified modelerfour version(4.15.448) which cause CI(Build Analyze) to fail.
Thanks,
Lucas

HI @allenjzhang,
For fix swagger issue, I used the specified autorest/modelerfour version(4.15.448) which cause CI(Build Analyze) to fail.
Thanks,
Lucas

Issue was fixed after syncing master. @YalinLi0312 could you take a look again? Thank you.

Thanks Allen for approving.
As we disscuessed in mails, we are going to put this pull request on hold.


remove legacy znode when delete namespace or tenant forcefully

Fixes #11195
Motivation
Fix metadata not cleaned after delete namespace or tenant forcefully.
Modifications
For force delete of namespace
Add delete for znode  /managed-ledger/tenant/namespaces/persistent , /managed-ledger/tenant/namespaces/non-persistent and  /managed-ledger/tenant/namespaces  if exist.
For force delete of tenant
Add delete for znode  /managed-ledger/tenant if exist.
Verifying this change
This change added tests and can be verified as follows:
Add new test for force delete of namespace in AdminApiTest.testDeleteNamespaceForcefully
Extended test for force delete of tenant.
Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): ( no)
The public API: ( no)
The schema: (no)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)

Documentation

Does this pull request introduce a new feature? (no)

/pulsarbot run-failure-checks

@murong00 @BewareMyPower PTAL

LGTM, could you confirm if the ZK related API could be replaced with the metadata store API? @merlimat

@BewareMyPower Do we need more discuss about this pull request?

I think we can merge it first.


UI: Update Settings Tab

Theme color choice will be removed from the Settings tab and the documentation that mention theme options will be updated accordingly.

closed by #322


Cannot connect on port numbers other than 7777

MITransport.cs needs to override Client Connect that uses URI
E.g.
    public override void ClientConnect(Uri uri)
    {
        _innerTransport.ClientConnect(uri);
    }

Thank you.
I tried calling method StartClient URI instead of using NetworkManager HUD and it failed to connect as you said.
I updated in commit e0e7a8b7e26435ae30905927c22ecf6b3104a40c


Text overlay not showing

bingwallpaper version 1.5.0 (linux/x86_64)
CONFIG:
image_dimension_width = 2560
image_dimension_height = 1440
text_overlay_position = "TOP_RIGHT"
target_filename = "/home/user44/.wallpapers/bingwallpaper.png"

CMD:
bingwallpaper -c /home/user44/.config/bingwallpaper/bingwallpaper.conf > /tmp/bingwallpaper.log
RESULT:
thread 'main' panicked at src/bingwallpaper/textoverlay.rs:49:89:
called `Result::unwrap()` on an `Err` value: Decoding(DecodingError { format: Exact(Png), underlying: Some(Format(FormatError { inner: InvalidSignature })) })
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Hi @mrlee14
I reproduce the error. It seems occur because the library detect file format (PNG, JPG, ...) from the filename (bad practice). As workaround, you can edit your configuration file to change file extension from .png to .jpg (file downloaded from Bing is really in JPG format).


Dynamic decimals and foced decimals to each view

Can you make this funcionality?

Sorry, not quite sure what you mean. Could you give an example?
On Feb 11, 2016 6:33 PM, "carmas123"<EMAIL_ADDRESS>wrote:

Can you make this funcionality?
—
Reply to this email directly or view it on GitHub
https://github.com/BlacKCaT27/CurrencyEditText/issues/10.


disable fleet-controller-configmap updates

IMPORTANT: Please do not create a Pull Request without creating an issue first.
Problem:

Rollback changes to reconcile fleet-controller configmap introduced as part of: https://github.com/harvester/harvester/issues/4565
This should not longer be need as the upgrade path is already address in v1.2.1 release.
The update to configmap seems to be causing the fleet-controller to be redeployed due to changes in fleet-controller.
Solution:

Related Issue:
https://github.com/harvester/harvester/issues/6851
Test plan:

@ibrokethecloud Do we plan to remove this controller on v1.5.0 ?

@w13915984028 i was hoping to remove this as it was only added for 1.2.x to work around a known bug related to rancher + fleet. We have had to add more work arounds to keep this working so may be best to drop it and simplify the upgrade path.

@ibrokethecloud That sounds great. BTW, could you create a new issue for this purpose, we will have enough time to cover all possible scenarios on v1.4.1/v1.5.0.


Resolves #185 - Flesh out user scenarios Pt 1

The Problem/Issue/Bug:
We currently do not have documentation around how DDEV UI operates and therefore cannot use the scenarios for testing/development purposes.
How this PR Solves The Problem:
Bit by bit we are going to flesh out all the user scenarios for DDEV UI. This is the first pr of many as we fill out this feature file!
@alkymst any and all feedback on how we can better validate that something has stopped/started/been created other than just looking at the UI would be super awesome!
Related Issue Link(s):
https://github.com/drud/ddev-ui/issues/185

@alkymst : when you get a chance, can you review this one? ty

@mafriend SO I added some comments and it looks like we have a conflict with merging ^ Let me know if you need me to take a look to resolve the conflict.

Hey @alkymst ! I've gone ahead and addressed your feedback as well as fixing the merge conflicts! I'm going to go ahead and merge this in since it was approved a few days ago, but if you have any feedback on the changes, please let me know!


Is the note about the restriction to proxy selectorless services still valid?

This is Support

Maybe I am misreading the next indicated constraint about proxying the service without selectors -- https://kubernetes.io/docs/concepts/services-networking/service/#service-no-selector-access --

The Kubernetes API server does not allow proxying to endpoints that are not mapped to pods. Actions such as kubectl proxy service-name where the service has no selector will fail due to this constraint.

But I am not getting any constraint about proxying it .... 🤔
How to reproduce:

kind create cluster -- use simple default kind cluster with 1 node --
Dummy Service without selectors to create

Example:

apiVersion: v1
kind: Service
metadata:
  name: external-name-without-selectors
spec:
  type: ExternalName
  externalName: without.selectors

kubectl proxy external-name-without-selectors

I don't get any restriction and you can access to the Kubernetes API Server through the default port locally -- "Starting to serve on <IP_ADDRESS>:8001" --

Note:

Tracing the PR and issue about this note

https://github.com/kubernetes/website/pull/38617
https://github.com/kubernetes/website/pull/29752
https://github.com/kubernetes/kubernetes/issues/105092

GitHub is not the right place to file questions. A bug report with details on how to reproduce the symptoms would be more valid.
Please add:

what version of kind you use
what IP address family the cluster uses
what steps you took to ensure that without.selectors resolves to an IP address
how you verified that kubectl does actually forward to that external name

I am not sure what kubectl proxy does for type: ExternalName Services. We should document that better.

/priority awaiting-more-evidence
/remove-kind support
/triage needs-information
If you really do only want support @dancer1325, then - because this is the wrong place to ask for it - you could re-add the label using /kind support, and then close the issue.
In that case, also see https://github.com/kubernetes/kubernetes/issues/new/choose for guidance on getting support.

Hi @sftim ,

what version of kind you use

kind v0.20.0 go1.20.5 darwin/arm64

what IP address family the cluster uses

IPv4

what steps you took to ensure that without.selectors resolves to an IP address
how you verified that kubectl does actually forward to that external name

I didn't put any effort here on confirming it
I just chose a Service without selectors, such as an externalName service, to check that constraint on proxying service without selectors

If you really do only want support @dancer1325, then - because this is the wrong place to ask for it - you could re-add the label using /kind support, and then close the issue.

🆗

/kind support


Add support for  elements

You can learn about what exactly this element is, and what sort of props it has here: click me!
What we want:

builder variants for each tag
element variants for each tag
All props defined in the above link are supported
It follows standard practices for this repo
It has proper KDoc annotation, in a similar style to the others
The code is idiomatic and not verbose

what I have to do in this task.Please explain . And I want to contribute in this as I know HTML .Please assign this to me.

what I have to do in this task.Please explain . And I want to contribute in this as I know HTML .Please assign this to me.

Same with me, can we both collaborate on our project?? Reply me I'll merge your request


style(client): overlay frame show scrollbar

Description
When the page displays an error message pop-up window, if the content is too long, it is more friendly to display a scrollbar.

Additional context

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[ ] Read the Contributing Guidelines.
[ ] Read the Pull Request Guidelines and follow the PR Title Convention.
[ ] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[ ] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

@bluwy Do you think this change is necessary?

Personally, I don't really know 😄 But it doesn't hurt to add a scrollbar so I'm going to approve this as see what others think. It's only showing when there's long content so I think it's fine.


Connection issue when backlog quota is exceeded - unable to consume

It seems that there's an edge case that's not handled properly when a backlog quota is exceeded.
The clients aren't able to connect, and I understand that they shouldn't be able to produce, but consumption gets blocked as well, even if the downstream topic has no subscribers (so the messages should be easily consumed, thus resolving the backlog.)

The issue had no activity for 30 days, mark with Stale label.


What's mean the 'executor' in API

I noticed that there is a 'executor' in API of create app. all examples about this parameters is empt string os '//cmd'. How to use this parameter, are there any example to use this? thanks

@mhausenblas We should improve documentation on that.

Good! Keep it coming …


fix broken breaks tracking

this never worked. sorry @chrisnojima nojima and @cjb for the bug :(
add a test, piggy backed on top of SoftSnoozeTest. I asserted by
hand that the test fails before the bug is fixed.
also remove some dead code

@cjb  / @chrisnojima  -- A further note.  The -s flag works without bugs, to the best of my understanding...

LGTM
(also restarted your travis build as the system was shutdown in the middle of the test run)

Cool thanks max
On Tuesday, March 29, 2016, Patrick Crosby<EMAIL_ADDRESS>wrote:

LGTM
(also restarted your travis build as the system was shutdown in the middle
of the test run)
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/keybase/client/pull/2487#issuecomment-203191026

Sorry for the bug and not owning up to it right away!


Two questions about the training data

Thanks for sharing the training scripts! I have two questions about the training data. In the data files, I noticed the use of occlusion files. Do they belong to the sub-dataset called Disparity Occlusion Weights? Also, for training on KITTI, it appears that only RGB images are used without depth supervision. I'm a bit confused about this.

Thank your for your question. The occlusion files are calculated with left right disparity consistency, though as stated， there are some sub folders, but using left right consistency, you can capture all. But anyway, since they are occlusion for stereo, when for monocular depth estimation, we did not use such files, refer to the dataloader and how we read data.
As for kitti, I just want to render some rgbs views, since the gT depth is sparse


Code Access

Hi, when can I see the code?

Hello!
Thank you for your interest and sorry for the delayed push. We've put some effort into cleaning up various stuff in the repository before pushing. It still isn't perfect, but hopefully we'll find the time to improve it.
For now, there's only a small patch for the host kernel missing; we're uploading it soon.
In fact, I'll leave this issue open as a reminder for that.

Thanks a lot!
I'll keep track of this. 👍


opening workspace on wsl has some issue?

Type: Bug
after the latest insiders update i am getting following popup when trying to open a vscode insiders on wsl.
the host 'wsl.localhost' was not found in the list of allowed hosts. Do you want to allow this anyway?

i am unsure if this is a bug or i messed something up.
UPDATE: this happens when i use code-insiders . to open the workspace, if i open it using the recent things work as usual.
in my workflow i use code-insiders . a lot (at least few times a day).
VS Code version: Code - Insiders 1.94.0-insider (a162831c17ad0d675f1f0d5c3f374fd1514f04b5, 2024-09-06T12:53:19.832Z)
OS version: Windows_NT x64 10.0.22621
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz (8 x 2112)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off

Load (avg)
undefined

Memory (System)
15.82GB (6.21GB free)

Process Argv
.

Screen Reader
no

VM
0%

Extensions (27)

Extension
Author (truncated)
Version

ng-template
Ang
18.2.0

vscode-markdownlint
Dav
0.55.0

vscode-eslint
dba
3.0.10

gitlens
eam
15.4.0

EditorConfig
Edi
0.16.4

prettier-vscode
esb
11.0.0

vscode-drawio
hed
1.6.6

output-colorizer
IBM
0.1.2

mongodb-vscode
mon
1.8.1

vscode-scss
mrm
0.10.0

vscode-dotnet-runtime
ms-
2.1.5

data-workspace-vscode
ms-
0.5.0

mssql
ms-
1.24.0

sql-bindings-vscode
ms-
0.4.0

sql-database-projects-vscode
ms-
1.4.3

remote-wsl
ms-
0.88.2

vscode-typescript-next
ms-
5.7.20240904

angular-console
nrw
18.26.0

vscode-xml
red
0.27.2024082510

vscode-yaml
red
1.15.0

sonarlint-vscode
Son
4.10.0

code-spell-checker
str
3.0.1

vscode-stylelint
sty
1.4.0

win-ca
uko
3.5.1

intellicode-api-usage-examples
Vis
0.2.8

vscodeintellicode
Vis
1.3.1

vscodeintellicode-completions
Vis
2.0.0

I also have this issue, starting today, same commit version as reported above.
It appears to me that, instead of opening files inside of my WSL instance, code-insiders is now opening the file under Windows using the full path spec to get to the WSL file from Windows.
One obvious change is that, after opening code-insiders from my WSL command line with code-insiders ., when I then choose "Open File..." from the File menu, a Windows file dialog box opens up with the path to get to that directory from Windows. In earlier versions, a dialog box integrated into VSCode opened with the Linux path specified.
I just upgraded code-insiders while entering this, and it still has the same issue. Here's my current version info:
Version: 1.93.0 (user setup)
Commit: 4849ca9bdf9666755eb463db297b69e5385090e3
Date: 2024-09-04T13:02:38.431Z
Electron: 30.4.0
ElectronBuildId: 10073054
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22631

after installing the update today, i am not facing this issue.
@fc-amiggi can you also confirm this so i can close this issue.

@sanket-bhalerao Confirmed, it's fixed. The issue can be closed.

thank you.
appreciate the quick fix from @vscode

I just updated to dc9412125d4e0a480593962ae2687e74e64af728 and code-insiders . is back to being broken :(

I am not getting this issue, i am currently on
Version: 1.94.0-insider
Commit: 8b7eb51f54d7e1492d9baf70454ab6547a4ff9df
Date: 2024-09-10T05:04:21.546Z
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Code-Insiders/1.94.0-insider Chrome/124.0.6367.243 Electron/30.4.0 Safari/537.36

I also no longer can reproduce with 8b7eb51f54d7e1492d9baf70454ab6547a4ff9df.
Please update to 8b7eb51f54d7e1492d9baf70454ab6547a4ff9df.
Version: 1.94.0-insider (user setup)
Commit: 8b7eb51f54d7e1492d9baf70454ab6547a4ff9df
Date: 2024-09-10T05:04:21.546Z
Electron: 30.4.0
ElectronBuildId: 10073054
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22635

Fixed by https://github.com/microsoft/vscode/pull/228044

@sanket-bhalerao The two dialogs are not the same. But both dialogs started to show due to the same bug: The code-insider . script: It was no longer able to detect that code insiders was invoked out of a WSL terminal and opened a local VS Code Window instead of a WSL Window.

@aeschli , okay.
i am aware this is unrelated to the current issue, but shouldn't this dialog also be a custom instead of a native dialogue then?

No, the first dialog comes from a check that is done before we start the VS Code. We can only show native dialogs there.


convert alt_ids to obsolete terms

For consistency with the OWL representation, and with other OBO ontologies, we would like to create obsolete terms for all alt_id entries. These would have a replaced_by link to the active term. After this, the ontology would contain no alt_id tags.

After this is done, must do:
https://github.com/geneontology/go-ontology/issues/18859


feature/open-ide

Closes  #111
This PR implements the ability to launch your Flutter projects directly into your IDE. Currently supports XCode and VSCode, but new IDEs may be added in the future by adding them to supportedIDEs in settings.utils.dart.

This will be very helpful, any eta for this to come in release?

@gauravmehta13 Should be ready soon, and I think the release will follow soon after as we haven't done a release in forever 😄

@gauravmehta13 Should be ready soon, and I think the release will follow soon after as we haven't done a release in forever 😄

Thanks


Update active-directory-windows-enterprise-state-roaming-troubleshoot…

…ing.md

Hi @tanning, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Ning Tan). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

@tanning : Thanks for your contribution to the Azure documentation! The author, @femila, has been notified to review your proposed change.

#sign-off

#sign-off

Please merge

@femila Please use the instructions in Resolve a merge conflict yourself to resolve the merge conflict. Thanks.

hi @tanning , Can you close this PR? I can open a new one and get that merged.

@Femila Sorry about that. I've closed this one. Thanks for letting me know.


Color elements not displayed, breaking whole PDF file (TypeError: codingStyleParameters is undefined etc.)

Attach (recommended) or Link to PDF file here:

https://fragdenstaat.de/anfrage/energiebedarfsausweis-fur-gebaude-landesbetrieb-information-und-technik-nordrhein-westfalen-mauerstrae-5-140476-dusseldorf/549002/anhang/WE2330Ausweis.pdf
local: WE2330Ausweis_2.pdf

Configuration:

Web browser and its version: Firefox 83
Operating system and its version: Linux/Gnome/Fedora 33
PDF.js version: I have no idea, but reproducible with the current version on your website
Is a browser extension: No???

Steps to reproduce the problem:

Go to this link.
Optionally, download PDF file and open it in Firefox.
Optionally, go to https://mozilla.github.io/pdf.js/web/viewer.html and open it there.

What is the expected behavior?
If I open it in Evince 3.38.0 it actually works and is shown in color:

What went wrong?
Everything:

The following console errors are shown:
In Firefox 83 (stable):

14:36:48.397 Warning: JPX: Trying to recover from: Codestream code 0xFF53 (COC) is not implemented pdf.worker.js:1104:13
14:36:48.398 Warning: Unable to decode image "img_p0_1": "TypeError: codingStyleParameters is undefined". pdf.worker.js:1104:13
14:36:48.400 PDF f2429f9760ebdfea04bae9a312813109 [1.5 RICOH MP C5504 / RICOH MP C5504] (PDF.js: 2.7.99) viewer.js:1351:13
14:36:48.400 Warning: JPX: Trying to recover from: Codestream code 0xFF53 (COC) is not implemented pdf.worker.js:1104:13
14:36:48.400 Warning: Unable to decode image "img_p0_2": "TypeError: codingStyleParameters is undefined". pdf.worker.js:1104:13
14:36:48.523 Warning: Dependent image isn't ready yet 2 pdf.js:1190:13
14:36:48.659 Warning: JPX: Trying to recover from: Codestream code 0xFF53 (COC) is not implemented pdf.worker.js:1104:13
14:36:48.659 Warning: Unable to decode image "img_p1_1": "TypeError: codingStyleParameters is undefined". pdf.worker.js:1104:13
14:36:48.660 Warning: JPX: Trying to recover from: Codestream code 0xFF53 (COC) is not implemented pdf.worker.js:1104:13
14:36:48.661 Warning: Unable to decode image "img_p1_2": "TypeError: codingStyleParameters is undefined". pdf.worker.js:1104:13
14:36:48.773 Warning: Dependent image isn't ready yet 2 pdf.js:1190:13

On https://mozilla.github.io/pdf.js/web/viewer.html:

14:37:20.206 PDF 110dd61fd57444010b1ab5ff38782f0f [1.4 pdfeTeX-1.21a / TeX] (PDF.js: 2.7.395) app.js:1672:4
14:37:28.352 Warning: JPX: Trying to recover from: Codestream code 0xFF53 (COC) is not implemented pdf.worker.js:1067:13
14:37:28.353 Warning: Unable to decode image "img_p0_1": "TypeError: codingStyleParameters is undefined". pdf.worker.js:1067:13
14:37:28.355 Warning: JPX: Trying to recover from: Codestream code 0xFF53 (COC) is not implemented pdf.worker.js:1067:13
14:37:28.355 Warning: Unable to decode image "img_p0_2": "TypeError: codingStyleParameters is undefined". pdf.worker.js:1067:13
14:37:28.359 PDF f2429f9760ebdfea04bae9a312813109 [1.5 RICOH MP C5504 / RICOH MP C5504] (PDF.js: 2.7.395) app.js:1672:4
14:37:28.473 Warning: Dependent image isn't ready yet 2 util.js:358:4
14:37:28.604 Warning: JPX: Trying to recover from: Codestream code 0xFF53 (COC) is not implemented pdf.worker.js:1067:13
14:37:28.604 Warning: Unable to decode image "img_p1_1": "TypeError: codingStyleParameters is undefined". pdf.worker.js:1067:13
14:37:28.608 Warning: JPX: Trying to recover from: Codestream code 0xFF53 (COC) is not implemented pdf.worker.js:1067:13
14:37:28.608 Warning: Unable to decode image "img_p1_2": "TypeError: codingStyleParameters is undefined". pdf.worker.js:1067:13
14:37:28.722 Warning: Dependent image isn't ready yet 2 util.js:358:4
14:37:31.893 Warning: JPX: Trying to recover from: Codestream code 0xFF53 (COC) is not implemented pdf.worker.js:1067:13
14:37:31.894 Warning: Unable to decode image "img_p2_1": "TypeError: codingStyleParameters is undefined". pdf.worker.js:1067:13
14:37:31.895 Warning: JPX: Trying to recover from: Codestream code 0xFF53 (COC) is not implemented pdf.worker.js:1067:13
14:37:31.895 Warning: Unable to decode image "img_p2_2": "TypeError: codingStyleParameters is undefined". pdf.worker.js:1067:13
14:37:32.023 Warning: Dependent image isn't ready yet 2 util.js:358:4

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):
As said, in all version of PDF.js that are used I see an error, this includes:

the platform FragDenStaat, where I saw the FOI request reply PDF the first time. See this link, it uses PDF.js. (downstream issue)
the stable version of Firefox (v83) on Linux
your website, as explained above.

Fixed by the PR above.

Wow, that was fast. Thanks a lot! :smiley: :tada:
Happy weekend and happy holidays!


[SerializedDiagnosticConsumer] Pass StringRef instead of raw data for…

… categories and educational notes
EmitRecordWithBlob accepts a StringRef and that a safer choice to correctly represent the size.

@swift-ci please smoke test


Uncaught InvalidCharacterError: Failed to execute 'add' on 'DOMTokenList': The token provided ('local function') contains HTML space characters, which are not valid in tokens.

If I return a type like local function in a suggestion.
Atom Version: 0.189.0
System: Microsoft Windows 8 Pro
Thrown From: autocomplete-plus package, v2.8.0
Stack Trace
Uncaught InvalidCharacterError: Failed to execute 'add' on 'DOMTokenList': The token provided ('local function') contains HTML space characters, which are not valid in tokens.
At C:\Users\bas\.atom\packages\autocomplete-plus\lib\suggestion-list-element.coffee:156

Error: Failed to execute 'add' on 'DOMTokenList': The token provided ('local function') contains HTML space characters, which are not valid in tokens.
  at Error (native)
  at autocomplete-suggestion-list.SuggestionListElement.renderItem (C:\Users\bas\.atom\packages\autocomplete-plus\lib\suggestion-list-element.coffee:156:26)
  at autocomplete-suggestion-list.SuggestionListElement.renderItems (C:\Users\bas\.atom\packages\autocomplete-plus\lib\suggestion-list-element.coffee:129:6)
  at C:\Users\bas\.atom\packages\autocomplete-plus\lib\suggestion-list-element.coffee:67:35
  at ViewRegistry.module.exports.ViewRegistry.performDocumentUpdate (C:\Users\bas\AppData\Local\atom\app-0.189.0\resources\app\src\view-registry.js:159:9)
  at __bind (C:\Users\bas\AppData\Local\atom\app-0.189.0\resources\app\src\view-registry.js:3:61)

Commands
     -0:26.0 core:move-up (atom-text-editor.editor.is-focused)
  2x -0:25.7 editor:move-to-end-of-word (atom-text-editor.editor.is-focused)
     -0:25.0 editor:select-to-end-of-word (atom-text-editor.editor.is-focused)
     -0:22.5 typescript:format-code (atom-text-editor.editor.is-focused)
     -0:22.2 core:save (atom-text-editor.editor.is-focused)
  2x -0:13.0 core:select-down (atom-text-editor.editor.is-focused)
     -0:12.4 core:backspace (atom-text-editor.editor.is-focused)
  3x -0:11.9 core:move-down (atom-text-editor.editor.is-focused)
     -0:11.2 editor:move-to-end-of-screen-line (atom-text-editor.editor.is-focused)
     -0:10.8 editor:select-to-first-character-of-line (atom-text-editor.editor.is-focused)
     -0:10.2 core:move-up (atom-text-editor.editor.is-focused)
     -0:09.8 editor:move-to-first-character-of-line (atom-text-editor.editor.is-focused)
  2x -0:09.4 core:select-down (atom-text-editor.editor.is-focused)
     -0:09.1 core:select-right (atom-text-editor.editor.is-focused)
  5x -0:06.6 core:backspace (atom-text-editor.editor.is-focused)
     -0:00.6 core:save (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "themes": [
      "atom-dark-ui",
      "monokai"
    ]
  },
  "autocomplete-plus": {}
}

Installed Packages
# User
atom-typescript, v2.4.0
atom-typescript-test, v0.0.0
autocomplete-plus, v2.8.0
last-cursor-position, v0.7.0
linter, v0.12.0
minimap, v4.7.5
minimap-find-and-replace, v4.2.0
minimap-git-diff, v4.1.2
minimap-selection, v4.2.0
monokai, v0.13.0
project-manager, v1.15.5

# Dev
No dev packages

Type should be a single word. Choose local. Or function.

It should probably not break in this. And you should choose function for
type in that case
On Friday, April 3, 2015, Joe Fitzgerald<EMAIL_ADDRESS>wrote:

Type should be a single word. Choose local. Or function.
—
Reply to this email directly or view it on GitHub
https://github.com/atom-community/autocomplete-plus/issues/353#issuecomment-89259520
.

Yes I should and did use function to fix it. However created this issue because other people might run into the same and get the "error box" and wanted to bring it to your notice ❤

The error seems pretty clear about the actions required to resolve the issue. I don't think this needs a fix.

I suppose the alternative would be for autocomplete plus to split on space and use the first word, instead of erroring. We could use the extended description in a popover or similar, or set leftLabel with this if it is empty.

The error seems pretty clear about the actions required to resolve the issue

Yes. :+1: for that.
But again would like this to not error. Don't want to depend on lazy autocomplete package authors like me to ensure a valid type :+1: (I was just passing through what typescript gave to me as a first step :smile: )


add exported configuration files

there are a couple of small changes in the files that I didn't expect and don't understand

You may have more changes in there than you indented to make. For example, I still see mention of attribute title, which I remember was just an experiment. One way to proceed would be to recreate your container from next branch, make just the changes that you want to make (as per the instructions you are writing), and re-export the configuration files.


Fee breakdown copies

Almost forgot, we do also need warning and error messages:

Warning instructing users to select a fee payer.
Error when user selected account with insufficient balance.

Almost forgot, we do also need warning and error messages:

Warning instructing users to select a fee payer.
Error when user selected account with insufficient balance.

I have added these, let me know if its okay:
"transactionReview_customizeNetworkFeeSheet_selectFeePayer_warning": "Please select a fee payer for the transaction fee",
	"transactionReview_customizeNetworkFeeSheet_insufficientBalance_warning": "Insufficient balance to pay the transaction fee",

I actually think we need one more string - In choose fee payer screen, we should also have string of sorts - "Select an account to pay %s XRD transaction fee". It will probably be a subtitle to "Select Fee Payer" title

@raf-rdx I don't think we will get design for that, and thought we have semi-agreed on what we should try to do.

@raf-rdx I don't think we will get design for that, and thought we have semi-agreed on what we should try to do.

@GhenadieVP Ok I just don't recall to have this additional string only the title (Select Fee Payer), so if you prefer to have it, then I can add it.
Additionally on Android I think we will keep list of accounts simple i.e. without balance as we said on demo to keep it simple, so that's why we might not use it. But in case we change mind, then we may make a use of that 👍

@raf-rdx I don't think we will get design for that, and thought we have semi-agreed on what we should try to do.

@GhenadieVP Ok I just don't recall to have this additional string only the title (Select Fee Payer), so if you prefer to have it, then I can add it. Additionally on Android I think we will keep list of accounts simple i.e. without balance as we said on demo to keep it simple, so that's why we might not use it. But in case we change mind, then we may make a use of that 👍

@GhenadieVP Is the naming correct for you? :
"transactionReview_customizeNetworkFeeSheet_selectFeePayer_subtitle": "Select an account to pay %s XRD transaction fee" ?


Add Prayer or Restore plugin.

Plugin adds a side panel which, when clicked on, displays a sorted list of the current wiki price per does of all prayer pots (1-4) and super restores (1-4).
This plugin can help decide if it is worth buying  prayer potions or super restores.

I don't see a reason to add this plugin when the GE search panel exists.

I'm not sure if this is for merching, or not, but there is already flipping plugins that can be used for that.

It is simply to help determine at a quick glance if someone wants to buy prayer potions or super restores. There are times when super restores end up being priced lower than prayer potions, even though super restores restore an additional +1 prayer point. Is simply meant to help quickly inform that decision if a player thinks it worth to spend for the extra prayer point of a super restore.


Syntastic check not checking errors

Hi,
Syntastic check not checking errors. Done Troubleshoot as per https://github.com/vim-syntastic/syntastic#faqinfo. But no success. I'm checking for java and see javac executable present in path. And by the way it's working for c filetype (gcc executable present in path). I think this is some setup issue. But unable to troubleshoot further. Please help
I'm on Windows 10 and following command gives error
:echo syntastic#util#system('echo %PATH%')
syntastic: error: exception running system('echo %PATH%'): Vim(let):E484: Can't open file C:\Users\Parrot\AppData\Local\Temp\VIo9A1C.tmp
Figured out 'echo %path%' not working due to space after echo

Please read :h syntastic-powershell.  Does that address your problem?

Strange. After couple of restarts. It's working. Thanks


docs.microsoft.com documentation is not generated

Documentation is not generated for neither old SDKs (Node.js) nor new SDKs (TypeScript).
Example
Node.js docs for OSProfile:
https://docs.microsoft.com/en-us/javascript/api/azure-arm-compute/osprofile?view=azure-node-latest
Python docs for OSProfile:
https://docs.microsoft.com/en-us/python/api/azure-mgmt-compute/azure.mgmt.compute.v2018_10_01.models.osprofile?view=azure-python

@kpajdzik make sure to file a request for publishing here: https://aka.ms/publish-on-docs, whenever you have the information on the new packages that we need to generate the documentation for.

@dendeli-msft - Is there a tentative date on when the docs for the new JS sdk will be published on docs.microsoft.com?
The landing page should mention JS instead of node.js and the icon should be that of JS as well.

I believe this has been resolved


Allow Drupal to lock tables, allows importing dumps generated by Drus…

…h: https://www.drupal.org/project/drupal/issues/2487089.

:+1: Surprised I haven't bumped into this.  I guess I've always just dumped using mysqldump directly when playing around with it.


Nugget variances

Hi
At the moment, the covariance models do not allow nugget variances. Since it is an often desired feature, I think it should be added. @juliohm : If you agree to it, please check my pull request for an example addition of nugget field in the GaussianCovariance composite type definition. Thanks.

Thank you @masiddique , I merged the PR https://github.com/juliohm/GeoStats.jl/pull/5, I appreciate it.
Feel free to add nugget to the other models too, I will merge them :+1:

I will just reorder the nugget to be the last field instead of the first and stop to think about the total sill vs. partial sill issue.

Fixed on the master branch, thanks again for catching this.


Add info about API intros

Why:
This PR adds two lines about writing intros for API pages since they are a bit different from how we outline intros for other articles.
Slightly related issue: https://github.com/github/docs-content/issues/4445
What's being changed:
Adds two bullet points to the "How to write an intro" section of the content model.
Check off the following:

[x] I have reviewed my changes in staging (look for the deploy-to-heroku link in your pull request, then click View deployment).
[x] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

This PR adds a bit more direction to the writer experience, but I do not think it has writer impact that warrants the writer impact label.

add-API-intro-info