Support layering_check and module_maps features

Hi,
I have recently upgraded a project using gRPC from 1.31 to 1.48, and now I have the following error:
Bazel version is 5.2.0. Running on an ARM64 Mac.
ERROR: /tmp/dev/.cache/bazel/_bazel/45687a9fc51e3180e3ee6f957bfa2b6a/external/com_github_grpc_grpc/BUILD:6593:16: in @com_grail_bazel_compdb//:aspects.bzl%compilation_database_aspect aspect on cc_library rule @com_github_grpc_grpc//:grpc++_config_proto:
Traceback (most recent call last):
	File "/tmp/dev/.cache/bazel/_bazel/45687a9fc51e3180e3ee6f957bfa2b6a/external/com_grail_bazel_compdb/aspects.bzl", line 268, column 42, in _compilation_database_aspect_impl
		compiler_info = _cc_compiler_info(ctx, target, srcs, feature_configuration, cc_toolchain)
	File "/tmp/dev/.cache/bazel/_bazel/45687a9fc51e3180e3ee6f957bfa2b6a/external/com_grail_bazel_compdb/aspects.bzl", line 137, column 73, in _cc_compiler_info
		compiler_options = cc_common.get_memory_inefficient_command_line(
Error in get_memory_inefficient_command_line: Invalid toolchain configuration: Cannot find variable named 'module_name'.

I have tried using various versions of bazel-compilation-database (0.4.2, 0.5.1, latest master), but it's always the same.
I have also tried gPRC versions (1.42: first that works with Bazel 5.2.0, 1.48), but it's the same.
I have attached a small project that reproduces the issue. repro.zip
Just run bazel build //hello-world:hello-world_compdb to reproduce.
Any help is appreciated, thanks.

Should have been resolved by #102.

So I looked into this a little more. It looks like the way we get the compile command in Starlark is not compatible with the layering_check feature, which is only enabled for clang on unix. Currently, this feature is enabled in a package by having something like package(features = ["layering_check"]) in the package BUILD file.
The grpc project does enable this feature and then explicitly disables it when using the compilation database generation Starlark code in this project (currently they use version 0.4.5, but the Starlark code should roughly be the same).
https://github.com/grpc/grpc/blob/a644d8c9b43ece0a2683f4940faad8c6795a0b6d/BUILD#L32
https://github.com/grpc/grpc/blob/a644d8c9b43ece0a2683f4940faad8c6795a0b6d/tools/bazel.rc#L137-L138
https://github.com/grpc/grpc/blob/a644d8c9b43ece0a2683f4940faad8c6795a0b6d/tools/distrib/gen_compilation_database.py#L38
I am going to file an issue with bazel to find out the right Starlark with the layering_check feature.

This project is being archived.


Added querycount to getWithExtraInfo

Summary
Fixed the getWithExtraInfo which was not using pagination, which was creating queries with 5000 Union statements. Also set the default value of queryCount as 100, and set the limitation on the setter method to not set above 100.
In conversation with MySQL team to know the ideal pagination count, they suggested 12. 12 seems too low lookibng at the 5000 union ran today. Working with them to test it on test server or prod read-replica
Testing
./gradlew build
Will Test locally on TMS
Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable)

Instead of trunking the response, which will change the existing behavior, we should truncate large request into small trunks, process them in multiple requests and then merge the results together.

Instead of trunking the response, which will change the existing behavior, we should truncate large request into small trunks, process them in multiple requests and then merge the results together.

@yangyangv2 Isn't this what we are doing here?


Fixing links to cvx_short_course

Description
Fixing all links to the cvx_short_course
See issue #2263
Issue link (if applicable):
Type of change

[ ] New feature (backwards compatible)
[ ] New feature (breaking API changes)
[ ] Bug fix
[x] Other (Documentation, CI, ...)

Contribution checklist

[ ] Add our license to new files.
[ ] Check that your code adheres to our coding style.
[ ] Write unittests.
[ ] Run the unittests and check that they’re passing.
[ ] Run the benchmarks to make sure your change doesn’t introduce a regression.

I have updated all links that contain cvx_short_course.


fixes #1036

Signed-off-by: osamahammad21<EMAIL_ADDRESS>

@osamahammad21 looks good now. I don't see any routing inside the blockage region. Thanks.


Fix precision error

Fix precision error that was resulting in slightly different magnifications in x and y axes (makes a difference when the server is called for tiles at a small magnification)
Parametrize threshold used to check if fetched image and mask correspond to each other

@Leengit @manthey I tested the functions and ran the unit tests locally without problems. It seems that the problem is related to circleci. The change is very minor. I think this is ready to merge, but let me know if you have suggestions for change.

@Leengit @manthey I tested the functions and ran the unit tests locally without problems. It seems that the problem is related to circleci. The change is very minor. I think this is ready to merge, but let me know if you have suggestions for change.

I do not know anything about those circleci errors and am not confident enough to ignore them.  Let's ask @manthey.

I do not know anything about those circleci errors and am not confident enough to ignore them.  Let's ask @manthey.

@kheffah I'll look into what is causing CI to fail (probably tomorrow).  Most likely some upstream package has changed and we need to either pin some package version or adjust some code.

@kheffah I'll look into what is causing CI to fail (probably tomorrow).  Most likely some upstream package has changed and we need to either pin some package version or adjust some code.

@manthey Great .. thanks :)

@manthey Great .. thanks :)

@kheffah I haven't determined what changed since this last built on CI on Oct. 22.  I get the same failures locally, even when I pull code from my backup snapshot from that date.  The differences seems like some sort of rounding has changed.
I'll make a PR tomorrow that should at least let the tests pass on master with the current behavior.  I'll also set up a weekly build so when something changes in the future it will (hopefully) be easier to track down.

@kheffah I haven't determined what changed since this last built on CI on Oct. 22.  I get the same failures locally, even when I pull code from my backup snapshot from that date.  The differences seems like some sort of rounding has changed.
I'll make a PR tomorrow that should at least let the tests pass on master with the current behavior.  I'll also set up a weekly build so when something changes in the future it will (hopefully) be easier to track down.

@manthey Sounds like a good plan, thanks very much.

@manthey Sounds like a good plan, thanks very much.

Closing PR because it is a subset of PR #884 to simplify resolving conflicts etc.

Closing PR because it is a subset of PR #884 to simplify resolving conflicts etc.


Heavy CPU load in OS X 10.10.2

I discovered heavy CPU load of 50 to 100 percent on one core during playback in 10.10.2 on a MacBookPro11,2.
Would you need any further info, process analysis, or similar?

Thanks for reporting. If it's reliably reproducible, would you mind giving detailed instructions? Does the same happen when using soundcloud.com in Safari?

@salomvary I'm seeing the same issue on 10.10.4. The same CPU load does not happen when you open SoundCloud on Safari.

Having the same issue at Mac OS El Capitan 10.11.1 on MBP 13" Retina. CPU constantly at about 70%, but it works fine in native Safari.

I'm having the same issues on my MacBook Pro 13" Retina, running 10.11.2.
It's working fine in Safari, but use of SoundCleod unfortunately is impossible like this.

Can confirm on Sierra with Safari technology preview (system webcore is linked to preview, right?)

(answering to above: nope)
Just tested the wkwebkitview branch and linked it specifically to the safari technology preview. I'm currently sitting at ~10-15% cpu which then drops to ~2% cpu after a while. Thinking the 'spike' is buffering-related but I haven't really looked into it.

So that's kinda good news, isn't it?

Should be fixed in 1.0.0. If not, please reopen.


fix: text font size for text widget inside modal & statbox.

Description

The font size given to the text widgets inside the modal & stat box widgets was different than what we have in the property pane font size dropdown.
This Pull request uses appropriate font size values.

Fixes #16758
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Manual

Test Plan
Issues raised during DP testing
Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

Tested on DP, working fine

/ok-to-test sha=6315fc0

/ok-to-test sha=2029659

/ok-to-test sha=ffc512e

/ok-to-test sha=ffc512e


Better support for library loaders

Add an asynchronous callback detection method for libraries that don't have all of their information available on page load. For example, we would see that we are loading Sproutcore, register a timer (or similar method) with a callback to update the library information when it is finished loading.

I have some local changes that make something very similar to this this work, using setTimeout.  I'll refine it further and update my fork so you can see if you find them worth merging into the master branch.

That would be awesome. This is definitely a tricky issue, because anything we add to make this work will have to load on every page load when the extension is running.
I'll definitely take a look at what you check in. What I am thinking is that we need to detect when someone is using a loader library that we recognize, and in that case, attach an event or use setTimeout as you mentioned to ascertain the libraries that are loaded. The trick is going to be doing this in a way that does not rely on the loader itself for notifying us when everything is loaded  - otherwise our maintenance is going to go way up as APIs change :)

Closing this as it will be investigated as a part of #15.


Add global, controller and action filters.

As the title says, please could you provide the ability to add add global, controller, and action filters.

 You are trying to allow attributes for methods by using DocComments when you don't need to. You can have a Global_Filters class, and in the class constructor you can specify fitlers to execute and at the start of each method you can specify filters to execute also, therefore until PHP provides the ability to add method attributes I would avoid trying to replicate such a feature in a hacky manner.

Hey Matt, I have been unable to locate any documentation for GlobalFilters in PHP.  Do you have an example of what you had in mind?

You would have to make a static class, something like

This is not complete code, however I can put something together and submit a pull request for you.

Yes, it would be great to see an example of how you might do something like:
class GlobalFilters {
public function Authorize() {
// todo: check user is authorized
return true;
}
}
...
// Authorize
public function Index()
{
// user should only see this if they are authorized
return View();
}
Thanks.


[Help Request]: Compilation of gaussian-splatting causes problems with vector_types.h

Problem Description
Trying to install https://github.com/graphdeco-inria/gaussian-splatting for pytorch on WSL2 Ubuntu 22.04 with a 79000XT on ROCm 6.1.3
I see this solves some issues for ROCm: https://github.com/expenses/gaussian-splatting, but the submodules are the same, so it probbably doesnt help me much.
A similar issue occurs with https://fs.hlrs.de/projects/par/events/2024/GPU-AMD/day1/HLRS_Exercises.html#makefile-option, but i'm not sure exactly what I am doing.
These submodules of gaussian-splatting, diff-gaussian-rasterization and simple-knn are require for https://github.com/MrForExample/ComfyUI-3D-Pack, of which currently works with ZLUDA.
$ PYTORCH_ROCM_ARCH=gfx1100 USE_ROCM=1 MAX_JOBS=16 pip install git+https://github.com/graphdeco-inria/diff-gaussian-rasterization.git@eb015708bb0ae0468367b60ec8d809a5f1ec34fe --global-option=build_ext --global-option="-I/usr/local/cuda/targets/x86_64-linux/include/"

