[Bug]: Recall incorrect when do vector search with filter when ground truth contains -1

Describe the bug
We're running a vector search with a filter benchmark, and the recall value is 0.01 when the ground truth neighbors contain -1. The -1 indicates non-existent values. No issues are found when the ground truth doesn't include -1.
To reproduce
PARAMS_FILE configuration for faiss-hnsw-restrictive benchmark:
{
    "target_index_name": "target_index",
    "target_field_name": "target_field",
    "target_index_body": "indices/filters/faiss-index-attributes.json",

    "target_index_primary_shards": 1,
    "target_index_dimension": 128,
    "target_index_space_type": "l2",

    "target_index_bulk_size": 100,
    "target_index_bulk_index_data_set_format": "hdf5",
    "target_index_bulk_index_data_set_path": "/home/ec2-user/data/sift-128-euclidean-with-attr.hdf5",
    "target_index_bulk_indexing_clients": 10,
    "target_dataset_filter_attributes": ["color", "taste", "age"],

    "target_index_max_num_segments": 1,
    "target_index_force_merge_timeout": 300,

    "query_k": 100,
    "query_body": {
        "docvalue_fields" : ["_id"],
        "stored_fields" : "_none_"
    },
    "filter_type": "efficient",
    "filter_body": {
    "bool":
    {
        "must":
        [
            {
                "range":
                {
                    "age":
                    {
                        "gte": 30,
                        "lte": 60
                    }
                }
            },
            {
                "term":
                {
                    "taste": "bitter"
                }
            },
            {
                "bool":
                {
                    "should":
                    [
                        {
                            "term":
                            {
                                "color": "blue"
                            }
                        },
                        {
                            "term":
                            {
                                "color": "green"
                            }
                        }
                    ]
                }
            }
        ]
    }
    },

    "query_data_set_format": "hdf5",
    "query_data_set_path":"/home/ec2-user/data/sift-128-euclidean-with-attr.hdf5",
    "neighbors_data_set_path":"/home/ec2-user/data/sift-128-euclidean-with-restrictive-filters-with-neigbors.hdf5",
    "neighbors_data_set_format":"hdf5",
    "query_count": 100
  }

Trigger the run by:
opensearch-benchmark execute-test     --target-hosts $URL:$PORT     --workload-params ${PARAMS_FILE}     --pipeline benchmark-only     --kill-running-processes     --workload-path /home/ec2-user/opensearch-benchmark-workloads/vectorsearch

Get recall result:
|                                                     error rate |         prod-queries |           0 |      % |
|                                                  Mean recall@k |         prod-queries |        0.02 |        |
|                                                  Mean recall@1 |         prod-queries |        0.01 |        |

Expected behavior
Recall should be correct calculated with ground true.
Screenshots
Dataset visualization in sift-128-euclidean-with-restrictive-filters-with-neigbors.hdf5 which contains -1:

Host / Environment
No response
Additional context
No response
Relevant log output
No response

@VijayanB Could you take a look at this?

Hi @junqiu-lei, how many search clients are being used and what is the number of vCPUs in the load generation host? Depending on the answer, this might be related to this issue that @VijayanB opened up. We're currently looking into recall feature and will provide updates there.

I will take a look into this issue


:seedling: Always create a Condition, if createServer failed (hcloud)

What this PR does / why we need it:
If this error happens (events):

Up to now, no Condition gets set:

This PR updates to code, so that always a Condition get set (if createServer failed)

this is related to #1414. Please consider that issue description

nice, this makes it simpler. I updated the PR.


Number of system acts for DSCT2 and GSIM

In the paper there are 19 system acts mentioned.
But when you query data you get 9 system acts?
len(np.unique(data_info['sys_act']))
The same applies to GSIM dataset.

Thanks for pointing this out, Pawel. We are going to double-check the universal-act mapping and will update the paper soon.


Is it suitable for faces?   (GFPGAN)

From the README:

Moreover, it may not perform well on human faces, text, etc, which will be optimized later.

From the README:

Moreover, it may not perform well on human faces, text, etc, which will be optimized later.
[...]
Here is a TODO list in the near future:

[ ]  optimize for human faces

Sorry，I didn't express it clearly.
I mean using high-order degradation modeling process in GFPGAN or others BFR model.


How do I automatically call find_package for package dependencies in CMake Config file

I'm novice in CMake. I recently wrote an OpenGL wrapper library and use the Vcpkg registry to manage my library,
here is the CMakeLists.txt of my library
cmake_minimum_required(VERSION 3.5)

# ---------------------------------------------------------------------------------------
# Start lomegl project
# ---------------------------------------------------------------------------------------
set(VCPKG_MANIFEST_DIR ${CMAKE_SOURCE_DIR}/vcpkg)

# ---------------------------------------------------------------------------------------
# Set default build to release
# ---------------------------------------------------------------------------------------
if(NOT CMAKE_BUILD_TYPE)
    set(CMAKE_BUILD_TYPE "Release" CACHE STRING "Choose Release or Debug" FORCE)
endif()

# lomegl require at least C++17
if(NOT CMAKE_CXX_STANDARD)
    message(STATUS "CMAKE_CXX_STANDARD is not set, automatically set it to C++17")
    set(CMAKE_CXX_STANDARD 17)
    set(CMAKE_CXX_STANDARD_REQUIRED ON)
elseif(CMAKE_CXX_STANDARD LESS 17)
    message(FATAL_ERROR "lomegl require at least C++17!")
endif()

# ---------------------------------------------------------------------------------------
# Set Build options
# ---------------------------------------------------------------------------------------
option(LOMEGL_USE_GLFW "Enable suporrt library for glfw" OFF)
option(LOMEGL_BUILD_TEST "Build test example(for dev purpose only)" ON)

if (LOMEGL_BUILD_TEST)
    set(LOMEGL_USE_GLFW ON)
    list(APPEND VCPKG_MANIFEST_FEATURES "glfw")
endif()

# ---------------------------------------------------------------------------------------
# Start to build lomegl library
# ---------------------------------------------------------------------------------------
project(lomegl LANGUAGES CXX)
include(GNUInstallDirs)

if (LOMEGL_USE_GLFW)
    find_package(glfw3 CONFIG REQUIRED)
endif()

find_package(glad CONFIG REQUIRED)
find_package(lotools CONFIG REQUIRED)
find_package(glm CONFIG REQUIRED)

set(LOMEGL_SRCS
    src/gl_base.cpp
    src/gl_exception.cpp
    src/gl_object.cpp
    src/gl_shader.cpp
    src/gl_texture.cpp
    src/gl_utility.cpp
    src/gl_vertex.cpp
    src/gl_world.cpp
)

message(STATUS "Build lomegl")
add_library(lomegl STATIC ${LOMEGL_SRCS})
add_library(lomegl::lomegl ALIAS lomegl)
target_include_directories(lomegl
PUBLIC
    "$<BUILD_INTERFACE:${PROJECT_SOURCE_DIR}/include>"
    "$<INSTALL_INTERFACE:${CMAKE_INSTALL_INCLUDEDIR}>"
)
target_link_libraries(lomegl PUBLIC glad::glad lotools::lotools glm::glm)

# ---------------------------------------------------------------------------------------
# Start to build lomegl-glfw library(if has)
# ---------------------------------------------------------------------------------------
if (LOMEGL_USE_GLFW)

    set(LOMEGL_GLFW_SRCS
    src/loglfw/glfw_utility.cpp
    )

    # Build lomegl-glfw
    message(STATUS "Build lomegl-glfw")
    add_library(lomegl-glfw STATIC ${LOMEGL_GLFW_SRCS})
    add_library(lomegl::lomegl-glfw ALIAS lomegl-glfw)
    target_include_directories(lomegl-glfw
    PUBLIC
        "$<BUILD_INTERFACE:${PROJECT_SOURCE_DIR}/include>"
        "$<INSTALL_INTERFACE:${CMAKE_INSTALL_INCLUDEDIR}>"
    )
    target_link_libraries(lomegl-glfw PUBLIC lomegl::lomegl glfw)
endif()

# ---------------------------------------------------------------------------------------
# Start to build lomegl-test(for dev purpose only)
# ---------------------------------------------------------------------------------------

if (LOMEGL_BUILD_TEST)
    add_executable(lomegl-test test/main.cpp)
    target_include_directories(lomegl-test PRIVATE test)
    target_link_libraries(lomegl-test PRIVATE lomegl::lomegl-glfw)
endif()

# ---------------------------------------------------------------------------------------
# Install
# ---------------------------------------------------------------------------------------
message(STATUS "Generating install")

list(APPEND lib_name "lomegl")
if (LOMEGL_USE_GLFW)
    list(APPEND lib_name "lomegl-glfw")
endif()

install(
    TARGETS ${lib_name} EXPORT lomegl-config
    RUNTIME DESTINATION ${CMAKE_INSTALL_BINDIR}
    ARCHIVE DESTINATION ${CMAKE_INSTALL_LIBDIR}
    LIBRARY DESTINATION ${CMAKE_INSTALL_LIBDIR}
)

install(
    EXPORT lomegl-config
    NAMESPACE lomegl::
    DESTINATION ${CMAKE_INSTALL_DATAROOTDIR}/lomegl
)

install(
    DIRECTORY ${PROJECT_SOURCE_DIR}/include/lomegl
    DESTINATION ${CMAKE_INSTALL_INCLUDEDIR}
    FILES_MATCHING PATTERN "*.hpp*" PATTERN "*.inl*" PATTERN "*.h*"
)

The corresponding portfile.cmake is as follows
vcpkg_from_github(
    OUT_SOURCE_PATH SOURCE_PATH
    REPO Chaojimengnan/lomegl
    REF aaf4ad4a810122f5d1415f19c0aa5d27abe6ebbb # 0.0.2
    SHA512 490f1d9366ac4f04449c193ab943265a4aab0c1365fb2344d8b51d51a9e9be2c2df22998577f1a0bbca93cffd56e72d7cc1e799286135d3099d54376c2bcee43
    HEAD_REF master
)

vcpkg_check_features(OUT_FEATURE_OPTIONS FEATURE_OPTIONS
    FEATURES
        glfw       LOMEGL_USE_GLFW
)

vcpkg_configure_cmake(
    SOURCE_PATH ${SOURCE_PATH}
    PREFER_NINJA
    OPTIONS
        ${FEATURE_OPTIONS}
        -DLOMEGL_BUILD_TEST=OFF
)

vcpkg_install_cmake()

vcpkg_fixup_cmake_targets()

file(REMOVE_RECURSE "${CURRENT_PACKAGES_DIR}/debug/include")
file(INSTALL "${SOURCE_PATH}/LICENSE" DESTINATION "${CURRENT_PACKAGES_DIR}/share/${PORT}" RENAME copyright)

I was able to successfully apply this OpenGL wrapper library to my application, but I had to explicitly call find_package on each dependency of the OpenGL wrapper library in CMakeLists.txt, e.g.:
# If these find_packages are not present, an error will occur
find_package(glad CONFIG REQUIRED)
find_package(lotools CONFIG REQUIRED)
find_package(glm CONFIG REQUIRED)
find_package(glfw3 CONFIG REQUIRED)

# lomegl is my OpenGL wrapper library, the above are all its dependency packages
find_package(lomegl CONFIG REQUIRED)

Otherwise, the following error will occur when CMake is configured :
[cmake] lomegl provides CMake targets:
[cmake]     # this is heuristically generated, and may not be correct
[cmake]     find_package(lomegl CONFIG REQUIRED)
[cmake]     target_link_libraries(main PRIVATE lomegl::lomegl lomegl::lomegl-glfw)
[cmake]
[cmake] -- Running vcpkg install - done
[cmake] -- Configuring done
[cmake] CMake Error at build/vcpkg_installed/x64-windows/share/lomegl/lomegl-config.cmake:55 (set_target_properties):
[cmake]   The link interface of target "lomegl::lomegl" contains:
[cmake]
[cmake]     glad::glad
[cmake]
[cmake]   but the target was not found.  Possible reasons include:
[cmake]
[cmake]     * There is a typo in the target name.
[cmake]     * A find_package call is missing for an IMPORTED target.
[cmake]     * An ALIAS target is missing.
[cmake]
[cmake] Call Stack (most recent call first):
[cmake]   D:/base/vcpkg/scripts/buildsystems/vcpkg.cmake:824 (_find_package)
[cmake]   CMakeLists.txt:15 (find_package)

