fix(build): fix release tag env in buildscript

Signed-off-by: Akhil Mohan<EMAIL_ADDRESS>Why is this PR required? What issue does it fix?:
RELEASE_TAG and BRANCH is now passed as a build argument to the buildx container,
so that build script can set the ldflags correctly.
Does this PR require any upgrade changes?:
No
If the changes in this PR are manually verified, list down the scenarios covered::
Any additional information for your reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
Checklist:

[ ] Fixes #
[x] PR Title follows the convention of  <type>(<scope>): <subject>
[ ] Has the change log section been updated?
[ ] Commit has unit tests
[ ] Commit has integration tests
[ ] (Optional) Are upgrade changes included in this PR? If not, mention the issue/PR to track:
[ ] (Optional) If documentation changes are required, which issue on https://github.com/openebs/openebs-docs is used to track them:

Codecov Report

Merging #11 (0551c33) into develop (969fa02) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           develop     #11   +/-   ##
=======================================
  Coverage     0.68%   0.68%
=======================================
  Files           10      10
  Lines          585     585
=======================================
  Hits             4       4
  Misses         581     581

Continue to review full report at Codecov.

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


Create include-fragment-element

@P-DUBB Could you elaborate on what you are trying to accomplish with this change?  It appears to just add an empty file

Based on past activity from @P-DUBB's I'm going to close this one. They can retry if it's genuine.


Preserve tuple information in Function.prototype.apply

Before this change, the overall element type of the array was passed
into all arguments of the target function. This made it impossible to
use apply for functions that took arguments of multiple parameters.
The added ApplyT type holds on to the target FunT until the arguments
array is resolved, and then calls the function. Because we wait for the
arguments array to be resolved, we can pull out the tuple types to use
as parameter types.
Fixes #64

we have a report internally of a similar problem using spreads, e.g.
let args = [0, 'foo', true];
function foo(x: number, y: string, z: boolean) {}
foo(...args);

the apply case already uses a RestT, so I'm wondering if the issue is actually in the way we call any function with a RestT arg, so maybe you could move this change out of the apply case and solve this more generically.

Yeah, it might very well be more useful to carry around the ArrT inside the RestT, or at least carry some kind of tuple information in the RestT itself. I can look into this in the coming days/week.

should we land this one so it makes the next release? seems good, even if we iterate/expand the scope.

If it looks correct on its own, I think the future work we discussed would be backwards compatible. Should be OK to land.

i just saw ArrRestT from your #1098, seems like that might be exactly what you need here?

Hmm. I'm not sure that would solve this problem, but might be useful in the
future work. If you want to hold off to the next release that's OK. There
might well be a more orthogonal feature set here. These two PRs are
admittedly somewhat ad hoc.
On Sun, Nov 15, 2015, 10:10 AM Marshall Roch<EMAIL_ADDRESS>wrote:

i just saw ArrRestT from your #1098
https://github.com/facebook/flow/pull/1098, seems like that might be
exactly what you need here?
—
Reply to this email directly or view it on GitHub
https://github.com/facebook/flow/pull/1104#issuecomment-156849245.

@facebook-github-bot shipit


Approve v2 addition of App.DefaultCommand

What type of PR is this?

cleanup
documentation

Which issue(s) this PR fixes:
related to #1388

The only thing I want to do -- and will work on when able -- before merging into a release is improving test coverage a bit. Some of my changes, while functional and passing tests I threw at them, were reported as uncovered by CodeCov in #1388.

@jalavosus Understood! Are you OK with this pr getting merged ahead of your test coverage? And do you want to set a timeout on your work landing before next release?


Unable to change mappings

I want to map <cr> to restore instead of of yank_additions so have the following setup (with lazy.nvim):
return {
  {
    "telescope.nvim",
    opts = {
      defaults = {
        dynamic_preview_title = true,
        file_ignore_patterns = {
          "yarn.lock",
          "^./.git/",
        },
        vimgrep_arguments = {
          "rg",
          "--color=never",
          "--no-heading",
          "--with-filename",
          "--line-number",
          "--column",
          "--smart-case",
          "--hidden",
          "-g",
          "!.git/*",
        },
      },
      extensions = {
        fzf = {
          fuzzy = true,
          override_generic_sorter = true,
          override_file_sorter = true,
          case_mode = "smart_case",
        },
        undo = {
          use_delta = true,
          side_by_side = true,
          diff_context_lines = 15,
          mappings = {
            i = {
              ["<cr>"] = require("telescope-undo.actions").restore,
              ["<c-cr>"] = require("telescope-undo.actions").yank_additions,
              ["<S-cr>"] = require("telescope-undo.actions").yank_deletions,
            },
          },
        },
      },
      pickers = {
        buffers = {
          show_all_buffers = true,
          sort_lastused = true,
        },
        command_history = {
          theme = "ivy",
        },
        find_files = {
          hidden = true,
          fuzzy = true,
        },
        live_grep = {
          file_ignore_patterns = {
            "yarn.lock",
            "^./.git/",
            "pnpm-lock.yaml",
          },
        },
        lsp_code_actions = {
          theme = "cursor",
        },
        spell_suggest = {
          theme = "cursor",
        },
      },
    },
    dependencies = {
      {
        "debugloop/telescope-undo.nvim",
        config = function()
          require("telescope").load_extension("undo")
        end,
      },
    },
  },
}

But I get the following error:
   Error  17:20:13 notify.error lazy.nvim Failed to load `plugins.telescope`

~/.config/nvim/lua/plugins/telescope.lua:65: module 'telescope-undo.actions' not found:

What am I doing wrong here?
I thought that having telescope-undo.nvim in the dependencies loading the undo extension there should do the trick to allow me to change mappings.

You'll have to move require("telescope").load_extension("undo") into your telescope config. To my knowledge, that is the only way. If you're aware of a telescope plugin that supports your style of doing it, please point me to it :)

Thanks, this works. However, mappings don't seem to change. I still have <cr> mapped to yank_additions.
Another problem, which I should probably open another issue for, is that non of the mapping seem to do what I expect (remapped or not). Can that be because I have clipboard set to unnamedplus?

I have the same clipboard setting, so that should definitely work. It's basically determining the default register from your clipboard setting and using vim.fn.setreg with that. See lua/telescope-undo/actions.lua.
Regarding your mappings: Do you run load_extension after telescope's setup including the extension.undo config part? Because it won't be picked up otherwise. Again, I'm also not a fan of how telescope "centralizes" configuration of its plugins, but I've not been bothered by it enough to look into a different way of achieving it. Let me know if you do and what a telescope plugin can do to support that way of configuration for users :)

That was the issue - I had load_extension before the setup function. Thanks!
I wish there was an option to restore a specific set of changes rather than to a specific set of changes. That would be a killer feature in my opinion. But completely unrelated to this issue :)


detect-only mode

is it possible to only detect the faces inside an image?
(like facedetect does)

@eadmaster Yes, this micro lib is only for images. Face recognition in videos implemented in OpenCV, but I didn't investigate it. Thanks.

I still meant face detection for static images, not videos...

Currently yes - only faces.
Object types declared in PROFILES
Maybe the same algorithm can be used to detect different types of objects - I don't know.


Make Soloud::mix() public

Is there any particular reason to make mix() and mix_signed_16 private? Those are rather useful for a variety of reasons (writing to file, custom backends etc.)

Thanks for quick reply!


remove hardcorded resource, move lukems and naziml images to patle

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[x] I adhere to the Command Guidelines.

View a preview at https://prompt.ws/r/Azure/azure-cli/6349
This is an experimental preview for @microsoft users.

@patricklee2, thanks! Can you fix the lint error and get the CI green for me to merge ?
   W293 blank line contains whitespace

Codecov Report

Merging #6349 into dev will not change coverage.
The diff coverage is n/a.

@@         Coverage Diff         @@
##           dev   #6349   +/-   ##
===================================
  Coverage    0%      0%
===================================
  Files       11      11
  Lines      133     133
  Branches     9       9
===================================
  Misses     133     133

Continue to review full report at Codecov.

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


Feature request: forwards autodifferentiation for gradient computation

Does TensorFlow use forwards instead of reverse (i.e. backprop) autodiff where appropriate?
For graphs with fewer inputs (layer input values plus model parameters) than outputs (as  occurs in convolutional upsampling architectures now popular in GANs and auto-encoders), I believe forwards auto-differentiation will be a faster way to compute gradients. The Jacobian matrices get progressively wider as you go from right to left (up the chain of functions), so if you start multiplying from the right (forwards), rather than from the left (backprop) you reduce the number of operations.
But maybe I'm missing something.

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

[ ] Have I written custom code
[ ] OS Platform and Distribution
[ ] TensorFlow installed from
[ ] TensorFlow version
[ ] Bazel version
[ ] CUDA/cuDNN version
[ ] GPU model and memory
[ ] Exact command to reproduce

Great. Thanks!


similar_text is very slow

https://github.com/kvz/locutus/blob/master/src/php/strings/similar_text.js
works very slow. To compare less than 100 pair of strings (less than 20 chars each) it takes minutes.

Could you provide example code? I'm able to do 84k comparisons a second (more than 20 chars each).
https://jsperf.com/similar-text/1

Thank you for the tests.
I used that function in Imacros javascript. It is clearly Imacros's fault.
2017-03-02 19:35 GMT+02:00 Theriault<EMAIL_ADDRESS>
Could you provide example code? I'm able to do 84k comparisons a second
(more than 20 chars each).
https://jsperf.com/similar-text/1
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kvz/locutus/issues/321#issuecomment-283722981, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACLVRY7uOvFV2fCPjL6FmWBZ5mcdj58Uks5rhv3qgaJpZM4MO5fV
.

I will close the ticket based on above two comments. If the problem is still there, it can be reopened.


Change metadata tracer to use log level INFO instead of DEBUG.

This allows the trace messages to be seen internally, where we don't support DEBUG.

I think the tracer name "metadata" is not properly reflecting what it does.
Some of the tracer blocks are wrapped by #ifndef NDEBUG, do we want to keep them?

Reverting this as per offline discussion.


Remove most remote watches

This PR explores the impact of removing watches and remote watches on k8s core kinds. The goal is to reduce memory footprint and spurious reconciles. I will use this PR to dump info on memory and API server request deltas due to this change.
I suspect this PR will:

Greatly reduce cache memory consumption, since we will no longer be caching all k8s core kinds on remote watch clusters
Reduce spurious reconciles.

I am running tests to evaluate if the above are true.

Scenario
Remote Watches?
Memory
Percent

Simple Migration
Yes
193MiB
100%

Simple Migration
No
104MiB
53%

Simple Migration - Remote Watches Removed (104 MiB memory)

Simple Migration - Remote Watches Enabled (193 MiB memory, 86% increase)

Using this set of queries.

Was reviewing #622 and saw a note I wrote about how the Cancel itinerary triggered a bunch of extra watches since it performs "List()" calls in each namespace. I will profile memory consumption of a migration involving Cancel next.


Surrogate Keys?

Hey André
We're currently using Fastly.com (kind of varnish-as-a-service) on a very heavy traffic website and it's working well for us. What I particularly like is their implementation of surrogate keys to selectively purge related content.
We're considering moving to a hosted version of Varnish. Although Fastly us a forked version of Varnish I think Surrogate Keys are available in Vernish 4.x. Have you looked into them?
https://docs.fastly.com/guides/purging/getting-started-with-surrogate-keys

Interesting, I didn't know about surrogate keys. It's almost like Cache Flag for Varnish. :)
How do you use it with fastly? Do you have a craft plugin for deciding what surrogate keys should be sent pr section, entry type, etc? Or do you just set them from the template? And how is the purge request sent to Fastly with the surrogate keys that you want?

Surrogate keys are set in the templates - a Twig array per template, and then a custom header in the base template to set them in Fastly.
We use a custom plugin to sent purge requests to Fastly's API whenever an element is updated.
So I might have urls such as:
Blog list:  /blog/
Blog detail: /blog/this-is-an-entry-slug
For each page/url on the site I set some surrogate keys in the templates.
On the blog listing I might have something like this:
{% set fastlySurrogateKeys = [
'blog',
'blog-index'
] %}
On the blog detail page I set them like this:
{% set fastlySurrogateKeys = [
'blog',
'blog-index',
'blog-detail',
'blog-detail-' ~ entry.id
] %}
Then in my base layout I set a custom header:
{% header "Surrogate-Key: " ~ fastlySurrogateKeys | join(" ") %}
This means we can be very selective when purging.
We have a plugin that fires a request to the Fastly API when ever an entry is updated.
So for example when a blog entry is updated we tell Fastly to soft purge any objects that have the surrogate keys 'home blog-index blog-detail-xxx' (where 'xxx' is the entry ID).
If you get your surrogate key naming right you get really good control. We can soft purge all blog detail pages by telling fastly to soft purge any objects that have the surrogate key 'blog-detail'. Or we can soft purge the whole blog section using the surrogate key 'blog'.
It looks like Varnish 4.1 has surrogate keys via the xkey vmod:
http://book.varnish-software.com/4.0/chapters/Cache_Invalidation.html
https://github.com/varnish/varnish-modules


Feature request: various q-value filters

First, thank you for a fantastic tool! Just tried it, works great.
I wonder, would it be possible to add options for applying various kinds of filters based on q-values?
Of course, the user can do the filtering before uploading the report, but it would be cool if all was automatic. With DIA-NN applying filters based on global precursor & protein q-values as well as run-specific PTM q-value & potentially site confidence score will usually be beneficial.
One simple way to implement it is by just adding a single textbox where the user can enter filters in a text format, one line per filter, e.g. Global.Q.Value < 0.01. And this is very easily parsed: find '<' or '>' in the string, everything to the left is the column name, everything to the right is the value.
Best,
Vadim

Thanks a lot, Vadim! 😊 I completely agree that it could be quite a useful feature. Thank you for the suggestion! We'll add it in the next release of the tool.


Add tests for theme_extension.1.dart API example.

This PR contributes to https://github.com/flutter/flutter/issues/130459
Description

Adds tests for examples/api/lib/material/theme/theme_extension.1.dart

Pre-launch Checklist

[X] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[X] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[X] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[X] I signed the [CLA].
[X] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[X] I added new tests to check the change I am making, or this PR is [test-exempt].
[X] I followed the [breaking change policy] and added [Data Driven Fixes] where supported.
[X] All existing and new tests are passing.

@Renzo-Olivares, could you please take a look at this PR?

@Renzo-Olivares thanks for the review!

@Renzo-Olivares @gspencergoog could you please tell me why Google testing is failing?

@Renzo-Olivares still failing =(

@ksokolovskyi can you try, assuming you have upstream as one of your remote repos.
git fetch upstream
git rebase upstream/master
git push -f origin myBranch

@Renzo-Olivares @gspencergoog @goderbauer thanks for the review!


Confusing default configuration values

The library assumes that there will exist a default account, and that account must have all properties configured.
In particular I tried to use this configuration:

    'accounts' => [
        'default' => [
            'port' => 993,
            'encryption' => 'tls',
            'validate_cert' => true,
        ],
        'grappling' => [
            'host' => 'mail.example.com',
            'username' =><EMAIL_ADDRESS>            'password' => env('IMAP_GRAPPLING_PASSWORD', null),
        ],
    ],

But in Client::setConfig only configuration properties from the default account will ever be set.
Expected behavior is that all the values from both grappling are used, with default values from default.

Hi @emilv ,
please make sure you published the package config file so it is available in your laravel config folder (config/imap.php) and take a look at the original config file: src/config/imap.php
You can define several accounts inside the accounts array. The default account which is currently placed inside, describes the account which will be used if none is specified.
If you are only using one account you don't have to add any account information inside the imap.php config file, because you can use the env-variables to archive the same.
You usually don't have to use Client::setConfig() at all - only if you want to manipulate configs during the runtime..
Hope I could help :)

I don't care about the default account. The confusion here is that the only config keys you are allowed to set are those that are defined on the default account. Look again on my example. I removed host, username and password from the default account. That makes it impossible to set those same values on the grappling account.

Ah I see. Yes you're right. I will move to a fixed config set - something like this:
public function setConfig(array $config) {
        $defaultAccount = config('imap.default');
        $defaultConfig  = config("imap.accounts.$defaultAccount");

        $availableConfig = ['host', 'port', 'encryption', 'validate_cert', 'username', 'password'];

        foreach($availableConfig as $key){
            $this->$key = isset($config[$key]) ? $config[$key] : $defaultConfig[$key];
        }

        return $this;
}

Hi @emilv ,
I just released a new version which handles the "config setting process" a bit different. Its now based on fixed keys :)
Ref.: v. <IP_ADDRESS>


Pasting text doesn't work on Godot Mobile Version

