Use Hugo for Sass processing

Addresses issue #9403. The Sass processing feature is not yet in easily installable version of Hugo, so review will need to wait. The PR is here mostly for visibility.

/hold

Update: this is a known Netlify issue, tracked here: https://github.com/netlify/binrc/issues/16

@bep Can you verify that we want to make this change? Thx

@bep My initial, more modest goal in this PR is to eliminate the  node-sass pipeline we currently have in place. Once we remove that, I would love to create a more refined setup. Once this goes through I can get to work on that.
Committing the resources folder to Git is a fine idea, though. I'm tracking the 0.44-related issues on Netlify's side so hopefully (namely here) so hopefully we'll be able to remove that sometime soon.

This Netlify preview doesn't seem to be showing up in the checks, so I'll link it here:
https://deploy-preview-9404--kubernetes-io-master-staging.netlify.com/

Looks like the CSS on the /docs/home page is now messed up: https://deploy-preview-9404--kubernetes-io-master-staging.netlify.com/docs/home/?path=users&persona=app-developer&level=foundational
Is there a way to fix that and still have your change go in?

@chenopis Yeah, I'll take a look

@lucperkins I'm seeing some newline issues, specifically that newlines aren't recognized:
Source: https://github.com/kubernetes/website/blob/master/content/en/docs/imported/community/guide.md
URL: https://deploy-preview-9404--kubernetes-io-master-staging.netlify.com/docs/imported/community/guide/#advanced-topics (look under Meetups and KubeCon)
Also, I don't remember where we are on resolving double bullets in TOCs, but it's happening here.

@zacharysarah I'm seeing the double bullets in the current production site, e.g. here. So I'm fairly certain that that issue stems from the underlying Sass/CSS sources, not this PR. I'd be happy to put this on hold until we get that fixed, though.