Its error message is obvious that find_package is not called for my package library dependencies, I confirmed this by looking at the generated CMake config file, my question is :
Does vcpkg provide a port function that automatically call find_package for package dependencies, if not, do I have to write the CMake config file manually to do this?
The following CMake config file is generated for my library :
# Generated by CMake

if("${CMAKE_MAJOR_VERSION}.${CMAKE_MINOR_VERSION}" LESS 2.6)
   message(FATAL_ERROR "CMake >= 2.6.0 required")
endif()
cmake_policy(PUSH)
cmake_policy(VERSION 2.6...3.21)
#----------------------------------------------------------------
# Generated CMake target import file.
#----------------------------------------------------------------

# Commands may need to know the format version.
set(CMAKE_IMPORT_FILE_VERSION 1)

# Protect against multiple inclusion, which would fail when already imported targets are added once more.
set(_targetsDefined)
set(_targetsNotDefined)
set(_expectedTargets)
foreach(_expectedTarget lomegl::lomegl lomegl::lomegl-glfw)
  list(APPEND _expectedTargets ${_expectedTarget})
  if(NOT TARGET ${_expectedTarget})
    list(APPEND _targetsNotDefined ${_expectedTarget})
  endif()
  if(TARGET ${_expectedTarget})
    list(APPEND _targetsDefined ${_expectedTarget})
  endif()
endforeach()
if("${_targetsDefined}" STREQUAL "${_expectedTargets}")
  unset(_targetsDefined)
  unset(_targetsNotDefined)
  unset(_expectedTargets)
  set(CMAKE_IMPORT_FILE_VERSION)
  cmake_policy(POP)
  return()
endif()
if(NOT "${_targetsDefined}" STREQUAL "")
  message(FATAL_ERROR "Some (but not all) targets in this export set were already defined.\nTargets Defined: ${_targetsDefined}\nTargets not yet defined: ${_targetsNotDefined}\n")
endif()
unset(_targetsDefined)
unset(_targetsNotDefined)
unset(_expectedTargets)

# Compute the installation prefix relative to this file.
get_filename_component(_IMPORT_PREFIX "${CMAKE_CURRENT_LIST_FILE}" PATH)
get_filename_component(_IMPORT_PREFIX "${_IMPORT_PREFIX}" PATH)
get_filename_component(_IMPORT_PREFIX "${_IMPORT_PREFIX}" PATH)
if(_IMPORT_PREFIX STREQUAL "/")
  set(_IMPORT_PREFIX "")
endif()

# Create imported target lomegl::lomegl
add_library(lomegl::lomegl STATIC IMPORTED)

set_target_properties(lomegl::lomegl PROPERTIES
  INTERFACE_INCLUDE_DIRECTORIES "${_IMPORT_PREFIX}/include"
  INTERFACE_LINK_LIBRARIES "glad::glad;lotools::lotools;glm::glm"
)

# Create imported target lomegl::lomegl-glfw
add_library(lomegl::lomegl-glfw STATIC IMPORTED)

set_target_properties(lomegl::lomegl-glfw PROPERTIES
  INTERFACE_INCLUDE_DIRECTORIES "${_IMPORT_PREFIX}/include"
  INTERFACE_LINK_LIBRARIES "lomegl::lomegl;glfw"
)

if(CMAKE_VERSION VERSION_LESS 2.8.12)
  message(FATAL_ERROR "This file relies on consumers using CMake 2.8.12 or greater.")
endif()

# Load information for each installed configuration.
get_filename_component(_DIR "${CMAKE_CURRENT_LIST_FILE}" PATH)
file(GLOB CONFIG_FILES "${_DIR}/lomegl-config-*.cmake")
foreach(f ${CONFIG_FILES})
  include(${f})
endforeach()

# Cleanup temporary variables.
set(_IMPORT_PREFIX)