Godot version
4.0 (latest mobile version)
System information
Android 13
Issue description
This bug is a little frustrating. Whenever I've to paste a script in Godot (Mobile Version)... It doesn't get pasted. Instead, it pastes half of the text and doesn't paste what I exactly copied. I want it to work properly. Whenever I paste something in a script, it should get pasted. Here's a video for the bug:
https://user-images.githubusercontent.com/80309124/223189445-0073228b-e31b-4cdd-9d0d-3e468f0d0570.mp4
In this video. I'm first showing what exactly is the code in the Notes App. Then I go to Godot and paste the same text but it doesn't paste the exact text.
Steps to reproduce
I was unable to figure out what really is going on with it (as it's a Mobile Version)...
Minimal reproduction project
As I told you before :( I've no clue how to solve it.

Duplicate of https://github.com/godotengine/godot/issues/70751
The root cause is the same for both issues.


[VTK] fix FindHDF5.cmake module not recycling targets already defined

What does your PR fix?
Fixes #20038

Which triplets are supported/not supported?

Yes

vtk is a cascade failure and so not tested in CI WTF!
but apart from it, again and again and again and again opencv is not tested anymore in CI (has a dependency on vtk and that's why i noticed it) due to a PR merging from master breaking something somewhere and NOBODY really even noticed it??????
SINCE WHEN???
Again, sorry for the rant, but this is happening TOO OFTEN for me to not be disappointed.
tagging everyone, something has to happen for CI to be considered useful again by me. Something very easy, again please just check if the cascade number of ports is increased by a PR and make it fail if so.
@ras0219 @ras0219-msft @strega-nil @strega-nil-ms @BillyONeal @vicroms @PhoebeHui @JackBoosY @NancyLi1013

#19945 and here it is
this pr just skipped some ports in CI, without any consideration of the "cascade" consequences!

Again, sorry for the rant, but this is happening TOO OFTEN for me to not be disappointed.

#19259 was meant to help, in particular with these cases in mind. But hey, it already has :+1: from @cenit...

This is really a case of the maintainers being stuck with a bunch of bad options. qt5-activeqt and qt5-declarative breaking each other has been a long standing issue, and eventually we got a PR build situation uncovering the real problem: that the qt ports are trying to guess when they will stomp on each other, which makes the results path-dependent. This is #19922 , and it caused all PRs not directly touching any qt parts to fail. The solutions enumerated in #19922 do not look like "can be done quickly" solutions. So our options were:

disable qt5-activeqt (and by extension, its cone of destruction)
allow no other port to be updated in vcpkg until qt5 is fixed

and given that we already had let many contributors wait for weeks, we chose the former. I don't believe we will ever truly end up in a situation where we wouldn't have made a similar decision; there are actions we want to take resulting from this feedback but none would really change the outcome in this particular case, although it would in other cases.
Actions that we are going to take from this:

We have fast tracked review of @dg0yt's PR #19259 which would have printed the cone of destruction in this example. Thank you @dg0yt for your contribution! That would have let you know quickly here that this PR edits a port that is currently a cascaded failure.
@ras0219 / @ras0219-msft has signed up to fix qt in a less correct way than described in #19922 (it will waste disk space) but which will restore the unique port attribution rule.
We are going to add logging of the count of "cascades at the top" -- those that result from ci.baseline.txt and "supports" -- and keep track of this as an important metric in CI.
We are going to add validation for the preceeding number and fail PRs if the number of cascades change. Then at least git blame will find PRs that had to make significant edits here.

Actions we want to do in the future:

We would like all cascades to be in ci.baseline.txt rather than locking to a number, but this would require better understanding of ci.baseline.txt inside vcpkg.exe than we have right now, and we want to roll something out which improves the situation ASAP.

We apologize that the situation has left you with a bad experience and hope you can bear with us trying to make the situation better.

I also further discovered that similar fixes will also need to be applied to LZ4 and PEGTL. See below CMakeLists.txt with two find_package(VTK REQUIRED) that will trigger it.
set(CMAKE_TOOLCHAIN_FILE $ENV{VCPKG_ROOT}/scripts/buildsystems/vcpkg.cmake)

cmake_minimum_required(VERSION 3.20)

project(example)

find_package(VTK REQUIRED)
find_package(VTK REQUIRED)

Below error will show up:
-- Selecting Windows SDK version 10.0.18362.0 to target Windows 10.0.19043.
-- Searching for PEGTL
-- Searching for PEGTL - found target taocpp::pegtl
-- Found LibXml2: C:/dev/vcpkg/installed/x64-windows/debug/lib/libxml2.lib (found version "2.9.12")
-- Found Eigen3: C:/dev/vcpkg/installed/x64-windows/include/eigen3 (found version "3.3.9")
-- Found TIFF: optimized;C:/dev/vcpkg/installed/x64-windows/lib/tiff.lib;debug;C:/dev/vcpkg/installed/x64-windows/debug/lib/tiffd.lib (found version "4.3.0")
CMake Error at C:/dev/vcpkg/scripts/buildsystems/vcpkg.cmake:574 (_add_library):
  _add_library cannot create ALIAS target "hdf5::hdf5" because another target
  with the same name already exists.
Call Stack (most recent call first):
  C:/dev/vcpkg/installed/x64-windows/share/vtk/patches/99/FindHDF5.cmake:5 (add_library)
  C:/dev/vcpkg/installed/x64-windows/share/hdf5/vcpkg-cmake-wrapper.cmake:17 (_find_package)
  C:/dev/vcpkg/scripts/buildsystems/vcpkg.cmake:738 (include)
  C:/dev/vcpkg/installed/x64-windows/share/vtk/VTK-vtk-module-find-packages.cmake:256 (find_package)
  C:/dev/vcpkg/installed/x64-windows/share/vtk/vtk-config.cmake:136 (include)
  C:/dev/vcpkg/scripts/buildsystems/vcpkg.cmake:784 (_find_package)
  CMakeLists.txt:37 (find_package)

CMake Error at C:/dev/vcpkg/scripts/buildsystems/vcpkg.cmake:574 (_add_library):
  _add_library cannot create ALIAS target "hdf5::hdf5_hl" because another
  target with the same name already exists.
Call Stack (most recent call first):
  C:/dev/vcpkg/installed/x64-windows/share/vtk/patches/99/FindHDF5.cmake:14 (add_library)
  C:/dev/vcpkg/installed/x64-windows/share/hdf5/vcpkg-cmake-wrapper.cmake:17 (_find_package)
  C:/dev/vcpkg/scripts/buildsystems/vcpkg.cmake:738 (include)
  C:/dev/vcpkg/installed/x64-windows/share/vtk/VTK-vtk-module-find-packages.cmake:256 (find_package)
  C:/dev/vcpkg/installed/x64-windows/share/vtk/vtk-config.cmake:136 (include)
  C:/dev/vcpkg/scripts/buildsystems/vcpkg.cmake:784 (_find_package)
  CMakeLists.txt:37 (find_package)

-- Searching for PEGTL
-- Searching for PEGTL - found target taocpp::pegtl
CMake Error at C:/dev/vcpkg/scripts/buildsystems/vcpkg.cmake:574 (_add_library):
  _add_library cannot create ALIAS target "PEGTL::PEGTL" because another
  target with the same name already exists.
Call Stack (most recent call first):
  C:/dev/vcpkg/installed/x64-windows/share/vtk/FindPEGTL.cmake:27 (add_library)
  C:/dev/vcpkg/scripts/buildsystems/vcpkg.cmake:784 (_find_package)
  C:/dev/vcpkg/installed/x64-windows/share/vtk/VTK-vtk-module-find-packages.cmake:491 (find_package)
  C:/dev/vcpkg/installed/x64-windows/share/vtk/vtk-config.cmake:136 (include)
  C:/dev/vcpkg/scripts/buildsystems/vcpkg.cmake:784 (_find_package)
  CMakeLists.txt:37 (find_package)

-- Found LibXml2: C:/dev/vcpkg/installed/x64-windows/debug/lib/libxml2.lib (found version "2.9.12")
CMake Error at C:/dev/vcpkg/scripts/buildsystems/vcpkg.cmake:574 (_add_library):
  _add_library cannot create ALIAS target "LZ4::LZ4" because another target
  with the same name already exists.
Call Stack (most recent call first):
  C:/dev/vcpkg/installed/x64-windows/share/vtk/FindLZ4.cmake:3 (add_library)
  C:/dev/vcpkg/scripts/buildsystems/vcpkg.cmake:784 (_find_package)
  C:/dev/vcpkg/installed/x64-windows/share/vtk/VTK-vtk-module-find-packages.cmake:1055 (find_package)
  C:/dev/vcpkg/installed/x64-windows/share/vtk/vtk-config.cmake:136 (include)
  C:/dev/vcpkg/scripts/buildsystems/vcpkg.cmake:784 (_find_package)
  CMakeLists.txt:37 (find_package)

-- Found TIFF: optimized;C:/dev/vcpkg/installed/x64-windows/lib/tiff.lib;debug;C:/dev/vcpkg/installed/x64-windows/debug/lib/tiffd.lib;optimized;C:/dev/vcpkg/installed/x64-windows/lib/lzma.lib;debug;C:/dev/vcpkg/installed/x64-windows/debug/lib/lzmad.lib;optimized;C:/dev/vcpkg/installed/x64-windows/lib/jpeg.lib;debug;C:/dev/vcpkg/installed/x64-windows/debug/lib/jpegd.lib;optimized;C:/dev/vcpkg/installed/x64-windows/lib/zlib.lib;debug;C:/dev/vcpkg/installed/x64-windows/debug/lib/zlibd.lib (found version "4.3.0")
-- Configuring incomplete, errors occurred!
See also "C:/Users/jasju/Desktop/test/build/CMakeFiles/CMakeOutput.log".
See also "C:/Users/jasju/Desktop/test/build/CMakeFiles/CMakeError.log".

@cenit There are plenty of signoffs now, do you want to land this now or do you want to wait until the qt5-activeqt situation is resolved?

i did the fix in this PR because tagged by @JackBoosY in the issue but i am not the author of the original broken patches nor because i was hit by the problem.
@jasjuang just uncovered another similarly broken patch also in vtk, let me just fix that too because it really belongs to this PR (i'll do that asap).
Not a problem for me to wait for a proper fix. Maybe @jasjuang can use vcpkg from this PR in the meantime and verify that the issue is properly solved?

@cenit I can confirm the current PR solves the
find_package(OpenCV REQUIRED)
find_package(VTK REQUIRED)

scenario.

@jasjuang if you have time, please check again, it should contains fixes for all your reported problems

@cenit I can confirm that your latest push solves the
find_package(VTK REQUIRED)
find_package(VTK REQUIRED)

scenario. Thanks.

FYI, the "cascades" enforcement enumerated above is in progress at: https://github.com/microsoft/vcpkg/pull/20140

Thanks for your fix!

Count enforcement of "cascade" is landed.

Unfortunately we were forced to back out enforcement of "cascade" due to "stealth merge conflicts". See further discussion in https://github.com/microsoft/vcpkg/discussions/20180


error when building variant-lite

The outputs are as follows:

I'll investigate. Thanks.

As my issue is similar to issue 32, I leave a comment there asking how he fixed it. But I didn't got '-std=c++17' and my gcc version is 12.2.0.
Later I read issue93 and I think maybe the reason I got the error log is because I installed libsodium on my own. So I follow your advice. But I still got exactly the same error log as above.

I don't think it's related to those...
My guess is that the when_all_ready header need to #include
Can you try that?

Sorry, could you be more specific? Thanks.

So you see the file that the compiler is saying that std::exchange doesn't exist? macoro/when_all.h
Add #include <utility> to the top and try to compile

Thanks for your help.
I succeeded in building variant-lite following your guide, and then I encountered a similar error log which says std::exchange doesn't exist several times. Each time I add #include <utility> at the top of the corresponding file.
Now I build the whole project successfully.
: )

First of all variant wasn't the issue. Macoro was.
Can you remember where these other errors were? I need to fix them. Unfortunately I don't get these errors on my machine so need your belp
Thanks

Much appreciated. I'll send out a fix soon.


[feature]an website for chainzRegistry

Is your feature request related to a problem? Please describe.
I'm always frustrated when I'm unable to find clear and concise information about the functionalities and features of the ChainzRegistry repository. Users, including myself, often need a comprehensive resource to understand what ChainzRegistry does and how to use it effectively.
Describe the solution you'd like
I would love to create a dedicated website for the ChainzRegistry repository. This website will provide detailed explanations about the functionalities, features, and usage of ChainzRegistry. It will serve as a one-stop resource for both new and experienced users to get the most out of ChainzRegistry.
You can access the website at jaibhedia.github.io/chainzRegistry.
Additional context
The website will include:

An overview of ChainzRegistry and its purpose.
Detailed documentation on how to use various features.
Examples and tutorials for common use cases.
A FAQ section to address common questions and troubleshooting tips.
Links to the repository, issue tracker, and other relevant resources.

This will not only help current users but also attract new users by providing a clear and structured presentation of what ChainzRegistry offers.

Hey @jaibhedia can u please create an branch named gh-pages?

HELLO @jaibhedia CAN YOU PLEASE CREATE AN BRANCH NAMED GH-PAGES


chore(schema): Add complete OpenAPI schema definition

Issue
When I tried to extend the openapi as explained on the docs, some properties, like security weren't available in the OpenAPI JSON $schema definition, causing a warning on my IDE:

I can also see this issue on the console:
err: {
      "type": "Error",
      "message": "must be boolean {\"type\":\"boolean\"}\nmust NOT have additional properties {\"additionalProperty\":\"security\"}\nmust NOT have additional properties {\"additionalProperty\":\"components\"}\nmust match a schema in anyOf {}",
      "stack":
          Error: must be boolean {"type":"boolean"}
          must NOT have additional properties {"additionalProperty":"security"}
          must NOT have additional properties {"additionalProperty":"components"}
          must match a schema in anyOf {}
              at DBConfigManager.parseAndValidate (/fastify-poc/node_modules/@platformatic/config/index.js:179:13)
              at async FileWatcher.<anonymous> (/fastify-poc/node_modules/@platformatic/config/index.js:67:9)
    }

Solution
I picked up the official OpenAPI schema definition and inserted into our schema.js generation logic.

@mcollina all tests are passing locally:

But the prompt suggested adding happy-dom, to make them pass...
Let me know if you want me to add it to this PR 😉

could you rebase? We had a few fixes along the way to make the CI green.

@mcollina done, but there is still a timeout error...

There is an actual bug in your PR: https://github.com/platformatic/platformatic/actions/runs/4427773809/jobs/7767085077#step:11:746


Switch to reqwest::blocking

Seems to work :)
How to use
Agree if we want to use this
Testing done
Downloading with a direct URL and with the XML works. I also checked that the download is done to disk and there is no copy in RAM (/usr/bin/time -v shows the Maximum resident set size to be 24 MB for the full Flatcar update payload which is 370 MB).

Can we please tokio and its dependencies, as they are not needed any more?

Yes, have removed Tokio as direct dependency but it is still used by reqwest.


Refactor testing to use the data structure directly

In this PR I'm splitting out most of the functionality of the plugin's run() method into a new method, _generate(), which returns the data structure corresponding to the contents of the pyproject.toml file but without actually writing it out as TOML. I've also modified the test infrastructure to give access to the return value of this method directly, through the new Project.generate() wrapper, so we can run tests without going through an unnecessary (ish?) round of writing the structure to TOML and then reading it back in.
I also copied all the existing tests but changed them to use this new generate() method.  I think we can safely get rid of many of the original tests and just keep a few to make sure the whole process works, but most of our testing from now on can probably be done by using generate(). As I create this PR I'm not yet sure which/how many of the original tests it makes sense to remove, but we'll figure that out. @sjlongland I'd appreciate your thoughts on this.

I still have a bit of work to do to fix mypy's complaints about assignments to pyproject... I'm working on that. But other than the type annotations this should be ready.

Yeah, that would remove a source of potential test failures.  It'd still be worth keeping a test that ensures that valid TOML is emitted regardless, but we'd then be able to make it just one single test and not multiple like we have now.

Yay, I finally managed to satisfy mypy :grin: It was a bit tricky in this case.
@sjlongland Any thoughts about which of the original tests in test_setup_command.py we should keep to ensure that valid TOML is emitted? Personally, I'm thinking that it makes sense to keep one very basic test that emits a minimal pyproject.toml (like, just the project name or something), and one test that is as comprehensive as possible, emitting all the fields we have defined - of course we should keep updating that test as we add support for new fields. And honestly I'm not even sure of what sort of problem the basic test would detect; it's just my instinct that it might be useful to have as an edge case. :shrug: Let me know if you think there are other cases that would be useful to keep, and I'll push a commit that removes the ones we don't need. Or you could push that commit yourself, if you prefer.

Yay, I finally managed to satisfy mypy grin It was a bit tricky in this case.
@sjlongland Any thoughts about which of the original tests in test_setup_command.py we should keep to ensure that valid TOML is emitted?
Personally, I'm thinking that it makes sense to keep one very basic test that emits a minimal pyproject.toml (like, just the project name or something), and one test that is as comprehensive as possible, emitting all the fields we have defined - of course we should keep updating that test as we add support for new fields.

test_name_and_version seems the simplest… the others are testing the logic in behind the generation of the data that is transformed to TOML, so would be good candidates to be re-worked to call the underlying generate() function.
I don't think there's one that emits everything yet.

And honestly I'm not even sure of what sort of problem the basic test would detect; it's just my instinct that it might be useful to have as an edge case. shrug Let me know if you think there are other cases that would be useful to keep, and I'll push a commit that removes the ones we don't need. Or you could push that commit yourself, if you prefer.

True, and if we keep the serialisation routine as dumb as possible, we're realistically not testing our own code, we're testing tomlkit, which should have its own tests.
Another approach is the call to tomlkit is its own method, which in unit tests, we stub and is itself excluded from test coverage (as we keep it "trivial").  That way, we just test what we feed into tomlkit, and we assert whatever we return from the stub, is processed correctly by the calling function.
It comes down to how much you trust the upstream project to be consistent in their output. :-)

test_name_and_version seems the simplest… the others are testing the logic in behind the generation of the data that is transformed to TOML, so would be good candidates to be re-worked to call the underlying generate() function.

Makes sense. I'll push a commit that removes the others.

I don't think there's one that emits everything yet.

Yeah, I mean we haven't implemented support for most of the fields but I think there should be one test that emits all the fields we do have support for, and as we add support for new fields we just keep expanding the scope of that test. Sorry if I wasn't clear about that.

True, and if we keep the serialisation routine as dumb as possible, we're realistically not testing our own code, we're testing tomlkit, which should have its own tests.

My thoughts as well :+1:

Another approach is the call to tomlkit is its own method, which in unit tests, we stub and is itself excluded from test coverage (as we keep it "trivial"). That way, we just test what we feed into tomlkit, and we assert whatever we return from the stub, is processed correctly by the calling function.
It comes down to how much you trust the upstream project to be consistent in their output. :-)

