Issue 39299: Assay result row and sample count metrics

The GPAT assay would be the only one we care about for the Sample Manager case, but would there be any other assay providers outside of the platform and commonAssays ones that we care about for tracking for say Biologics?

I'm not sure of the intent of the metric but my guess is that the result
row count for the flow data should be grouped per well instead of counting
all statistic value rows.  I can help after the holidays.
Kevin
On Tue, Dec 31, 2019, 7:11 AM Cory Nathe<EMAIL_ADDRESS>wrote:

The GPAT assay would be the only one we care about for the Sample Manager
case, but would there be any other assay providers outside of the platform
and commonAssays ones that we care about for tracking for say Biologics?
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/LabKey/commonAssays/pull/107?email_source=notifications&email_token=AA557BJGZZPQADUMUAQJ37TQ3NOLNA5CNFSM4KBRN3C2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEH4KKEY#issuecomment-569943315,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA557BO7467KOLUPHU75ZM3Q3NOLNANCNFSM4KBRN3CQ
.

@labkey-kevink The intent is to get better insight into adoption of assays. I don't think it's critical for the counts to match what you'd see in the schema browser, and I'd like for these queries to be as cheap as possible to run. I'll go ahead and merge this as-is, and resolve the tracking issue to you to consider followup changes on the flow side at your convenience


Wifi not working (AX1650 - AX201)