I agree with @lucperkins -- the "double bullets" has several sources (one being Hugo's markup; we will eventually fix that) -- but from the CSS side of it, this and other CSS issues get's much more easy to fix when you can "adjust and see".

@lucperkins Solution 1 works for me. :+1:
/lgtm
/approve


Issue rejoining as host when you once left the room

If you leave your room and rejoin it as host you get put in a different room.

as an addendum:
imagine everyone left the team.
someone else wants to start it again...


Seeder

Created seeder files to implement base data with first Admin user to create other users with administrator privileges.

 Fazer seeders para as tabelas do banco (prioridade ADM)


525 generalize creating graph for ode simulation

Merge Request - GuideLine Checklist
Guideline to check code before resolve WIP and approval, respectively.
As many checkboxes as possible should be ticked.
Checks by code author:
Always to be checked:

[x] There is at least one issue associated with the pull request.
[x] The branch follows the naming conventions as defined in the git workflow.
[x] New code adheres with the coding guidelines
[x] Make sure that the pre-commit linting/style checks pass.

If functions were changed or functionality was added:

[x] Tests for new functionality has been added
[x] A local test was succesful

If new functionality was added:

[x] There is appropriate documentation of your work. (use doxygen style comments)

If new third party software is used:

[ ] Did you pay attention to its license? Please remember to add it to the wiki after successful merging.

If new mathematical methods or epidemiological terms are used:

[ ] Are new methods referenced? Did you provide further documentation? Has the glossary been updated?

The following questions are addressed in the documentation if need be:

[ ] Developers (what did you do?, how can it be maintained?)

[ ] For users (how to use your work?)

[ ] For admins (how to install and configure your work?)

For documentation: Please write or update the Readme in the current working directory!

Checks by code reviewer(s):

[ ] Is the code clean of development artifacts e.g., unnecessary comments, prints, ...
[ ] The ticket goals for each associated issue are reached or problems are clearly addressed (i.e., a new issue was introduced).
[ ] There are appropriate unit tests and they pass.
[ ] The git history is clean and linearized for the merge request. All reviewers should squash commits and write a simple and meaningful commit message.
[ ] Coverage report for new code is acceptable.

closes #525

Codecov Report
Base: 92.11% // Head: 92.20% // Increases project coverage by +0.08% :tada:

Coverage data is based on head (8dd4dd2) compared to base (6eb01e6).
Patch coverage: 90.74% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #556      +/-   ##
==========================================
+ Coverage   92.11%   92.20%   +0.08%
==========================================
  Files          93       93
  Lines        7156     7289     +133
==========================================
+ Hits         6592     6721     +129
- Misses        564      568       +4

Impacted Files
Coverage Δ

cpp/memilio/compartments/parameter_studies.h
100.00% <ø> (ø)

cpp/memilio/data/analyze_result.h
100.00% <ø> (ø)

cpp/memilio/io/mobility_io.h
85.24% <ø> (ø)

cpp/memilio/mobility/graph_parameters.h
87.32% <ø> (ø)

cpp/memilio/geography/regions.cpp
37.87% <27.77%> (ø)

cpp/models/abm/simulation.cpp
87.50% <50.00%> (-12.50%)
:arrow_down:

cpp/memilio/io/epi_data.cpp
82.14% <78.26%> (-7.86%)
:arrow_down:

cpp/models/ode_secir/parameters_io.h
92.92% <89.18%> (-4.08%)
:arrow_down:

cpp/memilio/mobility/graph.h
91.86% <93.93%> (+2.39%)
:arrow_up:

cpp/models/ode_secirvvs/parameters_io.h
97.29% <97.89%> (-0.10%)
:arrow_down:

... and 11 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


maxFiles doesn't work as I try to attach files and try 2 limit the files to be uploaded

I have this line of html

						Upload a photo of yours :

						<upload-image :url="uploadUrl" :maxFiles="form.maxFiles"></upload-image>


IndexError: index 197 is out of bounds for axis 1 with size 2

Hey there,
I'm having some issues with np_utils.py.
Traceback (most recent call last):
  File "/home/osheak/Documents/neural-network-plant-trait-classification/software/neuralNetworkSoftware/serialiseAllTheData/serialise.py", line 27, in <module>
    (directory,num_classes,custom_height,custom_width, split, True)
  File "../../pyvec/pyvec/images/dataset.py", line 212, in vectorise
    label = np_utils.to_categorical(train_label, nb_classes)
  File "/usr/local/lib/python2.7/dist-packages/keras/utils/np_utils.py", line 16, in to_categorical
    Y[i, y[i]] = 1.
IndexError: index 197 is out of bounds for axis 1 with size 2

Process finished with exit code 1

Naughty code.
def to_categorical(y, nb_classes=None):
    '''Convert class vector (integers from 0 to nb_classes)
    to binary class matrix, for use with categorical_crossentropy
    '''
    y = np.asarray(y, dtype='int32')
    if not nb_classes:
        nb_classes = np.max(y)+1
    Y = np.zeros((len(y), nb_classes))
    for i in range(len(y)):
        Y[i, y[i]] = 1.
    return Y

I think to_categorical expects y to be 0-indexed and consecutive. You can leave nb_classes=None, but then you'll have some column(s) that are all 0.
I would take a look at the unique values of your train_label variable

Can please someone guide me about that extra column. why I am getting it?


Add dice rolling sound effect when user selects a die to roll

This will need to pause the app while the sound effect plays, then show the results - thus simulating a real dice throw.

Doesn't appear to be any memory leaks caused by the media player.


Missing all_physical_paths at PA level

In PA we are missing the physical path object. We should fix that

This is what we should do to close this issue:

[ ] add .all_physical_paths accessor to PhysicalArchitecture
[ ] introduce PhysicalPath class into pa.py
[ ] add .physical_paths accessor to PhysicalLink
[ ] add tests for new functionality
[ ] update API documentation

This is how Capella actual meta-model looks like for PhysicalPath:


Removed BackendError and replaced single usage with SkipRendering

This is exactly the change I was expecting. I'm tempted to merge right away but I suppose I should wait for the tests...

I'm going to take a risk and merge it now - I'm pretty certain it is fine. I'll make sure it goes green on master though...


Cross compiling for OpenWRT

I am trying to cross compile this library for OpenWRT. In order to do this I set up a VM and installed the OpenWRT cross compile toolkit according to this tutorial.
As the building of this library depends on cmake, I created a openwrt.cmake file with the following content:
# this one is important
SET(CMAKE_SYSTEM_NAME AR7xxx)
#this one not so much
SET(CMAKE_SYSTEM_VERSION 1)

# specify the cross compiler
SET(CMAKE_C_COMPILER   /home/vagrant/openwrt/staging_dir/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-<IP_ADDRESS>/bin/mips-openwrt-linux-gcc)
SET(CMAKE_CXX_COMPILER /home/vagrant/openwrt/staging_dir/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-<IP_ADDRESS>/bin/mips-openwrt-linux-g++)

# where is the target environment
SET(CMAKE_FIND_ROOT_PATH  /home/vagrant/openwrt/target/linux/ar71xx)

# search for programs in the build host directories
SET(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER)
# for libraries and headers in the target directories
SET(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY)
SET(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)

and I edited this repos Makefile to include the DCMAKE_TOOLCHAIN_FILE flag, like this:
LUV_TAG=$(shell git describe --tags)

ifdef WITHOUT_AMALG
    CMAKE_OPTIONS+= -DWITH_AMALG=OFF
endif

BUILD_MODULE ?= ON
BUILD_SHARED_LIBS ?= OFF
WITH_SHARED_LIBUV ?= OFF
WITH_LUA_ENGINE ?= LuaJIT
LUA_BUILD_TYPE ?= Static

ifeq ($(WITH_LUA_ENGINE), LuaJIT)
  LUABIN=build/luajit
else
  LUABIN=build/lua
endif

CMAKE_OPTIONS += \
    -DBUILD_MODULE=$(BUILD_MODULE) \
    -DBUILD_SHARED_LIBS=$(BUILD_SHARED_LIBS) \
    -DWITH_SHARED_LIBUV=$(WITH_SHARED_LIBUV) \
    -DWITH_LUA_ENGINE=$(WITH_LUA_ENGINE) \
    -DLUA_BUILD_TYPE=$(LUA_BUILD_TYPE) \
    -DCMAKE_TOOLCHAIN_FILE=~/openwrt/openwrt.cmake \

all: luv

deps/libuv/include:
    git submodule update --init deps/libuv

deps/luajit/src:
    git submodule update --init deps/luajit

build/Makefile: deps/libuv/include deps/luajit/src
    cmake -H. -Bbuild ${CMAKE_OPTIONS} -DWITH_AMALG=OFF

luv: build/Makefile
    cmake --build build --config Debug
    ln -sf build/luv.so

clean:
    rm -rf build luv.so

test: luv
    ${LUABIN} tests/run.lua

reset:
    git submodule update --init --recursive && \
      git clean -f -d && \
      git checkout .

publish-luarocks:
    rm -rf luv-${LUV_TAG}
    mkdir -p luv-${LUV_TAG}/deps
    cp -r src cmake CMakeLists.txt LICENSE.txt README.md docs.md luv-${LUV_TAG}/
    cp -r deps/libuv deps/*.cmake deps/lua_one.c luv-${LUV_TAG}/deps/
    COPYFILE_DISABLE=true tar -czvf luv-${LUV_TAG}.tar.gz luv-${LUV_TAG}
    github-release upload --user luvit --repo luv --tag ${LUV_TAG} \
      --file luv-${LUV_TAG}.tar.gz --name luv-${LUV_TAG}.tar.gz
    luarocks upload luv-${LUV_TAG}.rockspec --api-key=${LUAROCKS_TOKEN}

Then, when I start the build like this
$ WITH_LUA_ENGINE=Lua LUA_BUILD_TYPE=System WITH_SHARED_LIBUV=ON BUILD_MODULE=OFF BUILD_SHARED_LIBS=ON STAGING_DIR=./staging_dir make

the build starts but fails as it cannot find the lua headers
cmake --build build --config Debug
make[1]: Entering directory '/home/vagrant/openwrt/custom/luv/build'
make[2]: Entering directory '/home/vagrant/openwrt/custom/luv/build'
make[3]: Entering directory '/home/vagrant/openwrt/custom/luv/build'
make[3]: Leaving directory '/home/vagrant/openwrt/custom/luv/build'
[ 92%] Built target uv
make[3]: Entering directory '/home/vagrant/openwrt/custom/luv/build'
make[3]: Leaving directory '/home/vagrant/openwrt/custom/luv/build'
make[3]: Entering directory '/home/vagrant/openwrt/custom/luv/build'
[ 96%] Building C object CMakeFiles/luv.dir/src/luv.c.obj
In file included from /home/vagrant/openwrt/custom/luv/src/luv.c:18:0:
/home/vagrant/openwrt/custom/luv/src/luv.h:19:17: fatal error: lua.h: No such file or directory
 #include <lua.h>
                 ^
compilation terminated.
CMakeFiles/luv.dir/build.make:62: recipe for target 'CMakeFiles/luv.dir/src/luv.c.obj' failed
make[3]: *** [CMakeFiles/luv.dir/src/luv.c.obj] Error 1
make[3]: Leaving directory '/home/vagrant/openwrt/custom/luv/build'
CMakeFiles/Makefile2:104: recipe for target 'CMakeFiles/luv.dir/all' failed
make[2]: *** [CMakeFiles/luv.dir/all] Error 2
make[2]: Leaving directory '/home/vagrant/openwrt/custom/luv/build'
Makefile:127: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/vagrant/openwrt/custom/luv/build'
Makefile:40: recipe for target 'luv' failed
make: *** [luv] Error 2

How can I make sure lua is available in the cross compile environment? I am quite new to openwrt, lua and cross compiling in general so I might be missing something obvious.

I would think you could simply add the path to the header file manually in your custom cmake script.  Also look through the existing config variables in the cmake script.  I seem to remember someone contributing a variable to specify the lua to link against.

I tried the same and everything works fine except the fact that luv tries to compile luajit and luajit tries to compile minilua and uses the executable to do something. As we are crosscompiling, the resulting minilua is not runnable on the host system, so the build fails.
$ make
cmake --build build -- -j4
make[1]: Entering directory `/tmp/luvi/build'
make[2]: Entering directory `/tmp/luvi/build'
make[3]: Entering directory `/tmp/luvi/build'
make[3]: Entering directory `/tmp/luvi/build'
make[3]: Entering directory `/tmp/luvi/build'
make[3]: Leaving directory `/tmp/luvi/build'
make[3]: Leaving directory `/tmp/luvi/build'
[  0%] make[3]: Leaving directory `/tmp/luvi/build'
Built target LPEGLIB
[  3%] make[3]: Entering directory `/tmp/luvi/build'
Built target pcre
make[3]: Entering directory `/tmp/luvi/build'
[  7%] make[3]: Leaving directory `/tmp/luvi/build'
make[3]: Leaving directory `/tmp/luvi/build'
Built target uv
make[3]: Entering directory `/tmp/luvi/build'
[  7%] Built target minilua
make[3]: Entering directory `/tmp/luvi/build'
[  7%] Built target lrexlib
make[3]: Entering directory `/tmp/luvi/build'
make[3]: Leaving directory `/tmp/luvi/build'
make[3]: Leaving directory `/tmp/luvi/build'
[  7%] [  8%] Built target luv
Generating buildvm_arch.h
/bin/sh: 1: minilua: not found
make[3]: *** [deps/luv/buildvm_arch.h] Error 127
make[3]: Leaving directory `/tmp/luvi/build'
make[2]: *** [deps/luv/CMakeFiles/buildvm.dir/all] Error 2
make[2]: *** Waiting for unfinished jobs....
[  8%] Built target pcreposix
make[3]: Entering directory `/tmp/luvi/build'
make[3]: Leaving directory `/tmp/luvi/build'
[ 92%] Built target openssl
make[2]: Leaving directory `/tmp/luvi/build'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/tmp/luvi/build'
make: *** [luvi] Error 2

The line that does not work: https://github.com/luvit/luv/blob/master/deps/luajit.cmake#L206

Recently, LuaJIT added support for cross-compiling to MIPS (https://github.com/LuaJIT/LuaJIT/tree/v2.1). It would be nice to use this new version in luv.

@joustava Use your staging_dir for CMAKE_FIND_ROOT_PATH, not your target build directory and everything would work.

I am crosscompiling for aarch64 nevertheless the same issue I believe - getting the same errors using a properly functioning yocto-generated toolchain and sysroots for building on a Debian Bullseye host.
apt install qemu-user qemu-user-static gcc-aarch64-linux-gnu binutils-aarch64-linux-gnu
diff --git a/deps/lua.cmake b/deps/lua.cmake
index 7c0b9e3..0dd09f7 100644
--- a/deps/lua.cmake
+++ b/deps/lua.cmake
@@ -142,7 +142,7 @@ MACRO(LUA_add_custom_commands luajit_target)
         OUTPUT ${generated_file}
         MAIN_DEPENDENCY ${source_file}
         DEPENDS lua
-        COMMAND lua
+        COMMAND QEMU_LD_PREFIX=/usr/aarch64-linux-gnu/ qemu-aarch64 lua
         ARGS "${LUA_DIR}/../luac.lua"
           ${source_file}
           ${generated_file}
diff --git a/deps/luajit.cmake b/deps/luajit.cmake
index 189aabd..ab47a4c 100644
--- a/deps/luajit.cmake
+++ b/deps/luajit.cmake
@@ -253,7 +253,7 @@ if(MINILUA_USE_LIBM)
 endif()

 add_custom_command(OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/buildvm_arch.h
-  COMMAND minilua ${LUAJIT_DIR}/dynasm/dynasm.lua ${DASM_FLAGS} -o ${CMAKE_CURRENT_BINARY_DIR}/buildvm_arch.h ${LUAJIT_DIR}/src/vm_${DASM_ARCH}.dasc
+  COMMAND QEMU_LD_PREFIX=/usr/aarch64-linux-gnu/ qemu-aarch64 minilua ${LUAJIT_DIR}/dynasm/dynasm.lua ${DASM_FLAGS} -o ${CMAKE_CURRENT_BINARY_DIR}/buildvm_arch.h ${LUAJIT_DIR}/src/vm_${DASM_ARCH}.dasc
   DEPENDS ${LUAJIT_DIR}/dynasm/dynasm.lua minilua
 )

@@ -288,7 +288,7 @@ SET_TARGET_PROPERTIES(buildvm PROPERTIES COMPILE_DEFINITIONS "${TARGET_ARCH}")

 macro(add_buildvm_target _target _mode)
   add_custom_command(OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/${_target}
-    COMMAND buildvm ARGS -m ${_mode} -o ${CMAKE_CURRENT_BINARY_DIR}/${_target} ${ARGN}
+    COMMAND QEMU_LD_PREFIX=/usr/aarch64-linux-gnu/ qemu-aarch64 ${CMAKE_BINARY_DIR}/buildvm ARGS -m ${_mode} -o ${CMAKE_CURRENT_BINARY_DIR}/${_target} ${ARGN}
     WORKING_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}
     DEPENDS buildvm ${ARGN}
   )
@@ -386,7 +386,7 @@ MACRO(LUAJIT_add_custom_commands luajit_target)
         OUTPUT ${generated_file}
         MAIN_DEPENDENCY ${source_file}
         DEPENDS luajit
-        COMMAND luajit
+        COMMAND QEMU_LD_PREFIX=/usr/aarch64-linux-gnu/ qemu-aarch64 luajit
         ARGS -bg
           ${source_file}
           ${generated_file}

The issue was opened for compiling an ar71xx target with the mips34kc toolchain - quick research about openwrt and ar71xx seems to have been dropped/deprecated in favor of ar79 so I'd assume 6 years later it's not relevant anymore in this particular case.
I'm completely aware that there are more elegant ways of solving this, but considering the fact that the issue is from 2016 and is still open, I'm dropping this diff here for people who stumble upon the same issue, because I do not have time to write a proper fix for CMake getting into consideration that a crosscompile is being done.
This works for me and produces valid and working binaries and libraries.
In the case of a mips emulation I'd also guess something like qemu-mips -cpu 24kc has to be used


Review new GridAPPS-D Runtime documentation

Running GridAPPS-D - Notebook 1.4 (https://gridappsd-training.readthedocs.io/en/latest/installation/1.4-Running-GridAPPS-D.html)
Using GridAPPS-D Viz - Notebook 1.5 (https://gridappsd-training.readthedocs.io/en/latest/installation/1.5-Using-GridAPPS-D-Viz.html)

1.0--Module-1--Installation-Runtime
The links to the Os-specific installation also seem to break.
(1)	1.0--Module-1--Installation-Runtime/Windows 10 Installation 404: Not Found
(2)	1.0--Module-1--Installation-Runtime/Ubuntu Linux Installation404: Not Found
(3)	1.0--Module-1--Installation-Runtime/MacOSInstallation404: Not Found
1.4-Running-GridAPPS-D
i)Starting the Platform
(1)	Had to run ./run-gridappsd.sh to get access to the localhost:8080
ii)	Previous Lesson Link breaks
(1)	1.4-Running-GridAPPS-D/Previous Lesson404: Not Found
1.5-Using-GridAPPS-D-Viz – No comments
1.6-Docker Shortcuts
i)	 Empty Page
1.7-Cloud-Server-Configuration
i)	Was not able to locate file viz.config
1.8-Platform-Release-History – No comments
1.9-Known-VPN-Proxy-Issues – No comments


Are Heatmaps supported?

Trying to find an alternative to mapbox-gl-native than can be used in .NET Core. Does VectorTileRenderer support adding Heatmap layers?

Not yet. But if you want to work on this feature, you may add a pull request


active cell and selected cells

Hi, @TonyGermaneri
I am a bit confused about property activeCell.
I opened the fiddle with one of the examples from documentation:
http://jsfiddle.net/t57Lzwsr/
When I click some cell, it's became active. I am able to move selection by using keyboard and see strange behavour:

cell (1,1) is selected, but cell (0, 3) is active. My question is: what is exact behavior of an active cell? How we should use it? Does it possible to set it null to avoid confusing users?
That story came from my personal jira. Users asked me to investigate pre-selected default cell at the left top angle and I found out that it's slightly different to the "selected" cell.
They aren't able to move selecting ant get scary.
Thanks!

Active cell: The cell that the "cursor" is on.  There can only be one active cell.  It helps the user see where they are navigating with the keyboard, and it also indicates the target of keyboard commands like "enter".
Selection is a jagged array of cells.  It can take any form and be as many cells as desired.  Selection is not changed by keyboard navigation.  Selection indicates what will be changed when copy/paste/move happen.
If you want to make active cell "go away":
Active cell is a different style than the rest of the cells, if you want to "get rid" of active cell, you can just change the style of active cell to the style of the normal cell.  Keep in mind that active cell has "selected active cell" state as well, so you would have to update both styles to look the same as the normal cell/selected cell to make it go away.
If you hide the active cell, it might make it more difficult for users to navigate with the keyboard.  If that's not important to you, than hiding it should be pretty easy.  Let me know if this answers you question.

@TonyGermaneri And if we want to change the selected active cell while navigating in the grid how we would be able to do that?

I'd like to put in a vote for bringing the interaction between selection and active cell in line with expected behavior, as it tripped me initially, and I can imagine anyone used to Google Sheets or Excel would find the current distinction confusing as well.
In Excel or Sheets, the 'active' cell is, normally speaking, where the selection started out (here, top left B3):

The exception to this is when a non-contiguous set of cells are selected. In that case the 'active' cell is the last cell to be added to the selection:

Either way, navigating away from wherever the active cell is using the arrows keys or clicking another cell clears the selection and moves the active cell to that new location:

I believe we should strive to mimic this behavior instead of current behavior, but I may not be aware of the reasoning behind why it's set up the way it is now. What say you, @TonyGermaneri ?

We should always abide by the principle of least astonishment and follow the behavior of the de facto standard.  I would love to see this change.

This would be a great feature. I'm wondering if there is any movement on it? I'm writing an Excel-like view atm and want to replicate their approach. I'm not too confident with the actual code base, but I expect I can get to something close by hooking onto the selection events which I'll be happy to share as a workaround if I can get this working.

I think setting selectionFollowsActiveCell to 'true' as a default solves (most of) this issue.
Setting this argument to true changes the grid behaviour as follows for 'normal' selections:

and for (B) non-contiguous cell selection:

For normal selections the behaviour is identical to what @ndrsn describes as standard Excel and Google Sheets behaviour.
For non-contiguous selections the difference is that the active cell remains the first cell of the selection instead of the last selected cell.


Revert "Update curl-sys to use libcurl 7.88.1"

Reverts rust-lang/cargo#11749 due to a pipewait issue, see rust-lang/cargo#11746

@bors r+

:pushpin: Commit 43a27cbcde4b6a77f356326b846a1745ac081fbb has been approved by weihanglo
It is now in the queue for this repository.

:hourglass: Testing commit 43a27cbcde4b6a77f356326b846a1745ac081fbb with merge 7ddcf0fe3348b7e0f4ad4a730eab60a20638ef28...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing 7ddcf0fe3348b7e0f4ad4a730eab60a20638ef28 to master...


Create a default value for github_username in the generated YAML file

github_username defaults to suffolklitlab for purposes of checking the last modified date and submitting feedback. Authors can customize this value, but it's not present in the file by default so it can be hard to identify.
We should let the author specify this value as well as fill in a default based on the branding package.

Note that #125 would let us fill in the actual real GitHub username instead of just a placeholder. That's worth considering.

Because it's easy to configure github_username in:

the branding package
the server-wide config setting

this is pretty low priority. I think we should only consider when it can be combined with #125


derive Semigroup and Monoid

should pass once https://github.com/purescript/purescript-free/pull/98 is merged

@safareli is this still in play? purescript/purescript-free#98 has been merged

Looks like it's passing so should be fine to merge/squish


performance improvement  suggestion

awesome work, btw didn't tested it yet, i have a suggestion that can improve it's performance for a few or even a lot of frames, the instantiation of the builder should happen only once instead of every frame, you can do that implementing it on the class constructor and reinstantiating it only if the props used on it changes
https://github.com/gev2002/react-native-vision-camera-v3-face-detection/blob/7af3a2d1033e73046a6c4315734bfa5804cff398/android/src/main/java/com/visioncamerav3facedetection/VisionCameraV3FaceDetectionModule.kt#L28-L35

awesome work, btw didn't tested it yet, i have a suggestion that can improve it's performance for a few or even a lot of frames, the instantiation of the builder should happen only once instead of every frame, you can do that implementing it on the class constructor and reinstantiating it only if the props used on it changes
https://github.com/gev2002/react-native-vision-camera-v3-face-detection/blob/7af3a2d1033e73046a6c4315734bfa5804cff398/android/src/main/java/com/visioncamerav3facedetection/VisionCameraV3FaceDetectionModule.kt#L28-L35

Thank you, I will do it soon.

Hello, I did this with my new plugins, and I will do it on these plugins when I find some free time.


Bump remote debugger to v5

I''m not quite sure the old ios driver supports the recent major changes in the remote debugger

looks good to me, but I would ask @imurchie

This will not work. The appium-ios-device package is untested for these versions of iOS. This dependency is locked in Greenkeeper for a reason.


Change the style of feature in the example of geojsonvt

Hello,
I want to change the style of feature in the VectorTile Layer. I fork the example of geojson-vt integration, and add map onclick function. This is my demo of geojson-vt, and it can't change feature style by click on map.the demo of geojson-vt

I solve the problem. This is the solution. setStyle on a pre-rendered Vector feature with ol.layer.VectorTile
Thanks!


Part-2: Add Combine and Segment Level Operators for Time Series

Building upon #13885, this PR adds support for the Combine Operator and other segment level operators. A test in QueryExecutorTest verifies that the combine operator works as expected.
I have also updated the test dataset to make it more meaningful and also add a time column to the same.
The PRs are light on test right now. Since this is rapidly evolving I am focusing on tests that test E2E functionality. I'll be improving the coverage significantly after a baseline implementation is working with a Quickstart.

Codecov Report
Attention: Patch coverage is 0% with 251 lines in your changes missing coverage. Please review.

Project coverage is 0.00%. Comparing base (59551e4) to head (2af428f).
Report is 1035 commits behind head on master.

Files with missing lines
Patch %
Lines

...ator/timeseries/TimeSeriesAggregationOperator.java
0.00%
107 Missing :warning:

...org/apache/pinot/core/plan/TimeSeriesPlanNode.java
0.00%
33 Missing :warning:

...ombine/merger/TimeSeriesAggResultsBlockMerger.java
0.00%
25 Missing :warning:

...inot/common/request/context/TimeSeriesContext.java
0.00%
16 Missing :warning:

...e/pinot/core/query/request/ServerQueryRequest.java
0.00%
13 Missing :warning:

...perator/blocks/results/TimeSeriesResultsBlock.java
0.00%
9 Missing :warning:

...erator/timeseries/TimeSeriesSelectionOperator.java
0.00%
8 Missing :warning:

...core/query/executor/ServerQueryExecutorV1Impl.java
0.00%
7 Missing :warning:

...sdb/spi/series/SimpleTimeSeriesBuilderFactory.java
0.00%
7 Missing :warning:

...ator/timeseries/TimeSeriesPassThroughOperator.java
0.00%
6 Missing :warning:

... and 6 more

:exclamation:  There is a different number of reports uploaded between BASE (59551e4) and HEAD (2af428f). Click for more details.
HEAD has 48 uploads less than BASE

Flag
BASE (59551e4)
HEAD (2af428f)

integration
7
2

integration2
3
2

temurin
12
2

java-21
7
2

skip-bytebuffers-true
3
1

skip-bytebuffers-false
7
1

unittests
5
0

unittests1
2
0

java-11
5
0

unittests2
3
0

integration1
2
0

custom-integration1
2
0

Additional details and impacted files
@@              Coverage Diff              @@
##             master   #13999       +/-   ##
=============================================
- Coverage     61.75%    0.00%   -61.76%
=============================================
  Files          2436     2540      +104
  Lines        133233   139542     +6309
  Branches      20636    21421      +785
=============================================
- Hits          82274        0    -82274
- Misses        44911   139542    +94631
+ Partials       6048        0     -6048

Flag
Coverage Δ

custom-integration1
?

integration
0.00% <0.00%> (-0.01%)
:arrow_down:

integration1
?

integration2
0.00% <0.00%> (ø)

java-11
?

java-21
0.00% <0.00%> (-61.63%)
:arrow_down:

skip-bytebuffers-false
0.00% <0.00%> (-61.75%)
:arrow_down:

skip-bytebuffers-true
0.00% <0.00%> (-27.73%)
:arrow_down:

temurin
0.00% <0.00%> (-61.76%)
:arrow_down:

unittests
?

unittests1
?

unittests2
?

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@ankitsultana There are couple of tests failing https://github.com/apache/pinot/actions/runs/10860622852/job/30141445761?pr=13999 Are these related or unrelated?


refactoring and clean-up

added/fixed various export comments
fixed up receivers by-val and by-ref
implemented stateless policies as first-class funcs
rewrote the retry policy to be generic and always retry on errors

[ ] The purpose of this PR is explained in this or a referenced issue.
[ ] The PR does not update generated files.

These files are managed by the codegen framework at Azure/autorest.go.

[ ] The PR targets the latest branch.
[ ] Tests are included and/or updated for code changes.
[ ] Updates to CHANGELOG.md are included.
[ ] Apache v2 license headers are included in each file.

Can one of the admins verify this patch?


publish to npm

NPM is becoming the standard way to distribute JavaScript-based code libraries, both browser-based and server-based.  It would be great if heatmap.js was available on npm as well.  And it's pretty simple to do this.  I made it even easier in this pull request.  Simply run grunt publishToNpm.

+1 for this!

thank you for your contribution, it's now available on npm :)


Remove polling from sample unit request

Motivation and Context
Sample service no longer inserts something into the database which is
later polled and actioned on. The changes should be backwards
compatible as the API should allow fields that are not defined.
What has changed
Remove polling
How to test?
All acceptance tests and integration tests should still pass
Links
https://trello.com/c/45IDo0nJ/129-remove-polling-mechanism-from-sample-service

Superseded by changes @NickGrantONS is making


Unable to connect to payed Heroku database

The standard-0 Postgres database from Heroku requires to have ssl enabled. Therefore, when configuring the app with .postgres(url:) I added the sslmode=require to the URL.
if let urlString = Environment.get("DATABASE_URL") {
    url = URL(string: urlString + "?sslmode=require")
}

Now, when the vapor application tries to connect to the DB, the connection is revoked because of this: sql_error_code = 08P01 LOG:  could not accept SSL connection: tlsv1 alert unknown ca
In vapor 3, there was the unverifiedTLS transport property (https://docs.vapor.codes/3.0/deploy/heroku/#configure-the-database)
How can I achieve a valid connection to the database?

vapor 4.5.1
fluent-postgres-driver 2.0.0-rc.2
postgres-kit 2.0.1
swift 5.2.2

You can disable certificate verification when you configure the database. E.g.:
app.databases.use(.postgres(
    hostname: Environment.get("DATABASE_HOST") ?? "localhost",
    username: Environment.get("DATABASE_USERNAME") ?? "vapor_username",
    password: Environment.get("DATABASE_PASSWORD") ?? "vapor_password",
    database: Environment.get("DATABASE_NAME") ?? "vapor_database",
    tlsConfiguration: .forClient(certificateVerification: .none)
), as: .psql)


iPadAir4 screen ratio is not correct??

Hello,
It seems that the screen ratio of iPad Air 4th is not correct.
// case .iPadAir4: return (width: 3, height: 4)
Is it exactly the same as the iPad Pro 11, right?
case .iPadPro11Inch: return (width: 139, height: 199)

Oh my mistake...
After calculating it, the aspect ratio of iPad Air (4th generation) is 41 : 59. I will push a PR to fix it.


Scope for DialOutPolicy

Hello,
could I get clarification on the desired scope for the DialOutPolicies please?
For Skype we could apply matching patterns on voice routes that would work for us for Call Restrictions.
For Teams we are doing the same thing (for TDR, as we have the same mechanics available).
Are the CsDialOutPolicy intended to provide this functionality for Microsoft Calling Plans or can/should they be used for TDR as well?
Thanks,
David

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

ID: fab4e86c-f8f6-36fa-874c-756e5a88f0ae
Version Independent ID: 307f2569-889a-b887-9536-d91d26fe184e
Content: Get-CsOnlineDialOutPolicy (skype)
Content Source: skype/skype-ps/skype/Get-CsOnlineDialOutPolicy.md
Service: skypeforbusiness-powershell
GitHub Login: @tomkau
Microsoft Alias: tomkau

@officedocsbot assign @yogkumgit

@pupara Please help us in resolving this issue. Thanks.

@pupara @tomkau can you please help us confirm if this cmdlet is only intended for Calling Plans? AFAIK it is not used on DR scenarios. Thank you

@pupara Please update. cc @Kateyanne

@DEberhardt David, have you seen this article? https://docs.microsoft.com/en-us/microsoftteams/outbound-calling-restriction-policies

Hello,
I think I have had read the article. Re-reading it, I note that:

It does not tell anything about support with/for Direct Routing
It does mention rules not being able to be customized
It does not list the restriction level with enough clarity to be useful (Does domestic include Emergency services calls if they are routed via the Voice Routing Policy...?)

All of the above drive previously established behaviors (i.E. adding matching patterns on Voice Routes) to facilitate Outbound voice routing.
PS: The same is true for the Calling Line Identity - Using a CLI Policy results in multiple diversion headers which generates call drops upstream (only one header allowed, Teams currently sends two). Granted, this will need more investigation with the Carrier, but is currently blocking use of the policy

Hello @DEberhardt David, I could get more information that this cmdlet also affects DR.

@yogkumgit I think you can close this thread now.


GH-4431: Replace WireMock with MockServer

GitHub issue resolved: #4431
Briefly describe the changes proposed in this PR:
This PR migrates all use of WireMock in the codebase to MockServer. MockServer is built on Netty, and provides no-dependency shaded jars, which will ease upgrading Jetty (https://github.com/eclipse/rdf4j/issues/4252), upgrade Java/Jakarta EE and migrate from Java EE to Jakarta EE (https://github.com/eclipse/rdf4j/issues/3559).
The MockServer code is a bit more verbose, but fairly equivalent to WireMock. MockServer lacks the ability to load mocked response bodies from file, so in order to not change "everything" in this PR, I added small utility methods to adapt this missing feature. This can be changed/improved in a follow-up PR.

PR Author Checklist (see the contributor guidelines for more details):

[x] my pull request is self-contained
[ ] I've added tests for the changes I made
[x] I've applied code formatting (you can use mvn process-resources to format from the command line)
[x] I've squashed my commits where necessary
[x] every commit message starts with the issue number (GH-xxxx) followed by a meaningful description of the change

The CI failure seems unrelated and probably a flake. Is there a way for regular users to trigger a re-run of failing workflows?


Displacement field transform in 3D

temp is a forward 3D displacement field of size DxMxNx3.
displacement_image = sitk.GetImageFromArray(np.double(temp),sitk.sitkVectorFloat64)
tx = sitk.DisplacementFieldTransform(displacement_image)
tx.SetInterpolator(sitk.sitkLinear)
I find the inverse transform using the code below:
sitk_inverse_displacement_field = sitk.InvertDisplacementField(tx.GetDisplacementField())
tx1 = sitk.DisplacementFieldTransform(sitk_inverse_displacement_field)
tx1.SetInterpolator(sitk.sitkLinear)
Using the inverse transform and a resampler I transformed a 3D volume.
using the same inverse transform i also transform a set of  K 3D points (X,Y,Z) spread uniformly across the surface of the volume.
px, py, pz =tx1.TransformPoint((x_points,y_points,z_points))
When i plot the transformed volume and points on paraview, they don't align. can you please help in explaining what i am doing wrong.

Closing this issue as it was cross posted on ITK discourse. See discussion there.


Some JS optimizations

After moving JS calculation of a prime number into a separate function the code began to execute faster - from 2.41s to 0.31s on my machine.

No, you change test logic.
Examples:
Current logic: if number = 6 - we check each numbers: 1, 2, 3, 4, 5, and 6
Your logic: if number = 6 - we will check only 2 first numbers: 1, 2. As result you will get huge performance improvement


ScriptContext.now() is undefined

I am attempting to do some sample Helios scripting and deploy it to Preprod.  I am looking into the minting policy scripting as found in Helios Book Chapter 3.  When I use Helios v0.6.5 (either from compiling into my source code in npm or using the playground as in the attached photo) I get the following error:
ReferenceError on line 6: ScriptContext.now undefined

Please advise on how to proceed.

Looks like the ScriptContext object does not have the now() method the Tx does:
https://hyperion-bt.github.io/Helios-Book/chapter_2/03_ScriptContext.html
Looks to be a doc fix for chapter 3.

Where did you see that now was a member of ScriptContext?

The first link (chapter 3).

On Sep 27, 2022, at 1:19 PM, christianschmitz @.***> wrote:

Where did you see that now was a member of ScriptContext?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.

I've corrected the documentation.
If you are happy with the changes I will close this issue
Next time issues with the documentation should probably be posted under the Helios-Book repository instead.

Will do thanks!


remove unused parameter in mapParams and Observation.mapParams

This PR removes the unused "inverse mapping" t -> i from mapParams.
In fairness, we could entirely remove the time parameter t from Observation t x a as the time dependency is always implicit (in a) and introduced when the observation is "reified".
I am however unsure whether removing the time parameter from observation is desirable as it is intuitive to have that type parameter there. Moreover, we might wish to introduce observations that depend explicitly on-time going forward.
Happy to hear your thoughts @lucianojoublanc-da.
This is a breaking change.

So on further though, I recall that at some point Observable (or Observation) implemented a Haskell Arrow instance (so you could use Claim with a pure function, instead of Observation). And as mentioned in a separate thread, t is present in Inequality now, which didn't exist before.

I am closing this PR for now, as we might want to consider adding time-explicit observations at some point in the future. Hence I'd rather not apply a breaking change that might be reverted at some point.
If, on the other hand, you think this improves user experience, happy to reopen it.


Remove Apocalypse code

Now that the Master Sword is no longer offered, this commit can be reverted.

Shouldn't we keep it if we need some other item to show off?  It seems a waste just to get rid of it when it's likely we'll be offering another item at some point.

I need to modify the code to keep around some of the logic for showing off items and highlighting levels, so let me figure it out.

I say this, because the Apocalypse is highlighted with the particles and has the Master Sword in it's circle (it is a little bit misleading).


Brave browser blocks flagsmith/react requests to api

When shields up in Brave, flagsmith cannot fetch the features from api. So that i cannot use the feature flagging properly.

I searched docs and issues but cannot find anything about network blocking issue. I am expecting feature flag operations should not be blocked by any adblocker.
Is there any option to prevent blocked by ad blockers or is it just a bug?
gz#70

This looks like brave is blocking requests to localhost - there's nothing we can do about this. You will need to allow that in your browser.


Port substrate-developer-hub/knowledgebase#26

!!! NOTICE !!!
All documentation has been moved to the Knowledge Base. Please make your PR there.
https://github.com/substrate-developer-hub/knowledge-base/

@danforbes how to add to users section on this new repo that you mention?

@siman - you should be able to follow the normal Pull Request workflow to update the new Knowledge Base repo.

@siman https://github.com/substrate-developer-hub/substrate-cms/blob/master/pages/substrate-users.json


[Question] Does IORedis send multiple requests concurrently?

If I run two successive commands like so:
redis.set('key1', 'val1');
redis.set('key2', 'val2');

Does the second command get sent to redis only after the reply from the first command has been received by the client?
Or does the client send both commands concurrently?

Sorry for the late response. They are sent to Redis server concurrently.


Include configuration.ts in state/index

@darthtrevino,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Support for passing authorization header

We can configure graphql URL, can we also indicate authorization header to pass JWT token?

You can do that with the fetchOptions option when setting up your client. Probably the functional style. Did you have a different way in mind?

Not really. I missed the fetchOptions part. All is good :)


zef: 0.21.2 -> 0.21.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ugexe/zef/releases.
meta.description for zef is: Raku / Perl6 Module Management
meta.homepage for zef is: https://github.com/ugexe/zef
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.21.3 with grep in /nix/store/5y7p138aw85fdzlrngfgrbdk6j52v0as-zef-0.21.3
found 0.21.3 in filename of file in /nix/store/5y7p138aw85fdzlrngfgrbdk6j52v0as-zef-0.21.3

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
zef

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/5y7p138aw85fdzlrngfgrbdk6j52v0as-zef-0.21.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A zef https://github.com/r-ryantm/nixpkgs/archive/e1dee8bd49a63c0f3ecfca7c5f953f777399b413.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/e1dee8bd49a63c0f3ecfca7c5f953f777399b413#zef

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/5y7p138aw85fdzlrngfgrbdk6j52v0as-zef-0.21.3
ls -la /nix/store/5y7p138aw85fdzlrngfgrbdk6j52v0as-zef-0.21.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

zef

Maintainer pings
cc @stigtsp for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ugexe/zef/releases.
meta.description for zef is: Raku / Perl6 Module Management
meta.homepage for zef is: https://github.com/ugexe/zef
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.21.4 with grep in /nix/store/lizwchrqm2aicz69iz09l7nxrg2x7s71-zef-0.21.4
found 0.21.4 in filename of file in /nix/store/lizwchrqm2aicz69iz09l7nxrg2x7s71-zef-0.21.4

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
zef

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/lizwchrqm2aicz69iz09l7nxrg2x7s71-zef-0.21.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A zef https://github.com/r-ryantm/nixpkgs/archive/47845c94add899ec9d8fe98b13c60eeaac248e3d.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/47845c94add899ec9d8fe98b13c60eeaac248e3d#zef

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/lizwchrqm2aicz69iz09l7nxrg2x7s71-zef-0.21.4
ls -la /nix/store/lizwchrqm2aicz69iz09l7nxrg2x7s71-zef-0.21.4/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

zef

Maintainer pings
cc @stigtsp for testing.


chore: create Algebra/Module/LinearMap/Basic in preparation of splitting

chore: create Algebra/Module/LinearMap in preparation of splitting
adjust imports

bors merge


add correct sha details for semaphoreapp

I'm using semaphoreapp for CI and some non-insignficant fraction of the time the message I get from slack is for a really old commit and I'm confident that that the test run didn't use this commit.  I'm not sure how coveralls figures out the correct commit but semaphoreapp is supposed to provide it in environment variables and it looks like there is code to use that sort of setup for a number of CI providers.  This pull request just adds the same for semaphoreapp.

Coverage increased (+0.06%) to 91.04% when pulling b46f741fcc2e83fa66c334b370c1f481ce8e16f1 on dontfidget:semaphoreapp into 409735b8c5d51dd2e2a92c585b9ef14a73a85499 on lemurheavy:master.

Thanks @dontfidget!

While I think this is setting the correct sha explicitly, it appears that coveralls is still occasionally sending me a message with the wrong sha.  Any idea how that could be happening?

@dontfidget ok do you know if the incorrect SHA is coming from Semaphore's environment variables? or is it the gem checking the local git status?

I wasn't using semaphore's environment variables before this pull request,
so this behavior has nothing to do with my change. I could be my change
isn't doing what I expect it to do, and that it's still getting the sha
some other way.  It doesn't break anything but it isn't really tested (not
are the settings for any other providers for that matter).
On Thu Feb 05 2015 at 3:20:23 PM Nick Merwin<EMAIL_ADDRESS>wrote:

@dontfidget https://github.com/dontfidget ok do you know if the
incorrect SHA is coming from Semaphore's environment variables? or is it
the gem checking the local git status?
—
Reply to this email directly or view it on GitHub
https://github.com/lemurheavy/coveralls-ruby/pull/76#issuecomment-73151455
.

Ok, I haven't tested on Semaphore in quite some time. Could you keep an eye
on it and let me know if you find the cause? I'll update the gem / docs
accordingly.
On Thu, Feb 5, 2015 at 4:03 PM, Andrew Brown<EMAIL_ADDRESS>wrote:

I wasn't using semaphore's environment variables before this pull request,
so this behavior has nothing to do with my change. I could be my change
isn't doing what I expect it to do, and that it's still getting the sha
some other way. It doesn't break anything but it isn't really tested (not
are the settings for any other providers for that matter).
On Thu Feb 05 2015 at 3:20:23 PM Nick Merwin<EMAIL_ADDRESS>wrote:

@dontfidget https://github.com/dontfidget ok do you know if the
incorrect SHA is coming from Semaphore's environment variables? or is it
the gem checking the local git status?
—
Reply to this email directly or view it on GitHub
<
https://github.com/lemurheavy/coveralls-ruby/pull/76#issuecomment-73151455

.

—
Reply to this email directly or view it on GitHub
https://github.com/lemurheavy/coveralls-ruby/pull/76#issuecomment-73156723
.

--
Nick Merwin
LEMUR Heavy Industries
p<PHONE_NUMBER> | c<PHONE_NUMBER> | lemurheavy.com http://lemurheavy.com/


Portal-Screenshot update required for design site menu

Open https://developers.sap.com/tutorials/cp-portal-cloud-foundry-create-site.html
Step 3- Design the site menu
Remark- Screenshot update required.
Actual

Expected

Hi, I do not understand the difference between expected and actual screenshots - can you please explain?

@IrisSasson I think @Mukesh-50 is referring to the Translation tab that is missing in the "expected" screenshot.

Hi
We are planning to update all tutorials at the end of this month
Thanks for your comment
Iris

Hi,
All tutorials were replaced with Launchpad tutorials. Please use the Launchpad service tutorials instead

Thank you for your feedback. The issue seems to be resolved, so I am closing the issue.
If you still have questions, feel free to reopen the issue.


Add codecov

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@c576909). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #6   +/-   ##
=======================================
  Coverage        ?   95.71%
=======================================
  Files           ?       25
  Lines           ?      373
  Branches        ?        0
=======================================
  Hits            ?      357
  Misses          ?        8
  Partials        ?        8

Continue to review full report at Codecov.

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

Merged manually


Transform_vis_6.0.0 support for Kibana 6.0.1

Hi,
Will Transform_vis_6.0.0 will be supported for Kibana version 6.0.1?
Thanks,
Jan

As per @PhaedrusTheGreek answer for issue #14 : "you can build it easily on your own if you like - download the 6.1.1 zip , open it up, modify package.json to set the version numbers to your current Kibana version, then re-zip it"


Enhancement: Confirmation for muting notifications when muting user

when muting a user, Mastodon asks whether to mute notifications as well. Default is TRUE, personally I prefer it on FALSE 99% of the time. Is there a way to introduce this option/confirmation window?

Hi, I'll look into this when I have some spare time, thx


API doc : some more function doc added

... painful
my day contribution to the Cause

And the Cause thanks you :)


SWARM-447 StageConfig CDI integration rework

make ConfigValue a qualifier
replace ConfigExtension with producers
remove Configured
add ConfigValueProducer test

Unlike the original solution:

let the CDI container perform the injection (@ConfigValue qualifier must be used together with @Inject)
allow to use constructor injection and initializers
allow to inject Resolver<String> if custom conversion is needed
see also ConfigValueProducerTest for examples

Cool, looks good to me. Have you tested it with the config examples?

Have you tested it with the config examples?

No, I have no idea how to do it ;-)

All you need to do is to build core with your changes and then run mvn clean verify on the examples: https://github.com/wildfly-swarm/wildfly-swarm-examples

You can also shortcut the examples by doing:

cd base mvn clean install
cd ../config-options mvn clean verify

These are the tests that should pass: https://github.com/wildfly-swarm/wildfly-swarm-examples/tree/master/config-options/cdi-injection

The reason for running the examples is that they verify specific class loading combinations

These are the tests that should pass...

These will have to be fixed - @Configured is removed and injection points require @Inject now.


Trigger filament change event so other plugins can react

This PR triggers the FILAMENT_CHANGE event similar to what OctoPrint does when an M600 is detected. This allows other plugins to react to the filament change request, in my case the OctoApp companion plugin will send a push notification to alert the user.
Change was tested by the user reporting the missing notification and confirmed working.

Is this mod abandoned?

Seems so :(

Ok, that is too bad.. Reported it to github.

Any other good (and not abandoned) filament sensor you know off?

No not completely but I have been very busy i would also recommend run the sensor using the printer own firmware.

Sorry, there are things higher in my priority list than this, will find spare time to look at your PR.

@LazeMSS @LuckyX182 Thanks! Please also look at the one i reported.


Use /etc/mime.types to set Content-Type accordingly

My server created bunch of css files automatically and they got written to S3 with Content-Type:binary/octet-stream, which is the default.
It would be nice if goofys could guess MIME type and set the header accordingly (same as s3fs does it).

#60

Yes, please. This can actually be a pretty big problem.
In python, the known mimetypes could be read into a dict as follows:
with open('/etc/mime.types') as mimetypes_file:
    mimetypes = {}
    for line in mimetypes_file:
        if len(line.split('\t')) > 1:
            extensions = line.split('\t')[-1].split()
            for ext in extensions:
                mimetypes[ext] = line.split('\t')[0]

Is the best workaround for this right now using a custom AWS lambda function to act whenever a new file appears in a bucket?

Excellent, thanks!


First commit of ADSArxiv direct_ingest_pipeline worker with test cases

This version of ADSArxiv can be integrated with seasidesparrow/eb-deploy (the direct_ingest_pipeline) to add daily ArXiv updates directly into Solr via master_pipeline.
Test cases are currently passing and covering almost everything.  However, I need to figure out how to test the execution of ADSArxiv.tasks.task_output_results -- nothing I've tried has worked yet.

Closing: not pursuing this development path.  Arxiv and other direct importers will be added to ADSImportPipeline instead, with functionality from adsabs-pyingest.


Mutual guilds implementation on the User class

Please describe the changes this PR makes and why it should be merged:
This PR implements a mutualGuilds property in the User class.
How it works: it returns the guilds collection containing guilds where the User is on.
I know we can get the same thing in the fetchProfile method but that's something we would like to get implemented on d.js because it is already in a lot of other librairies for Discord without needing of fetching profile (so having a user account).
Semantic versioning classification:

[X] This PR changes the library's interface (methods or parameters added)

[ ] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)

[ ] This PR only includes non-code changes, like changes to documentation, README, etc.

Working example

Cool! :P

im not quit sure if this is needed since you can do it yourself when you need it with an extension of the D.js class or by just filtering the guild collection like you did there :thinking:

True, but I think anything nice that could help is welcome ^_^

This helper method really isn't needed. You can see yourself that this is a one-liner.


OVS-DPDK support

The copyright dates on all the new files should be updated to 2018

I diffed the mode1 and mode2 4_port NIC configs, and they are identical.  Since they are the same, we should eliminate one of them and call it something like "compute-oovs-dpdk.yaml".
The same is true for the mode 1 and mode 2 5_port NIC configs.

I think that instead of modifying the existing NIC configs that we should create 2 new dpdk 4_port and 5_port nic configs.  This would allow us to replace the changeme tokens in the added compute NIC config files with actual variable names and then add those variables to a new nic_environment.yaml.  Taking this approach will take advantage of the standard NIC configuration mechanism.

There should a check on features dependencies associated with ovs-dpdk . Profile already enforces that, but in case of a custom profile  we still want to make sure that if ovs-dpdk is enabled, numa and hp also are. ( in settings_sanity.py possibly , but also deploy-overcloud.py for manual deployments)

We should delete the dpdk_4_port and dpdk_5_port nic_configs since these are no longer needed.


Added the initial patches for the 4.11 kernel

Added the initial patches for the 4.11 kernel

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


0 libraries currently shown in the UI

Not sure if it’s an error in the code or the delivery of the packages

It might be that you exceeded the github api limit at one point, but that would surprise me, since it caches the results for every session.
I really should check this project more often 😅


test.concurrent - buffered console messages

Do you want to request a feature or report a bug?
feature
What is the current behavior?
Console messages from tests executed with test.concurrent are intermingled.
If the current behavior is a bug, please provide the steps to reproduce and
either a repl.it demo through https://repl.it/languages/jest or a minimal
repository on GitHub that we can yarn install and yarn test.
n/a
What is the expected behavior?
Console messages are buffered and printed together with individual test functions similar to how they are for parallelized test files but at the individual test function level.
Please provide your exact Jest configuration and mention your Jest, node,
yarn/npm version and operating system.
jest 21.2.1
node 6.12.0
npm 3.10.10
Windows 10.0

test.concurrent is currently not documented or supported well. It has the gotchas you are describing and it's unlikely we'll fix them anytime soon without completely redoing the test framework within Jest. I'll close this as wontfix for now because nobody is actively working on this.


Release 0.0.3 version of microcks-spectral-ruleset

Tag on GitHub and push on NPM

Is has been release here<EMAIL_ADDRESS>


jumanpp: init at 1.02

Motivation for this change
Adds JUMAN++, a morphological analyzer for Japanese.
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg build jumanpp

Failure on aarch64-linux (full log)
Attempted: jumanpp
Partial log (click to expand)
g++: error: unrecognized command line option '-m64'
make[3]: *** [Makefile:486: charlattice.o] Error 1
make[3]: Leaving directory '/build/jumanpp-1.02/src'
make[2]: *** [Makefile:519: all-recursive] Error 1
make[2]: Leaving directory '/build/jumanpp-1.02/src'
make[1]: *** [Makefile:347: all] Error 2
make[1]: Leaving directory '/build/jumanpp-1.02/src'
make: *** [Makefile:473: all-recursive] Error 1
builder for '/nix/store/712x4wx1ndx0vsbcz9anly1pwwzizg7k-jumanpp.drv' failed with exit code 2
error: build of '/nix/store/712x4wx1ndx0vsbcz9anly1pwwzizg7k-jumanpp.drv' failed

Success on x86_64-darwin (full log)
Attempted: jumanpp
Partial log (click to expand)
 /nix/store/5lkrw9dnsgy62qm1ampvww1c5n1pdm4b-coreutils-8.29/bin/install -c -m 644 jumanpp-resource/dic.base jumanpp-resource/dic.bin jumanpp-resource/dic.da jumanpp-resource/dic.form jumanpp-resource/dic.form_type jumanpp-resource/dic.imis jumanpp-resource/dic.pos jumanpp-resource/dic.read jumanpp-resource/dic.rep jumanpp-resource/dic.spos jumanpp-resource/feature.def jumanpp-resource/freq_words.list jumanpp-resource/lang.mdl jumanpp-resource/lang.mdl.nnet jumanpp-resource/version jumanpp-resource/weight.mdl '/nix/store/vz8kxf7rs8913d6yig9dz1gxcyfzbzxg-jumanpp/share/jumanpp'
 /nix/store/5lkrw9dnsgy62qm1ampvww1c5n1pdm4b-coreutils-8.29/bin/mkdir -p '/nix/store/vz8kxf7rs8913d6yig9dz1gxcyfzbzxg-jumanpp/share/jumanpp'
 /nix/store/5lkrw9dnsgy62qm1ampvww1c5n1pdm4b-coreutils-8.29/bin/install -c -m 644 jumanpp-resource/lang.mdl.direct jumanpp-resource/lang.mdl.map jumanpp-resource/lang.mdl.nnet.map jumanpp-resource/weight.mdl.map jumanpp-resource/dic.base.map jumanpp-resource/dic.form.map jumanpp-resource/dic.form_type.map jumanpp-resource/dic.imis.map jumanpp-resource/dic.pos.map jumanpp-resource/dic.read.map jumanpp-resource/dic.rep.map jumanpp-resource/dic.spos.map '/nix/store/vz8kxf7rs8913d6yig9dz1gxcyfzbzxg-jumanpp/share/jumanpp'
make[2]: Leaving directory '/private/tmp/nix-build-jumanpp.drv-0/jumanpp-1.02'
make[1]: Leaving directory '/private/tmp/nix-build-jumanpp.drv-0/jumanpp-1.02'
post-installation fixup
strip is /nix/store/kdff2gim6417493yha769kh00n63lnrw-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/vz8kxf7rs8913d6yig9dz1gxcyfzbzxg-jumanpp/bin
patching script interpreter paths in /nix/store/vz8kxf7rs8913d6yig9dz1gxcyfzbzxg-jumanpp
/nix/store/vz8kxf7rs8913d6yig9dz1gxcyfzbzxg-jumanpp

Success on x86_64-linux (full log)
Attempted: jumanpp
Partial log (click to expand)
make[1]: Leaving directory '/build/jumanpp-1.02'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/8x7v4qgvlk874s4hvx489zmy7dxxj0qk-jumanpp
shrinking /nix/store/8x7v4qgvlk874s4hvx489zmy7dxxj0qk-jumanpp/bin/jumanpp
shrinking /nix/store/8x7v4qgvlk874s4hvx489zmy7dxxj0qk-jumanpp/bin/mkdarts_jumanpp
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/8x7v4qgvlk874s4hvx489zmy7dxxj0qk-jumanpp/bin
patching script interpreter paths in /nix/store/8x7v4qgvlk874s4hvx489zmy7dxxj0qk-jumanpp
checking for references to /build in /nix/store/8x7v4qgvlk874s4hvx489zmy7dxxj0qk-jumanpp...
/nix/store/8x7v4qgvlk874s4hvx489zmy7dxxj0qk-jumanpp

Can you disable aarch64 for the meantime. the build system passes x86 only compiler flags.

To make it work -m64 would need to be removed. This could be reported upstream, by somebody with Japanese knowledge...

I just realized that there was a GitHub repo with much newer code (https://github.com/ku-nlp/jumanpp), I'll get that working first, so please don't merge yet :)

@Mic92 Everything should be working now (including aarch64 I assume, since the devs have switched to CMake)

@GrahamcOfBorg build jumanpp

Success on x86_64-linux (full log)
Attempted: jumanpp
Partial log (click to expand)
-- Installing: /nix/store/f4qwjq7vls79p7vs3vrymq7ljx26k7pb-jumanpp/libexec/jumanpp/jumandic.jppmdl
-- Installing: /nix/store/f4qwjq7vls79p7vs3vrymq7ljx26k7pb-jumanpp/libexec/jumanpp/jumandic.config
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/f4qwjq7vls79p7vs3vrymq7ljx26k7pb-jumanpp
shrinking /nix/store/f4qwjq7vls79p7vs3vrymq7ljx26k7pb-jumanpp/bin/jumanpp
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/f4qwjq7vls79p7vs3vrymq7ljx26k7pb-jumanpp/libexec  /nix/store/f4qwjq7vls79p7vs3vrymq7ljx26k7pb-jumanpp/bin
patching script interpreter paths in /nix/store/f4qwjq7vls79p7vs3vrymq7ljx26k7pb-jumanpp
checking for references to /build in /nix/store/f4qwjq7vls79p7vs3vrymq7ljx26k7pb-jumanpp...
/nix/store/f4qwjq7vls79p7vs3vrymq7ljx26k7pb-jumanpp

Success on x86_64-darwin (full log)
Attempted: jumanpp
Partial log (click to expand)
Install the project...
-- Install configuration: "Release"
-- Installing: /nix/store/khm8x8jnii7cdbblblpc59x6vlbpx097-jumanpp/bin/jumanpp
-- Installing: /nix/store/khm8x8jnii7cdbblblpc59x6vlbpx097-jumanpp/libexec/jumanpp/jumandic.jppmdl
-- Installing: /nix/store/khm8x8jnii7cdbblblpc59x6vlbpx097-jumanpp/libexec/jumanpp/jumandic.config
post-installation fixup
strip is /nix/store/kdff2gim6417493yha769kh00n63lnrw-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/khm8x8jnii7cdbblblpc59x6vlbpx097-jumanpp/libexec  /nix/store/khm8x8jnii7cdbblblpc59x6vlbpx097-jumanpp/bin
patching script interpreter paths in /nix/store/khm8x8jnii7cdbblblpc59x6vlbpx097-jumanpp
/nix/store/khm8x8jnii7cdbblblpc59x6vlbpx097-jumanpp

Success on aarch64-linux (full log)
Attempted: jumanpp
Partial log (click to expand)
-- Installing: /nix/store/p4fvv2hkpk69k428cf199q30sy0p4wbk-jumanpp/libexec/jumanpp/jumandic.jppmdl
-- Installing: /nix/store/p4fvv2hkpk69k428cf199q30sy0p4wbk-jumanpp/libexec/jumanpp/jumandic.config
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/p4fvv2hkpk69k428cf199q30sy0p4wbk-jumanpp
shrinking /nix/store/p4fvv2hkpk69k428cf199q30sy0p4wbk-jumanpp/bin/jumanpp
strip is /nix/store/j7d4mr0ikv974ig7yzhknpsq288js4bs-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/p4fvv2hkpk69k428cf199q30sy0p4wbk-jumanpp/libexec  /nix/store/p4fvv2hkpk69k428cf199q30sy0p4wbk-jumanpp/bin
patching script interpreter paths in /nix/store/p4fvv2hkpk69k428cf199q30sy0p4wbk-jumanpp
checking for references to /build in /nix/store/p4fvv2hkpk69k428cf199q30sy0p4wbk-jumanpp...
/nix/store/p4fvv2hkpk69k428cf199q30sy0p4wbk-jumanpp


⚠ St. Lawrence Global Observatory CKAN has degraded performance

In 76081b3, St. Lawrence Global Observatory CKAN (https://catalogue.ogsl.ca/en/) experienced degraded performance:

HTTP code: 200
Response time: 6140 ms

Resolved: St. Lawrence Global Observatory CKAN performance has improved in 3425157 after 15 minutes.


DragOverlay misplaced when sorting multiple elements

I've used the multi column multi sort example (https://github.com/clauderic/dnd-kit/pull/588) but I can't figure out how to actually get the overlay to get to the right position when removing more than one node from the list, as happens in the storybook.
https://user-images.githubusercontent.com/705677/193299052-33b7ceec-da18-4589-a25e-ea6d7c2e002e.mov
I made a minimal example here https://github.com/tozz/dnd-multisort where you can yarn start to test in your browser, the files are in src/js/ and component.tsx is the main entry point for the DnD stuff. I tried to keep the example as minimal as possible.

I am having the same problem. Were you able to solve this issue?

Unfortunately not, I moved on to other things but it would be great if someone has a fix :)

@tozz Thanks. I just found that the example at #588 was using outdated versions of the packages:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Using those versions seem to fix the problem of the cursor position. But now some things (like moving into another container are broken on my example).

Not so a good code, but I come up with a workaround.
It is how to delay updating the state on onDragStart.
In this example, delay updating filteredItems to prevent the number of items from changing.
This will help calculate the correct position.
onDragStart={e => {
  setTimeout(() => {
    doSomething()
  }, 1)
}}

Did someone find other solution to this because using setTimeout creates a lot of other issues and wrapping it with promise does not solve problem because delaying whole events like onDragEnd until execution of onDragStart breaks dnd behavior and delaying only parts of it creates yet another issues.

it would be nice to have a onBeforeDragStart where it is safe to cause rerenders without messing with the position.

same. I don't think the cursor position is wrong, the overlay should be at the current mouse dragging location.

I'm facing the same problem, fortunately the setTimeout did work for me.

Got the same issue with my horizontal list dragOverlay and i have pretty simple workaround that just shifts overlay to correct position :)
Keep in mind that this is example for horizontal list, but its very simple to modify it for the vertical list :P
`dnd-drag-overlay.tsx`

type OverlayProps = {
  activeId: string | null;
  selectedIds: string[];
};
export function DndDragOverlay({ activeId, selectedIds }: OverlayProps) {
  // To keep the cursor over the drag overlay during drag-and-drop of multiple selected Ids,
  // The drag overlay is shifted to the right and it equals to
  // The activeId index in the selectedIds array (needs to be sorted by the indexes)
  // Times the ITEM_WIDTH (or the sum of widths if they vary between items).
  const translateX = activeId && selectedIds.length > 1 ? selectedIds.indexOf(activeId) * ITEM_WIDTH : 0;

  return (
    <DragOverlay style={{ translate: `${translateX}px 0` }}>
      <Overlay activeId={activeId} selectedIds={selectedIds} />
    </DragOverlay>
  );
}

function Overlay({ activeId, selectedIds }: OverlayProps) {...}

That is how I handle select thats also sorts the selectedIds array by the indexes of the ids
You need to implement your own findItemIndex function that returns the index of the item in the array (.findIndex() method is probably what you need)
`different-file.tsx`

const handleSelect = (id: string) => {
  setSelectedIds((selectedIds) => {
    // If the selected id is already in the array, remove it and return the updated array.
    // The order of the remaining ids is preserved. (no need to sort)
    if (selectedIds.includes(id)) return selectedIds.filter((value) => value !== id);

    // If the array is empty or the selected id is from a different container than the rest,
    // return a new array with just the selected id.
    if (!selectedIds.length || findContainer(id) !== findContainer(selectedIds[0])) return [id];

    // If none of the above conditions are met, add the selected id to the array,
    // sort the array by the index of the ids, and return the sorted array.
    return [...selectedIds, id].sort((a, b) => findItemIndex(a) - findItemIndex(b));
  });
};

I'm facing the same problem, fortunately the setTimeout did work for me.
@williamisnotdefined williamisnotdefined
could you provide your example?

@ricardomejiasilva omg, sorry for the late answer, i didn't see your comment!
<DndContext
      ...
      onDragStart={(event) => {
        /**
         * This tricky timeout is needed
         * to prevent the overlay from being misplaced
         * in relation to the mouse cursor
         */
        setTimeout(() => {
          handleDragStart(event);
        }, 1);
      }}
      ...