# Loop over all imported files and verify that they actually exist
foreach(target ${_IMPORT_CHECK_TARGETS} )
  foreach(file ${_IMPORT_CHECK_FILES_FOR_${target}} )
    if(NOT EXISTS "${file}" )
      message(FATAL_ERROR "The imported target \"${target}\" references the file
   \"${file}\"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   \"${CMAKE_CURRENT_LIST_FILE}\"
but not all the files it references.
")
    endif()
  endforeach()
  unset(_IMPORT_CHECK_FILES_FOR_${target})
endforeach()
unset(_IMPORT_CHECK_TARGETS)

# This file does not depend on other imported targets which have
# been exported from the same project but in a separate export set.

# Commands beyond this point should not need to know the version.
set(CMAKE_IMPORT_FILE_VERSION)
cmake_policy(POP)

This is a cmake question.
When the library is found using find_package in CMakeLists.txt, cmake will export these configurations. There are two situations at this point:

Use the macro provided by the Find module.
For libraries, macros are composed of absolute paths, so in the exported configuration, the full path of the library will be written directly into INTERFACE_LINK_LIBRARIES, no additional work is required.

Use the targets provided by the config module.
Since the target is an object, the target name will exist directly in the exported cmake configuration, and you must find the target through the find_dependency corresponding to the find_package before using them and then use it.

Thanks for the reply, it worked finally, I created a lomegl-config.cmake.in file based on what spdlog did, as follows :
@PACKAGE_INIT@

include(CMakeFindDependencyMacro)
set(LOMEGL_USE_GLFW @LOMEGL_USE_GLFW@)

find_dependency(glad CONFIG)
find_dependency(lotools CONFIG)
find_dependency(glm CONFIG)

if (LOMEGL_USE_GLFW)
    find_dependency(glfw3 CONFIG)
endif()

include("${CMAKE_CURRENT_LIST_DIR}/lomegl-config-targets.cmake")

check_required_components(lomegl)

And in CMakeLists.txt, adjust the install code to the following:
install(
    TARGETS ${lib_name} EXPORT lomegl-config
    RUNTIME DESTINATION ${CMAKE_INSTALL_BINDIR}
    ARCHIVE DESTINATION ${CMAKE_INSTALL_LIBDIR}
    LIBRARY DESTINATION ${CMAKE_INSTALL_LIBDIR}
)

install(
    EXPORT lomegl-config
    NAMESPACE lomegl::
    DESTINATION ${CMAKE_INSTALL_DATAROOTDIR}/lomegl
    FILE lomegl-config-targets.cmake
)

include(CMakePackageConfigHelpers)
configure_package_config_file("${PROJECT_SOURCE_DIR}/cmake/lomegl-config.cmake.in"
        "${CMAKE_CURRENT_BINARY_DIR}/lomegl-config.cmake"
        INSTALL_DESTINATION ${CMAKE_INSTALL_DATAROOTDIR}/lomegl)

install(FILES "${CMAKE_CURRENT_BINARY_DIR}/lomegl-config.cmake" DESTINATION ${CMAKE_INSTALL_DATAROOTDIR}/lomegl)

Finally my user application was able to find all dependencies properly with just find_package(lomegl CONFIG REQUIRED). But I still find this quite annoying.
I think these dependencies should be visible to vcpkg, if only vcpkg could automatically manage them for my library (e.g. automatically modify lomegl-config.cmake).
Then I don't need to write package config file manually

I think these dependencies should be visible to vcpkg, if only vcpkg could automatically manage them for my library (e.g. automatically modify lomegl-config.cmake).
Then I don't need to write package config file manually

In general, there is no desire that source packages technically depend on vcpkg to create exported Cmake config.

Close as solved


Implement ISO week number (%V)

This is based off of the logic in https://github.com/d3/d3/pull/2151 and would close #8.
The logic for parsing is much more complicated than the other week formats (%W and %U), so I wasn't quite sure how to fit it in. Any new commits or suggestions of refactoring/rewriting are welcome 😄

An unrelated bug I noticed here: week number parsing should consume two characters at most. So in parseWeekNumberMonday, parseWeekNumberSunday, parseWeekNumberISO, instead of:
var n = numberRe.exec(string.slice(i));

It should say:
var n = numberRe.exec(string.slice(i, i + 2));

Nicely done. Thank you for this pull request!

That should do it.

Thanks! Merged with a few tweaks.


Enable column clip content in SceneTreeEditor

Fixes: https://github.com/godotengine/godot/issues/68218#issuecomment-1386957073
Enable column clip content in SceneTreeEditor.

Before
After

So while it was wonky before, you could scroll and see at least a bit more of the name, and now you can't? I'm not sure that's an improvement.

Yeah deep trees are a problem. Long node names are ok, because you can just hover them and see full name in tooltip, but if a node is deeply nested, there's a chance it will go completely outside the visible area.

Yeah, both versions look bad.
Before:
https://user-images.githubusercontent.com/1756388/213435711-fa7e9efe-3e0a-45a8-bf62-1c4ebaf86a62.mp4
After:
https://user-images.githubusercontent.com/1756388/213435766-5c707af2-e0bf-4ba5-9da8-9cdd14b66e15.mp4

Buttons can have a background to make clipping less of a visual sore.

@YuriSizov Somethings like that?
https://user-images.githubusercontent.com/1756388/213866807-1163292f-08f1-4239-ad38-f90ddff046e2.mp4

Yes, but without cell clipping, so we have the horizontal scroll.

https://user-images.githubusercontent.com/1756388/213869234-e65115d6-8b08-4357-b226-0c368644784c.mp4

@DarkMessiah I don't think you've pushed the latest version, did you? From the clip it looks like the most sensible approach to the UX, so I'd like to give it a review.


Add unit tests for nginx runtime manager

As a developer,
I want my code to be thoroughly unit tested,
so that I can ensure that everything works as expected.
The nginx runtime manager is lacking in unit test coverage.
Acceptance

Add unit tests to thoroughly cover the nginx runtime manager code

Dev notes

will likely need mocks for nginx plus client and "verifyClient"
use ginkgo since we're testing interfaces

Heey @sjberman, feel free to assign me, would be cool to add some tests there !

Hey @zedGGs, thanks for the help on this. Assigned the issue to you and will pull your PR into the sprint when we see it!
Let us know if you need any help!

@zedGGs Feel free to use counterfeiter to mock any interfaces that need it.


How to use restful way node api call

I created a local node, but how can I use the restful api call method. Something like this:curl curl http://<IP_ADDRESS>:16127/daemon/getblockhash/1

@COLUD4 Sorry for the delay. In order to do something like this you need to have a restful api running along side the local node daemon.
You can also create direct http calls to the daemon using curl.
that command would look something like
curl --user StandUp --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getmininginfo", "params": [] }' -H 'content-type: text/plain;' http://<IP_ADDRESS>:18332/
You can find more information about that here Blockchain Communications

@COLUD4 Closing as this has been answered.


Please add a MIT license

ok

Thank you, This is a great initiative. A good start to use fins protocol.

这个库可能以后不在维护，新的库（Ping9719.DeviceCommunication）支持6+种协议，5+种PLC，10+种设备（如，刻印，扫码，打印，温控，RFID，FCT，机器人等...）。
This library may not be maintained in the future. The new library (Ping9719. DeviceCommunication) supports 6+protocols, 5+PLCs, and 10+devices (such as engraving, scanning, printing, temperature control, RFID, FCT, robots, etc.).

Ping9719. DeviceCommunication I am not able to find the library, may be its a private library

DeviceCommunication：https://gitee.com/cquni_mx/baseui/tree/master/Ping9719.DeviceCommunication
DeviceCommunicationUi：https://gitee.com/cquni_mx/baseui/tree/master/Ping9719.DeviceCommunication.WPF
他们都在gitee上，github上完善了才会加入进来。这个库的bug很多，文档也没有，正在生产环境中慢慢的优化。
They are all on Gitee and will only join after they have improved on Github. This library has many bugs and no documentation, and is slowly being optimized in a production environment.


Mapping Null value to Nested properties do not create intermediate instance

Hello!
By declaring a mapping using between One field to nested field like this
factory.classMap(ClassA.class, ClassB.class) .fieldMap("valueA.valueB.value1", "value2").mapNulls(true).mapNullsInReverse(true).add()
So Im' asking to map inner value1 -> value2 even if value1 or value2 are null.

When I put a value inside value2, then path to valueA.valueB.value1 is created and value1 is filled correctly.
When I put a null value inside value2 and I put a value different from null inside valueA.valueB.value, then value1 is replace by null
When I put a null value inside value2 and ask mapper to map to new instance, the path valueA.valueB.value1 is not instianciated, which is surprising.

I would think that third case would to be create hiercachy instead of nothing in case of mapNulls is set to true.
What could be a work around for that please?

No luck?


Update CODE_OF_CONDUCT.md

Description
Update code of conduct.
Checklist:
Not relevant.

~[ ] I have run ./ci/run_stable_checks.sh~
~[ ] I have reviewed my own code~
~[ ] I have added tests – if this is a bug fix, these tests will fail if the bug is present (to stop it from cropping up again). If this is a feature, my tests prove that the feature works.~

Great, thanks!


Search and pagination features to the articles and pages query

Added search and pagination features to the articles and pages query.
HCRC-63. HCRC-64. Filter posts and pages by a search term and a language.

[ ] The content field should be added to the articles and pages cards.

Koros should be with a Koros-wrapper


Test on Ruby 3.2 and 3.3

The fails are because bundler isn't installing on Ruby 2.x versions. All of Ruby 2.x is very EOL now, so I could remove it and Mittsu goes Ruby 3 only? Or, if you want to keep supporting 2.x, we should find a way to get those builds working with an older version of bundler.

Could we just add the gem install bundler version to the workflow?

Probably yes. I'll have a look.

Having a go at fixing builds in #124

#124 fixes the builds generally, so once that's merged in I'll update this one to go on top.

All green! Side note, I love how fast these builds are now!


React app: Filters feature and new entry point from All submissions

Fixes #2135

@frjo We can deploy this to test environment. Next, we can plan on filter options.

I have put this on test now.

@frjo Add filters in react pages, Could you check and give your feedback

@frjo Add filters in react pages, Could you check and give your feedback

This looks great @vimal1083! Some minor issues:
Possible to make the filter set a bit more narrow? Flow with the window width to some degree?
If I go to "/apply/submissions/all/" and do some filtering there I need to clicks the button twice to activate the React app.

This looks great @vimal1083! Some minor issues:
Possible to make the filter set a bit more narrow? Flow with the window width to some degree?
If I go to "/apply/submissions/all/" and do some filtering there I need to clicks the button twice to activate the React app.

Possible to make the filter set a bit more narrow? Flow with the window width to some degree?

Is this about the newly added filters in react app or the existing filters in django page?

Possible to make the filter set a bit more narrow? Flow with the window width to some degree?

Is this about the newly added filters in react app or the existing filters in django page?

The new filters in the React app.
Except for the with issue I really like how the look and work.

The new filters in the React app.
Except for the with issue I really like how the look and work.

Looks like we can deploy to test environment to check with more submissions.

Looks like we can deploy to test environment to check with more submissions.

Nice work on the filters! Deploying to test now.

Nice work on the filters! Deploying to test now.

Will deploy to live first thing tomorrow Friday.

Will deploy to live first thing tomorrow Friday.

@sks444 will create a separate PR to make the improvements suggested in above review comments. Great work.

@sks444 will create a separate PR to make the improvements suggested in above review comments. Great work.


Accept input from a pipe for a multipart form

I'm able to upload a file using the following form syntax:
$ http -f POST <IP_ADDRESS>/upload<EMAIL_ADDRESS>
but I was wondering if there is a way to pipe stdout to the form, for example:
$ date | http -f POST <IP_ADDRESS>/upload file@-

This results in the following error:
http: error: "file@-": [Errno 2] No such file or directory: u'-'

I can achieve the same thing with curl:
$ date | curl -XPOST <IP_ADDRESS>/upload -H 'Content-Type:multipart/form-data' --form file=@-

So I was wondering whether I was doing something wrong with httpie.

Another way to achieve this in curl without requiring a filename is to specify the multipart/form-data Content-Type header with a -F form field:
curl -X POST <IP_ADDRESS>/upload -H 'Content-Type: multipart/form-data' -F 'metadata={"description": "foo"}'

curl creates a part that looks like this:
--------------------------69798281f9911ef1
Content-Disposition: form-data; name="metadata"

{"description": "foo"}

The closest I can get with httpie is to use process substitution for the input:
http --form POST <IP_ADDRESS>:8080/upload metadata@<(echo -n '{"description": "foo"}')

which creates:
--a7311cce943f40c4837806985cff8404
Content-Disposition: form-data; name="metadata"; filename="63"

{"description": "foo"}

Which is close, but note the filename added to the Content-Disposition from the process substitution file descriptor.


Doesn't play well with

When one of my content views renders a <Modal /> the drawer will still open and close with swipe gestures. Can't actually see it happening because the modal covers it up, but if you swipe over the modal and then close it, the drawer will then be open under it. Would like to see interaction with the drawer disabled while a modal is open. Perhaps there's a way to do this already? If it matters, here's my drawer props:
const drawerConfig = {
  type: 'static',
  openDrawerOffset: 0.1,
  tweenDuration: 300,
  tweenEasing: 'easeInOutCubic',
  captureGestures: 'open',
  negotiatePan: true,
  tapToClose: true,
  panOpenMask: 0.1,
  panThreshold: 0.25,
  styles: {
    main: {shadowColor: '#000000', shadowOpacity: 0.8, shadowRadius: 10},
    mainOverlay: {backgroundColor: 'white', opacity: 0},
  },
  tweenHandler: (percent) => ({
    drawer: Drawer.tweenPresets.parallax(percent).drawer,
    mainOverlay: { opacity: percent * 0.8 },
  }),
};

Experiencing the same problem. Here, swipe motion is still captured by drawer under the modal.
@tybro0103 did you find a fix to this eventually?

@tybro0103 Thanks man. Works like magic. Not very elegant, but gets the job done. Some kind of state store or react context should serve for global tracking. For me they happen to be on same component, so this was a easy fix. Thanks!


Make "backtrace" an optional dependency behind different feature

Hi!
Currently miette pulls backtrace crate if fancy feature set is enabled. While I like color output and all the eye-candy miette provides, I plan to use it explicitly without relying on "global hook" and thus don't have any need for backtrace dependency. Unfortunately currently backtrace is pulled if fancy feature set is enabled and thus brings a lot of dependencies that I would prefer to avoid:
[[package]]
name = "backtrace"
version = "0.3.64"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5e121dee8023ce33ab248d9ce1493df03c3b38a659b240096fcbd7048ff9c31f"
dependencies = [
 "addr2line",
 "cc",
 "cfg-if 1.0.0",
 "libc",
 "miniz_oxide",
 "object",
 "rustc-demangle",
]

Is there any way backtrace could be hidden behind a separate feature flag?

I'm happy to take a PR that adds a fancy-no-backtrace feature!

I'm happy to take a PR that adds a fancy-no-backtrace feature!

That'd be great, much appreciated 🙏


Add unit tests, improve a dozen other things

Another milestone PR to set main things in place. Next ones should finally be smaller.
This one includes:

full test coverage of core basic classes
support for --skip-steps option
dabs.sh script should not break file permissions anymore
bug fixes

All in all LGTM!
Some things in Dockerfile could be improved but I could've mentioned this in the last review..
If you want, I can issue a PR for things I think could be improved in the Dockerfile

Sure I do :) Any contributions are welcome.


Several networks in wpa_supplicant

Hi @roleoroleo.
Is it possible to add several networks to wpa_supplicant.conf file? I guess it's a temporary file created on boot.
I have several APs with the same SSID and I would like to establish priorities as the camera frequently connects to one with low signal quality.
Would it be possible?
Thanks in advance!

wpa_supplicant.conf is created by Yi processes.
I don't know how and when it's created.
Sorry...

Do YI processes have some sort of log file that can help hint how it is created?
Anyway, I guess it could be changed with startup.sh script. I'll try to investigate a bit, do some tests and share the results back here.

Maybe a secondary "/Factory/wpa_supplicant.conf" could help?

Hi.
I have finally done it by using the following script (done quickly and probably with mistakes) in startup.sh.
Maybe it can help somebody. Seems to be working so far ....
#!/bin/sh
CFG="/tmp/wpa_supplicant.conf"
bssid1="xx:xx:xx:xx:xx:xx"
cat $CFG | grep update_config >/dev/null || echo "update_config=1" >> $CFG
wpa_pid=$(ps | grep wpa_supplicant | grep -v grep | awk '{print $1}')
[ -z $wpa_pid ] && echo "Error al obtener el PID" && exit 1
kill -HUP $wpa_pid
sleep 5
cat << EOF | wpa_cli
remove_network 1
remove_network 2
remove_network 3
set_network 0 bssid $bssid1
set_network 0 priority 2
add_network
set_network 1 ssid "WiOT"
set_network 1 key_mgmt WPA-PSK
set_network 1 psk "password"
set_network 1 scan_ssid 1
set_network 1 priority 0
enable_network 1
save_config
EOF

Brilliant, thank you so much for sharing! I've always wished for a function like this.


[wip]add two item pv.capacity total and available capacity and dynamic pv count of each type

add two item pv.capacity total and available capacity and dynamic pv count of each type

:+1:


use relative file path in CommandLineFormatter

This changes the format of the file name to add a leading "." so that the path is a relative path instead of an absolute path.
Modern terminal programs allow control-clicking on paths to jump to a file, so if this is a relative path, we can jump to the file. If it is printed as an absolute path, this doesn't work.

I think this is a great idea but I did find a couple issues.
I think I added a unit test to recreate the first, but I am having trouble running the unit tests right now. The source generators are causing me some pain after I started looking at supporting c# 11. I at least managed to build things so that I could test the cli.

Passing a subdirectory as a path, the relative path output isn't correct

PS C:\projects> dotnet csharpier csharpier
Error /Src/CSharpier.Generators/NodePrinterGenerator.cs - Failed to compile so was not formatted.

PS C:\projects> C:\projects\csharpier\Src\CSharpier.Cli\bin\Debug\net6.0\dotnet-csharpier.exe csharpier
Error .Src/CSharpier.Generators/NodePrinterGenerator.cs - Failed to compile so was not formatted.

Passing a fully qualified path, csharpier currently outputs a path relative to the path that was input (although missing the .) - to get it clickable would require it to be relative to the current directory, or a fully qualified path. Maybe the fully qualified path makes more sense, because the path supplied was fully qualified.

PS C:\projects> dotnet csharpier c:\projects\csharpier
Error /Src/CSharpier.Generators/NodePrinterGenerator.cs - Failed to compile so was not formatted.

PS C:\projects> C:\projects\csharpier\Src\CSharpier.Cli\bin\Debug\net6.0\dotnet-csharpier.exe c:\projects\csharpier
Error .Src/CSharpier.Generators/NodePrinterGenerator.cs - Failed to compile so was not formatted.

I may have my terminology confused.
I intended csharpier to output paths relative to the path that was supplied to be formatted, but they were missing the ..
If csharpier is supplied a relative path, like . or Subdirectory, then it should output a relative path that is clickable.
If csharpier is supplied an absolute path, like c:/projects/csharpier, then it should probably output an absolute path that is clickable.
And it looks like if you supply a path as ./Subdirectory then csharpier fails. I am going to create a bug for that.