Hi @zachs78, thank you for your job !
I'm able to boot the installer but I cannot run the installation process because it says that I have to be connected to internet.
I've tried the kext you've recommended (itlwmx) but it doesn't works. I've tried this one too: https://github.com/OpenIntelWireless/itlwm but I still cannot see my wifi working.
My question is, what is you wifi card (I don't know if there are some XPS 9500 with different wifi card version)? Mine is AX1650 (considered as AX201). As you can see here in my comment, it should works: https://github.com/OpenIntelWireless/itlwm/issues/36#issuecomment-682047960.

Hey @BenDevelopment, I can help you out here. itlwm isn't working in the installer because it requires the Heliport application to function properly. You can only install Heliport once you've got a working MacOS install. If you're making your installer from a Windows machine, you'll only be able to use the recovery installer and you'll need internet for that as it installs the OS from Apple's servers. Here are a few things that you can try:

Create the installer with a Mac or with a Windows machine running a Virtual Machine of Mac using the following guide: https://dortania.github.io/OpenCore-Install-Guide/installer-guide/mac-install.html

(as far as I know installers made with Windows can only create recovery media installers, whereas installers made with MacOS have the full OS image included and therefore do not require internet connections)

This one is a little more experimental, and I'm not sure if it'll work. You're going to need an Android phone or tablet for this.

Go to my repo: https://github.com/robotblox/XPS-15-9500-Catalina-10.15.6 and use "HoRNDIS.kext" from my kext folder. I extracted the kext file from the official release a little while back to make it easier to use. What HoRNDIS basically does is use your Android device as an internet tether. Boot into the MacOS installer and plug in your device to your laptop. After that, you should get internet connectivity. The Dortania guide mentions it but I didn't have my USB ports working when I was in the installer, (which was fixed by zachs78, so it should be fine) so I didn't get a chance to test it out.
Let me know if you figure it out!

Thank you @robotblox, I can now pass this step. I've another issue with the next step, I'll make a new post.


--message-format option missing from cargo install

I want to build, install and launch debugging from the install directory in VSCode.
I have create the following launch configuration:
        "configurations": [
        {
            "type": "lldb",
            "request": "launch",
            "name": "Install & Debug 'HelloWorld'",
            "cargo": {
                "args": [
                    "install",
                    "--path",
                    ".",
                    "--bin=HelloWorld",
                    "--root",
                    "./install"
                ],
                "filter": {
                    "name": "HelloWorld",
                    "kind": "bin"
                }
            },
            "args": [],
            "cwd": "${workspaceFolder}"
        },

which causes the following error:

Running cargo install --path . --bin=HelloWorld --root ./install --message-format=json...
error: Found argument '--message-format' which wasn't expected, or isn't valid in this context

Am I holding it wrong or is this a limitation of the system?
Well it looks like I'm holding it wrong. Could we have this --message-format=json option in the install context to enable install&debug workflow?

I have transferred this to the cargo repo since it looks like a cargo issue.
Indeed, --message-format seems to be missing from cargo install.  It should be a relatively easy thing to add.

@rustbot claim
I will add it.

That was FTL fast! Thanx!


PATCH on metadata should retain old values

Right now, this overwrites all the metadata fields, which is not what you would expect to happen, and is also really inconvenient for updating records.

It may be simpler to implement this in the CLI client.


Compatibility of pair syntax with DataFrames

It was noted on Discourse that the pair syntax for mappings is close to the DataFrames but  note quite compatible. I thought it would be nice to have a place to summarize the issue and document the decision (hope you don't mind!).
Single rows vs columns
The main issue is that AlgebraOfGraphics mappings work on single rows instead of whole columns. For example this
:bill_length_mm => (t -> t + 10) => "bill length (cm)"

must be adapted for DataFrames to:
:bill_length_mm => (t -> t .+ 10) => "bill length (cm)"

or
:bill_length_mm => ByRow(t -> t + 10) => "bill length (cm)"

Advantages of single rows include:

Simpler for the user in most cases.
Less error prone especially

with grouped data (should a column operation apply to each group or the whole dataset?)
when several datasets are used

Downsides include

No support for operations that require the whole column (for example z-score standardisation)
Risk of confusion with DataFrames API
Transformations cannot be reused between DataFrames and AlgebraOfGraphics

Tuples vs arrays
Another point I noticed in the machine learning tutorial section: AlgebraOfGraphics allows giving multiple input variables as a tuple:
error_rate = (:species, :predicted_species) => !isequal => "error rate"

In DataFrames only arrays are allowed:
error_rate = [:species, :predicted_species] => ByRow(!isequal) => "error rate"

I personally like arrays here as they stand out more in the middle of function calls, but that's subjective of course.

Btw, I'm adding the documentation part of your post in the docs, as part of #182, because I think it's very informative. The "comparison with DataFrames" bit should probably go in a FAQ section in the future.

Update: actually the "internal style guide" to use Tuple for passing many arguments to an operation may well become enforced, because I plan to support pregrouped data, as in #79, and also supporting an array for "many-to-one" operations would create too much confusion, as it becomes less clear whether [a, b, c] => f means map(f, a, b, c) or [map(f, a), map(f, b), map(f, c)].


add rwkv world tokenizer

prepare for https://github.com/mlc-ai/mlc-llm/pull/848

After latest commit, unittest can also run success.

Thanks @BBuf

@BBuf @Hzfengsy This commit introduces a regression on windows build and blocks our nightly package rebuild. Please see the detailed logs below:
D:\a\package\package>cd mlc-llm

D:\a\package\package\mlc-llm>rd /s /q build
The system cannot find the file specified.

D:\a\package\package\mlc-llm>mkdir build

D:\a\package\package\mlc-llm>cd build

D:\a\package\package\mlc-llm\build>cmake -A x64 -Thost=x64       -G "Visual Studio 17 2022"       -DUSE_VULKAN=ON       ..
-- The C compiler identification is MSVC 1[9](https://github.com/mlc-ai/package/actions/runs/6069714174/job/16464517741#step:10:10).36.32538.0
-- The CXX compiler identification is MSVC 19.36.32538.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Enterprise/VC/Tools/MSVC/14.36.32532/bin/HostX64/x64/cl.exe - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: C:/Program Files/Microsoft Visual Studio/2022/Enterprise/VC/Tools/MSVC/14.36.32532/bin/HostX64/x64/cl.exe - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Performing Test SUPPORT_CXX17
-- Performing Test SUPPORT_CXX17 - Success
-- Setting default build type to RelWithDebInfo
-- Hide private symbols
-- TVM_HOME: 3rdparty/tvm
-- Found the path to ccache, enabling ccache
-- VTA build is skipped in Windows..
-- Vulkan_INCLUDE_DIRS=C:/Miniconda/envs/tlcpack-build/Library/includeC:/Miniconda/envs/tlcpack-build/Library/include/spirv-toolsC:/Miniconda/envs/tlcpack-build/Library/include/spirv/unified1C:/Miniconda/envs/tlcpack-build/Library/include/spirv/unified1
-- Vulkan_LIBRARY=C:/Miniconda/envs/tlcpack-build/Library/lib/vulkan-1.lib
-- Vulkan_SPIRV_TOOLS_LIBRARY=C:/Miniconda/envs/tlcpack-build/Library/lib/SPIRV-Tools.lib
-- Build with Vulkan support
-- Build with contrib.random
-- Build with contrib.sort
-- Build with contrib.hybriddump
-- Git found: C:/Miniconda/envs/tlcpack-build/Library/bin/git.exe
-- Found TVM_GIT_COMMIT_HASH=b0d1c21f329e6aed8fd639c530c29acc3b1f9305
-- Found TVM_GIT_COMMIT_TIME=2023-08-31 15:57:11 -0400
-- Building with TVM Map...
-- Build with thread support...
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - not found
-- Found Threads: TRUE
-- Performing Test FILE_PREFIX_MAP_SUPPORTED
-- Performing Test FILE_PREFIX_MAP_SUPPORTED - Failed
-- system-nameWindows
MSBuild version 17.7.2+d6990bcfa for .NET Framework

  1>Checking Build System
  1>Creating directories for 'msgpack-populate'
  Performing download step (git clone) for 'msgpack-populate'
  Cloning into 'msgpack-src'...
  HEAD is now at 8c602e85 Merge pull request #[10](https://github.com/mlc-ai/package/actions/runs/6069714174/job/16464517741#step:10:11)83 from redboltz/update_610
  CMake Error at msgpack-subbuild/msgpack-populate-prefix/tmp/msgpack-populate-gitclone.cmake:62 (message):
    Failed to update submodules in:
-- Configuring incomplete, errors occurred!
    'D:/a/package/package/mlc-llm/build/_deps/msgpack-src'

C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(249,5): error MSB8066: Custom build for 'D:\a\package\package\mlc-llm\build\_deps\msgpack-subbuild\CMakeFiles\dfa5057374fb3dfcddc46b7b964a6e83\msgpack-populate-download.rule;D:\a\package\package\mlc-llm\build\_deps\msgpack-subbuild\CMakeFiles\dfa5057374fb3dfcddc46b7b964a6e83\msgpack-populate-update.rule;D:\a\package\package\mlc-llm\build\_deps\msgpack-subbuild\CMakeFiles\dfa5057374fb3dfcddc46b7b964a6e83\msgpack-populate-patch.rule;D:\a\package\package\mlc-llm\build\_deps\msgpack-subbuild\CMakeFiles\dfa5057374fb3dfcddc46b7b964a6e83\msgpack-populate-configure.rule;D:\a\package\package\mlc-llm\build\_deps\msgpack-subbuild\CMakeFiles\dfa5057374fb3dfcddc46b7b964a6e83\msgpack-populate-build.rule;D:\a\package\package\mlc-llm\build\_deps\msgpack-subbuild\CMakeFiles\dfa5057374fb3dfcddc46b7b964a6e83\msgpack-populate-install.rule;D:\a\package\package\mlc-llm\build\_deps\msgpack-subbuild\CMakeFiles\dfa5057374fb3dfcddc46b7b964a6e83\msgpack-populate-test.rule;D:\a\package\package\mlc-llm\build\_deps\msgpack-subbuild\CMakeFiles\df644a9fff8f1cab49663ee66d0ee69a\msgpack-populate-complete.rule;D:\a\package\package\mlc-llm\build\_deps\msgpack-subbuild\CMakeFiles\b[12](https://github.com/mlc-ai/package/actions/runs/6069714174/job/16464517741#step:10:13)dc4ee056b4292e5c2bb36792642c2\msgpack-populate.rule;D:\a\package\package\mlc-llm\build\_deps\msgpack-subbuild\CMakeLists.txt' exited with code 1. [D:\a\package\package\mlc-llm\build\_deps\msgpack-subbuild\msgpack-populate.vcxproj]

CMake Error at C:/Miniconda/envs/tlcpack-build/Library/share/cmake-3.27/Modules/FetchContent.cmake:[16](https://github.com/mlc-ai/package/actions/runs/6069714174/job/16464517741#step:10:17)62 (message):
  Build step for msgpack failed: 1
Call Stack (most recent call first):
  C:/Miniconda/envs/tlcpack-build/Library/share/cmake-3.27/Modules/FetchContent.cmake:1802:EVAL:2 (__FetchContent_directPopulate)
  C:/Miniconda/envs/tlcpack-build/Library/share/cmake-3.27/Modules/FetchContent.cmake:1802 (cmake_language)
  C:/Miniconda/envs/tlcpack-build/Library/share/cmake-3.27/Modules/FetchContent.cmake:2016 (FetchContent_Populate)
  3rdparty/tokenizers-cpp/CMakeLists.txt:86 (FetchContent_MakeAvailable)

D:\a\package\package\mlc-llm\build>cmake --build . --parallel 3 --config Release -- /m
MSBuild version [17](https://github.com/mlc-ai/package/actions/runs/6069714174/job/16464517741#step:10:18).7.2+d[69](https://github.com/mlc-ai/package/actions/runs/6069714174/job/16464517741#step:10:70)90bcfa for .NET Framework
MSBUILD : error MSB1009: Project file does not exist.
Switch: ALL_BUILD.vcxproj

D:\a\package\package\mlc-llm\build>cd ..\..

@BBuf would be great if we can followup on this. In the meantime, we can pin tokenizer-cpp to an earlier version if needed for now. Indeed submodule would be better

I will change it to the submodule approach as soon as possible.

 Please see the detailed logs below:
D:\a\package\package>cd mlc-llm

D:\a\package\package\mlc-llm>rd /s /q build
The system cannot find the file specified.

D:\a\package\package\mlc-llm>mkdir build

D:\a\package\package\mlc-llm>cd build

D:\a\package\package\mlc-llm\build>cmake -A x64 -Thost=x64       -G "Visual Studio 17 2022"       -DUSE_VULKAN=ON       ..
-- The C compiler identification is MSVC 1[9](https://github.com/mlc-ai/package/actions/runs/6069714174/job/16464517741#step:10:10).36.32538.0
-- The CXX compiler identification is MSVC 19.36.32538.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Enterprise/VC/Tools/MSVC/14.36.32532/bin/HostX64/x64/cl.exe - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: C:/Program Files/Microsoft Visual Studio/2022/Enterprise/VC/Tools/MSVC/14.36.32532/bin/HostX64/x64/cl.exe - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Performing Test SUPPORT_CXX17
-- Performing Test SUPPORT_CXX17 - Success
-- Setting default build type to RelWithDebInfo
-- Hide private symbols
-- TVM_HOME: 3rdparty/tvm
-- Found the path to ccache, enabling ccache
-- VTA build is skipped in Windows..
-- Vulkan_INCLUDE_DIRS=C:/Miniconda/envs/tlcpack-build/Library/includeC:/Miniconda/envs/tlcpack-build/Library/include/spirv-toolsC:/Miniconda/envs/tlcpack-build/Library/include/spirv/unified1C:/Miniconda/envs/tlcpack-build/Library/include/spirv/unified1
-- Vulkan_LIBRARY=C:/Miniconda/envs/tlcpack-build/Library/lib/vulkan-1.lib
-- Vulkan_SPIRV_TOOLS_LIBRARY=C:/Miniconda/envs/tlcpack-build/Library/lib/SPIRV-Tools.lib
-- Build with Vulkan support
-- Build with contrib.random
-- Build with contrib.sort
-- Build with contrib.hybriddump
-- Git found: C:/Miniconda/envs/tlcpack-build/Library/bin/git.exe
-- Found TVM_GIT_COMMIT_HASH=b0d1c21f329e6aed8fd639c530c29acc3b1f9305
-- Found TVM_GIT_COMMIT_TIME=2023-08-31 15:57:11 -0400
-- Building with TVM Map...
-- Build with thread support...
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - not found
-- Found Threads: TRUE
-- Performing Test FILE_PREFIX_MAP_SUPPORTED
-- Performing Test FILE_PREFIX_MAP_SUPPORTED - Failed
-- system-nameWindows
MSBuild version 17.7.2+d6990bcfa for .NET Framework

  1>Checking Build System
  1>Creating directories for 'msgpack-populate'
  Performing download step (git clone) for 'msgpack-populate'
  Cloning into 'msgpack-src'...
  HEAD is now at 8c602e85 Merge pull request #[10](https://github.com/mlc-ai/package/actions/runs/6069714174/job/16464517741#step:10:11)83 from redboltz/update_610
  CMake Error at msgpack-subbuild/msgpack-populate-prefix/tmp/msgpack-populate-gitclone.cmake:62 (message):
    Failed to update submodules in:
-- Configuring incomplete, errors occurred!
    'D:/a/package/package/mlc-llm/build/_deps/msgpack-src'

C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(249,5): error MSB8066: Custom build for 'D:\a\package\package\mlc-llm\build\_deps\msgpack-subbuild\CMakeFiles\dfa5057374fb3dfcddc46b7b964a6e83\msgpack-populate-download.rule;D:\a\package\package\mlc-llm\build\_deps\msgpack-subbuild\CMakeFiles\dfa5057374fb3dfcddc46b7b964a6e83\msgpack-populate-update.rule;D:\a\package\package\mlc-llm\build\_deps\msgpack-subbuild\CMakeFiles\dfa5057374fb3dfcddc46b7b964a6e83\msgpack-populate-patch.rule;D:\a\package\package\mlc-llm\build\_deps\msgpack-subbuild\CMakeFiles\dfa5057374fb3dfcddc46b7b964a6e83\msgpack-populate-configure.rule;D:\a\package\package\mlc-llm\build\_deps\msgpack-subbuild\CMakeFiles\dfa5057374fb3dfcddc46b7b964a6e83\msgpack-populate-build.rule;D:\a\package\package\mlc-llm\build\_deps\msgpack-subbuild\CMakeFiles\dfa5057374fb3dfcddc46b7b964a6e83\msgpack-populate-install.rule;D:\a\package\package\mlc-llm\build\_deps\msgpack-subbuild\CMakeFiles\dfa5057374fb3dfcddc46b7b964a6e83\msgpack-populate-test.rule;D:\a\package\package\mlc-llm\build\_deps\msgpack-subbuild\CMakeFiles\df644a9fff8f1cab49663ee66d0ee69a\msgpack-populate-complete.rule;D:\a\package\package\mlc-llm\build\_deps\msgpack-subbuild\CMakeFiles\b[12](https://github.com/mlc-ai/package/actions/runs/6069714174/job/16464517741#step:10:13)dc4ee056b4292e5c2bb36792642c2\msgpack-populate.rule;D:\a\package\package\mlc-llm\build\_deps\msgpack-subbuild\CMakeLists.txt' exited with code 1. [D:\a\package\package\mlc-llm\build\_deps\msgpack-subbuild\msgpack-populate.vcxproj]

CMake Error at C:/Miniconda/envs/tlcpack-build/Library/share/cmake-3.27/Modules/FetchContent.cmake:[16](https://github.com/mlc-ai/package/actions/runs/6069714174/job/16464517741#step:10:17)62 (message):
  Build step for msgpack failed: 1
Call Stack (most recent call first):
  C:/Miniconda/envs/tlcpack-build/Library/share/cmake-3.27/Modules/FetchContent.cmake:1802:EVAL:2 (__FetchContent_directPopulate)
  C:/Miniconda/envs/tlcpack-build/Library/share/cmake-3.27/Modules/FetchContent.cmake:1802 (cmake_language)
  C:/Miniconda/envs/tlcpack-build/Library/share/cmake-3.27/Modules/FetchContent.cmake:2016 (FetchContent_Populate)
  3rdparty/tokenizers-cpp/CMakeLists.txt:86 (FetchContent_MakeAvailable)

D:\a\package\package\mlc-llm\build>cmake --build . --parallel 3 --config Release -- /m
MSBuild version [17](https://github.com/mlc-ai/package/actions/runs/6069714174/job/16464517741#step:10:18).7.2+d[69](https://github.com/mlc-ai/package/actions/runs/6069714174/job/16464517741#step:10:70)90bcfa for .NET Framework
MSBUILD : error MSB1009: Project file does not exist.
Switch: ALL_BUILD.vcxproj

D:\a\package\package\mlc-llm\build>cd ..\..

Link to the nightly run: https://github.com/mlc-ai/package/actions/runs/6069714174/job/16464517741
I do not have any clear idea how to get it fixed as I don't have a windows machine, but usually we would prefer submodule to FetchContent for network stability concerns.

https://github.com/mlc-ai/tokenizers-cpp/pull/15


Display github user image instead of github username in author and assignee inside IssueTile

Instead of displaying Github usernames, it would be better to display the GitHub user image inside a circle, like in AddProjectPage.

@otech47 @sofiaromorales Can we add the avatar URL to the contributor table? That's one option I was thinking about of how to do this Issue. Do you guys think of a better solution?


Print preview add watermark

Hi
my problem:

How to do Print preview add watermark
Please give my a demo
thanks very much!

That's not a use-case that this library is intended for; note https://github.com/mozilla/pdf.js#pdfjs-

PDF.js is a Portable Document Format (PDF) viewer that is built with HTML5.

For future reference: When opening an issue, please provide all of the information requested in https://github.com/mozilla/pdf.js/blob/master/.github/ISSUE_TEMPLATE.md


Allow passing defines such as -- -DFOO=bar

Checklist

[ ] npm install && npm test passes
[ ] tests are included
[ ] documentation is changed or added
[ ] commit message follows commit guidelines

Description of change

My small change in node-pre-gyp hit a wall because node-gyp configure .. -- -DFOO=bar results in creating an msbuild option /t:-DFOO=bar, thank you very much.
https://github.com/mapbox/node-pre-gyp/pull/416

Sorry I do not know how to run tests.  I see some added in the change that exposed my issue.
https://github.com/nodejs/node-gyp/pull/1164

Hello @ilatypov and thank you for the contribution.
Could you write a test for this change? An example can be:
https://github.com/nodejs/node-gyp/blob/aebdd7a710862c13592a9d2c8a28aadf661b0542/test/test-addon.js#L34-L48
(BTW: you run the test suite with a simple npm install; npm test)

Hmm, this is an issue that does not only affect the the configure options but also overloading of properties.
/p:FOO=bar

becomes
/t:/p:FOO=bar

This fix wouldn't apply in all cases :/

@ilatypov would still like to pursue this? if so, please rebase to the current master and let's see if we can figure out a test for it.

Too many conflicts.


Proposal: Support Reverse Proxy in the client

Today in the client you can use -H with unix://<file>, tcp://<ip:port> and fd://<num>
I'm currently hosting my docker daemon behind a Reverse Proxy (nginx).
I wonder if the docker client should support
-H tcp://<ip:port></path> or -H http://<ip></path>
What do you guys think ?

This is not supporting a reverse proxy, its for supporting a base URL right?

@crosbymichael yes, sorry if it's confusing

Makes sense for me. We just need little modify parsing and router creation.

Can you clarify the use case here?

/containers/redis
vs
/mydockerapi/containers/redis

@huslage My docker daemon is behind a reverse proxy (nginx)
I want to do docker -H tcp://<IP_ADDRESS>/swarm info and go through my reverse proxy hosted at <IP_ADDRESS>.
@crosbymichael @LK4D4 are you more in favor of changing tcp:// or using http://
I think tcp makes more sense.

@vieux Yes, I don't want new proto to handle.

@LK4D4 cool, I'll open a PR soon.

It might make sense to support http and https as proto too. The api talks http anyways.

Today we differentiate proto and scheme, the scheme is always http or https (if a tlsconfig is given)
and then we use this scheme on any proto (unix/tcp)

There was another issue on this : https://github.com/docker/docker/issues/13871. I submitted a PR that is related : https://github.com/docker/docker/pull/14285. Let me know what you think.


22639 - Update Certify Section Wording

Issue #: /bcgov/entity#22639
Description of changes:

This PR is for Edit UI (Create UI and Filing UI are in progress)
Updated the wording in Certify Section

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the bcrs-entities-create-ui license (Apache 2.0).

/gcbrun

Temporary Url for review: https://business-edit-dev--pr-598-f03y4ktw.web.app

/gcbrun

Temporary Url for review: https://business-edit-dev--pr-598-f03y4ktw.web.app


[Snyk] Upgrade io.grpc:grpc-protobuf from 1.64.0 to 1.65.1

Snyk has created this PR to upgrade io.grpc:grpc-protobuf from 1.64.0 to 1.65.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 4 versions ahead of your current version.

The recommended version was released on 25 days ago.

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:

🧐 View latest project report
📜 Customise PR templates
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Already on 1.68.1


Configure Azure Pipelines

This pipeline configuration builds the application and produces a build for the Release configuration.

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


suggestion: Entity:restrict method

The Problem:
When using components for status effects, it makes sense to remove the components related to actions which that status prevents. One problem that arises with this is with two status effects that have an action that they both restrict.
For example, you have a 'stunned' status effect which prevents both movement and attacking:
function StunSystem:stun(entity, duration)
    entity:give('stunned', duration)
    entity:remove('canattack')
    entity:remove('canmove')
end

function StunSystem:end_stun(entity)
    entity:remove('stunned')
    entity:give('canattack')
    entity:give('canmove')
end

and a 'rooted' status, which only prevents movement
function RootSystem:root(entity, duration)
   entity:give('rooted', duration)
   entity:remove('canmove')
end

function RootSystem:end_root(entity, duration)
   entity:remove('rooted')
   entity:give('canmove')
end

The problem that arises is that if an entity is rooted for a long time, while also being stunned for a short time they will wind up moving as soon as their stun ends even if they are still supposedly rooted. One very poor solution would be to have every status effect check all overlapping ones and only give the components when appropriate - obviously not a favorable approach. Another would be to have the actions (MovementSystem, AttackSystem) check what status effects are active instead of including 'canmove' and 'canattack' in the pool. Besides being inefficient, that approach also seems to me to be poor separation of concerns. The effects of a particular status effect should be contained within the system that implements it.
The proposed solution: : Entity:restrict(component) and Entity:unrestrict(component)
Entity:restrict will record that something is preventing the passed component from being active and will 'hide' it so that the entity is excluded from pools containing that, and it maintains a counter of the number of times the component is restricted.
`Entity.unrestrict' will decrement the aforementioned counter, and if it reaches 0 (indicating that nothing is now restricting the component) it will un-hide the the component in question.
Another advantage of this is that it allows one to temporarily remove parameterized components and add them with the same values as before without caching them (as :remove would handle that).
Let me know what you think. I'll be doing something like this for a project anyway so I can easily make a PR afterward with my modification.

I think your issue can be fixed with Component Negation (see #32) which would allow you to specify that you only want entities that canmove but are not stunned nor rooted so you could specify your filters such as:
local YourSystem = Concord.system({
   movable = { "canmove", "!stunned", "!rooted" },
   attacker = { "canattack", "!stunned" }
})

And now you don't need to remove canattack and/or canmove whenever you give these status effects.
This aligns with your second proposed solution:

Another would be to have the actions (MovementSystem, AttackSystem) check what status effects are active instead of including 'canmove' and 'canattack' in the pool. Besides being inefficient, that approach also seems to me to be poor separation of concerns. The effects of a particular status effect should be contained within the system that implements it.

Don't worry this is not inefficient, component negation is just as fast and simple any other Filter check. You also mention that it's a poor separation of concepts, but to be fair these components are flag that tell your system whether this Entity can perform the action the System takes care of.
All in all, it's a little more redundant than adding and removing a single canmove flag, but it's a great solution for your specific use case.

Your proposed solution sounds useful but it's still added complexity to Concord (which tries to be minimal but feature complete).
You also need to take into account you will need to have a separate location for restricted components, and possibly needing an isRestricted check. Then again it's doable, and if you want to make a PR so we can better evaluate how useful it is and what problems may arise later, I'll definitely appreciate it.

Thanks for taking the time to reply!
Ah, I didn't know about component negation! That's a much better solution. I think you're right as well that as long as it's in the pool declaration the concern is exactly where it should be. This was really helpful, thanks!

I don't have other usecases in mind for this so as you say it wouldn't be worth the complexity. As far as I'm concerned this issue can be closed.

Great to hear!
I'm glad that this can be solved with "Component Negation" since I feel it's the ideal use case for this feature.
I will keep this in the back of my mind just in case it's needed at some point 💖
Thank you very much for your proposal, really appreciated.


Doors

Add an INT to each script with a return at the top of the script if it is not intended to fire.
This could also be a way to integrate the intelligent doors script.
At same time create blank scripts for events that don't presently have one.

if (!GetLocalInt(OBJECT_SELF, "DOOR_OPEN")) return;


Cart - Academic discount

Academic discount is missing from the product description text in the cart. This seems to be removed with the latest update. @nathakits please fix.

PR https://github.com/pupil-labs/pupil-labs-website/pull/311

Resolved; closing. 😸


Add docs for if-diff to if.greensoftware.foundation

Why: In relation to #637
What: Add documentation of this new feature that's implemented in #637
Scope of work:

[ ] feature is documented in a README in the if repository
[ ] feature is documented on if.greensoftware.foundation in a dedicated page at https://if.greensoftware.foundation/reference/cli/if-diff

@jmcook1186 Please check the documentation issue here, if this is what it's expected as part o the scope

blocked pending merge of if-diff feature


Icon Appears While Not Logged In

The icon appears and seems to work fine when logged in, however, it is also appearing while not logged in (I didn't try to see if it actually worked then, but I did bring up the warning dialog). I'm not sure if that is what is expected from your plugin, but it feels like either a bad idea or a bug.

Hi, i will take a look to this, I have don't seen this bug on my ocotoprint because I'm auto loged on.
I correct this bug as soon as possible

If it makes a difference, I'm running 1.3.5rc2. I hadn't tried this plugin before this version, so I don't know if something broke or not.

here it appears when not logged in too... I haven't tried to press it yet beause I'm in the middle of a print :-)
I'll try later to see if it really stops even when logged off.

Tested. It shows the confirmation dialog, but even after confirming, the printer is not "killed" when not logged in

Ok thanks for testing, anyway I will try to fix the icon when I have time.
Thanks you guys! ;)

Bug Fixed ! Thanks for reporting ;)


Half hourly reporting

Is it possible to have half hourly / hourly values displayed as half hourly values are available in the api?
Not sure if this possible, but I currently only get the accumulated value at 4am each day.
Cheers

Hi there, sorry for the late response - Work life is busy at the moment.
When you say display, do you mean in the energy dashboard or separate sensors?
For the energy dashboard, no as HA currently only officially supports "live" data which is why we have the accumulations for the previous day. There is an issue which has uncovered a way of potentially porting stats historically, but there is currently no documentation (which makes me nervous about how stable it is) and I haven't had the time to investigate.
In terms if separate sensors, I'm not sure how useful this would be.
I can however look at exposing the breakdowns on the accumlation sensor as an attribute. That way you can create template sensors and then do what you need with the data?

No need to apologize.
Sorry, yes I meant the breakdown on the energy dashboard.
The officially supporting only live data makes sense as to why its not possible yet. I was curious as I could see the data from Octopus being in 30 minute intervals. If HA does support / document importing historic data, that would be nice to throw the previous days break down in.

Yeah I can understand why your output is causing confusion.

Octopus publish your daily usage in 30 minute intervals one day in arrears, as a bulk upload.

Ideally this is what Octopus would do, however in testing and with previously raised issues, this is not what occurs in practice. There are days when Octopus part publishes the previous days worth of data, and then publishes the rest later on in the day. This is what looks like is happening in your instance, which results in the dashboard summing the partial total and actual total. I'm not sure why one of your days is going negative when the value is clearly positive. This might be a bug with HA.
I tried to combat the partial updates by waiting for there to be 48 entries available before updating the sensor. Unfortunately, some other users ended up never seeing their sensors update because there was missing data.
I'll add something to the list to see about making the entry threshold configurable before the sensors are updated. This way, users can reduce this threshold in instances where their meter might be missing half hour blocks.

Cheers, I think I’ve got it now. I’d say that with these limitations considered you’ve implemented this in the best way. Truthfully though until retrospective data loads are possible there will always be issues esp. with such an inconsistent 3rd party.
I had a look and there are a number of CRs logged to add this functionality to load historical data.  None of them seem to be getting off the ground. I’m guessing that something in the ability to retrospectively modify sensor data must break something architecturally. Would definitely cause issues for any feeds out of HA (e.g. to Influx).
There are some cowboy suggestions for doing your own SQL updates to the HA database but am sure you’ve seen these and discounted the approach as being too risky. E.g.
https://community.home-assistant.io/t/remove-faulty-readings-from-energy-dashboard-history/335555
Will put my mind to it and let you know if I can think of another approach.

Closing this issue until a better solution from home assistant is possible.


Parsing error due to forced integer

DruidEmittedData.Value takes in int type, while some druid metrics sends out float values

Thanks for contribution


Leverage EvolutionSynthesis in the EvolvedOperatorAnsatz

Summary
Closes #9516 and supersedes #7275.
Use the evolution synthesis module along with the PauliEvolutionGate and HamiltonianGate in the EvolvedOperatorAnsatz over qiskit.opflow components.
Details and comments
Also moves the HamiltonianGate, which does matrix-based state-evolution, into the circuit library to be in the same place as the PauliEvolutionGate.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

164 of 173 (94.8%)  changed or added relevant lines in 8 files are covered.
32 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.02%) to 85.29%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit/circuit/library/evolved_operator_ansatz.py
32
33
96.97%

qiskit/circuit/library/evolution/pauli_evolution.py
54
56
96.43%

qiskit/circuit/library/evolution/hamiltonian_gate.py
58
64
90.63%

Files with Coverage Reduction
New Missed Lines
%

qiskit/dagcircuit/dagdepnode.py
11
76.47%

qiskit/transpiler/target.py
21
94.28%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
67295

Relevant Lines:
78901

💛  - Coveralls

I removed the changes to HamiltonianGate from this PR and included Max' comments in another branch we can use to move it in a different PR 🙂


chore: remove PUT container workaraound

Removed workaround code that was required to create containers in ESS.
This got fixed in ESS and is thus no longer needed.

Can you see if you can also enable the browser e2e tests for NSS by adding in - "NSS" to here: https://github.com/inrupt/solid-client-js/blob/main/.github/workflows/e2e-browser.yml#L62

Had to rebase and force push to update the branch as another PR had been merged in the meantime.


how long Transfer supports ?

Sorry, but I have no idea what this request refers to. Can you describe your problem in more detail?


Reconnect on settings apply only when custom id is modified

Reconnect to the Discord client only when the customApplicationId setting is modified. Reconnecting to the Discord client is otherwise unnecessary.

This isn't a higher priority now that #18 has been implemented and #25 has been closed.


exp sharing updates - Studio docs

This contains changes to the Studio docs, related to dvc exp push.

Closing this one as well as Heroku didn't stop retrying failed deployment https://github.com/iterative/dvc.org/pull/4485. Please reopen once fixed.


Lens App is not displaying Requests and Limits for pods

Describe the bug
Lens App is not Displaying Requests and Limits for my pods.
To Reproduce
Steps to reproduce the behavior:

Opne lens
got to the pods
get the pod details

Expected behavior
I remember in the past being able to see Request and Limits as Lines in the pod graphs.
Screenshots

Environment (please complete the following information):

Lens Version:
OS:OSX Arm Lens: 2024.9.300059-latest
Installation method from the website

Logs:
When you run the application executable from command line you will see some logging output. Please paste them here:
➜  ~ DEBUG=TRUE /Applications/Lens.app/Contents/MacOS/Lens >> output
[15862:1011/001431.289494:ERROR:platform_util_mac.mm(283)] Unable to set login item: The operation couldn’t be completed. Operation not permitted
[15862:1011/001433.808691:ERROR:cert_verify_proc_builtin.cc(1051)] CertVerifyProcBuiltin for <IP_ADDRESS> failed:
----- Certificate i=0 (O=Lens,CN=Lens Certificate Authority) -----
ERROR: No matching issuer found

[winston] Attempt to write logs with no transports, which can increase memory usage: {"level":"info","message":"[LENS-USER-STORE]: LOADING ..."}
Error occurred in handler for 'get-demo-cluster-config-channel': Error: You are not allowed to access the demo-cluster config.
    at /Applications/Lens.app/Contents/Resources/app.asar/node_modules/@lensapp/lens-platform-client-main/dist/index.js:188:13
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async WebContents.<anonymous> (node:electron/js2c/browser_init:2:83654)
[winston] Attempt to write logs with no transports, which can increase memory usage: {"level":"info","message":"[LENS-USER-STORE]: LOADING ..."}
(node:15862) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 11 abort listeners added to [AbortSignal]. MaxListeners is 10. Use events.setMaxListeners() to increase limit
(Use `Lens --trace-warnings ...` to show where the warning was created)
(node:15862) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 11 abort listeners added to [AbortSignal]. MaxListeners is 10. Use events.setMaxListeners() to increase limit

Kubeconfig:
Quite often the problems are caused by malformed kubeconfig which the application tries to load. Please share your kubeconfig, remember to remove any secret and sensitive information.
your kubeconfig here

Additional context
I am using kube-promehteus-stack + promehteus-adapter instead of metrics server.
I am able to see everything normally in k9s. (via metrics server and prom-adapter)
To be able to visualize metrics I am using helm provider and as shown in the picture monitoring/promeheus-operated:9090
I was following also the troubleshooting guide for custom-Prometheus I don't think this is the problem.
I don't have issues between API and Nodes. I am using kubernetes 1.30 and VPC-CNI Standard networking.

output.log

Thank you @tkcontiant for your feedback and the detailed description of your issue. I have already forwarded your problem to the relevant team internally, and I will get back to you here as soon as there are any updates. Thank you!


Bump: 0.3.0-next -> 0.4.0

Proposed changes
This PR node-red-contrib-letsfiware-NGSI version from 0.3.0-next -> 0.4.0.
Types of changes
What types of changes does your code introduce to the project: Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Update only documentation, not any source code.
[ ] Maintain repository

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of
them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before
merging your code.

[X] I have read the CONTRIBUTING doc
[ ] I have signed the CLA
[X] I have updated the change log (CHANGELOG.md)
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Further comments
N/A

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
529

Relevant Lines:
529

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
529

Relevant Lines:
529

💛  - Coveralls


feat: add option to use S3 for reports and results

Demo: https://cyborg-s3.shelex.dev/
Token: 12345
Added

split data file into separate fs for storage and pw for generating reports
common interface that is required to work with storage and apply to fs
added error handling for api routes
added loading for results/reports table as it may take some time to fetch with external storage option
added loading for deleting results/reports as it may take some time with external storage option
storage is configured with env variable DATA_STORAGE. If it is "s3" - it will use s3 client, otherwise fallback to "fs".
s3 storage implementation
use batches for reading and writing multiple files into s3 storage
move sorting reports and results on route level to work with s3 data as well

If you can update docs with how to configure this - i can merge this PR

If you can update docs with how to configure this - i can merge this PR

Please check updated readme documentation in fork: github.com/Shelex/playwright-reports-server/feat/useDataStorageS3

added table of contents
added "getting started" section which aggregates installation, setup and running service locally
added sections how to enable s3 storage
added section how to use docker image
fixed path for local fs folder


ESlint throws errors about invalid configuration for rule "eol-last"

Description
The lint script in the project has completely stopped working for me. Originally I thought I might have changed something in my project so I grabbed a fresh clone of the repo, and saw the same issue. I have tested this on 3 physical machines and 2 docker containers with different configurations to determine that the problem is not in global node/npm modules.
Every time I run npm run lint I get the following output:
><EMAIL_ADDRESS>lint:eslint /Users/test/workspace/rb
> eslint --ignore-path .gitignore --ignore-pattern internals/scripts "."

/Users/test/workspace/rb/node_modules/eslint-config-airbnb-base/rules/style.js:
	Configuration for rule "eol-last" is invalid:
	Value "always" must be an enum value.

Referenced from: /Users/test/workspace/rb/node_modules/eslint-config-airbnb-base/index.js
Referenced from: airbnb
Referenced from: /Users/test/workspace/rb/package.json
Error: /Users/test/workspace/rb/node_modules/eslint-config-airbnb-base/rules/style.js:
	Configuration for rule "eol-last" is invalid:
	Value "always" must be an enum value.

Referenced from: /Users/test/workspace/rb/node_modules/eslint-config-airbnb-base/index.js
Referenced from: airbnb
Referenced from: /Users/test/workspace/rb/package.json
    at validateRuleOptions (/Users/test/workspace/rb/node_modules/eslint/lib/config/config-validator.js:115:15)
    at /Users/test/workspace/rb/node_modules/eslint/lib/config/config-validator.js:162:13
    at Array.forEach (native)
    at Object.validate (/Users/test/workspace/rb/node_modules/eslint/lib/config/config-validator.js:161:35)
    at load (/Users/test/workspace/rb/node_modules/eslint/lib/config/config-file.js:522:19)
    at /Users/test/workspace/rb/node_modules/eslint/lib/config/config-file.js:391:36
    at Array.reduceRight (native)
    at applyExtends (/Users/test/workspace/rb/node_modules/eslint/lib/config/config-file.js:362:28)
    at load (/Users/test/workspace/rb/node_modules/eslint/lib/config/config-file.js:529:22)
    at /Users/test/workspace/rb/node_modules/eslint/lib/config/config-file.js:391:36

What is really interesting is that the lint worked just fine 2 days ago, no updates to the dependencies have been made, and it just started throwing this error yesterday. I have seen at least one more user mention this issue in Gitter.
Steps to reproduce

clone repo
npm run setup
npm run lint

Versions

Node/NPM: 6.6.0 / 3.10.7
Browser: n/a

this has been fixed with https://github.com/mxstbr/react-boilerplate/pull/1031

oh, it's not in master yet, so I've completely missed it. Thanks


Snippet Title and Component length is not limited

We need to introduce validation on Snippet Titles and components length, most importantly limits.
Snippet titles should not exceed a certain amount of characters and maybe even match a regex.
Snippet component contents should also be limited in size and there must be a limit for component counts.
(Some of these limits must only apply to sheets that are uploaded/shared)


[gardening] Remove assert requirement for fixed crashers. Fix invalid Swift URLs.

@swift-ci please smoke test and merge


Allow multiple mrkdwn elements in

<Context> merges continuous text contents into one mrkdwn automatically. However, someone may want to control mrkdwn elements separately for layouting message.
Separated mrkdwn have a look like fields in section block, or flexbox layout in HTML.
[
  {
    "type": "context",
    "elements": [
      {
        "type": "mrkdwn",
        "text": "foo\nbar",
        "verbatim": true
      },
      {
        "type": "mrkdwn",
        "text": "A ->\nB ----->\nC ->\nD -->",
        "verbatim": true
      },
      {
        "type": "mrkdwn",
        "text": "Hello,\nworld!",
        "verbatim": true
      }
    ]
  }
]

Our idea is to allow separated mrkdwn contents by using
 HTML element. It would allow to use an interesting layout in <Context>.
<Blocks>
  <Context>

      First mrkdwn element

      ┐
Second markdown element

      ┌→
┘

  </Context>
</Blocks>

This layout makes sense by treating <Context> block as a flex container.

I've used  instead of
 to avoid the side effect for layout in HTML-like formatting in #31.
 is block element so must render as like as block, but  inline element may ignore.


Cutoff

Hi - I have been playing around with my input parameter for a while now but regardless what I include in the self-, close-, or distant-group, my cutoffs are always <0.03. It also does not matter if several bacterial genomes of the same genus are analyzed simultaneously or a single genome.
Inputs that I tried:
self group: tax ID of the genome of interest; the genus of the single genome of interest
close group: the genus of the single genome of interest; closely related other genera; family-, order,- class-, and phylum-level; and domain
Papers that report on using HGTector all show much higher cutoffs for the close and distant group. Can you please help me identify what this low cutoff means or can we please discuss any analytical errors I may have caused?
Thanks again,
Markus

Solved! A great  answer to fix this problem is provided in the comments "Reporter: Generate reports of HGT prediction results - loop #3". The attached zip file in this comment includes helpful info to adjust settings in the config.file.

Hello @mdieser Sorry for not responding so far. I was bit too involved in my current works. Glad that you solved it!


Add Collection view

Thank you for your contribution to the KodaDot NFT gallery.
Let's do a quick check before the merge.
Your contribution will be an eternal part of the community codebase.
PR type

[ ] Bugfix
[x] Feature
[ ] Refactoring

Before submitting this PR, please make sure:

[x] Code builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've didn't break any original functionality
[x] I've posted screenshot of demonstrated change in this PR

Optional

[ ] I've tested it on mobile and everything works
[ ] I found edge cases

What's new? (may be part of changelog)

This PR resolves #981 - Add Collection View

If issue had bounty label ($,$$,$$$)

Fill up your KSM address: https://kodadot.xyz/transfer/?target=135gYktcTwUJPkkZHsjcg3Tpw4JPNGrdLRvotQHVx1kGFSLW

Community participation

[x] Are you at KodaDot Discord? If not yet, let's join us - https://discord.gg/35hzy2dXXh

Screenshot

[x] Whenever my fix has changed something on UI, a screenshot for others, is more than welcome

Before diving into the code, let me suggest some things I would add or change.
page title: something like "Explore all collections" - Yes, I'll change it.
n° of collection (totalCount) - You can see totalCount of collections in above pagination.
display collection issuer with Identity component - Where?
hide collection without nfts? - Shall I do this one?
not a big fan of collection activity on Detail, instead I would have put collection short description - The Issue 981 asked to display those activity.
maybe we should make a difference in design between a collection card and a gallery card - Shall I change the design of collections?
searchbar ? - What can I search in SearchBar?

searchbar ? - What can I search in SearchBar?

search by name or adress

Hey let's add to navbar "COLLECTIONS"

and add it to landing page as well

For detail per collection,

Make heading for collection much bigger
spacing between second and third row I would do much less space.
align it to the center

I think maybe figure out mobile and we can merge it :)

Changed Mobile Layout.

Probably put 80% width for a header in name of the collection and for now, I guess we are good to go!
There is still some cosmetic stuff we can tune later with the design.
Working Functionality first, design last 😄

Changed the width of title.

After finished this issue, I'll take a look at this issue.
Show only collection has NFT with various properties #1023

@TK-Development I've sent you to pay out! https://kusama.subscan.io/extrinsic/0xe4e984cf692f06a76319756e0e6a9589c0bfaa8420868e42118991d60650e19b

Got it. Thanks!


Added Kocaeli University

@mertcankuzey I am sorry, the domain kocaeli.edu.tr is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).


Nav bar does not change on login, dashboard does not load on login

When doing a fresh login, the dashboard does not load apps and the navbar doesn't change.
@brewhousedigital I'm taking a peek at this unless you have immediate ideas.

My only guess is the global store isn't updating. Since we moved from a hard refresh to using the sveltekit router. Is there a way to make the isLoggedIn() reactive?

This seems to help in NavBar:
  let _isLoggedIn = isLoggedIn()
  onMount(() => {
    _isLoggedIn = isLoggedIn()
    const unsub = onAuthChange(() => {
      console.log('auth changed')
      _isLoggedIn = isLoggedIn()
    })
    onDestroy(unsub)
  })

But then it creates an oddity where the dashboard won't populate upon subsequent navigation back to it.
https://user-images.githubusercontent.com/1068356/197836672-fb464750-8c0b-40a4-8949-5036af2e4809.mp4

Ok this has been fixed in https://github.com/benallfree/pockethost/commit/a149df0d583a8f43b1a7422ba849f911e90fe74b

A slightly less secure version of this would be to use a global store to save the token + user information in, so that the entire app updates as soon as the store changes. Thoughts? This way we wouldn't have to worry about onMount, and destroying subscriptions and stuff
// store.js
const globalUserData = writable({});
const isLoggedIn = writable(false);

globalUserData.subscribe(value => {
	isLoggedIn.set(!!value?.user)
});

// database.js
const response = await authViaEmail(email, password)
globalUserData.set(response)

{#if isLoggedIn}
   Reactive content goes here...
{/if}

Yeah something like that would work. I'm not super familiar with svelte stores, but that looks similar to a global React store which is normally how I would do it
const MyComponent = ()=>{

   const isLoggedIn = useIsLoggedIn()
   ... render ...
}

Let me know if you want me to swap it out! I can write out some docs for it too.

It’s working for now but if you’d like to take a shot at something better go right ahead! I am so glad to have someone collaborating!


resolve both sides of name check before throwing an error

Attempt to solve SBS assertion resolution race.

cc @patrickxb this probably would have saved you, won't help you now though.


Docs editing

You must first register a validator, and then configure the script, otherwise nothing will work

Thanks for this - it's somewhat in that order because running the script gives you your operator addresses. But I need to make that whole process smoother with a dedicated script to get the addresses.
Will merge ASAP once I've had a chance to look at docs/setup process as a whole

Thank you for this, unfortunately this PR conflicts but suggested improvements will be included in #590


build: implement covdefaults coverage plugin.

Pull Request Checklist

[ ] New code has 100% test coverage
[ ] (If applicable) The prose documentation has been updated to reflect the changes introduced by this PR
[ ] (If applicable) The reference documentation has been updated to reflect the changes introduced by this PR
[ ] Pre-Commit Checks were ran and passed
[ ] Tests were ran and passed

Description

This PR adds the covdefaults plugin to our coverage config.
The plugin offers default configs for [tool.coverage.run] and [tool.coverage.report].
For "run", the main difference is that it activates branch coverage. This is something I always run on other projects and I think would be a nice addition to our config. Our overall coverage score takes a hit, but it's not as bad as I thought it might be.
For reporting, it adds a fail_under value - which we don't currently have as we let sonar handle that. We can override their default of 100, so I set it to 96 which is our current baseline after branch coverage activated.
Close Issue(s)

RFC @litestar-org/maintainers - WDYT about adding this plugin?

sgtm


Support CSharp Light Bulbs (FQN, Add Using)

Summary of the changes

Support for Fully Qualified Namespace C# Light Bulb

Support for Add Using C# Light bulb

Abstraction Layer / Refactoring to create shared light bulb infrastructure between TSLanguageServer + HTMLCSharpLanguageServer.

This implementation doesn't have support for code actions which require resolving with Roslyn (ex. via textDocument/codeActionResolve). Working on an appropriate expansion for this, and will likely require changes in omnisharp-vscode.

Tracked here: https://github.com/dotnet/aspnetcore/issues/25918

Some general perf optimizations are possible, but wanted to avoid potential pre-optimizations. Will re-visit if we see issues.

Testing: TODO assuming no issues with the design.

Fixes: https://github.com/dotnet/aspnetcore/issues/24779
Fixes: https://github.com/dotnet/aspnetcore/issues/18173
Fixes: https://github.com/dotnet/aspnetcore/issues/24778
Fixes: https://github.com/dotnet/aspnetcore/issues/25144

Thanks @NTaylorMullen @ajaybhargavb. Addressed the feedback.
Noticing some issues where fully qualifying <Hello> results in <SomeComponent.Hello.Hello> despite the preview showing <SomeComponent.Hello>. Considering the preview is correct, I believe this is an external regression.
I'm also not getting any code actions with CTRL + . (shows no code actions found), but I do get them when I right click and select quick actions. I believe this is likely also an external regression.
Is anyone else seeing this on latest VS?


Clean up json dumps

Currently we have the line
json.dumps(prop, ensure_ascii=False)

in a lot of places. We should move this to the utils function so we never forget the ensure_ascii flag.

let me do it.

Awesome thank you @d29107d


[RMQ ERROR] on v10.11.1

since last ios update (yesterday), my team and i got such errors while running our specs :
[RMQ ERROR]  style_name :list_view_cell doesn't exist for a ProductListView::ItemWithProductCell. Add 'def list_view_cell(st)' to SignOnControllerStylesheet class

dis someone herer notice same behaviour ?

Standard question, sorry: I assume you did rake clean:all and reset your simulator?
I haven't noticed this behavior yet, but I haven't built an app yet since updating. Maybe @kevinvangelder ?

this is an Error/warning that has been in RMQ for a while from here
Short answer, you must be trying to apply a style :list_view_cell on a view that is of class type ProductListView::ItemWithProductCell and the test you are running is testing on a controller that is setting the stylesheet to SignOnControllerStylesheet (most likely SignOnController)

@jney did that answer your question, is there still an issue here?

no issue there, thank you guys

glad to help! :+1:


Prepare plugin support for objects with multiple BaseTextures

The entire discussion for this task and its development is found at #3829
Changes:

Adds support for AnimatedSprites with more than 1 source texture to the Prepare plugins
Removes the duplicate function findBaseTextures() found in both WebGL & CanvasPrepare
Moves function findBaseTextures() to BasePrepare.js
Splits the `BasePrepare.register(addHook,uploadHook) into 2 separate methods
Updates unit tests

I am not thoroughly please with the naming of the findBaseTexure and findTexture methods, hopefully there are some better suggestions
Resolves #3829

Whats the etiquette when making changes to pull requests. update the branch or make a new one?

Just "rebase" the branch, it wont be big change.

Awesome!
No problem, I enjoyed it. I'd be happy to help in the future if you ever need some extra hands.


Update 06a-data-warehouse-load.md

this code block will be used later, not here
Module: 00
Lab/Demo: 00
Fixes # .
Changes proposed in this pull request:

Hello  @sophiexu
Changes were made in another commit, closing this PR.
Thank you,
Mihai


Fix product key examples

With this change in all Autounattend.xml files:

the Key element is commented
the same description is used

The corresponding documentation on the XML schema can be found here.

@joefitzgerald can you have a look at this?


evel=info msg="Starting image update cycle, considering 0 annotated application(s) for update"

Has anyone experience this with the image updater ? This was initially working fine, I've recreated it a couple of time but the same issue persists.
time="2021-02-22T23:52:33Z" level=info msg="argocd-image-updater v99.9.9+457b52f starting [loglevel:DEBUG, interval:2m0s, healthport:8080]"
time="2021-02-22T23:52:33Z" level=debug msg="rate limit for https://90152327234848.dkr.ecr.us-east-1.amazonaws.com is<PHONE_NUMBER>"
time="2021-02-22T23:52:33Z" level=info msg="Loaded 1 registry configurations from /app/config/registries.conf"
time="2021-02-22T23:52:33Z" level=debug msg="Creating in-cluster Kubernetes client"
time="2021-02-22T23:52:33Z" level=debug msg="Using ArgoCD API credentials from environment ARGOCD_TOKEN"
time="2021-02-22T23:52:33Z" level=info msg="ArgoCD configuration: [apiKind=kubernetes, server=argocd-server.argocd.svc.cluster.local, auth_token=true, insecure=true, grpc_web=true, plaintext=true]"
time="2021-02-22T23:52:33Z" level=info msg="Starting health probe server TCP port=8080"
time="2021-02-22T23:52:33Z" level=info msg="Starting metrics server on TCP port=8081"
time="2021-02-22T23:52:33Z" level=info msg="Warming up image cache"
time="2021-02-22T23:52:33Z" level=info msg="Finished cache warm-up, pre-loaded 0 meta data entries from 6 registries"
time="2021-02-22T23:52:33Z" level=info msg="Starting image update cycle, considering 0 annotated application(s) for update"
time="2021-02-22T23:52:33Z" level=info msg="Processing results: applications=0 images_considered=0 images_skipped=0 images_updated=0 errors=0"
time="2021-02-22T23:54:33Z" level=info msg="Starting image update cycle, considering 0 annotated application(s) for update"
time="2021-02-22T23:54:33Z" level=info msg="Processing results: applications=0 images_considered=0 images_skipped=0 images_updated=0 errors=0"
time="2021-02-22T23:56:33Z" level=info msg="Starting image update cycle, considering 0 annotated application(s) for update"
time="2021-02-22T23:56:33Z" level=info msg="Processing results: applications=0 images_considered=0 images_skipped=0 images_updated=0 errors=0"
time="2021-02-22T23:58:33Z" level=info msg="Starting image update cycle, considering 0 annotated application(s) for update"

Hi @a5a5a9, given the fact that you are using kubernetes API as access type according to the logs: Have you installed the Image Updater to the same namespace where Argo CD is running in?
I also see that you have ARGOCD_TOKEN set-up, and are using an unreleased version (i.e. latest), so maybe there's a discrepancy between your configuration and the version you are running? Do you expect Image Updater to use Kubernetes API or Argo CD API?

No, the image updater is installed on a separate namespace in the same cluster but that is how it was working before.
I was not aware of Kubernetes API vs ARGO CD API , as long as I can make it work again it wouldn't matter to me making changes.

I think when you restarted the pod, a new image was pulled containing recent changes. You can either use the v0.8 image in your deployment manifest (this is the general suggestion, since latest may contain - as you now experienced - breaking changes), or you will have to specify the API type to be used as argocd, either by

passing the --applications-api argocd command line parameter to the container's startup command or
setting applications_api: argocd in the argocd-image-updater-config ConfigMap and restarting the deployment

now getting this level=error msg="Error: rpc error: code = Unauthenticated desc = invalid session: token contains an invalid number of segments" I have recreated the TOKEN with no luck
time="2021-02-23T20:43:08Z" level=info msg="argocd-image-updater v0.8.0+18d3e63 starting [loglevel:DEBUG, interval:2m0s, healthport:8080]"
time="2021-02-23T20:43:08Z" level=debug msg="rate limit for https://XXXX.dkr.ecr.us-east-1.amazonaws.com is<PHONE_NUMBER>"
time="2021-02-23T20:43:08Z" level=info msg="Loaded 1 registry configurations from /app/config/registries.conf"
time="2021-02-23T20:43:08Z" level=debug msg="Creating in-cluster Kubernetes client"
time="2021-02-23T20:43:08Z" level=debug msg="Using ArgoCD API credentials from environment ARGOCD_TOKEN"
time="2021-02-23T20:43:08Z" level=info msg="ArgoCD configuration: [server=argocd-server.argocd.svc.cluster.local, auth_token=true, insecure=true, grpc_web=false, plaintext=true]"
time="2021-02-23T20:43:08Z" level=info msg="Starting health probe server TCP port=8080"
time="2021-02-23T20:43:08Z" level=info msg="Starting metrics server on TCP port=8081"
time="2021-02-23T20:43:08Z" level=info msg="Warming up image cache"
time="2021-02-23T20:43:08Z" level=error msg="error while communicating with ArgoCD" argocd_server=argocd-server.argocd.svc.cluster.local grpc_web=false grpc_webroot= insecure=true plaintext=true
time="2021-02-23T20:43:08Z" level=error msg="error while communicating with ArgoCD" argocd_server=argocd-server.argocd.svc.cluster.local grpc_web=false grpc_webroot= insecure=true plaintext=true
time="2021-02-23T20:43:08Z" level=error msg="Error: rpc error: code = Unauthenticated desc = invalid session: token contains an invalid number of segments"

it is fixed now .


Add support for Oracle

Follow the other integration test patterns for MySQL and PostgreSQL.
Use Oracle test container support.

@kdhrubo  I will start working on this. I will be taking sometime to understand the project.

@kdhrubo
Update about the work on writing integrated tests
1/28/2024 - created the schemas , tables, procedure and functions for testing. Need to verify the syntaxes are correct.

Did you create the same sakiladb for oracle ?
We use a trimmed version from the JOOQ repo

Please allow the use of different oracle jdbc drivers versions (for example ojdbc6-<IP_ADDRESS>.jar) so we can create APIs for legacy Oracle Databases.

Which versions of Oracle do you want us to support ? We can definitely look into supporting legacy oracle databases.

Oracle 9i. We use another java based tool ReplicaDB and we swapped the jdbc drivers to support Oracle 9i and works flawless.
https://github.com/osalvador/ReplicaDB/issues/61#issuecomment-1055169183
This is the compatible driver
https://repo1.maven.org/maven2/com/oracle/database/jdbc/ojdbc6/<IP_ADDRESS>/ojdbc6-<IP_ADDRESS>.jar

Got it. Have you tried using the current version?
The challenge is testing. We use testcontainer for integration test - which does not have oracle9i support.
Also we do not have access to oracle 9i or other versions. If you help us we can definitely make this compatible with Oracle 9i.
You can also join us on discord for faster response.

I haven't tried it yet. Will report at the start of the week. I can not join discord. It says "This invite may be expired"

Super.
Here is the updated invite -

@lingaiahdanda - closing this as already implemented now.
Duplicate of
#386


How to properly forward request/response payloads to a non blocking payload analysis endpoint?

What should we add or change to make your life better?
The Middleware doco states "Middleware should avoid interacting with the request or response bodies. Bodies are not buffered by default, so interacting with them can prevent them from reaching their destinations. While enabling buffering is possible, it's discouraged as it can add significant memory and latency overhead. Using a wrapped, streaming approach is recommended if the body must be examined or modified. See the ResponseCompression middleware for an example."
We understand this, however putting this together, while impacting the overall performance as little as possible, may be a little tricky.
Would there be any interest in providing such a sample, I'd be happy to work on this, while benefiting from your review, in order to provide the community with a best possible approach.
Why is this important to you?
As stated in the title, we're requested to transmit incoming/outgoing payloads to an external analysis endpoint (for audit/compliance reasons) and would like to do it as cleanly as possible.

I'd certainly collaborate with you on this.
Are you mirroring the whole request/response, or just the bodies? See https://github.com/microsoft/reverse-proxy/issues/105.
The bodies are the difficult part.
Step 1: A middleware that wraps the request and response body streams, copies request fields and headers, and starts the mirroring.
Step 2: As request body data is read by the real application, the wrapper duplicates that data into a write-behind buffer to avoid slowing the main request. E.g. a Pipe. That buffer needs to be big enough to keep up. Decide what to do when it fills up. E.g. abandoning the mirror if it's too slow, or allow for a larger buffer.
Step 3: As response body data is written by the real application, the wrapper the wrapper duplicates that data into a write-behind buffer just like the request.
Step 4: When the request processing application ends, gracefully or otherwise, make sure to clean up the mirroring logic. Decide if you want to let it continue in the background (so long as it's no longer referencing any request/response structures), etc. but let the middleware exit quickly so you don't block processing new requests.


Fix Makefile to be less stringent on failues of zsh

I am making some lines optional in the Makefile and added fixes from the RPM review.

Didn't @ericcurtin do this yesterday?

He did but I missed it in my merge. I tried it in f39 and it broke in the make so I have went with my original design. If the other mode is still needed I can try to figure out why f39 Make hates shell

LGTM


On contact page there is a "Contact Form" section, but no form

This is fixed:
https://github.com/spicygreenbook/greenbook/issues/14
Thanks!


Unlisted editions should say "not for sale"

Instead of "$0.00"

Fixed in https://github.com/macterra/artx-market/commit/c4a548d12366a9c23dfcbc6579b938827dc3ec0d


Unable to send command

I have set up the server and learned a command successfully, however when I try to run my ifttt applet, it fails on a 404 error and says command not found: acpower (acpower is the name of my command).  I am thinking maybe there is something wrong with my array formatting but not sure...my ngrok is working correctly and I am able to access from the ngrok address.  This is my commands.js with the secret removed:
module.exports = [
{
"command": "acpower",
"secret": "removed",
"mac": "77:0f:78:00:60:bf",
"ip": false,
"data": "26006000000127901411141014111436141014111411141014361411143514111436140005480001274715000c540001254714000c550001244715000d050000000000000000"
}
];

Apologies, after adding a bunch of console outputs I realized that I hadn't copied the last character in my secret to IFTTT.  Doh!

Lol, glad you got that working. Have fun


cotp: 1.2.1 -> 1.2.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/replydev/cotp/releases.
meta.description for cotp is: Trustworthy, encrypted, command-line TOTP/HOTP authenticator app with import functionality
meta.homepage for cotp is: https://github.com/replydev/cotp
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.2.3 with grep in /nix/store/a098lndwx175nwxp5r5cl22m059mv371-cotp

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
cotp

Instructions to test this update (click to expand)

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

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

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

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

1 package built:

cotp

Maintainer pings
cc @DavSanchez for testing.

Tested on aarch64-darwin from my side.


fix(*): allow modal and popover to use lazy loaded components

Short description of what this resolves:
When Ionic is used with @angular/router, and a module is lazy-loaded using angular's standard lazy-loading API (loadChildren route config), the lazy-loaded components cannot be displayed in a modal or popover. This is a huge problem because a real-life application will need to utilize lazy-loading in order to have acceptable performance.
Changes proposed in this pull request:
Expose ModuleLoader and allow to register lazy-loaded entry components explicitly so that they can be displayed in a Modal or Popover
Ionic Version: 3.9.2

Hello and thank you for contributing to Ionic! We have been working on porting all of the Ionic components to web components and have recently updated master to reflect this. This significant change has caused this pull request to break. While we really appreciate the time and effort you put into creating this, we are not able to merge it because of the newly introduced conflicts. We are extremely sorry about this. We will not be merging any more features in to v3. If this is a feature and you have the time, please resubmit this PR against the master branch. If this is a critical security issue in v3, we would greatly appreciate it if you would resubmit the PR against the new v3 branch. Thanks so much for your time!


Sticky table cells

Closing this, as it's not longer relevant with our plans to move to Filament v3.


install for Mac

anyone know how to install on Mac

readon ...
StackOverflow.com

@theplexguy please join discord if you need handholding


Only permit web workers to be initialized once.

Description
When embedded in a SPA, the initWebWorkers method should only be called once per page.
When the DOM element the viewer is attached to is rendered within a React component, the installViewer method may be called multiple times per page if user navigation is causing that DOM element to be created and removed multiple times.
Because of this line of code, Cornerstone will throw an exception if this is tried. Cornerstone does not export the control object such that consumers could base their logic on that, so I created my own control object.
This gets past the exception within Cornerstone, but causes the logs to be noisy as multiple other parts of the viewer are loaded multiple times, reporting warnings. However the viewer appears to be functional after a reload.
This PR is a workaround of code in Cornerstone, and handling this use case in a more permanent fashion would require multiple checks elsewhere and perhaps changes in Cornerstone code. I am unsure of side effects stemming from this change, but after my own experimentation it appears benign aside from the noisy logs. I have only tested in Chrome.
Images of the noisy logs.

This makes sense to me and I am fine with the PR.
p.s. Your Github profile picture is great.
Thanks!


tests: enable fuzz for filtered anti-semi NLJoin

Which issue does this PR close?

Closes #11537.
Rationale for this change

It turned out to be not a NLJoin issue, but fuzz tests -- during NLjoin construction, join filter was completely ignored, and all NLjoin tests were running with only equijoin conditions in filter.
In the same time filtered inner/left/right/full join fuzz tests were passing even without the filter -- the reason is that they've been using less_than_100_join_filter, which always returns True, as generation of input data for column, used in this filter, always returns values less than 100 -- make_staggered_batches comment:
/// two sorted int32 columns 'a', 'b' ranged from 0..99 as join columns

so it seems to be more useful to place col_lt_col_filter in all tests, since it has non 100% selectivity.
Finally, after replacing filter in all test cases, some of HjSmj tests turned out to be flaky, so they are temporarily disabled, until #12359 fix.
What changes are included in this PR?

NLJoin construction in fuzz tests now takes into account join_filter, and constructs composite filter as a union of join_filter and equijoin conditions, all fuzz tests are enabled for NljHj case
all _filtered test cases now use col_lt_col_filter
some _filtered testcases disabled for SortMergeJoin due to their flakiness

Are these changes tested?

Yes
Are there any user-facing changes?

No, it's related exclusively to the tests

To find if test is flaky I followed the approach of running the test 1000 times in the loop. Like for AntiJoin

I've run all them in a loop with hundred iterations, and all currently present tests are passing. The only failed tests after filter chenge were SMJ related -- they are disabled in f9d2a907f48cffdb1bf2d6ba601f8104d0dd8eeb


Prevent Pinger Exceptions

Under certain error conditions (if the connection is disconnected by the caller during adverse network conditions) the "pinger" setInterval will continue to run, triggering a fatal unhandled exception.
This patch makes gdax-node a little smarter about disabling pinger during any websocket disconnect scenario.

@alexmarkley Thanks for this patch — if you're still interested, could you rebase it?

Thanks a lot @alexmarkley!


Finalize development checklist draft

Finalize first draft checklist:

[ ] Review and revise ordering of items
[ ] Review and revise copy for clarity
[ ] Update test fields for all items to help standardize testing tools
[ ] Annotate standards to identify which items apply at product, page, component, and content type levels
[ ] Annotated standards with mobile considerations
[ ] Decide on checkbox formatting

@wlla is this still relevant?

I am currently revising and reformatting these checklists for various audiences, but they may be published somewhere other than the design toolkit. I'm going to close this ticket to help tidy up your issues list. When I have something actionable we can return. Sound good?

It does. Thank you.


New version: Atom v0.10.1

Registering package: Atom
Repository: https://github.com/JunoLab/Atom.jl
Created by: @pfitzseb
Version: v0.10.1
Commit: 7c060f9a5d26b10ced8ebe46be2bc0a78a86030f
Reviewed by: @pfitzseb
Reference: https://github.com/JunoLab/Atom.jl/commit/7c060f9a5d26b10ced8ebe46be2bc0a78a86030f#commitcomment-34953376

TagBot tag


Rename testSecret to testPasswordHash in the install dashboard tests.

A followup tot he analytics PRs. I was going to add this minor refactoring yesterday while adding analytics-related fixes to the dashboard manifests generation tests, but got distracted and forgot about it.
We are using a password hash not a secret for dashboard installation, so I think the variable name should match it.

Haha, thanks!


Will be a plugin available?

Is this only a standalone application or will be a plugin available for the netbeans IDE? I know the other plugin but it's not maintained anymore I think. Would be nice, if we can have yours.

Yes, it's suppose to be available as plugin as well. Just build it as nbm and install it via Tools/Plugins/Downloaded/Add Plugins. I put current build here: http://deltahex.exbin.org/dev/org-exbin-deltahex-netbeans.nbm
Beware, that this plugin is far from being finished. I have to connect undo and other stuff... Also netbeans plugins portal is down right now, so it cannot be published anyway...

Sounds great, thx :)

Published as NetBeans plugin:
http://plugins.netbeans.org/plugin/67898/deltahexeditor
Not verified for central plugins repository yet.

Saw it and it is in use, thx :)


Not able to get the difference work item from last release to current release if we manually linked the Work items with latest build number.

Azure DevOps Extensions
Generate Release Notes (Node Cross Platform)
Platform
Azure DevOps Services
Azure DevOps Server (TFS) Version
No response
Extension Version
No response
Describe the bug
Not able to get the difference work item from last release to current release if we manually linked the Work items with latest build number.
“The data source for the generated Release Notes is the Azure DevOps REST API's comparison calls that are also used by the Azure DevOps UI to show the associated Work items and commit/changesets between two builds/releases. Hence this task should generate the same list of work items and commits/changesets as the Azure DevOps UI, though it attempts to enrich this core data with extra information.”
Repo Steps

Go to '...'
Click on '....'
Scroll down to '....'
See error
...

Expected Behavior
No response
Logging Information
No response

To give more details into this issue, let me elaborate. The API Get Work Items Between Builds is not returning manually linked work items, whereas the API Get Build Work Items Refs returns those work items, for each build.
One option to give support for this request is to add a new parameter to the task and, when set, the Get Build Work Items Refs is used instead.

Hi Richard
Thank You for your precious time,
Answer to your comments ,

Does this match what is needed?
yes it will match our requirement as @SWarnberg mentioned in the above comments, So a parameter by default off where we can choose to generate manually linked work items also along with regular auto linked work Items by Azure.
Would it be better to place these 'manually linked' WI in separate array to the existing workitems array?
No , I guess we can club both manually linked and auto linked based on some parameter is good idea , instead of separate array.

Note :
I'm using Version 3 of this tasks , I have written an MD Template file to fetch the work items between releases .

Hi @rfennell
I appreciate your help.
After testing this this with a live release and build, it still did not work for me.
I am using Version 3.72.2 of Generate Release Notes.
I have a YAML Build which doesn't have stages defined (hence using ___default) and I am using the Generate Release Notes in a Classic Release pipeline to pickup the release notes from the build.
I have attached a bug manually to the build, and expected it to be added to the release notes.
I have the "Check for Manually Linked WI" checked.
Still no luck.
In the log, I can't see any mention of it checking for Manual Linked Work items....
What am I missing?
Do i need stages?
Can I use the "WIQL Where Clause" instead to bring in the work items i need from a query or is that just filtering the already found work items?

Could you send we a debug log so I can see what is happening. We should see the new manual check running and we can compare the number of WI found by each call prior to the removal of duplicates.
As you mention you could use the new wiql query. The builds a separate list of WI to main list.
See https://blogs.blackmarble.co.uk/rfennell/2021/10/30/new-features-for-my-azure-devops-release-notes-extension/

Hi Richard,
I've sent you an email.
Cheers

OK there are a few things going on here
Code Path and the manually added WI fix
I can see from your log that you are using the default fix to bypass API limits #349
2021-11-04T10:08:46.8747392Z Checking what commits and workitems have changed from [XXX-20211104-4][ID 803] => [XXX-20211104-5] [ID 804]
2021-11-04T10:08:46.8748005Z Defaulting on the workaround for build API limitation (see issue #349 set 'ReleaseNotes.Fix349=false' to disable)
2021-11-04T10:08:46.8748529Z Using workaround for build API limitation (see issue #349)
2021-11-04T10:08:46.8749689Z Processing commits found

This code path does not make use of the new 'checkForManuallyLinkedWI: true' parameter as it should not need it, the #349 fix already makes calls based on the build. However, if you want to test this theory set a build variable ReleaseNotes.Fix349=false (the default is on), or make a change in your local runner config file. This will use the code path that does not use the fix and hence use the new feature.
Direct API call
You mention that you can't see the WI listed in an API call
/_apis/build/builds/804/workitems?api-version=6.0&$top=10000

If this is the case, then I am not sure what we can do, as this is the call I am making to get the associations

Thanks for the help @rfennell
I can't turn ReleaseNotes.Fix349=false as I am using the Classic Release Pipeline.  Is there a way of doing this with Classic?
  I am not sure if you are using this call, or doing it some other way... but that call is definately picking up the work item (#5235)

Hi @rfennell
I tried with ReleaseNotes.Fix349 = false and it is now working!
So this means I am limited to 200 works items per build in the release - correct?

Looks like I need to re investigate the fix349 code.

I have revised (and simplified) the calls to the new manual wi check to make sure all code paths calls them even when the fix349 code is used.
If you want to try it locally it is in the PR #1135, I will get it pushed through the release pipeline

It is shipped in 3.74.3

Thanks @rfennell
I will try it out today.

@rfennell
Ok, tried it out - yes it's working now with and without fix349 turned on.
Thanks!


Change Names for Most(If Not All) Particles

The current particle names aren't really all that great. They were made up on the spot, and really more meant to be place holders than anything. However, I never changed them before releasing the mod. Now, it's time to change that, and change them.

Boom particle -> Blast wave
Big explosion -> Fireball
Lingering smoke -> Mushroom cloud
Default explosion -> Either default explosion or explosion emitter
Underwater names:
Shockwave -> Shockwave(?)
Underwater blast -> Underwater blast(?)

Completed for both 1.19.2 and 1.19.3


automatically create a cherry-pick PR to the release candidate branch by either command or label

https://docs.prow.k8s.io/docs/overview/ can enable a whole set of functionalities besides cherry-picking PRs.

we installed the GitHub action.
A bot system may take too much time, will revisit in the future.


⚠ gorzdrav.org has degraded performance

In fe2dbb8, gorzdrav.org (https://gorzdrav.org) experienced degraded performance:

HTTP code: 200
Response time: 5170 ms

Resolved: gorzdrav.org performance has improved in f03b449.


Scheduler updates

Coverage decreased (-1.5%) to 30.206% when pulling 7b141e770a68af87a942b32ddaf6fae5984e8a17 on scheduler-updates into 51a3c77cc709d9b7857299ea5a81d7a03b01da44 on next.


Vrf reveal

Implementing VRF for Launchpeg. A few notes :

I kept forceReveal() with pseudo-randomness for safety
Multisig will need to add the launchpeg contract to its list of VRF consumers.

An example on Fuji can be found here
Not related but I noticed that the tests were forking mainnet. I removed it, I think it was unnecessarily slowing down the tests.
Detailed description of how this works here.

Deployed a new contract on Fuji : https://testnet.snowtrace.io/address/0xa8e171869fc5a8da7183d535906d0fca76a51b41


Plugins installed but not autoload in vim

Hi, i have a problem with vim-plug with vim8.
I have two plugins in .vimrc:
call plug#begin('~/.vim/plugged')

Plug 'itchyny/lightline.vim'
Plug 'neomake/neomake'

call plug#end()

Plugins are correctly install but when i edit a new files they don't load automatically.
Do you have an idea please ?
Thanks

Type:

[X] Bug
[ ] Enhancement
[ ] Feature Request
[ ] Question

OS:

[ ] All/Other
[X] Linux
[ ] OS X
[ ] Windows

Vim:

[X] Terminal Vim
[ ] GVim
[ ] Neovim

@Sideris35, seems like the problem is with lightline plugin, other stuff loads normally for me.

I installed neovim it's works


Proposal: allow to type and draw numbers

Is your feature request related to a problem? Please describe.
Since color is currently selected by 1-9 keys, it's impossible to type these numbers as text or draw with them.
Describe the solution you'd like
When pressing 1-9 key, it should be allowed to type them instead of changing color. Of course, a question arises: how to change color? I've did some tests, and keys Alt+1 up to Alt+9 worked fine for me, so I'm proposing to move color switching to them instead.
Here's how it could look:
case "alt+1", "alt+2", "alt+3", "alt+4", "alt+5", "alt+6", "alt+7", "alt+8", "alt+9":
	m.color = msg.String()[len(msg.String())-1:] // last symbol is number we need

Describe alternatives you've considered
There are other ways to approach this:

Make Alt+number keys to type/select the number. However, it's inconvenient for typing.
Use other hotkeys for color selection. Not sure what hotkeys could be used though because Ctrl+number gives unexpected results (like Ctrl+@ when you're trying to type Ctrl+2), and Shift+number are used to typing special characters.

Ah I wish I thought about this a little more and went with Alt+[1234] or Alt+[rbgy] for color picking instead of using simply the numbers but I figured that not many people would need the numbers to draw with since you can now type them out when in "insert" mode.
I think the Alt+[1234] is reasonable, I'd accept a PR for that change if you want to contribute to the project or I can add the changes myself, let me know :)

Also, thanks for the well-written + well-thought issue. I really appreciate it ❤


Simplify Where API

The idea is to simplify the API making less verbose
Remove the api.ConditionByXXX functions and instead have two ways of creating conditionalAPIs:
Where(Model, ...Condition) -> For conditions that will be evaluated in the server.

An empty list of conditions defaults to index-based model equality

WhereCache(predicate) -> For conditions that will be evaluated in the cache using a callback function.
Based on #113

Pull Request Test Coverage Report for Build 849051643

91 of 116 (78.45%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.5%) to 73.496%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

client/condition.go
37
41
90.24%

ovsdb/bindings.go
13
17
76.47%

client/api.go
21
26
80.77%

client/orm.go
16
28
57.14%

Totals

Change from base Build 842678591:
0.5%

Covered Lines:
1564

Relevant Lines:
2128

💛  - Coveralls


Error: 410 Gone:  {"jsonrpc":"2.0","error":{"code": 410, "message":"The RPC call or parameters have been disabled."}, "id": "b8c96bb9-ea15-4c14-8e71-a80e1cfe3225" }

Running any of the yarn script fails with a grpc 410 error. For example
yarn run dev --init-user --config-file config.yaml
produces:
yarn run v1.22.21
$ NODE_OPTIONS=--max-old-space-size=8192 ts-node src/index.ts --init-user --config-file config.yaml
[2024-02-19T12:39:31.599Z] info: Loading config from config.yaml
[2024-02-19T12:39:31.609Z] info: Bot config:
{
  "global": {
    "driftEnv": "mainnet-beta",
    "initUser": false,
    "testLiveness": false,
    "cancelOpenOrders": false,
    "closeOpenPositions": false,
    "forceDeposit": null,
    "websocket": true,
    "eventSubscriber": false,
    "runOnce": false,
    "debug": false,
    "subaccounts": [
      0
    ],
    "eventSubscriberPollingInterval": 5000,
    "bulkAccountLoaderPollingInterval": 5000,
    "endpoint": "https://api.mainnet-beta.solana.com",
    "priorityFeeMethod": "solana",
    "maxPriorityFeeMicroLamports": 10000,
    "keeperPrivateKey": "*******************************************************",
    "useJito": false,
    "jitoBlockEngineUrl": "frankfurt.mainnet.block-engine.jito.wtf",
    "jitoAuthPrivateKey": "/path/to/jito/bundle/signing/key/auth.json",
    "txRetryTimeoutMs": 30000
  },
  "enabledBots": [
    "filler",
    "trigger",
    "floatingMaker"
  ],
  "botConfigs": {
    "filler": {
      "botId": "filler",
      "dryRun": true,
      "fillerPollingInterval": 6000,
      "metricsPort": 9464,
      "revertOnFailure": true,
      "simulateTxForCUEstimate": true
    },
    "spotFiller": {
      "botId": "spot-filler",
      "dryRun": false,
      "fillerPollingInterval": 6000,
      "metricsPort": 9464,
      "revertOnFailure": true,
      "simulateTxForCUEstimate": true
    },
    "liquidator": {
      "botId": "liquidator",
      "dryRun": false,
      "metricsPort": 9465,
      "disableAutoDerisking": false,
      "useJupiter": true,
      "perpSubAccountConfig": {
        "0": [
          0,
          1
        ]
      },
      "spotSubAccountConfig": {},
      "maxSlippagePct": 50,
      "maxSlippageBps": 50,
      "deriskAuctionDurationSlots": 100,
      "deriskAlgo": "market",
      "minDepositToLiq": {
        "1": 10,
        "2": 1000
      },
      "excludedAccounts": [
        "9CJLgd5f9nmTp7KRV37RFcQrfEmJn6TU87N7VQAe2Pcq",
        "Edh39zr8GnQFNYwyvxhPngTJHrr29H3vVup8e8ZD4Hwu"
      ],
      "maxPositionTakeoverPctOfCollateral": 0.5,
      "notifyOnLiquidation": true
    },
    "trigger": {
      "botId": "trigger",
      "dryRun": true,
      "metricsPort": 9465
    },
    "markTwapCrank": {
      "botId": "mark-twap-cranker",
      "dryRun": false,
      "metricsPort": 9465,
      "crankIntervalToMarketIndicies": {
        "15000": [
          0,
          1,
          2
        ],
        "60000": [
          3,
          4,
          5,
          6,
          7,
          8,
          9,
          10,
          11,
          12,
          13,
          14,
          15,
          16
        ]
      }
    },
    "floatingMaker": {
      "botId": "floating-maker",
      "dryRun": true,
      "metricsPort": 9467
    }
  }
}
[2024-02-19T12:39:31.610Z] info: RPC endpoint: https://api.mainnet-beta.solana.com
[2024-02-19T12:39:31.610Z] info: WS endpoint:  undefined
[2024-02-19T12:39:31.610Z] info: Helius endpoint:  undefined
[2024-02-19T12:39:31.610Z] info: DriftEnv:     mainnet-beta
[2024-02-19T12:39:31.610Z] info: Commit:
[2024-02-19T12:39:31.610Z] info: Loading wallet keypair
[2024-02-19T12:39:31.611Z] info: loading private key from /.../keeper-bots-v2/id.json
[2024-02-19T12:39:31.611Z] info: Trying to load private key as numbers array
[2024-02-19T12:39:31.823Z] info: DriftClient ProgramId: dRiftyHA39MWEi3m9aunc5MzRF1JYuBsbn6VPcn33UH
[2024-02-19T12:39:31.823Z] info: Wallet pubkey: ...
[2024-02-19T12:39:31.823Z] info:  . SOL balance: 0.09787275
[2024-02-19T12:39:31.873Z] info:  . USDC balance: 112.712606
[2024-02-19T12:39:31.873Z] info: priorityFeeMethod: solana, maxFeeMicroLamports: 10000
[2024-02-19T12:39:31.878Z] info: filler: revertOnFailure: true, simulateTxForCUEstimate: true
[2024-02-19T12:39:31.878Z] info: filler: jito enabled: false
[2024-02-19T12:39:31.884Z] info: prometheus scrape endpoint started: http://localhost:9464/metrics
[2024-02-19T12:39:31.884Z] info: prometheus scrape endpoint started: http://localhost:9465/metrics
[2024-02-19T12:39:31.884Z] info: prometheus scrape endpoint started: http://localhost:9467/metrics
/home/.../keeper-bots-v2/node_modules/@solana/web3.js/src/connection.ts:1648
        callback(new Error(`${res.status} ${res.statusText}: ${text}`));
                 ^
Error: 410 Gone:  {"jsonrpc":"2.0","error":{"code": 410, "message":"The RPC call or parameters have been disabled."}, "id": "b8c96bb9-ea15-4c14-8e71-a80e1cfe3225" }

    at ClientBrowser.callServer (/home/.../keeper-bots-v2/node_modules/@solana/web3.js/src/connection.ts:1648:18)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Could you provide launch.json configs for VSCode and I could try debugging further?

You wont be able to run these examples using the public RPCs since we use methods that are disabled, considering using another RPC provider

@wphan could you elaborate a bit here for somebody who is new to Solana and Drift? I also ran into this issue and its a bit unclear to me how these examples are meant to be used in real life scenarios. Do I understand it correctly that the methods used by the Drift SDK is not actually allowed on the mainnet? Could you recommend an alternative RPC provider?

the public RPC endpoint you are using is restricted, recommend you use a dedicated RPC provider https://solana.com/rpc


exit status 1

Hi,
I compiled NAMEinator on ubuntu 18.10 with go1.10.4 linux/amd64
When I try to run it, I the the following result:
marc@thinkpad2:~/go/bin$ ./NAMEinator
starting NAMEinator - version 0.3 alpha
understood the following configuration: {numberOfDomains:100 debug:false contest:true nameserver:}
-------------
NOTE: as this is an alpha - we rely on feedback - please report bugs and featurerequests to https://github.com/mwiora/NAMEinator/issues and provide this output
OS: linux ARCH: amd64
-------------
2019/03/07 12:35:23 exit status 1

any idea?

thanks man - you are abolutely right!
I could verify the issue and observed that the same happens on other distributions with latest updates applied as nslookup no longer reports the used DNS Server to the application.
I will take care of this this weekend.
Cheers,
µ

hi @mlasch
could you please obtain the latest version and test it?
Would be happy about feedback!
// µatthias

hey @mwiora
that was the trick, works nicely.