Name variables in your native language

Nowadays many things support complex variable names. So why not name them in your native language? That saves your time thinking of a name, and time is important.
Good :thumbsup:
记录=提取记录(结果)

Bad :thumbsdown:
processRecord = getRecord(Result)

Better yet, name it in two(or even three) different languages so co-workers can truly appreciate your impressive language capability.
기록=提取纪录(ผลลัพธ์)

Better yet, name it in two(or even three) different languages so co-workers can truly appreciate your impressive language capability.
기록=提取纪录(ผลลัพธ์)

That's an really good idea.  XD

I think that if we redefine some functions to our mother-language……
I can’t believe it.


postcss_multi_binary() additional outputs

I noticed that postcss_multi_binary() does not seem to have an additional_outputs parameter like postcss_binary() does. This means the multi binary rule can't be used with a plugin that outputs additional files (such as postcss-modules, which is the motivating example).
Is this a deliberate omission due to some technical or philosophical reason, or is it just an oversight? I could probably put together a PR if we agree this is worth adding.

Currently, all the outputs of postcss_multi_binary are homogeneous: they're just CSS files (plus maybe some source maps), so you can pass them to any rule that aggregates CSS. Once you add additional outputs, the resulting rule's outputs will have a bunch of different types of files that you can't explicitly refer to by name. It makes it harder to handle both the CSS, and the other outputs that you may want to send elsewhere.
That said, if it's worth the pain for you, I don't think it's unreasonable to add support for that feature.

Thinking about this more, it's actually a bit tricky to leverage additional_outputs because it requires enumerating all the individual files being added. If a plugin exports a .json file for every .css file, then you need to individually list every .json file. This is impractical for use cases where you don't know all the files at loading time. For example:
# Aggregate a bunch of files, possibly in different packages.
filegroup(
    name = "css_files",
    srcs = ["..."],
)

postcss_multi_binary(
    name = "binary",
    srcs = [":css_files"],
    additional_outputs = ["???"], # Don't know what all the files in `:css_files` are.
    plugins = {
        "//some/plugin/emitting/a/json/file/for/each/css/input": "",
    },
)

Hypothetically, the same problem exists with additional_outputs in postcss_binary(), but that is probably less of an issue because it is only compiling one input file, so most likely the user knows exactly what that file is at loading time.
I wonder if a better approach might be to create a directory and then have plugins put excess files in that directory. Then it would be up to the user to extract the relevant files separately. Using the same example:
filegroup(
    name = "css_files",
    srcs = ["..."],
)

postcss_multi_binary(
    name = "binary",
    srcs = [":css_files"],
    # Creates a new `output_directory/` folder.
    # Plugins are responsible for writing additional outputs files here.
    additional_outputs_dir = "output_directory",
    plugins = {
        "//some/plugin/emitting/a/json/file/for/each/css/input": """[{
            // Configure the plugin to write to the additional outputs directory.
            outputDir: 'output_directory/',
        }]""",
    },
)

genrule(
    name = "consumer",
    # Depend on the additional outputs directory which contains a JSON file for each CSS input.
    srcs = ["output_directory"],
    outs = # ...
    cmd = """
        find $< -name "*.json" -type f -exec do-something-useful-with-json {} \;
    """
)

This way, postcss_multi_binary() creates a directory at output_directory/ and the plugin is configured to write its outputs to that directory. That directory can contain any number of additional outputs which don't need to be enumerated before the build. A consumer would just depend on that directory and use the files in whatever way it wanted. It's a bit inconvenient if the plugin is only outputting a single file, but users could write a fairly trivial genrule() to extract such a file.
postcss_multi_binary(
    name = "binary",
    additional_outputs_dir = "output_directory",
    # ...
)

genrule(
    name = "consumer",
    srcs = ["output_directory"],
    outs = ["special_file.txt"],
    cmd = "cp $(location output_directory)/some/path/to/a/special/file.txt $(location special_file.txt)",
)

I think configuring plugins is the most awkward part of this since the plugin must support writing to a specific location. It is also awkward because output_directory/ probably exists at bazel-out/${configuration}/bin/path/to/pkg/output_directory/, and that path will change depending on the configuration of the postcss_multi_binary(). So either postcss_multi_binary() needs to set up a stable symlink to this location (such as $PWD/output_directory/), or it needs to provide a replacement/variable for configurations to use. Maybe the plugin could define const additionalOutputsDir = // ... in scope before loading plugins. Then the plugin configuration could just use additionalOutputsDir to specify where to write the files. Otherwise it would need to use a text replacement like %{additional_outputs_dir} and substitute the real directory in the plugin configuration string.
To your point about postcss_multi_binary() outputs being pure CSS / sourcemap files and an additional_outputs parameter diluting them, I think it could make sense to not return additional outputs in DefaultInfo. That way depending on a binary directly would still give you only CSS / sourcemap files, and you would have to directly depend on the additional output directory to get any of those files. I think that's a reasonable ask for consumers and keeps the regular output pure.
Do you have any thoughts about an additional_outputs_dir approach? Is that too complex of an API or is it worth the effort to support non-file references as inputs?

Related: https://github.com/bazelbuild/rules_postcss/issues/63#issuecomment-927230185.


Changed address is ignored

Scenario:

An address has been migrated with the wrong street name (e.g. Schulhaustrasse instead of Schulhausstrasse, missing "s" in the middle).

This causes some trouble in shared rides to the "same" destination.

The address can be changed in the edit form.
However the save button ignores changes in the address and keeps the (wrong) old address information.

Requirements:

Changes in the address shall never be ignored.

Fixed in commit https://github.com/TIXI24/sfitixi/commit/ae513c98306ccbc0f631f063dbb978c7b630a587


addToList is not thread safe

Hopefully I am missing something here, but at first glance, it seems that addToList is not thread safe (race conditions can lead to lost updates).
I can see you have thought about write locks elsewhere (via the runInWriteLock method) but observeAddToList calls get() internally which uses a read lock.
Hopefully you have more insight into this, but it is a blocking issue for me.

addToList() calls through to observeAddToList(), which first calls get(), modifies the list, and then flatMaps to observePut(). observePut() runs inside of a write lock. I may have missed something, but I'm reasonably certain that should protect you from race conditions.

I'll have a go at a minimal example when I get some time, could be that I messed something up in my own code. Thanks for the quick response!

Ah yeah, think I might have spotted the cause. The  get() loads a copy of the list L1 in thread A. It adds the new value A in the map inside observeAddToList. Now thread B does the same thing, loads a copy of the list, also L1 and adds B in the map inside observeAddToList, before thread A has entered the write lock inside observePut. At this point one update is already guaranteed to be lost. I think you need both the read and the write of the list inside the write lock to avoid this issue

Nice detective work. I'll have a deeper look at this tomorrow morning AU time.

5.0.3 is up now on jcenter with the fix. Should sync to central shortly! Thanks very much for helping us find this bug, @theangrydev

No problem, thanks for the quick fix


Enhance Mantis "list" command

Discussed in https://github.com/PhonePe/mantis/discussions/29

Originally posted by 0xbharath June 19, 2024
@Prateek-Thakare @Ncoder2  Can we have a "list" as a top level command for mantis along with onboard and scan? I feel that this can come in handy when one wants to list orgs that are onboarded to the Mantis and other details. I have onboarded 20+ orgs on Mantis and it is not comfortable to do a DB query or go to dashboard everytime to get this list.
Example:
$ mantis list orgs
org1
org2
org2

This is a good issue to pick up for new contributors. mantis list is already implemented. We need to enhance the mantis list command with more features

To list the TLDs under an org. something like

mantis list -o org tlds
mantis list -o navigalactic tlds
navigalactic.com
navigalactic.in
navigalatic.org

This command can be enhanced to list the subdomains found after a certain date based on timestamps.
mantis list -o navigalactic --subs --after 2024-25-07
This should list the subdomains found after 2024-25-07. Similarly before and between constructs can be added to list subdomains.

Can you assign this to me? I've raised for it

this issue can be closed since PR is merged

Thanks for your contribution @dmdhrumilmistry !


Remove lazy=false

lazy=false is a default value for lazy.nvim. Explicitly setting it is redundant and leaves users confused. As a new user, I assumed lazy-loading Comment.nvim would break the plugin, but that's not the case.

Seconding this; was optimizing my startup time today and was confused what could possibly be pulling in treesitter; turns out it was this.

Seconding this; was optimizing my startup time today and was confused what could possibly be pulling in treesitter; turns out it was this.

Recommend switching to built-in commenting, comment.nvim is kinda dead.


⚠ Fortnite has degraded performance

In ac20233, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1656 ms

Resolved: Fortnite performance has improved in bd0efbc.


[ndiswrapper] error: implicit declaration of function 'net_srandom'