...
[1/5] /opt/rocm-6.1.3/bin/hipcc  -I/home/musclez/ComfyUI/.venv/lib/python3.11/site-packages/torch/include -I/home/musclez/ComfyUI/.venv/lib/python3.11/site-packages/torch/include/torch/csrc/api/include -I/home/musclez/ComfyUI/.venv/lib/python3.11/site-packages/torch/include/TH -I/home/musclez/ComfyUI/.venv/lib/python3.11/site-packages/torch/include/THC -I/home/musclez/ComfyUI/.venv/lib/python3.11/site-packages/torch/include/THH -I/opt/rocm-6.1.3/include -I/usr/local/cuda/targets/x86_64-linux/include/ -I/home/musclez/ComfyUI/.venv/include -I/usr/include/python3.11 -c -c /tmp/pip-req-build-42j1mq4k/hip_rasterizer/forward.hip -o /tmp/pip-req-build-42j1mq4k/build/temp.linux-x86_64-cpython-311/hip_rasterizer/forward.o -fPIC -D__HIP_PLATFORM_AMD__=1 -DUSE_ROCM=1 -DHIPBLAS_V2 -DCUDA_HAS_FP16=1 -D__HIP_NO_HALF_OPERATORS__=1 -D__HIP_NO_HALF_CONVERSIONS__=1 -I/tmp/pip-req-build-42j1mq4k/third_party/glm/ -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1011"' -DTORCH_EXTENSION_NAME=_C -D_GLIBCXX_USE_CXX11_ABI=0 --offload-arch=gfx1100 -fno-gpu-rdc -std=c++17
      FAILED: /tmp/pip-req-build-42j1mq4k/build/temp.linux-x86_64-cpython-311/hip_rasterizer/forward.o
      /opt/rocm-6.1.3/bin/hipcc  -I/home/musclez/ComfyUI/.venv/lib/python3.11/site-packages/torch/include -I/home/musclez/ComfyUI/.venv/lib/python3.11/site-packages/torch/include/torch/csrc/api/include -I/home/musclez/ComfyUI/.venv/lib/python3.11/site-packages/torch/include/TH -I/home/musclez/ComfyUI/.venv/lib/python3.11/site-packages/torch/include/THC -I/home/musclez/ComfyUI/.venv/lib/python3.11/site-packages/torch/include/THH -I/opt/rocm-6.1.3/include -I/usr/local/cuda/targets/x86_64-linux/include/ -I/home/musclez/ComfyUI/.venv/include -I/usr/include/python3.11 -c -c /tmp/pip-req-build-42j1mq4k/hip_rasterizer/forward.hip -o /tmp/pip-req-build-42j1mq4k/build/temp.linux-x86_64-cpython-311/hip_rasterizer/forward.o -fPIC -D__HIP_PLATFORM_AMD__=1 -DUSE_ROCM=1 -DHIPBLAS_V2 -DCUDA_HAS_FP16=1 -D__HIP_NO_HALF_OPERATORS__=1 -D__HIP_NO_HALF_CONVERSIONS__=1 -I/tmp/pip-req-build-42j1mq4k/third_party/glm/ -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1011"' -DTORCH_EXTENSION_NAME=_C -D_GLIBCXX_USE_CXX11_ABI=0 --offload-arch=gfx1100 -fno-gpu-rdc -std=c++17
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/forward.hip:14:
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/../hip_rasterizer/forward.h:18:
      In file included from /usr/local/cuda/targets/x86_64-linux/include/device_launch_parameters.h:53:
      In file included from /usr/local/cuda/targets/x86_64-linux/include/vector_types.h:68:
      /usr/local/cuda/targets/x86_64-linux/include/crt/host_defines.h:54:2: warning: "crt/host_defines.h is an internal header file and must not be used directly.  Please use cuda_runtime_api.h or cuda_runtime.h instead." [-W#warnings]
         54 | #warning "crt/host_defines.h is an internal header file and must not be used directly.  Please use cuda_runtime_api.h or cuda_runtime.h instead."
            |  ^
      /usr/local/cuda/targets/x86_64-linux/include/crt/host_defines.h:99:9: warning: '__align__' macro redefined [-Wmacro-redefined]
         99 | #define __align__(n) \
            |         ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_runtime.h:108:9: note: previous definition is here
        108 | #define __align__(x) __attribute__((aligned(x)))
            |         ^
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/forward.hip:14:
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/../hip_rasterizer/forward.h:18:
      In file included from /usr/local/cuda/targets/x86_64-linux/include/device_launch_parameters.h:53:
      /usr/local/cuda/targets/x86_64-linux/include/vector_types.h:107:27: error: definition of type 'char1' conflicts with type alias of the same name
        107 | struct __device_builtin__ char1
            |                           ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1185:1: note: 'char1' declared here
       1185 | __MAKE_VECTOR_TYPE__(char, char);
            | ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1158:15: note: expanded from macro '__MAKE_VECTOR_TYPE__'
       1158 |         using CUDA_name##1 = HIP_vector_type<T, 1>;\
            |               ^
      <scratch space>:353:1: note: expanded from here
        353 | char1
            | ^
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/forward.hip:14:
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/../hip_rasterizer/forward.h:18:
      In file included from /usr/local/cuda/targets/x86_64-linux/include/device_launch_parameters.h:53:
      /usr/local/cuda/targets/x86_64-linux/include/vector_types.h:112:27: error: definition of type 'uchar1' conflicts with type alias of the same name
        112 | struct __device_builtin__ uchar1
            |                           ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1184:1: note: 'uchar1' declared here
       1184 | __MAKE_VECTOR_TYPE__(uchar, unsigned char);
            | ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1158:15: note: expanded from macro '__MAKE_VECTOR_TYPE__'
       1158 |         using CUDA_name##1 = HIP_vector_type<T, 1>;\
            |               ^
      <scratch space>:349:1: note: expanded from here
        349 | uchar1
            | ^
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/forward.hip:14:
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/../hip_rasterizer/forward.h:18:
      In file included from /usr/local/cuda/targets/x86_64-linux/include/device_launch_parameters.h:53:
      /usr/local/cuda/targets/x86_64-linux/include/vector_types.h:118:40: error: definition of type 'char2' conflicts with type alias of the same name
        118 | struct __device_builtin__ __align__(2) char2
            |                                        ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1185:1: note: 'char2' declared here
       1185 | __MAKE_VECTOR_TYPE__(char, char);
            | ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1159:15: note: expanded from macro '__MAKE_VECTOR_TYPE__'
       1159 |         using CUDA_name##2 = HIP_vector_type<T, 2>;\
            |               ^
      <scratch space>:354:1: note: expanded from here
        354 | char2
            | ^
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/forward.hip:14:
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/../hip_rasterizer/forward.h:18:
      In file included from /usr/local/cuda/targets/x86_64-linux/include/device_launch_parameters.h:53:
      /usr/local/cuda/targets/x86_64-linux/include/vector_types.h:123:40: error: definition of type 'uchar2' conflicts with type alias of the same name
        123 | struct __device_builtin__ __align__(2) uchar2
            |                                        ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1184:1: note: 'uchar2' declared here
       1184 | __MAKE_VECTOR_TYPE__(uchar, unsigned char);
            | ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1159:15: note: expanded from macro '__MAKE_VECTOR_TYPE__'
       1159 |         using CUDA_name##2 = HIP_vector_type<T, 2>;\
            |               ^
      <scratch space>:350:1: note: expanded from here
        350 | uchar2
            | ^
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/forward.hip:14:
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/../hip_rasterizer/forward.h:18:
      In file included from /usr/local/cuda/targets/x86_64-linux/include/device_launch_parameters.h:53:
      /usr/local/cuda/targets/x86_64-linux/include/vector_types.h:128:27: error: definition of type 'char3' conflicts with type alias of the same name
        128 | struct __device_builtin__ char3
            |                           ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1185:1: note: 'char3' declared here
       1185 | __MAKE_VECTOR_TYPE__(char, char);
            | ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1160:15: note: expanded from macro '__MAKE_VECTOR_TYPE__'
       1160 |         using CUDA_name##3 = HIP_vector_type<T, 3>;\
            |               ^
      <scratch space>:355:1: note: expanded from here
        355 | char3
            | ^
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/forward.hip:14:
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/../hip_rasterizer/forward.h:18:
      In file included from /usr/local/cuda/targets/x86_64-linux/include/device_launch_parameters.h:53:
      /usr/local/cuda/targets/x86_64-linux/include/vector_types.h:133:27: error: definition of type 'uchar3' conflicts with type alias of the same name
        133 | struct __device_builtin__ uchar3
            |                           ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1184:1: note: 'uchar3' declared here
       1184 | __MAKE_VECTOR_TYPE__(uchar, unsigned char);
            | ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1160:15: note: expanded from macro '__MAKE_VECTOR_TYPE__'
       1160 |         using CUDA_name##3 = HIP_vector_type<T, 3>;\
            |               ^
      <scratch space>:351:1: note: expanded from here
        351 | uchar3
            | ^
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/forward.hip:14:
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/../hip_rasterizer/forward.h:18:
      In file included from /usr/local/cuda/targets/x86_64-linux/include/device_launch_parameters.h:53:
      /usr/local/cuda/targets/x86_64-linux/include/vector_types.h:138:40: error: definition of type 'char4' conflicts with type alias of the same name
        138 | struct __device_builtin__ __align__(4) char4
            |                                        ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1185:1: note: 'char4' declared here
       1185 | __MAKE_VECTOR_TYPE__(char, char);
            | ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1161:15: note: expanded from macro '__MAKE_VECTOR_TYPE__'
       1161 |         using CUDA_name##4 = HIP_vector_type<T, 4>;
            |               ^
      <scratch space>:356:1: note: expanded from here
        356 | char4
            | ^
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/forward.hip:14:
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/../hip_rasterizer/forward.h:18:
      In file included from /usr/local/cuda/targets/x86_64-linux/include/device_launch_parameters.h:53:
      /usr/local/cuda/targets/x86_64-linux/include/vector_types.h:143:40: error: definition of type 'uchar4' conflicts with type alias of the same name
        143 | struct __device_builtin__ __align__(4) uchar4
            |                                        ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1184:1: note: 'uchar4' declared here
       1184 | __MAKE_VECTOR_TYPE__(uchar, unsigned char);
            | ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1161:15: note: expanded from macro '__MAKE_VECTOR_TYPE__'
       1161 |         using CUDA_name##4 = HIP_vector_type<T, 4>;
            |               ^
      <scratch space>:352:1: note: expanded from here
        352 | uchar4
            | ^
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/forward.hip:14:
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/../hip_rasterizer/forward.h:18:
      In file included from /usr/local/cuda/targets/x86_64-linux/include/device_launch_parameters.h:53:
      /usr/local/cuda/targets/x86_64-linux/include/vector_types.h:148:27: error: definition of type 'short1' conflicts with type alias of the same name
        148 | struct __device_builtin__ short1
            |                           ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1187:1: note: 'short1' declared here
       1187 | __MAKE_VECTOR_TYPE__(short, short);
            | ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1158:15: note: expanded from macro '__MAKE_VECTOR_TYPE__'
       1158 |         using CUDA_name##1 = HIP_vector_type<T, 1>;\
            |               ^
      <scratch space>:361:1: note: expanded from here
        361 | short1
            | ^
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/forward.hip:14:
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/../hip_rasterizer/forward.h:18:
      In file included from /usr/local/cuda/targets/x86_64-linux/include/device_launch_parameters.h:53:
      /usr/local/cuda/targets/x86_64-linux/include/vector_types.h:153:27: error: definition of type 'ushort1' conflicts with type alias of the same name
        153 | struct __device_builtin__ ushort1
            |                           ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1186:1: note: 'ushort1' declared here
       1186 | __MAKE_VECTOR_TYPE__(ushort, unsigned short);
            | ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1158:15: note: expanded from macro '__MAKE_VECTOR_TYPE__'
       1158 |         using CUDA_name##1 = HIP_vector_type<T, 1>;\
            |               ^
      <scratch space>:357:1: note: expanded from here
        357 | ushort1
            | ^
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/forward.hip:14:
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/../hip_rasterizer/forward.h:18:
      In file included from /usr/local/cuda/targets/x86_64-linux/include/device_launch_parameters.h:53:
      /usr/local/cuda/targets/x86_64-linux/include/vector_types.h:158:40: error: definition of type 'short2' conflicts with type alias of the same name
        158 | struct __device_builtin__ __align__(4) short2
            |                                        ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1187:1: note: 'short2' declared here
       1187 | __MAKE_VECTOR_TYPE__(short, short);
            | ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1159:15: note: expanded from macro '__MAKE_VECTOR_TYPE__'
       1159 |         using CUDA_name##2 = HIP_vector_type<T, 2>;\
            |               ^
      <scratch space>:362:1: note: expanded from here
        362 | short2
            | ^
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/forward.hip:14:
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/../hip_rasterizer/forward.h:18:
      In file included from /usr/local/cuda/targets/x86_64-linux/include/device_launch_parameters.h:53:
      /usr/local/cuda/targets/x86_64-linux/include/vector_types.h:163:40: error: definition of type 'ushort2' conflicts with type alias of the same name
        163 | struct __device_builtin__ __align__(4) ushort2
            |                                        ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1186:1: note: 'ushort2' declared here
       1186 | __MAKE_VECTOR_TYPE__(ushort, unsigned short);
            | ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1159:15: note: expanded from macro '__MAKE_VECTOR_TYPE__'
       1159 |         using CUDA_name##2 = HIP_vector_type<T, 2>;\
            |               ^
      <scratch space>:358:1: note: expanded from here
        358 | ushort2
            | ^
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/forward.hip:14:
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/../hip_rasterizer/forward.h:18:
      In file included from /usr/local/cuda/targets/x86_64-linux/include/device_launch_parameters.h:53:
      /usr/local/cuda/targets/x86_64-linux/include/vector_types.h:168:27: error: definition of type 'short3' conflicts with type alias of the same name
        168 | struct __device_builtin__ short3
            |                           ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1187:1: note: 'short3' declared here
       1187 | __MAKE_VECTOR_TYPE__(short, short);
            | ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1160:15: note: expanded from macro '__MAKE_VECTOR_TYPE__'
       1160 |         using CUDA_name##3 = HIP_vector_type<T, 3>;\
            |               ^
      <scratch space>:363:1: note: expanded from here
        363 | short3
            | ^
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/forward.hip:14:
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/../hip_rasterizer/forward.h:18:
      In file included from /usr/local/cuda/targets/x86_64-linux/include/device_launch_parameters.h:53:
      /usr/local/cuda/targets/x86_64-linux/include/vector_types.h:173:27: error: definition of type 'ushort3' conflicts with type alias of the same name
        173 | struct __device_builtin__ ushort3
            |                           ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1186:1: note: 'ushort3' declared here
       1186 | __MAKE_VECTOR_TYPE__(ushort, unsigned short);
            | ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1160:15: note: expanded from macro '__MAKE_VECTOR_TYPE__'
       1160 |         using CUDA_name##3 = HIP_vector_type<T, 3>;\
            |               ^
      <scratch space>:359:1: note: expanded from here
        359 | ushort3
            | ^
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/forward.hip:14:
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/../hip_rasterizer/forward.h:18:
      In file included from /usr/local/cuda/targets/x86_64-linux/include/device_launch_parameters.h:53:
      /usr/local/cuda/targets/x86_64-linux/include/vector_types.h:178:30: error: definition of type 'short4' conflicts with type alias of the same name
        178 | __cuda_builtin_vector_align8(short4, short x; short y; short z; short w;);
            |                              ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1187:1: note: 'short4' declared here
       1187 | __MAKE_VECTOR_TYPE__(short, short);
            | ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1161:15: note: expanded from macro '__MAKE_VECTOR_TYPE__'
       1161 |         using CUDA_name##4 = HIP_vector_type<T, 4>;
            |               ^
      <scratch space>:364:1: note: expanded from here
        364 | short4
            | ^
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/forward.hip:14:
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/../hip_rasterizer/forward.h:18:
      In file included from /usr/local/cuda/targets/x86_64-linux/include/device_launch_parameters.h:53:
      /usr/local/cuda/targets/x86_64-linux/include/vector_types.h:179:30: error: definition of type 'ushort4' conflicts with type alias of the same name
        179 | __cuda_builtin_vector_align8(ushort4, unsigned short x; unsigned short y; unsigned short z; unsigned short w;);
            |                              ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1186:1: note: 'ushort4' declared here
       1186 | __MAKE_VECTOR_TYPE__(ushort, unsigned short);
            | ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1161:15: note: expanded from macro '__MAKE_VECTOR_TYPE__'
       1161 |         using CUDA_name##4 = HIP_vector_type<T, 4>;
            |               ^
      <scratch space>:360:1: note: expanded from here
        360 | ushort4
            | ^
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/forward.hip:14:
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/../hip_rasterizer/forward.h:18:
      In file included from /usr/local/cuda/targets/x86_64-linux/include/device_launch_parameters.h:53:
      /usr/local/cuda/targets/x86_64-linux/include/vector_types.h:181:27: error: definition of type 'int1' conflicts with type alias of the same name
        181 | struct __device_builtin__ int1
            |                           ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1189:1: note: 'int1' declared here
       1189 | __MAKE_VECTOR_TYPE__(int, int);
            | ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1158:15: note: expanded from macro '__MAKE_VECTOR_TYPE__'
       1158 |         using CUDA_name##1 = HIP_vector_type<T, 1>;\
            |               ^
      <scratch space>:369:1: note: expanded from here
        369 | int1
            | ^
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/forward.hip:14:
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/../hip_rasterizer/forward.h:18:
      In file included from /usr/local/cuda/targets/x86_64-linux/include/device_launch_parameters.h:53:
      /usr/local/cuda/targets/x86_64-linux/include/vector_types.h:186:27: error: definition of type 'uint1' conflicts with type alias of the same name
        186 | struct __device_builtin__ uint1
            |                           ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1188:1: note: 'uint1' declared here
       1188 | __MAKE_VECTOR_TYPE__(uint, unsigned int);
            | ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1158:15: note: expanded from macro '__MAKE_VECTOR_TYPE__'
       1158 |         using CUDA_name##1 = HIP_vector_type<T, 1>;\
            |               ^
      <scratch space>:365:1: note: expanded from here
        365 | uint1
            | ^
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/forward.hip:14:
      In file included from /tmp/pip-req-build-42j1mq4k/hip_rasterizer/../hip_rasterizer/forward.h:18:
      In file included from /usr/local/cuda/targets/x86_64-linux/include/device_launch_parameters.h:53:
      /usr/local/cuda/targets/x86_64-linux/include/vector_types.h:191:30: error: definition of type 'int2' conflicts with type alias of the same name
        191 | __cuda_builtin_vector_align8(int2, int x; int y;);
            |                              ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1189:1: note: 'int2' declared here
       1189 | __MAKE_VECTOR_TYPE__(int, int);
            | ^
      /opt/rocm-6.1.3/include/hip/amd_detail/amd_hip_vector_types.h:1159:15: note: expanded from macro '__MAKE_VECTOR_TYPE__'
       1159 |         using CUDA_name##2 = HIP_vector_type<T, 2>;\
            |               ^
      <scratch space>:370:1: note: expanded from here
        370 | int2
            | ^
      fatal error: too many errors emitted, stopping now [-ferror-limit=]
      2 warnings and 20 errors generated when compiling for gfx1100.

Operating System
WSL2 Ubuntu 22.04 Windows 11
CPU
7800x3D // 7900XT Navi 31
ROCm Version
No response
ROCm Component
HIPCC
Steps to Reproduce
No response
(Optional for Linux users) Output of /opt/rocm/bin/rocminfo --support
No response
Additional Information
No response

https://rocm.docs.amd.com/projects/HIP/en/latest/how-to/cooperative_groups.html

Unsupported NVIDIA CUDA features
HIP doesn’t support the following NVIDIA CUDA optional headers:
cooperative_groups/memcpy_async.h

cooperative_groups/reduce.h

cooperative_groups/scan.h

cooperative_groups/reduce.h is needed in both simple-knn and diff-gaussian-rasterization


Bring back the command-line utility

Sprockets 1.0 had a sprocketize command-line utility for building and installing assets. We should have something similar for Sprockets 2.1. Perhaps in conjunction with a .sprocketsrc file for setting up load paths and specifying the location of the document or dist root.

+1 Same as above. I'd love to use sprockets on a non-ruby project.

+1 ... that is all

… I'd love to use sprockets on a non-ruby project.

There's a sprockets-inspired concatenator that adds a few nifty features: https://github.com/DamonOehlman/interleave

+1

+1 ... using it as a pre-deploy hook is awesome.

I long for a CLI

I was just about to start using Sprockets only to find out from here no command line!
Making it useless for my purposes too :(

+1

All on the issue, please check out the 2.2 beta. CLI util is included.

Have pulled this and installed it but perversely am not doing anything where I'd be using it at command line at the moment, am actually currently using it in a Rack environment. Will try and play with it over the holidays and hopefully give any feedback I can after that.

Will check it out soon currently using an alternate for current projects since it wasn't available in sprockets at the time.
Will try sprockets next project as its a larger community.
Is the CLI still Sprocketize or is it something else?

Have reinstalled the sprockets gem it says version 2.2.0 but when I try the command "sprocketize" it doesnt exist.
How do you go about using this?

@rhysburnie Its just called sprockets.


transition not work

I set prop transition="zoom-in-top"，but it's not work
.zoom-in-top-enter-active,
.zoom-in-top-leave-active {
opacity: 1;
transform: scaleY(1);
transition: all 0.2s ease;
transform-origin: center top;
}
.zoom-in-top-enter,
.zoom-in-top-leave-active {
opacity: 0;
transform: scaleY(0);
}

OK, I developed v-popper by myself


SCP-4881 Fixed loss of redeemer bytes in chain index

The Redemer from the block is represented as MemoizedBytes, which includes an originalBytes function for retrieving the actual on-chain bytes. Deserializing and the serializing does not yield the same CBOR bytes, but this round-trip serialization was what was stored in the database record. This PR retains the original bytes.
Tested via:

100% match now for redeemer bytes between marlowe-chain-indexer versus cardano-db-sync for both preprod and preview networks. (Formerly there had been a one-byte shortage on the Marlowe side.)
Ran two contracts on preprod to make sure marlowe-tx still worked.
Successfully deserialized all Marlowe contracts on preprod using marlowe-finder.

Pre-submit checklist:

Branch

[ ] Tests are provided (if possible)
[ ] Test report is updated (if relevant)
[x] Commit sequence broadly makes sense
[x] Key commits have useful messages
[x] Relevant tickets are mentioned in commit messages
[x] Formatting, materialized Nix files, PNG optimization, etc. are updated

PR

[x] Self-reviewed the diff
[x] Useful pull request description
[x] Reviewer requested

Did you check that the result deserializes properly?

Yes and no, @jhbertra, I've looked into this very interesting question. Here is what I've found:

The ledger specification does require that plutus_data be the CBOR serialization of Data.
There are datums on the ledger that have extra bytes beyond the CBOR serialization, and this doesn't seem to be simple padding. Some CBOR deserializers will report that there are extra trailing bytes. However, those extra bytes were hashed when originally computing the datum, so they cannot be safely discarded.
All of the Marlowe datums have proper CBOR with no extra trailing bytes.
My conjecture is that some folks are using non-Haskell CBOR libraries to serialize their datums, and these trailing bytes are an artifact. We'd have to run these third-party Plutus scripts against the datum and redeemer on chain to verify that the node is ignoring the trailing bytes etc. when calls the untyped validator as BuiltinData -> BuiltinData -> BuiltinData -> ()

For the chain index, I think it is safest to take the bytes and hash as they appear on the ledger and not to check their conformance and CBOR deserialization: otherwise, we'd be second-guessing the ledger. This problem is irrelevant for all Marlowe contracts, but someday we might be running Marlowe and Plutus in the same tx, so I think we should respect the on-chain data, since that is what the Plutus scripts are expecting.


[Bug] Radarr not adding Freeleech indexer flag to custom format score on search

Which Guide
No guide, general use of custom formats and freeleech indexer flag and scores not calculating correctly.
Describe the Error in the Guide
Custom indexer score is not generating correctly when searching indexer items that have a freeleech flag. However, if downloaded manually the history shows the "FreeLeech" custom format tag and correct score.
Expected behavior
An item that has a freeleech flag should add the custom value to the score on search.
Screenshots

Additional context
Version
<IP_ADDRESS>83
Package Version
nightly-9f4152d by hotio

Trace logs
https://pastebin.com/ytmFhyMv

=> Radarr GHI
not a guide issue


Clean up docs/ folder

I spent some time looking through the docs folder today and found a couple things to clean up.

LGTM


Tmux

@stites @rycee - What is the benefit of using this module over programs.tmux in nixpkgs (which I currently use)?

@srid Well, I guess the major difference is that the one in Home Manager is per-user while the NixOS one is system wide.
The other differences, from what I can tell, are that the NixOS one does not provide tmux plugin management while the HM one at the moment does not provide detailed options such as historyLimit, keyMode, etc.
I don't use tmux so I can't say which one is best to use, I think it will depend on your needs.

The primary motivator was replacing tpm with nix. Looking at the options available. It's unclear to me if a nixpkg user can access these configurations in nixos modules.
That said, I didn't even realize there were these sorts of options were available -- is it possible to configure packages like this if you are on, say, arch or ubuntu?.

Is it not possible to extend the original nixpkgs module, and re-use it in home-manager? For the benefit of having a single source of truth, as it were.

@srid Unfortunately no, there is no easy way to share module implementations between projects. I have attempted it a few times but it's always lead to difficulties. I believe there should be a way to do it but right now I'm not certain what the solution might be.

I wholeheartedly agree! Since it seems like home-manager is easier to deploy remotely and runs on non-nixos boxes, I'm of the opinion that everything should be migrated here. That said, I won't have time to work on this until the holidays -- if someone else wants to take a crack at this, please do so!


Problem with installation

Hi,
I'm unable to run the setup as the following error pops up. What am I missing?

You don't have aspell headers installed.

How to install them?? Do you know?

I don't use Windows, so maybe it's not the best pointer. Please look at http://aspell.net/win32/, the section "Development" contains some headers and libraries. Read also http://aspell.net/win32/Readme-win32.txt -- it seems that is not so easy. (However, my friend somehow compiled the extension years ago.)

@sizhky have you finally compiled the module? Can I close this issue?

Yeah, no I didn't bother to compile.
I used a different tool to get my work done, so we can consider this issue closed.


Add lookahead

Add API for accepting optional lookahead. Use this lookahead to reduce the number of items and parse forest nodes that are created.
Tradeoff: on one side, less items produced. On the other side, more complex logic within tight loops, and branch mispredictions.

Implemented in https://github.com/pczarn/gearley/commit/cd98a461ceeb240b1bebe259c21e138a264d67c3


Create example JALSE project

Create example JALSE project to go with release. Maybe cows in a field.

https://github.com/Ellzord/JALSE-HappyCows


Remove notebooks and publications from git history

Up to empymod v1.3.0 the repo contained two more directories, notebooks and publications, which where moved into their own repos afterwards (example-notebooks and publications was split into article-geo2017 and article-tle2017).
A current check-out of the empymod-repo is almost 80 GB. I suspect that probably about 80 % of this weight is due to these two old directories (notebooks and figures for the publications). The other 20 % are mostly due to data in the test-directory.
It could be a good thing to get rid of that ballast. But it means messing with the git history, so it has to be done very carefully.

Similarly, move old, unused branches into an own repo or delete them.

Won't do it. The gain is little (a few dozen MB in case you clone the repo), and the uncertainties by messing with the git history too big (what happens with the links to zenodo, travis-ci, readthedocs, coveralls)? Let's look at this as historic baggage. Maybe I'll re-visit this if a major new version would come along (with the planned but probably never materializing abstraction of the code base).


[BSO] Mass watcher

Description:

BSO Mass Channel is cancer

Changes:

Adds a new monitor to remove everything that isn't =mass / =pingmass / =groupkill

[X] I have tested all my changes thoroughly.

Not in favour of this. I would rather just lock the channel so only hosters can talk in it.


[Folder Search] Extension not working

Extension
https://www.raycast.com/GastroGeek/folder-search
Description
Whetever I look for, there are no results.
https://user-images.githubusercontent.com/54178949/214118392-856eeff4-e6b9-4687-a1ec-6ba8c2666e12.mp4
Steps To Reproduce
No response
Current Behaviour
No response
Expected Behaviour
No response

I wonder if this is a spotlight issue. Does File search work for you?

@omarshahine yeah, Spotlight and the Raycast File Search feature are working perfectly fine. Thanks!

@GastroGeek might have ideas as he authored 99% of the extension including this piece.

FYI: extension started working after I've set macOS in English language (instead of Italian).

I have the same Problem, German language, same as @flegfleg i don't want to change to english. Thanx @GastroGeek and @omarshahine 😊

Are any of willing to install https://github.com/derhuerst/node-spotlight and see if you have the same problem?
The extension is just a wrapper for node-spotlight.

I have looked at this and honestly have no idea what it is, how to install it and what will happen after installation and/or how to test it. Even less do I know what a wrapper for node-spotlight is. Sorry, I am only a user and unfortunately completely lost 🤷♂

I found the problem, now I have to fix it.
@raycastbot can you merge this issue with https://github.com/raycast/extensions/issues/6559

I have a fix and am now testing it out.

Merged and closed, please give it a shot @andreaguida  - you can run Check for extension Updates to ensure you have the newest update


[Gitlab] : Pull request messages are not formatted

Since dependabot use github flavored markdown, the messages are not correctly formatted when displayed on a gitlab Merge request.

Is there an example PR you can link to? Would help with fixing!

Do you have a login on gitlab ?

Yep - I'm @greysteil there, too.

I gave you access

Ah, I see, looks like this is specific to the markdown in the <details> tags. Annoying that GitLab doesn't support that! Wouldn't be too hard to convert it all to html, though.

It looks like this was fixed? e.g. https://gitlab.com/deivid-rodriguez/nipanipa/merge_requests/548

Excellent news! 🎉

I suspect this is because GitLab now uses common mark for its Markdown rendering, if anyone was wondering how it got fixed :)

Yeah - I'm guessing so. I didn't do anything on it. Very pleased they're using the same standard as GitHub!


Change server port

How i can change the server port, without extrating the .war file? I don´t know how i can extract the file and compact again...

You can place an application.yml in the same location as the .war and it will read settings from it. See the sample_application.yml


💄Fix log.* method calls which meant to be log.*f

Stuff like log.Debug("foo bar: %s", baz) really wants to be log.Debugf("foo bar: %s", baz)...
Signed-off-by: Dave Henderson<EMAIL_ADDRESS>

:smile: LGTM

LGTM
@nathanleclaire wdyt?

LGTM thanks @hairyhenderson !


bugfix when build project

Signed-off-by: wuxc<EMAIL_ADDRESS>

Can you rebase the change to the tip of master?

Can you rebase the change to the tip of master?


EXC_BAD_ACCESS when using the sdk with firebase

Hello,
I have encountered an issue trying to use the plugin with Unity 2018.4.10, the issue is the plugin runs if I add it to an empty project, but when I add it to my project that has firebase with it and build it for IOS, XCode gives the following error :
EXC_BAD_ACCESS at #0	0x0000000105a5b660 in google::protobuf::internal::(anonymous namespace)::InitSCC_DFS(google::protobuf::internal::SCCInfoBase*) at /Users/jballoffet/Documents/PublicBuild/Crosscompilation/Latest/iOS/protobuf/src/google/protobuf/generated_message_util.cc:778
So I think protobuf is having a conflict with one of the plugins I have in the project, the plugins I have in the project :
Vuforia,Firebase,Tour360
my best guess is that it's Firebase having the same plugin and trying to initialize it twice, but I can't find the dll of protobuf anywhere else in the project and if I delete it, an error occur, so any idea of how to fix this ?
Thanks in advance

This is a hard one to debug, and I need more information to identify the issue.

When does this happen? During compile or during runtime? Does this happen before the app starts or after your splash screen shows up?
Can you post the full stacktrace here? I believe there is more to this than the single "at line".

@cdytoby Also happening here.
Using Unity 2018.4.15f1 with firebase in the project.
The error happens when trying to open the app, it throws this error and doesn't open

This is all there is in the logs.
Haven't tried without firebase in the project.

While trying it out myself, I'll mark it as help wanted.

@Dankann @AlyAmeen
Which firebase packages did you use? there are many of them.

Note for me: https://firebase.google.com/docs/unity/setup#add-sdks-upm
Firebase has unity package manager support.

Hi! I'm having the same problem in iOS. @cdytoby
I've read your developer statement regarding that you've stopped active maintenance and switched to intermittent check to this repository. Thankyou for your hard work for this repo and I wish you good luck for what's to come.
I'm using unity 2018.4 and firebase 6.14 (also tried 6.16.1 with the same result).
I've also tried enabling zombie objects in Xcode without result.
The package I'm using is:

Function
Storage
App (Core)
Auth
Messaging
Crashlyrics
Analytics

Here is my backtrace from lldb

Other than that I've realised that the same GoogleProtobuf can exist in the project without any compile issues. this plugin (Assets/Cardboard/Plugins/GoogleProtobuf.dll) and GVR obsolete SDK (Assets/GoogleVR/Plugins/Google.ProtocolBuffers.dll) is it the same case with firebase libraries? "Different dll name but same compiled object class name in runtime"
Though there wouldn't possibly be a fix in the near future, I would really appreciate if you can provide any leads on what's the root cause what should I try to help progress on this issue.


estimate dislikes count

Can't you deduce the dislike count with the up votes and the rating? I'm assuming it's just a simple ratio.

The rating is itself already estimated from the likes / views: see https://github.com/trizen/pipe-viewer/blob/main/lib/WWW/PipeViewer/Utils.pm#L783 and
https://github.com/trizen/pipe-viewer/blob/main/lib/WWW/PipeViewer/Utils.pm#L377.


Support vLLM as the inference server

vLLM is a popular choice for serving LLMs in production. It also has a strong community and iterates fast to support new models.

Verified on main 9621cd3.


Linux Settings, tree too small crash

In Linux if you make the tree too small when you try to reload it will crash with a BadItem crash. See CrashLogs:
https://github.com/meerk40t/meerk40t/projects/6
MeerK40t crash log. Version: 0.7.2 on linux - 4.1.1 gtk3 (phoenix) wxWidgets 3.1.5
Traceback (most recent call last):
  File "wx/core.py", line 3407, in <lambda>
  File "meerk40t/kernel.py", line 1705, in process_queue
  File "meerk40t/gui/wxmeerk40t.py", line 2327, in on_rebuild_tree_signal
  File "meerk40t/gui/wxmeerk40t.py", line 3482, in rebuild_tree
ValueError: Bad Item

https://github.com/meerk40t/meerk40t/commit/d636f53fb37821d9773d9b2ada661ccd7055dc85
Found and fixed.

Corrected.


Default voicemail_ok? to false

I rule and have completed some work on Case Manager that's ready for review!
Defaults voicemail_ok to false; adds it to the new call partial; cleans up the new call partial a little bit.
It relates to the following issue #s:

Fixes #484

[Current coverage][cc-pull] is 99.45%

Merging [#500][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master       #500   diff @@
==========================================
  Files            23         23
  Lines           368        368
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            366        366
  Misses            2          2
  Partials          0          0

Powered by Codecov. Last updated by [9076baf...d330f40][cc-compare]
[cc-base-branch]: https://codecov.io/gh/colinxfleming/dcaf_case_management/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/colinxfleming/dcaf_case_management/compare/9076baf3627d8ccafd897cb7803fda7884360b4a...d330f4034a6776ee4c3bf52a17d340c48e4cdba1?src=pr
[cc-pull]: https://codecov.io/gh/colinxfleming/dcaf_case_management/pull/500?src=pr


Map don't show up on first run

When you open the app and run a query, the map does not show up at first. But when you go back and try again it works.

Seems to be solved after update to RC.


Add SASS support documentation #1007

As pointed out in https://github.com/facebookincubator/create-react-app/issues/1007, adding a specific section about SASS in documentation could help users avoid ejecting in order to use sass-loader.
This is simpler in my opinion and more aligned to this project's way of thinking.

ℹ Quick tip about the example, node-sass with the --watch option does not initially build the output until a change is made on the input. It could end up with importing errors if the output file is not versioned for example.
Maybe you could chain with an initial build before the watch in the example?

Hi @gaearon, would you like to take a look at this? I think it is helpful but haven't seen any words from maintainers yet

Thank you for your feedback! Unfortunately, I don't have access to a Windows development environment and no previous experience developing on Windows.
Also, a known issue with watch-css script is that when you kill the process, node-sass is not. I'm looking for a workaround.

Does this mean that it is possible to add Sass support without ejecting ?

@jonathanphz yes it is

Random, unless I'm missing something (and I wouldn't put it past myself), node-sass still has the problem of not watching newly added files or stopping removed ones.
You can still have an external watcher build it into scss for you.  Although it's not purely ideal, I've settled on a docker ruby/sass containe just watching our project files and compiling the scss ones down into css.  On release, the scss files are removed before being pushed to built/prod.  You could also just do this with something on your local machine too I suppose if you're not worried about versions between teammates.

I would love to merge this, would anyone care to update?

I’ll make some changes and get it in.

Random, unless I'm missing something (and I wouldn't put it past myself), node-sass still has the problem of not watching newly added files or stopping removed ones.