Hmm, interesting idea. I hadn't thought of that. I do think it makes the test code a little more complicated to follow, though probably not enough to be a big deal. FWIW I do trust tomlkit's output to be stable over the long term; or if it's not, we can probably adjust for that (if nothing else by parsing the output as you implemented before), but bypassing tomlkit entirely does save us that particular bit of effort.


Change Draco modules to be created asynchronously

In general Draco npm modules have always been created asynchronously. But in gltf-pipeline they worked usually with getting created synchronously.
We are planning to release Draco 1.4.0, which uses a new version of emscripten and causes gltf-pipline to fail as the timing has changed.
The change in this PR makes it so the current version of the Draco npm modules work and it will work when 1.4.0 is released.
The question is is there a better way to create the Draco modules asynchronously in gltf-pipeline?

@lilleyse Any issue with this PR? We want to release a new version of Draco as soon as we can and we really don't want to break gltf-pipeline.

@FrankGalligan I tried out another approach that's more self-contained in compressDracoMeshes but I'm constantly getting Maximum call stack size exceeded not matter what I try. Could you take a look if I'm doing anything wrong? https://github.com/CesiumGS/gltf-pipeline/compare/draco-async?expand=1

@lilleyse Your branch worked for me using Draco 1.3.6 (the current version). Also I think I created a PR by mistake #562

@lilleyse I can reproduce the error you are seeing with Draco 1.3.6.
I had the newer modules when I was testing before. So your code works with the next release of Draco npm modules but doesn't work with Draco npm 1.3.6
I will see if I can debug what is going on with 1.3.6

@lilleyse Unfortunately I really only program in JavaScript to make changes to gltf-pipeline, so my experience is very minimal.
I can see it gets into this function and returns:
https://github.com/CesiumGS/gltf-pipeline/blob/draco-async/lib/compressDracoMeshes.js#L58
Then it tries to run compress stage and then it breaks. From the error message it looks like you might have an infinite recursion.
Can the promise just keep creating another promise?

The infinite recursion seems to be some strange interaction between the promise and the Draco module internals, and I can't seem to figure out why.
But if it's working in 1.4.0 then I can publish a gltf-pipeline release locked to 1.3.6 and then publish a new release once 1.4.0 is out. If that sounds good I'll go ahead with the first release.

@FrankGalligan now that https://github.com/CesiumGS/gltf-pipeline/pull/563 is merged you can go ahead and release Draco 1.4.0

Fixed in https://github.com/CesiumGS/gltf-pipeline/pull/562


Make model_id configurable for Llama2-c example

As stated above, this PR resolves a TODO comment by adding another command-line parameter to the eval command.

@LaurentMazare, what do you think of this PR? Do you think it is necessary?

@LaurentMazare, what do you think of this PR? Do you think it is necessary?

I don't think this adds much and I would even think that it may break the existing code if I'm not mistaking. The dataset was coming from roneneldan/TinyStories and after that it seems to come from karpathy/tinyllamas which I wouldn't think has the data. Maybe I'm missing something here, not sure how much testing was done. Anyway i think it would be great if you want to transform this example into a full replication of Karpathy's awesome work on tinyllama but this likely belongs to an external repo. Happy to link to it if you put something into place that works well.

Ok, sounds good. I suppose the default value for model_id should have been roneneldan/TinyStories. Regardless, I will look into making an example of tinyllama. Thanks!


Goroutines do not increase performance

Hi,
I'm unsure if this is an actual issue, or if this is just a side effect from how LevelDB is structured.
It seems that there is no speed increase when reading the database via multiple goroutines. I'm specifically just calling a new Iterator within the goroutines to read data based on key prefixes.
Here are the results from a quick test on some data.
With goroutines:
Loading database...
Done loading
Time start: 2016-11-07 23:40:44.796366138 +0000 UTC
Total: 94
Total: 114
Total: 261
Total: 1693
Total: 1781
Total: 2311
Total: 2357
Total: 2579
Total: 2915
Time end: 2016-11-07 23:40:56.571844079 +0000 UTC
Total time: 11.775478016 seconds

Without goroutines:
Loading database...
Done loading
Time start: 2016-11-07 23:43:38.458591384 +0000 UTC
Total: 94
Total: 114
Total: 2311
Total: 2579
Total: 2357
Total: 2915
Total: 261
Total: 1693
Total: 1781
Time end: 2016-11-07 23:43:49.349130386 +0000 UTC
Total time: 10.890539008 seconds

I also noticed while running the top command on a separate shell, that even though there's no speed increase when using goroutines, the memory used by the application does increase significantly.
Let me know if I can provide any further details to help, and thank you for your work on this!

It would be much more slower since it will generates more seeks (random IO is typically slower that sequential one) and cache miss.

Another question on this, is it possible to create multiple snapshots and have those snapshots read from the database concurrently?
My main concern is how reads don't seem to be concurrent. For instance, if I'm running a web server and an endpoint reads from the database, what happens when there's 100's of requests per second? It seems that, unless snapshots can be read concurrently, each request will happen synchronously.

Sure, you can create multiple snapshot, but you don't need to create snapshot to read the database concurrently. Remember, concurrency is not parallelism.

What I mean is though, in my original post you can see that reading the database concurrently does not actually seem to do so, i.e. even using multiple goroutines to read the database, it actually performs worse than just reading from the database in a single goroutine one by one.
What I'm picturing is for instance, using the example from my original post, calling call 9 of those database reads and all 9 complete in 2915 ms (the longest single read). The way it seems to work now, is it does it one by one, so the total time for all 9 reads is 11,775 ms.