>

Not so a good code, but I come up with a workaround. It is how to delay updating the state on onDragStart.
In this example, delay updating filteredItems to prevent the number of items from changing. This will help calculate the correct position.
onDragStart={e => {
  setTimeout(() => {
    doSomething()
  }, 1)
}}

@megos I found a better way, we dont need and we shouldn't use setTimeout as @kamilkazmierczakMtab has mentioned, I fixed the case by adding the modifier snapCenterToCursor
<DndContext
      sensors={sensors}
      collisionDetection={closestCenter}
      onDragStart={handleDragStart}
      onDragEnd={handleDragEnd}
      onDragCancel={handleDragCancel}
      modifiers={[snapCenterToCursor]}  // << it should fix the case, if I am not mistaken
      measuring={{
        droppable: { strategy: MeasuringStrategy.Always },
      }}
    >


Updated daily animations (data from 3 days)

Daily animations are now generated from data that was collected 3 days ago.
This avoids generating videos that are incomplete.

Forgot to merge this so messed up a few days of animations.


feat: allow chartPath to be set from env with CHART_PATH

In CI/CD I have multiple versions of the same chart equal to the name of branches, e.g. charts/production and charts/staging. When the pipeline runs on staging I want the chartPath to be charts/$PIPELINE_BRANCH and that Chart.yaml to be updated. Following that logic I can use { .Chart.Version } to correspond with the correct version on the release channel
Signed-off-by: Sjouke de Vries<EMAIL_ADDRESS>