Thanks for fixing this up. I didn't have time to get back to it yet.


Query based on input / output

Can we query based on input / output?
Not for now, because pipeline variables are generated only at execution, and are passed along in DSC via files. They are basically "capsuled". However with additional work we can query on them, ie, make a first query without these conditions, then for each RDS file involved so far, we load it from disk, compare it with the condition, and drop the entire row (of pipeline instance) if it does not satisfy it. It would not need us to change our design to make it happen. Just some post-processing.
When this is supported we have to use $ to refer to pipeline variables in queries.

I agree with all this. It just makes me wonder
whether to choose a different symbol than $ because
of its special use in R for element of a list...
that is, if we got to the point of having an object
representing the results of a pipeline in R, and we wanted
to refer to the $x value, we might have res[["$x"]] rather than res$x.
I'm not sure if $ is even a valid way to start a variable name in R.
(maybe this is why we chose $?!)
I actually like the $ , partly because of its association with wildcards,
and in a way the pipeline variables play a role somewhat
analogous to wildcards in make files...  But something to think about.
On Mon, Apr 24, 2017 at 8:35 AM, gaow<EMAIL_ADDRESS>wrote:

Can we query based on input / output?
Not for now, because pipeline variables are generated only at execution,
and are passed along in DSC via files. They are basically "capsuled".
However with additional work we can query on them, ie, make a first query
without these conditions, then for each RDS file involved so far, we load
it from disk, compare it with the condition, and drop the entire row (of
pipeline instance) if it does not satisfy it. It would not need us to
change our design to make it happen. Just some post-processing.
When this is supported we have to use $ to refer to pipeline variables in
queries.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/stephenslab/dsc2/issues/77, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABt4xbQvf2uhdF3I0jCMRuLVxeJwvJ4pks5rzKUwgaJpZM4NGK6A
.

I'm not sure if we have a need to change $ for something else. The query interface I have in mind is strictly module.variable theme, or module:variable. So if we eventually support pipeline input/output based query, we would use module.$variable or module:$variable for pipeline variables to distinguish them.
In other scenarios we do not allow for module.variable theme because which module a $variable comes from is is implicitly determined. I'd rather stick to this implicit feature unless there is a convincing case to persuade me otherwise.

I'm not sure if $ is even a valid way to start a variable name in R.

It is not valid. I started using $ because it seems to be a widely accepted wildcard symbol.

Ok, I'm good with keeping $


Please could someone help me?  Returning object with a promise instead of promise...

Could someone please help?  After using the latest code seeing that a promise isn't returned but an object I get function not found error.  If I unwrap the code and just have:
let obj =  RNFS.downloadFile(options);
I no longer get the error, but no combination of code I can figure out will let me use a .then to wait for the result.  I guess I can't see how an object returns and what to do with the promise!   I woiuld have used this in stack exchange but it's too specific to the module... Thanks so much.
Here is the original code which worked great.
	  var targetPath = in_parm.in_db_sys.downPath + in_parm.in_db_sys.realm_name + '.zip';
	  let fromU = in_parm.in_db_sys.server + 'Set1.zip';

	  var  options = {
		  fromUrl: fromU,
		  toFile: targetPath,
		  begin: mybegin,
		  progress: myprogress,
		  background: false,
		  progressDivider: 10
		};

	  RNFS.downloadFile(options)
	  .then((success) => {
console.log('FILE Copied!' + JSON.stringify(success));
	  })
	  .then((res) => {
		ZipArchive.unzip(targetPath, in_parm.in_db_sys.downPath)
	  })
	  .then((res) => {
		  console.log('unzip completed!');
		  getImportFiles(in_parm.in_db, in_parm.in_db_sys, in_parm.in_cur_bi, in_parm.in_maj_cat);
		})
	  .catch((error) => {
		  console.log(error)
	  })

Opps never mind... Got it now, leaving this here for others...
instead of .then, had to use .then.promise.   GOT IT!


Create-divisible-by-4-or-not.cpp

Check if a large number is divisible by 4 or not

Done
On Wed, Oct 13, 2021 at 7:51 PM Atul Sharma @.***>
wrote:

@.**** requested changes on this pull request.
Do make this changes:

Remove spaces with (-,_) in your file name.
(Optional) try to format your code.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/The-Streamliners/Data-Structures-and-Algorithms/pull/234#pullrequestreview-778652379,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARF3AHAXXOJDFBWLTLLS5BDUGWIWJANCNFSM5F3NFUKQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Comments in assembly view are sometimes hidden in IL view

I put a comment on 0x52664 in the assembly view. 0x52664 and 0x52668 were collected into a single if statement in the IL view, only 0x52668 was shown and the comment was not shown.

This was fixed a while ago.


Consider setting up continuos integration with Travis CI

In this way tests would be running for every Pull Request

To do this we need two thingsL

Someone who is a member of the repository needs to register on travis-ci.org and enable Travis integration for this repository
We need to create a build script for Travis

I can do number 2 if someone does number 1 first. @zosrothko can you look into this?

👍 more than a year passed, but the project still certainly needs the CI
@zosrothko all you need is just enable Travis build for the project. If @ftomassetti is not available now, I can help with number 2.

@new-javacc Could you grant me access to the javacc project for Travis CI.
Access request pending @javacc

Hi @new-javacc, I see a recent activity in the project. What do you think about this CI idea?

@inponomarev That's a very good idea but I am not able to setup the Travis script. try to make it happen...


Grid statesave

make grid.stateSave more flexibel

Use case: also save column.render if you want to.
Default settings will behave the same as the current stateSave().
This makes it also possible to save any custom column property.


Translator Application

Describe the project you want to add with tech stack
Translator application made using HTML CSS and Javascript
Expected behavior
Translates the given text in any language to the languuage of your choice
Screenshots (optional)

@pranjay-poddar @MohitGupta121


It seems this implementation is the combination of CBAM and Anti-adv without much insight?????

True dude...


Add full stop

Describe your changes
no need to explain
Issue ticket number and link
Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] If it is a core feature, I have added thorough tests.

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


[Feature] Yolo-based obstacle detection

Combine depth camera and YOLO bounding boxes to produce a list of obstacles.
For now, use a standard pretrained YOLO model
See this link for how to use the camera with depth
This should be its own package

So I got the sample code linked running. Aside from setting up a new package, is there anything more to this feature? With basic object/no object detection, it seems like it might be sufficient


Stickers don't work.

https://media.discordapp.net/attachments/753838523626291303/792210011039989810/unknown.png

I don't currently have stickers so you'll have to deal with it for now.

You can try using a Discord Experiments plugin to enable them.

You can try using a Discord Experiments plugin to enable them.

They are now available for everyone! 🙂

Finally fixed. Only took Discord 6+ months to make this available for everyone.


[ota] Revise BDX timeout logic

Problem
OTA requestor does not use the exchange response timeout for BDX messages. Instead, it uses a custom timeout mechanism which checks if the BDX downloader has made any progress within the last 5 minutes: https://github.com/project-chip/connectedhomeip/blob/90f32a0f678074a9b73773c978eedfddeeab97f5/src/app/clusters/ota-requestor/BDXDownloader.cpp#L39, https://github.com/project-chip/connectedhomeip/blob/90f32a0f678074a9b73773c978eedfddeeab97f5/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp#L52.
It results in suboptimal behavior. If OTA requestor sends BlockQuery message and does not receive Block response within a few seconds, that is not reported to the BDX downloader. All that happes is that MRP silently gives up after a few retransmissions, and the BDX downloader cancels the OTA only after 5 minutes without making any subsequent attempts to download the next block. For all that time the BDX exchange is kept active which causes unnecessary battery drain in the case of Sleepy End Devices.
Proposed Solution
Does anyone understand if the existing timeout mechanism is based on the spec or it's an implementation choice?
If it's the latter, maybe we could use the exchange response timeout mechanism and, say, make a few attempts of sending BlockQuery message until we give up?

@Damian-Nordic It does look like OTA will call into the BDX time out code when the exchange times out. Would you care to experiment to see by calling SetResponseTimeout, we're actually catching the time out much sooner than the 5 min that is there currently?

Spoke with @woody-apple and we'll take this for a v1 change but not into SVE branch.

@carol-apple I think given that the exchange timeout automatically closes the exchange, if the spec says 5 minutes is the minimum (thanks for the pointer, I missed this requirement!) we can't set the exchange timeout to anything less than that. But maybe the BDX code could try to re-send BlockQuery message after a minute or so.
I suspect the 5-minute timeout comes from the fact that the OTA provider may not have the file cached locally and must acquire it on the fly, but it many cases it seems it would be possible to increase the chances to complete the OTA transfer by repeating the query.

Thanks @Damian-Nordic! I think the retry would be a great optimization that we can do in post v1. I don't believe as is, there's a clear API into BDX that allows us to retry so we'll need to put some thought into enabling that down the road. Moving this out of v1.


Add Health & Safety policy

In the pandemic age, every conference should provide guidance regarding their policy on health & safety concerns.
With regards to C19, a policy should cover:

Mask expectations, even if the expectation is "haha anyone can do what they want"
Guidance regarding attendance when feeling unwell or having been in recent contact with the unwell
Expectations regarding notification on positive C19 tests, including after the fact
Any efforts AppSec NZ is committing to such as requiring ventilation, monitoring C02 levels, offering N95 masks and/or RATs

Ideally the core messages would be made clear in a section on the Conference page with links to the H&S policy elsewhere. This is, in fact, a sales feature as the absence of any messaging sends a clear message that the conference does not take its attendees health risks seriously.

Another year, another bump.


Hotfix/ls

This change is

Reviewed 6 of 6 files at r1.
Review status: all files reviewed at latest revision, 2 unresolved discussions.

support/src/main/java/edu/byu/support/activity/ByuActivity.java, line 28 at r1 (raw file):

 */
public abstract class ByuActivity extends AppCompatActivity implements ByuCallManager {
	private static final String TAG = ByuActivity.class.getSimpleName();

Remove

support/src/main/java/edu/byu/support/activity/ByuActivity.java, line 66 at r1 (raw file):