Okay, let's use goroutine as example, so you want to performs calculation concurrently on let's say 4 goroutines, but you only have single CPU core, then what happen. The calculation will be scheduled on that single CPU core, it doesn't automagically become 4 times faster than when you execute the computation in sequence. Concurrency is about dealing with lots of things at once, hence concurrency is not parallelism, which is doing lots of things at once.
Doesn't matter if you doing it sequentially on concurrently, the data still need to be pulled from the disk, the main bottleneck here is the disk. Also, random IO is typically much slower than sequential IO, even on SSD, and reading the different parts (well, if you read from a same parts concurrently, then the chance of cache hit would be much greater, so it will be pulled from cache instead of disk, hence more performant) of database concurrently means pulling multiple files at once, which means random IO, hence much slower, also concurrency is not free, it has its own overhead.

Thank you for explaining it further, I think I understand it now. So even if you have 2 goroutines for instance reading 2 different sections of the database, if both of those reads are happening on the same logical core, then the wait is inevitable because the wait is the time it takes for the one goroutine to pull the data it needs from disk? I.e. there is no 'waiting' or 'pausing' so the other goroutine will not run until the first is complete?
Do you think this could be solved by increasing the number of CPUs and having it run in parallel?

In leveldb case the bottleneck is the disk, not the CPU. So you need faster
disk.
On Sun, Dec 18, 2016 at 6:23 PM beeker1121<EMAIL_ADDRESS>wrote:

Thank you for explaining it further, I think I understand it now. So even
if you have 2 goroutines for instance reading 2 different sections of the
database, if both of those reads are happening on the same logical core,
then the wait is inevitable because the wait is the time it takes for the
one goroutine to pull the data it needs from disk? I.e. there is no
'waiting' or 'pausing' so the other goroutine will not run until the first
is complete?
Do you think this could be solved by increasing the number of CPUs and
having it run in parallel?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/syndtr/goleveldb/issues/158#issuecomment-267815878,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAscrT1So7QXSMMmnn4_CmhqwfrP9dtGks5rJRejgaJpZM4Kr3Sp
.

So if better/parallel read performance is required, do you think it would be legitimate to just replicate the data onto multiple machines, and then create a sort of frontend load balancer that chooses an available machine out of the pool?
I'm using Google Compute Engine so while I could attach a Local SSD or just increase the space for higher IOPS, I'm thinking it would be cheaper to just run a bunch of smaller instances, each with just enough disk space to hold the data.

Also you can try to increase the cache capacity.

Ok cool, thank you so much for your time and input on this, and especially for your work on LevelDB, I truly appreciate it!


How do I know the previous stroke and the next stroke？

How do I know the previous stroke and the next stroke？
for example：
Click the previous stroke to display the previous stroke，Not all of the strokes are shown

You can do same as below:
  animationWriter = HanziWriter.create('animation-target', "我", {
    width: 300,
    height: 300,
    showOutline: shouldShowOutline('animation'),
    showCharacter: false
  });

totalStroke = animationWriter._character.strokes.length

animationWriter.animateStroke(0)
animationWriter.animateStroke(1)
animationWriter.animateStroke(2)
...
animationWriter.animateStroke(totalStroke  -1 )

@chanind  is right? Thanks very much.

I think it is a good idea that ad preStroke and nextStroke for HanziWriter instance.  @chanind

What you wrote should work @yxxhero, but it's awkward because animationWriter._character might be null until the character data can load successfully. I think it makes sense to add a new method to get the current character as a promise, like animationWriter.getCharacter(). Adding a animateNextStroke() method or something similar is interesting too, I can see it being useful to make it easier to animate characters by clicking a button. animatePreviousStroke() is tricky though - would that remove the current stroke that's drawn first before animating the previous stroke?  I think for the previous stroke case it might be better to use animateStoke(strokeNum) explicitly to make things clear. I'll work on a PR for this!

Thanks your answer.  In the chrome console, animationWriter._character is ok, but in the nodejs, it is not ok.  why??? @chanind  thanks very much.

animatePreviousStroke() is tricky though - would that remove the current stroke that's drawn first before animating the previous stroke?
Yes

It might be that _character is null at first because the writer hasn't finished loading the character data yet. I'm hoping adding a proper method to get the character will solve that problem

Thanks very much! 太谢谢您了，感谢您百忙之中能回复。@chanind

v3.1.0 adds a writer.getCharacterData() method that you can use to get the contents of writer._character after the data has loaded. The method returns a promise which will contain this data. For instance, you could do:
const character = await writer.getCharacterData();
const numStrokes = character.strokes.length;

Hopefully this should make it easier to work with character data in both node and browser!

Thanks very much!


Make all tables in console to be sortable

From chicchiricco on October 12, 2010 12:22:48
Make every header element in tables to be clickable; this action will result in the table elements to be ordered on that column basis. A second click will revert the order.
Original issue: http://code.google.com/p/syncope/issues/detail?id=58

From<EMAIL_ADDRESS>on October 13, 2010 09:06:08
Status: Started

From<EMAIL_ADDRESS>on October 20, 2010 05:44:28
Status: Fixed


Agent unexpectedly deleting queues

I am running a scripted test that creates sequentially numbered pooled queues in a loop.   I am noticed that after about 1200 queues, the agent log reports that queues (and auto links) are being deleted.  When this occurs I am seeing many queues revert to a .status.isReady = false.
The address-plan-pooled-queue had been altered  so requiredResources for broker and router were 0.005.  No messages were being sent to the queues.
Here's one example:
2018-10-12T14:57:38.046Z agent info [broker-pooled-i6zbsyu6xh-5] Creating queue "b187"...
...
2018-10-12T14:57:43.396Z agent info [broker-pooled-i6zbsyu6xh-5] Deleted queue "b187"
..
2018-10-12T14:57:43.936Z agent info deleted autolink in b187 on qdrouterd-i6zbsyu6xh-2
2018-10-12T14:57:43.936Z agent info deleted autolink out b187 on qdrouterd-i6zbsyu6xh-2
I am seeing this for many addresses.
agent.log

From log:
addresses_ready: added ["b192","b194","b196","b198","b200"], modified ["b187"]
I think it is whatever causes the agent to believe the definition of b187 has changed which then prompts the deletion. Is it possible the broker it is allocated to is changing?

Also:
2018-10-12T15:03:45.155Z agent info addresses_ready: added ["b641"], modified ["b467"]
2018-10-12T15:03:45.487Z agent info [broker-pooled-i6zbsyu6xh-8] Creating queue "b467"...
2018-10-12T15:03:45.559Z agent info [broker-pooled-i6zbsyu6xh-7] Deleting queue "b467"...
2018-10-12T15:03:45.952Z agent info [broker-pooled-i6zbsyu6xh-7] Deleted queue "b467"
2018-10-12T15:03:45.997Z agent info [broker-pooled-i6zbsyu6xh-8] Created queue "b467"
Which would match the theory that the queue is being reallocated.

@k-wall a change that might shed further light on whether the theory above holds: https://github.com/EnMasseProject/enmasse/pull/1785

@grs - reproduction with additional logging #1785
agent_20181015.log

This is a race condition.  In the problematic case AddressController#onUpdate acts on an address whose state is stale in the FifoQueue#store.    This means that the address is treated as if they were Pending when in actual fact they have already been moved to Configuring by a previous invocation of AddressController#onUpdate.  This then causes the Agent the assign address to a new broker.   (as testified by the logging added by #1785).
The store is updated either by incoming watch notifications or a periodic resync.   When the store is updated by a watch notification, this triggers AddressController#onUpdate on a different thread, passing the current state of the whole store.  If many addresses are being created concurrently, this opens the possible where an update to address A causes the AddressController#onUpdate` to see stale address B, simply because the notification for B has not hit the store yet.
The problem is most likely to be seen when creating many addresses concurrently.
some of which have stale states.
The issue is that the FifoQueue#store can  stale.   The store is updated either by incoming watch notifications or a periodic resync.  If many addresses are being created concurrently
I see the race occurring when there a system has many hundreds or thousands of addresses though I think the issue could occur with smaller number of addresses.
The sequence of the events is:

AddressController#onUpdate provisions resources for a new address and updates the address AddressApi#replaceAddress.

The AddressController#onUpdate is passed a set


Confuse to link this page to "A conceptual overview of this feature is available in Cluster extensions - Azure Arc-enabled Kubernetes article"

I wonder if this feature will only be supported by Azure Arc-enabled Kubernetes  or will be supported by the managedCluster

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

ID: 78b10581-fc01-7ae0-ef90-81d754d2f560
Version Independent ID: 01ee8215-7cb9-6588-b715-8ae12d95e88a
Content: Cluster extensions for Azure Kubernetes Service (AKS) - Azure Kubernetes Service
Content Source: articles/aks/cluster-extensions.md
Service: container-service
GitHub Login: @Nickomang
Microsoft Alias: nickoman

@showpune
Thanks for your feedback! We will investigate and update as appropriate.

@showpune
Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can take a look at it accordingly.
@Nickomang
Can you please check and add your comments on this doc update request as applicable.

Hi @showpune -
First of all, I apologize for the long time to respond. Thanks for sharing your feedback. There have been updates to this page and the linked page since the time you left your feedback. The linked page provides an overview of how extensions work, which is not limited to extensions on Arc-enabled Kubernetes clusters. The list of available extensions for AKS clusters is on the original page at https://learn.microsoft.com/en-us/azure/aks/cluster-extensions#currently-available-extensions
I'm going to close this issue now, but please let us know if you have additional feedback or if anything is still not clear. Thanks again for taking the time to help us improve the docs.
#please-close


set baudRate with 256000,but the results of payload is different

the results of payload in android is different

in assistant of Serial
the results:
[[11:01:54.625] ] 7E 10 00 3A 02 00 00 7E
[[11:01:55.125] ] 7E 10 00 44 02 00 00 7E
[[11:01:55.626] ] 7E 10 00 4E 02 00 00 7E
[[11:01:56.126] ] 7E 10 00 58 02 00 80 7E
in android
the value of payload:
FCFEF0003COOOOOOF8FE
Are there any settings that need to be changed? Except baudRate


XboxLiveUser.User.Privilege in Unity editor