Yea, seems like this is a problem. (But it should be reported to node-sass if you’re using it 😉 ).

I slightly tweaked it:

Used a diff highlighting
Changed the command to build a separate CSS file for each SCSS file
Added a warning that you might not need a preprocessor

Thank you so much for getting this rolling!

Without ejecting, how do you watch subdirectories for scss import changes so your main.scss automatically compiles?
I'm assuming it's a tweak to this line in the package.json:
"watch-css": "npm run build-css && node-sass src/**/ -o src/ --watch --recursive",

Yes, you can see this in the documentation: https://github.com/facebookincubator/create-react-app/blob/master/packages/react-scripts/template/README.md#adding-a-css-preprocessor-sass-less-etc
😄

@Timer Thanks for the quick response, I have already implemented this section.
Below is my folder structure, main.scss lives in the /src directory, but my includes live within the styles folder. Now every time I update  /src/styles/pages/_admin.scss the watcher isn't aware of the changes, I actually have to open and resave main.scss for it to grab those changes. I'm wondering if there is a glob pattern or something like it where the watcher will pick up the subfolder changes and recompile main.scss

Oh I'm sorry, I thought you were suggesting to use --recursive. This seems like something you want to ask the node-sass people. 😅
I assume you're talking about the sass watcher and not our watcher.