I made a MR for this in your plugin instead of replicating https://github.com/nflaig/semantic-release-helm/blob/master/lib/prepare.js#L8-27 in a separate plugin. Currently I have a script with yq that handles this logic for me.


Not enough contrast when selecting title or text in search box

(copied from Obsidian forum)
Love this theme! Thank you so much for it.
I’m trying to change one thing and I can’t figure it out.
When I select text it highlights with the secondary colour (I believe) which is great. However, that doesn’t seem to apply to the title or the search box.  I’m not sure where or how to specify a different bg colour when these items are selected.

I've been doing some customizations on the Nord theme for myself. One of the biggest drivers was not being able to tell when text was highlighted in search boxes.
What I've learned is that something in Obsidian is causing the --text-selection variable to shift to a darker shade in areas outside editor panes. It's less noticable in other themes and with other colors, but for some reason is extreme with Nord.
I haven't been able to figure out what the cause is. I've scoured the CSS in several themes and in app.css and nothing there seems related. Changing the background of CSS ::selection to a different value works outside editor panes but the color is still darker than normal. It doesn't effect content in editor panes at all. I'm guessing Obsidian is parsing the --text-selection value and applying it separately in Prism.

This was fixed in a prior commit. The highlighting should be more noticeable now.


:packadd doesn't source files from "after" directory inside "opt" directory