XboxLiveUser.User.Privilege will return null when tested in Unity Editor. It's worth mentioning that in the documentation, or amending Unity Xbox Live plugin.
Overall instructions how to test privileges would be very useful here.

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

ID: 4b31d99e-6d2d-2920-46f4-70113c928e04
Version Independent ID: dab334e9-d385-1946-ed23-5fb94acca7b7
Content: Check user privilege settings in Unity - UWP app developer
Content Source: windows-apps-src/xbox-live/get-started-with-creators/check-user-privileges-in-unity.md
Service: unspecified
GitHub Login: @staceyhaffner
Microsoft Alias: sthaff

You are correct.  The Unity editor does not actually connect to the Xbox Live service and uses fake data to simulate a connection, thus you will currently get a null response. In order to test with real data, you will need to export your game to Visual Studio and test as described in https://docs.microsoft.com/en-us/windows/uwp/xbox-live/get-started-with-creators/test-visual-studio-build.
I will update the topic to reflect this.


Add breadcrumbs functionality

It'd be cool if the extension showed the current directory you were in at the top of the tree using the vscode breadcrumbs. It could be tied to the breadcrumbs setting in vscode so people that don't have breadcrumbs on wouldn't have to see it.

I can try and do a PR for this, just don't want to take the time if it's not something you'd be interested in merging

@jtmkrueger I'm not against this feature (although I don't personally use breadcrumbs, so it's not a high priority) but I would actually be surprised if vscode gives you an extension API for controlling this bit of UI.
If the code required for setting them is minimal, then I'd happily merge the PR, but before you set off implementing can you send the links to the docs for the API for interacting with the breadcrumbs from an extension codebase?

I was going to research how the vscode module's breadcrumbs api works. You're probably right, but I didn't wanna dig in on anything if it wasn't something you'd accept PR's for.
(Really digging the extension thanks for making it! I use it with the VSCode Neovim extension and it was super easy to set up.)

I actually don't use breadcrumbs in my editor tabs either but I think it might be helpful here.


Importing a SCSS file into a Scss file with indented syntax is no longer working

Version
3.0.0-rc.11
Node and OS info
Node v9.11.2, Yarn 1.9.4, macOS 10.13.6
Steps to reproduce
Install this simple test-case and run yarn serve:
https://github.com/rhinel/vue-cli-issue-scss-import-scss
What is expected?
In projects created with Vue CLI 3-rc-10, these @import statements were working without problems.
this result like this:
#nav {
  padding: 30px;
}
#nav a {
  font-weight: bold;
  color: #2c3e50;
}
#nav a.router-link-exact-active {
  color: #42b983;
}

What is actually happening?
the result like this:
#nav {
  padding: 30px;
  a {
    font-weight: bold;
    color: #2c3e50;
    &.router-link-exact-active {
      color: #42b983;
    }
  }
}

thanks.

Why are you using url() for @import? @import './assets/reset.scss' works just fine.

ok, sorry, url() works fine in 3.0.0-rc.10 and before version ...

It worked by accident - you should not be using url() when importing scss files.

ok, thanks.


Keeps the hash same for parent and child compilation

fixes #15

this is 2 things in 1 pr, or is the aliasing required for the hash thing?

woops my bad

yeah i added two things in one branch

opening other one with one feature at a time

also for aliasing modules, @developit has a better PR


Is this plugin affecting fastify's performance?

Not exactly.
This plugin connects Fastify with Zod. So, the performance impact will be the same as verifying something with a Zod schema.
If you have some performance problem in your schema, you will have performance problems with Fastify, but not directly because of fastify-type-provider-zod

How would you skip the validation in production mode if you wanted to avoid the performance impact?

I took a look at the project, and it is using JSON.stringify, fastify uses its own implementation: https://github.com/fastify/fast-json-stringify which might have some impact in certain scenarios.

@filipesarturi fair point, makes sense to replace


Must C has 2 versions

Must C has 2 versions right know i wanna ask which version did you trained your model.

Oops there are 4 different versions 1, 1.1, 1.2, 2

There are only one with tr my bad

v1.2


design ordering policy execution

https://github.com/stolostron/backlog/issues/25611
this is a draft, feel free to add some review! want to wait until @JustinKuli gets back next week to finalize anything.

/cc @JustinKuli

@gparvin @JustinKuli I think I should be done with the changes, anything else I should change/add?

Thanks to everyone who contributed in the sync call! Feel free to add any other comments. We discussed adding the following changes to the doc:

should the compliance field be made optional? we decided to keep it
should policy sets be ordered instead of basing ordering around policy dependencies? we decided to keep the current approach as it allows for more flexibility
should a namespace field be added in the dependencies map? yes, we will add a namespace field and the namespace logic will handle replicated policy names so users do not have to include the namespace in the policy name
create a simple dependency example that Christian can show to customers for feedback


Remove empty fields

When getting data from a form with the content loader empty fields
should be replaced with None to cause the field to be removed in the
API. This means that the API will throw the correct error
(answer_required) when all types of field are not filled in.

As discussed in real life, this should work :+1:


1.18.2 Support + Improvements

I added some improvements to this bot :)
Update Mineflayer to version 4.1.0 (For 1.18.2 Support)
General code formatting (ES6-ify Callback functions, semi-colons, etc)
Added a feature to delay the auto-recconect action  (Customizable in settings.json), not doing this can sometimes lead to this.
All modules (Path-finding, auto-auth, anti-afk and chat-messages) were tested in a PaperMC 1.18.2-241 Server and encountered no issues.

Nice work :)


[wildcards] Consider reporting UNUSED_CATCH_STACK for stack wildcard params

Follow-up from: https://github.com/dart-lang/sdk/issues/55721#issuecomment-2113263991, It'd be nice to have a fix (or at least assist) that removes the unnecessary stack catch in code like:
try { } catch(e, _) {
  print(e);
}

producing:
try { } catch(e) {
  print(e);
}

@bwilkerson: if this is a fix, I guess we'd want a diagnostic for what's essentially dead code?

Question: do we want to start reporting UNUSED_CATCH_STACK for the wildcard case?
For example:
try { } catch(e, _) {
  print(e);
}

/cc @kallentu @bwilkerson

That seems reasonable to me. There's no value that I can see to having a wildcard as a stack-trace parameter.

Note that as we're ignoring underscores today this may cause new diagnostics for folks. (Something to consider.)


popover dismiss

hello guys,
I'm using reactstrap popovers in my pop.js component.The issue which i'm facing is that when i'm clicking anywhere within the popover it is closing randomly.I doesn't want this type of behaviour.

Hi @ashutoshsenger,
Good news, by default reactstrap's Popover component will not trigger the toggle method/callback when clicking within the popover.
Checkout these examples: https://reactstrap.github.io/components/popovers/
If you are placing the Popover within the triggering element/button and if you are toggling isOpen yourself when that trigger/button is clicked, you may be closing the Popover inadvertently yourself. It's really hard to tell what is happening since you didn't follow the issue template and you didn't provide any code or link to see your code (via something like stackblitz or codesandbox)


Feature request: Add support for newer 'vim.keymap.set' Nvim API

I'm really enjoying using this plugins functionality!
I think it could really be boosted by adding in support for the latest vim.keymap.set() API, which allows the user to do something like this:
vim.keymap.set({ "i", "s" }, "<c-l>", function()
  if ls.choice_active() then
    ls.change_choice(1)
  end
end)

So, allowing two modes to be combined in one keymap, and inlining a function in place of the string cmd from the older vim.api.nvim_set_keymap().
At the moment, in places where I do this in my config files, I haven't switched to using nvim-mapper for those bindings.
Obviously, you could keep backwards compatibility with the older API function, but I imagine that given the newer function has been around since Neovim 0.7.0, not many people are still using versions older than that.
Thanks!

#22 - PR to support this

#22 Merged


fix(ci): contracts_deployed check

Please provide a paragraph or two giving a summary of the change, including relevant motivation and context.
Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge.

[ ] If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag.
[ ] I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code.
[ ] Every change is related to the PR description.
[ ] I have linked this pull request to relevant issues (if any exist).

Benchmark results
Metrics with a significant change:

note_history_trial_decrypting_time_in_ms (5): 161 (+113%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit 4847c199 and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,444
179,588
716,132

l1_rollup_calldata_gas
222,960
867,872
3,449,648

l1_rollup_execution_gas
842,047
3,594,980
22,205,310

l2_block_processing_time_in_ms
1,327 (-1%)
5,280 (+4%)
20,955 (-1%)

note_successful_decrypting_time_in_ms
339
1,066 (+2%)
3,798

note_trial_decrypting_time_in_ms
47.6 (-5%)
39.6 (+5%)
137 (-4%)

l2_block_building_time_in_ms
13,501 (-1%)
53,564
216,115

l2_block_rollup_simulation_time_in_ms
9,971
39,590
160,220

l2_block_public_tx_process_time_in_ms
3,496 (-1%)
13,907 (+1%)
55,662

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
15,755 (+2%)
29,770 (+1%)

note_history_successful_decrypting_time_in_ms
2,760 (+2%)
4,970 (+3%)

note_history_trial_decrypting_time_in_ms
:warning: 161 (+113%)
214 (-29%)

node_database_size_in_bytes
3,926,270
5,821,101

pxe_database_size_in_bytes
29,940
59,499

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
199
43,109
20,441

private-kernel-ordering
114
25,833
9,689

base-rollup
2,055
244,144
881

root-rollup
84.9
4,088
889

private-kernel-inner
260
64,516
20,441

public-kernel-private-input
171
25,203
20,441

public-kernel-non-first-iteration
170
25,245
20,441

merge-rollup
11.2
2,608
881

Miscellaneous
Transaction sizes based on how many contracts are deployed in the tx.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
10,323
26,359


Add requirements.txt

This patch adds the requirements.txt file which lists the required
dependencies of this project. The file can be used by pip as shown in
the README file.

Looks good to me.

Thanks for the review, @vcgomes. I'm merging it now.


How-to use needs-render-context with a function without getting an unpickable warning

I try to use needs-render-context and get
cannot cache unpickable configuration value: 'needs_render_context' (because it contains a function, class, or module object)

Is there an option, to configure it without getting the warning?
I have set: suppress_warnings = ["config.cache"] in conf.py, but this is only a work around.

The trouble is sphinx-needs takes a str() of the parameter. Which is a dynamic address for functions. So what I did so far was wrap the functions in a class, but this has stopped working (not sure which version). Now we run into pickle trouble when we inject a class in that way.
class puml_participant:  # noqa: N801
    def __repr__(self):
        """
        Encapsulating the function in a class, forces cache compatibility as
        sphinx-needs will internally call str(obj) to determine the cache key.
        """
        return "[my puml_participant class]"

    def __call__(self, need: dict | str):
        """Create a PlantUML participant string for a need."""
        ...

needs_render_context = {
    "puml_participant": puml_participant(),
}

I tried injecting into jinja2uml instead of render_context. It's not the best API, but very first attempts look promising....

def inject_custom_fn_into_jinja2uml_render_context(functions: dict[str, Callable]):
    def wrap_jinja2uml():
        orig_jinja2uml = sphinx_needs.directives.needuml.jinja2uml

        def wrapper(  # noqa: PLR0913
            app: sphinx.application.Sphinx,
            fromdocname: None | str,
            uml_content: str,
            parent_need_id: str,
            key: str,
            processed_need_ids: dict,
            kwargs: dict[str, Any],
        ) -> tuple[str, dict]:
            # inject functions into kwargs, which will be appended to data
            kwargs.update(functions)
            return orig_jinja2uml(
                app,
                fromdocname,
                uml_content,
                parent_need_id,
                key,
                processed_need_ids,
                kwargs,
            )

        is_replaced = str(orig_jinja2uml).find("inject_custom_fn") != -1
        if not is_replaced:
            # print("Replacing!")
            sphinx_needs.directives.needuml.jinja2uml = wrapper

    wrap_jinja2uml()

And in setup() or somewhere:
    inject_custom_fn_into_jinja2uml_render_context(
        {
            "puml_participant": puml_participant,
        }
    )


These asserts validate some behavior of the compiler around which
SILInstruction can be paired with what type of SILLocation. That being said,
these asserts only effect debug info and are tripping in some programs on Linux
where we ship the compiler with assertions enabled. Darwin does not have these
issues since the compiler is shipped /without/ compiler assertions enabled.
rdar://77325585

Explanation: Avoid a harmless debug-info assertion that some people are seeing on Linux (when compiled with optimization) where we ship the compiler with assertions enabled.
Scope: The change turns off an assertion that validates that certain structural debug info properties are maintained. The problem itself being found results in just a small code local degradation in debug info quality. The assert in the mean time stops the user from being able to compile their code with optimizations enabled on Linux. So to balance that out, given where we are with the 5.4 release, it makes sense to just turn this off for now. The issue here does not happen on master and I am adding a new form of this assert that should make it much easier to track these down here: https://github.com/apple/swift/pull/37468.
Risk: Low
Testing: None. Commented out the debug info assert that was firing.
Issue: rdar://77325585
Reviewer: Adrian Prantl

@swift-ci test

Build failed
Swift Test Linux Platform
Git Sha - c923ea4fd59ac2f00f414fe58cdbc8a86fe95ecf

@swift-ci test linux platform

Got approval to merge. Going to do a subsequent PR that deletes the code.


we need logo icons for our languages

logo-32x32.png and logo-64x64.png in the same directory as kernel.json

here's how they appear in lab:

use the same colored squares as we use on http://beakernotebook.com/
with the same letter codes.

@scottdraves shouldn't this issue be closed already?


You May Also Like - Date Font Size

Date font size is much larger than live site. Can we reduce to match live?

@colinvlasak Can you please specify page url here

@jindaliiita here's a url with the component - https://main--shredit--stericycle.aem.live/en-us/resource-center/infographics/businesses-cant-ignore-consumers-data-protection-expectations

@jindaliiita thanks for updating this!


DNA Backmapping Procedure

Adding new functionality to Polyply in the form of a DNA backmapping procedure.

Gosh, that was quite a few commits. These also finally contain the changes I made this month. Which are:

As much as possible implemented the suggestions in the previous pull request.
Changed the data type for the coordinate input file to .dat, this now allows users to pass in both base pair positions and orientations.
First draft for dsDNA itp generator


Week 35

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 3 committers have signed the CLA.:white_check_mark: Pawka:x: epriestley:x: joshuaspenceepriestley seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


feat(bump-version): add bump version action

Summary of PR
Adds the action to bump a version according to our release rules and process. Also sorts out any tooling in the actions repo.
Tests for unexpected behavior

See comprehensive test suite.

Time spent on PR
6 hours
Related Issues
Related #2
Related #8
Reviewers
@saihaj @bhajneet

?
Thanks,
Harjot

On 20 Nov 2020, at 17:08, Bhajneet S.K<EMAIL_ADDRESS>wrote:

@bhajneet commented on this pull request.
In bump-version/index.ts:

+import { readJSON } from 'fs-extra'

+import getConventionalBump from './get-conventional-bump'
+
+const asyncExec = promisify( exec )
+
+type Package = {

version: string,
+}

+const nextInc = ( version: string, releaseType: string ) => inc( version, releaseType as ReleaseType, 'next' ) ?? version
+const removeNext = ( version: string ) => nextInc( version, 'patch' )
+
+const increment = ( version: string, releaseType: ReleaseType, isNext: boolean ) => {

// Current version is a next release or not
const currentNext = !!prerelease( version )
To actions?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I see that there are tests but how are we running them? I don't see any workflows for CI tasks that will run in this repo. I assume that we will be using this action to do release for this action 😄

With npm test for now lol, there will be CI workflows that use the repo's own workflows :)

Why didn’t we add CI in this PR ?

No particular reason other than I'm going to evaluate a generalised test action and see if it's worth it, and use that


[R] join with numeric columns has poor performance

Describe the bug, including details regarding any error messages, version, and platform.
When joining and the columns are numeric the performance scales really badly with size. I was noticing a huge speed difference when joining columns on numeric columns vs int32/int64 columns when by mistake my columns were numeric. This is not the case for dplyr.
I made the following figure by creating arrow tables of increasing sizes and joined them with another table a third of the size (see bottom for  code):

As can be seen when join columns are numeric it scales much worse than the other ones. I'm not even sure it makes sense to join on numerics... but I think this could be a bug. Or at least something worth investigating.

Code to reproduce
sizes <- c(1e3, 1e4, 1e5, 1e6)
results <- data.frame()
for (size in sizes) {
size1 <- size
size2 <- floor(size/3)

# int 32 id column
dfInt1 <- data.frame(id=sample(1:size1, replace=F),
                value=runif(size1))
dfInt2 <- data.frame(id=sample(1:size2, replace=F),
                value2=runif(size2))
arrowInt1 <- arrow::as_arrow_table(dfInt1)
arrowInt2 <- arrow::as_arrow_table(dfInt2)

# int 64 id column
type <- bit64::as.integer64
dfInt64_1 <- data.frame(id=type(sample(1:size1, replace=F)),
                      value=runif(size1))
dfInt64_2 <- data.frame(id=type(sample(1:size2, replace=F)),
                      value2=runif(size2))
arrowInt64_1 <- arrow::as_arrow_table(dfInt64_1)
arrowInt64_2 <- arrow::as_arrow_table(dfInt64_2)

# numeric id column
type <- as.numeric
dfNum1 <- data.frame(id=type(sample(1:size1, replace=F)),
                      value=runif(size1))
dfNum2 <- data.frame(id=type(sample(1:size2, replace=F)),
                      value2=runif(size2))
arrowNum1 <- arrow::as_arrow_table(dfNum1)
arrowNum2 <- arrow::as_arrow_table(dfNum2)

arrowResultsInt <- arrowInt1 |> dplyr::inner_join(arrowInt2, by='id') |> dplyr::compute()
arrowResultsInt64 <- arrowInt64_1 |> dplyr::inner_join(arrowInt64_2, by='id') |> dplyr::compute()
arrowResultsNum <- arrowNum1 |> dplyr::inner_join(arrowNum2, by='id') |> dplyr::compute()

res <- microbenchmark::microbenchmark(arrowInt32=arrowInt1 |> dplyr::inner_join(arrowInt2, by='id') |> dplyr::compute(),
arrowInt64=arrowInt64_1 |> dplyr::inner_join(arrowInt64_2, by='id') |> dplyr::compute(),
arrowNum=arrowNum1 |> dplyr::inner_join(arrowNum2, by='id') |> dplyr::compute(),
dplyrNum=dfNum1 |> dplyr::inner_join(dfNum2, by='id'),
dplyrInt=dfInt1 |> dplyr::inner_join(dfInt2, by='id'),
check = NULL, times=10
)
res <- summary(res)
res$size <- size

results <- rbind(res, results)

}

ggplot2::ggplot(data=results, ggplot2::aes(x=size, y=mean, group=expr, color=expr)) +
ggplot2::geom_line() + ylab('mean time (ms)')

Component(s)
R

This script is helpful, it reproduces the issue quite clearly.  It seems the issue is definitely in the join code.  A flame chart shows that significantly more time is spent both building and searching the hash table.  The size of the key shouldn't really matter in this case since these operations are working on the hash which is always 32-bit.
More concretely, the arrow::compute::SwissTable::search_block function is called an order of magnitude more times when working with numeric data. Based on my (admittedly rough) understanding I believe this suggests a less even distribution across hash buckets when working with numeric data.
This fix is going to require someone motivated to really dig in and understand how the hash table works.


Support for suspendable property resolvers

Would be great with suspendable property resolvers. Something like #37. But something that actually works.
I haven't gotten a full overview of how everything in this project works yet, so I failed implementing this. If there is anything I can help out with I would love to.

Would to see this feature as well! So I could use java-dataloader which uses Futures.
The problem is that we can't just call dataloader.dispatchAndJoin in property resolver since the batching won't work.
With suspend resolver we could use await() to solve the problem


Mention graphql-java-servlet project

Hi, I thought this might also deserve a spot in "Related Projects": This project exports a servlet that automatically exposes a schema dynamically built from GraphQL queries and mutations.

Thanks.


not compatible anymore with appium java-client 8.0

My testsuite is running with the latest appium java client and i came up to a problem that the flutter finder seems to use mobileElement which is not supported anymore.
Anyone a workaround instead of going back with the java client version ?

Perhaps https://github.com/appium-userland/appium-flutter-driver/tree/main/finder needs some update.

@StephanB75 I made some workarounds here on the Kotlin project to made it work with java-client 8.0, hope it helps.

@hai-ha THANKS for your help !
Maybe i'm doing something wrong but i after building the FlutterFinder.class with "gradle clean assemble" and importing it into my project i get this errors

@hai-ha Thank you looks better now :)
Do you have only replaced MobielElement with RemoteWebElement ?
If yes i had also tried that yesterday myself but most probably i have done something wrong on importing the compiled class to my project ;)
Again Thank you for our help.
@KazuCocoa Will this change come into the master ?