I wasn't sure what I needed to do, I was trying to avoid exiting to create custom configs for now.  I'll ask them about it, thanks!


Issue compiling with 0.20.2

I'm not sure if this is the right place, but I'm working on the ESP channel, and compiling 0.20.2 doesn't work, while 0.19.1 seems to be fine.
Let me know if there is anything else I can do to diagnose anything!
    Checking crossbeam-utils v0.8.8
   Compiling gbplay-rs v0.1.0 (/workspaces/gbplay/esp/gbplay-rs)
error[E0432]: unresolved imports `core::sync::atomic::AtomicI64`, `core::sync::atomic::AtomicU64`
  --> /opt/cargo/registry/src/github.com-1ecc6299db9ec823/crossbeam-utils-0.8.8/src/lib.rs:79:49
   |
79 |             pub(crate) use core::sync::atomic::{AtomicI64, AtomicU64};
   |                                                 ^^^^^^^^^  ^^^^^^^^^ no `AtomicU64` in `sync::atomic`
   |                                                 |
   |                                                 no `AtomicI64` in `sync::atomic`
   |
help: a similar name exists in the module
   |
79 |             pub(crate) use core::sync::atomic::{AtomicI8, AtomicU64};
   |                                                 ~~~~~~~~
help: a similar name exists in the module
   |