			return view;
		} else {
			throw new NullPointerException("Retrieval of the specified resource returned null");

Keep this, but change the error case

Comments from Reviewable

Review status: 5 of 6 files reviewed at latest revision, 2 unresolved discussions.

support/src/main/java/edu/byu/support/activity/ByuActivity.java, line 28 at r1 (raw file):
Previously, romrell4 (Eric Romrell) wrote…
Remove

Done.

support/src/main/java/edu/byu/support/activity/ByuActivity.java, line 66 at r1 (raw file):
Previously, romrell4 (Eric Romrell) wrote…
Keep this, but change the error case

Done.

Comments from Reviewable

Reviewed 1 of 1 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Translation extraction

Is your feature request related to a problem? Please describe.
Is there a way to extract missing translations?
Ex: I have translated a key in english but is missing in spanish etc

You can use the fallbackLocale option in both createI18nClient / createI18nServer to automatically fallback to this locale if the current one is missing a key.
Example: https://github.com/QuiiBz/next-international/blob/8bb7f87268ccd77a189cb109abd78290f2cdd700/examples/next-app/locales/client.ts#L22
Documentation (probably needs to be improved for this option): https://next-international.vercel.app/docs/pages-setup#setup-provider

I mean something like that:
https://www.i18next.com/how-to/extracting-translations

Sorry for misunderstand your question. We have a defineLocale helper that you can use to wrap your locales in: https://github.com/QuiiBz/next-international/blob/e4acd2fdf3c6ec181e218df82477f05df90c7311/examples/next-app/locales/fr.ts#L1
export default defineLocale({
  hello: 'World',
  ...
})


Can you provide database files?

I want to test it and I need the database file.

We mock the database driver, no real database access.
This is just a reference, using your own codes to test is recommended.
And this was long history, 5 years ago. So, do on your own.


Terraform unable to detect ct provider

I am having an issue where the terraform provider isn't detected.
I have a providers.tf file defined like so:
provider "ct" {
  version = "0.3.1"
}

provider "local" {
  version = "~> 1.0"
  alias = "default"
}

provider "null" {
  version = "~> 1.0"
  alias = "default"
}

provider "template" {
  version = "~> 1.0"
  alias = "default"
}

provider "tls" {
  version = "~> 1.0"
  alias = "default"
}

After manually installing ct v0.3.1 and specifying the directory for all plugins of the project, I get the following:
$ terraform init -plugin-dir=.terraform/plugins/linux_amd64/

Initializing provider plugins...

Missing required providers.

The following provider constraints are not met by the currently-installed
provider plugins:

* ct (0.3.1)

Terraform can automatically download and install plugins to meet the given
constraints, but this step was skipped due to the use of -get-plugins=false
and/or -plugin-dir on the command line.

If automatic installation is not possible or desirable in your environment,
you may manually install plugins by downloading a suitable distribution package
and placing the plugin's executable file in one of the directories given in
by -plugin-dir on the command line, or in the following directory if custom
plugin directories are not set:
    terraform.d/plugins/linux_amd64

The structure of the plugin folder is as follows:
$ tree .terraform
.terraform/
├── plugin_path
└── plugins
    └── linux_amd64
        ├── terraform-provider-ct_v0.3.1_x4
        ├── terraform-provider-local_v1.2.0_x4
        ├── terraform-provider-null_v1.0.0_x4
        ├── terraform-provider-template_v1.0.0_x4
        └── terraform-provider-tls_v1.2.0_x4

2 directories, 6 files

I notice on the terraform documention for 3rd party plugins that the naming convention doesn't include the _x4 part of the current filenames, however removing that part of the name still yields the same result.
I am currently using Terraform v0.11.13.  Am I missing something?

I doubt Terraform will infer that by .terraform/plugins/linux_amd64/ you mean within your home directory. Try a full path. Also, you probably don't need to specify, the default should be fine.

You also don't neccessarily need the os/arch specific directories either. And drop the _x4, not sure why that's there.
Here's a related guide with examples I've written.

That path was actually just a relative path for a folder in the current directory.
I originally tried it without the -plugin-dir= flag, but it kept giving the the "Provider "ct" not available for installation." error, despite having the provider in my ~/.terraform.d/plugins folder.
By explicitly using the -plugin-dir, I figured I could ensure all the providers were in the folder I specified explicitly.

Even with an absolute path, it does did not detect this provider for some reason. Renaming the provider with or without the _x4 suffix did not fix the issue.
What's weird is that I tried this same setup on a different machine and it worked using the default methods (vanilla terraform init and placing the providers within the $HOME/.terraform.d/plugins directory).  It must be a weird configuration I have on this machine or something.
I have a slight suspicion that this is more of an issue with terraform, rather than a terraform-provider-ct issue, so I'll probably submit an issue with them to hopefully gain some more insight on the situation.
Thanks for your help!


CTRL + ALT + ENTER not working to Replace All

VSCode Version: 1.6.1
OS Version: Windows 10 Anniversary Update

Steps to Reproduce:

Perform a regex search/replace using CTRL + H
Press CTRL + ALT + ENTER to perform the replacement operation
The replacement operation does not occur

NOTE: When I use the mouse to hover over the Replace All button, it specifically mentions a CTRL + ALT + ENTER keyboard shortcut, hence the expectation is that, that keyboard shortcut would invoke the Replace All operation.
Cheers,
Trevor Sullivan
Docker Captain
Microsoft MVP: Cloud & Data Center Management
https://trevorsullivan.net
https://twitter.com/pcgeek86

@pcgeek86 I cannot reproduce.
I have tried pressing ctrl+alt+enter with focus both in the replace field and inside the editor. All 6 matches are replaced for me.

I narrowed it down to the Python extension. Sorry for the trouble.
Just a suggestion: It might be a good idea to have some kind of "export extensions" guidance, for easy debugging / inclusion in bug reports! Is there a way to do this?

I reported the issue here: https://github.com/DonJayamanne/pythonVSCode/issues

@pcgeek86 Have you tried

It produces something like this for me:

VSCode Version: Code - Insiders 1.7.0-insider (0706b425537d8cfe2766eac00662ecf988c7ed7f, 2016-10-28T13:10:55.168Z)
OS Version: Windows_NT ia32 10.0.14393
Extensions:

Extension
Author
Version

copy-relative-path
alexdima
0.0.1

vscode-lcov
alexdima
0.2.0

vscode-eslint
dbaeumer
1.0.8

tslint
eg2
0.5.39

vsc-travis-ci-status
felixrieseberg
1.0.5

debugger-for-chrome
msjsdiag
2.1.0

vscode-versionlens
pflannery
0.8.0

vscode-open-in-github
sysoev
1.2.1

Steps to Reproduce:

@alexandrudima Awesome, didn't know about that. I prefer the Command Palette version though. :)


Use relative imports so otioview works in python3.

Codecov Report

Merging #489 into master will decrease coverage by 0.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #489      +/-   ##
==========================================
- Coverage   88.23%   88.14%   -0.09%
==========================================
  Files          68       68
  Lines        6900     6900
==========================================
- Hits         6088     6082       -6
- Misses        812      818       +6

Impacted Files
Coverage Δ

opentimelineio/adapters/fcp_xml.py
91.86% <0%> (-0.47%)
:arrow_down:

opentimelineio_contrib/adapters/fcpx_xml.py
93.28% <0%> (-0.47%)
:arrow_down:

opentimelineio_contrib/adapters/hls_playlist.py
90.68% <0%> (-0.31%)
:arrow_down:

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 878c67f...540af8c. Read the comment docs.


UI is reporting the wrong version

As displayed by 0.4.1 GUI:

Your sia-version is determined by the call to /daemon/version from siad, so yours is 0.4.0 when testing. Otherwise, I will update this in a PR.


Initial work for supporting ValidatingAdmissionPolicy

Description
This PR adds initial support for evaluating ValidatingAdmissionPolicy configurations
Linked Issues
How has this been tested?

Some tests have been included in the codebase for verifying the positive results

Checklist

[X] I have labeled this PR with the relevant Type labels
[] I have documented my code (if applicable)
[X] My changes are covered by tests

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

Replaced by #42


Test Cases added for for NDArray.

1. Create a test class for NDArray.
2. Test constructors and initialization.
3. Test getter methods.
4. Test array manipulation methods (reshape, flatten, transpose).
5. Test exception handling.
6. Test edge cases and boundary conditions.

Good job.


Original Demo should be Ported Completely to Kotlin

Found the issue. It was me.

Somehow I found them. My bad wow.

Hey Daniel,
shall we modify/add some lines to the readme to make it clear?

I did not have the sources loaded correctly in intelliJ so when I "Ctrl+B" and was unable to browse to the demo.  Cloned the demo code and was able to get my project working.
I figured out why my UI was not working. I was confusion between what is now under the package named DSL in the recent commits and the ImGui methods. It was a result of directly translating the Java example to kotlin and using the c++ API and not realizing that the DSL was calling multiple functions vs the ImGui c++ API. I was thinking about how to explain it in the readme that there is some wrapped functionality that if you use the ImGui C+ API will not match the same method calls in this library.

I wrote a first draft
Dont hesitate to give me some feedbacks or modify it directly


Locking single dependencies and pruning the lock file

If explicitly listing packages to vendor as command line arguments with the -l option, do not clean vendor directory; just add the new dependencies to the vendor.yml lock file.
Also, if using the --prune flag with the -l flag, dependencies that are pruned out are now removed from the vendor.yml lock file.
This resolves #48 and #50

Thanks for adding this PR @sha1sum. This was something I was about to report. I hope the PR gets merged soon! 👍

@sha1sum and @aarongreenlee thanks for the help :)


Can it be implemented with wavesurfer?

Hey, thank you for testing and contributing to wavesurfer.js!
Please make sure you can check all of these points below before opening an issue:
Hello.?
I recently came across wavesurfer and I'm still amazed by its cool features.
I write because I have a question.
What I want to do is amplify the voice of the microphone and output it to the speaker like a hearing aid. Is it possible with only wavesurfer?
I think you can use microphone.plugin + equalizer
If you use the microphone plugin, only the waveform is not output from the speaker.
I saw it..
How can I equalize the mic input and output it?
Actually, I'm deaf... Let's implement the function of a hearing aid instead.
I would like to. Is it possible?

If you use the microphone plugin, only the waveform is not output from the speaker.
I saw it..

what browser/operating system/wavesurfer.js version?

google.chrome 92 / windows 10 / wavesurfer.js 5.1.0

we can look to add this as part of the accessibility enhancements with this pr: #2369


Log user changes to courses

Hook into post_save signal of Course and Link in order to log course display name, link name and link url.

Should actually be implemented in post_save on the ModelAdmin instead.


Gravity.Top does not display when FLAG_LAYOUT_NO_LIMITS is set

In case of application with no actionBar, we should set the FLAG_LAYOUT_NO_LIMITS to remove the black bar on the phones with a notch. but in this case, the FlashBar is displayed like this:

I actually solve the issue. @aritraroy would u please have a look?

I have the same issue with this activity styles config:
<style name="Theme.AuthActivity" parent="Theme.MaterialComponents.DayNight.NoActionBar">
        <item name="android:windowBackground">@drawable/bg_auth</item>
        <item name="android:windowTranslucentStatus">true</item>
        <item name="android:windowTranslucentNavigation">true</item>
</style>

I call flash bar show() method in AuthActivity and the flash bar does not show. but when i come back to MainActivity, the prev called method runs and flash bar will be shown!


fix CustomDateTime issue

It appears that the current implementation of the CustomDateTime class  has a problem when used with certain date-time formats. I've observed this issue when running the following test code:
from siwe import SiweMessage

message = {
    'domain': 'localhost:3000',
    'statement': 'Sign in with Ethereum to the app.',
    'uri': 'http://localhost:3000',
    'version': '1',
    'chain_id': 1,
    'nonce': 12345678,
    'not_before': '2023-09-28T14:35:42.031383+08:00',
    'address': '0x0000000000000000000000000000000000000000',
    'expiration_time': '2023-09-30T14:35:42.035047+08:00',
    'issued_at': '2023-09-28T14:35:42.035060+08:00'
}

siwe_message = SiweMessage(message)
print(siwe_message.expiration_time)
print(siwe_message.expiration_time.date)

# output:
# 2023-09-30T14:35:42.035047+08:00
# 2023-09-28 14:35:42.031383+08:00 (incorrect)

This is expected, expiration_time is the string whilst expiration_time.date is the date object that can be used for comparisons/manipulations.
But the wrapper isn't necessarily great and is confusing. So I am going to close this PR is favour of #50


Wrong setting in button

modules\auto\index.ts:159
this button toggles the wrong setting

@RedGuy12

then fix it

oh yu did


I can´t sign up

I have a problem for sign up in my gdrive account.

Google Issue
This is a Google-Based issue @DenisSaint. Maybe try again?
Lolxgaming
Unofficial Support

Try again, Google may be having issues at that time.


merge "with_SRDB" branch to master

This is the pull request to merge SRDB data into ForC.
I believe we can pick if we want to merge with or without keeping the history of commits of the branch being merged...
if that is the case I think it is best not to so we don't have many commits to revert if we need to go back to before this merge.

Thanks, and congratulations!

Woo hoo! Big congratulations you guys

And to you!


Performance issues for pageload

With the following languages loaded, is the performance very bad for the critical pageload time on mobile, here a Nexus 4 running Chrome. 4.3 seconds are added to the page load time. This example is on a page with no highlighting.

With a fewer number of languages the performance is better, but the page still takes more than 500ms longer to load, on a page with no highlighting.