Steps to reproduce:

install https://github.com/msanders/snipmate.vim to pack/foo/opt
vim --clean
packadd snipmate.vim
check :scriptnames
pack/foo/opt/vim-snipmate/after/plugin/snipMate.vim is not sourced

If I move plugin to pack/foo/start/ everything it's sourced properly.

Steps to reproduce:

install https://github.com/msanders/snipmate.vim to pack/foo/opt
vim --clean
packadd snipmate.vim
check :scriptnames
pack/foo/opt/vim-snipmate/after/plugin/snipMate.vim is not sourced

If I move plugin to pack/foo/start/ everything it's sourced properly.

The "after" directory isn't explicitly used, it is added to the
'runtimepah' and directories found there found later.  Since by the time
you use your :packadd command startup already finished, Vim won't go
looking for plugins there.
I understand that you would expect a package to work the same, no matter
if they are under "start" or "opt".
--
I recommend ordering large cargo containers of paper towels to make up
whatever budget underruns you have.  Paper products are always useful and they
have the advantage of being completely flushable if you need to make room in
the storage area later.
(Scott Adams - The Dilbert principle)
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

:packadd already has logic to :source the added scripts from the plugin and ftdetect subdirs here. I think what's missing is that after/plugin should be considered and :sourced, too.

But is there a valid use case for an after directory within a plugin? After directories are for sysadmins and personal user overrides, AFAIK (see :help after-directories).
SnipMate (ab)uses it to override the mappings of other plugins (SuperTab), which IMHO is an anti-pattern.