79 |             pub(crate) use core::sync::atomic::{AtomicI64, AtomicU8};
   |                                                            ~~~~~~~~

error[E0412]: cannot find type `AtomicU64` in module `core::sync::atomic`
    --> /opt/cargo/registry/src/github.com-1ecc6299db9ec823/crossbeam-utils-0.8.8/src/atomic/consume.rs:78:14
     |
78   |   impl_atomic!(AtomicU64, u64);
     |                ^^^^^^^^^ help: a struct with a similar name exists: `AtomicU16`
     |
    ::: /opt/rustup/toolchains/esp/lib/rustlib/src/rust/library/core/src/sync/atomic.rs:2148:1
     |
2148 | / atomic_int! {
2149 | |     cfg(target_has_atomic = "16"),
2150 | |     cfg(target_has_atomic_equal_alignment = "16"),
2151 | |     stable(feature = "integer_atomics_stable", since = "1.34.0"),
...    |
2164 | |     u16 AtomicU16 ATOMIC_U16_INIT
2165 | | }
     | |_- similarly named struct `AtomicU16` defined here

error[E0412]: cannot find type `AtomicI64` in module `core::sync::atomic`
    --> /opt/cargo/registry/src/github.com-1ecc6299db9ec823/crossbeam-utils-0.8.8/src/atomic/consume.rs:80:14
     |
80   |   impl_atomic!(AtomicI64, i64);
     |                ^^^^^^^^^ help: a struct with a similar name exists: `AtomicI16`
     |
    ::: /opt/rustup/toolchains/esp/lib/rustlib/src/rust/library/core/src/sync/atomic.rs:2129:1
     |
2129 | / atomic_int! {
2130 | |     cfg(target_has_atomic = "16"),
2131 | |     cfg(target_has_atomic_equal_alignment = "16"),
2132 | |     stable(feature = "integer_atomics_stable", since = "1.34.0"),
...    |
2145 | |     i16 AtomicI16 ATOMIC_I16_INIT
2146 | | }
     | |_- similarly named struct `AtomicI16` defined here

Some errors have detailed explanations: E0412, E0432.
For more information about an error, try `rustc --explain E0412`.
error: could not compile `crossbeam-utils` due to 3 previous errors
[Finished running. Exit status: 101]

This is the right place. Here's some extra info that can help:

What is the version of your compiler? Recent esp-rs compilers do support AtomicU64, earlier ones don't.
What is the chip you are compiling for? RiscV or ESP32*?
Are you having the isr-async-executor feature enabled? In theory, the crossbeam dependency should be part of the build only if this feature is enabled. By the way, this feature (and the 0.20.2 release) is brand hot new (from today); note that if you enable this feature, it will enable a bunch of other experimental features as well.

I'm using Esppressif's Docker image espressif/idf-rust-examples, and it comes with the esp target/toolchain preinstalled. How can I gather more information about the environment?
root@a90d7c5a54b1:/workspaces/gbplay/esp/gbplay-rs# rustup --version
rustup 1.24.3 (ce5817a94 2021-05-31)
info: This is the version for the rustup toolchain manager, not the rustc compiler.
info: The currently active `rustc` version is `rustc 1.58.0-dev`