Don't have any Nexus to investigate this. But if you're concerned with the performance, you should probably consider loading Prism asynchronously and running the highlighting by yourself.

The problem isn't specific to the Nexus, it is devices with slow CPUs (all smartphones and tablets), because you have so much initialization that are very CPU heavy. But i hear you, you don't want to change that (which is fair), so i will play with som async loading, or change framework.

Don't get me wrong: you are very welcome to suggest any optimisation you think could improve the performance on such devices. You are also welcome to point at some specific CPU heavy initialization you think could be improved.
But with only those screenshots, there is nothing I can do.

Not sure if that helps in your case but I've rewritten the tokenizing part of prism as it was too slow and unstable with large files : https://github.com/siemiatj/prism-lite . It comes with some drawbacks but maybe this won't be a problem for you.

Hey there, thanks for working on Prism!
Why don’t you submit a PR so we can actually have a diff of the changes? Also, explaining your changes and what drawbacks they entail would help.


Follow up on PR #108

Fixes #27.
To follow up on #108. Polish it up such as changing input format for time_obs variable as previously discussed.

@DanRyanIrish I think we could change the format of the time_obs to some astropy.time.Time object instead... Or better yet, we could add another method to the class to do this for us. What is the best approach forward in your opinion?

Hi @kakirastern.  Following up on your matrix message, yes this PR should be to the same branch as #108, i.e. sunpy:time_dependent_response.  I'll close this PR and you reopen another to that branch?

Hi @DanRyanIrish Sure, am on to it now...


downscale DTR using tasmax and tasmin

As we've discussed, we'll be running tasmax and diurnal temperature range (DTR, e.g. tasmax - tasmin), along with daily precip through our pipeline. DTR will be treated as a multiplicative type of variable (like precip) as opposed to additive.
This means that we need to add two steps to our pipeline:

make sure that DTR is being computed at the beginning after cleaning tasmax and tasmin (this might already exist?)
after downscaling, we'll need a step to compute tasmin from tasmax and DTR, which is what we'll be using/sharing

We've had DTR in the past but, not with the scheme described here, as we ran tasmin just like any other variable rather than derived from existing downscaled output.
So, it sounds like we need a dtr parameter file that specs both tasmin and tasmax inputs in the historical and ssps lists.
The parameter file for tasmin would then indicate the dtr and tasmax downscaling output zarr stores to use as input.

If we had that dtr parameter file with both tasmin and tasmax specs, would we be cleaning tasmax twice?
Interesting - that would work for tasmin but that's not how I was thinking about it. I was thinking we would have DTR and tasmax parameter files, and the DTR would ultimately produce tasmin.

Closed with PR #335


Performance analysis on map vertices

Summary
As a data processing platform, we always want to make the data processing as efficient as possible. So we expect some performance analysis on the vertex pod, to figure out if there's any inefficient processing logic in the code, as well as the potential solutions for improvement.
The output of this issue would be a number of follow-up issues for the improvement tracking.

Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

Duplicate of #609


Cannot load v17 projects in ingest-ui

Project:
https://contribute.data.humancellatlas.org/projects/detail?uuid=a991ef15-4d4a-4b80-a93e-c538b4b54127&tab=project

The URL that fails:
https://ingest.archive.data.humancellatlas.org/schemas/json?url=https://schema.**data**.humancellatlas.org/type/project/17.0.0/project&deref
BUT
schema.data.humancellatlas.org doesn't exist and should instead refer to
https://schema.humancellatlas.org/type/project/17.0.0/project

@idazucchi can you please check the schemas tab of the spreadsheet for schema.data.humancellatlas.org rather than schema.humancellatlas.org?
If this spreadsheet was tested on staging, and then adapted for production.
Because the urls have a different format:

https://schema.staging.data.humancellatlas.org
https://schema.humancellatlas.org

(Thanks to @ESapenaVentura for the advice.)