Since it's somewhat debatable whether this is a bug, I've opened #15584 to request that the functionality be added. Maybe this issue could be closed?

Let's close this one here then as duplicate


Add referrer header to requests

This feature will implement an optional referrer field to all requests.  The value will default when not populated.

Instructions from Slack (13.dec.21)

We're probably going to need to restructure the code a bit since there is already an optional parameter.
So it will need to accept an optional configuration object instead.
We can default it to 'dora-ts' with the ability to override.
This merge pattern is how I recommend implementing:

https://github.com/CityOfZion/props/blob/develop/sdk/src/Collection.ts#L10

@lllwvlvwlll Is this issue still relevant?

Its still relevant and helpful for tagging api usage.


Add options for silence cutoff and individualized thresholds

For our project, we found that using the current 'silence' parameters was insufficient - we needed some cases where we could allow a pause of longer than 1s before recording was cut off, and we wanted the activation threshold to be different from the cutoff threshold.
I added additional options to support this, with defaults.
Additionally, the current option for threshold, if provided, will still continue to work as it does in the existing version and apply to both activation and cutoff.

LGTM, probably makes #11 and #14 obsolete but I'm more in favor of this approach since it splits up the thresholds into separate params.


[KeyVault] KeyVault already supports abortSignal, so I added a test