I'm compiling for ESP32* (specifically ESP-WROOM-32 Chip CP2102 for ESP32 according to the Amazon page.
As far as I know, I don't have isr-async-executor feature enabled. I'm just using cargo check on this Cargo.toml:
[package]
name = "gbplay-rs"
version = "0.1.0"
authors = ["Forest Anderson<EMAIL_ADDRESS>edition = "2018"
resolver = "2"

[patch.crates-io]
smol = { git = "https://github.com/esp-rs-compat/smol" }
polling = { git = "https://github.com/esp-rs-compat/polling" }
socket2 = { git = "https://github.com/esp-rs-compat/socket2" }
getrandom = { version = "0.2", git = "https://github.com/esp-rs-compat/getrandom.git" }

[profile.release]
opt-level = "s"

[profile.dev]
debug = true # Symbols are nice and they don't increase the size on Flash
opt-level = "z"

[features]
pio = ["esp-idf-sys/pio"]

[dependencies]
esp-idf-sys = { version = "0.31.0", features = ["binstart"] }
esp-idf-svc = "0.39.2"
esp-idf-hal = "0.35.2"
embedded-svc = "0.19.1"
# tiny_http = "0.11"
anyhow = {version = "1", features = ["backtrace"]}
log = "0.4"
url = "2"
embedded-hal = "0.2"
embedded-graphics = "0.7"
display-interface = "0.4"
display-interface-spi = "0.4"
st7789 = "0.6"
ili9341 = { version = "0.5", git = "https://github.com/yuri91/ili9341-rs" }
ssd1306 = "0.7"
epd-waveshare = "0.5.0"
smol = "1.2"

[build-dependencies]
embuild = "0.28"
anyhow = "1"

Argh, I've accidentally left alloc enabling crossbeam: https://github.com/esp-rs/embedded-svc/commit/f794828cd79f171acb05e265f4f1138c91a1a50e
I'll release 0.20.3 shortly and yank the 0.20.2 one. Today is not my day for releasing. This would be the third yanked 0.20 release in 5 hours. :)

:smile: no worries! Thanks for your quick responses, and looking into the issue already. As I'm diving deeper into embedded Rust, I'm finding more and more with your name on it, so I greatly appreciate your work in the ecosystem :) Thanks!

Released. If you could try the build again. You might have to remove manually the 0.20.2 release somehow from your machine, so that it picks up the 0.20.3. Please don't change anything else and just let me know whether it now compiles cleanly.

Awesome! :+1: as far as I can tell, that not only let me push embedded-svc's version, but also esp-idf-svc and esp-idf-hal. Looks like we're good :)


Fixed query parameters causing route matching problems

Codecov Report

Merging #37 (69d4f73) into master (0c9d6bc) will decrease coverage by 2.04%.
The diff coverage is 45.45%.

@@            Coverage Diff             @@
##           master      #37      +/-   ##
==========================================
- Coverage   87.53%   85.48%   -2.05%
==========================================
  Files           6        6
  Lines         353      317      -36
==========================================
- Hits          309      271      -38
  Misses         42       42
- Partials        2        4       +2

Impacted Files
Coverage Δ

services/server.go
93.54% <33.33%> (-6.46%)
:arrow_down:

services/route_matcher.go
89.47% <60.00%> (-10.53%)
:arrow_down:

services/authorizer.go
96.22% <0.00%> (-0.70%)
:arrow_down:

services/authenticator.go
100.00% <0.00%> (ø)

services/config_parser.go
100.00% <0.00%> (ø)

main.go
34.48% <0.00%> (+1.14%)
:arrow_up:

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 0c9d6bc...69d4f73. Read the comment docs.


Calling DateTime.Now property for the first time causes an unwanted delay

Godot version
v3.4.4.stable.mono.official [419e713a2]
System information
Android
Issue description
Tested on both Samsung SM-A127F (Android 12, arm64-v8a, physical device) and Google Pixel (Android 11 x86, emulated device)
As seen on the screenshot below, there's a quite big time difference between the two first calls on Android.

There's no such a big delay on desktop though.

Steps to reproduce
I ran into this issue while using DateTime.Now property in overridden _Process method.
Minimal reproduction project
No response

Please provide a project, we don't know what code you're running and what these times account for.
There seems to be a delay on both screenshots, the first time is half of the second in both.

@akien-mga

Please provide a project, we don't know what code you're running and what these times account for.

here is some really basic example project. the sprite wouldn't start moving immediately if you touch the screen because of getting the current date.
TestProject.zip

There seems to be a delay on both screenshots, the first time is half of the second in both.

these values represent current number of milliseconds according to DateTime.Now prop. they don't matter themselves in this case, but their difference does. i've updated screenshots with deltaTime output to be more clear

@Calinou This is a Mono specific bug, DateTime.Now is a .NET API.

here is some really basic example project. the sprite wouldn't start moving immediately if you hold the screen because of getting the current date.
TestProject.zip

In action, screen recording (Xiaomi Redmi Note 9 Pro, Android 11) slowed to 0.25X speed:
https://user-images.githubusercontent.com/9283098/182154640-e25b6ece-3362-4426-bb8f-120c8358750a.mp4
https://user-images.githubusercontent.com/9283098/182154637-2348db6e-29f5-424c-b4de-08181761081a.mp4


"ntwin32.mak file not found" error when attempting to build

Using the quickstart guide on the official website I've been stuck on step 4 that says:
"Build GA by running 'nmake /f NMakefile all' command in the 'ga' directory."
It gives me the error mentioned above. I installed microsoft sdk and VS 2010 C++ redistributable (from the same installer) successfully, acquired a ntwin32.mak file from the internet and pasted it into the only include folder withing the entire project and still it doesnt work, can anyone help? My system is 64 bit just in case.
Microsoft (R) Program Maintenance Utility Version 11.00.61030.0
Copyright (C) Microsoft Corporation.  All rights reserved.
    cd core && nmake /f NMakefile && cd ..

Microsoft (R) Program Maintenance Utility Version 11.00.61030.0
Copyright (C) Microsoft Corporation.  All rights reserved.
..\NMakefile.def(10) : fatal error U1052: file 'ntwin32.mak' not found
Stop.
NMAKE : fatal error U1077: 'cd' : return code '0x2'
Stop.

@jmzg1229   Hi,I got a same problem (fatal error U1052: file 'ntwin32.mak' not found), I found resolutions everywhere but it still doesn't work.
How did you figure it out?

Are you working with visual studio 2013? GA has to work with visual studio
2010.
Chun-Ying
On Thu, Sep 24, 2015 at 11:29 PM, wxj2829232101<EMAIL_ADDRESS>wrote:

@jmzg1229 https://github.com/jmzg1229 Hi,I got a same problem (fatal
error U1052: file 'ntwin32.mak' not found), I found resolutions everywhere
but it still doesn't work.
How did you figure it out?
—
Reply to this email directly or view it on GitHub
https://github.com/chunying/gaminganywhere/issues/6#issuecomment-142963468
.

Thank you!
I was working with visual studio 2015. Now I change to work with visual studio 2010, and the problem is gone.


Improve coverage on occt related classes

more info here: https://gitlab.kitware.com/f3d/f3d/-/issues/99

according to codecov, this is fine.


[feature-request] Support sparse-checkout

git 2.25+ allows tracking of partial repository directories through sparse-checkout. This is useful when a project needs only a limited set of packages in a monolithic repository. E.g. swri_yaml_util in swri-robotics/marti_common.
I've been working on a branch to adapt vcs to do sparse-checkouts for our CI/CD pipeline. If you approve of the approach and are comfortable accepting git specific functionality, I can make a PR.
Proposed changes:
YAML

New "subpaths" key specifies sparse-checkout patterns for repository. Key is the same level as url/uri.

Example from above, with a second package specified.
# VCS Format
repositories:
  marti:
    type: git
    url: https://github.com/swri-robotics/marti_common.git
    version: master
    subpaths:
      - swri_yaml_util
      - swri_console_util

import_.py

Add subpaths member to ImportCommand
Parsing logic for subpaths in get_repos_in_vcstool_format and get_repos_in_rosinstall_format
Include subpaths in generate_job

Git Client

Add check for git version > 2.25.0 when "subpaths" key is found in import/export
Import

Match sparse-checkout patterns when determining if existing repo matches yaml specification
If subpaths in command

Clone with --no-checkout
Initialize sparse repo with --cone
Set sparse-checkout patterns to space separated list of subpaths
Verify that subpaths exist in final repo, warn if they do not (to protect against typos in subpath specification)

Export

Add subpaths (if any exist) to export_data key

+1
I discussed offline with @aaronplusone  and suggested:

Backup compatibility: i.e. the tool should not fail when 1) the option to trigger the new feature is not passed, 2) the underlining functionality is not available in non-git vcs tool.

For non-git, handle unimplemented feature and behave the same way that the tool works without the option.

+1
I discussed offline with @aaronplusone and suggested:
* Backup compatibility: i.e. the tool should not fail when 1) the option to trigger the new feature is not passed, 2) the underlining functionality is not available in non-git `vcs` tool.

  * For non-`git`, handle unimplemented feature and behave the same way that the tool works without the option.

At least for git, adding a key prior to this PR would still clone the repository if the rest of the yaml entry was correct. I'm assuming cloning in other version control systems would work the same way. Assuming it does, is it better to pull in the entire repo or to fail? I could see cases for either.


It's broken!

"Unable to connect to your device with those details. It could be an intermittent issue, or they may be incorrect."
I think it's not a intermittent issue.  It's a permanent issue.
I entered my information EXACTLY the same as tinytuya python script which works!

This tracker is for bug reports, not complaints without detail

@make-all, first of all, thank you for your hard work! I had been avoiding using local Tuya due to the difficulty of obtaining all the required keys. Yesterday, I discovered your project and was very happy until I encountered "Unable to connect" error. I'm new to homeassistant and smart home stuff, so if you need logs - tell me, I will send them as soon as I figure out how.
I am using a Tuya Zigbee hub to control my devices. With this integration, I was able to add two devices without any problems. However, I soon ran into this error. My Zigbee hub's IP address is <IP_ADDRESS>, and both devices that I have successfully added, used this IP address. For the remaining devices that were also controlled by Zigbee Hub, they also used this same IP, but I was unable to add them. Maybe there is a limit of how many devices you can control using one IP address? I managed to add another device through this integration, though that device was using a different IP address.

So far I have tried using all available protocol versions, rebooting my Raspberry Pi, reconnecting Zigbee devices, but no luck…


Meteor 1.3 error

Error when trying to upload a file with meteor 1.3:
//client
{error: 400, reason: "Match failed", details: undefined, message: "Match failed [400]", errorType: "Meteor.Error"}
//server
Exception while invoking method 'slingshot/uploadRequest' Error: Match error: Failed Match.OneOf or Match.Optional validation
//more info
Works fine on Meteor 1.2

https://github.com/meteor/meteor/issues/5712

Have you resolved the issue? I'm on meteor 1.2 and it throws same error.

I had same error when sending only string to Slingshot.Upload("directiveName", param) <-- here param should be object not a string.


Check path for maven capability

Updated powershell script to look for maven in the path if maven home environment variable isn't set.

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

@madhurig