This was caused by #883
A bug was introduced where there wrong schema url was used (due to the above difference between prod and staging urls:
https://github.com/ebi-ait/hca-ebi-dev-team/blob/42d5657a74014561dc15e54cecd4432e1bc27ee4/scripts/dcp-883/patch_projects.py#L5

from hca_ingest.api.ingestapi import IngestApi
from assertpy import assert_that, soft_assertions

api_url = 'https://api.ingest.archive.data.humancellatlas.org'
bad_schema = 'https://schema.data.humancellatlas.org/type/project/17.0.0/project'
good_schema = 'https://schema.humancellatlas.org/type/project/17.0.0/project'
token = 'your_token_here'
api = IngestApi(api_url)
api.set_token(f'Bearer {token}')

Projects with bad v17 url
target_projects = []
all_projects = api.get_all(f'{api_url}/projects', 'projects')
for project in all_projects:
    schema = project.get('content', {}).get('describedBy', '')
    if schema == bad_schema:
        target_projects.append(project)
print(f'Projects with bad v17 url {len(target_projects)}')

Projects with bad v17 url: 777
Patching Projects:
patched_projects = {}
error_projects = {}
skipped_projects = []
for project in target_projects:
    has_submission = project.get('hasOpenSubmission')
    if not has_submission:
        url = project.get('_links', {}).get('self', {}).get('href')
        if url not in patched_projects and url not in error_projects:
            patch = project.get('content')
            if url and patch:
                patch['describedBy'] = good_schema
                response = api.session.patch(url, json={'content': patch}, headers=api.get_headers())
                if response.ok:
                    patched_project = response.json()
                    patched_projects[url] = patched_project
                else:
                    error_projects[url] = response.content
            else:
                skipped_projects.append(project)
api.session.cache.clear()
print(f'Patched Projects: {len(patched_projects)}, Error Project: {len(error_projects)}, Skipped Projects: {len(skipped_projects)}')

Patched Projects: 672, Error Project: 0, Skipped Projects: 0
Open Projects: 105
UUID: ae71be1d-ddd8-4feb-9bed-24c3ddb6e1ad ShortName: Healthy and type 2 diabetes pancreas, Wrangling State: Published in DCP
UUID: 8c3c290d-dfff-4553-8868-54ce45f4ba7f ShortName: Mouse Melanoma, Wrangling State: Published in DCP
UUID: 005d611a-14d5-4fbf-846e-571a1f874f70 ShortName: HPSI human cerebral organoids, Wrangling State: Published in DCP
UUID: a9c022b4-c771-4468-b769-cabcf9738de3 ShortName: Drop-seq, DroNc-seq, Fluidigm C1 Comparison, Wrangling State: Published in DCP
UUID: a29952d9-925e-40f4-8a1c-274f118f1f51 ShortName: BM_PC, Wrangling State: Published in DCP
UUID: 027c51c6-0719-469f-a7f5-640fe57cbece ShortName: Kidney biopsy scRNA-seq, Wrangling State: Published in DCP
UUID: 90bd6933-40c0-48d4-8d76-778c103bf545 ShortName: CD4+ cytotoxic T lymphocytes, Wrangling State: Published in DCP
UUID: 74b6d569-3b11-42ef-b6b1-a0454522b4a0 ShortName: 1M Neurons, Wrangling State: Published in DCP
UUID: f86f1ab4-1fbb-4510-ae35-3ffd752d4dfc ShortName: HumanMousePancreas, Wrangling State: Published in DCP
UUID: f8aa201c-4ff1-45a4-890e-840d63459ca2 ShortName: HumanColonicMesenchymeIBD, Wrangling State: Published in DCP
UUID: 577c946d-6de5-4b55-a854-cd3fde40bff2 ShortName: Diabetic Nephropathy snRNA-seq, Wrangling State: Published in DCP
UUID: 4a95101c-9ffc-4f30-a809-f04518a23803 ShortName: HumanTissueTcellActivation, Wrangling State: Published in DCP
UUID: 8185730f-4113-40d3-9cc3-929271784c2b ShortName: WongAdultRetina, Wrangling State: Published in DCP
UUID: 116965f3-f094-4769-9d28-ae675c1b569c ShortName: Reprogrammed_Dendritic_Cells, Wrangling State: Published in DCP
UUID: 4d6f6c96-2a83-43d8-8fe1-0f53bffd4674 ShortName: SingleCellLiverLandscape, Wrangling State: Published in DCP
UUID: 1defdada-a365-44ad-9b29-443b06bd11d6 ShortName: MouseGastrulationAtlas, Wrangling State: Published in DCP
UUID: 88ec040b-8705-4f77-8f41-f81e57632f7d ShortName: scRNAseqSystemicComparison, Wrangling State: Published in DCP
UUID: 4e6f083b-5b9a-4393-9890-2a83da8188f1 ShortName: Mouse Endoderm Project, Wrangling State: Published in DCP
UUID: abe1a013-af7a-45ed-8c26-f3793c24a1f4 ShortName: KidneySingleCellAtlas, Wrangling State: Published in DCP
UUID: c4077b3c-5c98-4d26-a614-246d12c2e5d7 ShortName: TissueStability, Wrangling State: Published in DCP
UUID: a815c84b-8999-433f-958e-422c0720e00d ShortName: prefrontal_cortex_dev, Wrangling State: Published in DCP
UUID: 2086eb05-10b9-432b-b7f0-169ccc49d270 ShortName: DevelopingCardiacSystem, Wrangling State: Published in DCP
UUID: 7027adc6-c9c9-46f3-84ee-9badc3a4f53b ShortName: Pitx2DevelopingHeart, Wrangling State: Published in DCP
UUID: b4a7d12f-6c2f-40a3-9e35-9756997857e3 ShortName: Lung_Fibroblasts, Wrangling State: Published in DCP
UUID: 42d4f8d4-5422-4b78-adae-e7c3c2ef511c ShortName: HumanAdiposeTissue, Wrangling State: Published in DCP
UUID: f48e7c39-cc67-4055-9d79-bc437892840c ShortName: nktpbmcZhou, Wrangling State: Published in DCP
UUID: 1cd1f41f-f81a-486b-a05b-66ec60f81dcf ShortName: HumanFirstTrimesterPlacentaDecidua, Wrangling State: Published in DCP
UUID: 996120f9-e84f-409f-a01e-732ab58ca8b9 ShortName: HumanBrainSubstantiaNigra, Wrangling State: Published in DCP
UUID: 559bb888-7829-41f2-ace5-2c05c7eb81e9 ShortName: HumanLiverImmuneCells_GSE125188, Wrangling State: Published in DCP
UUID: 1c6a960d-52ac-44ea-b728-a59c7ab9dc8e ShortName: HealthyAndDiabeticPancreas, Wrangling State: Published in DCP
UUID: 41fb1734-a121-4616-95c7-3b732c9433c7 ShortName: TCellsNeuroinflammation, Wrangling State: Published in DCP
UUID: d3a4ceac-4d66-4984-9704-2570c0647a56 ShortName: TCellsHumanCentralNervousSystem, Wrangling State: Published in DCP
UUID: ce7b12ba-664f-4f79-8fc7-3de6b1892183 ShortName: MultipleSclerosisLineageDiversity, Wrangling State: Published in DCP
UUID: c893cb57-5c9f-4f26-9312-21b85be84313 ShortName: EpithelialDiversityHealthInflammation, Wrangling State: Published in DCP
UUID: ce33dde2-382d-448c-b6ac-bfb424644f23 ShortName: PreCdcFateTxFactCompetition, Wrangling State: Published in DCP
UUID: ccef38d7-aa92-4010-9621-c4c7b1182647 ShortName: AllelicExpressionPatterns, Wrangling State: Published in DCP
UUID: 23587fb3-1a4a-4f58-ad74-cc9a4cb4c254 ShortName: HumanDevoLiverSegalRashid, Wrangling State: Published in DCP
UUID: 7adede6a-0ab7-45e6-9b67-ffe7466bec1f ShortName: HumanIsletType2Diabetes, Wrangling State: Published in DCP
UUID: 07073c12-8006-4710-a00b-23abdb814904 ShortName: AneurysmalHumanAorticTissue, Wrangling State: Published in DCP
UUID: 520afa10-f9d2-4e93-ab7a-26c4c863ce18 ShortName: HumanInnateLymphoidCells, Wrangling State: Published in DCP
UUID: 842605c7-375a-47c5-9e2c-a71c2c00fcad ShortName: ProximalEpididymisCFTR, Wrangling State: Published in DCP
UUID: 1ce3b3dc-02f2-44a8-96da-d6d107b27a76 ShortName: HumanLymphoMyeloidProgenitorCells, Wrangling State: Published in DCP
UUID: 0fd8f918-62d6-4b8b-ac35-4c53dd601f71 ShortName: ImmuneCellExhaustianHIV, Wrangling State: Published in DCP
UUID: 63b5b6c1-bbcd-487d-8c2e-0095150c1ecd ShortName: CordBloodHematopoieticStemCells, Wrangling State: Published in DCP
UUID: 0c3b7785-f74d-4091-8616-a68757e4c2a8 ShortName: HumanBoneMarrowMyeloma, Wrangling State: Published in DCP
UUID: 08b794a0-519c-4516-b184-c583746254c5 ShortName: HumanGermlineCells, Wrangling State: Published in DCP
UUID: 05657a59-9f9d-4bb9-b77b-24be13aa5cea ShortName: HumanDermalFibroblastSubpopulations, Wrangling State: Published in DCP
UUID: 5ee710d7-e2d5-4fe2-818d-15f5e31dae32 ShortName: lymphaticEndothelialCells, Wrangling State: Published in DCP
UUID: ccd1f1ba-74ce-469b-9fc9-f6faea623358 ShortName: HumanPhagocytesHealthyLupusDutetre, Wrangling State: Published in DCP
UUID: eaefa1b6-dae1-4414-953b-17b0427d061e ShortName: TranscriptionalHeterogeneityInLatentAndReactivatedHivInfectedCells, Wrangling State: Published in DCP
UUID: 05be4f37-4506-429b-b112-506444507d62 ShortName: HumanDCsFromPre-cDCs, Wrangling State: Published in DCP
UUID: 3a694703-3084-4ece-9abe-d935fd5f6748 ShortName: HumanPreimplantationEmbryosESCs, Wrangling State: Published in DCP
UUID: 24c654a5-caa5-440a-8f02-582921f2db4a ShortName: HumanCorneaStemCells, Wrangling State: Published in DCP
UUID: 03c6fce7-789e-4e78-a27a-664d562bb738 ShortName: humanPreimplantationEmbryos, Wrangling State: Published in DCP
UUID: d2111fac-3fc4-4f42-9b6d-32cd6a828267 ShortName: HumanCerebralOrganoidsFetalNeocortex, Wrangling State: Published in DCP
UUID: b51f49b4-0d2e-4cbd-bbd5-04cd171fc2fa ShortName: SingleCellsAlzheimers, Wrangling State: Published in DCP
UUID: 52b29aa4-c8d6-42b4-807a-b35be94469ca ShortName: SurveyhumanBrainTranscriptomediversity, Wrangling State: Published in DCP
UUID: a96b71c0-78a7-42d1-88ce-83c78925cfeb ShortName: DropletSequencingNaturalGeneticVariation, Wrangling State: Published in DCP
UUID: c6ad8f9b-d26a-4811-b2ba-93d487978446 ShortName: HumanT2DPancreas, Wrangling State: Published in DCP
UUID: 6072616c-8794-4b20-8f52-fb15992ea5a4 ShortName: RevisedAirwayEpithelialHierarchy, Wrangling State: Published in DCP
UUID: 0c09fade-e079-4fde-8e60-6725b8c1d84b ShortName: CsfFromTwinsDiscordantForMultSclerosis, Wrangling State: Published in DCP
UUID: 2a72a4e5-66b2-405a-bb7c-1e463e8febb0 ShortName: StemCellsInChronicMyeloidLeukemia, Wrangling State: Published in DCP
UUID: 4037007b-0eff-4e6d-b7bd-8dd8eec80143 ShortName: pyleSkeletalMuscle, Wrangling State: Published in DCP
UUID: 946c5add-47d1-402a-97bb-a5af97e8bce7 ShortName: TranscriptomeLandscapeHumanFollicle, Wrangling State: Published in DCP
UUID: 52d10a60-c8d1-4d06-8a5e-af0d5c0d5034 ShortName: HumanSpermatogonialStemCells, Wrangling State: Published in DCP
UUID: 53c53cd4-8127-4e12-bc7f-8fe1610a715c ShortName: ProstateCellAtlas, Wrangling State: Published in DCP
UUID: 248fcf03-16c6-4a41-b6cc-aad4d894ca42 ShortName: OleicAcidMultipleSclerosis, Wrangling State: Published in DCP
UUID: b963bd4b-4bc1-4404-8425-69d74bc636b8 ShortName: Covid19PBMC, Wrangling State: Published in DCP
UUID: 962bd805-eb89-4c54-bad2-008e497d1307 ShortName: SC_analysis_kidney_organoids_fetal_kidney, Wrangling State: Published in DCP
UUID: 0792db34-8047-4e62-802c-9177c9cd8e28 ShortName: JointProfilingChromatinAccessibilityGeneExpression, Wrangling State: Published in DCP
UUID: 99101928-d9b1-4aaf-b759-e97958ac7403 ShortName: HumanEndocrinePancreas, Wrangling State: Published in DCP
UUID: d3ac7c1b-5302-4804-b611-dad9f89c049d ShortName: SingleCellsMultipleSclerosis, Wrangling State: Published in DCP
UUID: 8a40ff19-e614-4c50-b23b-5c9e1d546bab ShortName: HumanFetalKidney, Wrangling State: Published in DCP
UUID: 67a3de09-45b9-49c3-a068-ff4665daa50e ShortName: AcuteSkinInflammation, Wrangling State: Published in DCP
UUID: d3446f0c-30f3-4a12-b7c3-6af877c7bb2d ShortName: atlasOfHumanTeeth, Wrangling State: Published in DCP
UUID: bb19eac6-db1a-4334-befa-d6f200d467fc ShortName: dcp6471713778515119, Wrangling State: Eligible
UUID: 7880637a-35a1-4047-b422-b5eac2a2a358 ShortName: HumanRPEandChoroid, Wrangling State: Published in DCP
UUID: 51f02950-ee25-4f4b-8d07-59aa99bb3498 ShortName: scAgingHumanMaleSkin, Wrangling State: Published in DCP
UUID: 71436067-ac41-4ace-be1b-2fbcc2cb02fa ShortName: CorticalNephrogenicNicheKidney, Wrangling State: Published in DCP
UUID: faeedcb0-e046-4be7-b1ad-80a3eeabb066 ShortName: Human5Ovary10xChuva, Wrangling State: Submitted
UUID: df88f39f-01a8-4b5b-92f4-3177d6c0f242 ShortName: HeterogeneityCD4TCells, Wrangling State: Published in DCP
UUID: 376a7f55-b876-4f60-9cf3-ed7bc83d5415 ShortName: AtlasOfMajorAdultOrgans, Wrangling State: Submitted
UUID: e526d91d-cf3a-44cb-80c5-fd7676b55a1d ShortName: GompertsAirwatCfCells, Wrangling State: Submitted
UUID: c5f46615-68de-4cf4-bbc2-a0ae10f08243 ShortName: DevelopmentalCellProgramsSkin, Wrangling State: Published in DCP
UUID: 8bd2e5f6-9453-4b9b-9c56-59e3a40dc87e ShortName: photoreceptorMacularSubregions, Wrangling State: Submitted
UUID: da2747fa-2921-42e0-afd4-39ef57b2b88b ShortName: stemCellTrophoblast, Wrangling State: Submitted
UUID: 4af795f7-3e1d-4341-b867-4ac0982b9efd ShortName: humanUrineCells, Wrangling State: Submitted
UUID: b7259878-436c-4274-bfff-ca76f4cb7892 ShortName: GSE119561_KidneyOrganoidsNephronLineage, Wrangling State: Published in DCP
UUID: 20f37aaf-caa1-40e6-9123-be6ce8feb2d6 ShortName: DopaminergicNeuronDifferentiation, Wrangling State: Published in DCP
UUID: e0c74c7a-20a4-4505-9cf1-38dcdd23011b ShortName: GSE117211_KidneyMicroOrganoids, Wrangling State: Published in DCP
UUID: 3c27d2dd-b180-4b2b-bf05-e2e418393fd1 ShortName: HumanPancreasNormalandDiseased, Wrangling State: Submitted
UUID: 074a9f88-729a-455d-bca5-0ce80edf0cea ShortName: HumanHepatocyteDifferentiation, Wrangling State: Published in DCP
UUID: 783c9952-a4ae-4106-a6ce-56f20ce27f88 ShortName: HumanGumsNormalandDiseased, Wrangling State: Published in DCP
UUID: d7b7beae-652b-4fc0-9bf2-bcda7c7115af ShortName: LungEndothelialCells, Wrangling State: Published in DCP
UUID: 74493e98-44fc-48b0-a58f-cc7e77268b59 ShortName: distinctFunctionsOfPlasmablasts, Wrangling State: Submitted
UUID: 78d7805b-fdc8-472b-8058-d92cf886f7a4 ShortName: iPSCderivedTenocyte, Wrangling State: Submitted
UUID: 06c7dd8d-6cc6-4b79-b795-8805c47d36e1 ShortName: immuneCellsDuringSkinDevelopment, Wrangling State: Submitted
UUID: 2c041c26-f75a-495f-ab36-a076f89d422a ShortName: MouseNervousSystem, Wrangling State: Submitted
UUID: 6ac8e777-f9a0-4288-b5b0-446e8eba3078 ShortName: HumanCorneaDevelopment, Wrangling State: Published in DCP
UUID: 61515820-5bb8-45d0-8d12-f0850222ecf0 ShortName: GSE171668_SingleCellAndSpatialAtlasCovid, Wrangling State: None
UUID: 94e4ee09-9b4b-410a-84dc-a751ad36d0df ShortName: LiverCellAtlasHeterogeneity, Wrangling State: None
UUID: a62dae2e-cd69-4d5c-b5f8-4f7e8abdbafa ShortName: FreshAndFrozenTumours, Wrangling State: Published in DCP
UUID: a27dd619-25ad-46a0-ae0c-5c4940a1139b ShortName: CrossTissueSARS-CoV-2Study, Wrangling State: Published in DCP
UUID: 7be05025-9972-493a-856f-3342a8d1b183 ShortName: HumanMouseEntericNervousSystem, Wrangling State: Published in DCP
UUID: 34da2c5f-8011-48af-a7fd-ad2f56ec10f4 ShortName: ProfilingCisRegulatoryElements, Wrangling State: Published in DCP

@idazucchi I think I've fixed it.
but we have 105 projects with bad urls that were unable to be re-patched, possibly a database script will be required after all ><

I've managed to patch the remaining 105 projects. Which are now showing in the UI
I was being too conservative and not trying to patch when they would have actually patched fine.


suggestion-multicard network transmitter

It's really annoying and unaesthetic to have to have a separate transmitter for each networked location. A single transmitter that could hold multiple cards would be excellent. I don't even care if I have to put equivalent resources to a whole network transmitter into it every time I add a card. I just really want a single block solution, or at least something better than the 9 transmitters I've got now! (each powering an infinite wireless antenna in a different dimension.)

I have to think about this.

nod Even just like, a "network rack" or something, that the player still has to build the transmitter and upgrades and network card, but then can integrate it into a block with other transmitters. And the power draw could increase by the current transmitter draw for every transmitter in the "rack", that'd be fine by me. I just really want the multiple transmitters to take less space. :)


[FEATURE] skip_defaults for path operations

Is your feature request related to a problem? Please describe.
Need to exercise the skip_defaults option for pydantic json serialization so that Optional elements do not get serialized when they are nulls (see Pydantic issue.
Describe the solution you'd like
Allow the ability to set skip_defaults for endpoints (path operations) so that null values are not emitted in the JSON serializations.
I can take a stab at putting together a PR for this. I didn't realize my front-end colleagues wanted this cleaned up so urgently.

Thanks for adding it here! That helps us track the state of this feature.
If you can start a PR that would be great, otherwise I'll do it soon (but I'm fixing a couple of things first).

As the PR is already merged and it is available in the latest versions, I'll close this issue now. But feel free to add more comments or create new issues.


chore(registry.yaml): dummy in upper case

Signed-off-by: Jason Dellaluce<EMAIL_ADDRESS>What type of PR is this?
/kind cleanup
Any specific area of the project related to this PR?
/area registry
What this PR does / why we need it:
Little chore to trigger the CI
Which issue(s) this PR fixes:
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: ad4f06afcceea9bf9dfb4c64eaab499386673870


Jira webhook integration for "all issues" scope causes 404 errors in logs

Bug description
Jira webhook creation according to the Docs https://defectdojo.github.io/django-DefectDojo/integrations/jira/#enabling-the-webhook forses Jira to push webhook for default scope "all issues", which causes ton of 404 errors in DefectDojo logs for issues are not connected with Dojo.
Expected behavior
The documentation can be updated mentioning that we should configure the scope of the webhook instead of using default "all issues" (e.g with labels=defectdojo).
Webhook Scope and Events should be defined for configuration on Jira side. I'm not sure which events DefectDojo currently handle, but it would be great to have a list for configuring.
Deployment method (select with an X)

[X] Docker Compose
[ ] Kubernetes
[ ] GoDojo

Logs
[20/Jan/2023 10:51:32] WARNING [dojo.jira_link.views:205] 404 error processing JIRA webhook
[20/Jan/2023 10:51:32] WARNING [django.request:224] Not Found: /jira/webhook/[token]
[pid: 33|app: -|req: -/-] ***.**.**.*** (-) {60 vars in 1020 bytes} [Fri Jan 20 10:51:32 2023] POST /jira/webhook/[token] => generated 15948 bytes in 12 msecs (HTTP/1.0 404) 6 headers in 189 bytes (1 switches on core 0)

Faced the same bug for K8s based deployment. Could you take a look, please?

Hi @awakenine,
Have you mitigated it somehow? Could you provide an example of a JQL query?

I encountered the same issue ! documentations should point that out.
Thanks @awakenine for bringing this up, saved me troubleshooting time - I'll use the same path as you with labels=defectdojo

Closed as stale


Allow forwards without bans

We have an admin group for our main group, and sometimes we just forward messages from one to another to discuss something. I would really like users of the forwarded messages to not be banned, instead, I would prefer to mark messages as spam/ham manually.

It appears that you use the common group where all the admins communicate for spam messages as well. This is not the intended use - spam messages should have a separate group, eliminating the issues you've described.
The suggested change to manually mark messages as spam/ham is overly complicated for the convenience of having a common group, and its implementation is unclear. It would require adding a button for manual banning to each forwarded message, which is problematic. Messages that admins forward to each other would also have this button, as the bot cannot distinguish between a simple forward and one intended for banning.
An alternative solution to address your concern might be to optionally disable the "forwarded ban" feature. However, this approach is flawed, as it would prevent admins from marking messages as spam, thereby completely disabling the bot's learning capability.

I get the idea, but why would I want to have two admin groups?
OTOH, probably alternative solution is to introduce a bot command "ban", and allow to disable the forwarding feature altogether.
This way I will just say "/ban@asm0dey_killer_bot" in reply to the spam message, bot will add the message to the spam list, and that's pretty much all.

I made it this way because I want to have two admin groups and avoid polluting the chat/group admins use for regular communication with hundreds of spam reports. This will be fine for the small group with a couple of detected spam messages, but in our case, with 6000+ participants group, we may get tens of spam reports a day. Sending all those to the regular admin group will make it unusable for everyday communication.

Regarding your suggestion, this will work if combined with a new flag, "disable forwarded spam". Feel free to submit a PR with this functionality. As long as this doesn't break the current flow but just adds support of /ban command in the admin change -  I will be okay with the change.

@umputun I think it can actually be a ban command in the main chat by any of admins, WDYT?

Yeah, this will do. Probably not too hard to implement as it will follow the same logic as the current admin.MsgHandler does. This can be just a reply from the admin to spam messages with "spam" or "/spam", One more thing that should be handled here,  in addition to the ban itself, will be the removal of those replies from the chat as well by the bot

The change in master, you can try it by using :master image
It includes two things:

the new option --disable-admin-spam-forward env:DISABLE_ADMIN_SPAM_FORWARD you likely need to set
the ability to reply to any message in the primary chat with /spam or spam text triggering the same chain of events as forwarding did (remove spam messages, remove a user from the list of approved, add spam text to samples, report to admin group). In addition, it will also remove the admin's reply

Give it a try, please, and see how this works.

Wow, it was fast! I only started understanding the language :)