@StephanB75 Mostly so, you may see the code changes here: https://github.com/appium-userland/appium-flutter-driver/compare/main...hai-ha:main

Hi @KazuCocoa,
I'm new to this project. Not sure how I can submit the code changes for kotlin finder project?
Thanks,
Hai

You could just create a pr

https://github.com/appium-userland/appium-flutter-driver/pull/266


[Mod compatibility suggestion] medievalmusic

If there are any other mods that either add music tracks to the overworld or have their own dimension with custom music tracks, please let me know and I will add support for them!

Well then. medievalmusic does exactly that, but right now its tracks are recognized as builtins.

I looked into this and quickly learned that this mod is just replacing the vanilla game soundtrack with their stuff. Unfortunately, this means I can't support this as its not adding its own tracks to the game.


IntField with default value of 0 is lost on subsequent saves

Similar to BooleanFields with default values of False (see issue #282), IntFields with default values of 0 are dropped from the database when the originally created document is tweaked and saved.
Test code:
from mongoengine import *

connect("wolf")

class Doc(Document):
    count = IntField(default=0)
    name = StringField()

doc = Doc()

doc._get_collection().drop()

doc.save()

for d in doc._get_collection().find():
    print d

# Uncomment this line, and things work fine
# doc.reload()

doc.name = "foo"
doc.save()

for d in doc._get_collection().find():
    print d

This has output like this:
{u'count': 0, u'_types': [u'Doc'], u'_id': ObjectId('4f2223111725c673f6000000'), u'_cls': u'Doc'}
{u'_types': [u'Doc'], u'_id': ObjectId('4f2223111725c673f6000000'), u'_cls': u'Doc', u'name': u'foo'}

Note that count is missing from the latter.
If you uncomment the doc.reload() call, or query for the document any other way, things work as expected.

Seems like the fix for issue 282 in commit 6419a8d should be checking for not-None instead of truthiness?
Ie, instead of:
if value or isinstance(value, bool): continue

it should be:
if value is not None: continue


Missing File in Documentation without full Feature

The documentation talks about a syn::File parser for parsing a complete file:

The syntax tree is rooted at syn::File which represents a full source file, ...

However this is a broken link without the full feature. I'm not sure how best to handle this, but thought I'd let you know since it caused me a moments confusion.

This crate is only meant to be documented with all features enabled, matching https://docs.rs/syn.
https://github.com/dtolnay/syn/blob/ee66f12d9154b984531eacfb084fd4fe8a87b466/Cargo.toml#L64-L67


adding docker build materials and README

Adds a Dockerfile for building an (admittedly large) container image which has all of the project environments pre-installed via pinto. We can make this available on LDG and use it as the default entrypoint for new users to get BBHNet running. Also adds a README which covers the couple different paths to get running with BBHNet, and will eventually include developer instructions as well.

[x] Add workflow for container build/push
[ ] Make a PR against OSG to include this container on /cvmfs
[ ] Include developer set-up instructions in README

Closes #237 , closes #192

Omicron won't work with a containerized deployment right now. pyomicron doesn't support creating condor sub files that leverage singularity images, so there won't be any omicron executable to point to which will exist in the submitted job.
Taking a look at the pyomicron code, it seems like it might be somewhat straightforward to augment to support this behavior. Basically you would just need to add some code to its OmicronProcessJob.write_sub_file function to check if the job is meant to run in a singularity container, and if so add the corresponding
+SingularityImage = "..."
Requirements = HasSingularity

lines to the sub file and re-write it. All you would have to do then is add an arg to the command line parser and pass it to the DAG instantiation here.
@EthanMarx I know you were also planning on doing some forking/developing of omicron. Have you made any moves on that? Might make sense for us to create an ML4GW/pyomicron fork that we develop on our own and use to submit PRs upstream without having to wait for their dev cycle.

Filed this in gwpy/pyomicron#150 for reference and tracking purposes

Yeah I like the idea of an ML4GW/pyomicron fork. We can fork and make pull requests against it ourselves, and then if the pyomicron folks deem our PRs worthy, we can make PRs from ML4GW/pyomicron to gwpy/pyomicron.
I'll try to set this up for my more basic addition (flag for cleaning the temporary files) today.

PR for omicron fix filed in ML4GW/pyomicron#1

Been looking into docker more and how it may interact with condor.
Thoughts on the following:

Instead of creating a monolithic image for the entire project (which seems to be large) we containerize each component (e.g. an individual container for each of datagen, train, analysis, etc.)
Create a condor wrapper script that creates the end to end pipeline and runs each individual component in its respective container.
Create a version of the pipeline with docker-compose in the scenario a user does not have condor access. (For the pyomicron jobs, we could simply launch the bash file that is created, or write a wrapper that creates a more parallelized version)

@EthanMarx great points. What you've described with (1) is my plan for production for sure, I would never use a container like this. And (2) and (3) are generalizations of pinto to containerization that I've been considering for a while but haven't really made sense until the past couple months now that we can use apptainer without root to build and pull containers at will for dev purposes.
I think the idea here for me was to create something that didn't require someone to install any dependencies to run. Just a true out-of-the-box implementation that someone who just wanted to get up and running could use with 0 thought, and could also be used to recreate deterministically any results we eventually publish. This was more attractive when I thought it wouldn't take that much work, but obviously Omicron is proving that's not the case, so maybe it's a fair time to rethink this.

Was able to get a docker image built that installs omicron and gwollum from source via the git.ligo.org master branches, into a conda environment. I've pushed the docker image here .
Here's the Dockerfile. My first ever so curious to hear feedback:
ARG CONDA_TAG=22.11.1

FROM continuumio/miniconda3:${CONDA_TAG} as base

# create conda environment installing omicron/gwollum deps
COPY environment.yaml .
RUN conda env create -f environment.yaml

ENV SRCDIR=/src/ \
    INSTALLDIR=/opt/conda/envs/omicron

SHELL ["conda", "run", "-n", "omicron", "/bin/bash", "-c"]

RUN apt-get update && apt-get install -y --no-install-recommends \
        git \
        build-essential \
        pkg-config \
        cmake

# install GWOLLUM
RUN mkdir -p ${SRCDIR} \
        && cd ${SRCDIR} \
        && git clone https://git.ligo.org/virgo/virgoapp/GWOLLUM.git && cd GWOLLUM \
        && mkdir ./build && cd ./build \
        && cmake -DCMAKE_INSTALL_PREFIX=${INSTALLDIR} ${SRCDIR}/GWOLLUM \
        && make && make install \
        && source ${INSTALLDIR}/etc/gwollum.env.sh

# install Omicron
RUN cd ${SRCDIR} \
    && git clone https://git.ligo.org/virgo/virgoapp/Omicron.git && cd Omicron \
    && mkdir ./build && cd ./build \
    && cmake -DCMAKE_INSTALL_PREFIX=${INSTALLDIR} ${SRCDIR}/Omicron \
    && make && make install \
    && source ${INSTALLDIR}/etc/omicron.env.sh

And the environment.yaml that contains the gwollum / omicron deps
name: omicron
channels:
  - conda-forge
dependencies:
  - fftw
  - hdf5
  - framel>=8.42
  - root_base>=6.26
  - libstdcxx-ng


Updateable robot model

This allows the robot footprint model to be updated. The current "Is_footprint_dynamic" dynamically reconfigurable parameter only updates the global planner footprint to check feasibility. This change allows updating the actual model, even changing the model type.  To use, first update the values on the parameter server, then call the dynamic reconfigure service. No need to reconfigure anything though, it's the call that triggers the update. So if the footprint_dynamic is set to true, calling the service to set it to true again will update the model  (unless someone wants to implement a separate service call...).
Tested on melodic.

Thanks.


fix: fixed regex missing from heartbeat method

- What I did
Removed regex as a parameter from the monitor methods
helps fix Python sshnpd unreliable
- How I did it
- How to verify it
- Description for the changelog
fix: regex missing from heartbeat method

Looks like a test flake with python 3.8


Little more detail please

How and where can I check all these options and/or set them via GPO?
The following settings are known to interfere with the ability to use and reset passwords on Windows 10 devices
If Ctrl+Alt+Del is required by policy in versions of Windows 10 before v1809, Reset password will not work.
If lock screen notifications are turned off, Reset password will not work.
HideFastUserSwitching is set to enabled or 1
DontDisplayLastUserName is set to enabled or 1
NoLockScreen is set to enabled or 1
EnableLostMode is set on the device
Explorer.exe is replaced with a custom shell
The combination of the following specific three settings can cause this feature to not work.
Interactive logon: Do not require CTRL+ALT+DEL = Disabled
DisableLockScreenAppNotifications = 1 or Enabled
IsContentDeliveryPolicyEnforced = 1 or True

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

ID: c2015c6c-60c7-bb74-469c-e9320301d08a
Version Independent ID: 0ff19de6-c892-10ff-5fe8-f6a70abfa3f5
Content: Azure AD self-service password reset for Windows - Azure Active Directory
Content Source: articles/active-directory/authentication/howto-sspr-windows.md
Service: active-directory
Sub-service: authentication
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@cfizz34 Thanks for your feedback! We will investigate and update as appropriate.

They can be set via Group Policy or Intune CSP. I can add a link to the top level pages for them in the next steps sections.


[BUG] Add Portfolio Link with Icon to Founder Card

Description
On the team page of the HelpOps-Hub repository, I noticed that the founder card currently displays a GitHub icon with a link to the GitHub profile. To enhance the representation, I would like to replace the GitHub icon with a portfolio link that includes a suitable portfolio icon. This will give users direct access to the founder's portfolio, showcasing their work in a more professional and visually appealing way.
Screenshots
No response
Any additional information?
No response
What browser are you seeing the problem on?
No response
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[ ] I'm a GSSoC'24-Extd contributor
[X] I'm a Hacktoberfest'24 contributor
[X] I am willing to work on this issue (optional)

@NitishKumar525 you are assigned.