I updated the PR to use the helper capability function.
From: Madhuri Gummalla<EMAIL_ADDRESS>Sent: Friday, September 22, 2017 10:35 AM
To: Microsoft/vsts-agent<EMAIL_ADDRESS>Cc: Kellie Jos<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Microsoft/vsts-agent] Check path for maven capability (#1218)
@madhurig commented on this pull request.

In src/Misc/layoutbin/powershell/Add-MavenCapabilities.ps1https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fvsts-agent%2Fpull%2F1218%23discussion_r140510072&data=02|01|Kellie.Jos%40microsoft.com|a5e7507477304f5cf71808d501c71448|72f988bf86f141af91ab2d7cd011db47|1|0|636416876912877906&sdata=RaIG%2BVogC8ibRbhlAKz8VWRUBQMhVCPA7cn2cAi8%2BPY%3D&reserved=0:

@@ -1,10 +1,40 @@

[CmdletBinding()]
param()
+function Get-MavenDirectoryFromPath {
There is also a module you can use: https://github.com/Microsoft/vsts-agent/blob/f7e9a7ee42d0c30f0d31d449bb51d95bd6e9e0fb/src/Misc/layoutbin/powershell/CapabilityHelpers/CapabilityFunctions.ps1#L1https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fvsts-agent%2Fblob%2Ff7e9a7ee42d0c30f0d31d449bb51d95bd6e9e0fb%2Fsrc%2FMisc%2Flayoutbin%2Fpowershell%2FCapabilityHelpers%2FCapabilityFunctions.ps1%23L1&data=02|01|Kellie.Jos%40microsoft.com|a5e7507477304f5cf71808d501c71448|72f988bf86f141af91ab2d7cd011db47|1|0|636416876912877906&sdata=UikQrnIM2QBy39ewSBXpRgLBwONL%2B4MXsCKshpUOboA%3D&reserved=0
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fvsts-agent%2Fpull%2F1218%23discussion_r140510072&data=02|01|Kellie.Jos%40microsoft.com|a5e7507477304f5cf71808d501c71448|72f988bf86f141af91ab2d7cd011db47|1|0|636416876912877906&sdata=RaIG%2BVogC8ibRbhlAKz8VWRUBQMhVCPA7cn2cAi8%2BPY%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAeBaAWGzhaK5iTONh_DCD_SSBvS8BByNks5sk8WIgaJpZM4PgwuX&data=02|01|Kellie.Jos%40microsoft.com|a5e7507477304f5cf71808d501c71448|72f988bf86f141af91ab2d7cd011db47|1|0|636416876912877906&sdata=URQYbDQzs7%2BaIQEg3voCQUY5Qk72yOkx3jd%2FLUpjhMc%3D&reserved=0.


Make tutorial

it can be a video, or text, and you can clobber Tutorial.vue with your tutorial

Ott: write about addresses: directions, street types (what is avenue court, what is SR (= state route)), etc

Should contain two components:

[ ] tutorial: hands-on tutorial how to use the app

[ ] a text document that explains more complex concepts in more detail (say, street types and such)


Publish on web project does not copy the dacpac file

This might be a configuration issue, but i have tried everything i can and been to every corner of the world wide web.
I have followed this from the .md

This is what it looks like in my Web project. The *.Database.Build project is the relevant one.

So what happens is when publishing, is that the file is not there in the publish folder. But interestingly enough, when just building the project, it does get into the bin folder. For some reason they there is a miss alignment :(

Any help would be appreciated !

<PropertyGroup>
	<TargetFramework>net6.0</TargetFramework>
	<Nullable>disable</Nullable>
	<TypeScriptCompileBlocked>true</TypeScriptCompileBlocked>
	<TypeScriptToolsVersion>Latest</TypeScriptToolsVersion>
	<IsPackable>false</IsPackable>
	<SpaRoot>ClientApp\</SpaRoot>
	<DefaultItemExcludes>$(DefaultItemExcludes);$(SpaRoot)node_modules\**</DefaultItemExcludes>
	<ImplicitUsings>enable</ImplicitUsings>
</PropertyGroup>

<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|AnyCPU'">
	<NoWarn>1701;1702;TS1005;</NoWarn>
	<WarningLevel>4</WarningLevel>
</PropertyGroup>

<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|AnyCPU'">
	<NoWarn>1701;1702;TS1005;</NoWarn>
	<WarningLevel>4</WarningLevel>
</PropertyGroup>

<!--<ItemGroup>
	<Script Include="**" Exclude=“*.esproj;node_modules\**“ />
</ItemGroup>-->

<ItemGroup>
	<PackageReference Include="Microsoft.AspNetCore.SpaServices.Extensions" Version="6.0.1" />
	<PackageReference Include="Microsoft.EntityFrameworkCore.InMemory" Version="6.0.1" />
	<PackageReference Include="Microsoft.Identity.Web" Version="1.22.1" />
	<PackageReference Include="Microsoft.Identity.Web.MicrosoftGraph" Version="1.22.1" />
	<PackageReference Include="Microsoft.SqlServer.DacFx" Version="160.5400.1" />
	<PackageReference Include="Swashbuckle.AspNetCore" Version="6.2.3" />
</ItemGroup>

<ItemGroup>
	<!-- Don't publish the SPA source files, but do show them in the project files list -->
	<Content Remove="$(SpaRoot)**" />
	<None Remove="$(SpaRoot)**" />
	<None Include="$(SpaRoot)**" Exclude="$(SpaRoot)node_modules\**" />
</ItemGroup>

<ItemGroup>
	<Script Include="**" />
	<Script Remove="**.d.ts" />
</ItemGroup>

<ItemGroup>
	<Script Remove="Migration\DacpacService.cs" />
</ItemGroup>

<ItemGroup>
	<Folder Include="Authentication\" />
</ItemGroup>

<ItemGroup>
	<ProjectReference Include="..\PM.WhatIf.Database.Build\PM.WhatIf.Database.Build.csproj">
		<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
	</ProjectReference>
	<ProjectReference Include="..\PM.WhatIf.Services\PM.WhatIf.Services.csproj" />
</ItemGroup>

<ItemGroup>
	<Content Update="Seeding\GanttTasks.json">
		<CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
	</Content>
</ItemGroup>

<Target Name="PublishRunWebpack" AfterTargets="ComputeFilesToPublish">
	<!--As part of publishing, ensure the JS resources are freshly built in production mode-->
	<Exec WorkingDirectory="$(SpaRoot)" Command="npm install" />
	<Exec WorkingDirectory="$(SpaRoot)" Command="npm run build" />

	<!--Include the newly-built files in the publish output-->
	<ItemGroup>
		<DistFiles Include="$(SpaRoot)build\**" />
		<ResolvedFileToPublish Include="@(DistFiles->'%(FullPath)')" Exclude="@(ResolvedFileToPublish)">
			<RelativePath>wwwroot\%(RecursiveDir)%(FileName)%(Extension)</RelativePath>
			<CopyToPublishDirectory>PreserveNewest</CopyToPublishDirectory>
			<ExcludeFromSingleFile>true</ExcludeFromSingleFile>
		</ResolvedFileToPublish>
	</ItemGroup>
</Target>

Why do you need a reference? just publish the dacpac .csproj to the desired output folder in your pipeline.

Hi Erik, i would normally do that. But we do not have control over the clients web app that will host the solution for themselves (Can be many different customers), so we are "integrating" the dacpac file into the web project and then applying it on the startup if certain conditions are met.
We would also like to have this in our development process so we can actually debug that everything is running as expected.
If there is no solution then we will settle for just doing it in a step in the devops pipeline.
But we would like the pipeline to be as close to the dev process as possible.
Could be we should chat at some point, i unfortunately missed the day where you talked with some of the Projectum Devs :)
Br Nicklas

You could add a post build step for local dev?

Yes probably, but it seems wierd since it works with the build part, and not with publish

I managed to fix it ^^
So I added two more properties to anyone that might find this one day :)
Thanks for the help

Please share code rather than screenshot.

There we go :)

<PropertyGroup>
	<TargetFramework>net6.0</TargetFramework>
	<Nullable>disable</Nullable>
	<TypeScriptCompileBlocked>true</TypeScriptCompileBlocked>
	<TypeScriptToolsVersion>Latest</TypeScriptToolsVersion>
	<IsPackable>false</IsPackable>
	<SpaRoot>ClientApp\</SpaRoot>
	<DefaultItemExcludes>$(DefaultItemExcludes);$(SpaRoot)node_modules\**</DefaultItemExcludes>
	<ImplicitUsings>enable</ImplicitUsings>
</PropertyGroup>

<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|AnyCPU'">
	<NoWarn>1701;1702;TS1005;</NoWarn>
	<WarningLevel>4</WarningLevel>
</PropertyGroup>

<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|AnyCPU'">
	<NoWarn>1701;1702;TS1005;</NoWarn>
	<WarningLevel>4</WarningLevel>
</PropertyGroup>

<!--<ItemGroup>
	<Script Include="**" Exclude=“*.esproj;node_modules\**“ />
</ItemGroup>-->

<ItemGroup>
	<PackageReference Include="Microsoft.AspNetCore.SpaServices.Extensions" Version="6.0.1" />
	<PackageReference Include="Microsoft.EntityFrameworkCore.InMemory" Version="6.0.1" />
	<PackageReference Include="Microsoft.Identity.Web" Version="1.22.1" />
	<PackageReference Include="Microsoft.Identity.Web.MicrosoftGraph" Version="1.22.1" />
	<PackageReference Include="Microsoft.SqlServer.DacFx" Version="160.5400.1" />
	<PackageReference Include="Swashbuckle.AspNetCore" Version="6.2.3" />
</ItemGroup>

<ItemGroup>
	<!-- Don't publish the SPA source files, but do show them in the project files list -->
	<Content Remove="$(SpaRoot)**" />
	<None Remove="$(SpaRoot)**" />
	<None Include="$(SpaRoot)**" Exclude="$(SpaRoot)node_modules\**" />
</ItemGroup>

<ItemGroup>
	<Script Include="**" />
	<Script Remove="**.d.ts" />
</ItemGroup>

<ItemGroup>
	<Script Remove="Migration\DacpacService.cs" />
</ItemGroup>

<ItemGroup>
	<Folder Include="Authentication\" />
</ItemGroup>

<ItemGroup>
	<ProjectReference Include="..\PM.WhatIf.Database.Build\PM.WhatIf.Database.Build.csproj">
		<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
		<OutputItemType>Content</OutputItemType>
		<CopyToOutputDirectory>Always</CopyToOutputDirectory>
	</ProjectReference>
	<ProjectReference Include="..\PM.WhatIf.Services\PM.WhatIf.Services.csproj" />
</ItemGroup>

<ItemGroup>
	<Content Update="Seeding\GanttTasks.json">
		<CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
	</Content>
</ItemGroup>

<Target Name="PublishRunWebpack" AfterTargets="ComputeFilesToPublish">
	<!--As part of publishing, ensure the JS resources are freshly built in production mode-->
	<Exec WorkingDirectory="$(SpaRoot)" Command="npm install" />
	<Exec WorkingDirectory="$(SpaRoot)" Command="npm run build" />

	<!--Include the newly-built files in the publish output-->
	<ItemGroup>
		<DistFiles Include="$(SpaRoot)build\**" />
		<ResolvedFileToPublish Include="@(DistFiles->'%(FullPath)')" Exclude="@(ResolvedFileToPublish)">
			<RelativePath>wwwroot\%(RecursiveDir)%(FileName)%(Extension)</RelativePath>
			<CopyToPublishDirectory>PreserveNewest</CopyToPublishDirectory>
			<ExcludeFromSingleFile>true</ExcludeFromSingleFile>
		</ResolvedFileToPublish>
	</ItemGroup>