Deployed, let's wait for spam now

heh, gimme your group and I'll spam you, have a dedicated account for such type of tests

https://t.me/newpodcast2chat

Released in v1.8.0


nano: Depends on libmagic for Linuxbrew

Fix nano: error while loading shared libraries: libmagic.so.1: cannot open shared object file

Fix nano: error while loading shared libraries: libmagic.so.1: cannot open shared object file

Merged in https://github.com/Homebrew/homebrew-dupes/commit/36b6b7cd76a482319611eeb71e51f3134018a21c. Thanks Shaun!

Thanks for merging, Dominyk!


Export the module name

When using ng-react with CommonJS require statements it's not possible to retrieve the AngularJS module name from the module.
Most AngularJS modules published to npm export the module name string value so they can be used like following example:
angular.module('myApp', [require('angular-resource')]);

this is not a problem with ngReact...

If I require mgreact in a commonjs environment it doesn't return the module name

@mohsen1 thanks for the issue. Right now we return the module it self and you need to type name name of the module your self.
Would it be a better option to return the name instead ?

Yes. Angular core modules do this. They return the name so you can directly require it in the dependency lost of the app. See my original post example of Angular resource

This is be a breaking change to ngReact (a small one, but still breaking), so I'm not sure this small nicety is worth breaking over.


Choose by clicking label if input is hidden

Hi!
I'm trying to choose a hidden radio input by it's label with Capybara Webkit, but I'm getting Capybara::Webkit::ClickFailed: Failed to find position for element ... because it is not visible.
Here is a simple case for reproduction:
  <form>
    <input id="one" type="radio" name="form"/>
    Click me!
    <input id="two" type="radio" name="form"/>
    Click me!
  </form>

The spec would have a line something like:
choose 'one'
Would be great to get this working!  No issues with vanilla Capybara.
Thanks!
-Lee

@mhoran A giant thank you for this sir! Wasted so much time before I finally found this.


Tab logs is too long and disable_log() does not seem to have any effect

Hello !
I have an issue regarding the log of the tab.navigate_to()function, which displays a log like info!("Navigating a tab to {}", url); but when we use data URLs, that log can be exceedingly long. I tried using the disable_log() function without success, logs are still displayed, here is my code
    use headless_chrome::{Browser, LaunchOptionsBuilder};

    fn html_to_pdf(&self, html: &str) -> Result<Vec<u8>, RenderError> {
        let launch_options = LaunchOptionsBuilder::default()
            .sandbox(false) //Need this to run in docker, otherwise cannot find debug ports
            .build()
            .context("Failed to create browser launch options")?;
        let browser = Browser::new(launch_options)?;
        let tab = browser.new_tab()?;
        let tab = tab.disable_log()?;
        let report_data_url = format!("data:text/html;charset=utf-8,{}", encode_html(html));

        tab.navigate_to(&report_data_url)?;
        tab.wait_for_element(".footer__notice")?;

        let pdf_data = tab.print_to_pdf(None)?;
        Ok(pdf_data)
    }

I also tried disabling logs at the Browser level and eventhough those are disabled by default, I still get browser logs, my code :
        let launch_options = LaunchOptionsBuilder::default()
            .sandbox(false) //Need this to run in docker, otherwise cannot find debug ports
            .enable_logging(false)
            .build()
            .context("Failed to create browser launch options")?;

An example log 2024-02-14T13:50:53.388165Z  INFO headless_chrome::browser::process:246: Started Chrome. PID: 72442
The reason why we use data URL is that we are using headless_chrome to save pdf from a percent encoded html str that is not written on disk.
Am I using disable_log()in the wrong way ? I looked up source code and issues and could not find anything relevant. Any help is appreciated 😃

May be this line should output log in debug or trace ?
In fact providing a html str as Url will cause to have a very long log output :(


Use dataTypeClass to help support type safety in scala

@smrutimo do you think your PR would solve the following:
I can load a case class Foo definition with
dataType = "models.Foo"
But it doesn't work with
dataType = "forms.Bar.Foo" // compile error java.lang.ClassNotFoundException
where Foo is contained in object Bar
I can reach the class with
dataTypeClass = classOf[forms.Bar.Foo]
but it has no visible effect, the type is not displayed.


Fix Security Advisory 3137909 update

@HenrikFrystykNielsen there was a mistake in the advisory last time and I didn't notice the code was changed to VB. Here's the updated fix.
cc @blowdart

Much nicer, :shipit: :smile:

:ocean: :hocho:

Incorporated into dev: 75599639f07760ab664d8f362ade8381060fc1c5


randomize-upstreams added to the configuration

when set to true causes the upstream lists to be randomized. This helps w/ sticky session distribution

This change is

Changes Unknown when pulling 1f646e9fc56cb250c0be50354ab449a2d3f30b5e on Nordstrom:randomizeupstreams into ** on kubernetes:master**.

This is an interesting use case.  I noticed your comment in the code about more frequent nginx reloads. Without the sorts, we were seeing nginx reloads every minute or so.  I wonder if there is a better way to solve your problem besides having such a potential for high frequency reloads.

There may be. The problem, in short is the following:
the sticky session module keeps an index of which upstream was last sent traffic. Whenever nginx reloads this is set to 0. That means, in a dynamic environment like kubernetes where reloads are frequent (even with the sorting), that index will be 0 more than it should be (after ever reload) this leads to lumpy distribution.
I originally wrote this patch for 0.8.3 and shared this before and after graph. I spun up the version with randomized upstreams about 3pm on 4/6.

As you can see the effect is dramatic.
Since the current code compares the resulting plaintext config and not a snapshot of the data it's the best I could do on the schedule I had. I wouldn't mind taking a stab in another pull at comparing the data (pre randomization) to the previous run's data and dropping the reload before the config is even built.

@SleepyBrett Let me understand this, it's related only to randomize upstream order, not the name itself, right?

@rikatz this randomize the upstream servers inside each upstream (right now we sort by endpoint address/port here)

Closing. This feature is being implemented by default in #862


fixed factual error

@SergeyKanzhelev,
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

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

@bwren - Please review the proposed changes and add an appropriate comment so that automation can take the corresponding action.
Also, please update the metadata author for this article.
Thanks

#sign-off


Why the runtime is slow when using  nms_cpu.cpp complied by g++ self  than the .so file in  mmdetection?

Question:
I run a c++ trace model from mmdetection, and use the nms_cpu.cpp . when I use g++ complie the project， I can get the right result. But the time model used is much than the mmdetection inference.  Then I check the problem ,I found the nms_cpu.cpp take more time than the same process in mmdetection. Do you have some special args setting when you compile the nms_cpu.cpp to the .so file?

Do you have some special compile using the cpp_extension in torch? thank you very much.

We just use the default compiling args of pytorch extension. You can figure it out from the printed log.

ok, i found it and replace my settings with the printed log,  i got the same time cost. Thanks.

Hi,can you tell me how to compile nms_cpu?What instructions should I type?Thanks!