Can't create the image from dockerfile

I am not able to create the image from the dockerfile.
Running
docker build -t external-image .
getting below error.
curl https://raw.githubusercontent.com/golang/dep/master/install.sh | sh
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:--  0:00:19 --:--:--     0curl: (6) Could not resolve host: raw.githubusercontent.com
dep ensure -vendor-only
make: dep: Command not found
Makefile:31: recipe for target 'dep' failed
make: *** [dep] Error 127
The command '/bin/sh -c make dep' returned a non-zero code: 2

could you provide the docker file from which i can build the image.

Your issue here is that you can't resolve raw.githubusercontent.com from the machine where you are running the command. I can guarantee that the Dockerfile works and that the URL is also working.
I'm closing this issue for now, feel free to reopen it in case you have other problems.


Dependency service graph

Status
READY
JIRA Ticket
SPACON-567 & 566
Description
Add service dependency injections, and make service start synchronous
Todos

[ ] Tests
[ ] Documentation
[ ] License

Steps to Test or Reproduce
Outline the steps to test or reproduce the PR here.
git fetch --all
git checkout <feature_branch>
./gradlew connectedCheck

@boundlessgeo/spatial-connect

👍


No errors are reported when a pipeline is not created

Problem

Steps

Put this in a .troy file:

define flow main
flow
  define connector console from stdio
  with
    preprocessors = ["separate"],
    postprocessors = ["separate"],
    codec = "string"
  end;

  define pipeline dumb
  pipeline
    select event from in into out;
  end;

  create connector console from console;

  connect /connector/console/out to /pipeline/dumb/in;
  connect /pipeline/dumb/out to /connector/console/in;
end

run with cargo run -- server run my.troy
Observe lack of error (note the pipeline is defined, but not created).

Possible Solution(s)

Notes
Latest version from main branch.
Output of rustup --version:
Output of rustup show:
Output of tremor --version:

After a bit of investigation: It seems like the flow was not deployed. It would be useful if server run complained if no flows are deployed.


Done..!

Closes: #1
Updated validations.py python script.
Fixed the behavior of validate_user function in validations.py.
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

Fixed the behavior of validation_user function in validations.py

Fixed the behavior of validate_user function in validations.py.


Awesome window manager can't load GTK+3 introspection

Describe the bug
The awesome window manager  cannot load GTK+3 introspection, as is reported in the journal when logging to a awesome session:
Dec 09 20:44:09 romildo xsession[1683]: 2019-12-09 20:44:09 W: awesome: Can't load GTK+3 introspection. Seems like GTK+3 is not installed or `lua-lgi` was built with an incompatible GTK+3 ve

It is also reported by the command awesome --version:
$ awesome --version
awesome 4.3 (Too long)
 • Compiled against Lua 5.2.4 (running with Lua 5.2)
 • D-Bus support: ✔
 • execinfo support: ✔
 • xcb-randr version: 1.6
 • LGI version: [string "return require('lgi.version')"]:1: module 'lgi.version' not found:
	no field package.preload['lgi.version']
	no file '/usr/share/lua/5.2/lgi/version.lua'
	no file '/usr/share/lua/5.2/lgi/version/init.lua'
	no file '/usr/lib/lua/5.2/lgi/version.lua'
	no file '/usr/lib/lua/5.2/lgi/version/init.lua'
	no file './lgi/version.lua'
	no file '/usr/lib/lua/5.2/lgi/version.so'
	no file '/usr/lib/lua/5.2/loadall.so'
	no file './lgi/version.so'
	no file '/usr/lib/lua/5.2/lgi.so'
	no file '/usr/lib/lua/5.2/loadall.so'
	no file './lgi.so'

Metadata

system: "x86_64-linux"
host os: Linux 5.4.1, NixOS, 20.03pre204199.3140fa89c51 (Markhor)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.1
channels(root): "nixos-20.03pre204199.3140fa89c51"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

cc @lovek323 @rasendubi  @ndowens

This looks like an issue with the --version command and not with the package in NixOS, from a quick glance it doesn't look like the flag uses the --search paths? The wrapped package has exec "/nix/store/prkk8z2mclcl527m73ws4g9nc0m9ri0x-awesome-4.3/bin/.awesome-wrapped"  --search /nix/store/ywlwjyd40zviyyjj66azci1wdsxf56v9-luajit-2.1.0-beta3-lgi-0.9.2-1/lib/lua/5.1 --search /nix/store/ywlwjyd40zviyyjj66azci1wdsxf56v9-luajit-2.1.0-beta3-lgi-0.9.2-1/share/lua/5.1 "$@" as the wrapping, and going into the last directory and running awesome --version there gives me the correct output. Have you enabled GTK3 support for Awesome? I have in my configuration and can't see the same error, I just see a bunch of warnings for colors etc. @psychon @Elv13 (sorry to bring you in), is this something that is from the Nix end or AwesomeWM end?

The --version issue looks like a LUA_PATH / LUA_CPATH more than anything. I guess LGI is installed using luarocks? As for the GTK issue itself, is it causing any side effects? AwesomeWM doesn't use GTK+ beside one theme that pulls it to auto-update its color palette.