</Target>


Remove initializers feature gate

Initializers are removed in 1.14 (see https://github.com/kubernetes/kubernetes/pull/72972).
Related issue #14590
I'll add korean + japanese doc update in a separate PR.
/assign @lavalamp @erictune @jessfraz @luxas

/lgtm
/approve

/lgtm
/approve


identify channels in butterfly plot

It would be great if there would be a way to identify a bad channel in the topo butterfly plot. sometimes you just don't know how bad a channel is until you plot it among the others.

You mean click a line in evoked plot and get channel name?

It would be great if there would be a way to identify a bad channel in the topo butterfly plot

for that just don't pick it away don't plot with exclude='bads', and it will be displayed.

@agramfort yes, that.

http://matplotlib.org/1.4.0/users/event_handling.html#object-picking
I might try getting it working this morning, and also making it so that our raw plotting uses this instead. IIRC right now it does something with display ranges, which doesn't seem as elegant.


Update Array, Math, Number, Date, String, RegExp to Foundry VTT 0.7.9

Which class should be updated?
Foundry adds additional functionality to the standard JS classes Array, Math, Number, Date, String, and RegExp. The declarations for this should be updated.
For which version should the class be updated?
Foundry VTT 0.7.9

Resolved by #228

Resolved by #228


Update for jupyterlab3 - switch to pip install (federated)

Updates for jlab3. I took the opportunity to switch this over to the new style "federated" extensions that eliminate the need for a build step. A consequence of this is that a pypi package will need to be released and that the method for loading the vim keymap switched from importing it to calling the ensureVimKeymap function (more details in commit message).
I also applied the recommended tsconfig, eslint, and prettier settings from the upgrade script and then linted in a separate commit.
Closes: https://github.com/axelfahy/jupyterlab-vim/issues/14
Installing now
If anyone is realllllllly wanting this extension for jlab3 prior this being merged then you're in luck @axelfahy has uploaded this PR to pypi and you can install like so
pip install jupyterlab-vim

[x] Add a line to History.md briefly documenting the change.

If this is a release, additionally do the following:

[x] Update the dependencies in package.json
[x] Run jlpm install to update yarn.lock

CI fails but I can confirm that the extension works.

But I think we should wait until the release of the final jupyterlab3 version to merge in order to keep compatibility with jupyterlab2 until the stable release of jupyterlab3.

Totally agree, but I knew how to do this and to avoid the gotcha of not knowing about ensureVimKeymap so I just wanted to make this public sooner rather than later.

Once we decide on the package name, I will publish this to pypi.

Two things here if it ends up with a name like jupyterlab-vim:

@jwkvam should have an input (or ability to say "please don't")
Given that this is a pretty general name would you be open to giving a few other people write access/pypi access so the project is robust against any one person no longer being involved. (i.e. safegaurd against the jlab2 switch nightmare)?

2\. Given that this is a pretty general name would you be open to giving a few other people write access/pypi access so the project is robust against any one person no longer being involved. (i.e. safegaurd against the jlab2 switch nightmare)?

Sure, I can set multiple maintainers for the pip repository.

* Though if jlab-vim makes it's way into core in 3.1 this would be less of an issue.

That would be the best solution IMHO, I hope it will be in core in the 3.1 version.

Two things here if it ends up with a name like jupyterlab-vim:
1. @jwkvam should have an input (or ability to say "please don't")

So let's stick with jupyterlab_vim?

I wonder what was so bad about nodejs 13? weird.

Looking at this more carefully: the build.yml workflow actually does everything that the pull-request action does already so maybe just delete the old pull-request script and rename the build one?

Also, we can set up automated releases to pypi - though the version I know how to use requires you to bump the version manually then you create a release using the github interface. Thoughts on disabling the automated version bumper and switching to script that publishes to both pypi and npm?

Also, we can set up automated releases to pypi - though the version I know how to use requires you to bump the version manually then you create a release using the github interface. Thoughts on disabling the automated version bumper and switching to script that publishes to both pypi and npm?

For Python, I know versioneer, that uses the tag of the commit. But we can bump it manually, there will probably not be many versions.

Actually it seems that the single source of truth for versioning is contained in the package.json. _version.py just reads that file to get the version. So The automated version bump should still work, though it will need to be modified to also push to pypi

though it will need to be modified to also push to pypi

Yes, definitely. In the meantime, I pushed the package from this branch to pypi (https://pypi.org/project/jupyterlab-vim/). An hyphen was set instead of the underscore on the Pypi page, even if the package name has undescore (jupyterlab_vim-0.13.0-py3-none-any.whl). I sent you an invite for the pypi project, so you can push new versions as well.

Yes, definitely. In the meantime, I pushed the package from this branch to pypi (https://pypi.org/project/jupyterlab-vim/)

Nice! I'll edit my first post to reflect this.

I sent you an invite for the pypi project, so you can push new versions as well.

Awesome thanks. Though hopefully I'll never have to make use of that ability.

Hey @axelfahy heads up that jlab3 has been released now. Is there anything more we need to do here?

Hey @axelfahy heads up that jlab3 has been released now. Is there anything more we need to do here?

I don't think so, I will merge. Thank you!

Hey @axelfahy heads up that jlab3 has been released now. Is there anything more we need to do here?

I don't think so, I will merge. Thank you!


DEV - Clean and update dependencies

Thanks to @pavithraes we realised that now runtime dependencies for conda-store(-server) are not up to date nor included in distributed versions of the package.
This is in part due to having bloated environment.yaml files that contain both dev and runtime dependencies (that should only de specified in the pyproject.toml). Since these are both used in local development and CI missing dependencies have gone unnoticed. This PR aims to clean the dependencies and enviroments.
Description

This pull request:

Adds conda-store(-server) runtime dependencies to the corresponding pyproject.toml
Keeps dev only dependencies in environment.yaml
Bumps GH actions and pre-commit versions

Pull request checklist

[x] Did you test this change locally?
[x] Did you update the documentation (if required)?
[ ] Did you add/update relevant tests for this change (if required)?

Additional information

How to test

Will close this as all the additions here have been split across other PRs


coloredFlatButton issue

I tried to edit alignment of the button text to the left, but it's always shown at the center of button

@zichaolim can you post some sample code?


PrettierとESLintを導入する

ESlintの導入
基本こちらの手順ESLintを導入してみました + 公式ドキュメント
設定は以下の通り。
You can also run this command directly using 'npm init @eslint/config'.
✔ How would you like to use ESLint? · style
✔ What type of modules does your project use? · esm
✔ Which framework does your project use? · none
✔ Does your project use TypeScript? · No / Yes
✔ Where does your code run? · browser, node
✔ How would you like to define a style for your project? · guide
✔ Which style guide do you want to follow? · standard
✔ What format do you want your config file to be in? · JavaScript
Checking peerDependencies of eslint-config-standard@latest
The config that you've selected requires the following dependencies:

eslint-config-standard@latest <EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>|| ^16.0.0<EMAIL_ADDRESS>✔ Would you like to install them now? · No / Yes
✔ Which package manager do you want to use? · npm

Prettierを導入
prettier/plugin-rubyのREADMEの手順で導入。

scriptを追加。
package.json：
{
  "scripts": {
    "lint": "prettier --check . && eslint .",
    "fix": "prettier --write . && eslint --fix ."
  }
}

npm run lintまたはnpm run fixで実行できる。


Can't add a guardian when ready to activate

To Reproduce

Login as testingseeds.
Go to Profile > Security > Key Guardians.
Remove all guardians, if any.
Invite 3 guardians (testingsee11, testingseed2, testingseed3).
Login as each guardian and accept the invitation in Profile > Security > Key Guardians.
Switch to testingseeds.
Go to Profile > Security > Key Guardians.
Tap Dismiss to skip guardian activation.
Tap + Add Guardians.

Current behavior

Observe the activation pop-up
Tap Dismiss multiple times and observe the pop-up show up multiple times as well

Expected behavior

User is expected to be able to add another guardian
Alternatively, user might be expected to activate guardians first? (before being able to add another one)

Platform & App Version

Both
2.8.0 (72)

Workaround

Go to Profile > Security > Key Guardians.
Tap Activate Guardians!.
Observe Success! Guardians are now active.
Tap + Add Guardians to invite another guardian.

@buildc0de  next time while creating the bug pls take a screen shot and attach to the issue. One pic its worth 1000 words

@gguijarro-c-chwy I agree, sounds good! 👌 In this case I decided the screenshot was irrelevant as it would just show our guardian activation screen 🤓


Hl-672: Mock authenctications

Description :sparkles:
Mock authentication when NEXT_PUBLIC_MOCK_FLAG is on also on the handler side. Remove mocking from user info endpoint, as now there should always be a real user with request objects when logged in.
Based on python upgrade branch, so that should be merged first

Codecov Report

Merging #1892 (c78b25d) into develop (d1dbd64) will increase coverage by 41.78%.
The diff coverage is 73.33%.

:exclamation: Current head c78b25d differs from pull request most recent head 07b71f0. Consider uploading reports for the commit 07b71f0 to get more accurate results

@@             Coverage Diff              @@
##           develop    #1892       +/-   ##
============================================
+ Coverage    39.57%   81.36%   +41.78%
============================================
  Files          676       82      -594
  Lines        13852     2865    -10987
  Branches      2519        0     -2519
============================================
- Hits          5482     2331     -3151
+ Misses        8033      534     -7499
+ Partials       337        0      -337

Impacted Files
Coverage Δ

backend/shared/shared/azure_adfs/mock_views.py
65.21% <65.21%> (ø)

.../shared/shared/azure_adfs/tests/test_adfs_login.py
100.00% <100.00%> (ø)

backend/shared/shared/azure_adfs/urls.py
100.00% <100.00%> (ø)

frontend/shared/src/components/pages/ErrorPage.tsx

...src/components/stickyActionBar/StickyActionBar.tsx

frontend/shared/src/utils/regex.utils.ts

...components/notificationView/NotificatinsView.sc.ts

frontend/shared/browser-tests/utils/input.utils.ts

...nd/shared/src/__tests__/utils/FakeObjectFactory.ts

frontend/tet/youth/reporter.config.js

... and 588 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Fix: faq/moderation

Added content to faq as per @kapilharesh's request.
Closes #145.

Yes I saw that in each of my PRs there's a bit of a commit mix. I'll take a look and only leave the important ones

Thanks for the contribution @LuckeeDev! Sorry we let it languish for a couple of days there.

No worries @davesteinberg!


[#5370] feat(iceberg):  make IcebergTableOperationDispatcher interface more extendible

What changes were proposed in this pull request?
add IcebergRequestContext in IcebergTableOperationDispatcher
Why are the changes needed?
Fix: #5370
Does this PR introduce any user-facing change?
No
How was this patch tested?
existing tests

Do we plan to make similar changes to IcebergNamespaceOperations and IcebergViewOperations once those classes are switched to use getCatalogWrapper method?

Do we plan to make similar changes to IcebergNamespaceOperations and IcebergViewOperations once those classes are switched to use getCatalogWrapper method?

yes, will do