Failed on raspberry pi OS (64bit)

[  0%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/__/third_party/protobuf-lite/arena.cc.o
[  0%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/__/third_party/protobuf-lite/arenastring.cc.o
[  3%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/__/third_party/protobuf-lite/bytestream.cc.o
[  3%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/__/third_party/protobuf-lite/coded_stream.cc.o
[  7%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/__/third_party/protobuf-lite/common.cc.o
[  7%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/__/third_party/protobuf-lite/extension_set.cc.o
[  7%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/__/third_party/protobuf-lite/generated_enum_util.cc.o
[ 11%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/__/third_party/protobuf-lite/generated_message_table_driven_lite.cc.o
[ 11%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/__/third_party/protobuf-lite/generated_message_util.cc.o
[ 11%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/__/third_party/protobuf-lite/implicit_weak_message.cc.o
[ 15%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/__/third_party/protobuf-lite/int128.cc.o
[ 15%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/__/third_party/protobuf-lite/io_win32.cc.o
[ 15%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/__/third_party/protobuf-lite/message_lite.cc.o
[ 19%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/__/third_party/protobuf-lite/parse_context.cc.o
[ 19%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/__/third_party/protobuf-lite/repeated_field.cc.o
[ 19%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/__/third_party/protobuf-lite/status.cc.o
[ 23%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/__/third_party/protobuf-lite/statusor.cc.o
[ 23%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/__/third_party/protobuf-lite/stringpiece.cc.o
[ 23%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/__/third_party/protobuf-lite/stringprintf.cc.o
[ 26%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/__/third_party/protobuf-lite/structurally_valid.cc.o
[ 26%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/__/third_party/protobuf-lite/strutil.cc.o
[ 26%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/__/third_party/protobuf-lite/time.cc.o
[ 30%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/__/third_party/protobuf-lite/wire_format_lite.cc.o
[ 30%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/__/third_party/protobuf-lite/zero_copy_stream.cc.o
[ 30%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/__/third_party/protobuf-lite/zero_copy_stream_impl.cc.o
[ 34%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/__/third_party/protobuf-lite/zero_copy_stream_impl_lite.cc.o
[ 34%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/builtin_pb/sentencepiece.pb.cc.o
[ 34%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/builtin_pb/sentencepiece_model.pb.cc.o
[ 38%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/bpe_model.cc.o
[ 38%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/char_model.cc.o
[ 42%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/error.cc.o
[ 42%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/filesystem.cc.o
[ 42%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/model_factory.cc.o
[ 46%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/model_interface.cc.o
[ 46%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/normalizer.cc.o
[ 46%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/sentencepiece_processor.cc.o
[ 50%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/unigram_model.cc.o
[ 50%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/util.cc.o
[ 50%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/word_model.cc.o
[ 53%] Building CXX object _deps/sentencepiece-build/src/CMakeFiles/sentencepiece.dir/__/third_party/absl/flags/flag.cc.o
[ 53%] Linking CXX shared library libsentencepiece.so
[ 53%] Built target sentencepiece
[ 53%] Building CXX object _deps/highway-build/CMakeFiles/hwy.dir/hwy/aligned_allocator.cc.o
[ 57%] Building CXX object _deps/highway-build/CMakeFiles/hwy.dir/hwy/nanobenchmark.cc.o
[ 57%] Building CXX object _deps/highway-build/CMakeFiles/hwy.dir/hwy/per_target.cc.o
[ 57%] Building CXX object _deps/highway-build/CMakeFiles/hwy.dir/hwy/print.cc.o
[ 61%] Building CXX object _deps/highway-build/CMakeFiles/hwy.dir/hwy/targets.cc.o
[ 61%] Building CXX object _deps/highway-build/CMakeFiles/hwy.dir/hwy/timer.cc.o
[ 61%] Linking CXX static library libhwy.a
[ 61%] Built target hwy
[ 61%] Building CXX object _deps/highway-build/CMakeFiles/hwy_contrib.dir/hwy/contrib/sort/vqsort_128a.cc.o
[ 65%] Building CXX object _deps/highway-build/CMakeFiles/hwy_contrib.dir/hwy/contrib/sort/vqsort_128d.cc.o
[ 65%] Building CXX object _deps/highway-build/CMakeFiles/hwy_contrib.dir/hwy/contrib/sort/vqsort_f16a.cc.o
[ 65%] Building CXX object _deps/highway-build/CMakeFiles/hwy_contrib.dir/hwy/contrib/sort/vqsort_f16d.cc.o
[ 69%] Building CXX object _deps/highway-build/CMakeFiles/hwy_contrib.dir/hwy/contrib/sort/vqsort_f32a.cc.o
[ 69%] Building CXX object _deps/highway-build/CMakeFiles/hwy_contrib.dir/hwy/contrib/sort/vqsort_f32d.cc.o
[ 73%] Building CXX object _deps/highway-build/CMakeFiles/hwy_contrib.dir/hwy/contrib/sort/vqsort_f64a.cc.o
[ 73%] Building CXX object _deps/highway-build/CMakeFiles/hwy_contrib.dir/hwy/contrib/sort/vqsort_f64d.cc.o
[ 73%] Building CXX object _deps/highway-build/CMakeFiles/hwy_contrib.dir/hwy/contrib/sort/vqsort_i16a.cc.o
[ 76%] Building CXX object _deps/highway-build/CMakeFiles/hwy_contrib.dir/hwy/contrib/sort/vqsort_i16d.cc.o
[ 76%] Building CXX object _deps/highway-build/CMakeFiles/hwy_contrib.dir/hwy/contrib/sort/vqsort_i32a.cc.o
[ 76%] Building CXX object _deps/highway-build/CMakeFiles/hwy_contrib.dir/hwy/contrib/sort/vqsort_i32d.cc.o
[ 80%] Building CXX object _deps/highway-build/CMakeFiles/hwy_contrib.dir/hwy/contrib/sort/vqsort_i64a.cc.o
[ 80%] Building CXX object _deps/highway-build/CMakeFiles/hwy_contrib.dir/hwy/contrib/sort/vqsort_i64d.cc.o
[ 80%] Building CXX object _deps/highway-build/CMakeFiles/hwy_contrib.dir/hwy/contrib/sort/vqsort_kv128a.cc.o
[ 84%] Building CXX object _deps/highway-build/CMakeFiles/hwy_contrib.dir/hwy/contrib/sort/vqsort_kv128d.cc.o
[ 84%] Building CXX object _deps/highway-build/CMakeFiles/hwy_contrib.dir/hwy/contrib/sort/vqsort_kv64a.cc.o
[ 84%] Building CXX object _deps/highway-build/CMakeFiles/hwy_contrib.dir/hwy/contrib/sort/vqsort_kv64d.cc.o
[ 88%] Building CXX object _deps/highway-build/CMakeFiles/hwy_contrib.dir/hwy/contrib/sort/vqsort_u16a.cc.o
[ 88%] Building CXX object _deps/highway-build/CMakeFiles/hwy_contrib.dir/hwy/contrib/sort/vqsort_u16d.cc.o
[ 88%] Building CXX object _deps/highway-build/CMakeFiles/hwy_contrib.dir/hwy/contrib/sort/vqsort_u32a.cc.o
[ 92%] Building CXX object _deps/highway-build/CMakeFiles/hwy_contrib.dir/hwy/contrib/sort/vqsort_u32d.cc.o
[ 92%] Building CXX object _deps/highway-build/CMakeFiles/hwy_contrib.dir/hwy/contrib/sort/vqsort_u64a.cc.o
[ 92%] Building CXX object _deps/highway-build/CMakeFiles/hwy_contrib.dir/hwy/contrib/sort/vqsort_u64d.cc.o
[ 96%] Building CXX object _deps/highway-build/CMakeFiles/hwy_contrib.dir/hwy/contrib/image/image.cc.o
[ 96%] Building CXX object _deps/highway-build/CMakeFiles/hwy_contrib.dir/hwy/contrib/sort/vqsort.cc.o
[ 96%] Linking CXX static library libhwy_contrib.a
[ 96%] Built target hwy_contrib
[ 96%] Building CXX object CMakeFiles/gemma.dir/run.cc.o
[100%] Building CXX object CMakeFiles/gemma.dir/gemma.cc.o
In file included from /home/lo/dbot/gemma.cpp/./gemma.cc:27,
                 from /home/lo/dbot/gemma.cpp/build/_deps/highway-src/hwy/foreach_target.h:174,
                 from /home/lo/dbot/gemma.cpp/gemma.cc:22:
/home/lo/dbot/gemma.cpp/./ops.h: In function ‘float gcpp::N_SVE::SquaredL2(const float*, size_t)’:
/home/lo/dbot/gemma.cpp/./ops.h:352:12: error: ‘MulAdd’ was not declared in this scope
  352 |     sum0 = MulAdd(a0, a0, sum0);
/home/lo/dbot/gemma.cpp/./ops.h:352:12: note: suggested alternatives:
In file included from /home/lo/dbot/gemma.cpp/build/_deps/highway-src/hwy/highway.h:432,
                 from /home/lo/dbot/gemma.cpp/./compression/sfp-inl.h:37,
                 from /home/lo/dbot/gemma.cpp/./compression/nuq-inl.h:41,
                 from /home/lo/dbot/gemma.cpp/./compression/compress-inl.h:48,
                 from /home/lo/dbot/gemma.cpp/./gemma.cc:25,
                 from /home/lo/dbot/gemma.cpp/build/_deps/highway-src/hwy/foreach_target.h:163:
/home/lo/dbot/gemma.cpp/build/_deps/highway-src/hwy/ops/arm_neon-inl.h:2492:22: note:   ‘hwy::N_NEON::MulAdd’
 2492 | HWY_API Vec128<T, N> MulAdd(Vec128<T, N> mul, Vec128<T, N> x,
      |                      ^~~~~~
In file included from /home/lo/dbot/gemma.cpp/build/_deps/highway-src/hwy/highway.h:435,
                 from /home/lo/dbot/gemma.cpp/./compression/sfp-inl.h:37,
                 from /home/lo/dbot/gemma.cpp/./compression/nuq-inl.h:41,
                 from /home/lo/dbot/gemma.cpp/./compression/compress-inl.h:48,
                 from /home/lo/dbot/gemma.cpp/./gemma.cc:25:
……
gmake[3]: *** [CMakeFiles/gemma.dir/build.make:90: CMakeFiles/gemma.dir/gemma.cc.o] Error 1
gmake[2]: *** [CMakeFiles/Makefile2:377: CMakeFiles/gemma.dir/all] Error 2
gmake[1]: *** [CMakeFiles/Makefile2:384: CMakeFiles/gemma.dir/rule] Error 2
gmake: *** [Makefile:189: gemma] Error 2

Many error reports point to the same problem:
error: ‘MulAdd’ was not declared in this scope
or
error: ‘Add’ was not declared in this scope
I checked highway's code and MulAdd seems to exist, so I'm not sure why the error "not declared" is reported.
Help me pls.

Thanks for reporting. This is an error in our code, we are missing the hn:: prefix, sorry about that. I'm fixing most of them, to avoid a merge conflict I'd recommend patching in #105, or waiting until that lands (soon).

Thanks for reporting. This is an error in our code, we are missing the hn:: prefix, sorry about that. I'm fixing most of them, to avoid a merge conflict I'd recommend patching in #105, or waiting until that lands (soon).

Sorry I made mistakes,
should I add it in #105 ? I am asking because I have seen a fix p.r.
@jan-wassenberg do you mind if I add gh action to check build on different arch
(run-on-arch-action)

should I add it in https://github.com/google/gemma.cpp/pull/105 ? I am asking because I have seen a fix p.r.

No worries! You mean #113? I was intending not to conflict with the changes in your #105, so yes, please update #105 with hn:: in the new code :)

@jan-wassenberg do you mind if I add gh action to check build on different arch

Great idea, please do! We can do something similar to github.com/google/highway, let's keep in mind that there is a deadline of about 6-7 minutes after which our internal CI times out, so hopefully the runs will finish before that.

I think this is now fixed. Please reopen if you are still seeing an issue.


Bring back the "add new row" from MZmine2

Is your feature request related to a problem? Please describe.
I wish to manually define several peaks (the range of m/z and retention time of a peak) applied  to all  the raw data  files in
the peak list.
Describe the solution you'd like
Bring back the "add new row" from MZmine2 so that we can manually define a peak.
Describe alternatives you've considered
I am using the command "define manually" in mzmine 3.7.0. However, I need to repeat the process for every file. This is time consuming and error prone when there are a lot of files.
Thank you for your time!

Manual steps are currently relatively late on our todo list, considering there are too many new features that we would like to implement. We are happy to assist anyone who would like to take on this issue though


Remove fomantic message module

Remove this CSS-only module, which gives a nice reduction in CSS size. Should look exactly like before.

Sorry I merged this too fast.
I didn't see related changes in semantic.json. So next make fomantic would still generate these "message" classes?

Ah, i reverted the setting once, yes I will follow up.


⚠ Bofrost.de has degraded performance

In 482be7b, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 871 ms

Resolved: Bofrost.de performance has improved in c2e771d after 37 minutes.


Sentry no longer shows variables in stack trace after switching from SDK raven-php 0.14.0.dev0 to SDK sentry-php 1.2.0

Hi @dcramer, rather than continuing in Zendesk, I thought I'd fire up a public ticket here instead.
We just switched from SDK raven-php 0.14.0.dev0 to SDK sentry-php 1.2.0 and stopped seeing variables. What could be going wrong, why may they not be showing?
Here's an example of the full entry in Sentry: http://i.imgur.com/hj7yo8w.png.
For instance, it should be trivial to debug what $target mkdir is trying to create, but the variables are just not showing.
We're on PHP Version 5.6.25 btw.

@archon810 thanks! Definitely easier for us to track here. I haven't yet had a chance to look into what could be causing it -- we have test cases that show reflection working, so it's possible this is another change (e.g. misshaped data that got discarded).

So one of the interesting bits of this example is its a single frame. I'm not entirely sure how that can possibly be true here unless it's all inline code (and I dont think thats the case). That said, I have a local case, and while its not the same, I do see missing arguments from mkdir.

@archon810 so from what I can tell we aren't able to actually get scoped context for mkdir. I'm still digging into it, but I have a feeling this never worked for that specific kind of call.

Digging through this I think we should eliminate some of the complexity of this code. We try to shift context around so the vars appear in the frame that is calling them (we effectively shift all vars up one).
I did confirm that the mkdir call doesn't give us context:
array(4) {
  ["type"]=>
  int(2)
  ["message"]=>
  string(34) "mkdir(): No such file or directory"
  ["file"]=>
  string(74) "/Users/dcramer/Development/sentry-php/test/Raven/Tests/IntegrationTest.php"
  ["line"]=>
  int(52)
}

@archon810 so I can't find any actual regression. Do you have an example of an error that used to have context and doesnt now? If you have a sentry.io link you can email it to me (david@).

@dcramer , I'm noticing a possible pattern when I was trying to find errors with context for you. Could this be related to the suppressed errors bug? It seems the errors/notices without context actually had an @ in front. I can actually confirm that I'm seeing all variables in 1.2.0 in PHP exceptions that do not have the suppressor.
So to us, this felt like a 0.14.0.dev0 to 1.2.0 bug, but in reality it's due to the @. The @ bug resulted in us seeing many new exceptions, all without context.
I think this is solved actually.

@SeBsZ ah thats very possible given that it was happening later in the process (maybe error_get_last never has context?)
I will go ahead and close this, but if you find any more details let me know.

Since the @ bug isn't resolved for us with 1.3.0 yet, from what I can tell, I'll wait for it to be resolved first to look at this again.


Install using pip install .

Turns out we are having issues installing due to a change in ipython installation. We seem to be able to workaround this by switching from the python setup.py install to pip install ..

CI appears to be working now. Of course the coverage went down as we are no longer measuring the coverage of the setup script.

This is no longer necessary. So closing.


Abort file upload inside a Directive

Hi,
Not sure if its a bug or not -
I have a directive which I use in a wizard for uploading files with the following code:
var upload = Upload.upload({
                url: fileObj.aws_url,
                data: fileData,
                method: 'POST'
            });

            upload.then(function (resp) {  // success
                   fileObj.upload_time = new Date();
                    initFileObj('success');

            }, function (resp) { // error
                initFileObj('init');
                alertsModalService.error(resp.status);
                logger.error('Error status: ' + resp.status + ' ' + resp.data);
            }, function (evt) { // uploading....
                   progressbar.value = parseInt(100.0 * evt.loaded / evt.total);
            });

everything works ok, but if I leave the page and go back, the directive is initiated  and I am not able to cancel the upload process in case it was already started.
I tried passing the upload variable to the parent controller using 2-way binding. although I get the full object inside the initiated directive properly, using abort() throws me to the error response from the promise.
Thanks.

Could you create a jsfiddle?

http://jsfiddle.net/s8kc7wg0/909/

There is no call to the abort in this example. How do you call abort?

sorry, wrong plnkr.
http://jsfiddle.net/s8kc7wg0/910/

it does cancel the upload.

but returns error.
which I use to catch real netwotk / upload errors.
I there a way to distinguish?
בתאריך 15 בספט׳ 2016 3:00 אחה״צ, "Danial Farid"<EMAIL_ADDRESS>כתב:

it does cancel the upload.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/danialfarid/ng-file-upload/issues/1705#issuecomment-247308808,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKc-1TqKK8Icl6oFVW9jDes6ARIxJFPzks5qqTNHgaJpZM4J8uyP
.

You can check for the status code or set a flag before you call abort to know that the error is from abort.


remove link to dead project

the old repo has not updates since two years. It looks dead.

Related issue there: https://github.com/instrumenta/kubernetes-json-schema/issues/32#issuecomment-1021133568


not working buggyyyyyy

Closing this issue as I have updated the entire script. File a new issue if you face any problems running it


hubot rocket.chat adapter cannot be restarted without re-configuration

Every time when i started hubot, i have to do the following first before bin/hubot -a rocketchat? Why is that?
export ROCKETCHAT_USER=bot
export ROCKETCHAT_PASSWORD=bot
export ROCKETCHAT_AUTH=password

Also I did install redis and hubot-redis-brain, and from the following info i got when i log in hubot, the adapter did connect to redis:
[Wed Oct 19 2016 02:44:24 GMT+0000 (UTC)] INFO hubot-redis-brain: Using default redis on localhost:6379
[Wed Oct 19 2016 02:44:24 GMT+0000 (UTC)] INFO hubot-redis-brain: Data for hubot brain retrieved from Redis

Please see answer already given here: https://github.com/RocketChat/hubot-rocketchat/issues/182#issuecomment-254556722


[gemini] a new tensor structure

Init a new data structure for tensor.
related to #557

What is the purpose of state op?

hijack the original OP. You do not need to modify Linear as col.nn.Linear

hijack the original OP. You do not need to modify Linear as col.nn.Linear

Cool.


[common] handle volume configmaps/secrets

Details
Helm chart name:
common

Describe the solution you'd like:
I need something like
volumeFromConfigMap:
  nameSuffix: config
  data: |
    whatever

Or a way to be able to compute release names in additionalVolumes. In transmission this is only a minor nuisance, but stuff like mosquitto 2.x or icantbelieveitsnotvaletudo can't move to common, because they can't work without a config file.

Anything else you would like to add:
In my charts i try to make the config present itself as yaml and then try to process it into the target format ( with toJson for example ). It would be great if I could keeo doing that, but have absolutely no idea how to make that happen :(

Additional Information:

Hi, thanks for raising this issue.
Currently what you wish to accomplish is already possible through the features of the common library. For example, the Zigbee2MQTT chart already does something like this.
Could you let us know if this approach would work for you?

Yes! This is exactly what I was looking for :) You can close this

Cool! Great that that would work :) I'll leave the issue open for now as a reminder for me to add some documentation about this to the wiki.

I've added this example to the wiki: https://github.com/k8s-at-home/charts/wiki/Common-library:-Creating-a-new-chart


Remove manifest overwrites

The manifest overwrites are conflicting with the latest androidx test libraries:
androidx.test:core-ktx:1.4.1-alpha07
Building with both androidx.test as well as the image cropper fails compilation with the error:
.../build/intermediates/tmp/manifest/androidTest/debug/tempFile1ProcessTestManifest12009438010904517303.xml:30:13-56 Error:
	Attribute activity#androidx.test.core.app.InstrumentationActivityInvoker$BootstrapActivity@theme value=(@style/WhiteBackgroundTheme) from [androidx.test:core:1.4.1-alpha07] AndroidManifest.xml:30:13-56
	is also present at [com.github.CanHub:Android-Image-Cropper:4.0.0] AndroidManifest.xml:41:13-49 value=(@android:style/Theme).
	Suggestion: add 'tools:replace="android:theme"' to <activity> element at tempFile1ProcessTestManifest12009438010904517303.xml:27:9-34:20 to override.

Isn't it possible to just update this library to target 12 and get rid of the entire build.gradle hacky whacky scripting?

Yes thats what I would have suggested as well

Feel free to drop a PR with the fix 👍


Feature/vbox example

Adds an example that can easily build a kraken/VirtualBox cluster.

Nice! I’ll look at this next week.

Yeah!  I was pretty excited to finally get this done.  We'll probably add the web dashboard next week.


Add SpscLinkedQueue

Motivation:
See #3746.
Modifications:
For SPSC, we have no need for XCHG, an ordered store (lazyset) is enough. This patch just added SpscLinkedQueue as a subclass of MpscLinkedQueue and override the XCHG codes to a lazyset.
Result:
Add SpscLinkedQueue and apply it in LocalChannel.

@windie thanks a lot! Can you also add a benchmark to micro benchmark comparing the SpscQueue and MpscQueue when used by a single producer and single consumer ? This should go into the microbenchmark module

@normanmaurer I added 3 benchmarks: SPSC, MPSC and Java LinkedList. Ideally, the result of Java LinkedList is the best we can do. The result of MPSC is the baseline, and SPSC must be better than it. Here is the result running in my laptop:
Benchmark                                Mode  Cnt     Score     Error  Units
SpscLinkedQueueBenchmark.offer          thrpt   10  4692.646 ±  93.210  ops/s
SpscLinkedQueueBenchmark.offerBaseline  thrpt   10  4487.135 ±  75.156  ops/s
SpscLinkedQueueBenchmark.offerIdeal     thrpt   10  5319.869 ± 249.280  ops/s

Benchmark                                Mode  Cnt     Score     Error  Units
SpscLinkedQueueBenchmark.offer          thrpt   10  4499.430 ± 281.367  ops/s
SpscLinkedQueueBenchmark.offerBaseline  thrpt   10  4576.356 ±  80.708  ops/s
SpscLinkedQueueBenchmark.offerIdeal     thrpt   10  5382.993 ± 440.369  ops/s

Benchmark                                Mode  Cnt     Score     Error  Units
SpscLinkedQueueBenchmark.offer          thrpt   10  4780.066 ± 115.477  ops/s
SpscLinkedQueueBenchmark.offerBaseline  thrpt   10  4589.913 ±  85.083  ops/s
SpscLinkedQueueBenchmark.offerIdeal     thrpt   10  5345.122 ± 454.216  ops/s

@windie I'm missing something or you only listed the Spsc benchmarks ? I would love to see the difference between Spsc and Misc.

Since MpscLinkedQueue was made non-final consider making the methods in MpscLinkedQueue final that don't need to be overridden.

@windie - Also on the benchmark, can we simulate the consumer/producer being on different threads (for MpSc and SpSc)? I think this would be the most interesting comparison.

@windie - Looks good! Just a few comments/questions.

@windie I'm missing something or you only listed the Spsc benchmarks ? I would love to see the difference between Spsc and Misc.

Misc? Do you mean Mpsc? If so, SpscLinkedQueueBenchmark.offerBaseline is the result of Mpsc.

@windie - Also on the benchmark, can we simulate the consumer/producer being on different threads (for MpSc and SpSc)? I think this would be the most interesting comparison.

I was thinking writing that. However, I realized that the difference between MPSC and SPSC is just offer and the speed of poll will be same. Therefore I just wrote the benchmark for offer.

@windie - Checkout the JCTools Benchmark. I would be interested to see if a more "practical use case" (adding and removing) from the queue demonstrates value.

I just forked SpscLinkedQueue and SpscLinkedAtomicQueue from JCTools.
There are two commints in this PR now: the first one is just copying the related files from JCTools; the seconds changes the package name and fixes some style errors. I split it into 2 commits so that you can just review the second one.

@windie - 1 small comment and lgtm

@Scottmitch updated

@windie looks good! Please squash commits and update commit message to match our template :)

@normanmaurer - squashed and rebased

Cherry-picked into 4.0 (1b231cbfe884884b79d33ebe7cb1ab76ea51c9f3) and 4.1 (c7aadb5469601074526155d7330bcf355b27fcb7)


Add AutoSelect to SelectionModel

What does the pull request do?
Adds AutoSelect flag to SelectionModel which will implement the SelectionMode.AlwaysSelected behavior.
Part of #3469
Checklist

[x] Added unit tests (if possible)?

Targets #3498

https://github.com/AvaloniaUI/Avalonia/pull/3583


log destination CLI option - use enum

Use enum for the allowable values and add them to the help output

now, when you specify an invalid value:
Invalid value for option '--log-destination': expected one of [BOTH, CONSOLE, DEFAULT_BOTH, FILE] (case-insensitive) but was 'booth'

usage:
      --log-destination=<LOG_DESTINATION>
                             Whether a logger is added for the console, the log
                               file, or both (Valid values: BOTH, CONSOLE,
                               DEFAULT_BOTH, FILE)
                               Default: BOTH

One option is to simply ignore the --log-destination regardless of it's value if a custom log4j config is detected.  That may well be less confusing than having a weird mix of your custom log4j and Teku programatically changing stuff on you.


avoid double Us

the letter code U stands for Utc not Unkown
Issue #, if available:
Description of changes:

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

We appreciate your interest in Ion 1.1 and your willingness to contribute. The choice of the word "unknown" is not by accident. An offset of "none" could imply that the offset is actually zero, which is not what "unknown offset" refers to. The Ion 1.0 specification says of timestamps:

Ion follows the “Unknown Local Offset Convention” of RFC3339:

If the time in UTC is known, but the offset to local time is unknown, this can be represented with an offset of “-00:00”. This differs semantically from an offset of “Z” or “+00:00”, which imply that UTC is the preferred reference point for the specified time. RFC2822 describes a similar convention for email.

Given that Ion follows the convention of RCF 3339, which uses "Unknown" to describe the offset, Ion will continue using "Unknown".


Add pgbouncer process metrics

Add an option to pass a pgboucner PID file into the exporter to collect
process metrics.
Closes: https://github.com/prometheus-community/pgbouncer_exporter/issues/26
Signed-off-by: Ben Kochie<EMAIL_ADDRESS>

:+1:


Run mix format

merge #216 first
manually excluded some changes, probably better refactor the code instead of formatting it poorly.

I'd probably

I'd probably format all the code even if it yields poor formatting, we can update it afterwards.
👍

Will do a second pass on the rest of the files at some point 👍


New M1 - Unable to find bundled Java version

I just bought a new M1 and am struggling to get my environment set back up. I’m down to this last error and have tried everything and can’t seem to clear it. I’ve been through SDK Manager and uninstalled and reinstalled JDK, JRE you name it. Java errors are clear from terminal but flutter will not clear this error. Anyone have any ideas on how I can fix this?

Omg, I solved my own issue. Finally, noticed in posting this screenshot that Android Studio was showing twice (once with a version). This was an error caused by Android Studio Preview. Once I deleted that app version the error went away. Funny, because I had checked the setting in both and they were both set up identical. Oh, well. Leaving this up for anyone else who has snow blindness and can't see the app is duplicated in the Flutter Doctor results.


No Pullup Resistor for the Probe

First of all I have to say that you have a very nice board here.
I noticed that you do not have a pullup resistor for the probe input but you have pullup resistors for the X,Y,Z and A limit pins.
Why you didn't add a pullup resistor for the probe too ?
Cheers

The probe is on a pin that has an optional internal, to the ESP32, pullup resistor. The ESP32 has that feature on most pins, but not the XYZ pins.
In hindsight, I probably should have put external pullups on all inputs. The Internal pullups are rather weak (40k-60k ish). I lower value of 5k-10k would help against noise.


Shell completions (for zsh) fail for kubectx if its binary is renamed to kx

If I mv kubectx kctx (or ln -s kubectx kctx) - then shell completions work fine for kctx {TAB}.
But if I mv kubectx kx (or ln -s kubectx kx) - then shell completions fail for kx {TAB}.
The name by which I address the very same binary shouldn't affect this functionality.
kubectx v0.9.5

I added  kx=kubectx to this line and removed ~/.zcompdump (for it to get regenerated) and that way kx completion started to work.


Ctrl owns too much of the application

@wryun and I had a chat and we figured that Ctrl "owns" too much. Right now, if we want to spin up any additional components alongside the controller, and they require flags, we always need to do one of:

Pulling the Logger out, pull the flags out of the constructor after the App has been NewFromFlags' and having the init code alongside the App, which feels a bit wrong.
Have all the init live inside the ControllerConstructor (which feels like the "owner" is wrong")

Maybe it would be better to have the ownership of flags and loggers be separate to Ctrl. That way, users can decide how the application is started up.
The current method is nice however, since we basically don't need to worry about writing any sort of init code, but it means things are a bit opaque unless you understand what Ctrl is doing.

Although given stuff like https://github.com/atlassian/ctrl/pull/4/files, maybe this is totally fine

Yeah, I see what you mean. I think we should get that PR merged and then think about restructuring the project to make it more like a library rather than like a framework. And maybe there is room for both approaches.


chore(package.json): update ip package

yarn start was erroring out in the ip package, as shown below.  If this is a broader issue that others are experiencing, forcing yarn to use a newer ip package via the resolutions config seems to solve the issue.
❯ yarn && yarn start
yarn install v1.22.17
[1/4] 🔍  Resolving packages...
success Already up-to-date.
$ husky install
husky - Git hooks installed
✨  Done in 0.62s.
yarn run v1.22.17
$ start-storybook -p 6006
info @storybook/react v6.4.22
info
info => Loading presets
Warning: React.createFactory() is deprecated and will be removed in a future major release. Consider using JSX or use React.createElement() directly instead.
ERR! TypeError: details.family.toLowerCase is not a function
ERR!     at /Users/jfu/sci-components/node_modules/ip/lib/ip.js:385:39
ERR!     at Array.filter (<anonymous>)

Summary
Structural Element (Base, Gene, DNA, Chromosome or Cell)
Shortcut ticket: sh-XXXX
Copy ticket descirption here
Checklist

[x] Default Story in Storybook
[x] LivePreview Story in Storybook
[x] Test Story in Storybook
[ ] Tests written
[ ] Variables from defaultTheme.ts used wherever possible
[ ] If updating an existing component, depreciate flag has been used where necessary
[ ] Chromatic build verified by @chanzuckerberg/sds-design

Thanks so much for the PR, @jfoo1984 🤩 🙏
Do we know which library depends on ip? Assuming our library doesn't have a direct dependency on it. And if so, can we check if it's possible to upgrade that library, so we update both the direct dependency and the indirect dependency (ip)?
Also can other people reproduce this? Given that we all have the same yarn.lock from the repo, I wonder if everyone is getting the same error or is it limited to certain machines like the ones using M1 or something?
Thank you!

@tihuan this is what I see using the ip package
❯ npm ls ip
<EMAIL_ADDRESS>/Users/jfu/sci-components
├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   └─┬<EMAIL_ADDRESS>│     └──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   └─┬<EMAIL_ADDRESS>│     └─┬<EMAIL_ADDRESS>│       └─┬<EMAIL_ADDRESS>│         └─┬<EMAIL_ADDRESS>│           └──<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>extraneous
  └──<EMAIL_ADDRESS>
I agree it would definitely be good to hear if anyone else is running into this as well.  In case it's relevant, I'm running node version 18.2.0.  Could that possible be an issue?

node version That could be the problem, I'm on node 18.2.0.  Is node v14.17.4 the recommended version for running the project?

I switched to node 16.15.1, which I believe is the current stable LTS version, and that seems to work.
Would it be worth adding a .node-version file to indicate the node version?  That's the file that the node version manager nodenv uses to autoswitch the node version, but we could add other files as well if other version managers use a different file.

I'm in favor of the .node-version file. thanks for the suggestion!


runtime: apparent deadlocks on Windows builders

Starting in November, there appears to be a dramatic uptick in the number of test timeouts on the windows-* builders.
Many of these are for tests that normally run nearly instantaneously, such as archive/tar and bufio.
2019-11-22T03:06:22-0e02cfb/windows-amd64-race
2019-11-21T22:20:17-94e9a5e/windows-amd64-race
2019-11-21T19:27:16-f4a8bf1/windows-amd64-longtest
2019-11-21T19:09:24-2434869/windows-amd64-longtest
2019-11-21T19:09:24-2434869/windows-amd64-race
2019-11-21T16:56:47-37715cc/windows-amd64-longtest
2019-11-21T16:56:47-37715cc/windows-amd64-race
2019-11-21T16:01:14-c7e73ef/windows-amd64-race
2019-11-20T20:51:13-9852b4b/windows-amd64-race
2019-11-13T19:15:27-7ad2748/windows-amd64-longtest
2019-11-12T22:09:05-a56d755/windows-amd64-2016
2019-11-12T01:07:15-ec73263/windows-amd64-2012
2019-11-08T17:01:05-a5a6f61/windows-amd64-2012
2019-11-07T19:18:12-1b0b980/windows-amd64-2012
2019-11-07T05:52:34-3eabdd2/windows-amd64-longtest
2019-11-06T09:09:59-0c5d545/windows-amd64-2008
2019-11-06T02:52:51-f71bd51/windows-amd64-2016
2019-11-05T16:31:48-414c1d4/windows-amd64-2016
2019-11-05T14:44:56-e457cc3/windows-amd64-race
2019-11-05T05:19:08-d51f7f3/windows-amd64-longtest
2019-11-05T03:50:54-979d65d/windows-amd64-2016
2019-11-05T00:19:10-6cbd737/windows-amd64-race
2019-11-01T14:48:28-a570fcf/windows-amd64-2012
2019-03-19T08:30:50-451a2eb/windows-amd64-2008
2018-12-05T21:54:54-6454a09/windows-amd64-race
CC @ianlancetaylor @aclements @alexbrainman @zx2c4

I suspect that the same root cause is responsible for apparent deadlocks in the os/exec test.
2019-11-22T04:26:34-95be9b7/windows-amd64-2008
2019-11-21T22:20:17-94e9a5e/windows-amd64-2012

2019-11-22T14:32:02-ea18a1c/windows-amd64-race
2019-11-22T15:32:23-c02f3b8/windows-amd64-longtest
2019-11-22T15:32:23-c02f3b8/windows-amd64-race
2019-11-22T19:01:42-c931f1b/windows-amd64-longtest
2019-11-22T19:01:42-c931f1b/windows-amd64-race
2019-11-22T19:03:26-28314cf/windows-amd64-race
2019-11-22T19:03:50-941ac9c/windows-amd64-race
2019-11-22T19:17:28-8324aca/windows-amd64-race
2019-11-22T21:09:43-9f3c2b6/windows-amd64-race
2019-11-22T22:24:38-980f0c0/windows-amd64-race
2019-11-22T23:23:13-6ba1bf3/windows-amd64-race
2019-11-23T00:06:41-f29e53d/windows-amd64-race
2019-11-23T11:00:41-6f7b96f/windows-amd64-longtest
2019-11-23T11:00:41-6f7b96f/windows-amd64-race
2019-11-24T15:06:38-b81dd1c/windows-amd64-longtest
2019-11-24T15:06:38-b81dd1c/windows-amd64-race
2019-11-25T15:08:18-01f15b6/windows-amd64-race
2019-11-25T16:26:15-476395c/windows-amd64-race
2019-11-25T16:43:27-e16f64c/windows-amd64-2016
2019-11-25T16:43:27-e16f64c/windows-amd64-race
2019-11-25T19:02:50-7adafc9/windows-amd64-2016
2019-11-25T21:15:11-5de3b97/windows-amd64-race
2019-11-25T23:37:03-87805c9/windows-amd64-race
2019-11-26T16:55:36-67f0f83/windows-amd64-race
2019-11-26T20:21:04-4a378d7/windows-amd64-2008
2019-11-27T01:29:00-c3f1492/windows-amd64-race
2019-11-27T01:30:19-b2482e4/windows-amd64-2008
2019-11-27T01:30:32-0f25102/windows-amd64-2008
2019-11-27T15:06:55-4e3d580/windows-amd64-race
2019-11-27T18:42:33-f1c8e2c/windows-amd64-race
2019-12-02T16:11:24-3edd1d8/windows-amd64-race
2019-12-02T16:45:37-bf3ee57/windows-amd64-race
2019-12-02T19:05:01-e4c01f0/windows-amd64-race
2019-12-02T20:12:54-a18608a/windows-amd64-2012
2019-12-02T20:12:54-a18608a/windows-amd64-longtest

These failures are all either on the race builder or for tests with the race detector enabled.  Seems like something makes deadlocks possible with the race detector.
The findflakes programs reports that this might be due to https://golang.org/issue/204340 "runtime: support preemption on windows/{386,amd64}".
CC @aclements @cherrymui

Seems like something makes deadlocks possible with the race detector.

That could be related to #18717 — does the runtime assume that its preemption signals are eventually delivered?

does the runtime assume that its preemption signals are eventually delivered?

It does not. It will always try both a cooperative and a non-cooperative preemption and take whichever one it can get. If the signal goes missing, it will wait for a cooperative preemption just like before.

I keep seeing these as trybot flakes too:
https://storage.googleapis.com/go-build-log/dd36d1f3/windows-amd64-2016_767dbeaf.log
It'd be nice to see stacks, though. Maybe we could work on that first and it might yield a clue.

I've had a tough time trying to reproduce this in a gomote to get a stack trace, but I was able to reproduce at least once (unfortunately, I didn't get a stack trace that time...). If it's not too hard, it might be easier to reproduce in CI and the trybots @bradfitz, though I'm not sure how best to do that.
In particular, I've been targeting the "Testing race detector" tests that tend to be the source of failure as @ianlancetaylor mentioned and haven't been able to reproduce this failure on a gomote.
Meanwhile, I'll keep trying.

Alrighty thanks to @aclements and a Windows laptop we have a reproducer, a theory, and a partial fix.
The problem is a race between SuspendThread and ExitProcess on Windows. The order of events is as follows:
Thread 1: Suspend (asynchronously) Thread 2.
Thread 2: Call ExitProcess, which terminates all threads except Thread 2.
Thread 2: In ExitProcess, receives asynchronous notification to suspend, and stops.
This race is already handled in the runtime for the usual exits by putting a lock around suspending a thread (and effectively disallowing it in certain cases, like exit), but in race mode __tsan_fini (called by racefini) calls ExitProcess instead. The fix is to just grab this lock before calling into __tsan_fini.
Unfortunately this raises a bigger issue: what if C code, called from Go, calls ExitProcess on Windows? We have no way to synchronize asynchronous preemption with that like we do with exits we can actually control. One thought is that ExitProcess already calls a bunch of DLL hooks; could we throw in our own to side-step this issue maybe? More thought on this problem is required.

Put a lock on each M? Lock the lock when the M is entering cgo call, and before SuspendThread on that M. So we won't suspend a thread running C code. This is fine as we won't preempt C code anyway.
In fact, if we want to SuspendThread on an M for which the lock is locked, meaning that it is running C code, we don't need to suspend it anyway, so we don't need to wait on the lock. If the M is about to enter C, and the lock is locked, meaning that there is a pending suspend, it can just preempt itself.

@cherrymui that solution makes sense, and would solve other issues such as sending signals to threads running C code resulting in surprising behavior like in #36281 (IIUC) if we used it on all platforms, not just Windows.

Unfortunately this raises a bigger issue: what if C code, called from Go, calls ExitProcess on Windows?

I took a stab at fixing this using @cherrymui's suggestion (varied slightly after chatting in person so there's no actual blocking behavior, just a one-shot CAS). Unfortunately, in Windows, any "system call" can potentially call ExitProcess, so we need to defend against this in reentersyscall, not just cgo calls. That's an extra atomic CAS on every system call.

I also have make.bat reliably hanging on a Windows 7 computer here. I run make.bat (I use GOARCH=amd64) on top of
commit f376b8510ed7884c69a09fbcf61418f7285f2787 (origin/master, origin/HEAD, mas
Author: Emmanuel T Odeke<EMAIL_ADDRESS>Date:   Thu Jan 2 02:00:55 2020 -0800

    all: fix invalid invocations of Fatalf in goroutines

    Found by running the go vet pass 'testinggoroutine' that
    I started in CL 212920.

    Change-Id: Ic9462fac85dbafc437fe4a323b886755a67a1efa
    Reviewed-on: https://go-review.googlesource.com/c/go/+/213097
    Run-TryBot: Emmanuel Odeke<EMAIL_ADDRESS>    TryBot-Result: Gobot Gobot<EMAIL_ADDRESS>    Reviewed-by: Ian Lance Taylor<EMAIL_ADDRESS>
and this is how far it gets

As you can see, there is stuck go_bootstrap.exe there. I used Delve to see what the process does, and this is what I see:
(dlv) threads
  Thread 2004 at :0
  Thread 3912 at :0
  Thread 4064 at :0
  Thread 4368 at :0
  Thread 4580 at :0
  Thread 4852 at :0
  Thread 7620 at :0
  Thread 7680 at :0
  Thread 8592 at :0
* Thread 8712 at :0
  Thread 8852 at :0
  Thread 11816 at :0
  Thread 13452 at :0
  Thread 13632 at :0
  Thread 13692 at :0
  Thread 13792 at :0
  Thread 13956 at :0
  Thread 14180 at :0
  Thread 14192 at 0x5b6351 c:/Users/alexb/dev/go/src/crypto/sha256/sha256block_a
md64.s:805 crypto/sha256.block
(dlv) goroutines -t
  Goroutine 1 - User: c:/Users/alexb/dev/go/src/runtime/sema.go:56 sync.runtime_
Semacquire (0x447179)
         0  0x00000000004385e5 in runtime.gopark
             at c:/Users/alexb/dev/go/src/runtime/proc.go:305
         1  0x000000000044754e in runtime.goparkunlock
             at c:/Users/alexb/dev/go/src/runtime/proc.go:310
         2  0x000000000044754e in runtime.semacquire1
             at c:/Users/alexb/dev/go/src/runtime/sema.go:144
         3  0x0000000000447179 in sync.runtime_Semacquire
             at c:/Users/alexb/dev/go/src/runtime/sema.go:56
         4  0x000000000047e4bb in sync.(*WaitGroup).Wait
             at c:/Users/alexb/dev/go/src/sync/waitgroup.go:130
         5  0x00000000006a6735 in cmd/go/internal/work.(*Builder).Do
             at c:/Users/alexb/dev/go/src/cmd/go/internal/work/exec.go:187
         6  0x00000000006a08c6 in cmd/go/internal/work.InstallPackages
             at c:/Users/alexb/dev/go/src/cmd/go/internal/work/build.go:605
         7  0x000000000069fc3d in cmd/go/internal/work.runInstall
             at c:/Users/alexb/dev/go/src/cmd/go/internal/work/build.go:516
         8  0x000000000077d0d6 in main.main
             at c:/Users/alexb/dev/go/src/cmd/go/main.go:189
         9  0x0000000000438212 in runtime.main
             at c:/Users/alexb/dev/go/src/runtime/proc.go:203
        10  0x0000000000462c91 in runtime.goexit
             at c:/Users/alexb/dev/go/src/runtime/asm_amd64.s:1375
  Goroutine 2 - User: c:/Users/alexb/dev/go/src/runtime/proc.go:305 runtime.gopa
rk (0x4385e5)
        0  0x00000000004385e5 in runtime.gopark
            at c:/Users/alexb/dev/go/src/runtime/proc.go:305
        1  0x0000000000438485 in runtime.goparkunlock
            at c:/Users/alexb/dev/go/src/runtime/proc.go:310
        2  0x0000000000438485 in runtime.forcegchelper
            at c:/Users/alexb/dev/go/src/runtime/proc.go:253
        3  0x0000000000462c91 in runtime.goexit
            at c:/Users/alexb/dev/go/src/runtime/asm_amd64.s:1375
  Goroutine 3 - User: c:/Users/alexb/dev/go/src/runtime/proc.go:305 runtime.gopa
rk (0x4385e5)
        0  0x00000000004385e5 in runtime.gopark
            at c:/Users/alexb/dev/go/src/runtime/proc.go:305
        1  0x00000000004232bf in runtime.goparkunlock
            at c:/Users/alexb/dev/go/src/runtime/proc.go:310
        2  0x00000000004232bf in runtime.bgsweep
            at c:/Users/alexb/dev/go/src/runtime/mgcsweep.go:89
        3  0x0000000000462c91 in runtime.goexit
            at c:/Users/alexb/dev/go/src/runtime/asm_amd64.s:1375
  Goroutine 4 - User: c:/Users/alexb/dev/go/src/runtime/proc.go:305 runtime.gopa
rk (0x4385e5)
        0  0x00000000004385e5 in runtime.gopark
            at c:/Users/alexb/dev/go/src/runtime/proc.go:305
        1  0x0000000000421718 in runtime.goparkunlock
            at c:/Users/alexb/dev/go/src/runtime/proc.go:310
        2  0x0000000000421718 in runtime.scavengeSleep
            at c:/Users/alexb/dev/go/src/runtime/mgcscavenge.go:203
        3  0x0000000000421a32 in runtime.bgscavenge
            at c:/Users/alexb/dev/go/src/runtime/mgcscavenge.go:302
        4  0x0000000000462c91 in runtime.goexit
            at c:/Users/alexb/dev/go/src/runtime/asm_amd64.s:1375
  Goroutine 5 - User: c:/Users/alexb/dev/go/src/runtime/proc.go:305 runtime.gopa
rk (0x4385e5)
        0  0x00000000004385e5 in runtime.gopark
            at c:/Users/alexb/dev/go/src/runtime/proc.go:305
        1  0x0000000000418b91 in runtime.goparkunlock
            at c:/Users/alexb/dev/go/src/runtime/proc.go:310
        2  0x0000000000418b91 in runtime.runfinq
            at c:/Users/alexb/dev/go/src/runtime/mfinal.go:175
        3  0x0000000000462c91 in runtime.goexit
            at c:/Users/alexb/dev/go/src/runtime/asm_amd64.s:1375
  Goroutine 39 - User: :0 ??? (0x77ace306) (thread 13956)
        0  0x0000000077ace306 in ???
            at ?:-1
            error: Only part of a ReadProcessMemory or WriteProcessMemory reques
t was completed.
        (truncated)
  Goroutine 54 - User: c:/Users/alexb/dev/go/src/runtime/proc.go:305 runtime.gop
ark (0x4385e5)
        0  0x00000000004385e5 in runtime.gopark
            at c:/Users/alexb/dev/go/src/runtime/proc.go:305
        1  0x000000000041c6f4 in runtime.gcBgMarkWorker
            at c:/Users/alexb/dev/go/src/runtime/mgc.go:1880
        2  0x0000000000462c91 in runtime.goexit
            at c:/Users/alexb/dev/go/src/runtime/asm_amd64.s:1375
  Goroutine 55 - User: :0 ??? (0x77acbd7a) (thread 3912)
        0  0x0000000077acbd7a in ???
            at ?:-1
            error: Only part of a ReadProcessMemory or WriteProcessMemory reques
t was completed.
        (truncated)
  Goroutine 56 - User: :0 ??? (0x77acbd7a) (thread 7680)
        0  0x0000000077acbd7a in ???
            at ?:-1
            error: Only part of a ReadProcessMemory or WriteProcessMemory reques
t was completed.
        (truncated)
  Goroutine 991 - User: c:/Users/alexb/dev/go/src/cmd/go/internal/work/exec.go:1
68 cmd/go/internal/work.(*Builder).Do.func3 (0x6dc154)
        0  0x00000000004385e5 in runtime.gopark
            at c:/Users/alexb/dev/go/src/runtime/proc.go:305
        1  0x00000000004469e8 in runtime.selectgo
            at c:/Users/alexb/dev/go/src/runtime/select.go:316
        2  0x00000000006dc154 in cmd/go/internal/work.(*Builder).Do.func3
            at c:/Users/alexb/dev/go/src/cmd/go/internal/work/exec.go:168
        3  0x0000000000462c91 in runtime.goexit
            at c:/Users/alexb/dev/go/src/runtime/asm_amd64.s:1375
  Goroutine 992 - User: c:/Users/alexb/dev/go/src/cmd/go/internal/work/exec.go:1
68 cmd/go/internal/work.(*Builder).Do.func3 (0x6dc154)
        0  0x00000000004385e5 in runtime.gopark
            at c:/Users/alexb/dev/go/src/runtime/proc.go:305
        1  0x00000000004469e8 in runtime.selectgo
            at c:/Users/alexb/dev/go/src/runtime/select.go:316
        2  0x00000000006dc154 in cmd/go/internal/work.(*Builder).Do.func3
            at c:/Users/alexb/dev/go/src/cmd/go/internal/work/exec.go:168
        3  0x0000000000462c91 in runtime.goexit
            at c:/Users/alexb/dev/go/src/runtime/asm_amd64.s:1375
  Goroutine 993 - User: c:/Users/alexb/dev/go/src/cmd/go/internal/work/exec.go:1
68 cmd/go/internal/work.(*Builder).Do.func3 (0x6dc154)
        0  0x00000000004385e5 in runtime.gopark
            at c:/Users/alexb/dev/go/src/runtime/proc.go:305
        1  0x00000000004469e8 in runtime.selectgo
            at c:/Users/alexb/dev/go/src/runtime/select.go:316
        2  0x00000000006dc154 in cmd/go/internal/work.(*Builder).Do.func3
            at c:/Users/alexb/dev/go/src/cmd/go/internal/work/exec.go:168
        3  0x0000000000462c91 in runtime.goexit
            at c:/Users/alexb/dev/go/src/runtime/asm_amd64.s:1375
  Goroutine 1042 - User: c:/Users/alexb/dev/go/src/crypto/sha256/sha256block_amd
64.s:805 crypto/sha256.block (0x5b6351) (thread 14192)
         0  0x00000000005b6351 in crypto/sha256.block
             at c:/Users/alexb/dev/go/src/crypto/sha256/sha256block_amd64.s:805
         1  0x00000000005b25f2 in crypto/sha256.(*digest).Write
             at c:/Users/alexb/dev/go/src/crypto/sha256/sha256.go:198
         2  0x00000000004a3f2e in io.(*multiWriter).Write
             at c:/Users/alexb/dev/go/src/io/multi.go:60
         3  0x00000000004a38c2 in io.copyBuffer
             at c:/Users/alexb/dev/go/src/io/io.go:407
         4  0x00000000004a3621 in io.Copy
             at c:/Users/alexb/dev/go/src/io/io.go:364
         5  0x00000000004a3621 in io.CopyN
             at c:/Users/alexb/dev/go/src/io/io.go:340
         6  0x00000000005be33a in cmd/go/internal/cache.(*Cache).copyFile
             at c:/Users/alexb/dev/go/src/cmd/go/internal/cache/cache.go:490
         7  0x00000000005bdd43 in cmd/go/internal/cache.(*Cache).put
             at c:/Users/alexb/dev/go/src/cmd/go/internal/cache/cache.go:428
         8  0x00000000006a5897 in cmd/go/internal/cache.(*Cache).Put
             at c:/Users/alexb/dev/go/src/cmd/go/internal/cache/cache.go:403
         9  0x00000000006a5897 in cmd/go/internal/work.(*Builder).updateBuildID
             at c:/Users/alexb/dev/go/src/cmd/go/internal/work/buildid.go:706
        10  0x00000000006aaf34 in cmd/go/internal/work.(*Builder).build
             at c:/Users/alexb/dev/go/src/cmd/go/internal/work/exec.go:783
        (truncated)
[13 goroutines]
(dlv)

I also tried reproducing this on another Windows 7 (386 this time) running in VM, and I could not reproduce it. I am not sure what is special about this computer that it fails. But, I guess, if it is a race, then anything is possible. Anything can push it over the age.
Also I can make.bat pass, if I set runtime.preemptMSupported to false.
Let me know, if you want me to debug something. I can reproduce it pretty much every time.
Sorry all this details are vague. That is only free time I had.
Alex

@alexbrainman, thanks for sharing the details you had time to collect. From the Delve output it looks like the process has a lot of threads, which would mean this is a different issue. Could you confirm that through some other process explorer and paste your report into a new issue if there's more than one thread in the hung process?

For the record, this is what @mknyszek was using as a repro (based on dist's test):
stress -p 1 -timeout 10s -- go test -run 'TestParse|TestEcho|TestStdinCloseRace|TestClosedPipeRace|TestTypeRace|TestFdRace|TestFdReadRace|TestFileCloseRace' -race -count 1 - timeout 0 flag net os os/exec encoding/gob

We whittled this down to the following, which fails after a few minutes
go test -c -race flag
stress -p 4 -timeout 10s -- 'flag.test.exe' '-test.run' TestParse '-test.timeout' 0

I think we can unpin this now.

Could you confirm that through some other process explorer and paste your report into a new issue if there's more than one thread in the hung process?

Done. See #36492.
Alex


Error format when copying table from .docx

Bug Description
Copy table from .docx, several issues may happen:

text disappeared
column disappeared if there exist merged cell

What did you expect to happen?
Some table format as in .docx
System, Browser, and Version

MacOS 14.6
Chrome 127.0.6533.120

wangEditor-next Version
"@wangeditor-next/editor": "^5.4.2"
"@wangeditor-next/editor-for-vue": "^5.1.14"
Can the demo reproduce the bug?
Yes

Demo: https://cycleccc.github.io/demo/index.html

Online Demo
https://cycleccc.github.io/demo/index.html
Steps to Reproduce at Minimum Cost

Step 1
copy a table from the attached .docx file
test.docx

Step 2
paste in wangEditor

fixed in 5.5.1

fixed in 5.5.1

@cycleccc  Work well. Thanks!
But in Safari,  after pasting it shows likes this:

What's more, when I use Windows 11 + Office word 2019, and if the text in cell are with Chinese fonts (微软雅黑), after pasting, Chinese characters are lost. But if I set the numbers/alphabets to English fonts, Chinese characters are kept. (Everything works fine on MacOS + Chrome + Office word.)

test2.docx

The second problem in a comment has been fixed, but the first problem is difficult to debug because I don't have a mac device.


Switch to Windows agents & local SQL DB for CI builds

Switch to Windows agents for CI builds in order to use MSSQLLocalDB for tests.
I couldn't verify this in the previous PR as builds didn't kick-off yet.
Relates to #117

/azp run CI

/azp run ci

/azp run ci

/azp run ci

I really don't get it - This works fine here...
https://codit.visualstudio.com/Practical API Guidelines/_build/results?buildId=30497

A-ha - That build was running in debug, YAML in release.

/azp run ci

All is well! Creating issue for release builds


Authorization Matchers: Fix header matcher to check for :method, :path and :authority

According to https://github.com/grpc/proposal/blob/master/A41-xds-rbac.md, headers can include :method, :path, :authority

How urgent is this?
#28267 will finish metadata_batch::GetStringValue method that will allow getting these and all other metadatum being sent without the special casing here.

We're currently transitioning from one metadata implementation to another
and there's a few rough edges.
The pr I linked to above will resolve this specific rough edge - right now
we either use this tagged style of metadata lookup or string style, but the
string style does not know about the other segment for lookups (however it
does for inserts).
It's nothing fundamental other than a desire to work incrementally on a
very difficult set of changes.
On Thu, Dec 16, 2021, 10:31 AM Ashitha Santhosh @.***>
wrote:

@.**** commented on this pull request.
In src/core/lib/security/authorization/matchers.cc
https://github.com/grpc/grpc/pull/28371#discussion_r770807277:

@@ -130,6 +130,23 @@ bool NotAuthorizationMatcher::Matches(const EvaluateArgs& args) const {
}

bool HeaderAuthorizationMatcher::Matches(const EvaluateArgs& args) const {

if (matcher_.name() == HttpMethodMetadata().key()) {

Thank you @yashykt https://github.com/yashykt for making the updates. I
thought GetHeaderValue would be able to fetch :method, :authority and :path
too. But recently, when I was working on the PR related to A41 proposal, I
realized there is some difference. I was just curious, why the change in
the handling of certain metadata keys?
Also I think instead of adding these changes here, we could update
EvaluateArgs::GetHeaderValue
https://github.com/grpc/grpc/blob/master/src/core/lib/security/authorization/evaluate_args.cc#L117
if (key == HttpMethodMetadata().key()) {
return GetMethod();
}
// similarly for :path and :authority
And we don't have to change HeaderAuthorizationMatcher::Matches.
—
Reply to this email directly, view it on GitHub
https://github.com/grpc/grpc/pull/28371#pullrequestreview-834462293, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACNG45PE7NX6HDOZB3OECGTURIV7BANCNFSM5KFFECOA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because your review was requested.Message ID:
@.***>

Oh I see. Thank you @ctiller for the explanation:)

It's urgent in the sense that RBAC is broken right now since these known metadata types are not handled properly, so if https://github.com/grpc/grpc/pull/28267 is gonna take longer than a day or so, I'd like to get this in.
I can add a TODO to remove this once #28267 lands

Issues: #26072


Fix the GetFileInformationByHandleEx function usage

There are two issues in the current implementation of the msys_tty_on function. Firstly, the size returned by the GetFileInformationByHandleEx function is the size in bytes not in characters. Secondly, the path can exceed the MAX_PATH constant.
I stumbled upon this issue when some of our tests begin to fail on Windows after the update to the env_logger 0.10 version which switches to the is-terminal crate.

Alternatively, a slightly different implementation from the standard library can be used. At least it does take into account that the size in bytes is returned.

@sunfishcode Friendly ping. 🙃

Thanks for the ping! This looks good to me.

This is now released in 0.4.2.

@sunfishcode Thanks!


[pylon]parser of cluster object model

2 internal used configurations will be undocumented.

webhdfs_legacy_port is for legacy use
deploy_service is for future use

Coverage increased (+0.01%) to 51.774% when pulling 762a6bd2b40056e81c562fa764515845aba939eb on qixcheng/pylon/parser into e3775d69023d0111559c7e09e31269a4e4dd7c81 on yuye/improve-com.

Coverage increased (+0.01%) to 51.774% when pulling 762a6bd2b40056e81c562fa764515845aba939eb on qixcheng/pylon/parser into e3775d69023d0111559c7e09e31269a4e4dd7c81 on yuye/improve-com.

Coverage increased (+0.01%) to 51.774% when pulling 762a6bd2b40056e81c562fa764515845aba939eb on qixcheng/pylon/parser into e3775d69023d0111559c7e09e31269a4e4dd7c81 on yuye/improve-com.

Coverage increased (+0.01%) to 51.774% when pulling 762a6bd2b40056e81c562fa764515845aba939eb on qixcheng/pylon/parser into e3775d69023d0111559c7e09e31269a4e4dd7c81 on yuye/improve-com.


Edit the JSON using property-based components instead of raw JSON.

Add element
Select element type, i.e. text, number, list, object
Show input field(s) for selected type
Generate JSON behind the scene

Maybe like this: https://github.com/josdejong/jsoneditor


g++: error: unrecognized command line option ‘-mavx512f’

When I compile avx512_vectorized_addition.cpp, it said "g++: error: unrecognized command line option ‘-mavx512f’".

It seems strange to me since avx512f is supported by the cluster CPU. Could you please tell me your student ID so that I can login your account and help you fix it? If you have changed the password, please send a email to me about your student ID and password.

My student ID is 120090702.
Sincerely,

Li, Yiqian
发件人: Yuxuan @.>
发送时间: 2023年9月11日 11:17
收件人: @.>
抄送: Yiqian Li (SDS, @.>; State @.>
主题: Re: [tonyyxliu/CSC4005-2023Fall] g++: error: unrecognized command line option ‘-mavx512f’ (Issue #4)
It seems strange to me since avx512f is supported by the cluster CPU. Could you please tell me your student ID so that I can login your account and help you fix it? If you have changed the password, please send a email to me about your student ID and password.
[image]https://user-images.githubusercontent.com/62693471/266897955-0be57f03-4398-424c-a42a-4c4de526679f.png
―
Reply to this email directly, view it on GitHubhttps://github.com/tonyyxliu/CSC4005-2023Fall/issues/4#issuecomment-1713096543, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASUAY7DYXHX4QFPQ4QZMEGLXZZ7EJANCNFSM6AAAAAA4SRTS24.
You are receiving this because you modified the open/close state.Message ID: @.***>

Hi Yiqian @Lee-7102
I just login your account but found that everything worked as expected. I have attached the terminal input & output below. I don't know why this failed in your computer. Maybe you should bring your laptop to the classroom on the tutorials this week.
[120090702@node21 sample_programs]$ pwd
/nfsmnt/120090702/sample_programs
[120090702@node21 sample_programs]$ ls
avx512_vectorized_addition      cuda_hello.cu  mpi_hello.cpp     openacc_parallel.cpp  openmp_hello.cpp  pthread_hello.cpp
avx512_vectorized_addition.cpp  mpi_hello      openacc_parallel  openmp_hello          pthread_hello     README.md
[120090702@node21 sample_programs]$ g++ -mavx512f avx512_vectorized_addition.cpp -o avx512_vectorized_addition
[120090702@node21 sample_programs]$ ./avx512_vectorized_addition
c[0] = 0
c[1] = 3
c[2] = 6
c[3] = 9
c[4] = 12
c[5] = 15
c[6] = 18
c[7] = 21
c[8] = 24
c[9] = 27
c[10] = 30
c[11] = 33
c[12] = 36
c[13] = 39
c[14] = 42
c[15] = 45

OK. Thank you, TA!
Sincerely,

Li, Yiqian
发件人: Yuxuan @.>
发送时间: 2023年9月11日 12:18
收件人: @.>
抄送: Yiqian Li (SDS, @.>; @.>
主题: Re: [tonyyxliu/CSC4005-2023Fall] g++: error: unrecognized command line option ‘-mavx512f’ (Issue #4)
Hi Yiqian @Lee-7102https://github.com/Lee-7102
I just login your account but found that everything worked as expected. I have attached the terminal input & output below. I don't know why this failed in your computer. Maybe you should bring your laptop to the classroom on the tutorials this week.
@.*** sample_programs]$ pwd
/nfsmnt/120090702/sample_programs
@.*** sample_programs]$ ls
avx512_vectorized_addition      cuda_hello.cu  mpi_hello.cpp     openacc_parallel.cpp  openmp_hello.cpp  pthread_hello.cpp
avx512_vectorized_addition.cpp  mpi_hello      openacc_parallel  openmp_hello          pthread_hello     README.md
@.*** sample_programs]$ g++ -mavx512f avx512_vectorized_addition.cpp -o avx512_vectorized_addition
@.*** sample_programs]$ ./avx512_vectorized_addition
c[0] = 0
c[1] = 3
c[2] = 6
c[3] = 9
c[4] = 12
c[5] = 15
c[6] = 18
c[7] = 21
c[8] = 24
c[9] = 27
c[10] = 30
c[11] = 33
c[12] = 36
c[13] = 39
c[14] = 42
c[15] = 45
―
Reply to this email directly, view it on GitHubhttps://github.com/tonyyxliu/CSC4005-2023Fall/issues/4#issuecomment-1713136402, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASUAY7FWNJVAXJRD4UQYMELXZ2GH3ANCNFSM6AAAAAA4SRTS24.
You are receiving this because you were mentioned.Message ID: @.***>

Hi all,
I met the same problem on my own desktop's docker image. My processor is 11th Gen Intel(R) Core(TM) i5-11400F @ 2.60GHz, and result from /proc/cpuinfo indicates that my processor supports avx512f instruction set. In addition, g++ --version says version is g++ (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44). From here, I guess that's because g++ 4.8 in that docker image does not support avx512f?

Yes, if you find your gcc version is 4.8.5 on the cluster, please refer to this updated issue 3 and add gcc-7 bin to the system $PATH.

Hi all, I met the same problem on my own desktop's docker image. My processor is 11th Gen Intel(R) Core(TM) i5-11400F @ 2.60GHz, and result from /proc/cpuinfo indicates that my processor supports avx512f instruction set. In addition, g++ --version says version is g++ (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44). From here, I guess that's because g++ 4.8 in that docker image does not support avx512f?

u can upgrade it in docker 😅

Hi all, I met the same problem on my own desktop's docker image. My processor is 11th Gen Intel(R) Core(TM) i5-11400F @ 2.60GHz, and result from /proc/cpuinfo indicates that my processor supports avx512f instruction set. In addition, g++ --version says version is g++ (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44). From here, I guess that's because g++ 4.8 in that docker image does not support avx512f?

u can upgrade it in docker 😅

Yeah, of course, thank you for your solution. I have already done this last week. Can't figure out what your emoji means.

乐

发件人: Lai Wei @.>
发送时间: 2023年9月19日 19:51
收件人: tonyyxliu/CSC4005-2023Fall @.>
抄送: Zhen Tong (SDS, 120090694) @.>; Comment @.>
主题: Re: [tonyyxliu/CSC4005-2023Fall] g++: error: unrecognized command line option ‘-mavx512f’ (Issue #4)
Hi all, I met the same problem on my own desktop's docker image. My processor is 11th Gen Intel(R) Core(TM) i5-11400F @ 2.60GHz, and result from /proc/cpuinfo indicates that my processor supports avx512f instruction set. In addition, g++ --version says version is g++ (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44). From herehttps://stackoverflow.com/questions/57043592/compilation-error-for-avx512-is-it-a-gcc-issue, I guess that's because g++ 4.8 in that docker image does not support avx512f?
u can upgrade it in docker 😅
Yeah, of course, thank you for your solution. I have already done this last week. Can't figure out what your emoji means.
—
Reply to this email directly, view it on GitHubhttps://github.com/tonyyxliu/CSC4005-2023Fall/issues/4#issuecomment-1725350779, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AVDWSRMSR6PAQZWPNYUHQRTX3GBM3ANCNFSM6AAAAAA4SRTS24.
You are receiving this because you commented.Message ID: @.***>


Update docs site with latest from master -> gh-pages

Update docs site with latest from master -> gh-pages
https://wilix-team.github.io/iohook/

Closing as irrelevant. Apparently resolved.


[Feature]: Add transformation for AWS Config endpoint

Self-service

[ ] I'd be willing to implement this feature

Problem
Transformer does not transform config endpoint from v2 to v3.
Input
import AWS from "aws-sdk";

const client = new AWS.DynamoDB({
  endpoint: "http://localhost",
});

Output
import { DynamoDB } from "@aws-sdk/client-dynamodb";

const client = new DynamoDB({
  // The transformation for endpoint is not implemented.
  // Refer to UPGRADING.md on aws-sdk-js-v3 for changes needed.
  // Please create/upvote feature request on aws-sdk-js-codemod for endpoint.
  endpoint: "http://localhost",
});

Solution
Add transformation for endpoint, where there are no changes in output code.
Alternatives
N/A
Additional context
https://github.com/CrowdDotDev/crowd.dev/blob/01dc55271f5f2572e16fd092c7f719f29fc2f2fb/backend/src/services/aws.ts#L22

https://github.com/relatedcode/Messenger/blob/fa8b18b222fe6c141e62198d8c148157a01fd490/api/src/utils/storage.ts#L18

https://github.com/trivikr/serverless-patterns/blob/a0e762f85bb49842b30d98e40f71035c830b8331/apigw-lambda-sfn-transcribe-translate-polly-sam/src/invokeTranslator.js#L4

https://github.com/uselagoon/lagoon/blob/eee3dabd8b0c372e5c9a2b0835577aca0429c430/services/api/src/clients/aws.ts#L13

+1


What is the capacity of Arangodb and how many data can be stored without obvious performance degradation. Can you provide some information for reference, including hardware information? Thank you.

ArangoDB Version: 3.4
Storage Engine: RocksDB
Deployment Mode: Single Server
Infrastructure: own
Operating System: Ubuntu 16.04
Used Package:  Ubuntu .deb

The information is interesting for me too.
This could help me to decide if multi-company would be possible regarding performance.

@cangsangkanyun and @CBlinguland
I am closing this issue as solved for now.
In case you have any further questions, please feel free to comment and we will reopen.


⚠ ClamAV has degraded performance

In 7b43bf1, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 52 ms

Resolved: ClamAV performance has improved in 2c48986.


fix(42019): Quick info on implementation is missing JSDoc tags from interface declaration

Fixes #42019

Hi @a-tarasyuk  - great PR. Looking at the outcome of the tests and the internal logic this feels like a solid answer to me 👍🏻

Hi @a-tarasyuk  - great PR. Looking at the outcome of the tests and the internal logic this feels like a solid answer to me 👍🏻

@orta Thanks

@orta Thanks


Backslash in folder name still not handled correctly by flattened tree view

Related to https://github.com/microsoft/vscode/issues/81798

Create a folder with \ in name
Add a file to it
Stage it

It will duplicate itself:

Forgot to update the delete method in https://github.com/microsoft/vscode/commit/c850f0716e6193d0a11d48c81b29c8aff6147d1b :man_facepalming:

Verification: Follow steps in first comment. ⬆


Uncaught TypeError: Cannot read property 'length' of undefined        (SingleSelectionIListModel.js:156)

Project Details are :
https://paste.apache.org/cpo8y
Test case is available on VDI.
Go to Purchase from Select in Menu
Go to Reports -> Product Ledger in Menu
File : com/dbz/reports/view/INV/dbzProductLedger.mxml

Looks like dataProvider is not set.  Try adding a check to make sure dataProvider is not null in DropDownListBase

i have added a check in DropDownListBase's get and set DataProvider
when i open dbzProductLedger the debugger goes to get DataProvider
if(dataProvider == null)
   trace("dataprovider is null" + dataProvider);
}

this.dataprovider
Message : maximum call stack size exceeded
Stack : "RangeError: Maximum call stack size exceeded
at spark.components.DropDownList.spark.components.supportClasses.DropDownListBase.get__dataProvider (http://localhost:8080/SHMA/spark/components/supportClasses/DropDownListBase.js:35:88)
at spark.components.DropDownList.spark.components.supportClasses.DropDownListBase.get__dataProvider (http://localhost:8080/SHMA/spark/components/supportClasses/DropDownListBase.js:36:12)
at spark.components.DropDownList.spark.components.supportClasses.DropDownListBase.get__dataProvider (http://localhost:8080/SHMA/spark/components/supportClasses/DropDownListBase.js:36:12)
at spark.components.DropDownList.spark.components.supportClasses.DropDownListBase.get__dataProvider (http://localhost:8080/SHMA/spark/components/supportClasses/DropDownListBase.js:36:12)
at spark.components.DropDownList.spark.components.supportClasses.DropDownListBase.get__dataProvider (http://localhost:8080/SHMA/spark/components/supportClasses/DropDownListBase.js:36:12)
at spark.components.DropDownList.spark.components.supportClasses.DropDownListBase.get__dataProvider (http://localhost:8080/SHMA/spark/components/supportClasses/DropDownListBase.js:36:12)
at spark.components.DropDownList.spark.components.supportClasses.DropDownListBase.get__dataProvider (http://localhost:8080/SHMA/spark/components/supportClasses/DropDownListBase.js:36:12)
at spark.components.DropDownList.spark.components.supportClasses.DropDownListBase.get__dataProvider (http://localhost:8080/SHMA/spark/components/supportClasses/DropDownListBase.js:36:12)
at spark.components.DropDownList.spark.components.supportClasses.DropDownListBase.get__dataProvider (http://localhost:8080/SHMA/spark/components/supportClasses/DropDownListBase.js:36:12)
at spark.components.DropDownList.spark.components.supportClasses.DropDownListBase.get__dataProvider (http://localhost:8080/SHMA/spark/components/supportClasses/DropDownListBase.js:36:12)"
value is :

The null check should go in the selectedItems setter, not in the dataProvider getter/setters.

same output for selectedItems setter as for dataProvider getter/setters.
maximum call stack size exceeded

What code did you try?  Did you use _dataProvider instead of dataProvider like the rest of the setter?


[TF] Fix flaky dataset test

In SR-8575 @mhong found out that the execution order was undefined because #tfop("IteratorV2", ...) was not set up to return ResourceHandle, and graph lowering thereby did not add the necessary control dependencies.  This should've been caught by graph lowering, but it apparently wasn't.
This fixes the existing flaky test TensorFlowRuntime/dataset_1.swift.

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow

Merging to fix broken CI.

@swift-ci please test tensorflow

Nice!


USB Passthrough with Apple Virtualization

Feature Request: Connect USB devices to a virtual machine that is virtualized using Apple Virtualization.
Example use case: attach USB storage device to the virtual machine.
This is possible in QEMU, but that would lose Rosetta x86 emulation.

Duplicate of #3778


[bazel] run verilator on workspace

I mostly just want to kick off the CI and check it's healthy after https://github.com/lowRISC/opentitan/pull/10041 landed
Signed-off-by: Drew Macrae<EMAIL_ADDRESS>

I'm looking into the CI failure in bazel that's happening here.


Page is scrolled down when I type a text with the space symbol (Safari 11)

Are you requesting a feature or reporting a bug?
bug
What is the current behavior?
Page is scrolled down when I type a text with the space symbol into a content editable element.
What is the expected behavior?
Page should not be scrolled.
How would you reproduce the current behavior (if this is a bug)?
Start the client test into the Safari 11.
Provide the test code and the tested page URL (if applicable)
Tested page URL:
test\client\fixtures\automation\content-editable\api-actions-content-editable-test\index-test.js
Specify your

operating system: win 8.1
testcafe version: 0.18.6-dev20171211
node.js version: 9.0.0

Seeing this issue referenced in the code alongside https://github.com/DevExpress/testcafe/issues/2008. Can we re-open unless they've been resolved?

Yes, you can re-open issues if they still affect your use cases.


set the usage when creating notification channels on Android

Description of Change
When channels are created in Android, media volume is what is used, instead of using notification volume. Set the usage to AudioUsageKind.Notification so that all of the volumes work the proper way and the correct sounds are presented to the user.
Issues Resolved
None
API Changes
None
Platforms Affected

Android

Behavioral Changes
None
Testing Procedure
Create a new channel on Android and make sure that Notification Volume controls the sound, and not Media Volume.
PR Checklist

[x] Rebased on top of the target branch at time of PR
[x] Changes adhere to coding standard
[x] Sent to a v(branch) or DEV branch

Thanks for the PR


JLCPCB should export separate front/back position files

This is why the placement in my test board isn't working properly. JLCPCB expects separate front and back position files and the offset location is different between the two.
See https://github.com/matthewlai/JLCKicadTools/blob/73057998b2bf1965d31161aa58ed487dcb4cad73/jlc_kicad_tools/jlc_lib/cpl_fix_rotations.py#L94 for where I found this.
Place to change the script: https://github.com/neilenns/12x16-LED-Matrix/blob/a8eb79cb8853e4807517e132f47c49ad7ec36b13/.kibot/includes/JLCPCB-2layer.kibot.yaml#L74

Also need to change the output name to output: "%f_cpl_%i_jlc.%x".

This is all wrong.


Is this compatible with Debut theme?

There's no package.json out of the box. No webpack. Not sure if ES6 is supported. No documentation anywhere. Slate theme is deprecated. This library isn't maintained. WTF Shopify.

There's no package.json out of the box. No webpack. Not sure if ES6 is supported. This library isn't maintained.

Not sure I follow - can you clarify? These are individual node modules you can bring into your own theme project. There wouldn't be a need to use Webpack, ES6 depends on what browsers you need to target for your project, and while we're not extremely active on this repository, it is no way deprecated and we will continue to add to it over time.


Adding dominodatalab.com labels to Service, NetworkPolicy to Spark DCO

Ensure the correct dominodatalab.com labels exist on the correct K8s resources for DCO Spark

I think we should use the same approach as Dask to add global labels but I will defer to @sonnysideup on this.
https://github.com/dominodatalab/distributed-compute-operator/blob/2e68bab1794d1075f34e216aeeaf0082719de5f4/pkg/cluster/dask/metadata.go#L19


File Transform - does not replace empty applicationSettings values

Question, Bug, or Feature?
Type: Bug
Enter Task Name: File transform
Environment

Server - Azure Pipelines
Agent - Windows Server 2019 Datacenter

Issue Description
App.config settings with an empty value element are not replaced (task version 1).

File format: XML
parent stage has a linked variable group with a key for each setting name

relevant config file part:
...
<applicationSettings>
    <ProjectName.Properties.Settings>
      <setting name="Setting1" serializeAs="String">
        <value>foobar</value>
      </setting>
      <setting name="Setting2" serializeAs="String">
        <value></value>
      </setting>
      <setting name="Setting3" serializeAs="String">
        <value> </value>
      </setting>
      <setting name="Setting4" serializeAs="String">
        <value/>
      </setting>
   </ProjectName.Properties.Settings>
</applicationSettings>

Values for Setting2, Setting3, Setting4 are not updated and are changed to <value/>, which might cause other issues, e.g., setting value changing from empty string or whitespace to null.
For values that are updated, task log contains 2 rows when a setting is replaced - is repeated after  Processing substitution for xml node : configSections. configSections does not contain these keys
Task logs
Task logs don't contain rows for the "empty" settings, would look like:
Processing substitution for xml node : applicationSettings
Updating value for key= Setting1 with token value: CONFIG_FILE_SETTINGS_TOKEN(Setting1)
Processing substitution for xml node : connectionStrings
Processing substitution for xml node : configSections
Updating value for key= Setting1 with token value: CONFIG_FILE_SETTINGS_TOKEN(Setting1)

I tried to reproduce this issue. value for settings3 replaced for me. Yes other 2 cases are not handled.

@gunars-skangals We do not support the scenario of Settings 2 and settings 4 with empty value to be replaced.

that would be the same as not supporting transformations in JSON for keys like
{
  "key1": null,
  "key2": ""
}

otherwise - this is for the .NET Framework setting format which will be irrelevant soon enough and meanwhile i can deal with this by having dummy values everywhere

@gunars-skangals Can we close this issue ?

Since we do not support these scenarios, please feel free to re-open if you face any other issue.


Implement history search in repl via up/down arrows

Resolves #196

Some possible improvements are documented in #199.

Pull Request Test Coverage Report for Build 303

4 of 47 (8.51%)  changed or added relevant lines in 7 files are covered.
4 unchanged lines in 4 files lost coverage.
Overall coverage decreased (-0.4%) to 25.706%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/actions/workspaces.ts
2
4
50.0%

src/containers/assessment/AssessmentWorkspaceContainer.ts
0
2
0.0%

src/containers/PlaygroundContainer.ts
0
2
0.0%

src/containers/academy/grading/GradingWorkspaceContainer.ts
0
2
0.0%

src/components/workspace/ReplInput.tsx
0
6
0.0%

src/reducers/workspaces.ts
0
29
0.0%

Files with Coverage Reduction
New Missed Lines
%

src/containers/academy/grading/GradingWorkspaceContainer.ts
1
39.13%

src/reducers/workspaces.ts
1
8.27%

src/containers/assessment/AssessmentWorkspaceContainer.ts
1
39.13%

src/containers/PlaygroundContainer.ts
1
39.13%

Totals

Change from base Build 297:
-0.4%

Covered Lines:
719

Relevant Lines:
2367

💛  - Coveralls

Changes made with c6b0fdc and d4eb7ae.


Detected that custom integration 'yamaha_ynca' sets "minor_version" directly to update a config entry

Describe the bug
Log shows following warnings about migration changing version
2024-06-16 18:13:46.352 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'yamaha_ynca' sets "minor_version" directly to update a config entry. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to use async_update_entry instead at custom_components/yamaha_ynca/migrations.py, line 131: config_entry.minor_version = 2, please create a bug report at https://github.com/mvdwetering/yamaha_ynca/issues
2024-06-16 18:13:46.353 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'yamaha_ynca' sets "minor_version" directly to update a config entry. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to use async_update_entry instead at custom_components/yamaha_ynca/migrations.py, line 112: config_entry.minor_version = 3, please create a bug report at https://github.com/mvdwetering/yamaha_ynca/issues
2024-06-16 18:13:46.354 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'yamaha_ynca' sets "minor_version" directly to update a config entry. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to use async_update_entry instead at custom_components/yamaha_ynca/migrations.py, line 83: config_entry.minor_version = 4, please create a bug report at https://github.com/mvdwetering/yamaha_ynca/issues

To Reproduce
Steps to reproduce the behavior:

Have an old config entry which needs migration
Trigger migration

Expected behavior
No warnings in the Home Assistant lgos
Diagnostics
N.A.
Logging
See description
Environment
Provide details about the versions you are using, which helps to reproduce and find the issue quicker.

Home Assistant Core version: HA core 2024.6.0
Home Assistant operating environment (OS/Container/Supervised/Core): Core
Integration version: dev, but is in all
Last working version (if known):

Additional context
No

Fixed with PR #303


[User Interface: Redesign]: Limit the number of topicCategory items displayed in card view

Issue Name
Limit the number of topicCategory items displayed in card view
Issue Description
Some records like Figshare may have a lot of topicCategories due to mappings -- this will clutter the card view. Limit the number of topicCategory items displayed in the card view
Issue Discussion
This is considered a minor change and will not be discussed extensively
Mockup URL
No response
WCAG Compliance Check

[X] The ui changes are not expected to significantly affect WCAG compliance (ex- wording changes)
[ ] The ui changes have visual elements which have yet to be tested for WCAG compliance
[ ] The ui changes have visual elements which have been tested for WCAG compliance
[ ] The ui changes have passed all checks for WCAG compliance

Related WBS task

[X] Check here if the ui change is centered on the look and feel (https://github.com/NIAID-Data-Ecosystem/nde-roadmap/issues/52)
[ ] Check here if the ui change includes new features (https://github.com/NIAID-Data-Ecosystem/nde-roadmap/issues/53)
[ ] Check here if the ui change was suggested by the NIAID team (https://github.com/NIAID-Data-Ecosystem/nde-roadmap/issues/2)

For internal use only. Assignee, please select the status of this issue

[ ] Not yet started
[ ] In progress
[ ] Blocked
[ ] Will not address

Status Description
No response
UI change status check list

[X] This ui change has yet to be discussed between NIAID, Scripps, Leidos
[ ] This ui change has been discussed/reported between NIAID, Scripps, Leidos
[ ] This ui change has been mocked up
[ ] This ui change has been implemented on Dev
[X] This ui change has been approved for Staging
[ ] This ui change has been implemented on Staging
[ ] This ui change has been approved for Production
[ ] This ui change has been implemented on Production

Changes are applied on all instances.
Old:

Update:


implement code standard

https://github.com/airbnb/javascript

@qw3rtman

Implemented Airbnb's Javascript coding standards into existing project: mattpat/node-schedule#79.


EFI Shell Getting Started Guide pdf is 404 (Bugzilla Bug 1531)

This issue was created automatically with bugzilla2github
Bugzilla Bug 1531
Date: 2019-02-16T00:17:45+00:00
From: Carl <>
To:   Stephano Cetola <>
CC:   edk2+bugs+int+994+563148131503455288, yonghong.zhu
Last updated: 2019-10-08T17:32:42+00:00

Comment 6496
Date: 2019-02-21 20:12:36 +0000
From: Yonghong Zhu <<yonghong.zhu>>
Assign to Stephano

Comment 6376
Date: 2019-02-16 00:17:45 +0000
From: Carl <>

Industry Specification: ---
Target OS: ---

This page:
https://github.com/tianocore/tianocore.github.io/wiki/Efi-shell
contains this link:
Download the "EFI Shell Getting Started Guide" (pdf)
http://cdnetworks-us-1.dl.sourceforge.net/project/efi-shell/Releases/Snapshot Release Notes/EFI_Shell_Release_Notes0_91.pdf
404

Comment 9963
Date: 2019-10-08 17:32:42 +0000
From: Stephano Cetola <>
Test groups.io email address #3

Comment 9948
Date: 2019-10-08 17:23:07 +0000
From: Stephano Cetola <>
Test groups.io email address #2

Comment 9947
Date: 2019-10-08 17:17:41 +0000
From: Stephano Cetola <>
Test groups.io email address


Vector backend refactor

Remove dependency on std::array
Re-introduce compatibility with HIP_vector_type
Introduce HIP vector compatibility for non-native types (not built-in, represented by container classes such as bfloat16 and __half)
Extend HIP_vector_type size support (VecSize = 8, 16, 32, 64, 128, 256)
Start implementing drop-in std:: classes for hipRTC support
Integrate HIP_vector_type to rocwmma, adjust unit tests

Disabling GEMM i8 tests until LLVM patch is merged to compute-rocm-dkms-no-npi-hipclang


Smarter Corpse Role Selection

In the recent 1.1.0 update, corpses will now always show up as innocent. This is regardless of the original role of the player.
This is an issue because some roles like Detective should probably show up as detectives and not as an innocent.
Unfortunately, I will have to write two fixes for both TTT and TTT2.
Proposal
TTT
For TTT, we know upfront what all the roles are. We have Innocent, Traitor, Detective. The fix here is pretty simple. Traitors using the dead ringer will show up as innocents, but Detectives will show up as Detectives.
TTT2
For TTT2, we don't know what roles a server might have. However, we do have access to some information about them. TTT2 lets us query roles for information such as whether or not they are a public role, a policing role, or omniscient (sees MIA players).
My proposal here is for public to always show their real role. Any other type of role will respect  the ttt_deadringer_corpse_role convar to either show their real role or show up as innocent.
However, I am still a bit hesitant on this. There seems to be some differing opinions so I am opening this up to discussion

Ok I have gone with a new approach. I have changed the ttt_deadringer_corpse_role setting to a new ttt_deadringer_corpse_mode setting.
There are currently 3 modes:

0 (default) - A corpse with a 'Fake' role/team will be spawned for TTT2, for TTT this will just show innocent
1 - A corpse will spawn with the player's REAL role (traitors will show as traitors, jackals as jackals, etc.) for both TTT2 and TTT
2 - A corpse will spawn with a spoofed innocent role (traitors appear as innocent)

By default the corpse's role will NOT be confirmed when identifying the body. This is to prevent confusion with the scoreboard in most cases. I do NOT recommend turning this on but you can if you want.
Corpses with the 'Fake' role CANNOT be confirmed in any way.


Allow for configurable container startup command

Enhancement Proposal
Currently the pebble layer for the charm is hard coded to use /srv/gunicorn/run as the startup command for workloads running in the "gunicorn" container. It would be more flexible if we defaulted to this, but allowed for it to be overrriden via Juju config. This would mean we can deploy more images unmodified.

This is now available in edge, will be in stable with the next stable release


cutpoint: Clarify control flow and improve efficiency

This PR makes a number of changes to clarify control flow; multiple instances like:
for(...) {
    if (!cond)
        continue;
    //...
}

into the clearer:
for(...) {
    if (cond) {
        //...
    }
}

It also changes a loop like:
for (auto wire : module->wires()) {
    if (!wire->port_input)
        continue;
    //...
}

into the more efficient:
for (auto id : module->ports) {
    RTLIL::Wire *wire = module->wire(id);
    if (wire->port_input) {
        //...
    }
}

The PR is split into three commits for easier review, but I am happy to rebase this into one commit if preferred.

The downside of course is that it adds indentation levels, so that now an even greater portion of the default github viewport is occupied by whitespace (and everyone loves scrolling sideways...) I guess I'll put it to a vote at the thursday meeting.

We actually think that early exit is the cleaner way to go. We are not alone. For example, LLVM: https://llvm.org/docs/CodingStandards.html#use-early-exits-and-continue-to-simplify-code


Change version to 3.7.2

Checklist

[x] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@souravsingh @mpenkov @menshikh-iv how do the Conda releases work exactly? Is there some documentation for this process?
Can you answer the gentleman asking about it here? https://groups.google.com/forum/#!topic/gensim/khNKMpT3YRc
Thanks!

@piskvorky The conda-forge docs mention everything about how packages are maintained- https://conda-forge.org/docs/
Essentially, if someone wishes to update the recipe, they have to update the version number and SHA in the meta.yaml file. The CI then fetches the tarballs from pypi.io and builds and tests it for conda. Once the tests pass, the build files are uploaded to the conda-forge channel from where anyone can download the package. There is also a bot which does this step automatically when a new version of a package is uploaded to PyPI, as shown in the PR here- https://github.com/conda-forge/gensim-feedstock/pull/26
As for the question asked regarding Mac OS X support, this was a problem back in the day when the recipe was created,which caused the tests on Mac OS X to timeout and fail. I believe the situation may have changed with the use of Azure pipelines for CI testing and changes in the gensim package and support for Mac is possible, but it is something that hasn't been tried.

@piskvorky Does this answer the queries? You could get in touch with people in conda-forge team if needed.


an issue and a question

is there anyway i can make the web server remotely viewable?
isnt it supposed to dumps a log of the decoded requests and the raw requests?

Hi,
You can see the web server from anywhere, if it's running on your home, just enable port forwarding on your router and make sure windows firewall lets you get through.
It does dump the logs, just edit the pogomitm.exe.config and set DumpRaw and DumpProcessed to true. Also make sure you have

Next release will fix the dump problems.


A feature request for droping root privileges

It would be nice if you could implement such feature for security reason. Switcher runs with root privileges on privileged ports it could have some obvious bad implications.

you may need linux command setcap


self.extend_orms should include ActiveRecord and Mongoid ORMs by default

self.extend_orms is now [:active_record, :mongoid] by default
ORMs will be skipped if the required gem hasn't been loaded, even if self.extend_orms includes that ORM
Note that even prior to this commit the README.rdoc states that AR is included by default, but it is not currently
I've updated the README.rdoc to clarify this behavior

It not includes active_record by default in the generated initializer. This should work for newbies.
I have extracted out all mongoid support to https://github.com/adzap/validates_timeliness-mongoid. Would you like to take over that repo?

@adzap yes please add me as an admin / collaborator of validates_timeliness-mongoid and also give me Rubygems permissions to make releases.

I added you as a collaborator, but then realised I should just transfer it to you. There is no published gem yet, so you can push one and own it.


Inconsistent redeclared symbol compilation error

Description:

For the below code it gives a compilation error saying redeclared symbol.
function foo() {
    int a = 2;

    var func = function (string a) returns string {
        return "hello " + a;
    };
}

gives
Compiling source
        newiss.bal
ERROR [newiss.bal:(4:26,4:34)] redeclared symbol 'a'
error: compilation contains errors

But if we change the order of the two statements, it is not giving the error.
function foo() {
    var func = function (string a) returns string {
        return "hello " + a;
    };

    int a = 2;
}

I think it should behave the same way in both cases.
Steps to reproduce:
Given above.
Affected Versions:
Ballerina 2201.1.0 (Swan Lake)
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

@Nadeeshan96 This behaviour is explained in 5.9.3 Variable and identifier scoping. The function expr works as block scope and its parameters shadows the parent scode variable a in the first example. But in the second example there is no shadowing. So this behaviour is correct.


Fix bug where null response were accidentally excluded from profile export

Null responses were accidentally not included in raw timestamps vector for each request. We actually want those in the profile export. This adds them in, but still excludes them from response throughput calculation.

simple unit test to lock in this behavior and this is good to go


add encryption support

DONE - decryptEvent
encryptData
decryptData
DONE - encryptEvent

https://www.npmjs.com/package/aws-kms-ee

obfuscate when logging if encryptionInfo is present
do the same for fault events as well

add debug logger redaction support
wrap debug added to pipeline
pass options
visit all args
find eem elements and collect field names
obfuscate any listed field with ****


Use with angular app

Hi, i am new to mjml , i am install the mjml into the my angular application, but i am block in the build time i need to convert the mjml files into the html, can you any one guide me ?How i do with this CLI build .
Thank you.

closed

Can you please provide more details about this ?
If you need mjml2html on your front end you can use mjml-browser package that can be used.
If you only want to convert in cli then follow the instruction in the readme.

Closing for now feel free to reopen with more details


Fixed instance completion with profile

Now completion takes care of the aws profile
After this PR gets merged, if so, a release will be highly appreciated ;)

@padilo Thanks for the work and idea.
This implementation introduce real network calls to the AWS APIs to retrieve completion information. Before, thanks to the local always present, the fetching operated locally on the data graph. This is one of the strong point of awless to be able to use with no cost this local graph for a lot of things.
My concern is that since a lot of our users have huge resources graph regardless of their profile (and so far awless has helped them a lot managing that), fetching this amount of data just for completion could be a bit problematic in term of lagging and responsiveness - although I understand well that putting the flag -p is a way of saying "go and fetch my data remotely".

Would there be a way of clarifying better (i.e. notifying the CLI user) the fact that completion is being resolved by fetching remote data?

And yes a release is scheduled in this week. The delay is due to our major design of our AWS modelling so we get more flexibility and scalability in the future.

Completely agree on the problem about network calls, the problem is that currently the autocomplete is broken when using --aws-profile, because it tries to do the completion with a invalid list of instances.
That's why on this PR the --local will be still used when user doesn't specify the profile using awless flags.
This will fix this problem when using profiles, but it will introduce some problems in terms of performance if user has many resources on AWS account.
So... Probably the good way to solve this is to have the data graph by aws profiles, in case there is one, and by now just disable the autocomplete if user sets a profile, because the autocompletion is wrong. I don't check enough how the data graph is done, and If what I'm saying has sense at all, sorry about that.
Could you describe shortly the devops use case you are trying to cover (i.e. the daily struggle your are trying to solve)?

In my case I jumping across 12 AWS accounts, and it helps me a lot to have completion to just connect to the instance I need using awless ssh command
Would there be a way of clarifying better (i.e. notifying the CLI user) when the completion is being resolved by fetching remote data?

I can check that, not sure. But I think using the local data maybe is the only good way to solve this.

@padilo Indeed, the fact that multi-account is not supported yet causes issues. This has been on our roadmap for some time and should be completed in the next few months. That is paramount for a smooth usage of awless for people with multi-account
I have personally already tried a implementation to store the profile/account info as part of the local data file tree (under ~/.awless/aws/rdf/...). It did not work and scale well. We will give that another go and come up with some other solutions. For instance, we might introduce a awless switch command, etc. If you have any ideas, solutions to solve multi-account let us know.
Anyway, we will close this PR and create an issue (referencing you) about that. For the completion, as for now, you can have your local bash follow the work you did on your PR.

Closing this PR. Now issue referenced in #166