Since KeyVault already supports abortSignal:

Should we add tests for some of the API calls with abortSignal?

In case we should test abortSignal, what API calls should we test? (or should we test all of
them?)
In case we should test abortSignal, remember that this PR is missing the recording files,
so I would need to generate them before we merge this.

Should we do the same for keyvault-certificates?

Fixes #4183

I'm not sure we have abortable long-running operations for keys/secrets. I know certificates has some I think quality. But that's just my vague recollection, @bterlson and @schaabs would probably know more.

@jonathandturner We do not have long running operations, other than network calls. What this means is that we don't need to change our API, but it is also true that our API still supports abortSignal. Having the option to cancel an HTTP useful everywhere for the same reasons! Having said that, should we add tests and samples displaying this feature? If not, I guess that's fine, but I don't generally favor undocumented features.

I think KeyVault has a long running operation when you manually sign something, but I might be wrong.


Add all files to the zip

Custom Hotbar now consists of index.js, custom-hotbar-populator.js and custom-hotbar.js. They all need to be included in the zip.

always helpful


Incompatibility with main constructor

Hello,
Your extension is fixing one of the major issue I have with vscode, but unfortunately it doesn't seem to work when we are using main constructors.
Here is a simple example :

If we use the Extract interface feature, we get :

But we should get something like this :

Or even :

Maybe it's just a configuration I'm missing?
Thanks for your work!

Hi @maximeozenne,
Thanks for pointing that out. I will try to fix it within couple of days.

It works! Thank you very much @hmn53!

Hi again @hmn53,
Sorry to bother you again, but it seems like it's not working as expected
2 issues here :
First, the bracket is not at the right place when the main constructor is on several lines :

The bracket, which was on the next line before using the Extract interface option, was put back at the end of the line, after the interface name
Second, the interface is created, but is totally empty, even if the original class contains public methods :

Can you please take a look at it?
Thanks for your reactiveness and again, thanks for your work!

Hi @maximeozenne ,
Can you give an example for a class where the interface is empty?

Hi @hmn53,
Sure!
First, will writing an example for you, I've seen that the extraction was working with synchrnous methods.
But the issue seems to come from asynchronous methods.
Here is a simple example :
public class TestService(
    IMapper mapper,
    ILogger<TestService> logger)
{
    public async Task Test()
    {
        await Task.Run(() => Console.WriteLine("Test"));
    }

    public async Task Test2()
    {
        await Task.Run(() => Console.WriteLine("Test2"));
    }
}

Which gives this interface, after extraction :
public interface ITestService
{

}

And with the bracket just after the interface name :

Fixed. Please update and try now.
Thanks

Thank you very much!!


Prevent blocks from moving into landed blocks from the side

At the moment you can push blocks into already landed blocks by pressing left or right button