For the original issue (Can't load GTK+3 introspection):
$ git grep -5 "Can't load GTK+3 intr"                                             master:5
lib/beautiful/gtk.lua-    local _gtk_status, Gtk = pcall(function()
lib/beautiful/gtk.lua-        return require('lgi').Gtk
lib/beautiful/gtk.lua-    end)
lib/beautiful/gtk.lua-    if not _gtk_status or not Gtk then
lib/beautiful/gtk.lua-        gears_debug.print_warning(
lib/beautiful/gtk.lua:            "Can't load GTK+3 introspection. "..
lib/beautiful/gtk.lua-            "Seems like GTK+3 is not installed or `lua-lgi` was built with an incompatible GTK+3 version."
lib/beautiful/gtk.lua-        )
lib/beautiful/gtk.lua-        return nil
lib/beautiful/gtk.lua-    end

So, this is the gtk-theme, which tries to fetch colors from Gtk. On Debian, this depends on the package gir1.2-gtk-3.0. On NixOS... well, you already support it!
https://github.com/NixOS/nixpkgs/blob/6d881472ef7c6a592eda36c2783130dc03c678b9/pkgs/applications/window-managers/awesome/default.nix#L9-L13

from a quick glance it doesn't look like the flag uses the --search paths?

Yup, --version does not use --search... :-/
Quick hack that would add, but is way too much copy&paste:
diff --git a/awesome.c b/awesome.c
index 413b64c90..cbb2d2a36 100644
--- a/awesome.c
+++ b/awesome.c
@@ -622,7 +622,7 @@ main(int argc, char **argv)
         switch(opt)
         {
           case 'v':
-            eprint_version();
+            eprint_version(&searchpath);
             break;
           case 'h':
             exit_help(EXIT_SUCCESS);
diff --git a/common/version.c b/common/version.c
index 00833a952..8eba2ec00 100644
--- a/common/version.c
+++ b/common/version.c
@@ -30,14 +30,81 @@
 #include <lauxlib.h>
 #include <xcb/randr.h> /* for XCB_RANDR_GET_MONITORS */

+/* Add things to the string on top of the stack */
+static void
+add_to_search_path(lua_State *L, string_array_t *searchpath, bool for_lua)
+{
+    if (LUA_TSTRING != lua_type(L, -1))
+    {
+        warn("package.path is not a string");
+        return;
+    }
+
+    foreach(entry, *searchpath)
+    {
+        int components;
+        size_t len = a_strlen(*entry);
+        lua_pushliteral(L, ";");
+        lua_pushlstring(L, *entry, len);
+        if (for_lua)
+            lua_pushliteral(L, "/?.lua");
+        else
+            lua_pushliteral(L, "/?.so");
+        lua_concat(L, 3);
+
+        if (for_lua)
+        {
+            lua_pushliteral(L, ";");
+            lua_pushlstring(L, *entry, len);
+            lua_pushliteral(L, "/?/init.lua");
+            lua_concat(L, 3);
+
+            components = 2;
+        } else {
+            components = 1;
+        }
+        lua_concat(L, components + 1); /* concatenate with string on top of the stack */
+    }
+
+    /* add Lua lib path (/usr/share/awesome/lib by default) */
+    if (for_lua)
+    {
+        lua_pushliteral(L, ";" AWESOME_LUA_LIB_PATH "/?.lua");
+        lua_pushliteral(L, ";" AWESOME_LUA_LIB_PATH "/?/init.lua");
+        lua_concat(L, 3); /* concatenate with thing on top of the stack when we were called */
+    } else {
+        lua_pushliteral(L, ";" AWESOME_LUA_LIB_PATH "/?.so");
+        lua_concat(L, 2); /* concatenate with thing on top of the stack when we were called */
+    }
+}
+
 /** \brief Print version message and quit program.
  * \param executable program name
  */
 void
-eprint_version(void)
+eprint_version(string_array_t *searchpath)
 {
     lua_State *L = luaL_newstate();
     luaL_openlibs(L);
+
+    /* add Lua search paths */
+    lua_getglobal(L, "package");
+    if (LUA_TTABLE != lua_type(L, 1))
+    {
+        warn("package is not a table");
+        abort();
+    }
+
+    lua_getfield(L, 1, "path");
+    add_to_search_path(L, searchpath, true);
+    lua_setfield(L, 1, "path"); /* package.path = "concatenated string" */
+
+    lua_getfield(L, 1, "cpath");
+    add_to_search_path(L, searchpath, false);
+    lua_setfield(L, 1, "cpath"); /* package.cpath = "concatenated string" */
+
+    lua_pop(L, 1); /* pop "package" */
+
     lua_getglobal(L, "_VERSION");
     lua_getglobal(L, "jit");

diff --git a/common/version.h b/common/version.h
index 7bf3bc908..2591a44c8 100644
--- a/common/version.h
+++ b/common/version.h
@@ -22,7 +22,9 @@
 #ifndef AWESOME_COMMON_VERSION_H
 #define AWESOME_COMMON_VERSION_H

-void eprint_version(void) __attribute__ ((noreturn));
+#include "luaa.h" /* yup, this should not be here */
+
+void eprint_version(string_array_t *) __attribute__ ((noreturn));
 const char *awesome_version_string(void);
 const char *awesome_release_string(void);

Feel free to open an issue over at the AwesomeWM repository for this. Alternatively, just patch out the LGI version info from --version in NixOS and replace it by e.g. [not possible on NixOS]. That would be simpler (for me). ;-)

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/awesomewm-luamodules-apparently-not-taking-effect/8507/2


Language pt-BR

brazilian language - pt-Br
close #2

@MarcioPaulo first of all thanks for the PR! Just one quick question. Have you tried using cucumber with language setting pt-BR? I'm just asking, because at least according to Gherkin docs they only support language code pt.

@MarcioPaulo first of all thanks for the PR! Just one quick question. Have you tried using cucumber with language setting pt-BR? I'm just asking, because at least according to Gherkin docs they only support language code pt.

Yes, I changed the JS code on my local machine and it worked.

ex.


Update user guide (as of v1.3)

Tasked myself to update the tag-related functionality part of the UG


Not parsed in Widgets

If writing a youtube link in a widget, the links isn't parsed.

Wow, I missed this by months. That's because it uses the parse.post hook. I don't know if there's a widget hook you can add. In widgets you can use html though, so may be easier to just use the following in your widget.


YouTube: Unable to extract video title

Checklist

[x] I'm reporting a broken site support
[x] I've verified that I'm running youtube-dl version 2019.08.13
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar issues including closed ones

Verbose log
C:\!Others>youtube-dl https://www.youtube.com/watch?v=bdgTa9ni4S8 -e --ignore-config -v
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['https://www.youtube.com/watch?v=bdgTa9ni4S8', '-e', '--ignore-config', '-v']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2019.07.02
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.18362
[debug] exe versions: ffmpeg 4.1.1, ffprobe 4.1.1
[debug] Proxy map: {}
WARNING: Unable to extract video title
[debug] Default format spec: bestvideo+bestaudio/best

Description
I see #21934, but that one is supposed to be fixed (since 08.13 released after it). So I assume it's worth to report it again.

Sorry, I didn't notice that updating Youtube-dl failed..


!level command does not support decimals

level command only displays full numbers
In case of bot rate being 21 and user needs 20 sets !level command will display 0 instead of 0.9 or 1 full
In case of bot rate being 21 and user needs 21 sets !level command will display 1 key
Shod be
In case of bot rate being 21 and user needs 20 sets to reach the level !level command shod display 1 or 0.9
Option to keep full numbers or add decimals shod be included

when will we get this ?
its a very important feature.

when will we get this ?
its a very important feature.

Next update which i will be working on soon, feel free to join our discord server where we post announcements and info about the updates.
Discord
We push updates based on donations and stars activity on the project:
Leave an Star
Donate


Update index.md

correction in new text: from "![NOTE]" to "[!NOTE]"

Docs Build status updates of commit cfaa86c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/operationsmanager/index.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

#sign-off


Usb and car radio

Is possible to connect android on car for playing music through UsbSerial?

Hi @jefferson
If that radio has a Serial interface or a CDC Usb interface it should be possible

Hi @felHR85
Thanks for your answer.
My car has a Usb Interface but I don't know if is "CDC Usb".
I tried something for get wich protocol my car use but dont's works to.
Is it possible to test to see what protocol my car uses?

Steps I would follow:

Check information about that particular radio to know more info.
Connect the radio to your PC and using PuTTY monitor what is happening.
Maybe it uses the CAN protocol (used a lot in automotive industry) but it's hard to say

Thank, I'll test the steps.
I think the car should use Mass Storage class (MSC device)  to fetch the files and play.


Missing check for signature algorithms

Have not yet been able to implement the signature algorithm fetching method (src1, src2)
See: https://github.com/O-X-L/haproxy-ja4/blob/latest/ja4.lua#L163
Not sure if this is currently possible. See: source code

There's a dev branch where ssl_fc_sigalgs_bin has been made available. I tested it already and the result looks good
local function signature_algorithms(txn)
    local algos = txn.c:be2hex(txn.f:ssl_fc_sigalgs_bin(), '-', 2)
    return algos
end

results in  0403-0804-0401-0503-08. Those values match the ones from RFC8446.

Nice :D


Perl syntax breaks while using underscore in function name and @_

VSCode Version: 1.39.2
OS Version: Fedora 20

Steps to Reproduce:

Have a perl function that has an underscore in its name. Example: s_expand()
Pass @_ as parameter. s_expand(@_)
The syntax is broken until another character breaks the highlight, for instance, another underscore.

sub myExample()
{
  s_expand(@_);
}

sub fixHighlight()
{
  #perl comment_
}

Does this issue occur when all extensions are disabled?: Yes/No
Yes

Moved to owning repo: https://github.com/textmate/perl.tmbundle/issues/40


Add query management to DownloadsController#new

Coverage: 93.524% (+0.0005%) from 93.524% when pulling 5b5c4f46e580485de52bab2c229e0c27c175ab02 on fix-report-query-passing into e45a3b9b0a31c551aeee567b482942a25232b211 on main.


WIP: examples folder refactoring

name: :book: New/Updated Documentation Content
about: Adding a new docs page, or updating content in an existing docs page
PR Type
Does this PR add a new page, or update an existing page?
Not yet
Checklist

[x] Is there an existing issue for this PR?

#3917

[x] Have the files been linted and formatted?
yes

What docs page is being added or updated?

Section: Introduction
Page: Examples

For Updating Existing Content
What updates should be made to the page?
Linking updated redux examples
Do these updates change any of the assumptions or target audience? If so, how do they change?

First observation: since there may be external links that still point to those folders, can we replace the dead examples with small README.md files that have specific suggestions on what other examples to look at instead? ie, examples/todomvc/README.md might say "Go look at the new Redux Fundamentals example todo app -> here".

@markerikson wait wait, I did nothing else but removing the folders we said to remove and replacing counter with "npx create-react-app --template=redux"

I'm fine with the one PR - just saying that +12.2K -66K is a pretty big diff :)

YOLO 😄

Please don't switch to Yarn. We use npm for this repo.

@timdorr good catch, I missed that.
Although I think I may have used Yarn for the "Essentials" tutorial repo?  At least the README file ended up saying yarn build, etc, although I didn't include a lockfile in there.

I don't really care much about the tooling in other repos. It's just we should use one package manager per repo, so that tooling usage will be consistent. And so the install scripts for the examples have the right lock file format available (even though npm 7 can read yarn.lock now)

Let me know if I can improve this pr anytime :)
Just ping!

we've got a solution for such PRs like this. Just check it out here: https://viezly.com/change_requests/4135. Guess that way it'd be possible to review such refactoring.


HDDS-10103. Simplified snapshotCache by using single reentrant lock instead multiple locks

What changes were proposed in this pull request?
Currently we use different locks to provide consistent view of the snapshot cache. Which are causing multiple problem e.g. deadlock, race condition.
In this change, a reentrant lock is used to achieve the synchronization which give the consistency view of the cache. And Guava's Striped is used to distribute the lock so that multiple thread can access the cache at the same time.
What is the link to the Apache JIRA
HDDS-10103
How was this patch tested?
Existing unit and integration tests.

Thanks for fixing this @hemantk-12. There can still be a case where this can result in a deadlock. For example,
At timet0 Thread 1 -> Acquires lock for snap1
At timet0 Thread 2 -> Acquires lock for snap2
Now both the threads are doing the cleanup(), We may end up in a scenario.
At time t1 Thread 1 -> Waiting for lock snap2
At time t1 Thread 2 -> Waiting for lock snap1
Let me know if this is possible.

There can still be a case where this can result in a deadlock. For example, At timet0 Thread 1 -> Acquires lock for snap1 At timet0 Thread 2 -> Acquires lock for snap2
Now both the threads are doing the cleanup(), We may end up in a scenario. At time t1 Thread 1 -> Waiting for lock snap2 At time t1 Thread 2 -> Waiting for lock snap1

Currently cleanup is synchronized at class level and should prevent this. Only one thread will be doing clean up at a time.
I think we can move cleanup here out of the lock.

Even with synchronized, we can still hit this scenario.
Thread 1(holding snap1 lock) -> waiting to get lock synchronized method
Thread 2(holding snap2 lock) -> doing cleanup() waiting for snap1 lock

@aswinshakil actually you are right (Good catch), even after the synchronized cleanup, it is possible the thread is waiting for the lock which is acquired by another thread.
For example,
At timet0 Thread 1 -> Acquires lock for snap1
At timet0 Thread 2 -> Acquires lock for snap2
Now thread one acquires the cleanup() lock and starts the clean up, but it will stuff for snap2 lock because it has not been released so far.
At time t1 Thread 1 -> Waiting for lock snap2
Moving out cleanup in get function out of the lock should fix it.
After the change,
At timet0 Thread 1 -> Acquires lock for snap1 -> does dbMap#getOrCompute() -> release the lock
At timet0 Thread 2 -> Acquires lock for snap2 -> does dbMap#getOrCompute() -> release the lock
One of the thread will acquire the cleanup lock because it is synchronized. Let's say, Thread 1 gets it.
At time t1 Thread 1 -> acquire the cleanup lock -> acquire snap1 (and other keys sequentially) lock -> remove the entry if possible -> release snap1 lock -> release clean up lock.

LGTM + 1. It would be great if someone else also took a look at it. Thanks @hemantk-12 for working on this.

Closing the pull request in favour of https://github.com/apache/ozone/pull/5986


adding a functionality to add classes on deleted and added text and elements in the document

Hello,
I have added the functionality for add custom css classes on added and removed text and elements into a document. Please review the code and accept the pull request.
Thanks

I like this idea, but I think the DocumentDiffViewer class needs configuration options or callbacks, so users can set their own CSS classes.

Going to close this, no offense. I think this should be a separate library or tool. Also, I could see others wanting a visual-diff, similar to how GitHub displays diffs of code, where the XML/HTML is displayed raw with a red or green background color.


Allow users to edit completed workflow's parameters before rerunning

Sometimes users want to change one or two parameters and run again. Currently, we can rerun a workflow but can't edit it before execution. I can think of two possible solutions:
1- Show parameters and allow editing (similar to Execute workflow popup) when the user clicks on Rerun. The default parameters should be same as the ones in completed workflow. Then, users can change whatever parameters they want to change and rerun.
2 - Another way is to have two options in a menu- Rerun and Edit and Rerun. Rerun's behavior will be the same. But Edit and Rerun will be just like (1).

I think we should go with #1 but also allow them to select another template version as well.


Local .continueignores

Validations

[X] I believe this is a way to improve. I'll try to join the Continue Discord for questions
[x] I'm not able to find an open issue that requests the same enhancement

Problem
I have a mono-repo structured as each folder is a micro service. I'd like to have .continueignore file per folder (similar to how .gitignore works).
Solution
Scan project for all .continueignore files, build an aggregated internal model of the merged .continueignores using each location as a prefix, then use that to apply to the codebase from the root.

I believe it already works this way. Are we talking about .continueignore for indexing?

Both. I guess I missed that in the docs or it isn't documented.

Linking to the docs here. We'll also be making it more prominent as we do a rewrite soon.


lxd 3.20 daemon fails to fully start

Required information

Distribution: Alpine Linux
Distribution version: 3.11 / lxd packages from edge-testing
The output of "lxc info" or if that fails:

Kernel version: 5.4.12-1-lts
LXC version: 3.20
LXD version: 3.20
Storage backend in use: zfs

Issue description
The lxd daemon does not fully start; the logfile is not written to and socket does not exist for lxc to communicate with lxd.  The issue appears to be related to the feature check process.  Killing the lxd child process started by the main lxd process resumes the daemon startup, writes the buffered messages to the logfile, and creates the socket for lxc communication.
Steps to reproduce

start the lxd service
'lxc info' output: Error: Get http://unix.socket/1.0: dial unix /var/lib/lxd/unix.socket: connect: no such file or directory
logfile specified via command line does not have any entries from the startup
kill lxd child
lxc commands work as expected and log file has new entries

log output
lxd.log:
t=2020-02-04T00:45:15+0000 lvl=info msg="LXD 3.20 is starting in normal mode" path=/var/lib/lxd
t=2020-02-04T00:45:15+0000 lvl=info msg="Kernel uid/gid map:"
t=2020-02-04T00:45:15+0000 lvl=info msg=" - u 0 0<PHONE_NUMBER>"
t=2020-02-04T00:45:15+0000 lvl=info msg=" - g 0 0<PHONE_NUMBER>"
t=2020-02-04T00:45:15+0000 lvl=info msg="Configured LXD uid/gid map:"
t=2020-02-04T00:45:15+0000 lvl=info msg=" - u 0<PHONE_NUMBER>6"
t=2020-02-04T00:45:15+0000 lvl=info msg=" - g 0<PHONE_NUMBER>6"
t=2020-02-04T00:45:15+0000 lvl=warn msg="AppArmor support has been disabled because of lack of kernel support"
t=2020-02-04T00:45:15+0000 lvl=info msg="Kernel features:"
t=2020-02-04T00:45:15+0000 lvl=info msg=" - netnsid-based network retrieval: yes"
t=2020-02-04T00:45:15+0000 lvl=info msg=" - uevent injection: yes"
t=2020-02-04T00:45:15+0000 lvl=info msg=" - seccomp listener: yes"
t=2020-02-04T00:45:15+0000 lvl=info msg=" - seccomp listener continue syscalls: no"
t=2020-02-04T00:45:15+0000 lvl=info msg=" - unprivileged file capabilities: yes"
t=2020-02-04T00:45:15+0000 lvl=info msg=" - cgroup layout: hybrid"
t=2020-02-04T00:45:15+0000 lvl=warn msg=" - Couldn't find the CGroup blkio.weight, I/O weight limits will be ignored"
t=2020-02-04T00:45:15+0000 lvl=warn msg=" - Couldn't find the CGroup memory swap accounting, swap limits will be ignored"
t=2020-02-04T00:45:15+0000 lvl=info msg=" - shiftfs support: no"
t=2020-02-04T00:45:15+0000 lvl=info msg="Initializing local database"
t=2020-02-04T00:45:15+0000 lvl=dbug msg="Initializing database gateway"
t=2020-02-04T00:45:15+0000 lvl=dbug msg="Start database node" address= id=1 role=voter
t=2020-02-04T00:45:15+0000 lvl=info msg="Starting /dev/lxd handler:"
t=2020-02-04T00:45:15+0000 lvl=info msg=" - binding devlxd socket" socket=/var/lib/lxd/devlxd/sock
t=2020-02-04T00:45:15+0000 lvl=info msg="REST API daemon:"
t=2020-02-04T00:45:15+0000 lvl=info msg=" - binding Unix socket" socket=/var/lib/lxd/unix.socket

lxd child strace at time of hang:
gettid()                                = 27910
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
seccomp(SECCOMP_SET_MODE_FILTER, SECCOMP_FILTER_FLAG_NEW_LISTENER, {len=4, filter=0x7ffd2a8205a0}) = 5
rt_sigprocmask(SIG_BLOCK, ~[], [], 8)   = 0
fork()                                  = 27911
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
poll([{fd=5, events=POLLIN|POLLOUT}], 1, 5000) = 1 ([{fd=5, revents=POLLIN}])
ioctl(5, SECCOMP_IOCTL_NOTIF_RECV, 0x7ffd2a820620) = 0
poll([{fd=5, events=POLLIN|POLLOUT}], 1, 5000) = 1 ([{fd=5, revents=POLLOUT}])
ioctl(5, SECCOMP_IOCTL_NOTIF_SEND, 0x7ffd2a820600) = -1 EINVAL (Invalid argument)
ioctl(5, SECCOMP_IOCTL_NOTIF_SEND, 0x7ffd2a820600) = 0
kill(27911, SIGKILL)                    = 0
wait4(27911, [{WIFSIGNALED(s) && WTERMSIG(s) == SIGKILL}], 0, NULL) = 27911
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_KILLED, si_pid=27911, si_uid=0, si_status=SIGKILL, si_utime=0, si_stime=0} ---
futex(0x7ffd2a820444, FUTEX_WAIT_PRIVATE, 2, NULL

lxd child fork strace at time of hang:
gettid()                                = 27911
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
pipe([6, 7])                            = 0
dup(6)                                  = -1 EPERM (Operation not permitted)
+++ killed by SIGKILL +++

@brauner please take a look at this.
@atersurs could you start LXD entirely under strace (strace -fF lxd --debug), then do the same trick of killing the subprocess until LXD works and then close the daemon and strace?
That would give us a more complete trace.

strace -fF -o /tmp/lxc lxd --debug -v --logfile /var/log/lxd/lxd.log

lxd output to terminal:
strace: deprecated option -F ignored
INFO[02-05|03:36:53] LXD 3.20 is starting in normal mode      path=/var/lib/lxd
INFO[02-05|03:36:53] Kernel uid/gid map:
INFO[02-05|03:36:53]  - u 0 0<PHONE_NUMBER>
INFO[02-05|03:36:53]  - g 0 0<PHONE_NUMBER>
INFO[02-05|03:36:53] Configured LXD uid/gid map:
INFO[02-05|03:36:53]  - u 0<PHONE_NUMBER>6
INFO[02-05|03:36:53]  - g 0<PHONE_NUMBER>6
WARN[02-05|03:36:53] AppArmor support has been disabled because of lack of kernel support
INFO[02-05|03:36:53] Kernel features:
INFO[02-05|03:36:53]  - netnsid-based network retrieval: yes
INFO[02-05|03:36:53]  - uevent injection: yes
INFO[02-05|03:36:53]  - seccomp listener: yes
INFO[02-05|03:36:53]  - seccomp listener continue syscalls: no
INFO[02-05|03:36:53]  - unprivileged file capabilities: yes
INFO[02-05|03:36:53]  - cgroup layout: hybrid
WARN[02-05|03:36:53]  - Couldn't find the CGroup blkio.weight, I/O weight limits will be ignored
WARN[02-05|03:36:53]  - Couldn't find the CGroup memory swap accounting, swap limits will be ignored
INFO[02-05|03:36:53]  - shiftfs support: no
INFO[02-05|03:36:53] Initializing local database
DBUG[02-05|03:36:53] Initializing database gateway
DBUG[02-05|03:36:53] Start database node                      id=1 address= role=voter
INFO[02-05|03:36:57] Starting /dev/lxd handler:
INFO[02-05|03:36:57]  - binding devlxd socket                 socket=/var/lib/lxd/devlxd/sock
INFO[02-05|03:36:57] REST API daemon:
INFO[02-05|03:36:57]  - binding Unix socket                   socket=/var/lib/lxd/unix.socket
INFO[02-05|03:36:57] Initializing global database
DBUG[02-05|03:36:57] Dqlite: connected address=1 id=1 attempt=0
INFO[02-05|03:36:57] Initializing storage pools
DBUG[02-05|03:36:57] Initializing and checking storage pool "default"
DBUG[02-05|03:36:57] Mount started                            driver=zfs pool=default
DBUG[02-05|03:36:57] Mount finished                           driver=zfs pool=default
INFO[02-05|03:36:57] Initializing networks
DBUG[02-05|03:36:57] New task Operation: 6d641fc4-c922-4286-9298-765a4beedf6d
INFO[02-05|03:36:57] Pruning leftover image files
DBUG[02-05|03:36:57] Started task operation: 6d641fc4-c922-4286-9298-765a4beedf6d
DBUG[02-05|03:36:57] Success for task operation: 6d641fc4-c922-4286-9298-765a4beedf6d
INFO[02-05|03:36:57] Done pruning leftover image files
INFO[02-05|03:36:57] Loading daemon configuration
DBUG[02-05|03:36:57] Initialized inotify with file descriptor 22
INFO[02-05|03:36:57] Started seccomp handler                  path=/var/lib/lxd/seccomp.socket
DBUG[02-05|03:36:57] New task Operation: 643a582d-a367-4970-bdee-22b2e4f54acd
INFO[02-05|03:36:57] Pruning expired images
DBUG[02-05|03:36:57] Started task operation: 643a582d-a367-4970-bdee-22b2e4f54acd
INFO[02-05|03:36:57] Done pruning expired images
DBUG[02-05|03:36:57] Success for task operation: 643a582d-a367-4970-bdee-22b2e4f54acd
DBUG[02-05|03:36:57] New task Operation: dfac949e-7192-4268-afc5-ad7dbb039085
INFO[02-05|03:36:57] Pruning expired container backups
DBUG[02-05|03:36:57] Started task operation: dfac949e-7192-4268-afc5-ad7dbb039085
DBUG[02-05|03:36:57] Success for task operation: dfac949e-7192-4268-afc5-ad7dbb039085
INFO[02-05|03:36:57] Done pruning expired container backups
DBUG[02-05|03:36:57] New task Operation: ddcf235b-2720-4f1a-82e9-472ff29c890a
INFO[02-05|03:36:57] Updating instance types
DBUG[02-05|03:36:57] Started task operation: ddcf235b-2720-4f1a-82e9-472ff29c890a
DBUG[02-05|03:36:57] New task Operation: 748c4cfd-e522-4f62-ac2e-1260a5fb1603
INFO[02-05|03:36:57] Done updating instance types
INFO[02-05|03:36:57] Expiring log files
DBUG[02-05|03:36:57] Started task operation: 748c4cfd-e522-4f62-ac2e-1260a5fb1603
INFO[02-05|03:36:57] Done expiring log files
DBUG[02-05|03:36:57] Success for task operation: 748c4cfd-e522-4f62-ac2e-1260a5fb1603
DBUG[02-05|03:36:59] Success for task operation: ddcf235b-2720-4f1a-82e9-472ff29c890a
INFO[02-05|03:37:06] Received 'interrupt signal', exiting
INFO[02-05|03:37:06] Starting shutdown sequence
INFO[02-05|03:37:06] Stopping REST API handler:
INFO[02-05|03:37:06]  - closing socket                        socket=/var/lib/lxd/unix.socket
INFO[02-05|03:37:06] Stopping /dev/lxd handler:
INFO[02-05|03:37:06]  - closing socket                        socket=/var/lib/lxd/devlxd/sock
INFO[02-05|03:37:06] Closing the database
DBUG[02-05|03:37:06] Stop database gateway
DBUG[02-05|03:37:07] Not unmounting temporary filesystems (containers are still running)

strace log:
lxc-strace.log

According to the last strace the checkfeature stuff runs just fine and finishes in order.

Ah, you sent SIGTERM to the checkfeature process?

This smells like a container or compiler bug since this is hanging in futex_wait(). Can you try to reproduce on a new kernel, please?

Never mind the kernel this very much looks like musl is doing something strange with futexes here. This is only reproducible on Alpine afaict. I can harden this code a little more but overall this seems to not be a bug in lxd.

@atersurs once https://github.com/lxc/lxd/pull/6841 is merged, can you see whether this fixes things for you?

@brauner the changes in that pull fix the problem for me; thank you.

This is so weird but ok.


Improve 'any' search message during uv python install

Special cases the Any request in output
e.g.,
❯ cargo run -q -- python install --isolated
warning: `uv python install` is experimental and may change without warning.
Searching for Python installations
Found existing installation: cpython-3.12.3-macos-aarch64-none
Python is already available. Use `uv python install <request>` to install a specific version.

instead of
❯ cargo run -q -- python install --isolated
warning: `uv python install` is experimental and may change without warning.
Searching for Python versions matching: any Python
Found existing installation for any Python: cpython-3.12.3-macos-aarch64-none
Python is already available. Use `uv python install <request>` to install a specific version.

Loosely considering keeping the existing messages when --verbose is used.


Update OutlineButton default border width and highlight elevation

Fixes https://github.com/flutter/flutter/issues/22778.
An earlier version of these changes was contributed by @sir-boformer in https://github.com/flutter/flutter/pull/22781

The default highlightElevation, the size of the shadow when the button is pressed, is now 0.0 (was 2.0).
The default borderSide.borderWidth, the width of the button's outline, is now 1.0 (was 2.0).
The default border's color when the button is enabled is the color scheme's "onSurface" color with 12% opacity. By default, that's Colors.white12 for dark themes and Colors.black12 for light. The border color no longer changes when the button is pressed unless highlightedBorderColor is specified. Previously the border color was an opaque shade of grey.
If highlightElevation is 0.0 (the default) then the highlight color is transparent. The highlight color is the background color of the button when it is pressed,
If highlightElevation is > 0.0 then, when pressed, the button is filled with the theme's canvas color before animating the underlying material's elevation to highlightElevation. This is the original behavior and 2.0 is the original highlightElevation.

These changes are backwards incompatible. Tests that verify OutlineButton visuals, for example golden image tests, will need to be updated.
This screenshot shows the original appearance of OutlineButtons in various configurations:

This screenshot shows the same buttons with the changes described here:

uh, I guess I was a few seconds too late. Sadly you forgot to add a materialTapTargetSize property. That was a part of my original PR.

Hi, does OutlineButton have 'materialTapTargetSize' property?
I don't see it in the constructor but I see this pull request already merged. Thanks

Hi, does OutlineButton have 'materialTapTargetSize' property?
I don't see it in the constructor but I see this pull request already merged. Thanks

I noticed this too while working with OutlineButton today. Looks like this is still an issue.


documentation: security best practices for volumes

To prevent code inside a container from creating objects that could be potential security holes on the host.
Might also show a warning if a container is started and the filesystem used to mount a volume does not have those options ("the filesystem used allows device, executable and suid files to be created, please consider using a separate filesystem with nodev,noexec,nosuid options").

Context: the discussion started from this blog post and on the rkt-dev mailing list.
As far as I understand the scenario in the blog post, the command ./sh to become root (and the following whoami) are executed on the host, and not in the Docker container. So in order to block the scenario described above, the options nosuid would need to be set up on the host mountpoints, rather than on the mountpoints in the container's mount namespace. That's not up to Docker or rkt to decide the mount options on the host. And noexec cannot be used on "/" on the host.
The nosuid option does not block the creation of files with the suid bit, but rather ignore the bit when the file is executed. Similarly, nodev does not restrict the ability to create device nodes, but rather block access to them.
So I don't think it is necessary to change the mount options in the rkt mount namespace. (And it would not help)
I like your idea of a warning.
I suggest we also keep this issue open until the security implications of bind mounting a volume from the host to the pod are properly documented. Security best practices in rkt/Documentation/security.md?

Use volumes with "readOnly=true" when write access is not necessary
When write access is necessary, advise to only share directories that are on a
filesystem mounted with the options nosetuid, nodev.

That makes sense. Thanks a lot @alban!

Updated title to capture proposal.

Mounting with nosuid still allows to create setuid binaries, it is just the setuid bit would have no effect. That leaves a possibility of doing cp -a or similar to transfer setuid binary to another location. This is probably insignificant threat, but still emphasizing in the documentation about avoiding root for processes in the containers would be nice.

More ideas for security best practices for volumes:

it is better if the volume being shared is a full filesystem rather than just a directory in a filesystem (a mounted partition or some file mounted with mount -o loop)
avoid sharing directories when tools on the host can move files outside the directory (such as Nautilus moving directories to the wastebasket ~/.local/share/Trash when the user deletes it)

See:
https://github.com/docker/docker/issues/12317


Building Backend Applications using Astra DB

We ask that you please be patient as our team works through approving and publishing all articles/tutorials in a timely manner. Allow 1-3 days for a topic to be reviewed and/or approved - allow 3-7 days for an articles to be reviewed and/or published.
Be sure to visit our Resources Page for tools, resources, and example articles to go over.
NOTE: (Please ensure that you have only one open issue + linked pull request at a time. This will ensure that we complete the article in a timely manner from inception to publishing.)
NOTE: We tend to stray away or tend not to publish reviews/comparisons of commercial product offerings.
We're looking for the first 2-3 paragraphs of the article that appropriately summarize what your article will be about.
Proposed title of the article
Building Backend Applications using Astra DB
Introduction paragraph (2-3 paragraphs):
Astra DB is a Multi-cloud DBaaS built on Apache Cassandra. Normally, cloud-native Cassandra application development is complicated. Astra DB simplifies this by reducing deployment time to deliver an unprecedented combination of serverless, pay-as-you-go pricing with the freedom and agility of multi-cloud and open source.
This database runs on Apache Cassandra, which uses the Cassandra Query Language (CQL) to create tables which is similar to SQL. The main difference is that Apache Cassandra databases are non-relational, so they use different concepts to store and retrieve data.
Key takeaways:

An introduction to distributed, wide-column store, NoSQL database management system such as Apache Cassandra.
Features that Astra DB offers such as Serverless, Stargate APIs that work natively with Document (JSON), REST, and GraphQL APIs, Scalability, Security, and more.
3.Creating a DataStax Astra database, generating tables, inserting some data, and how to retrieve data.
Use React and Nodejs to build an application

References:
Please list links to any published content/research that you intend to use to support/guide this article.
Templates to use as guides

How To Guide Template
Software Review Template
Tutorial Template

Hi @Qodestackr
This sounds like an informative tutorial. Please make sure it does not conflict with content already available on section and that it has more original content. Otherwise, topic approved.
:rocketP:

To help avoid a backlog queue (and longer review times) we are currently only accepting ONE article TOPIC/PR approved at a time 👍. We can re-open this topic - once the 1st one has been merged/published.


[RIP-9] Add the introduction of the Operations_Producer in RocketMQ

What is the purpose of the change
Add description section for the Operations_Producer to RocketMQ Develop Guide:
Brief changelog

Add description section for Operations_Producer to English RocketMQ Develop Guide

Verifying this change
Browse the section 1 in the best_practice.md
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage increased (+0.09%) to 44.911% when pulling 8dfd0384f1845f083df60974cf29ee17a9d97d18 on frayds:develop into 6a573a773a87edbcdcc138614b756019fc280988 on apache:develop.

@frayds Could you please check these suggestions again?


Typescript: Add class & className to SVGAttributes

There are many SVG attributes missing, but I think class should be considered essential - especially as its absence breaks the TS compilation.

Coverage remained the same at 97.695% when pulling 39e39ca48c45362e14ca7e42442274b7f376f8b7 on shakyShane:master into 861439623d77c1f2cc69371c071c88fca7290d9b on developit:master.

Thank-you for the contribution and I'm sorry it took such a long time to review. In the meantime another PR (#609) was submitted which added extensive SVG attributes to the type definitions, including class and className by extending HTMLAttributes.

Perfect!
On Sun, 2 Apr 2017 at 20:13, Robert Knight<EMAIL_ADDRESS>wrote:

Closed #542 https://github.com/developit/preact/pull/542.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/developit/preact/pull/542#event-1025611735, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABkUAuL94yVGSSk4usERZzCsTufkEkJdks5rr_NhgaJpZM4L8QKW
.


Install apt packages before pip packages

Moves apt installs to just below the initial FROM line
This prevents pip packages not installing due to depending on these apt packages

Fixes: https://github.com/replicate/cog/issues/1949

Thanks, @8W9aG.
I love this improvement. I don't love what's needed to get there. (And I'm sure you're also not super jazzed about pipInstallStage take aptInstalls as an argument).
How we generate Dockerfiles is long overdue for a rethink. I don't believe we have the appetite to pick that up anytime soon, so I'm fine to hold my nose on this one.

In this case if we removed the separate weights stuff I think we could come up with a very decent dockerfile generator which was more declarative than procedural.


Incompatible with new 64-bit game clients (STO)

Since Star Trek online updated to a 64 bit client awhile ago, this toolset doesn't appear to work with STO.

Having same issues. Was hoping to develop client side model swapping for various ground weapons to remove those atrocious holograms on weapons. This and the extractor seem to no longer function.

@Jff007 By extractor do you mean Unpack? because I haven't seen any issue with that on my end.

Yeah, the unpacker worked for the first set of files I tried. But then I tried to unpack again, and nothing happened. I even redownloaded, used a different directory, and rebooted just to be sure.

@Jff007 If you can figure out what's happening there, please open a new issue since that's separate from the 64-bit support.

Noted, I'll try a couple of other Windows machines tomorrow to see if I can replicate it. If not, I'll edit this comment sometime before the next 24 hours.

@Jff007 No worries, suggesting that since this issue will be closed momentarily.


query with array of arributes, values

Is if possible to query with a array off arributes, values and comparison operators?
This is what Im kinda searching for

var params = [
{attribute:firstname, value:"liz", compareOperator:"$contains"}
{attribute:Lastname, value:"Op", compareOperator:"$contains"}
{attribute:Born, value:"01.02.2015", compareOperator:"$gte"}
{attribute:Age, value:50, compareOperator:"$lte"}
}

mySuperCollection.find('$and' :params)

And how do I make a find in-casesensitive?
So "liz" and "Liz" is the same..

You can either :

use nested queries
query chaining
collection transforms

nested query might look like :
var results = coll.find({
  '$and': [{
      'Age' : {
        '$gt': 30
      }
    },{
      'Name' : 'Thor'
    }]
});

collection transform might look like :
var tx = [
  {
    type: 'find',
    value: {
      'owner': someOwner
    }
  }
];

or chained queries which just run them in sequence
case insensitive find probably need $regex op.
https://github.com/techfort/LokiJS/wiki/Query-Examples
https://github.com/techfort/LokiJS/wiki/Collection-Transforms

Thank you for the fast reply
Would have been great if there was a option you could pass into the query where it did lowercase to all database string attribute values, so during my query I could just transform my values to lowercase before passing it to the query if I wanted to.


fix: install does not include dev-deps

Also, switches to using fork, as this provides improved start-up time
when the child process is node, and use a dependency-provided npm@7
instead of installing one on each execution.

@RomainMuller is this pr still relevant?

@RomainMuller Abandon?

Looks like this auto-closed when I renamed the default branch from master to main. Feel free to re-open this or create a new PR.


Question: Configuring install.sh to see prereqs

Question
Question: Configuring install.sh to see prereqs

OpenCoarrays Version: 2.0.0
Fortran Compiler: GNU Fortran Ubuntu 5.5.0-12ubuntu1~16.04 comes up with gfortran --version, but I do have GNU Fortran (Ubuntu 7.3.0-16ubuntu3~16.04.1) installed.
C compiler used for building lib: same deal. gcc (Ubuntu 5.5.0-12ubuntu1~16.04) comes up when I type gcc -version, but I have gcc-7 (Ubuntu 7.3.0-16ubuntu3~16.04.1) installed.
Installation method: "bash install.sh"
Output of uname -a: "Linux NukeBox 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
MPI library being used: I don't think I got to using the MPI library. The install script isn't seeing what I have installed--I have MPICH 3.2.
Machine architecture and number of physical cores: 64-bit, 4 cores, but it's a VM.
Version of CMake: 3.5.1

Observed Behavior
After downloading prerequisites that I have installed on my system, install.sh crashed out trying to compile gcc-7.3.0, it appears. The output is attached. I should note that I am new to playing with compilers, so my mistake is probably silly and easily corrected, but I need some help understanding what that is. How would I configure the install.sh script to see my installed prerequisites?
Expected Behavior
Completing the install, and recognizing the preinstalled prerequisites. I do expect, however, to have to point the install script to my install of MPICH 3.2, but I'm not sure how.
Steps to Reproduce
Type the following into your terminal:
sudo apt-get install aptitude
sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt-get update
sudo aptitude install gcc-7 g++-7 gfortran-7
cd ~/Codes/src
git clone https://github.com/sourceryinstitute/OpenCoarrays.git
cd OpenCoarrays
bash install.sh

After it gets to installing gcc-7, it will crash out like this.
OUTPUT after error is attaches (it was longer than expected).
Compile Error.txt

See example 3 in the Example script invocations in the INSTALL.md file.  In addition, I recommend adding the --disable-bootstrap or equivalently the -z argument to speed up the build process considerably (but try again without these arguments if the build fails.  Also, I recommend speeding things up further with a parallel build.  For example, on a system with 4 cores, use --num-threads 4 or equivalently -j 4.  So please try something like the following:
./install.sh
   --with-fortran <path-to-gcc-bin>/gfortran \
   --with-cxx <path-to-gcc-bin>/g++ \
   --with-c <path-to-gcc-bin>/gcc \
   --disable-bootstrap \
   --num-threads 4 \
   --install-prefix <path-to-desired-opencoarrays-location>

where <path-go-gcc-bin>\ may be ommitted if the desired gcc/g++/gfortran are at the front of your $PATH.

@jordana309 If you already have gcc-7, g++-7 and gfortran-7 installed at the front of your path then just specify them to install.sh
Confirm that GCC-7 compilers are on your path:
which gcc-7
which g++-7
which gfortran-7

Each command should print the location of the compiler.
Next, try:
./install.sh \
   --with-fortran "`which gfortran-7`"
   --with-cxx "`which g++-7`"
   --with-c "`which gcc-7`"
   -j 4
   --install-prefix "/path/to/install/OpenCoarrays/into"

If you have CMake and MPI installed too, you might just want to install directly with CMake.

I got Fortran to install by running the following line (I had to manually put in all my paths, and specifically install mpich for some reason:
bash install.sh --with-fortran "/usr/bin/gfortran-7" --with-cxx "/usr/bin/g++-7" --with-c "/usr/bin/gcc-7" --disable-bootstrap --num-threads 4 --package mpich --install-prefix "home/jordan/Codes/"
Thank you for your help. Then, I installed the Jupyter CAF kernel, and when I ran the kernel in jupyter, it connected fine. However, when trying to run a simple hello world program to make sure it works, I got the following error:
  File "/home/jordan/Codes/Anaconda/lib/python3.6/subprocess.py", line 1344, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'caf': 'caf'

Is that likely a kernel problem, or a Coarrays Fortran problem? I'm not sure how to overcome it, because the actual kernelspec file looks fine from what I can tell.
Thank you!

hmmmm I'm not sure. Jupyter CAF kernel has been neglected for a few months. If you type which caf does it show you where you installed OpenCoarrays? If you set the --install-prefix to something that is not on your PATH by default you will have to make sure it gets added, probably somewhere in your "dot files". I'm not 100% sure how python & Jupyter handle the user's PATH in the context of Jupyter kernels.

which caf returns nothing, and when I tried to add the  from my --install-prefix, it still can't find it. I tried doing the bin folder in that directory, but no dice. I tried to point to the caf kernel and several folders in there, but it didn't like any of them (and I did remember to close all my terminals and reopen them between tests). What is 'caf' supposed to be pointing to? MPICH? the CAF kernel?

Yes, there is a default of two coarray images. You can use some magic to control compilation and number of images. Let's close this issue and open one on Jupyter-CAF-kernel to continue discussion there.

See, e.g., https://github.com/sourceryinstitute/jupyter-CAF-kernel/blob/master/index.ipynb. This should load as a non-interactive example notebook. You can see in the first input cell two "magics" one to say how many images to use %num_images: 1 and one to allow longer input lines: %fc_flags: -ffree-line-length-none. It looks like GH is having trouble rendering the entire document for me, so you can also look at it here: https://nbviewer.jupyter.org/github/sourceryinstitute/jupyter-CAF-kernel/blob/master/index.ipynb

Shall we close the issue?


Pass time.Duration to client init, instead of int

This avoids the confusion of having both int and time.Duration as
possible arguments, and the complication of adding a config object if we
were to do that.
Related to #6

Thanks for this @kgrz, merging


Update README.md

the full path is "cd fabric-samples/commercial-paper/organization/magentocorp
./magnetocorp.sh"      miss organization

Please follow instructions here to sign your commit

Once change #138 is merged you'll need to do a rebase on the master branch to fix this issue.

#138 was merged, please rebase on the tip of master

@lehors change made


Test: terminal location API

Refs #45407

[x] macOS @weinand
[ ] linux @TylerLeonhardt
[x] windows @stevencl

Complexity: 3
Authors: @meganrogge, @tyriar
Create Issue

With proposed API enabled, use the extension-terminal-sample to test the following:

	export interface TerminalOptions {
		location?: TerminalLocation | TerminalEditorLocationOptions | TerminalSplitLocationOptions;
	}

	export interface ExtensionTerminalOptions {
		location?: TerminalLocation | TerminalEditorLocationOptions | TerminalSplitLocationOptions;
	}

	export enum TerminalLocation {
		Panel = 0,
		Editor = 1,
	}

	export interface TerminalEditorLocationOptions {
		/**
		 * A view column in which the {@link Terminal terminal} should be shown in the editor area.
		 * Use {@link ViewColumn.Active active} to open in the active editor group, other values are
		 * adjusted to be `Min(column, columnCount + 1)`, the
		 * {@link ViewColumn.Active active}-column is not adjusted. Use
		 * {@linkcode ViewColumn.Beside} to open the editor to the side of the currently active one.
		 */
		viewColumn: ViewColumn;
		/**
		 * An optional flag that when `true` will stop the {@link Terminal} from taking focus.
		 */
		preserveFocus?: boolean;
	}

	export interface TerminalSplitLocationOptions {
		/**
		 * The parent terminal to split this terminal beside. This works whether the parent terminal
		 * is in the panel or the editor area.
		 */
		parentTerminal: Terminal;
	}

Also, be sure to test splitting terminals in the editor and panel as that should all still work properly and there were a lot of changes that went into this work.

I expect that this is probably just my misunderstanding of how viewColumn works but I expected this code to create a new terminal in the 4th editor. If I have a 2 x 3 grid of editors (2 rows of 3 columns) I expected this to create a new terminal in the first editor group in the second row. But instead it creates a new terminal next to whatever editor is active.
context.subscriptions.push(vscode.commands.registerCommand('terminaltest.createTerminal', () => {
	let termEdLocation:vscode.TerminalEditorLocationOptions = {
		viewColumn: vscode.ViewColumn.Four,
		preserveFocus: false
	};
	vscode.window.createTerminal({
		name: `Ext Terminal #${NEXT_TERM_ID++}`,
		location: termEdLocation
	} as any);
	vscode.window.showInformationMessage('Hello World 2!');
}));

@meganrogge for testing the TerminalSplitLocationOptions.parentTerminal property, I my extension code passed the vscode.window.activeTerminal. Then I noticed that activeTerminal only tracks the terminals of the panel, but not the ones from the editor area. If this is the intended behavior, then the comment needs to be updated.

@Tyriar I debugged and see this happening appropriately when I create a terminal in the editor area or panel or when I focus and switch between them. So not sure how it's not working
public async $acceptActiveTerminalChanged(id: number | null): Promise<void> {
		const original = this._activeTerminal;
		if (id === null) {
			this._activeTerminal = undefined;
			if (original !== this._activeTerminal) {
				this._onDidChangeActiveTerminal.fire(this._activeTerminal);
			}
			return;
		}
		const terminal = this._getTerminalById(id);
		if (terminal) {
			this._activeTerminal = terminal;
			if (original !== this._activeTerminal) {
				this._onDidChangeActiveTerminal.fire(this._activeTerminal.value);
			}
		}
	}

@meganrogge I was using this code in the "helloWorld" command of the standard "hello world" extension:
		const terminal = vscode.window.createTerminal({
			name: 'august',
			message: 'a message',
			location: {
				viewColumn: ViewColumn.Beside,
				parentTerminal: vscode.window.activeTerminal
			}
		});

When running the "helloWorld" command, new terminals are always added to the panel but not to editor area. Maybe my interpretation that "activeTerminal only tracks the terminals of the panel" is wrong...


GoRun GoTest errors

I've been playing with GoRun and GoTest and noticed a few bugs;
* (GoTest) if you set a non-default runner, e.g. richgo, and run only GoTest without any args, it installs it, and runs the test. But next time around it has to install it again, and the binary is also not callable from anywhere else. So it only does a temporary install. (bug on my side)

(GoTest) if you pass in the -F flag, and have a non-default test runner. It does install it, but only after printing out an error about it not being found. Then opens the terminal prior to it being installed, and then never actually runs the tests.
(Both) If you pass in the -F flag, and an error occurs, the floating term still opens up empty even though an error occurred. Would be nice to have a check that if an error occurred, don't open floating term anymore.

Turns out some of the bugs previously reported were misconfigs on my side. Updated the comment.
Side request; it would be nice if running GoRun on a main.go file or main package would automatically run that main file/package

-F option allows you run in floaterm, without it it runs in background and send result to loclist.
If you set run_in_floaterm to be true, you can omit -F option.
Pushed an update and hope it solves the defect you found.

I get the same error as you GitHub tests
E5108: Error executing lua ...share/nvim/site/pack/vendor/start/go.nvim/lua/go/env.lua:19: attempt to concatenate local 'val' (a userdata value)

if I change your append function to this, it works;
function M.append(env, val)
  local oldval = vfn.getenv(env)
  if val == vim.NIL or string.find(oldval, val) then
    return
  end
  local newval = oldval .. ":" .. val
  vfn.setenv(env, newval)
end


Make it smart/compatible with rushjs

Clear and concise description of the problem
When used with rushjs-based monorepos the tool prompts every time for the target agent cause it couldn't find one of the agent files (yarn.lock, package-lock.json)
Suggested solution
Make the tool lookup for the rush.json file then check what package manager rush uses by checking which one of these options are active on the config file
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

It's out-of-scope. I still belive you should use lock, or create a dummy package.json.


Feature request : Ability to get an image fill for progress instead of a still image

I'm asking that now that I see you're reworking on this Nuget lately.
I don't really know how hard it would be to create here but instead of the circle fill (who's been working really great so far for me, thanks a lot for that !), would it be possible to get an image getting filled depending of the progress ?
Maybe with the idea of using 2 different pictures, one slowly covering the other ?
Thanks a lot

Do you have an example of this? A video or something that shows what you would want?

For exemple, would look something like that. Depending on the progress, the image would appear to get filled up. Here there would be 2 different pictures : The one on the background and the other who's progressively covering up the other.

Or maybe with only one pic, since the background of the loading popup is darker

Why don't you just use something like Lottie for that?


fix(pdk) - respect the trace flags from the parent span (if present)

Summary
Kong respects the should_sample decision from a parent span if one was provided. Previously it was not doing this resulting in incomplete traces.
When using kong as an internal api gateway we are seeing incomplete traces. The logs show that the following appears to be happening:
(this is based on a sampling rate of 0.01)

Service A makes a request to Service B with no traceparent header specified
Kong generates a traceparent header and specifies trace flags of "01" (i.e. the trace should be sampled)
Service B handles the request from Service A and ingests the traceparent header
Service B then makes a request to Service C, setting the traceparent header appropriately (i.e. using flags "01")
Kong then resets the trace flags to "00" (i.e. the trace should not be sampled)
Service C handles the request from Service B and, respecting the flags from the traceparent header, does not sample the trace

This results in Kong and Services A and B sampling the trace, but Service C does not, and so we get an incomplete trace.
I identified the get_sampling_decision method as the most likely place where the issue occurs, and since parent_should_sample is a tri-state boolean (i.e. it can be true, false, or nil) it makes most sense (to me) to respect the value of parent_should_sample if it exists.
I tested this locally and it behaves as I would expect; when a traceparent header is included in the request, then the flags are respected, however if not, probabilistic sampling is applied.
However rereading the code, I can't work out why that should be the case, since the probablistic sampler is deterministic based on trace id (i.e. the same trace-id will always return the same outcome). Even stepping through the code, I couldn't work out exactly what was going on. It seems likely to me that it's something to do with how the root span is constructed, but I couldn't tell for sure.
Checklist

[ ] The Pull Request has tests
[x] A changelog file has been created under changelog/unreleased/kong or skip-changelog label added on PR if changelog is unnecessary. README.md
[ ] There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

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

Hi @andyroyle, thank you for your contribution!
Could you please test the branch from this PR and let me know if it soves your problem? The explanation of the fix (which should answer your questions) is in the PR description.
Regarding your changes:

I identified the get_sampling_decision method as the most likely place where the issue occurs, and since parent_should_sample is a tri-state boolean (i.e. it can be true, false, or nil) it makes most sense (to me) to respect the value of parent_should_sample if it exists.

This is not wrong, however, it is also not the way Kong's sampler is currently designed and I'm afraid your logic might turn out to be a breaking change for some. At the moment, as you noticed, the parent's sampling decision is only inherited when false, else the probabilistic logic is applied.
This (if everything worked correctly) should allow configuring the sampler to do either of the following:

Always inherit the parent's decision, when the sampling_rate matches that of the parent
Apply additional sampling on top of the incoming trace, with a different value of sampling_rate

Since some might be relying on (2.), if we wanted to introduce a change and make Kong support a "parent based sampler", it should be configurable. However, I believe that with the fix I linked, this should not be needed any longer, but please do let me know in case I missed anything or you have a different opinion.
I am converting this to draft for the time being.
Once again, thank you for your investigation and for bringing this up!

Yep, I think you identified the correct way to solve this issue. I think the key piece of context I was missing was that the sampling_rate could be empty (because it's actually the plugin's sampling rate, which can be different from the global sampling rate).
Amazing work, thanks for highlighting this, otherwise I would probably have continued to use my "fixed" version forever, believing it to be correct 😬

Yep, I think you identified the correct way to solve this issue. I think the key piece of context I was missing was that the sampling_rate could be empty (because it's actually the plugin's sampling rate, which can be different from the global sampling rate).
Amazing work, thanks for highlighting this, otherwise I would probably have continued to use my "fixed" version forever, believing it to be correct 😬

Thanks for getting back to me @andyroyle and for confirming the fix (now merged) works! I'm really  glad that helped. I'm going to close this PR, your contribution was very much appreciated!


[Button] Don't apply hover styles when disabled

The goal is to eventually enable tooltips on disabled buttons with
<Tooltip title="why it is disabled">
  <Button disabled style={{ pointerEvents: "all" }}>
    disabled button
  </Button>
</Tooltip>

In case it isn't clear: Right now this only enables Button disabled style={{ pointerEvents: "all" }} /> to not trigger hover styles on hover. There's a reason pointer-events: none is not platform standard: To enable tooltips on disabled buttons. Right now we prohibit this and it's a major customization hazard with Buttons and a common pitfall (which is why we have a dedicated docs section).
With pointer-events enabled we can leverage PointerEvents such as pointerover and pointerout.
Double clarification: Check out https://codesandbox.io/s/textbuttons-material-demo-forked-wz3dz
https://deploy-preview-26412--material-ui.netlify.app/components/buttons/#main-content

What's the main downside with the current approach?

It cannot allow tooltips on disabled buttons.

I have rebased on HEAD to take edfaadcf7c4da1e1fcbad67bcb987fc7742cd215 in.

I have created two sandboxes with:
import * as React from "react";
import Button from "@material-ui/core/Button";
import Tooltip from "@material-ui/core/Tooltip";

export default function BasicTooltip() {
  return (
    <Tooltip title="why it is disabled">
      <Button disabled style={{ pointerEvents: "all" }}>
        disabled button
      </Button>
    </Tooltip>
  );
}

Before https://github.com/mui-org/material-ui/pull/26412#issuecomment-860079516: https://codesandbox.io/s/basicbuttons-material-demo-forked-4oi9k OK
After https://github.com/mui-org/material-ui/pull/26412#issuecomment-860079516: https://codesandbox.io/s/basicbuttons-material-demo-forked-nyw7j KO

I'm closing per https://github.com/mui-org/material-ui/pull/26412#issuecomment-860275928. We could restart it later on with a different strategy.

I'm closing per #26412 (comment). We could restart it later on with a different strategy.

I think you don't understand the path forward. I'm not sure in how many other ways I can explain to you that this doesn't work yet. This change is a requirement to unlock Tooltips on disabled elements. This PR can stand on its own since it integrates with other Tooltip implementations.

The test case feels fabricated.

I don't know which person you're representing here but this purposely being obtuse is just toxic. This behavior is not acceptable. You're actively trying to prevent allowing tooltips on disabled buttons and don't have the courage to explain why. Instead you're claiming the feature request is "fabricated". Why you never use that terminology in other feature request? Who knows. Probably people who pay you.

For anybody else reading: Olivier's responses are misleading. The behavior this PR allows has been outlined sufficiently: Allowing tooltips on disabled buttons.

@eps1lon To be clear, my previous comment was meant to help push the solution further.
I would like to acknowledge that It's only now that I saw the edit done in the description of the page after https://github.com/mui-org/material-ui/pull/26412#pullrequestreview-666172493. My previous comment didn't take unto account that we would rely on onpointerover to make it work. I assumed it would work as-is, hence my confusion.
With this extra information at hand, I think that we could act on https://github.com/mui-org/material-ui/pull/26412#pullrequestreview-712229834 with:

Use the e2e test infra to add a test case with onpointerover
Update all the other components, IconButton, ListItem, BreadcrumbCollapse, CardActionArea, Fab, ToggleButton
I think that these points are still worth exploring.

What do you think?

To answer on the previous:

The test case feels fabricated.

I don't know which person you're representing here but this purposely being obtuse is just toxic.

I have expressed how I felt about the test case (in the source, I didn't saw the new codesandbox in the PR's description). It's not meant to be a fact, it's a feeling. I feel the same way as in https://github.com/mui-org/material-ui/issues/25578#issuecomment-820573382

it's unclear what actual problem it is fixing (the codesandbox in this issue is constructed i.e. missing real world use case)

I mean, do we have a GitHub issue that goes into the problem we have in HEAD? I think that it would be great to make a case on how we can improve https://next.material-ui.com/components/tooltips/#disabled-elements/Why the proposed solution is a better tradeoff.

The behavior this PR allows has been outlined sufficiently: Allowing tooltips on disabled buttons.

I think that we could use your framework of https://github.com/mui-org/material-ui/pull/23726#pullrequestreview-539171917 that I think is great. Do the changes done in a given PR bring value on their own?
I personally think that it would be better to go to the end goal in a single PR, but maybe the other members think otherwise, in which case, happy to be overruled.


Search component does not render correctly on mobile and tablet

What
The label text in the Search component on small screen sizes overlaps with the search button on small sizes

A live example of this issue can seen in the service manual - https://www.gov.uk/service-manual/service-standard

A quick fix for this is something like the following CSS, which will prevent the .gem-c-search__label element from overflowing:
    max-width: 68%;
    text-overflow: ellipsis;
    max-height: 100%;
    overflow: hidden;
    white-space: nowrap;

Looking like this:

This is not ideal, though. Another approach would be to adjust the columns on the header, from this:

To this:

(included above is a suggested change to the text of the label, to make it more accurate as to what it actually searches)

Noting also a problem in Firefox, when using the 'zoom text only' zoom option.


Provide secrets to the provisioner/nodeplugin pods directly, rather than rely on secrets via the CSI requests

Branching off from this comment: https://github.com/ceph/ceph-csi/issues/578#issuecomment-583501921
This issue to track specifically, the ability to provide the CSI pods with cluster secrets for use as below,
To overcome lack of secrets for any required solution in NodeUnstageVolume request, it is proposed that we can add secrets (name/namespace data) to the clusterID configuration, and read/watch said kubernetes secrets.

This separates the secrets into their own namespaces (a requirement when different users administer the different ceph clusters), and needs required RBACs for pods in the CSI namespace to read the same
Provides the secrets for all calls that CSI may want to make (now and in the future)
Brings us closer to cloud provider implementations, where ability to access secrets by the CSI driver is assumed in such environments

Further as more RPCs are added (expand requests as an example) the StorageClass need not be recreated to add the said secret, rather secrets present with the CSI pods can be leveraged to perform the required operations.

@ShyamsundarR Thanks for creating the issue. We need to do this enhancement to overcome some limitations. This is a good candidate for next release after 3.0.0

This enhancement also help to overcome some validation and failure in CSI driver to perform some operations. One example would be expansion of the PVs which does not carry the expansion secret..etc.

Closing this one as we dont have any plan to support it now.


Weird results when combined with Quaternions.jl

I was testing out Measurements together with some orientation quaternions using Quaternions.jl. Starts out ok, but then something happens with the derivatives.
I have a function to create an orientation quaternion given an axis (a unit vector) and an angle:
using Quaternions, Measurements, LinearAlgebra

orientation(v, angle) = Quaternion(cos(0.5 * angle), sin(0.5 * angle) .* v)

Then I have a function to apply an orientation quaternion to perform a vector rotation (3-vectors are represented as quaternions with zero real part):
vec_quaternion(v) =  Quaternion(0.0, v)
rotate(q, v) = Quaternions.imag(q * vec_quaternion(v) * inv(q))

(Above, Quaternions.imag returns a 3-element Array{Float64,1} with the three imaginary components of the given quaternion.)
Using Measurements, I create an orientation that represents a 45° rotation around the Z axis, with a 1% error in the angle. Looks ok so far:
julia> q = orientation([0.0, 0.0, 1.0], π/4 * (1 ± 0.01))
Quaternion{Measurement{Float64}}(0.9239 ± 0.0015, 0.0 ± 0.0, 0.0 ± 0.0, 0.3827 ± 0.0036, false)

I apply this quaternion to rotate the X-axis unit vector. The printout also looks ok:
julia> u = rotate(q, [1.0, 0.0, 0.0])
3-element Array{Measurement{Float64},1}:
 0.7071 ± 0.0056
 0.7071 ± 0.0056
    0.0 ± 0.0

But this resulting vector does not behave like expected:
julia> norm(u)
1.0 ± 1.1e-18

julia> u[1]^2 + u[2]^2
1.0 ± 2.2e-18

julia> u[1] + u[2]
1.414213562373095 ± 0.0

I'm not familiar with Quaternions, so I don't know what you expect.
I tried to run your code with a plain number 1 instead of 1 \pm 0.01 and I got the following:
julia> q = orientation([0.0, 0.0, 1.0], π/4 * (1))
Quaternion{Float64}(0.9238795325112867, 0.0, 0.0, 0.3826834323650898, false)

julia> u = rotate(q, [1.0, 0.0, 0.0])
3-element Array{Float64,1}:
 0.7071067811865475
 0.7071067811865476
 0.0

julia> norm(u)
1.0

julia> u[1]^2 + u[2]^2
1.0

julia> u[1] + u[2]
1.414213562373095

so I don't really know what's wrong with what you get when using a Measurement, the nominal values are just the same.  Were you expecting different uncertainties?

Wait, never mind. Now that you said that, I thought about it more, and looked at it from another angle, and those are reasonable. I was thrown off by the fact that if I do it "manually", the results are quite different, but that's of course due to the history. I blame a flu I'm currently suffering… Sorry about that.
v = [0.7071 ± 0.0056, 0.7071 ± 0.0056, 0.0 ± 0.0]
3-element Array{Measurement{Float64},1}:
 0.7071 ± 0.0056
 0.7071 ± 0.0056
    0.0 ± 0.0

julia> norm(v)
1.0 ± 0.0056

julia> v[1]^2 + v[2]^2
1.0 ± 0.011

julia> v[1] + v[2]
1.4142 ± 0.0079

No problem, I'm glad you're finding this package useful :slightly_smiling_face:   It's always amazing to see how easy it's in Julia to plug different packages together!

Yes, now I'm actually rather impressed by how well it works. For what it's worth, what I'm working on is a simple code that lets me integrate orientation and angular velocity using quaternions, similar to a leapfrog integrator for position and velocity. It's technically complete but I have not thoroughly tested it against analytical solutions or other codes, so I haven't really announced it anywhere, https://github.com/dronir/QuaternionIntegrator.jl


[Buggy] Biome Replacer incapable on Sinytra

Mod Name
Biome Replacer
Mod Homepage
https://legacy.curseforge.com/minecraft/mc-mods/biome-replacer
Describe the bug
When replacing a modded biome with config, nothing works.
Steps to reproduce

See this report first.
Attempt to replace a modded biome yourself.
Create new world after fiddling with config.
Notice you can still /locate biome

Logs
N/A
Additional context
Although this mod is a virgin, I really like the simplicity behind it because as a mod-pack creator, utilizing mods that are overly simplified like this one, is a godsend - it saves me lots and lots of time. 🙌
Anyway, I did some testing on fabric 0.14.22 and had no issues replacing a cinderscapes biome with a vanilla biome which leads me to believe this just might be a Sinytra bug since I was unable to get the same results on forge.
Config you can test yourself:
cinderscapes:ashy_shoals > minecraft:basalt_deltas

I tested this as you described and it appears to work just fine. No ashy shoals biome is found, and the rest of cinderscapes' biomes are still present.

I tested this as you described and it appears to work just fine. No ashy shoals biome is found, and the rest of cinderscapes' biomes are still present.

okay I need to diagnosis this better. perhaps one of the mods I use is disrupting everything. i’ll do some more testing

sorry for wasting time - this is a mod conflict with BCLib. ticket has been passed over to biome replacer dev to investigate.


Show log items in DataGrid.

This pull request has the code that displays log items in DataGrid. The filters and some other features will be added in following pull requests.

This batch of changes contains the following items.
Define the title bar area with an icon, account name, project name
A refresh button
Datagrid that displays logs line by line
Load log items and add to datagrid collection view
Auto-load more log lines when scrolling down to the bottom.


Re-rendering Optimization

This PR includes

Re-rendering Optimization on Toolbar, Screensaver page and Dashboard page
Chrome Error fixes related to Material UI Grid component

I had been expecting that you would be instantiating a bunch of containers by connecting various components to various selectors, and then passing the containers into the props of parent components - an example of how I did this is in FlowGraphInfo.tsx. However, it looks like what you did instead was pass in selectors as props of parent components, and then use it in a memoized component. Your approach is a bit harder for me to understand implementation details (e.g. memoized components, what are the implications of passing a selector in as a prop) but it makes a lot of sense, and I suspect your approach leads to simpler and more maintainable code than my approach of instantiating a bunch of containers everywhere, where each container is a single component connected to a different selector. Is the approach you've taken a standard practice in the Redux world?

I tested it and things work fine. I've also identified some more areas for optimization to fix in either this PR or a future PR:

When the Set New value modal is opened, it is constantly being redrawn all the time - I suspect this is where some of the input freezing related to #233 is coming from.
When the Events Log is opened, it is also constantly being redrawn all the time
When the Set Alarm limits modal is opened, it is not constantly being redrawn all the time. However, it is redrawing the entire modal whenever an alarm limit value is changed.
The Display tab of the Settings screen is constantly being redrawn all the time
When the red visual alarm border is added or removed, the entire screen is redrawn.

For records-keeping:

This project is licensed under Apache License v2.0 for any software, and Solderpad Hardware License v2.1 for any hardware - do you agree that your contributions to this project will be under these licenses, too?
Were any of these contributions also part of work you did for an employer or a client?
Does this work include, or is it based on, any third-party work which you did not create?

This project is licensed under Apache License v2.0 for any software, and Solderpad Hardware License v2.1 for any hardware - do you agree that your contributions to this project will be under these licenses, too? Yes
Were any of these contributions also part of work you did for an employer or a client? No
Does this work include, or is it based on, any third-party work which you did not create? No


Include domain-name support for the service /v1/ bequeath-your-data-and-die

Note : This issue can be taken after completing the issue https://github.com/openBackhaul/ApplicationPattern/issues/350
In the initial CONFIGfile , there will not be any attributes related to domain-name.
In the server-side logic , the code needs to be enhanced so that if a domain-name attribute can be added via a service , then the server-side code should include the domain-name attribute along with the values and delete the ip-address attribute at the same time and vice versa.

This issues is closed with pull request https://github.com/openBackhaul/OperationKeyManagement/pull/161


List of available rate centres in Canada?

How about adding a list of rate centres for Canada and US that are available? That would help us all understand if this service is viable for our enterprises.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4ddf1c3c-7fb9-ff3c-e8cd-af75999c78cb
Version Independent ID: 6178c672-003f-8f99-f4ab-cf9b06cf5ede
Content: Contact the PSTN service desk - Microsoft Teams
Content Source: Teams/manage-phone-numbers-for-your-organization/contact-pstn-service-desk.md
Service: msteams
GitHub Login: @tonysmit
Microsoft Alias: tonysmit

@the-hutch  Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@tonysmit is it possible to have this information added to the article?

@CarolynRowe - you should check with Dave Lickorish about this. @LanaChin - did you do an article about Canadian Rate Centers for Dave a while back. I can't find it in the TOC anywhere.

@Tonysmit - I don't recall doing or updating an article on Canadian rate centers.

@scanum - I pinged a PM. Let's see what he says.

@the-hutch - I'm working with the PM on this. The issue is it's a bit complex. There are rate centers that are supported now and of course ones coming on line all the time. He has a resource, but he needs to get approval for us to post it publically. Stay tuned.

Wahoo! Thanks :)
On Tue, Mar 31, 2020 at 12:00 PM Tony Smith (MSFT<EMAIL_ADDRESS>wrote:

@the-hutch https://github.com/the-hutch - I'm working with the PM on
this. The issue is it's a bit complex. There are rate centers that are
supported now and of course ones coming on line all the time. He has a
resource, but he needs to get approval for us to post it publically. Stay
tuned.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/3895#issuecomment-606719554,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOOP6UWMNM2F6FS3IM3AX5DRKIHSNANCNFSM4KPJC2JQ
.

@the-hutch - We got approval! I'm going to create a task for our vendor @LanaChin to create a downloadable XLS. I don't have a URL for it right this minute. I'm going to close this, but please ping me in the next week or so to remind me to send you the URL when we get it published. Here is my MSFT email<EMAIL_ADDRESS>in case.


Better support for updating contexts

Notes
obvs doesn't support updating context very well:

When updating prompt to a soft prompt, we don't validate the dimensions of the soft prompt.
When updating max_new_tokens, user needs to also call patchscope.generation_kwargs = ModelLoader.generation_kwargs(...).
When setting position = None, user needs to call patchscope.init_positions().

This PR fixes these issues.
Issue
https://app.asana.com/0/1206344788073276/1206914748769697
Testing
pytest passed.

Love this!
WDYT, can we make the layer and position attributes to properties too and check e.g. if the layer is within 0 and model_layers and the position is within 0 and prompt_length when setting them?

That’d be a bit more involved because the context objects don’t really have the models. They only store the model names. Same for position, they only store the prompt and not the tokens.

I see. In that case, I vote for merge and will create a ticket for checking these cases.

I just noticed that the nnsight.LanguageModel doesn't load the model on init. This means we can validate the layers before actually loading it into memory.

When we initialize LanguageModel, we aren’t yet loading the parameters of the model into memory. We are actually loading a ‘meta’ version of the model which doesn’t take up any memory, but still allows us to view and trace actions on it.

https://nnsight.net/notebooks/tutorials/walkthrough/#Setting
In [8]: x = LanguageModel('gpt2', device_map='mps')

In [9]: x
Out[9]:
GPT2LMHeadModel(
  (transformer): GPT2Model(
    (wte): Embedding(50257, 768)
    (wpe): Embedding(1024, 768)
    (drop): Dropout(p=0.1, inplace=False)
    (h): ModuleList(
      (0-11): 12 x GPT2Block(
        (ln_1): LayerNorm((768,), eps=1e-05, elementwise_affine=True)
        (attn): GPT2Attention(
          (c_attn): Conv1D()
          (c_proj): Conv1D()
          (attn_dropout): Dropout(p=0.1, inplace=False)
          (resid_dropout): Dropout(p=0.1, inplace=False)
        )
        (ln_2): LayerNorm((768,), eps=1e-05, elementwise_affine=True)
        (mlp): GPT2MLP(
          (c_fc): Conv1D()
          (c_proj): Conv1D()
          (act): NewGELUActivation()
          (dropout): Dropout(p=0.1, inplace=False)
        )
      )
    )
    (ln_f): LayerNorm((768,), eps=1e-05, elementwise_affine=True)
  )
  (lm_head): Linear(in_features=768, out_features=50257, bias=False)
  (generator): WrapperModule()
)

In [10]: torch.mps.current_allocated_memory()
Out[10]: 0

In [11]: with x.trace("a prompt"):
    ...:     pass
    ...:
You're using a GPT2TokenizerFast tokenizer. Please note that with a fast tokenizer, using the `__call__` method is faster than using a method to encode the text followed by a call to the `pad` method to get a padded encoding.

In [12]: torch.mps.current_allocated_memory()
Out[12]: 510346240


Change to PDFLoader to us Legacy pdf.js  Accepts Polyfills

pdfjs-dist is causing an error with message The browser/environment lacks native support for critical functionality used by the PDF.js library (e.g. Path2D and/or ReadableStream); please use a legacy-build instead.
According to pdf.js legacy is the only way to run inside node.
https://github.com/mozilla/pdf.js/wiki/Frequently-Asked-Questions#faq-support

We can use PDFLoader like this
new PDFLoader(path, {
    pdfjs: () =>
      import('pdfjs-dist/legacy/build/pdf.js').then((mod) => mod.default)
  })

We can use PDFLoader like this
new PDFLoader(path, {
    pdfjs: () =>
      import('pdfjs-dist/legacy/build/pdf.js').then((mod) => mod.default)
  })

Thank you that is much better.


HoverEvent is not firing while it is added in AsyncChatEvent.

Today, I was trying to replace string to a component which after hover is showing item from player's hand, but I was surprised while this wasn't firing. After cancelling the event and sending message by 'Player#sendMessage' method it is working as it was supposed to do.
Component component = itemMeta.displayName();
if (component == null)
{
        component = Component.text(itemStack.getI18NDisplayName() == null
                ? "Unknown name"
                : itemStack.getI18NDisplayName());
}
component = component
        .append(Component.text(" x"))
        .append(Component.text(itemStack.getAmount()))
        .hoverEvent(itemStack);

event.message(event.message().replaceText(TextReplacementConfig.builder()
        .matchLiteral("<item>")
        .replacement(component)
        .build()));

If you can confirm that this bug is present with zero other server or proxy plugins present then you need to open this issue on Paper's GitHub.


== / hashcode

I recently switched from "manually" storing degrees as doubles to using this package. I only noticed later that the lack of overrides for equality/hashcode of angles led to unexpected behaviour, is this intended? Especially since the "compareTo" method is implemented such that it cannot return 0 for angles of equal values (other than instance identity).

Well, you cannot really test IEEE 754 floating points for equality, so it does not really make sense to provide a way to test for value-equality.
I've still implemented it, together with a approximation comparision, testing an angle withing a given acceptance range. The angle class now provides both, a hash code and a comparision operator.
Thank you for pointing out that issue and please feel free to create a pull request if you see something that's definitely missing in the angle class.

Great, thanks for the quick response. Are you going to release the pub version soon as well or should I let my pubspec point to github instead?

Note: current version number does not allow adding this package as a dependency, dart pub requires semantic versioning (three-digit version number).

So, the new version 1.2.1 is uploaded to pub. I also tagged the git commit with a three-digit version, but it's probably better use the pub served version anyway.


Suggestion: Do not consider lists (numbered, bullet point, ...) as not-done tasks when including subtasks for archiving.

Hi! Thank you @ivan-lednev for creating this wonderful and versatile and modifiable tool! It makes life a lot easier.
There is one minor thing that stops me from being able to use it to its full potential. In my workflow, I often create bullet-points as a indented sub-level of tasks. These help me to keep track of notes as to how/why/... the task was completed.
However, if I enable

Archive a task only if its subtasks are done

which I find immensely useful to not flood my archive in an unstructured way, these bullet points seem to represent "not-done tasks", meaning the parenting task does not get archived even though its completed.
I use the tasks-plugin including a hashtag to denote tasks, and yet, these (not-tagged) bulletpoints count as "not-completed". Thus, given the setting above being enabled, the task will not get archived.
Is there any chance this is problematic for others, too? It feels like a bug, because they are bullet points, not tasks.

Example of tasks that are not archived:

[x] # Task TaskDescription1

How this was completed

[x] # Task TaskDescription2

[ ] Step 1

Example of task that is archived

[x] # Task TaskDescription3

[x] Step 1

Task 3 would be expected to work, and Task 2 would be expected not wo work.
However, Task 1, I would like to archive also, as it does not include any open To-Dos, but only "notes".
However, this might be subjective and is impacted by my personal workflow. Take it as an inspiration and decide whether you would think such a change valuable.
Cheers, and again, thanks for creating this plug-in!

Hi, @Glokta0,
Thank you for your input! This is definitely a bug, and it's fixed in 0.23.2.


Contribution help

Could you add a contribution doc outlining real quick how you want the project to work (what layout package you want to use, looks like you are on multisim now right? would you accept contributions of the design ported to a free package like kicad?, etc).
BTW, nice meeting you at makerfaire and sorry about blowing up your controller.

Hey! Was fun to meet you too. I wish I'd realized a 4S pack would blow this up as is. My fault :-/
I'd love to move to something open and free. I just don't have the time to learn it. I'd be glad if the design got converted. I think someone else might already be transferring this to EAGLE. They might want to publish that.
Anyway, high level, I just want to remove the "black magic" aspect of BLDC motor controllers, for the entire chain. If we end up with a (or a few) nice controller design(s) that are useful for the world to be used as is, great.
So, to that end, I'll basically accept any contributions as long as we have a mind to keep things organized and it doesn't devolve to such a crazy collection of things that it's not digestible.


Cargo doesn't understand prerelease versions or build metadata

Semver allows specifying versions such as 1.0.0-beta+exp.sha.5114f85, see http://semver.org/#spec-item-9 . Cargo doesn't handle these versions well or at all. See e.g. https://crates.io/crates/core_rustc-serialize which has these versions:

0.3.19
0.3.19+patch1
0.3.20-v0.3.19patch1

Specifying a dependency core_rustc-serialize = "*" (or  core_rustc-serialize = "^0.3") results in Cargo choosing 0.3.19, while it should choose the newer 0.3.20-v0.3.19patch1. You can't specify 0.3.20-v0.3.19patch1 in either case by using cargo update --precise. Specifying the exact version string does work.
There is simply no way to select 0.3.19+patch1. Putting it in the Cargo.toml results in the error message "the given version requirement is invalid". You also can't select it using cargo update --precise. This results in a crate existing on crates.io that can effectively not be used by anyone.

I think this may be a dupe of https://github.com/rust-lang/cargo/issues/2222 which has been discussed a bit more towards the end of the thread, so I'm going to close in favor of that.
cc @steveklabnik

That bug is currently solely about prerelease versions. There's also an issue with build metadata which has not been discussed in #2222. I'm happy to move that conversation over there too, but then the issue description should be updated.

Ah ok make sense to me, want to reopen one targeted at build metadata (may be good to start fresh). Thanks!