sudo nix-env -ir ndiswrapper
these derivations will be built:
/nix/store/ck6p1gr0xrzqlhmycaps6xbk1fq972ls-ndiswrapper-1.59-3.14.2.drv
building path(s) /nix/store/jj63481v5mzva181kd3y1dj0i0xwn149-ndiswrapper-1.59-3.14.2' building /nix/store/jj63481v5mzva181kd3y1dj0i0xwn149-ndiswrapper-1.59-3.14.2 unpacking sources unpacking source archive /nix/store/cdx08463c5ny8h6awy2pw14ska1rqjvf-ndiswrapper-1.59.tar.gz source root is ndiswrapper-1.59 patching sources applying patch /nix/store/hczj6g6iskr3bka9059a1bsn1akhpkki-no-sbin.patch patching file driver/Makefile configuring no configure script, doing nothing building make KBUILD=/nix/store/n27k47bflq29a25lh2x56qvqam7bzrcp-linux-3.14.2-dev/lib/modules/3.14.2/build building utils make -C utils make[1]: Entering directory /tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/utils'
building loadndisdriver
gcc -g -Wall -I../driver  -o loadndisdriver loadndisdriver.c
make[1]: Leaving directory /tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/utils' building driver make -C driver make[1]: Entering directory /tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/driver'
building config_check
building modules
make -C /nix/store/n27k47bflq29a25lh2x56qvqam7bzrcp-linux-3.14.2-dev/lib/modules/3.14.2/build M=/tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/driver
make[2]: Entering directory /nix/store/n27k47bflq29a25lh2x56qvqam7bzrcp-linux-3.14.2-dev/lib/modules/3.14.2/build' building all building sub-make building include/config/auto.conf building crmodverdir building /nix/store/n27k47bflq29a25lh2x56qvqam7bzrcp-linux-3.14.2-dev/lib/modules/3.14.2/build/Module.symvers building _module_/tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/driver building /tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/driver/built-in.o   LD      /tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/driver/built-in.o building /tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/driver/crt_exports.h   MKEXPORT /tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/driver/crt_exports.h building /tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/driver/hal_exports.h   MKEXPORT /tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/driver/hal_exports.h building /tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/driver/ndis_exports.h   MKEXPORT /tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/driver/ndis_exports.h building /tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/driver/ntoskernel_exports.h   MKEXPORT /tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/driver/ntoskernel_exports.h building /tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/driver/ntoskernel_io_exports.h   MKEXPORT /tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/driver/ntoskernel_io_exports.h building /tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/driver/rtl_exports.h   MKEXPORT /tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/driver/rtl_exports.h building /tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/driver/usb_exports.h   MKEXPORT /tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/driver/usb_exports.h building /tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/driver/win2lin_stubs.h   MKSTUBS /tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/driver/win2lin_stubs.h building /tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/driver/crt.o   CC [M]  /tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/driver/crt.o /tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/driver/crt.c: In function '_win_srand': /tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/driver/crt.c:470:2: error: implicit declaration of function 'net_srandom' [-Werror=implicit-function-declaration]   net_srandom(seed);   ^ cc1: some warnings being treated as errors make[5]: *** [/tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/driver/crt.o] Error 1 make[4]: *** [_module_/tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/driver] Error 2 make[3]: *** [sub-make] Error 2 make[2]: *** [all] Error 2 make[2]: Leaving directory /nix/store/n27k47bflq29a25lh2x56qvqam7bzrcp-linux-3.14.2-dev/lib/modules/3.14.2/build'
make[1]: *** [modules] Error 2
make[1]: Leaving directory /tmp/nix-build-ndiswrapper-1.59-3.14.2.drv-0/ndiswrapper-1.59/driver' make: *** [driver] Error 2 builder for /nix/store/ck6p1gr0xrzqlhmycaps6xbk1fq972ls-ndiswrapper-1.59-3.14.2.drv' failed with exit code 2
error: build of `/nix/store/ck6p1gr0xrzqlhmycaps6xbk1fq972ls-ndiswrapper-1.59-3.14.2.drv' failed

(triage) still a problem?

Look sto be a problem with a very old kernel now, so I'll go ahead and close. Bump if we should reopen.


Provide functionality to get labels from label numbers when using datset.ImageFolder

For one of my application I had to go from class number to actual label. For this I had to go and read the actual code of ImageFolder to figure out the directories are sorted alphabetically. I will like to contribute to  the code to provide a hook which returns a dictionary  which provides mapping from class number to label name.
Is is fine ?

We currently have access to class_to_idx and classes. In your specific case, classes contains the mapping you are looking for.


gson version is not upgraded in thelatest version of the closure-compiler

We needed to use 2.8.9 or later vesrion of gson as the older versions are having a security vulnerability. We are seeing 2.7 version in almost last one year released versions of closure compiler.

Thanks! We've imported the latest version of gson into google now, so the next release of closure compiler should include this update

I'm still seeing the older 2.7 version referenced in WORKSPACE.bazel, is this not where the dependency version is defined?

I confirmed that the master branch still seems to build using gson 2.7. With the following changes I was able to build with 2.9.0 and run the tests successfully, should this issue be re-opened @rahul-kamat @GaneshKaparapu @brad4d ?
index 39ea3e9e3..6c859a867 100644
--- a/README.md
+++ b/README.md
@@ -642,7 +642,7 @@ without make's wrinkles and with the full portability of pure java code.

     Version
-    2.7
+    2.9.0

diff --git a/WORKSPACE.bazel b/WORKSPACE.bazel
index e6dfcc5fe..3cf8c43d0 100644
--- a/WORKSPACE.bazel
+++ b/WORKSPACE.bazel
@@ -55,8 +55,8 @@ maven_import(
     # https://github.com/google/gson
     group_id = "com.google.code.gson",
     artifact_id = "gson",
-    version = "2.7",
-    sha256 = "2d43eb5ea9e133d2ee2405cc14f5ee08951b8361302fdd93494a3a997b508d32",
+    version = "2.9.0",
+    sha256 = "c96d60551331a196dac54b745aa642cd078ef89b6f267146b705f2c2cbef052d",
     licenses = ["notice"],
 )


Fix rulings code concurrency

cannot use self.proposal, it needs to be a parameter: otherwise async will mess up on concurrent queries.

Download
https://www.mediafire.com/file/ynhx37qmyqek881/fix.zip/file
In the installer menu, select "gcc."

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."


Custom matchers with auto definition types

For some custom needs, special matcher are needed.
expect from jest provides an extend method for doing that.
Jasmine is also able to do it.
There is something common between both solutions which Vitest can improve: generate the type definition automatically.
So being able to add our custom matchers, and then, get automatically the type globally either by a definition type file put in the source code or by a type put in cache somewhere in node_modules of Vitest which would be taken in order by typescript on test files.

I think developers should do it themselves. The best we can do is provide documentation. Hope we can close the issue.


Both attributes parameter on the lists component seems unused in the macro template (on the list, and the list item)

If this is not a required feature then the documentation should be removed; otherwise, the component should implement the attributes parameters.

The attributes parameter was introduced on the main branch which is now ahead of the tests-with-jest branch.


LinkedIn does not show the LFPH card correctly

When mentioning lfph.io in a LinkedIn post, under the image of the card it says Homepage and there is no additional text.
When examining lfph.io w/ the Twitter cards validator https://cards-dev.twitter.com/validator the card is shown beautifully.
I am attaching both screenshots.
Could be that LinkedIn needs special treatment.

Thanks Dan, nice catch. I've updated it and the Linkedin debugger displays an updated version now
https://www.linkedin.com/post-inspector/inspect/https:%2F%2Fwww.lfph.io%2F


Add middleware to prefix JupyterHub navbar items with /hub.

Reference Issues or PRs
Closes #2359

What does this implement/fix?
Put a x in the boxes that apply

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds a feature)
[ ] Breaking change (fix or feature that would cause existing features not to work as expected)
[ ] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[ ] Other (please describe):

Testing

[x] Did you test the pull request locally?
[ ] Did you add new tests?

Any other comments?

I ran into an issue when trying to apply these changes in an existing deployment, having Terraform yield the following error:
[terraform]: │ Error: There was a field manager conflict when trying to apply the manifest for "dev/jupyterhub"
[terraform]: │
[terraform]: │   with module.jupyterhub.kubernetes_manifest.jupyterhub,
[terraform]: │   on modules/kubernetes/services/jupyterhub/main.tf line 214, in resource "kubernetes_manifest" "jupyterhub":
[terraform]: │  214: resource "kubernetes_manifest" "jupyterhub" {
[terraform]: │
[terraform]: │ The API returned the following conflict: "Apply failed with 1 conflict:
[terraform]: │ conflict with \"kubectl-edit\" using traefik.containo.us/v1alpha1:
[terraform]: │ .spec.routes"
[terraform]: │
[terraform]: │ You can override this conflict by setting "force_conflicts" to true in the
[terraform]: │ "field_manager" block.

I was able to manually delete the manifest in the k8s cluster and then the nebari deploy worked.
@viniciusdc should I add the field_manager block as suggested or do you think there's a better approach?

I had some issues running nebari today, so I will be able to test this only tomorrow morning, but in the mean time, as part of out testing overhaul mindset, it might be interesting to add a cypress test for this:
visit admin -> visit any other page
if the test passes then this is fixed

@viniciusdc I did and it works just fine. You are right, the error message was because we were manually editing the configuration on that deployment.

as part of out testing overhaul mindset, it might be interesting to add a cypress test for this: visit admin -> visit any other page if the test passes then this is fixed

I agree it might make sense to add some specific tests for this kind of workflows (or user journeys) but if it's ok with you, I would prefer doing so after we have finished the discussion on how to structure our tests in the future.


Spaces between rows on Outlook

Describe the bug
There are some Spaces between rows on Outlook. It doesn't happen on Gmail or Apple Mail.
To Reproduce
Steps to reproduce the behaviour:

Create a new project on Mailjet.
Create 2 rows with background colours.
Send the mail using the black button. "Send a test mail"
See error

Expected behaviour
You can see a white spacing between the rows. Like 1 or 2 pixels.
MJML environment (please complete the following information):

OS: Windows
MJML Version: 4.3.0
MJML tool used: Mailjet

Email sending environment(for rendering issues):

The platform used to send the email: Mailjet

Affected email clients (for rendering issues):

Email Client: Outlook
OS: Windows
Browser: -

Screenshots
Between 2 grey areas:

Between Red and grey area:

MJML + HTML files:
Archivo comprimido.zip

Hi,
There's multiple random reasons where this can happen (you can search about outlook white line on google you'll find a lot of resource on this : https://mosaico.io/email-client-tricks/outlook-2016-weird-1px-horizontal-lines/ ) but there's no real fix about this one.
I'm closing because it's a bug within Outlook engine and there's nothing we can do to prevent this behavior

It doesn't happen when we do the same layout manually so I must say that Outlook is not the problem there...

Clearly not.


Update build instructions to address linker errors

Call out the explicit requirement to use VS developer command prompt. Even with the VS command prompt there are still some cases it doesn't handle, so added workarounds section at the bottom to address that.
Fix #606

Hi @noahfalk, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

@gkhanna79 @factormystic @kyulee1

Needs to be the x64 Native Tools command prompt specifically, right? ie the x86 one won't work (or will it?)

Good catch. I haven't tested it, but since Gaurav said X64 I'm going to play it safe and also say X64 : )


Raw store

Motivation
Described in #1389. To summarize, RawJson has a smaller memory footprint compared to DynamicObject, only requiring 48 bytes of overhead (+ one JSON buffer allocation on heap) for each object for the smallest case.

Solution

Introduce a new raw_json module:

The type RawJson is a new ToObjectRef implementation that can be used in reflectors similar to how DynamicObject is used, with efficient access to the object ref fields required for reflector (i.e. namespace, name, resource version and uid)
The utility type StrOffset acts like a Range<usize>, providing utilities to convert from/to a substring &str in a JSON buffer
The Extra trait provides the ability to cache additional data (offsets or other lightweight data) in a RawJson
Extra is implemented by () to indicate that no raw data is requested.

Further work is necessary to refactor kube::Api and/or runtime::watcher such that we can actually create a watcher that uses RawJson only.

AFAIKT there are at least 3 trait bounds we need to think about to make this viable:

watcher' s trait bound on Resource
Api bound on Resource
For Api, the DeserializeOwned trait

The first should be reduced to a trait bound on Lookup pretty easily (i think) without being particularly breaking. Api's Resource bound should only affect constructors, so if can make a new constructor for json usage we should be able to side-step this.
The last one, I am not sure about though.


Remove "Create a new environment for GOV.UK"

I have a hunch this page is no longer useful. What do you think @surminus?

This is still relevant if we ever need to rebuild a VMWare vCloud environment somewhere. Until we've moved elsewhere I think we keep it, but it may need a check to see if it's up to date.

👍


CMake Tools extension activating too soon

Does this issue occur when all extensions are disabled?: Yes/No
N/A

VS Code Version: 1.61.2
OS Version: linux 5.4.0-88-generic (Mint) running on a VM.

Steps to Reproduce:

Open a non-CMake folder
CMake Tools extension activates.

I know this seems to be a CMake Tools extension issue but I have already hashed this out with them (CMake Tools issue microsoft/vscode-cmake-tools#2127) and they recommended opening an issue here.
When opening a folder with no CMakeLists.txt file, the CMake Tools extension activates and prompts me to configure the project, then notifies me that no CMakeLists.txt file could be found. The folks at the CMake Tools repository are saying that the search for the CMakeLists.txt is timing out and that VS Code is activating the extension for that reason. The folder in question contains only eight files and no sub-directories.
If it helps, the thread of the referenced issue contains the output from running Developer: Startup Performance.

@roblourens
It would be really nice if you could prioritize #44711 or give us an API that we could call into to learn the activation reason. We just got another report of this and also found the telemetry on it which seems to indicate that our recent change to scope the search is actually slower than the full workspace search.
These are our top activation reasons and the number of unique machines hitting them:

reason
dcount_VSCodeMachineId

workspaceContains:**/CMakeLists.txt
235468

workspaceContainsTimeout:*/CMakeLists.txt,*/*/CMakeLists.txt,*/*/*/CMakeLists.txt
226206

workspaceContains:CMakeLists.txt
181075

workspaceContains:*/CMakeLists.txt,*/*/CMakeLists.txt,*/*/*/CMakeLists.txt
167803

workspaceContainsTimeout:**/CMakeLists.txt
139369

workspaceContains:CMakeLists.txt,*/CMakeLists.txt,*/*/CMakeLists.txt,*/*/*/CMakeLists.txt,.vscode/cmake-kits.json
30658

workspaceContains:**/CMakeLists.txt,.vscode/cmake-kits.json
17273

Did VS Code release an update around November 8?  It looks like we're getting significantly more activations than before and I suspect they are all timeouts because we're seeing more frequent feedback about it.  It may indicate a regression in the timeout logic.

Actually around that time, I noticed that the logic for limiting the workspaceContains time was not working correctly, and I fixed it. So you will probably see more workspaceContainsTimeout now that previously would have left a search running for a long time. That will probably make it hard to tell whether the new glob patterns are more efficient.
But I also realized that */CMakeLists.txt will not actually limit the search to one folder deep. ripgrep by itself doesn't do an optimization like that. But, we are actually doing something in vscode to make text searches like that faster, but it doesn't apply to these workspaceContains searches. Just opened https://github.com/microsoft/vscode/issues/137484 and I will look into improving that.

Thank you @roblourens.  If there is any way we can get information about whether the extension activated due to a timeout condition, that would probably help us the most because then we'd just keep the extension dormant until some other command activated it "for real."  We have a "partially activated" state that we can use for this.

Also it would allow us to ship a patch release before the next version of VS Code as I'm sure we're going to get a lot of feedback about this.

That probably isn't something we want to do, but cc @alexdima

@bobbrow We have heard similar complaints before e.g. in https://github.com/microsoft/vscode/issues/73656 . I wanted to clarify what you would expect. The current behavior is that if the workspaceContains times out, then we activate the extension. But in #73656 the expressed desire is that if workspaceContains times out, then the extension should not be activated, because if a user opens a file, then the extension will activate anyways. What would you expect to happen in the workspaceContains time-out? I'm willing to change the behavior.

EDIT: I've changed the behavior to no longer activate the extension if workspaceContains times out. We have received more complaints recently about this.

@alexdima that solution sounds great to me.

I didn't know you were getting new complaints about workspaceContainsTimeout. I think the change makes sense, extensions should be able to fall back on another activation event, I can mention this in release notes.


Prevent dropdown from looping from bottom to top.

I'm guessing this is feature someone added.
@arodenbeck Says it's unexpected to loop from the bottom item on a dropdown menu to a top menu.
Mac OS-X menu's do not have this behavior.

SLDS Menus loop. Closing. https://lightningdesignsystem.com/accessibility/patterns/menu/


Make the number of communities in the Browse by Community page configurable

Is your feature request related to a problem? Please describe.
In DSpace 7, there are 20 top-level communities listed on the Browse by Community page, https://demo7.dspace.org/community-list. When the user clicks on "Show More," this adds 20 more communities. This is slow for repositories with many top-level communities.

In DSpace 6 XMLUI, all the top-level communities are listed on the Browse by Community page, https://demo.dspace.org/xmlui/community-list, which allows the user to immediately explore them all. Administrators, too, want to see the entire list without multiple clicks.

Describe the solution you'd like
One solution would be to make the number of communities per page configurable with a number and the option, "all." Since the time to load the collections page in DSpace 6 XMLUI is acceptable, I don't think a large number or "all" would be a problem and would certainly be less time than waiting for multiple clicks to load the entire list.
Describe alternatives or workarounds you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Thank you very much for working on these feature requests. Does changing a setting to 0 mean unlimited, as @mwoodiupui suggested? I don't see a comment about it.

@alawvt : No, unfortunately at this time there's no option for an "unlimited" value at this time & no immediate plans for that.
The pageSize values should be one of the valid "pageSizeOptions" listed here: https://github.com/DSpace/dspace-angular/blob/main/src/app/shared/pagination/pagination-component-options.model.ts#L25   If they are not one of those values, then it'll be rounded to the nearest valid value.  As you can see in that list, the maximum you can choose is 100
This is purposeful as a value of "unlimited" is currently a bit dangerous in terms of performance.  If you have 500 top level communities and you attempt to load them all at once, the performance is very poor right now .  That's why currently we cap the max per page at 100.

@tdonohue, Thank you for that explanation. The maximum value of 100 is certainly reasonable.


header and basic set done

Maybe, it's better to take some screenshots if we want to modify the front-end pages. Especially when the components and pages get more and more complex, we may want to use screenshots and some mard to identify the changed place : )

thanks xichen this is the screenshots including the profile page


Potential contribution of more shortcodes

Hello, great minds think alike!
I had pulled together a bunch of the shortcodes I was using as well and stumbled on your site - feel free to add any you want to expand your list!

https://hugoshortcodes.netlify.app/
https://github.com/I-Dont-Remember/hugo-shortcodes

Your download one is creative, great work!

Amazing! Thank you for sharing! I collect shortcodes that are not binded to the appearance or CSS of a blog. So I add widgets to embed content from other services and something using simple HTML. From this point of view, I like your Giphy shortcode! I’ll try to add it later.

@isqua, I just want to thank you and appreciate all the efforts you've put into creating this repository.
The shortcodes proved to be quite useful.
Thanks a lot.


Match affected and fixed-by Packages

The initial commit in this PR adds CSS for the collapsed (< 1024px) responsive Bulma navbar and adjusts some template nesting.  Substantive work on matching affected and fixed-by Packages to follow.
Reference: https://github.com/nexB/vulnerablecode/issues/1287

@johnmhoran thanks! please provide screenshots and let us know when it's good to be merged

@TG1999 I just committed and tried to push my latest changes -- no tests yet, and I'm not yet able to properly sort the Package search results (but the immediate task, the new matched affected/fixed by records, look great and are properly sorted ;-) -- but immediately ran into a problem evidently because you had committed and pushed numerous changes of your own to this branch that I did not have locally.  I followed the git instruction to run 'git pull' on this branch, it seems to have been merged automatically and without reported conflicts.
I then ran git push origin 1287-resume-combining-affected-fixed-tabs successfully, no errors.  However, on this PR page, 1 test failed twice -- some codestyle test unrelated to my work -- and I see the warning This branch has conflicts that must be resolved.    I'd feel comfortable resolving conflicts locally with my VSCode, but have not yet used the GH interface for that and am a bit reluctant to click one of the links for web editor or command line or Resolve conflicts.

@TG1999 I just updated main locally, merged into my branch, resolved a few conflicts and committed and pushed.  Waiting for the GH checks to finish.
The primary goal of this issue and PR was matching the affected and fixed-by Packages, and that's now in place on the Vulnerability details page.  (I'll add a screen shot or two in another comment below.)  My next task will be to add some tests.
This PR also includes a few other items I encountered along the way:

Added version_class-based sorting to the matched affect/fixed-by records
Added a filter to encode Package URLs so that a link to a Package with a qualifiers value will properly recognize the qualifiers separator and following data.

Note:  I also tried to update the PackageSearch class in views.py to incorporate my version_class-based sorting into the get_queryset() method but could not figure out how to do that.  I tried to modify .order_by() directly and by adding a .annotate() clause (if that's the right word), but no luck.  Please let me know if you have any suggestions on how I should approach.

@TG1999 A few screen shots of the new matched affect/fixed-by Package records on the Vulnerabilities details page.
The landing page showing the Essentials tab contents and next to it, the new Affected/Fixed by packages tab.

Scrolling down the Essentials content a bit, here are the first 3 records from the new tab (plus a link to that tab):

And this is the new Affected/Fixed by packages tab when selected:

@TG1999 @pombredanne  While exploring the sorting of a variety of PURL types using purl_version_class = RANGE_CLASS_BY_SCHEMES[purl.type].version_class, I see that pkg:apk/alpine/apk@2.12.9-r3?arch=x86 is raising an exception: KeyError: 'apk'.
Although apk is listed as a PURL type (https://github.com/package-url/purl-spec/blob/master/PURL-TYPES.rst#apk), is it possible that univers handles alpine but does not yet handle apk, and thus a sort using version_class will fail for pkg:apk/*?
Not sure if this is still needed (or relevant to my question), but we import AlpineLinuxVersionRange separately from RANGE_CLASS_BY_SCHEMES and then update the latter with the former.
from univers.version_range import RANGE_CLASS_BY_SCHEMES
from univers.version_range import AlpineLinuxVersionRange

. . .

def purl_sort_key(purl: models.Package):
    RANGE_CLASS_BY_SCHEMES["alpine"] = AlpineLinuxVersionRange
    purl_version_class = RANGE_CLASS_BY_SCHEMES[purl.type].version_class
    return (purl.type, purl.namespace, purl.name, purl_version_class(purl.version), purl.qualifiers, purl.subpath)

AlpineLinuxVersionRange defines scheme as alpine but does not refer to apk.  The only univers reference I see for apk
is in alpine_test.txt.NOTICE --  "Alpine Package Keeper (apk) is a package manager developed for Alpine Linux.".

Note that alpine_test.txt.ABOUT contains a reference to an alpine PURL type:
package_url<EMAIL_ADDRESS>
but alpine is not listed in purl-spec as a PURL type and appears only under the listing for 'apk'.

I'm seeing similar key errors for some other PURL types like bitbucket, bitnami and cocoapods, so perhaps these are just examples of PURL types that are not yet covered by univers?

@TG1999 @pombredanne This PR is ready for review.  I've refactored the sort and version-class functions and added tests for these functions and for the custom quote filter.
Note: After learning that not all "known PURL types" -- https://github.com/package-url/purl-spec/blob/master/PURL-TYPES.rst#known-purl-types -- have a univers version_class, I revised the sort and version-class tests to test only PURL types currently supported by univers.
I see that once again the only failing check here is test_codestyle, which I think I've seen failing for other PRs recently as well -- no idea why it's failing or how to resolve.

Thanks @johnmhoran ! LGTM


Handle the arguments array in a way that will allow optimisation, resulting in massive performance gains.

LGTM


New version NamedTupleTools: 0.7.1

Registering: NamedTupleTools
Repository: https://github.com/JeffreySarnoff/NamedTupleTools.jl
Version: v0.7.1
Commit: 470e6e0cc8d156f3a90aee68bc94cf033c1860ce
Proposed by: @JeffreySarnoff
Reviewed by: @JeffreySarnoff
Reference: https://github.com/JeffreySarnoff/NamedTupleTools.jl/commit/470e6e0cc8d156f3a90aee68bc94cf033c1860ce#commitcomment-33451788

@JuliaRegistrator register()

You should trigger the bot from https://github.com/JeffreySarnoff/NamedTupleTools.jl/commit/f2f1522cc5a188495db2df200a4c550ca425b9bf


HSplitContainer Becomes Sticky When One Half Has Visibility Toggled and Then Dragged Off Screen

Tested versions

Reproducible in 4.3.rc3

Not reproducible in 4.2 stable

System information
Windows 11 - Godot Engine v4.3.rc3.official - Vulkan(Forward+)
Issue description
hsplitcontainer dragger is never released when one of the two halves has visibility toggled and then the dragger is grabbed by the mouse and pulled outside the viewport window. It should be released as it works when there is no panel visibility change.
https://github.com/user-attachments/assets/94c30679-df71-4ced-9ee2-bbbe7cfab999
Steps to reproduce
toggle the visibility of half of the hsplitcontainer, then grab the dragger and pull it out of the viewport. The dragger is then stuck to the mouse it is never released.
Minimal reproduction project (MRP)
hsplitcontainer_test.zip

maybe related https://github.com/godotengine/godot/issues/66273

Looks like this is happening because the window stops getting input events when the mouse leaves it if the window wasn't already focused even though it got a mouse down event. This happens easier when always_on_top is true like in the MRP.
It doesn't have anything to do with toggling child visibility and is not specific to SplitContainer.

Bisecting points to #91361 as the culprit:


Propagate validation flag on destroy dependent records

Currently flag isn't propagated

Fixed. By you :)

Oh, wait, this is for the destroy. You've already fixed the revive. I'll reopen.


Image saved to file does not have size of Frame

I am trying to generate a sequence of images with a specific size. The size is required because these images will be used for machine learning. I used the following code do set up and draw on a frame:
    val picture = Picture.circle(100).strokeColor(Color.crimson)
    val frame = Frame.default.withSize(width , height).withBackground(Color.white)

    // Using IO
    val r = picture.drawWithFrameToIO(frame)
    r.unsafeRunSync()

The output to screen seems to be what I want. However, when I save this picture the file seems to contain  a cropped image with a give margin. Here is what I do:
    val out1 = os.pwd / "circle.png"
    println(out1.toIO)
    picture.write[Png](out1.toIO)

My question is, how can I save the picture with the Frame size? Note that I also need to generate images were shapes appear in random positions and may be clipped if too close to the border.
TIA

I was looking through the code and found def write[A](file: File, frame: Frame, picture: Picture[A]): IO[A] . This seems to work:
    val out1 = os.pwd / "circle.png"
    picture.write[Png](out1.toIO, frame)

So my error. VSCode IDE intellisense does not show WriterOpsHelper and WriterIOOpsHelper methods unless I specifically look for the applymethod.
Apologies for the noise. Closing.


Improve Open Folder UI

It's happened to me a bunch of times that I clicked on Show Local instead of OK because the former is the rightmost and largest button. I think this could be improved by switching their position and maybe visually distinguishing them if the CI allows for that.

@moritz-t-w that dialog is from vscode itself not related to the remote-ssh extension, please create an issue upstream.
Thanks


GM: FPv2 support

@JasonJShuler I see part numbers for ecus in the CAN data occasionally. Want to see if you can figure out the correct response dat for our iso-tp library to parse the messages? If not I can take a look in a few weeks

Duplicate of https://github.com/commaai/openpilot/issues/22663


Laravel 5.6 compatible

When I try to install with Laravel 5.6, I get:
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Conclusion: remove laravel/framework v5.6.11
    - Conclusion: don't install laravel/framework v5.6.11
    - laravelarab/tarjama v1.6.0 requires illuminate/support 5.5.* -> satisfiable by laravel/framework[5.5.x-dev], illuminate/support[5.5.x-dev, v5.5.0, v5.5.16, v5.5.17, v5.5.2, v5.5.28, v5.5.33, v5.5.34, v5.5.35, v5.5.36, v5.5.37, v5.5.39].
    - laravelarab/tarjama v1.6.1 requires illuminate/support 5.5.* -> satisfiable by laravel/framework[5.5.x-dev], illuminate/support[5.5.x-dev, v5.5.0, v5.5.16, v5.5.17, v5.5.2, v5.5.28, v5.5.33, v5.5.34, v5.5.35, v5.5.36, v5.5.37, v5.5.39].
    - Can only install one of: laravel/framework[5.5.x-dev, v5.6.11].
    - illuminate/support 5.5.x-dev conflicts with laravel/framework[v5.6.11].
    - illuminate/support v5.5.0 conflicts with laravel/framework[v5.6.11].
    - illuminate/support v5.5.16 conflicts with laravel/framework[v5.6.11].
    - illuminate/support v5.5.17 conflicts with laravel/framework[v5.6.11].
    - illuminate/support v5.5.2 conflicts with laravel/framework[v5.6.11].    - illuminate/support v5.5.28 conflicts with laravel/framework[v5.6.11].
    - illuminate/support v5.5.35 conflicts with laravel/framework[v5.6.11].
    - illuminate/support v5.5.36 conflicts with laravel/framework[v5.6.11].
    - illuminate/support v5.5.37 conflicts with laravel/framework[v5.6.11].
    - illuminate/support v5.5.39 conflicts with laravel/framework[v5.6.11].
    - don't install illuminate/support v5.5.33|don't install laravel/framework v5.6.11
    - don't install illuminate/support v5.5.34|don't install laravel/framework v5.6.11
    - Installation request for laravel/framework (locked at v5.6.11, required as 5.6.*) -> satisfiable by laravel/framework[v5.6.11].
    - Installation request for laravelarab/tarjama ^1.6 -> satisfiable by laravelarab/tarjama[v1.6.0, v1.6.1].

Installation failed, reverting ./composer.json to its original content.

@jmcerrejon Thanks, I will solve the problem ASAP.


(GH-688) Inline context search

closes #688

I this PR Chocolatey GUI jumps to the first package title beginning with the typed letter/letters and highlights it for the DataGrid (local packages) or the ListView (remote packages) that is currently displayed. That means e.g. for the remote sources, when typing the letter 'e' it doesn't search for all remote packages starting with 'e'. It only jumps to the first package starting with 'e' in the currently rendered ListView.
Also currently it is only searching for the title and not the authors. They way I see it is that the current search field of the Chocolatey GUI also doesn't search for authors. Maybe I'm wrong with that.
Nevertheless I can't see a valid trigger to switch the search to authors. Switching the search to authors when the grid is sorted by authors isn't really transparent for the user. This would only lead to a strange UX.

@daveMueller your changes have been merged, thanks for your contribution 👍


Create release step should have a concurrency lock

Ultimately this will probably need to be in https://github.com/paketo-buildpacks/github-config but I'm capturing it here because this is the affected repo.
Currently we have multiple jobs running in parallel. This is happening because the timer is faster than the job. See below:

I think we could also reduce the frequency, but we should ensure that only one build runs at a time.

Oh, actually, it looks like we canceled the jobs when the newer one came in. I think that is probably not desirable behavior as it means we could potentially fail to create releases from specific commits - e.g. if we merge PRs too quickly.

Upon further investigation this appears to be behaving properly. Scheduled workflows have lower priority than workflows triggered by commits, so we should successfully run the workflow for each commit that comes in.
We should validate that we successfully build a release when there is a new patched USN - and that we don't cancel each in flight job when the next USN poll triggers.
Closing this.


Some tests in test_variants.py may produce segmentation faults

$ git clone https://github.com/milesgranger/cramjam.git
$ cd cramjam
$ uv venv _e
(_e) $ . _e/bin/activate
(_e) $ uv pip install -e .[dev]
(_e) $ python -m pytest -vs tests/test_variants.py
[…]
tests/test_variants.py::test_variants_different_dtypes[blosc2] Fatal Python error: Segmentation fault
(_e) $ python -m pytest -vs tests/test_variants.py
[…]
tests/test_variants.py::test_variants_different_dtypes[blosc2] Fatal Python error: Segmentation fault

In a build for Fedora Rawhide, I instead hit
tests/test_variants.py::test_variants_decompress_into[blosc2-bytearray-Buffer] Fatal Python error: Segmentation fault

This was on x86_64 only; other architectures succeeded. I’ve also had builds succeed, so it seems like this is “flaky” in practice.
This is probably related to https://github.com/cramjam/cramjam-cli/pull/2#issuecomment-2417768132, since I’ve only seen segmentation faults including blosc2 support.

Hrm, the common thing here is blosc, but in the CLI it was kinda expected since I know the cause, #160 but here I'm less certain. Especially since it's flaky.
Maybe some misuse of the blosc2 context/session thingy. I'm sorta tempted to take it out at this point until I have time to test/develop it better. However, being it's part of the experimental module I think this is okay now that I write this. By using that I think people are willfully opting into dragons. What do you think?

Hrm, the common thing here is blosc, but in the CLI it was kinda expected since I know the cause, #160 but here I'm less certain. Especially since it's flaky.
Maybe some misuse of the blosc2 context/session thingy. I'm sorta tempted to take it out at this point until I have time to test/develop it better. However, being it's part of the experimental module I think this is okay now that I write this. By using that I think people are willfully opting into dragons. What do you think?

The fact that blosc2 is in the experimental module is my justification for skipping the variant tests involving blosc2 and going ahead with shipping python-cramjam-2.9.0 and rust-libcramjam-0.6 (for which the C-API shared library doesn’t yet have any blosc2 functions) in Fedora. I don’t love the idea of shipping something with known memory-safety issues, but I agree that having it clearly marked experimental does help a lot.


Add test reproducing reported user story. Implement fix. Document edg…

Proposed Changes
Pass onValueChangeFinished further down the implementation in a way similar to onValueChangeState. Invoke it when key is released.
Testing
Test: test containing the reported using scenario is added to kotlin/androidx/compose/ui/window/window/WindowInputEventTest.kt
Issues Fixed
Fixes: https://github.com/JetBrains/compose-multiplatform/issues/2798

@MatkovIvan
Applied your changes, test succeeds, when run isolated on:

Branching commit
Commit with actual fix
Commit with your changes

@MatkovIvan
Reverted back your proposed changes on replacing || with when. IDE marks it as deprecated syntax.


Image Size limitation for registration and cv2 error

Hello @Yu-AnChen!
I produced some amazing registrations with PALOM!
Unfortunately, I have encountered and error for big images which I think is due to the size of these images.
Is there I size limitation and if yes, what is the maximum size PALOM can process?
The image size for which I encounter the error is width 54977 pixel, height 45935 (physical pixel size 0.325 um)
The error:
"/path/to/palom/block_affine.py", line 102 in lock affine
else:raise(err)
File
"/path/to/palom/palom/block_affine.py", line 90, in block_affine
warped_src_img_block = cv.2warAffine(
cv2.error:OpenCV(4.8.0)/io/opencv/modules/imgproc/src/imgwarp.cpp:1730:error: (-215:Assertion failed) dst.cols <SHRT_MAX && dst.rows <SHRT_MAX && src.cols <SHRT_MAX && src.rows <SHRT_MAX in function 'remap'
The error points towards a function of the OpenCV library. If this question should be moved there let me know.
Thank you for the help!
Best Barbara

Hey Babara, thanks for trying it out and reporting back.

Thank you for the answer!
I am working on a Linux computer cluster. I submit the script with enough memory, at least to my understanding.
Here is the resource summary of the failed job:
CPU time :                                   38.02 sec.
Max Memory :                                 10146 MB
Average Memory :                             2817.00 MB
Total Requested Memory :                     61440.00 MB
Delta Memory :                               51294.00 MB
Max Swap :                                   -
Max Processes :                              3
Max Threads :                                6
Run time :                                   276 sec.
Turnaround time :                            278 sec.

I updated palom recently, the installed version in my environment is 2023.8.1.
Thank you very much for your help!

Thanks for the details! A couple more questions 😅

Are you running palom in a conda/mamba environment? If so could you export the env package versions (info here) so that I could try to reproduce?

How big is the file size? Is that something you could share for me to inspect?

If you are comfortable with docker, palom is available in this docker image. You could use it to test if the error persists.

Hi!
Yes I am running it in a conda environment,here is the export:
spec-file_palom_env.txt
The sizes of the images are Cycle 1 34 GB, Cycle 2 20 GB, Cycle 3 28 GB. I successfully registered Cycle 1 and Cycle 2, but the error occurs when I register Cycle 3 to 1 and 2.
I unfortunately cannot share them at the moment, this might change. I understand if this makes it more difficult to find the error.
It is not possible for me to use docker directly on our computer cluster but singularity. I will try to pull it through singularity!
Thank you for the suggestion!

The script has run through without any errors and the registration looks good to me!
I think the way the script is processing the images (3 at a time) makes a different? When I got the error initially, I have registered cycle 1 and 2, and afterwards, I performed registration of cycle 3 to the already registered image consisting of cycle 1 and 2.
Attached you find the QC plots, it looks to me like the second image is rotated on the plot (which shouldn't be the case based on the raw image), but the registration worked and looks good!
I used the script to register the whole experiment (5 Cycles) and the registration looks good for all Cycles.
So this has solved my problem, thank you very much for your help!


Added Roadiz CMS - PHP

[✓] verified that the CMS I'm adding is still maintained.
[✓] read CONTRIBUTING.md.
[✓] did not generate README.md.

@faisalhmohd thank you! I'll fix that trailing slash in github_repo after I merge.


feat(axe-core-4.0.1): bump axe-core from 3.5.5 to 4.0.1

Description of changes
Update axe-core from 3.5.5 to 4.0.1, following the directions from the readme
Pull request checklist

[x] PR title respects Conventional Commits (starts with fix:, feat:, etc, and is suitable for user-facing release notes)
[x] PR contains no breaking changes, OR description of both PR and final merge commit starts with BREAKING CHANGE:
[x] (if applicable) Addresses issue: 1758928
[x] Added relevant unit tests for your changes
[x] Ran yarn precheckin
[x] Verified code coverage for the changes made

:tada: This PR is included in version 2.4.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


fs_scandir_next() sometimes returns name but no type

Hi!
After debugging for a long time why the LuaSnip plugin for Neovim doesn't load all my snippets, I think I've traced the issue to this (otherwise excellent!) library.
The documentation for luv.fs_scandir_next() states that the function either returns two strings (file name and directory entry type) or nil or it fails completely.
However, for whatever reason, on the specific machine that I use, I receive the file name as usual but nil for the entry type. (MWE at the bottom.) Because downstream Lua scripts expect either two strings or two nils, this breaks a lot of their assumptions and code starts to behave strangely.
After some digging, I think I located the issue in fs.c:126: whenever ent->type is an unknown enum value, the type is set to the string "unknown" and two values are returned as usual. However, if ent->type is the known enum value UV_DIRENT_UNKNOWN, then the type is not set at all and only one value is returned.
I'm not sure what the correct behavior is here, but I think either the code should be changed (by merging the UV_DIRENT_UNKNOWN with the default) or the docs (to inform users that sometimes string, nil is returned).
Of course, if you can think of a simple reason why the directory entry type suddenly fails to be recognized, I'd be extremely grateful for any pointers. :slightly_smiling_face:
No matter how you decide, thanks for your time and hard work!

According to https://www.gnu.org/software/libc/manual/html_node/Directory-Entries.html:

The type is unknown. Only some filesystems have full support to return the type of the file, others might always return this value.

On what OS and filesystem do you see this happening?

It's odd indeed, it took me a long time to piece together what was happening here.
I access the affected machine remotely, it's managed by our IT department. I'm in contact with them in parallel to figure out if there's something they can do.
$ cat /etc/redhat-release
Rocky Linux release 9.2 (Blue Onyx)
$ mount | grep "/home "
<...> on /home type nfs4 (rw,nosuid,nodev,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=<ip addr>,local_lock=none,addr=<ip addr>)

I wonder if the network filesystem and its inevitable lag cause any shenanigans somewhere inside libuv …

Surprised that our docs don't mention this; that should definitely be fixed regardless of whether we return nil or "unknown" as the type.
I assume the same applies to fs_readdir but the Libuv docs don't mention it there. Will need to try to test that as well.

We can make this return a "unknown" string as well, this is probably the more correct behavior here.  I remember reading the code relating this, should be an easy fix, assuming it wasn't intended behavior this shouldn't be a breaking change as well.

Personally, I think I prefer keeping it as nil, or at least keeping some way of distinguishing between 'we got a type but it's unknown--it is not one of the known types though' and 'we didn't get a type at all--it could be anything, you probably need to do a stat call to find out for sure'.

I can confirm that fs_readdir() shows the same behavior:
function Main()
  local luv = require "luv"
  local root = "<home>/.local/share/nvim/lazy/vim-snippets/snippets"
  local fs = luv.fs_opendir(root, nil, 200)
  local data = luv.fs_readdir(fs)
  if data then
    for _, dirent in ipairs(data) do
      print(dirent.type, dirent.name)
    end
  end
  if luv.fs_readdir(fs) then
    print("...")
  end
  luv.fs_closedir(fs)
end

Main()

This prints the same (lengthy) output as the original example.
Explicitly using stat on the entries that couldn't be read seems to kick the filesystem into doing its job. The following script correctly marks all files as "file" instead of nil:
function Main()
  local luv = require "luv"
  local root = "<home>/.local/share/nvim/lazy/vim-snippets/snippets"
  local fs = luv.fs_scandir(root)
  local name, type = "", ""
  while name do
    name, type = luv.fs_scandir_next(fs)
    if name and not type then
      local stat = luv.fs_stat(root .. "/" .. name)
      type = stat.type
    end
    print(type, name)
  end
end

Main()


More examples in xmldetails.md please

How to configure the input tag is not so clear:
<Input Id="FieldName" Value="RefNameOfTheField" />

What should I put as FieldName?
What about RefNameOfTheField?
Suppose I have a custom field called MyNamespace.MyField, do I put this in Id? Then what should I put as Value? FieldControl?
To specify the list of items, whether from a static list or a global list, and whether to allow existing value, still the same as previous version of TFS?

The "Id" is the name which identifies the input. This is used in the extension internally. You must not change it.
The ref name of your field is "MyNamespace.MyField".
So your input tag should look like this:
<Input Id="FieldName" Value="MyNamespace.MyField" />
The items are taken from the AllowedValues list. So, yes, this is the same as in previous versions.

@FlexiGit  Is correct. This extension defines two inputs ids FieldName and Values. For FieldName you make the value the reference name of the field. If you only specify this, then the extension will try to use that fieldName to also get the list of values from its Suggested value list. If you also specify values then it will use that list for the values to populate the control


Use COMPILE_ARGS and SIM_ARGS for xrun call.

Fixes #1000 by making Makefile.xcelium the same as Makefile.ius in that area.
The -licqueue argument is present in Makefile.ius too.

Thanks!


Fix crash when arcore not installed

@HalfdanJ You can close this PR as well. Changes are already included in #9.


Implement Input Buffers

Implement a 256-byte input buffer, so that characters can still be processed as they come into the ACIA.

Hi @jgharston, would you be able to answer a question for me if you have time?
I am unsure if I should implement my own input buffer, or try to utilise the input buffer mappings from MOS 1.20. Options include:
0 = Keyboard           $03E0-$03FF     $02CF     $02D8      $02E1       32 bytes
1 = RS-423 Input       $0A00-$0AFF     $02D0     $02D9      $02E2      256 bytes
2 = RS-423 Output      $0900-$09BF     $02D1     $02DA      $02E3      192 bytes
Does the BBC BASIC ROM have buffer processing inside it, or is it handled entirely in MOS?  See the 'buffer' branch for my first attempt at an input buffer at addresses $0800-0900. I'm still working out how to best handle buffer overflows.


TODO: https not implemented

what is needed:

https abilitity for users
programmers need to be able to give up certificates for ssl
HTTPS NEEDS TO BE ENFORCED!

able to go over https, not sure if enforced!


how works dataLength ?, different result when is a static number

Hello i am curious about how this works, let me explain
if i put in dataLength for example : arrExample.length works fine, but if i put a number , for example 20 , 1 or anothers, this only render one time ? , why this happend ?
the documentation says : set the length of the data.This will unlock the subsequent calls to next.
i am not sure but i have my theory, in this case the arrExample.length works fine beacuse every time is called the next function is re-rendered with a new value, for example if arrExample.length = 20 in the first render and in the second has 40 has value this means this only need a different number every time has re-rendered and not care if it is a any number, i only courious about this
i am right ?, how works internally ? , please if i am wrong let me know i wanna know why this happend
thanks for read and have a nice day :heart:

I think that's what it looks like, but no one explains it.


Superset is adding unnecessary Group By clause in MapBox query

A clear and concise description of what the bug is.
How to reproduce the bug

Create a new chart.
Choose a Dataset
Save the dataset
Choose mapbox in the chart options
Click on view query

Expected results
Mapbox should show results with all values of longitude and latitude.
Actual results
Mapbox only show results with distinct, unique values of longitude and latitude, and it adds a group by clause in query.
Screenshots
This is the result i am getting

Total rows should be 983:

Environment
(please complete the following information):

Edge
Using default docker-compose-non-dev.yml to set the environment

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
The mapbox works perfectly in a development environment, but this issue exists only in production environment. Is there any way to modify query so it removes the group by clause so i get all the values

I am facing the same issue ,Kindly someone please recommend the possible solution

Add the primary key, along with latitude and longitude in Dimension and the issue will be resolved.

Thank you, It works


[V0.0] Developer guide

Update the following appendices.

User Stories: Give a list of the user stories, including priorities. This can include user stories considered but will not be included in the final product.

Use cases: Give use cases (textual form) for a few representative user stories that need multiple steps to complete. e.g.

Rescheduling a task, which may require two steps: locating the task first and then updating it.
Checking a day's schedule at the end of the day: requires filtering the day's tasks, marking complete tasks as done, and rescheduling or deleting remaining tasks.
Finding something to do where here is a free time.

Non-functional requirements:
Note: User stories capture functional requirements. What are the non-functional requirements of your project? Many of the project constraints mentioned above are NFRs. You can add more. e.g. performance requirements, usability requirements, scalability requirements, etc.

Glossary: Define terms that are worth defining.

Product survey: Describe a summary of the product survey. i.e. Pros, cons, (from Jim's point of view). Each student should document the product they explored. If multiple students have explored the same product, you may have to explore more products to complete this section.

Completed specifications in the commits below -

User Stories: https://github.com/CS2103AUG2016-F12-B2/main/commit/d7962b26e384b4ead9d8b311c766c4500e03cd5e
Use Cases: https://github.com/CS2103AUG2016-F12-B2/main/commit/776ddfd562aa1511c97d795dc006f0820f0b94b6
Non-Functional Requirements: https://github.com/CS2103AUG2016-F12-B2/main/commit/70a51026bed52bd0d2f158cf8cfa7e5a1e14f275
Product Survey: https://github.com/CS2103AUG2016-F12-B2/main/commit/52860b158b92150cb9a44775bac1527f8c766fa3

There's nothing much to do for Glossary for now.
@huanhock @benwongwf can add more Product Surveys if both of you have good examples to share.
Else, can close this issue for [V0.0]

We will reopen this issue IF there's more things to add for Glossary / Product survey further down the road.


Not opening dev/ttyUSB0

Nothing happening when click on Connect

Seems that in Windows we based on COM as a base device, in Linux we should use /dev/ before port name, /dev/ = COM


Add Secret  Website

Prerequisites

[X] I am a GSSoC-22 Participant
[X] I checked to make sure that this issue has not already been filed

Description
I want to website named Secret where user can share his her secret anonmously.
Tech Stack
NodeJS

@manisha-27 @abhijeet007rocks8 Please assign I really wanna work on this issue

Already your 3 issues are in queue, but will be assigning you as soon as they get merged. Till then Good luck.


Add support for zend-expressive-authentication 0.5

Add support for zend-expressive-authentication 0.5
See: zendframework/zend-expressive-authentication#28

Thanks, @xtreamwayz!


Feature to add time items and date items manually

Another user request from my app.
Can you add a feature that the user can add there own time items and date items?
Some users don't need "Evening" with 17:00 instead they want 16:00 and so on ...
So it would be great to make the "text" and the time manually changeable.
A method like "addDropDownElements" or something like that.
So I can made a screen for the users where he can change and add time text and values.
After that I create the DropDownElements for the spinner.
The same for date.

Well technically you can do that right now with a couple of add-, remove-, and insertAdapterItem() calls, passing DateItems or TimeItems. But I know it is going to be messy as hell because the flag setting methods (and possibly others) are written without this in mind, assuming the spinner items are not changed externally. Also, adding a bunch of items at once or replacing all of them would be nice.
I'll see if I can find a way to implement that without having to rewrite the whole Adapter class breaking the flags...

Thanks, hopefully you can find a easy way. Would be a great feature.

OK so I thought about this a bit, and this is what I've come up with so far:
We'll change the items so that each TwinTextItem has an ID (haven't decided whether that has to be unique or not). Then we'd add a removeAdapterItemById method to the PickerSpinner and rewrite the various setter methods in both spinners to rely on IDs instead of position. At that point you could already manually add and remove items (and I'll add a batch add method as well), but I want to go a little further and move the spinner item creation in the getSpinnerItems() method over to an xml file which you could then easily override to provide a completely different set of spinner items.
This is quite a bit of work as I'm unsure what bugs will arise from the item removing (especially when retaining the selection), so I'll see when I get some free time. I'll first do a 1.2.1 release to maven though, if that answers the question in the other issue ;)

I think this is a good idea.
So if you find some free time let the show begin ;-)
Perfect, so I can use again the 'compile' feature once 1.2.1 is out ...
At the moment I use the downloaded project with 'compile project'...

There you go, it took some time to get a couple of bugs sorted out, but now you can easily add and remove spinner items, both from xml and at runtime. This will be in version 1.3 as there were quite a few changes needed.

Wow amazing! Thanks.. Will check this once I find time!! Thanks again for such a quick implementation!!

Implemented in release 1.3.


typo in command

given on the page:
sudo iotedge config mp --connection-string 'PASTE_DEVICE_CONNECTION_STRING_HERE'
but that does not work. so i changed in the following and that work in ubuntu 18
sudo iotedge config mp --connection-string "PASTE_DEVICE_CONNECTION_STRING_HERE"
so  change the ' in to "

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

ID: a3b8296d-c923-e990-dcad-35ef2b908a2a
Version Independent ID: 5f85fd7b-f2b6-b3b1-6be2-b6054bb33507
Content: Create and provision an IoT Edge device on Linux using symmetric keys - Azure IoT Edge
Content Source: articles/iot-edge/how-to-provision-single-device-linux-symmetric.md
Service: iot-edge
GitHub Login: @kgremban
Microsoft Alias: kgremban

@joachim-lazaroms-isolectra
Thanks for the feedback! We are currently investigating and will update you shortly.

Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@joachim-lazaroms-isolectra Thank you for your suggestion. In the context of this bash command, either single quotes or double quotes should work fine. Technically single quotes are more correct as we want the literal connection string to be passed in, without any processing of special characters that it might contain (although it shouldn't contain any).
For reference: https://www.gnu.org/software/bash/manual/bash.html#Quoting
I'm not sure why the command didn't work for you as written, but I just tested it to verify that it works on a fresh IoT Edge install on Ubuntu. At this point, we're not going to update the documentation.
#please-close

i did know about the single and double differce in bash, good information :)
would it be helpfull to reply here the error message when i use the single qoute?

I'm not sure if I'll be able to help debug the issue, but sure. I'd be interested to know what error you got.

I'm not sure if I'll be able to help debug the issue, but sure. I'd be interested to know what error you got.

I tried it today on a pi that was already successful configured
It did not give a error, so maybe, in a few weeks i will try a new pi. So closed for now.
thank you


Ranking for Schedules

Example:

2 adjacent subjects: give low minus points. (e.g. -1)
3 adjacent subjects: give high minus points. (e.g. -6)

Implemented a toggler for adjacent subjects.
Commit 66f0e5e394b3f19bc422b946e66a3bfbda84ff73


"unknown object type nil in kubernetesenv.spec" on istio addon

Istio is sometimes giving me this error during microk8s.enable istio.
error: error validating "/snap/microk8s/x1/actions/istio/istio-demo-auth.yaml": error validating data: unknown object type "nil" in kubernetesenv.spec; if you choose to ignore these errors, turn validation off with --validate=false

Based on https://github.com/istio/istio/issues/15130 it may need to be updated.

Here is an istio upgrade https://github.com/ubuntu/microk8s/tree/bug/fix-istio

Im getting this error, how to use the fix-istio branch

@pavankumarkatakam you can give it a try with sudo snap install microk8s --edge any feedback is much appreciated.


feat: implement 0xFF - SELFDESTRUCT

Since
Frontier
Group
System Operations
Description
0xFF - SELFDESTRUCT
See https://www.evm.codes/#ff?fork=merge

I can check this out:)

Hello @petarcalic99 how are you doing? Do you still want to work on this opcode?

Hey ! I am sorry i was really busy last week, i will be able to continue to work on it these days but if someone else wants to take the issue i m fine with it also.

Can I continue this ? ✌

Sure, i got stuck and don't have a lot of time right now. If you want text me on telegram so i can show you what i have done.


The code is not compilable

Issue ID
DLV-7
Risk level
Severity: Medium, Likelihood: Medium
Code segment
import "./contracts/interfaces/IBeforeTransfer.sol";
import<EMAIL_ADDRESS>

abstract contract LastPoolOwnerState is IBeforeTransfer, IERC165 {
   mapping(uint256 => address) internal lastPoolOwner;

   function beforeTransfer(address from, address to, uint256 poolId) external virtual override;

   function supportsInterface(bytes4 interfaceId) public view virtual override returns (bool) {
       return interfaceId == type(IERC165).interfaceId || interfaceId == type(IBeforeTransfer).interfaceId;
   }
}

Description
The code lacks the source code file IBeforeTransfer.sol
Recommendation
Add the missing file to the source code

The IBeforeTransfer import is used from integrated contracts.
https://github.com/The-Poolz/LockDealNFT.DelayVaultProvider/blob/8b3267ba2ec4d3d4d9dd49b5368cddd1ad3aad06/contracts/LastPoolOwnerState.sol#L4
To compile contracts on first use we use the following commands:
npm i

Download integration contracts:
npx ts-node ./scripts/fileImport.ts

Compile:
npx hardhat compile

Readme: https://github.com/The-Poolz/LockDealNFT.DelayVaultProvider#installation
We do the same thing in the github workflow:
https://github.com/The-Poolz/LockDealNFT.DelayVaultProvider/blob/8b3267ba2ec4d3d4d9dd49b5368cddd1ad3aad06/.github/workflows/node.js.yml#L33
Build statuses: https://github.com/The-Poolz/LockDealNFT.DelayVaultProvider/actions


Issues with downloading the dataset

When i try to download the dataset , the download gets cancelled on its own after some time  causing incomplete download.Please help with this , or let me know any other alternative to download the dataset.

I use this free tool for downloading large files https://xtremedownloadmanager.com it comes with parallel downloading and fault tolerance capabilities.

Can you upload the dataset to google drive for easier download ? Thanks @ssundaram21

You can download it using xtreme download manager as mentioned by @imneonizer it works


create angular recipes

A simple Angular app: https://github.com/johnpapa/angular-tour-of-heroes
{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "chrome",
            "request": "launch",
            "name": "Launch Chrome",
            "sourceMaps": true,
            "url": "http://localhost:4200",
            "webRoot": "${workspaceRoot}",
            "sourceMapPathOverrides": {
                "webpack:///./*": "${webRoot}/*"
            }
        }
    ]
}

The sourceMapPathOverrides was the important section...

/cc @roblourens

I've got a gist with launch configurations for Chrome debugging and Angular CLI.  It has configs both for ng serve and ng test.  Would you accept a PR?

@tonysneed sure, a PR would be really great!
Ideally the PR could contain a full subfolder "Angular" with a minimal sample, a readme.md and the launch config (similar to the two other subfolders).

@tonysneed @weinand I'm in the middle of prepping a VS Code blog post about Angular (angular-cli) + our Chrome debugger. Would to be able to back reference this repo.

Terrific, I'll get started on it. It's nice to have an example as a starting point. :)

@weinand @auchenberg See PR #2.

@weinand Thanks for merging my PR .. Happy to be of service! :bow:

Updated the README in PR #4.
Updated launch.json in PR #5.

Removed sourceMaps, trace, userDataDir from JSON in README.md file in PR #6.

@tonysneed @auchenberg thanks for your help on this recipe!
@tonysneed an official "Thank You" will appear in the June release notes.

@weinand Glad I could contribute! 😎


Add vignette

A nice to have. An enhancement to be tackled if there is time.

No time to write a vignette at the moment. Still, notice that the vignette builder is defined in DESCRIPTION and also package knitr is suggested. So, the pacakge is ready to support vignettes


Document errors/warns in the logs during catalog shutdown [skip ci]

Closes https://github.com/NVIDIA/spark-rapids/issues/8236
This documents an exception and WARN messages we can see while shutting down, as the spill framework (RapidsBufferCatalog) races with Spark task threads to shut down and stopping task work.

@revans2 thanks for the suggestions. I took them mostly verbatim and changed a couple of things.


Use <For /> in Status documentation

Provide the exact quote of the error or issue
We should use <For /> component when repeating a component
e.g.
<For each={items}>{(item, index) => <Text key={index} fontWeight="bold">{item}</Text>}</For>

https://yamada-ui.com/components/feedback/status
Does the docs page already exist? Please link to it.
No response
Are you willing to participate in fixing this issue and create a pull request with the fix?
None

I would like to work on this issue.

I would like to work on this issue.

Thank you! I will assign you.


add locale file for zh-TW

This is in reference to the issue https://github.com/d3/d3-format/issues/130
Added a locale file for zh-TW.
References:
https://en.wikipedia.org/wiki/Decimal_separator#Digit_grouping
https://en.wikipedia.org/wiki/New_Taiwan_dollar

I could not understand the release model. Please let me know if I need to make any modifications to the PR.

@Fil By when can we merge and release this PR?

@Fil By when can we merge and release this PR?

I am looking forward to the release of this PR. Can I get a tentative plan?
cc: @Fil

Please let me know if I can help in anyway wrt to this PR

@Fil Do you have an update on plan for merging this PR?

@Fil Do Is this package still under maintenance? If yes, Do you have a release cycle? Can you provide a clear direction on when this PR will get merged?

@Fil @mbostock would you be able to assist in the merging of this PR and publishing a new release? We also support zh-TW in our products, and need this. Thank you.

@mbostock is this library still actively maintained?

Yes, I am still maintaining this library, for whatever that means. But there is no guarantee of when I will merge this PR, or a release schedule, etc. This is a free open-source library and you are free to fork the library if you wish.
Also, JavaScript support for internationalized formatting has much improved since this library was first created, so you are probably better off using the built-in Intl.NumberFormat rather than relying on the locale files here.

@mbostock understood, thanks


Want to add VulkanMemoryAllocator-Hpp but failed

Xmake Version
v2.7.7+HEAD.da4fa3574
Operating System Version and Architecture
Windows 11
Describe Bug
Currenly I wanna add hpp binding of VulkanMemoryAllocator to this repo. I modify the xmake.lua from vulkan-memory-allocator a bit but install failed.
package("vulkan-memory-allocator-hpp")
    set_kind("library", {headeronly = true})
    set_homepage("https://gpuopen-librariesandsdks.github.io/VulkanMemoryAllocator/html/")
    set_description("C++ bindings for VulkanMemoryAllocator.")
    set_license("CC0 1.0")

    add_urls("https://github.com/YaaZ/VulkanMemoryAllocator-Hpp/archive/refs/tags/$(version).tar.gz",
             "https://github.com/YaaZ/VulkanMemoryAllocator-Hpp.git")
    add_versions("v3.0.0", '2f062b1631af64519d09e7b319c2ba06d7de3c9c5589fb7109a3f4e341cee2b7')
    add_versions("v3.0.1", '58aef30d992fea986a8ab3bf3b4c5ffece3679fb585af5700269b3d627bc6760')

    add_deps("vulkan-hpp")
    add_deps("vulkan-memory-allocator")

    on_install("windows", "linux", "mingw", "macosx", "iphoneos", "android", function (package)
        os.cp("include/vk_mem_alloc.hpp", package:installdir("include"))
    end)

    on_test(function (package)
        assert(package:check_csnippets({test = [[
            void test() {
                int version = VMA_VULKAN_VERSION;
            }
        ]]}, {includes = "vk_mem_alloc.hpp", configs = {languages = "c++11"} }))
    end)

❯ xmake project -k cmakelists
checking for Microsoft Visual Studio (x64) version ... 2022
checking for Microsoft C/C++ Compiler (x64) version ... 19.35.32215
note: install or modify (m) these packages (pass -y to skip confirm)?
in xmake-repo:
  -> vulkan-memory-allocator-hpp v3.0.1
please input: y (y/n/m)

  => install vulkan-memory-allocator-hpp v3.0.1 .. failed

_64662C8CE6DC4C4391A59D505F2EB05E.c
C:\Users\Frankorz\AppData\Local\.xmake\packages\v\vulkan-headers\1.3.231+1\0f4cca7c08ae41efa25d8d31c27328a8\include\vulkan/vulkan.hpp(26): fatal error C1189: #error:  "vulkan.hpp needs at least c++ standard version 11"
  ${yellow}> in ${bright}C:\Users\Frankorz\AppData\Local\Temp\.xmake\230318\_64662C8CE6DC4C4391A59D505F2EB05E.c
if you want to get more verbose errors, please see:
  -> C:\Users\Frankorz\AppData\Local\.xmake\cache\packages\2303\v\vulkan-memory-allocator-hpp\v3.0.1\installdir.failed\logs\install.txt
error: install failed!

Expected Behavior
no error
Project Configuration
No response
Additional Information and Error Logs
No response

check_csnippets -> check_cxxsnippets

os.cp("include/vk_mem_alloc.hpp", package:installdir("include")) -> os.cp("include", package:installdir())

os.cp("include/vk_mem_alloc.hpp", package:installdir("include")) -> os.cp("include", package:installdir())

Thanks for your reply, especially on holidays!
I try to build with your change, it complained:
F:\SDKs\VulkanSDK\<IP_ADDRESS>\include\vulkan/vulkan.hpp(457): error C2228: left of '.m_mask' must have class/struct/union
F:\SDKs\VulkanSDK\<IP_ADDRESS>\include\vulkan/vulkan.hpp(457): note: type is 'vk::FlagTraits<vma::VirtualAllocationCreateFlagBits>::<unnamed-enum-allFlags>'
F:\SDKs\VulkanSDK\<IP_ADDRESS>\include\vulkan/vulkan.hpp(456): note: while compiling class template member function 'vk::Flags<vma::VirtualAllocationCreateFlagBits> vk::Flags<vma::VirtualAllocationCreateFlagBits>::operator ~(void) noexcept const'
C:\Users\Frankorz\AppData\Local\.xmake\packages\v\vulkan-memory-allocator-hpp\v3.0.1\b1820fc4ee8d40c39f17f06e76174713\include\vk_mem_alloc_enums.hpp(442): note: see reference to function template instantiation 'vk::Flags<vma::VirtualAllocationCreateFlagBits> vk::Flags<vma::VirtualAllocationCreateFlagBits>::operator ~(void) noexcept const' being compiled
C:\Users\Frankorz\AppData\Local\.xmake\packages\v\vulkan-memory-allocator-hpp\v3.0.1\b1820fc4ee8d40c39f17f06e76174713\include\vk_mem_alloc_enums.hpp(429): note: see reference to class template instantiation 'vk::Flags<vma::VirtualAllocationCreateFlagBits>' being compiled

I guess it is a dependency version issue. So i decide to use git url instead of tar.gz to pull its submodule.
xmake.lua
package("vulkan-memory-allocator-hpp")
    set_kind("library", {headeronly = true})
    set_homepage("https://gpuopen-librariesandsdks.github.io/VulkanMemoryAllocator/html/")
    set_description("C++ bindings for VulkanMemoryAllocator.")
    set_license("CC0 1.0")

    add_urls("https://github.com/YaaZ/VulkanMemoryAllocator-Hpp.git")
    add_versions("v3.0.0", '2f062b1631af64519d09e7b319c2ba06d7de3c9c5589fb7109a3f4e341cee2b7')
    add_versions("v3.0.1", '58aef30d992fea986a8ab3bf3b4c5ffece3679fb585af5700269b3d627bc6760')

    add_deps("cmake")
    on_install("windows", "linux", "mingw", "macosx", "iphoneos", "android", function (package)
        os.cp("include", package:installdir())
    end)

    on_test(function (package)
        assert(package:check_cxxsnippets({test = [[
            void test() {
                int version = VMA_VULKAN_VERSION;
            }
        ]]}, {includes = "vk_mem_alloc.hpp", configs = {languages = "c++11"} }))
    end)

still failed.
❯ xmake project -k cmakelists
checking for Microsoft Visual Studio (x64) version ... 2022
checking for Microsoft C/C++ Compiler (x64) version ... 19.35.32215
note: install or modify (m) these packages (pass -y to skip confirm)?
in xmake-repo:
  -> vulkan-memory-allocator-hpp v3.0.1
please input: y (y/n/m)

  => clone https://github.com/YaaZ/VulkanMemoryAllocator-Hpp.git v3.0.1 .. ok
  => install vulkan-memory-allocator-hpp v3.0.1 .. failed

cl : Command line warning D9002 : ignoring unknown option '-std:c++11'
_64662C8CE6DC4C4391A59D505F2EB05E.cpp
C:\Users\Frankorz\AppData\Local\.xmake\packages\v\vulkan-memory-allocator-hpp\v3.0.1\b1820fc4ee8d40c39f17f06e76174713\include\vk_mem_alloc.h(130): fatal error C1083: Cannot open include file: 'vulkan/vulkan.h': No such file or directory
  ${yellow}> in ${bright}C:\Users\Frankorz\AppData\Local\Temp\.xmake\230318\_64662C8CE6DC4C4391A59D505F2EB05E.cpp
if you want to get more verbose errors, please see:
  -> C:\Users\Frankorz\AppData\Local\.xmake\cache\packages\2303\v\vulkan-memory-allocator-hpp\v3.0.1\installdir.failed\logs\install.txt
error: install failed!

The compile error seems to cause by my vulkan include:
#pragma once

#define VK_NO_PROTOTYPES
#define VULKAN_HPP_NO_SPACESHIP_OPERATOR
#define VULKAN_HPP_DISPATCH_LOADER_DYNAMIC 1
#include <vulkan/vulkan.hpp>
#define VMA_STATIC_VULKAN_FUNCTIONS 0
#define VMA_DYNAMIC_VULKAN_FUNCTIONS 1
#include <vk_mem_alloc.hpp>

hmmm, I am going to resolve the issue.

I guess it is a dependency version issue. So i decide to use git url instead of tar.gz to pull its submodule.

You should keep it as is, vulkan-memory-allocator-hpp doesn't actually use the submodules except to generate the bindings.
The second xmake.lua you posted is incorrect and you should stick with the first one.

If a newer official release isn't available with fixes you want, you can specify the branch or commit when using add_requires in the meantime.

It seems like the issue when vulkan-hpp work with vulkan-memory-allocator-hpp.
I also post the issue to Vulkan-Hpp:
https://github.com/KhronosGroup/Vulkan-Hpp/issues/1501#issuecomment-1474750506

has been submit to xmake-repo https://github.com/xmake-io/xmake-repo/pull/1925


Added different colors for sensors.

I made DebugColor have two fields physics and sensor that are both a Color.  DebugPlugin will receive a DebugColor and both have a Default trait.
I left some comments with some old implementations so not supper clean because I intent to add more stuff later, mostly new colors based on the RigidBody type.
So this should be able to fix #105 but can be improved upon.

Thanks :-) I'll look into that!

I've added all new colors for each body type, based on this basic color pallet.
Also made a little example for a platformer game so you can see them in a real scenario. Maybe it can be added in the main README to showcase the debug feature. (That I would say is a big plus from the bevy_rapier).

Can also add some public assets to the background to give some context.

Nice, thank you very much. I'll try to look at it tonight.


exploitdb: 2024-02-03 -> 2024-02-06

Diff: https://gitlab.com/exploit-database/exploitdb/-/compare/refs/tags/2024-02-03...2024-02-06
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 286687 run on x86_64-linux 1

1 package built:

exploitdb


[SourceKit] add qualified types in type requests

This adds the fully qualified type to the response of expression and variable type requests in SourceKit.
The qualified type can be accessed through the <key.expression_qualified_type> and <key.variable_qualified_type> keys in the response of the expression and variable type requests.

@ahoppen do you perhaps know who would be the right person to ask as a reviewer here?

While it's true that this will more than double the size of the result, since duplicated type names are shared in the string buffer, I'm not too worried about the size of the response.
That being said, having a option would be great :+1:

@swift-ci Please smoke test


Slow start script

Node: v5.4.1
OS:  OS X 10.11.5 / Darwin Stevens-MBP 15.5.0 Darwin Kernel Version 15.5.0: Tue Apr 19 18:36:36 PDT 2016; root:xnu-3248.50.21~8/RELEASE_X86_64 x86_64
I've narrowed it down to the detect-port library used. I tested out the library's CLI and got similar results.
Added a timer to the start script:
console.time('detect')

detect(DEFAULT_PORT).then(port => {
  console.timeEnd('detect')
  ...
})

Result of running npm run start
/Users/steven/my_projects/autocomplete steven@Stevens-MBP% npm run start

><EMAIL_ADDRESS>start /Users/steven/my_projects/autocomplete
> react-scripts start

detect: 75279.878ms

Wow, a minute? 😮
Is there anything unusual about your setup? Could you put some logs in its source and check where it’s spending the time? Could it be that a lot of ports after 3000 are busy on your computer for some reason?

I'm pretty sure I have a vanilla setup.
The problem is on this line:
https://github.com/xudafeng/detect-port/blob/master/lib/index.js#L64
My understanding is that the ipv4 library returns my local IP assigned by DHCP.
If I change this to 'host': '<IP_ADDRESS>', start time is almost instant. I get the Something else is running at port 3000 prompt if I run it while port 3000 is assigned.
The network stuff is out the scope of my knowledge.. Not sure what the implications are if this was just hardcoded to something like <IP_ADDRESS>.
If anyone else is having this problem on OS X, easy fix is disconnect from your network and run start.

To note, I have the same experience.
❯ create-react-app --version
create-react-app version: 0.2.0
❯ npm -v
3.10.3
❯ node -v
v6.3.1
❯ uname -ra
Darwin bonk.local 15.6.0 Darwin Kernel Version 15.6.0: Thu Jun 23 18:25:34 PDT 2016; root:xnu-3248.60.10~1/RELEASE_X86_64 x86_64

Just a little diagnostic.
❯  npm i detect-port -g
❯ detect --port 3000
This takes about 1 minute to execute.  It looks like if you have the OSX firewall enabled it will cause the long lag.  I disabled the OSX firewall and it returns instantly.

It looks like if you have the OSX firewall enabled it will cause the long lag

Thanks, this is very valuable info!
Can you check if the fix in https://github.com/facebookincubator/create-react-app/issues/302#issuecomment-236403638 also works for you?

Yea also long startup and I also have firewall enabled.
real	1m21.762s

@philstrong Does the fix in https://github.com/facebookincubator/create-react-app/issues/302#issuecomment-236403638 work for you?

I can reproduce this by turning on the firewall and enabling “block all incoming connections”.

Yes it does fix the issue @gaearon

OK, I’ll test this on Windows and release a patch today if it works cross platform.

This should be fixed in the new version. Can you please verify? Please find the upgrade instructions here.

@gaearon  https://github.com/xudafeng/detect-port/pull/4

Thank you so much! I will revert my commit and bump the version so we use detect-port again in 0.3.0.

Working for me 👍


Develop (data) fixture changes detection

duplicate of https://github.com/F-Secure/pytest-rts/issues/66