This causes another bug: sometimes line code that clears full lines (from #15) doesn't do anything when there is a full line, because there are two squares in the same place and it counts a total of width+1 squares on that line.


Fix Kosaraju

I'm afraid my previous fix wasn't quite sufficient. Unfortunately, the only test case I have contains about 10,000 nodes...

Thank you! This is going to be a part of PR #61. Keep this PR open, it should automatically close once #61 merges I think..

Ooh, that is a very nice test setup!

Released 0.2.4 with the fix. Thanks a lot for reporting & fixing.


Configure probot/stale to mark pull requests as stale.

Summary:
This uses probot to manage our pull requests.
When a pull request has seen no activity in the last seven days it is marked as staled.
A stale PR is closed after sixty days without any activity.

I agree with @unterstein - to some level.
I thought this is intended for PRs that we attempt to help to be merged, but e.g. the other side is not interested in working on it (and I think this happens in OS projects often - someone submits PR, received feedback, realizes there is much more work that would have to be put into that and just abandon the PR)
But I agree that we probably have to change the internal process too, not just merge this bot...

Let's drop it.


[nnx] split returns graphdef first

What does this PR do?
nnx.split now returns a GraphDef as the first element, and nnx.merge accepts a GraphDef as its first argument. Changes a couple of other APIs to be consistent with the new order.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 60.34%. Comparing base (9c4c8f5) to head (1739c52).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3794      +/-   ##
==========================================
+ Coverage   60.32%   60.34%   +0.01%
==========================================
  Files         101      101
  Lines       12863    12862       -1
==========================================
+ Hits         7760     7761       +1
+ Misses       5103     5101       -2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add Hashie::Extensions::Mash::SymbolizeKeys

We often have requests to make Mash symbolize keys by default. Since
Hashie is used across so many different version of Ruby, we have been
hesitant to make this behavior the default. However, there are valid use
cases for wanting symbol keys.
To satisfy both the needs of those on older Rubies and the needs of
those who want symbol keys, this extension gives the end-user the
ability to toggle on symbolized keys in their Mash subclasses. By adding
this ability, we can wait to implement the symbol keys as a default for
a while longer.
See #341, #342 for more information. This is a half-measure toward the
implementation of #342 (which makes Mash symbolize keys by default).

@zverok, how would you feel about this as a half-measure toward what you want from #342?

:+1: Looks like a wise compromise to me.

It's so clean and beautiful @michaelherold. Merging. Also I think we could subclass Mash with this and call it Smash?

The question becomes whether we want a proliferation of *ash classes. It could a smashing good time. 😂


Only one request saved when multiple called during single test

I'm having issues with multiple requests per recording. I'm testing a function which makes 2 requests (requests library) and only one of the two seems to get recorded. So the next time the test runs it throws this error:
vcr.errors.CannotOverwriteExistingCassetteException: No match for the request (<Request (GET) my_endpoint>) was found. Can't overwrite existing cassette ('/path/to/my/cassette/my_test') in your current record mode ('once').
My setup is something like this:
# conftest.py contents
test_data_dir = pkg_resources.resource_filename('mylib', 't/resources/cassettes')
vcr.default_vcr = vcr.VCR(
    cassette_library_dir=test_data_dir,
)
vcr.use_cassette = vcr.default_vcr.use_cassette

# test file contents
@vcr.use_cassette
def test_annotate_variant_success():
    run_test_with_2_calls()

I would expect all interactions during this test to get recorded but am not seeing that. I am using sessions requests for my calls and am wondering if that has an impact?

Not sure exactly what did it (path transformer?), but I got it working as needed with the following setup.
#confest.py
test_data_dir = pkg_resources.resource_filename('mylib', 't/resources/cassettes')
vcr.default_vcr = vcr.VCR(
    record_mode='once',
    cassette_library_dir=test_data_dir,
    path_transformer=VCR.ensure_suffix('.yaml'),
    filter_headers=['authorization']
)
vcr.use_cassette = vcr.default_vcr.use_cassette

# test file contents
@vcr.use_cassette
def my_test():
     run_test_with_2_calls()


Using zsh breaks terminal

Lapce Version
v0.2.0
System information
MacOS (M1) and Pop!_OS
Describe the bug
Using zsh with an oh-my-zsh theme breaks Lapce terminal. The theme is no longer represented correctly as it previously was (version working is v0.1.3), and key commands no longer function as intended. For example, backspacing does nothing and ctrl + L doesn't create newlines.
Additional information
From my Pop!_OS system, though the result is the same on my MBP with Nightly and release.

I can use ZSH (no oh-my-zsh, no special theme) without problems. What theme causes this?

I’m using the agnoster theme which is pictured. I can attach a picture of
how it should look via v0.1.3 if it helps.
On Fri, Sep 16, 2022 at 7:03 PM Matthias @.***> wrote:

I can use ZSH (no oh-my-zsh, no special theme) without problems. What
theme causes this?
—
Reply to this email directly, view it on GitHub
https://github.com/lapce/lapce/issues/1212#issuecomment-1249945889, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ANXAYHLH2DVLED7MJ3IJKVLV6UDEFANCNFSM6AAAAAAQMZSI6I
.
You are receiving this because you authored the thread.Message ID:
@.***>

I don't see anything weird using that theme. Do you have any other OMZ plugins or a custom prompt that would be causing issues?

Nope it’s just plain 🤔
On Fri, Sep 16, 2022 at 8:05 PM Matthias @.***> wrote:

[image: image]
https://user-images.githubusercontent.com/19734415/190834467-ba842f78-3330-499a-b9c8-ba21349db783.png
I don't see anything weird using that theme. Do you have any other OMZ
plugins or a custom prompt that would be causing issues?
—
Reply to this email directly, view it on GitHub
https://github.com/lapce/lapce/issues/1212#issuecomment-1249965973, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ANXAYHPHHSUU3Y54LE6ZJD3V6UKN7ANCNFSM6AAAAAAQMZSI6I
.
You are receiving this because you authored the thread.Message ID:
@.***>

Yours looks a lot better though, even 0.1.3 doesn’t look this good
On Fri, Sep 16, 2022 at 8:12 PM Chris O'Brien @.***> wrote:

Nope it’s just plain 🤔
On Fri, Sep 16, 2022 at 8:05 PM Matthias @.***> wrote:

[image: image]
https://user-images.githubusercontent.com/19734415/190834467-ba842f78-3330-499a-b9c8-ba21349db783.png
I don't see anything weird using that theme. Do you have any other OMZ
plugins or a custom prompt that would be causing issues?
—
Reply to this email directly, view it on GitHub
https://github.com/lapce/lapce/issues/1212#issuecomment-1249965973, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ANXAYHPHHSUU3Y54LE6ZJD3V6UKN7ANCNFSM6AAAAAAQMZSI6I
.
You are receiving this because you authored the thread.Message ID:
@.***>

Maybe important to note I'm on an M1 mbp, not sure if that helps at all either

Here's how it looks for me on my mac after giving it another try with the latest stable release

Here's a clean install

Here's a clean install of oh-my-zsh

@eureka-cpu how it looks other Terminals specially Alacritty as we use it as lib ?

I installed Alacritty some time ago on my Linux distro and it was working there, im not currently using it though

I'm having issues too
custom config
typeset -A ZSH_HIGHLIGHT_STYLES

# Custom ZSH config file
ZSH_AUTOSUGGEST_HIGHLIGHT_STYLE="fg=244"

# 'c' will clear the console
alias c="clear"
alias cr="clear && cd ~"

# alias for doas
alias sudo="doas"

# The Fuck, uses 'fuck'
eval $(thefuck --alias fuck)

# Color for most things
reg_color="#2196eb"

# Cursor type, bar vs rectangle, also configurable in Yakuake too
#echo -ne '\e[5 q'

# Syntax highlighting colors
ZSH_HIGHLIGHT_STYLES[command]="fg=$reg_color"
ZSH_HIGHLIGHT_STYLES[builtin]="fg=$reg_color"

# Underline paths
ZSH_HIGHLIGHT_STYLES[path]="fg=cyan,underline"

# Default stuff to cyan
ZSH_HIGHLIGHT_STYLES[default]="fg=cyan"

# Change argument color
ZSH_HIGHLIGHT_STYLES[single-hyphen-option]="fg=cyan"
ZSH_HIGHLIGHT_STYLES[double-hyphen-option]="fg=cyan"

# To differentiate aliases from other command types
ZSH_HIGHLIGHT_STYLES[global-alias]="fg=magenta,bold"
ZSH_HIGHLIGHT_STYLES[alias]="fg=magenta,bold"
ZSH_HIGHLIGHT_STYLES[suffix-alias]="fg=magenta,bold"
ZSH_HIGHLIGHT_STYLES[function]="fg=magenta,bold"

plugins
plugins=(
    git
    zsh-autosuggestions
    zsh-syntax-highlighting
)

theme
ZSH_THEME="powerlevel10k/powerlevel10k"

I'm facing the same problem, on Pop!_OS 22.04 LTS.
I'm also using oh-my-zsh.
Theme:
ZSH_THEME="robbyrussell"

Plugins:
plugins=(git docker docker-compose poetry)

Figured out the issue, it's due to the font Lapce uses by default, changing this font to something like MesloLGS NF (https://github.com/romkatv/powerlevel10k#meslo-nerd-font-patched-for-powerlevel10k) fixes the issue.

You're going to have to configure your font height to be relatively correct to your font size for certain characters to display properly, I'm using font size 14 with a height of 18

Figured out the issue, it's due to the font Lapce uses by default, changing this font to something like MesloLGS NF (https://github.com/romkatv/powerlevel10k#meslo-nerd-font-patched-for-powerlevel10k) fixes the issue.

You're going to have to configure your font height to be relatively correct to your font size for certain characters to display properly, I'm using font size 14 with a height of 18

Unfortunately this didn't work for me.
I tried the font you linked, JetBrains Mono and Fira Mono, but backspace still doesn't work in the terminal.

For me, it works now on the latest master.
I got weird font rendering first, but changing the font to a monospaced one fixed it.
At least typing, deleting characters and basic navigation works now, so ZSH is usable :)
@d-bucur maybe you can try nightly as well?


(WIP) What is AQ - updates

#hold-off

@Bradben : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@dphansen: I'm sorry - only the author of this article, @cjgronlund, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

#label:"aq-pr-triaged"


Is there any  class similar to tf.contrib.learn.monitors.ValidationMonitor in TF-Slim for evalution in logging?

I want to evaluate my model using validation data when training and show the evalution result in logging,which is similar to tf.contrib.learn.monitors.ValidationMonitor,and i can customize my metrics to evaluate.Is there any one in TF-Slim?

This question is better asked on  StackOverflow since it is not a  bug or feature request. There is also a larger community that reads questions there. Thanks!


Add fix for prop 572 code issue

Proposal 572 broke the cfmm-gamm pool links, due to the governance logic not behaving as expected (replacing a list of instead of fixing it)
Proposed for this to be included in the v19 upgrade due to urgency at hand.

devbot add changelog fix prop-572 introduced issue

e2e is failing because init genesis is not updated accordingly.
Stated to update it in: https://github.com/osmosis-labs/osmosis/pull/6280
However, I think we should merge as is and instead just test on a state exported testnet


worker: SplitClone: Handle keyspace_id changes properly.

If a row already exists on the destination with a different keyspace_id on a different destination shard, we cannot use UPDATE. Instead, we must DELETE the old row from the old destination shard and INSERT the new row to the new destination shard.
@alainjobart @enisoc @apmichaud

This change is

LGTM


Expose these two methods

So I can use them in the SNS adapter.  Any other better way?  (i.e. use an env. variable?)

that's good! waiting for travis and I'll bump

Current coverage is 88.01%

Merging #1 into master will not affect coverage as of 51c4cf6

@@            master      #1   diff @@
======================================
  Files            5       5
  Stmts          217     217
  Branches        34      34
  Methods          0       0
======================================
  Hit            191     191
  Partial          1       1
  Missed          25      25

Review entire Coverage Diff as of 51c4cf6

Powered by Codecov. Updated on successful CI builds.


can't see Compiler log

I installed miktex and latex workshop
I tried to build my tex file
they can't build it and ask me to see the compiler log, but when clicking on it, the output is empty

How is this related to VS Code?


nextjs with nile context

Merging. Will continue testing NextJS example after merge. I think (but am not sure) that I need to set context in the form action functions too.


ci: fixing workflow checks on feature/pbts

Trying to fix workflow checks on feature/pbts

PR checklist

[ ] Tests written/updated
[ ] Changelog entry added in .changelog (we use unclog to manage our changelog)
[ ] Updated relevant documentation (docs/ or spec/) and code comments
[ ] Title follows the Conventional Commits spec

Closing and the problem was on branch config