initializing source docker://docker.elastic.co/kibana/kibana:7.13.4: pinging container registry docker.elastic.co: Get "https://docker.elastic.co/v2/": x509: certificate has expired or is not yet valid: current time 2023-04-01T12:33:34+08:00 is before 2023-04-06T04:16:02Z

就是我在部署go-zero-looklook的时候，执行到这一步,  然后就报证书已过期或尚未生效的异常
docker-compose -f docker-compose-env.yml up -d
[+] Running 0/12
⠼ go-stash Pulling                                                                                3.5s
⠴ asynqmon Pulling                                                                                3.5s
⠴ redis Pulling                                                                                3.5s
⠴ jaeger Pulling                                                                                3.5s
⠴ mysql Pulling                                                                                3.5s
⠴ prometheus Pulling                                                                                3.5s
⠴ kafka Pulling                                                                                3.5s
⠴ grafana Pulling                                                                                3.5s
⠴ kibana Pulling                                                                                3.5s
⠴ filebeat Pulling                                                                                3.5s
⠴ elasticsearch Pulling                                                                                3.5s
⠴ zookeeper Pulling                                                                                3.5s
initializing source docker://docker.elastic.co/kibana/kibana:7.13.4: pinging container registry docker.elastic.co: Get "https://docker.elastic.co/v2/": x509: certificate has expired or is not yet valid: current time 2023-04-01T12:33:34+08:00 is before 2023-04-06T04:16:02Z

就是我在部署go-zero-looklook的时候，执行到这一步, 然后就报证书已过期或尚未生效的异常 docker-compose -f docker-compose-env.yml up -d [+] Running 0/12 ⠼ go-stash Pulling 3.5s ⠴ asynqmon Pulling 3.5s ⠴ redis Pulling 3.5s ⠴ jaeger Pulling 3.5s ⠴ mysql Pulling 3.5s ⠴ prometheus Pulling 3.5s ⠴ kafka Pulling 3.5s ⠴ grafana Pulling 3.5s ⠴ kibana Pulling 3.5s ⠴ filebeat Pulling 3.5s ⠴ elasticsearch Pulling 3.5s ⠴ zookeeper Pulling 3.5s initializing source docker://docker.elastic.co/kibana/kibana:7.13.4: pinging container registry docker.elastic.co: Get "https://docker.elastic.co/v2/": x509: certificate has expired or is not yet valid: current time 2023-04-01T12:33:34+08:00 is before 2023-04-06T04:16:02Z

这个错误信息提示说docker.elastic.co的SSL/TLS证书已过期或尚未生效。这可能是客户机上配置不正确或证书本身存在问题导致的。
要解决此问题，您可以尝试以下步骤：
检查客户机上的系统时钟并确保设置正确。如果时钟相差很大，可能会导致SSL/TLS证书验证错误。
尝试使用不同的网络或从不同的位置访问docker registry，以查看问题是否仍然存在。可能存在网络问题，导致SSL/TLS握手无法成功完成。
检查是否有更新版本的docker客户端可供安装。在较新的客户端版本中可能已经修复了此问题。

就是我在部署go-zero-looklook的时候，执行到这一步, 然后就报证书已过期或尚未生效的异常 docker-compose -f docker-compose-env.yml up -d [+] Running 0/12 ⠼ go-stash Pulling 3.5s ⠴ asynqmon Pulling 3.5s ⠴ redis Pulling 3.5s ⠴ jaeger Pulling 3.5s ⠴ mysql Pulling 3.5s ⠴ prometheus Pulling 3.5s ⠴ kafka Pulling 3.5s ⠴ grafana Pulling 3.5s ⠴ kibana Pulling 3.5s ⠴ filebeat Pulling 3.5s ⠴ elasticsearch Pulling 3.5s ⠴ zookeeper Pulling 3.5s initializing source docker://docker.elastic.co/kibana/kibana:7.13.4: pinging container registry docker.elastic.co: Get "https://docker.elastic.co/v2/": x509: certificate has expired or is not yet valid: current time 2023-04-01T12:33:34+08:00 is before 2023-04-06T04:16:02Z

The error message suggests that the SSL/TLS certificate used by the docker registry at docker.elastic.co has either expired or has not yet become valid. This could be due to a misconfigured clock on the client machine or an issue with the certificate itself.
To resolve this issue, you can try the following steps:
Check the system clock on the client machine and ensure it is set correctly. If the clock is significantly off, it may cause SSL/TLS certificate validation errors.
Try accessing the docker registry using a different network or from a different location to see if the issue persists. It is possible that there may be a network issue that is preventing the SSL/TLS handshake from completing successfully.
Check if there is an updated version of the docker client that you can install. There may be a fix for this issue in a newer version of the client.


[SPARK-46434][INFRA] Remove build_branch33.yml

What changes were proposed in this pull request?
This PR aims to remove the daily CI on branch-3.3.
Why are the changes needed?
branch-3.3 reached the End-Of-Life.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manual review.
Was this patch authored or co-authored using generative AI tooling?
No.

LGTM

Thanks， merged to master

Thank you, @zhengruifeng and @yaooqinn !


Use of exceptions for flow control in BlockStore sublasses cause tests (and maybe other things) to take approx 200x as long when debugging

https://user-images.githubusercontent.com/29954900/120114176-d8595680-c175-11eb-895c-e62318c353d0.MP4
In the attached video, TestMetaDataIPI.TestFour and TestSix take 144ms and 110ms respectively when run.
When debugged, they take 25.3s and 28.9s respectively.
What's taking up all this time? When I do the crudest form of profiling, i.e. break and see what it's doing, I find it in implementations of BlockStore.CreateBlockIfNeeded.
This function is trying to get the block,  creating a new one if an IndexOutOfBounds exception is thrown.
To mitigate this, introduce BlockStore.TryGetBlockAt(int offset, out ByteBuffer buffer) and make that avoid throwing IndexOutOfRangeExceptions, instead returning false when it can't find the block and true when it does.
This cuts the execution time of these tests down to about 40% of before.
Additionally, there is code in DirectoryNode.GetEntry that is catching a KeyNotFoundException and throwing a new, more informative exception when the key is missing. This exception handling can be avoided using _byname.TryGetValue(...).
This takes the  test execution time down to about 20% of before.

I've committed a fix for this, but there are many failing tests and I'm yet to determine if I've introduced breakages, so I've not made the pull request yet.

Why is help wanted?

Sorry, I think this is a mistake after long-time delaying. I forgot this issue is fixed by the PR.


feat: runtime module

link #124
Create a runtime module exposing functions like spawn
Example usage:
     let tasks = manifest_list
            .entries()
            .iter()
            .map(|manifest| {
                let cloned_manifest = Arc::new(manifest.clone());
                let file_io = self.file_io.clone();
                async move { cloned_manifest.load_manifest(file_io).await }
            })
            .map(runtime::spawn)
            .collect_vec();

        let manifests: Vec<Manifest> = try_join_all(tasks).await?;

Sorry, my bad. I thought I marked this PR ready for review, but I didn't remove the [WIP]. There are some code changes needed to resolve conflicts.
Let me know if you have any comments about the idea of the runtime module. It should be good for review.
There is a struct JoinHandle wrapping handlers from different async runtimes. Implement the JoinHandleExt trait for them so they fit in this wrapper.
The poll from async-std returns Poll<T>, but that from tokio returns Poll<Result<T, JoinError>>.  This is why we need to wrap them in our own poll.

cc @odysa Are you still interested in working on this?

I just got back from vacation today. Let me start working on it.

Made code change. Now tokio is always a dependency since traits like AsyncWrite are used. Do you have any plan for them?  I made tokio a default feature to avoid breaking change.

Now we run tests by --all-features
https://github.com/apache/iceberg-rust/blob/854171d42199f756d2ad1a81a742ce61d9299f05/.github/workflows/ci.yml#L73
Maybe we can have specific tests for tokio and async-std?

I did
cargo test --no-fail-fast --all-targets --no-default-features  --features "async-std" --features "storage-fs" --workspace

Thanks @odysa , generally it LGTM. But I think we should resolve #418 first to unblock this.

Got it. I will work on #418 first.


FileDialog multiselection support

It should be possible to select multiple files in FileDialog

Should be closed?

Closing. Assuming it's implemented by igor84


[docs] Demo HorizontalNonLinearStepper crashes

[ ] I have searched for similar issues in this repository and believe that this is not a duplicate.

Steps to Reproduce

Visit https://mui.com/material-ui/react-stepper/
Translate page "Google translate" plugin to russian language
Click to "Complete Step" 3 times
demo HorizontalNonLinearStepper crashes

Your Environment

Tech
Version

MUI
v5.5.2

netlify deploy
https://623b783c5d00500008af1795--material-ui-docs.netlify.app

Browser
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.83 Safari/537.36

I can't reproduce.

I'm closing this because there is no clue how the error happens. At least I don't think it is about the demo.


Add the PII information into our markdown files

Currently we have a boolean pii field in our per-element descriptions in our schema and in Element.kt, but it is missing from our .md files.  This task is to make the pii value show up in the markdown.
Def of Done:
[ ] In the markdown files, all element fields in all schema .md files show pii value.  Use 'Yes', 'No' instead of true/false, for readability. . (Current default is false)
[ ] re-run ./prime generate-docs and include those updates in the PR.
[ ] check with Carlos, he's working on html generation.  If he gets his PR in first, then add PII to the html as well.
This is meant to be a starter task.

pathikkothari: I am working on this one

@pathikkothari - this is done, true?

@pathikkothari - any status update on this?

@jimduff-usds Yeah, PII was added to Markdown files and merged in last week.


Windows Server DHCP 2016 - pending reboot issue

Hello,
I was trying to setup Windows Server DHCP 2016 VM from AutoLab but after running "unattend-lab" or "setup-lab" I get error message saying that there is a pending reboot.
Well, there is no pending reboot - I have already re-booted my computer couple of times.
I was able to setup Windows10 lab environment without any issues but I need AD.

The is an issue in older versions of Lability. Run the following and you should be sweet -
Update-Module -Name Lability

This project is now under new ownership. The 3.x version line is obsolete. Version 4.0.0 has been published to the PowerShell Gallery with new updates, configuration, and documentation. It is expected that this version will resolve most if not all of the problems you were experiencing. Read Updating for more information.
No further action will be taken on this issue and it will most likely be closed at some point. If you still have the same issue with the new version, then go ahead and open a new issue.

For future reference, the pending reboot problem was a Lability bug which has since been fixed.  Use v4 or later of this module.


Update free-courses-hi.md

Added machine learning tutorial in python in Hindi
What does this PR do?
Add resource(s) | Improve repo
For resources
Description
Why is this valuable (or not)?
Simple and step by step explanation.
How do we know it's really free?
It is available on Youtube.
For book lists, is it a book? For course lists, is it a course? etc.
Course.
Checklist:

[ ] Read our contributing guidelines.
[ ] Search for duplicates.
[ ] Include author(s) and platform where appropriate.
[ ] Put lists in alphabetical order, correct spacing.
[ ] Add needed indications (PDF, access notes, under construction).
[ ] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

@shrn01 Rectified linter error. Kindly merge the PR.

Thanks, and welcome to free-programming-books!


Clean up readme

Readme is a mess. The information need to be better organised.
Idea.
Should break build / testing / general info into a separate file
Need to have clear use cases for the users to use for syntax / word / libre office support so it is clear

Two new readme for documentation


Fix for failure to build against very recent ffmpeg (2020-05-02)

This is my fix to make freshplayerplugin compile on my Debian Sid system, with ffmpeg git master from 02 May 2020.
I think this is actually a fix, because simply changing the preprocessor checks from, for instance:
#if !HAVE_avcodec_free_context

to
#ifndef HAVE_avcodec_free_context

…let it build.
I just upgraded ffmpeg on my system to today's git master, and that builds with or without my patches; my week-old ffmpeg requires my patches to build however.
src/ppb_video_decoder.c:167:1: error: static declaration of ‘avcodec_free_context’ follows non-static declaration
  167 | avcodec_free_context(AVCodecContext **pavctx)

…and several others in the same file.

I just finished compiling ffmpeg; it appears that this morning's git master does allow freshplayerplugin to build without issues. So my guess is that the preprocessor defines aren't behaving as expected (!<something that is not defined> isn't working to check for undefined values; only defined ones).
My patch still appears to work with the most up-to-date ffmpeg, however, so I think my PR is still valid as it allows for ffmpeg libraries older than last week to be used.

#ifndef HAVE_avcodec_free_context

I used HAVE_ macros in a non-conventional way. Rather than just being defined only when feature is available, they are always defined, but has values of 0 or 1. That's why #if' were used instead of #ifdef or #ifndef.
I think the patch is not correct in its current state. Unfortunately, can't say how to make it correct yet.

Maybe check for a specific libavcodec version?
https://ffmpeg.org/doxygen/3.2/libavcodec_2version_8h.html


On IE11 including styles with css custom properties breaks all styling

NOTE, this occurs on any browsers that require ShadyCSS's css custom properties shim. This is currently only IE11 or older browser versions.
This is a limitation of lit-html's shady-render module. There is somewhat of a workaround, but it will only work correctly if the element has a style elements in one lit-html template, you will not be able to share styles in template parts with this workaround.
connectedCallback() {
  super.connectedCallback();
  if window.ShadyCSS) {
    window.ShadyCSS.styleElement(this);
  }
}

Same rendering issue when testing with Google's mobile friendly / rich results testing tools: https://twitter.com/igrigorik/status/994278130394124289 — those are powered by Blink M41.
Would love to see a fix for this!

It will be fixed with https://github.com/Polymer/lit-html/pull/337

Closing in favor of https://github.com/Polymer/lit-html/issues/326 which should be handled by https://github.com/Polymer/lit-html/pull/337 as noted above.


fix(authz): retry search memberships if no memberships found

relates https://github.com/caos/zitadel/issues/2760#issuecomment-996840366


Using negative and positive values on one slider?

Hello
Is it possible to have a range from -5 to +5 (0 included) and have the labels show the current value accordingly?
I tried with the settings below but somehow the labels show a different value.

from: -5,
to: 0,
step: 1,
scale: [-5, -4, -3, -2, -1, 0, +1, +2, +3, +4, +5],

Please advice
grtz
Daniel

I put in a pull request with code that can handle this.


TuneUp IMP

Add scrolling ability and also scroll ability can be enabled based on Dynamo window resizing
Add Graph Total Execution on top next to the Force Re-execute Button. The default value is N/A when graph has not been run, then become a sum of current execution total time plus previous execution total time
Add total execution time for both section
Group the results by state description instead of state enum name
Increased group font for better visualization
Updated project references to minimize local dependencies to Dynamo. While DynamoCoreWPFtests are still local dependency
Updated some styling to Tuneup for better visualization

Adjusting Dynamo window will enable scrolling now:

Default State:

After some graph run:

The whole workflow:

Does resizing the extension view also trigger scroll bar to update?

@mjkkirschner Yes

@DynamoDS/dynamo Merging as it is


Fix for python3

This fixes an attribute error caused by trying to decode a string and maintains compatibility with python2.
By default all strings in Python3 are unicode. Dropping ".decode('utf-8')" will fix an attribute error caused by trying to decode a str object.

Thank you! I had missed your PR, sorry about that. I'll fix the other one and make a release.


[BUG] Client side scripts does not load ocassionally

Describe the bug
Sometimes the client side scripts are not loaded for *.client.jsx files. I think it happens when the code is being loaded at the same time from two different iframes.
To Reproduce
https://stackblitz.com/edit/hydrogen-zansgs?file=src/pages/index.server.jsx
Expected behaviour
Client side scripts should load correctly for *.client.jsx files
Additional context
Component is loaded, but its scripts aren't loaded. For example I have a ClientCmp.client.jsx and it has useEffect(() => console.log('client loaded'), []); inside it. Ocassionally, this code is not executed. And I don't see ClientCmp.client.js being loaded in the Network tab.
The way I discovered this is, I have a separate page where I load 2 iframes of Hydrogen app. If I load 1 iframe, it works. If I load 2 iframes, it fails. If I load iframes lazily, it works.
So issue seems to happen when I load 2 iframes at the same time. I thought maybe this is related to vite but it also happens when I build and serve. Maybe it is related to React 18?
This behavior can be seen in the above stackblitz example. If you remove useShopQuery, the bug does not happen. If you remove one iframe, the bug does not also happen.

The hydration response when one page is loaded (everything works):

The hydration response when multiple load at the same time (it breaks):


add support for global filters

Add a way to pass filters for all data loaders that are used on the returned model.
In my case, I have multiple models with multiple resolve fields that have to be translated by a provided user language. Translations are loaded from an external source. Without this feature, I would have to define a language filter for every single data loader used in a model which sounds like a lot of boilerplate.

hey, thank your for your PR!
could you provide some simple code snippets for better understanding?
is it like from:
    resolver = Resolver(
        loader_filters={
            LoaderA: {'language': 'en'},
            LoaderB: {'language': 'en'},
        })

to
    resolver = Resolver(global_loader_filters={'language': 'en'})

my concern is global_filter may unexpectly overwrite other loader_filters params.

Yes, you got it right, this is exactly my use case. I was also thinking about it but the concept of overrides in the Resolver does offer more flexibility rather than being an issue. By explicitly defining everything during the initialization of Resolver and specifying a particular Loader filter, you effectively override the global filter for that loader. This approach is well-suited for scenarios where you might need to alter the global filter behavior for a specific loader. For instance:
Resolver(
    global_loader_filters={'some_filter': True},
    loader_filters={LoaderA: {'some_filter': False}},
)

This method allows for specific customization without complicating the overall structure. While the idea of raising a duplication error to prevent such overrides could be considered, it seems more restrictive than beneficial, potentially leading to inconvenience rather than adding value to the functionality.

If I got it right, in your example, the global_loader_filters plays a role like global_default_loader_filters which provides default params and can be overridden by explicitly define a specific Loader definition in loader_filters.
Resolver(
    global_loader_filters={'some_filter': True},
    loader_filters={LoaderA: {'some_filter': False}},
)

This idea is good, however I'm afraid it would be confused for developer to make it clear what's the final form of loader_filters because the final form is decided by two params at the same time.
I would prefer handling the process of building the filters at outside, for example using variable lang to keep the value.
by this way we can follow the zen of Explicit is better than implicit..
lang = 'en'

loader_filter={
    LoaderA: {'language': lang},
    LoaderB: {'language': lang},
    LoaderC: {'language': lang},
}

Resolver(loader_filter=loader_filter)

I guess you may feel annoying to import loader module and announce them explicitly, actually these restrictions are necessary to guarantee Resolver is bug free, inside Resolver it will verify that all filter attributes are provided.
you can also have a look of this file:
https://github.com/allmonday/composable-development-pattern/tree/master/src/services/sprint/tests
this case wants to prove that after cover the query & loader with testcases, there is no need to write testcases or router anymore.

Hmm, you have a point about the clarity of the final form of filters. But I'm still not convinced about explicitly building filters for every dataloader. What do you think if there is a validation for duplicated filters?
My main concern is that there is a way to pass global context across models but there is nothing similar to pass such data forward across dataloaders, it just feels unintuitive. Were you thinking about giving dataloaders access to context?

Actually, I used to have a plan to declare filter near the Loader
class Team(TeamBase):
    members: List[Member] = []
    def resolve_members(self, loader=LoaderDepend(MemberLoader, {"is_active": context["is_active"]})):
        return loader.load(self.id)

this has two potential problems:

Loaders with same filter name may have collision. It breaks the isolation between Loaders.
generating loader instance will be difficult, because loaders with different value of filter_a should be treated as two difficult loader instance.

loader itself is very special, the first LoaderDepend(LoaderA) will create the instance, and subsequences will use the cached one.
It will make things simple if we can make sure each Loader class has only one instance.

in this case, C and D can share the same LoaderY instance.
another scenario is C and D use the same LoaderY but wants different filter_a value.
the solution is to use copy_class： https://github.com/allmonday/composable-development-pattern/blob/master/src/router/sample_2/schema.py

If you have experience in using GraphQL, build schema is kind like writing the Query.

Were you thinking about giving dataloaders access to context?

actually, if you want to provide a pre-created loader instance, you can try loader_instance ~
@pytest.mark.asyncio
async def test_loader_instance_0():
    counter["n"] = 0
    root = Root()
    loader = FriendLoader()
    loader.prime('tangkikodo', ['tom', 'jerry'])
    loader.prime('john', ['mike', 'wallace'])
    result = await Resolver(loader_instances={FriendLoader: loader}).resolve(root)
    assert len(result.users[0].friends) == 2
    assert counter["n"] == 0

bad news is that you still need to declare the class (sad

Translations are loaded from an external source.

btw, @Dambre, could you pls paste some demo snippets, I'm just wondering why you have quite a few loader classes for one external source.

@allmonday graphql is the main reason I went with your library here :)
This is just a single example of a translated child class I use and there are and will be more user language specific resources. They all go into a nested structure of translateable and not translatable resources that need to be resolved.

def get_resource_field_translation_loader(model: models.Model, field: str) -> Type[DataLoader]:
    class ResourceFieldTranslationLoader(DataLoader):
        language: str

        async def batch_load_fn(self, keys: list[str]):
            queryset = TranslationModel.objects.filter(
                content_type__model=model._meta.model_name,
                content_type__app_label=model._meta.app_label,
                resource_field=field,
                resource_id__in=keys,
                language=self.language,
            )
            queryset_dict = {obj.resource_id: obj async for obj in queryset}

            def get_translation(key: str):
                translation = queryset_dict.get(key)
                return translation.text if translation else None

            return [get_translation(key) for key in keys]

    # pydantic_resolve lib uses __qualname__ to create cache key of LoaderDepend instance and it must be unique
    ResourceFieldTranslationLoader.__qualname__ = "{}.{}".format(
        ResourceFieldTranslationLoader.__qualname__,
        f"{model._meta.app_label}_{model._meta.model_name}_{field}_translation_loader",
    )

    return ResourceFieldTranslationLoader

TaskTypeTitleTranslationLoader = get_resource_field_translation_loader(TaskTypeModel, "title")
TaskTypeShortDescriptionTranslationLoader = get_resource_field_translation_loader(TaskTypeModel, "short_description")
TaskTypeFullDescriptionTranslationLoader = get_resource_field_translation_loader(TaskTypeModel, "full_description")

class TaskType(BaseSchema):
    id: str
    title: str

    async def resolve_title(self, loader=LoaderDepend(TaskTypeTitleTranslationLoader)) -> str:
        return await loader.load(self.id) or self.title

    short_description: str

    async def resolve_short_description(self, loader=LoaderDepend(TaskTypeShortDescriptionTranslationLoader)) -> str:
        return await loader.load(self.id) or self.short_description

    full_description: str

    async def resolve_full_description(self, loader=LoaderDepend(TaskTypeFullDescriptionTranslationLoader)) -> str:
        return await loader.load(self.id) or self.full_description

    default_photo_id: str | None
    default_photo: Photo | None = None

    async def resolve_default_photo(self, loader=LoaderDepend(PhotoLoader)) -> Photo | None:
        return await loader.load(self.default_photo_id) if self.default_photo_id else None

@Dambre  v1.9.0 release.


boltdb is not very scalable/HA

Is your feature request related to a problem? Please describe.

It's impossible to run multiple instances of Portainer and scale out the database without a network volume setup which also seems to overcomplicate the operation.
We frequently want to re-deploy Portainer in a b/g fashion for bug fixes, updates (customisations we do). This tends to be a problem since it's all or nothing as it can be a problem when two instances of Portainer share the same volume/database.
Backup is another "problem" — it would be simple enough to backup a stand-by (read-replica) or ETCD or RDBMS. There are solutions in this space, for boltdb there is none
LBNL, boltdb is unmaintained/archived. Though there is an active fork "bbolt" from CoreOS

Describe the solution you'd like
Replace boltdb with e.g. etcd, or a regular RDBMS. Anything with known solutions for scalability and HA.
Additional context
Add any other context or screenshots about the feature request here.

Duplicate of https://github.com/portainer/portainer/issues/523
It is in our next extensions plan.
Let's keep the discussion in one place.


SpecifiedIndex and put(): changes not reflected

Due to the nature of SpecifiedIndex the following code is not working as intended:
public void testSliceAssign1() throws Exception {
        INDArray array = Nd4j.zeros(4, 4);

        INDArray patch = Nd4j.create(new float[] {1e-5f, 1e-5f, 1e-5f});

        INDArray slice = array.slice(1);
        int[] idx = new int[] {0,1,3};
        INDArrayIndex[] range = new INDArrayIndex[]{new SpecifiedIndex(idx)};

        INDArray subarray = slice.get(range);

        slice.put(range, patch );

        assertFalse(BooleanIndexing.and(array, Conditions.equals(0f)));
    }

That happens because INDArray.get(range) for SpecifiedIndex returns detached copy from original array, and not a view. So later put() updates detached copy, not original array.
Here's implemented fix, that forces put, without get() for such cases:
@Override
    public INDArray put(INDArrayIndex[] indices, INDArray element) {
        if (indices[0] instanceof SpecifiedIndex && element.isVector()) {
            indices[0].reset();
            int cnt = 0;
            while(indices[0].hasNext()) {
                int idx = indices[0].next();
                putScalar(idx, element.getDouble(cnt));
                cnt++;
            }
            return this;
        } else return get(indices).assign(element);
    }

If that's ok for everyone, it'll be merged later

Fixed and merged

The error still exists for putScalar:
In BaseNDArray:
@Override     public INDArray put(INDArrayIndex[] indices, Number element) {         Nd4j.getCompressor().autoDecompress(this);         INDArray get = get(indices);         for (int i = 0; i < get.length(); i++)             get.putScalar(i, element.doubleValue());         return this;     }
Here, the get is not a view but a detached copy, and therefore the changes done in get.putScalar is not propagated to the original array.
INDArray original = ...; original.put(INDArrayIndex[] indices, INDArray element)
does solve the issue by copying item-by-item from the element array to the original array, but requires element to be of the same size as the original array - which could waste RAM:
val a1 = Nd4j.arange(12.0).reshape(2L, 3, 2).castTo(DataType.INT16);     println("Original")     println(a1);     val indices = arrayOf(all(), indices(0, 2), point(1))     a1.put(indices, Nd4j.onesLike(a1).muli(-1).castTo(DataType.INT16));     println("a1.put(arrayOf(all(), indices(0,2), point(1)), Nd4j.onesLike(a1).muli(-1).castTo(DataType.INT16))");     println(a1);
Is there a better solution?


bpf,chore: declare wireguard includes properly

Ran into a compilation failure due to this.
wireguard.h compiles today only because identity.h is included prior to its usage.
If code wants to use encap.h, which also includes wireguard.h, which does not include identity.h first the data-path will fail to compile.
Fix this by simply declaring wireguard.h's dependencies correctly.

/test


Build fails for electron v26.1 on opening

Electron: v26.1.0
Electron-builder: v24.6.4
Better-sqlite3: v8.6.0
When attempting to build via electron-builder I get the below error. If I adjust the node-abi version in the rebuild package from 3.3.0 to 3.47.0 it builds it without the failure but the app crashes on opening. I think it could be related to #1044
Build build failure with OG prebuild deps
This fails to build, but the application opens just fine and nothing seems to be wrong.
  • build native dependency from sources  name=better-sqlite3
                                          version=8.6.0
                                          platform=darwin
                                          arch=x64
                                          napi=
                                          reason=prebuild-install failed with error (run with env DEBUG=electron-builder to get more information)
                                          error=/Users/coltonshaw/Desktop/scripts/pcomvp-desktop/node_modules/prebuild-install/node_modules/node-abi/index.js:39
      throw new Error('Could not detect abi for version ' + target + ' and runtime ' + runtime + '.  Updating "node-abi" might help solve this issue if it is a new release of ' + runtime)
      ^

    Error: Could not detect abi for version 26.1.0 and runtime electron.  Updating "node-abi" might help solve this issue if it is a new release of electron
        at getAbi (/Users/coltonshaw/Desktop/scripts/pcomvp-desktop/node_modules/prebuild-install/node_modules/node-abi/index.js:39:9)
        at module.exports (/Users/coltonshaw/Desktop/scripts/pcomvp-desktop/node_modules/prebuild-install/rc.js:54:57)
        at Object.<anonymous> (/Users/coltonshaw/Desktop/scripts/pcomvp-desktop/node_modules/prebuild-install/bin.js:8:27)
        at Module._compile (node:internal/modules/cjs/loader:1233:14)
        at Module._extensions..js (node:internal/modules/cjs/loader:1287:10)
        at Module.load (node:internal/modules/cjs/loader:1091:32)
        at Module._load (node:internal/modules/cjs/loader:938:12)
        at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)
        at node:internal/main/run_main_module:23:47

    Node.js v20.5.1

Build success, failure to open
To ensure your native dependencies are always matched electron version, simply add script `"postinstall": "electron-builder install-app-deps" to your `package.json`
  • writing effective config  file=dist/builder-effective-config.yaml
  • rebuilding native dependencies<EMAIL_ADDRESS>platform=darwin arch=x64
  • install prebuilt binary  name=better-sqlite3 version=8.6.0 platform=darwin arch=x64 napi=
  • packaging       platform=darwin arch=x64 electron=26.2.0 appOutDir=dist/mac
  • downloading     url=https://github.com/electron/electron/releases/download/v26.2.0/electron-v26.2.0-darwin-x64.zip size=94 MB parts=8
  • downloaded      url=https://github.com/electron/electron/releases/download/v26.2.0/electron-v26.2.0-darwin-x64.zip duration=12.383s
  • signing         file=dist/mac/PCO MVP.app identityName=Developer ID Application: Colton Shaw (4UHVHSRL22) identityHash=B22AEB9D9BCF2EAAC4FAD28C290D825A19055CEA provisioningProfile=none
  • building        target=DMG arch=x64 file=dist/pcomvp-desktop-2.1.1-mac-x64.dmg
  • building        target=macOS zip arch=x64 file=dist/pcomvp-desktop-2.1.1-mac-x64.zip
  • Detected arm64 process, HFS+ is unavailable. Creating dmg with APFS - supports Mac OSX 10.12+
  • building block map  blockMapFile=dist/pcomvp-desktop-2.1.1-mac-x64.dmg.blockmap
  • building block map  blockMapFile=dist/pcomvp-desktop-2.1.1-mac-x64.zip.blockmap

I think it could be related to #1044

It is exactly that. It says " install prebuilt binary  name=better-sqlite3 version=8.6.0 platform=darwin arch=x64 napi=" so you've downloaded the broken prebuild. You need to force the package to be compiled for Electron 26 as described in that issue.

@Prinzhorn - Awesome, thanks. I didn't think that meant it was the same issue since it always downloads a prebuilt binary. So, effectively everyone on electron v26 is most likely broken? I'll close this and test the other fix though, thank you!

So, effectively everyone on electron v26 is most likely broken?

It looks like it, yes


Buttons not working

When I use the Plugin, I can see the logos going green or grey as modes or activated or not but I cant press the Buttons to switch between mods, it doesnt Work. I tried to close NVIDIA Broadcast, to restart Elgato Stream Deck as administrator and to restart my PC.

Hello, could you please tell me which version of NVidia Broadcast you are using? You can find it in NVidia Broadcast by clicking the settings cog in the top right. It should be a number like <IP_ADDRESS>.
If you open the NVidia Broadcast app, click on Camera, you should see a list of effects. When you press the buttons on the stream deck, do you see the toggles move in NVidia Broadcast?

Hi hope this finds you well! I'm having the same problem, I can see the logo turning green when I activate manually in Nvidia Broadcast App, but trying to togle using the stream deck doesn't work! I was wondering if this is something related to the language of my Nvidia Broadcast app, My system is in Portuguese from Brazil so I cannot change the language of Nvidia Broadcast that is also in Portuguese. Could you please help?

Hi, could you please attach this file: %ProgramData%\NVIDIA\NVIDIABroadcast\Settings\NvVirtualCamera\config.json so I can see if there is some language difference in your version?
Thanks!

Hi @Max0904, @cezou, I added localization support to the plugin, if you want to give it a shot: https://github.com/BackTrak/StreamDeckNvidiaBroadcastPlugin/releases/download/v<IP_ADDRESS>/com.zaphop.nvidiabroadcast.sdPlugin.zip
Quit the StreamDeck app completely, then you should be able to copy the contents of the zip to:
%AppData%\Elgato\StreamDeck\Plugins\com.zaphop.nvidiabroadcast.sdPlugin
If you can confirm it works for you, I will submit the update to Elgato.
Thanks!

Can you also send a screen shot, similar to the one I have above, showing the effect filter? I'd like to see if the text in the combo boxes is localized to your language.

Hello, thanks for the replay, here's the config.json and the screenshot, whit this new update with localization support looks like the buttons are not showing if it's enable or not, as this screenshot shows
Nvidia Broadcast is activated but on stream deck it's grayed.
config.json

Just to you know here's the translation for each item:
Remoção de ruído do vídeo (beta) = Video noise removal (beta)
Desfoque do fundo = Background blur
Substituição do fundo = Background replacement
Remover Fundo = Background removal
Enquadramento automático = Auto frame
Contato Visual (beta) = Eye contact (beta)
Vinheta = Vignette
Hope it helps.

Hi @Max0904, I had a small error in the release version that is corrected now. Could you please try again with this one?
https://github.com/BackTrak/StreamDeckNvidiaBroadcastPlugin/releases/download/v<IP_ADDRESS>/com.zaphop.nvidiabroadcast.sdPlugin.zip
Thanks!

Hi @Max0904, I had a small error in the release version that is corrected now. Could you please try again with this one?
https://github.com/BackTrak/StreamDeckNvidiaBroadcastPlugin/releases/download/v<IP_ADDRESS>/com.zaphop.nvidiabroadcast.sdPlugin.zip
Thanks!

Thank you so much! Now it's working everything!

Great! Thanks for confirming, I will send the update to the store today!


problem

In the process of repeating the code, I found that IndexError: list index out of range in parse_databases.py.

Hi @ZXXY09, thanks for the report. This code is not supported (7+ years old) and is not intended for external use; it's a reference implementation of  https://github.com/metaspace2020/metaspace.


prevent unnecessary deployment triggers

Even if config has not been changed new deployment is triggered because odo changes the order of env variables in DC definition.

This should be easy if instead of injecting ENVs we create a configMap and we inject all envs from the config map. This configMap should be done for everything odo internal (like the variables shown here).
Still, we should allow a user to inject configuration as an ENV and we still need to prevent re-ordering of the environment variables, although at least for the common scenario of bare odo this would not be a problem.

Still, we should allow a user to inject configuration as an ENV and we still need to prevent re-ordering of the environment variables, although at least for the common scenario of bare odo this would not be a problem.

yep, we need to figure out why odo generated env vars each time in a different order, this will resolve a lot of our issues.

My findings till now:

As @kadel suggested, Openshift is smart enough to detect no changes in the DC. Thus if config is not changed, update does nor trigger new deployment.

But three things always change regardless of a new deployment or no new deployment.
Status.observedGeneration, metaData.generation and metaData.resourceVersion.
The generation numbers always increase by two.

If there is a change in the config, other fields change along with the above mentioned ones.

The c.appsClient.DeploymentConfigs(c.Namespace).Update(currentDC) in PatchCurrentDC does not return the new DC with the updated Status.LatestVersion. That number changes after the new deployment is completed successfully. Thus in case of no config change, no new deployment is triggered and thus WaitAndGetDC keeps waiting until timeout.

If there is a change in the config, other fields change along with the above mentioned ones.

what other fields?

what other fields?

Depends on what was changed in the config. If max memory is changed in config, then fields related to that will be changed in the spec etc

what other fields?

Depends on what was changed in the config. If max memory is changed in config, then fields related to that will be changed in the spec etc

anything else in the status is not changed?
How does oc rollout status works, does it face the same problems?

anything else in the status is not changed?

In case of no config changed, no.

How does oc rollout status works, does it face the same problems?

My findings were based on oc get dc <dc-name>. Let me try out the rollout command and share the findings

Interestingly the field Status.observedGeneration doesn't change if we pass the same dc retrieve (without any modification) to the update call. Thus we can detect if the dc was updated or not by this field.
But in our case, this field changes, because while creating or updating the dc, the call generateSupervisordDeploymentConfig doesn't fill up all the fields. Some of these fields e.g dnsPolicy  are filled automatically by the server.
So every time we are calling update, the server detects the absence of these fields in the new dc and thus the field observedGeneration increases in value indicating that a new dc was detected. But the deployment doesn't get triggered though, probably because the main resource related fields are the same.

oc apply doesn't act smart in the case of 500Mi=512000Ki. New deployment is not triggered in this case but oc apply says that the deployment was configured with new values. So I guess fields matching won't work unless we bring each relative field to the same unit and compare.

The commands like oc rollout and oc apply all will fail in a like 500Mi to 512000Ki. So we need to come up with some other mechanism.

https://github.com/openshift/origin/blob/69c55bf03b7ea5e016221170da740297c5acbb22/pkg/apps/util/util.go#L262
Openshift detects whether to deploy anew deployment or not by comparing the two dcs. We have to modfiy our existing code base to prevent unnecessary deployments.


Category dropdown with default value

Add a global variable that is None ad the start and than became the choiced category.
Use it as a default in the dropdown to have a choice each time the page is changed

Change this issue to: write the category in the timer countdown text field


Add ability to resolve attr for view styles

Currently, setting the font to an attr value causes it to look for a font named - for example - "?attr/myThemeSpecificFont" instead of resolving it to the theme's value. This adds support for setting fontPath to an attr value per view.

Quite nice addition. checking the value for ?attr seems odd. This should work without any special use case. (as in when resolving the style it should work out the reference for us).

For example. context.obtainStyledAttributes(                 attrs, com.android.internal.R.styleable.View, defStyleAttr, defStyleRes); will resolve background resource correctly when you do: android:background="?attr/backgroundWindow" etc.
This might be an underlying issue with the way we resolve the fontPath attribute.

I haven't fully tested every case to make sure absolutely nothing broke - would be nice if it were possible to have sent this as a fix - maybe I just don't know GitHub as well as I know git but I didn't see how to do that. As far as resolving ?attr properties, it's been working wonderfully though.
I included a check for "?" to offset any possible notable performance hit (I did notice a few StackOverflow comments mentioning some portions of attr resolution using iteration), but I ended up going the route I did as obtainStyledAttributes was resolving to android.R instead of my application's package, even with the given context (From the examples I was reading, that shouldn't be the case - not sure if it's a bug or just my own misunderstanding of how obtainStyledAttributes should work)
The main purpose of doing this is the fact we have a product with a theme for the visually impaired that gets changed onCreate - and I needed a way to switch 4 different fonts. I was also under the impression that ? and @ were supposed to auto resolve, but as this library does make use of classes with minimal documentation as Google intended them for internal use, I'm sure you understand how difficult it was to make complete sense of how the system works internally.

@jlandrum @string/myFontPath will autoresolve, if not then that might be bug which is causing the issues you are seeing.
I wonder if changing the activity theme breaks it as you would need to recreate the baseContext with the new theme to lookup. When you change the theme do you recreate the activity?

Sorry, when I said "? and @" I meant that parts of the documentation imply that it will resolve both but it only resolves<EMAIL_ADDRESS>

Ahh OK, that is odd then. :/
On Thu, 9 Jul 2015 15:48 James Landrum<EMAIL_ADDRESS>wrote:

Sorry, when I said "? and @" I meant that parts of the documentation imply
that it will resolve both but it only resolves<EMAIL_ADDRESS>—
Reply to this email directly or view it on GitHub
https://github.com/chrisjenx/Calligraphy/pull/187#issuecomment-120009305
.

We came across this issue when trying to supply custom attribute to fontPath in styles.
  <declare-styleable name="ProjectTheme">
    <attr name="fontPathPrimary" format="reference"/>
  </declare-styleable>

  <style name="TextAppearance.Project.Headline1">
    <item name="android:textSize">@dimen/project_text_size_headline_1</item>
    <item name="fontPath">?attr/fontPathPrimary</item>
  </style>

Is this related to this merge? Any plans on pushing this forward?


[stable/keycloak] parameterize path of the docker-entrypoint script

Signed-off-by: Miguel Ruiz<EMAIL_ADDRESS>What this PR does / why we need it:
After updating keycloak version to 4.5.0.Final, it becomes useful to parameterize the path to the docker-entrypoint script to make easier for the chart to work with previous versions of keycloak
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/ok-to-test

/lgtm

/assign @unguiculus

The current release adds features which are not backwards-compatible (e. g. DNS_PING). Thus, it doesn't make sense to make the path configurable.


terraform/environments/electronic-monitoring-data/gateway_endpoint.tf…

… added

@madhu-k-sr2 Terraform plan evalaution detected changes to resources that require approval from a member of @ministryofjustice/modernisation-platform

@madhu-k-sr2 Terraform plan evalaution detected changes to resources that require approval from a member of @ministryofjustice/modernisation-platform

Withdrawn.


Java MalmoJava DLL not found

Help needed. Thanks.

MalmoJava.dll is actually in the directory.

Same

Try to install Microsoft Visual Studio 2013 redistributable(here: https://www.microsoft.com/en-us/download/details.aspx?id=40784)

Thank you for replying. I had Microsoft Visual Studio 2013 redistributable (x64) installed before.

I am facing the same issue. Can anyone please help?

I had the same issue. This solution from @timhutton solved my problem: https://github.com/Microsoft/malmo/issues/156#issuecomment-231459982

After I set PATH to "C:\Program Files (x86)\CodeSynthesis XSD 4.0\bin64"(no quote), I still had the same problem. I checked my system doesn't have directory "C:\Program Files (x86)\CodeSynthesis XSD 4.0". What is that?
Thanks

After I set PATH to "C:\Program Files (x86)\CodeSynthesis XSD 4.0\bin64"(no quote), I still had the same problem. I checked my system. It doesn't have a directory "C:\Program Files (x86)\CodeSynthesis XSD 4.0". What is that?
Thanks

I had the same issue,
make sure your JAVA_HOME variable is set to point to the folder of your jdk not the bin.
then add the absolute path of the bin folder of your java jdk to the PATH variable
example
JAVA_HOME: C:\Program Files\Java\jdk1.8.0_91
PATH: C:\Program Files\Java\jdk1.8.0_91\bin
also make sure the source files are in the PATH directory as well as your python folder. so this is how my PATH looks like:
PATH: C:\Program Files\Java\jdk1.8.0_91\bin; C:\Users\Sein\Desktop\ffmpeg-latest-win64-static\bin; C:\Python27
Then restart your computer and hopefully it would work

check this page:
https://github.com/Microsoft/malmo/blob/master/doc/install_windows.md
Download and install the third dependency "CodeSynthesis"

I have all others but not C:\Users\Sein\Desktop\ffmpeg-latest-win64-static\bin, nor C:\Python27. Do I have to all those software?

I have all others but not C:\Users\Sein\Desktop\ffmpeg-latest-win64-static\bin, nor C:\Python27. Do I have to install all those software?

Yes. Refer to this link.
Download all non optional dependencies and the optional ones that you want to work with

OK. Thanks.

It looks worked. Does the sample only run a few steps as in the picture?
Thanks.

Yes. Refer to this tutorial if you haven't already:
https://github.com/Microsoft/malmo/blob/master/Malmo/samples/Python_examples/Tutorial.pdf

Not yet. Thanks.


ARROW-1090: Improve build_ext usability with --bundle-arrow-cpp

This is based on a blackbox understanding of the build toolchain. It might be cleaner to update FindArrow.cmake, but I'm not sure what the consequences of that would be. This shouldn't be able to do much harm, since this codepath would previously crash.

thank you for the contribution!


static website option unclear

static web hosting is no longer in preview.
It is not obvious how to point to the web container instead of default blob origin.  Selecting custom origin type is not enough

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

ID: 339692e2-c35e-cf53-89c9-894c2d851f1f
Version Independent ID: f95242d1-b3f3-4bf3-089d-10ac447159fa
Content: Use Azure CDN to access blobs with custom domains over HTTPS
Content Source: articles/storage/blobs/storage-https-custom-domain-cdn.md
Service: storage
GitHub Login: @MichaelHauss
Microsoft Alias: mihauss

#reassign: @normesta


[BUG] offset_sweep() fails when passed a region

Describe the bug
Rounding module offset_sweep() fails when provided regions in BOSL2 version 2.0.716, but works as expected in BOSL2 version 2.0.652
Code To Reproduce Bug
include <BOSL2/std.scad>
include <BOSL2/rounding.scad>

rectPath = rect([40, 60]);
rectRegion = make_region(rectPath);
manualRectRegion = [rectPath];

echo("Conforming that rectPath is a path", is_path(rectPath));
echo("Conforming that rectRegion is a region", is_region(rectRegion));
echo("Conforming that manualRectRegion is a region", is_region(manualRectRegion));

// This command works in version 2.0.652 and version 2.0.716
*offset_sweep(rectPath, height = 20);

// This command works in version 2.0.652 but not in version 2.0.716
*offset_sweep(rectRegion, height = 20);

// This command works in version 2.0.652 but not in version 2.0.716
*offset_sweep(manualRectRegion, height = 20);

Expected behavior
Each of the three commands provided should produce a cube with the dimensions [40, 60, 20]. offset_sweep() began to throw the error after I updated versions of the BOSL2 library.
Error Message: (extra path info removed from the file path)
ERROR: Assertion 'is_region(region)' failed: 2 in file .../OpenSCAD/libraries/BOSL2/attachments.scad, line 2946
TRACE: called by 'attach_geom' in file .../OpenSCAD/libraries/BOSL2/attachments.scad, line 2597
TRACE: assignment to 'geom' in file .../OpenSCAD/libraries/BOSL2/attachments.scad, line 2596
TRACE: called by 'attachable' in file .../OpenSCAD/libraries/BOSL2/rounding.scad, line 1656
TRACE: called by 'if' in file .../OpenSCAD/libraries/BOSL2/rounding.scad, line 1654
TRACE: call of 'offset_sweep(path = [[[20, -30], [-20, -30], [-20, 30], [20, 30]]], height = 20, bottom = [], top = [], h = undef, l = undef, offset = "round", r = 0, steps = 16, quality = 1, check_valid = true, extra = 0, cut = undef, chamfer_width = undef, chamfer_height = undef, joint = undef, k = 0.75, angle = 45, convexity = 10, anchor = "origin", cp = "centroid", spin = 0, orient = [0, 0, 1], atype = "hull")' in file .../OpenSCAD/libraries/BOSL2/rounding.scad, line 1647
TRACE: called by 'offset_sweep' in file , line 16
Compiling design (CSG Products generation)...
Geometries in cache: 802
Geometry cache size in bytes: 1132360

Screenshots
Not applicable
Additional context
Add any other context about the problem here.

OpenSCAD Version: OpenSCAD version 2023.12.09 (git 3d094bf87)
Other libraries used: None

I'm finding actually the reverse behavior, that it fails when given a path and succeeds only when given a region.  (Note that offset_sweep doesn't really accept regions----only regions that have a single component.)
The fix for the problem I'm seeing is to change the attachable call in module offset_sweep to read
        attachable(anchor,spin,orient,region=force_region(path),h=h,extent=atype=="hull",cp=cp){

(line 1656 of rounding.scad)  But if you're seeing a reversed problem, not sure what's going on there.

I think this is fixed.  All three forms are working.  If it isn't, reopen the issue.

Here is a screenshot of what OpenSCAD generates when I call it on my machine..

I don't know if it is relevant, but I'm using a Windows machine, and in my OpenSCAD preferences I have both fast-csg-safer and manifold enabled.

Just got your message, I will download the latest version of the library and try it. Thank you.

I think this is fixed. All three forms are working. If it isn't, reopen the issue.

After downloading the latest version of the library all three commands now work as expected.

Thank you for resolving this issue so quickly.


duplicate flag

[Systemd] ❯ fleek show
Error: unable to redefine 'l' shorthand in "show" flagset: it's already used for "level" flag

Fleek version 0.9.16


Added @media query so the website is responsive

Fixes Issue #4
Changes proposed -- added @media queries so the website is responsive through all views!
Screenshots
Below are videos of how the website will look across different views:
Desktop View:
https://user-images.githubusercontent.com/94648837/192097511-51f7fa87-f903-405c-b4f7-784e977e7d07.mov
Tablet View:
https://user-images.githubusercontent.com/94648837/192097521-5d7990bd-a1e3-4ae5-9e74-2ea0bad81ae8.mov
Mobile View:
https://user-images.githubusercontent.com/94648837/192097526-443fcf3e-cf2f-4351-881e-465b63695021.mov

If you can make this changes, that would be great!

In mobile view fix the freelancer and open source contributor titles alignment.
hide navLinks in movie view only show github and twitter

@RakeshSangem That's not a problem, I'll fix  the freelancer and open source contributor part, so on mobile view you don't want the link and the toggle button, just the github and twitter buttons? Also should I put them side by side with the logo in mobile view since there is space or do you wish to keep them in a column layout?

@RakeshSangem That's not a problem, I'll fix the freelancer and open source contributor part, so on mobile view you don't want the link and the toggle button, just the github and twitter buttons? Also should I put them side by side with the logo in mobile view since there is space or do you wish to keep them in a column layout?

Yeah, In mobile view we don't need navigation links as it is single page website. And the GitHub and Twitter icons should be in row only.

Fixed the description alignment issues and removed the links on mobile view, I left the toggle switch as it seemed an important button for the user
New look on mobile view:
https://user-images.githubusercontent.com/94648837/192098483-5de4fd2d-ea37-4f45-b63d-a7d9af91cd6c.mov

Looks good to me. Thanks for contributing❤

@RakeshSangem Thanks for letting me. :)


restore values support

this has probably been dropped after the rework. test included :)

greate work, thanks!


token-2022: integrate memo into confidential extension

Confidential transfers without memo do not fail even if the destination accounts are extended to require fees. This PR fixes this so that confidential extension can work with the memo extension.

@mvines Can you take a quick look at the changes here for sanity? Since a memo instruction must immediately precede the token instruction, I moved the proof instructions to be immediately after the token instruction rather than immediately before.


pannellum max size

hi
i have an image with 5700 px.
when pannellum loaded show this error:
This panorama is too big for your device! It's 5726px wide, but your device only supports images up to 4096px wide. Try another device. (If you're the author, try scaling down the image.)
how to do?

Use an image editor and scale down the image. I don't know how I could make it any more obvious.


PR for #1297

A PR for mssql dialect tablecompiler.js Create Table logic incorrect #1297

This should have also test case for the fix.

@gmcdowell Any update on this one? Would be great to get it published with 0.11.

Apologies. Family stuff going on at present. Will try next week

Closing this as #1362 is merged.


Fix AddNusMods

Fix event generation : AddNusMods/AddNusMod seems to be erroneously creating more timeslots (edit: it's actually because the day of week weren't being considered previously).
Improve AddNusMods/AddNusMod commands to also add exam dates.

Another issue: lesson numbers are not unique within a module, rather it is within a lesson type, e.g. lecture, tutorial, etc. Thus, need to check for lesson type first then lesson number.

Another issue: Forgot to consider recess week in generating timeslots


[Chore]: Add AppWorkload.spec.buildRef

Background
To support the idea of a combined builder-runner component (as opposed to separate deployments to reconcile BuildWorkload and AppWorkload), we need to provide a way to link the AppWorkload to the CFBuild that generated its image.
Action to take

Add the same spec.buildRef field to AppWorkload that exists on BuildWorkload
Change the CFProcess controller to set this field on AppWorkload

Impact
After this change, alternative build+run implementations will be able to connect a BuildWorkload and AppWorkload together based on their namespace and spec.buildRef fields.
Dev Notes
No response

It sounds wrong to have the lower level resources (AppWorkload/BuildWorkload) depend on the higher level ones (CFBuild): how does this work? Does the buildRef have to be a CFBuild or is it more of a duck type?

@gcapizzi buildRef is a direct reference to a CFBuild in the same namespace. The goal in adding this was to have a single field to link Build and AppWorkloads from the same "origin" so that they can be connected easily by a combined builder+runner. There may be a better way to do this, though, that doesn't directly link to a higher level resource, like you mentioned.
When I was first writing this, I had it as a buildWorkloadRef, but then I saw that BuildWorkload already had buildRef so I went with that. BuildWorkload.metadata.name. That would also allow us to remove the buildRef field on the BuildWorkload, since we clearly weren't using it before (it was empty in practice). What do you think?

Definitely much better for AppWorkload to refer to BuildWorkload as at least they're at the same level of abstraction. Question: if it's just correlation we're after, can't we just have some sort of correlation id? Maybe as a label/annotation?

A correlation ID could work, but I'm not sure I see a benefit to making it more abstract when the link we want to establish is that the AppWorkload is running the output of a specific BuildWorkload.
RE labels and annotations, I've generally avoided using them in a "load bearing" way, since they're not a codified part of a CRD that we can easily validate (short of a validating webhook)

The problem I see is that this link is not necessary something runners and builders will want to establish most of the times, as they're usually separate and decoupled implementations - if a specific implementation does, then I'd rather see that solved via metadata.

While not every implementation will use the field, it will be essential information for those that do. If we change the label format or stop including it, those implementations will break without warning. If we keep that information in the spec, then it can be required in the schema and schema changes will be advertised through the CRD.

I might be a bit late to the party, but having a reference to the build workload in the app workload spec sounds weird to me. From my point of view, as a kubectl user, I should be able to get any object's spec, use the same namespace and a different name in the metadata, and as a result get a valid appliable yaml. In other words, my understanding of the spec is 'input args to create an object'.
Now having the buildworkload reference in the spec violates this understanding as an app workload created the way above would simply not be related to that build workload.
Having said this, I feel that the right place for this reference is the app workload status, rather than its spec. Then controllers that find this reference important  could set a 'valid' condition on the app workload, and controllers that do not care would do nothing.

@danail-branekov The goal here is to help the runner identify which BuildWorkload build the image used in this AppWorkload, for cases when the builder and runner coordinate or are the same component. The reconciler owns the status field and korifi only ever sets metadata and spec fields. Given that, this information can't live on the status field.
Given the lack of agreement on this, I'm going to revert the merge commit for the PR that implemented this chore. A hypothetical builder-runner may be able to do the correlation based on the image URL alone, so we may not end up needing this feature. I'll write up a new issue and solicit feedback if that proves not to be true.


fix bad performance caused by creating Status::RuntimeError (#28362)

Proposed changes
Pick #28362 from master
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Chapter 7. Hugging Face's Efforts: Ethics and Society

Hey team members, this is the issue for the final chapter of Unit 12: Ethics and Bias.
Main issue: https://github.com/johko/computer-vision-course/issues/51
Sub-tasks:

[x]  Include efforts of Hugging Face in emphasizing Ethics for Society
[x] Hugging Face's mission for transparency and reproducibility
[x] 6 categories of submission of HF Spaces
[x] Focus on CV models
[x] Links for Discord and Spaces
[x] Final structuring
[x] PR
[x] Push to main
[x] Reviews and Edits

Closing the issue as content was successfully merged here: https://github.com/johko/computer-vision-course/pull/170


Tree: Clicking on folder twisties should expand/collapse

Hello,
I have the "workbench.list.openMode" option set to "doubleClick", so the folders are opened after double-clicking.
But if you click the arrow:

then the folder is expanded with one click (this demarcation is very helpful)
Can you add an option that will make the folder icons behave like the default arrows?
I would like to hide the arrows, keeping the one-click function on the folder icons

This reproduces on themes like Ayu in which the twisties are hidden and only the folders show.

With the latest changes, folders actually expand on single click, despite this setting. I think this is actually good behavior since nothing really opens when you click it. Let's see if users complain.


[Bug]: Version 29.2.1 breaks default imports

Version
29.2.1
Steps to reproduce

Clone https://github.com/flovouin/ts-jest-default-imports-bug/.
Run npm i && npm run build. TypeScript compilation should succeed.
Run npm test.

Expected behavior
npm test should pass with no error.
You can install ts-jest version 29.2.0 instead and see it succeed.
Actual behavior
$ npm test

><EMAIL_ADDRESS>test
> NODE_OPTIONS="$NODE_OPTIONS --experimental-vm-modules --no-warnings=ExperimentalWarning" jest

 FAIL  src/index.spec.ts
  ● Test suite failed to run

    src/index.ts:2:28 - error TS2351: This expression is not constructable.
      Type 'typeof import("[..]/node_modules/i18next-fs-backend/cjs/index")' has no construct signatures.

    2 export const backend = new Backend();
                                 ~~~~~~~

Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        0.38 s
Ran all test suites.

For what it's worth, even though I wasn't expecting to see the CJS version imported, node_modules/i18next-fs-backend/cjs/index does exist and export a default class.
Debug log
ts-jest.log
Additional context
No response
Environment
System:
    OS: macOS 14.5
    CPU: (10) arm64 Apple M1 Max
  Binaries:
    Node: 20.12.1 - ~/.asdf/installs/nodejs/20.12.1/bin/node
    npm: 10.8.2 - ~/.asdf/plugins/nodejs/shims/npm
  npmPackages:
    jest: ^29.7.0 => 29.7.0

I could understand why it worked at 29.2.0 because we always used target: ESNext for ESM mode and Node16/NodeNext wasn't taken into account.
For some reasons, ts-jest starts throwing type error related when taking into account of Node16/NodeNext in your case.
As a workaround, you can use target: ESNext which should fix the issue

Thanks for the reply! Indeed, updating the Jest configuration does the trick:
  transform: {
    "^.+\\.ts$": ["ts-jest", { useESM: true, tsconfig: { module: "ESNext" } }],
  },

I'll let you keep the issue around or close it depending on how you want to address this. In my case it's probably an acceptable compromise, even though I may create new problems down the line.


[Question] Obsolete parameters?

Prior to the June Preview the launch.json did contain the following two parameters:
        "projectRoot": "${workspaceRoot}",
        "packageFileName": "${command:resolvePackageFileName}",

These give errors in the June Preview. Are they now obsolete parameters?
If so, please remove them from the sample projects.

That's right, these parameters are now obsolete. We will clean up the samples.

Thanx for the quick response


Handle yet another kind of Windows close exceptions

See failing external tests on (windows-latest, 1) here: https://github.com/toitlang/toit/actions/runs/4329728718/jobs/7560479748.


Downloads page archive link should be https

Noticed this while working on some automation. We're https everywhere else in this page, just not this link.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
0m 36s
Docker mode activated.

_ Other Tests _

:green_heart:
asflicense
0m 21s
The patch does not generate ASF License warnings.

58m 37s

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-622/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/622

Optional Tests
dupname asflicense mvnsite xml

uname
Linux 39c4dc3300dc 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-622/out/precommit/personality/provided.sh

git revision
master / 1dcc8ee50c

Max. process+thread count
96 (vs. ulimit of 10000)

modules
C: . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-622/1/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z)

Powered by
Apache Yetus 0.11.0 https://yetus.apache.org

This message was automatically generated.

I missed that this didn't include a jira key in the commit message. I'll repush with one. next time please include it.


How can I specify the entity field to be shown in UI when setting up a one to one composition?

First of all, I would like to sorry for asking my doubts on this platform.
I came across a scenario where I want to setting up a relation, a one to one composition, between entities for eg, Country and Region. My intention is to configure relationship in such a way that I can select the 'regionCode', when am creating a Country. Please see below relationship created.Now am getting a value 'undefined' in the select field for region.

Kindly help me to sort it out.

The command

Replace the content

The stacktrace
Paste it here!

Steps to reproduce

The XMI file

Versions

JHipster
JHipster UML

JHipster Version
jhipster-uml -v

I suggest you read the doc, here. Search for Declare the field you want to use to display a relationship in AngularJS. It works for every type of relationship.

Thanks Mathieu.
That is exactly what I did. But the otherEntityField is not showing up, intead it is showing 'undefined'.
I have specified the table name in braces for each entity. Will that be a problem?

The table name shouldn't be used, the class name should be however.


Fix regression in zip by escaping all args

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context
After I carried out some refactoring work in #19149, I mistakenly introduced a regression with argument escaping that was raised in #19203 and partially patched in #19207.
I say partially because prior to my regression, all input (including :password) was escaped and also my new inputs (:include and :exclude) should also have been escaped when invoked as a shell command.
My intention with the original refactoring was to rely on sh_helper.rb’s internal implementation that uses shelljoin and properly escapes the arguments passed in however I got caught out by some legacy behaviours that operate in a very similar way
Actions.sh Behaviours
Actions.sh("git diff My Project.xcodeproj")
# $ git diff My Project.xcodeproj
# ❌

Actions.sh("git", "diff", "My Project.xcodeproj")
# $ git diff My\ Project.xcodeproj
# ✅

cmd = ["git", "diff", "My Project.xcodeproj"]
Actions.sh(cmd)
# $ git diff My Project.xcodeproj
# ❌

Actions.sh(*cmd)
# $ git diff My\ Project.xcodeproj
# ✅

This regression/fix focuses on the last two examples. It turns out that example three is supporting legacy behaviour that does not escape any of the arguments whereas example four will escape each argument just like example two.
This is because the use of the * is Ruby magic to convert the array into a variable argument list just like the one used in the second example.
Description
The fix itself is simple. It involves adding the * and reverting the manual escaping of individual arguments.
In addition to this though, I have had to update the specs to expect the variable list of arguments instead of arrays. I’ve also reworked the spec that ensures that the arguments are escaped to be more of a sanctify check since the only real way to check without doing a full on integration test is to see if UI.command prints the right output.
Finally, I’ve added an extra test to sh_helper_spec.rb just to document the intention of not escaping array arguments.
Moving forward, there is probably some work to be done to clear up confusion here but Actions.sh is so frequently used both in fastlane and in plugins that it would be a massive effort to remove the legacy behaviour and clear things up. I’d be happy to try and help in the efforts though but I don’t really have a good plan of my own.
Testing Steps
The same steps from #19207 apply

cc @crazymanish


Add ability to get currently displayed page text from ePub

Please add a method to to get text from currently displayed page.
Whats would this enable:
It would be helpful to implement accessibility options i.e. text-to-speech implementations.
Or ability to get a copy of text if the ePub might be educational for example.
Ability to create implementation for citations.
etc....
Personally i would love if it was in one of two formats:
a) A method accessible through ref you can manually call.
b) A callback that is fired on page change.
I personally favor option a but this is only an opinion.

What are the use cases for the text of the currently displayed page instead of the whole text of the publication or current chapter?

TTS is supported in Readium, and can start from the current page. It's not available yet in the React native package though.
For the translation, you can get the text of a user selection and translate it. Translating the current page but not the full chapter would be complicated, and I don't really see the use case.

What languages does readium support for tts when it gets implemented in react native? Can it be customized? Will it parse language specific characters? All these questions can have an answer if the developer has access to implement custom tts. Not all books have chapters short enough for reasonable tts synthezizing in one batch and user selection is not always reliable or user friendly. Sadly o dont speak java or swift to open a pull request myself

@elraito I'm going to close this issue in favor of the preexisting TTS issue. https://github.com/5-stones/react-native-readium/issues/24

The TTS in Readium is made of several independent components:

A Content Iterator API which is used to extract the text (and more) from a publication. This is useful for TTS but also other use cases like search or to reformat the content in a custom view (accessibility reader).
A Decorator API which is used to draw decorations on the pages. This is used to highlight the speaking sentences in the context of TTS.
The TTS engine itself, that speaks utterances (sentences). You can provide your own TTS engine for full customization, but Readium provides a default implementation using the native TTS APIs on each platform, which support many languages. Users can add more languages from the system settings.

Not all books have chapters short enough for reasonable tts synthezizing in one batch and user selection is not always reliable or user friendly. Sadly o dont speak java or swift to open a pull request myself

The TTS in Readium is made of several independent components:

A Content Iterator API which is used to extract the text (and more) from a publication. This is useful for TTS but also other use cases like search or to reformat the content in a custom view (accessibility reader).
A Decorator API which is used to draw decorations on the pages. This is used to highlight the speaking sentences in the context of TTS.
The TTS engine itself, that speaks utterances (sentences). You can provide your own TTS engine for full customization, but Readium provides a default implementation using the native TTS APIs on each platform, which support many languages. Users can add more languages from the system settings.

Not all books have chapters short enough for reasonable tts synthezizing in one batch and user selection is not always reliable or user friendly.

Sentences are never synthesized by the TTS engine in one batch. Utterances are computed lazily for a whole chapter, but synthesized/spoken one by one when needed.
I'm asking all these questions to see if something is missing in the core Readium API. In any case you should be able to inject your own JavaScript for unusual use cases.


v1.1.1

Fixed ne constraint bug.
Added some methods for the AnnealResults object.
Testing .lgtm.yml file.

Codecov Report

Merging #15 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #15   +/-   ##
=======================================
  Coverage   97.78%   97.78%
=======================================
  Files          90       90
  Lines        5920     5920
  Branches      649      649
=======================================
  Hits         5788     5788
  Misses         79       79
  Partials       53       53

Continue to review full report at Codecov.

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


Document Windows prefix RKE cluster YAML additions #2659

https://github.com/rancher/docs/issues/2659

We need to assign someone else from the Windows team to review this PR because Luther no longer works here.

Closing this PR because it is outdated and because we are EOLing RKE1 windows in 2.6.7.


Add commas to large numbers

If you have larger numbers  it would be easier to read with commas added (and this does then touch on localization..)

Minor 1.0.1 release adds commas to large numbers.


[Workshop creation] "Додати ще один розділ" button doesn't open new area #1368

Task https://github.com/ita-social-projects/OoS-Frontend/issues/1368

add the same functionality to create-provider. Push first form to the array on init

In the scope of this PR, please remove old description filed from the provider and workshop. According to the last updates from backend, this field were removed from the models


Fix empty string issue in ext/args

Now the js string "" can be converted to C array by jerryx_arg_string
JerryScript-DCO-1.0-Signed-off-by: Zidong Jiang<EMAIL_ADDRESS>

lgtm (informally)


Readme file shows PBVI() instead of PBVISolver()

Addressed in PR #11

Thanks for fixing, @dominikstrb !


Create GIS-basic-profile-v1.0

Profile for use with mdEditor to create FWS compliant metadata for GIS data.

will add this when it is closer to final


Lighten our use of metrics

Remove some tags that are unused and big. Remove unused ones.

Yeah want to keep some of these just in case

... in case it breaks some dashboard so that I can revert quickly


Gitlab collector : javax.net.ssl.SSLException: Unrecognized SSL message

when I am trying to run gitlab collector jar file then it is giving error:

2017-06-01 07:26:00,462 INFO  c.c.d.c.GitlabGitCollectorTask - Failed to retrieve data, the repo or collector is most likey misconfigured: https://xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.git, I/O error on GET request for "https://xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:80/api/v3/projects/Groupname%2FProjectname/repository/commits/?ref_name=develop&since=2017-05-18T07:26:00Z&per_page=100": Unrecognized SSL message, plaintext connection?; nested exception is javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?

Please help me on this

application.properties is given below:

dbname=dashboarddb
dbusername=dashboarduser
dbpassword=dbpassword
dbhost=<IP_ADDRESS>
dbport=27017
logging.file=./logs/gitlab.log
gitlab.cron=0 0/1 * * * *
gitlab.host=xyz.com
gitlab.protocol=https
gitlab.port=80
gitlab.selfSignedCertificate=false
gitlab.apiToken=xxxxxxxxxxxxxxxxxxxxxxx
gitlab.commitThresholdDays=15

any solution guys???

Try making that selfSignedCertificate=true.

@rob-miller-777 i tried that way again, but no luck
giving same set of errors.

GitlabGitCollectorTask - Failed to retrieve data, the repo or collector is most likey misconfigured: https://xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.git, I/O error on GET request for "https://xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:80/api/v3/projects/Groupname%2FProjectname/repository/commits/?ref_name=develop&since=2017-05-18T07:26:00Z&per_page=100": Unrecognized SSL message, plaintext connection?; nested exception is javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?

while I have imported all the certificates of Gitlab Server

@prvnsinghal , is it a private repo ? or an enterprise level private repo ?

@golokeshpatra45 yes, It is enterprise private repo.
why??

@prvnsinghal ,,
No worries ,
Go to Hygieia-Master -> UI and open README.md.
Scroll to the end and you will get,  Encryption for private repos
Now generate this key and add it to the properties file of both api and github i.e
Hygieia-master -> api -> target -> (properties file) -> key = (new generated private key )
Hygieia-master -> collectors ->scm -> github -> target -> open your properties file ->github.key = (new generated private key )
This key will help you encrypt your credentials .
Now run api then gulp serve then collectors.
**ask your IT to provide you with username and password to bypass the enterprise (GHE) login. GHE logins are different as compared to that of normal github logins as you enter your Windows login or LDAP or (many options). if you dont have such login then your collector should perform properly.
I had been unsuccessful in getting GHE populating my dashboard but now I have figured out. Hope you have got everything, any doubts do ask me .

@golokeshpatra45
I tried this encryption for private repo. but could not get the data.
It is giving the same set of problems. please help me on this.
and yes we have configure LDAP for our gitlab, does it make any effect for authentication.

@prvnsinghal , are you getting the same I/O get error ?

Think your issue comes from the protocol and port.  You currently have your protocol set to https, however you are using the standard http port of 80. Verify that both of those values are correct. I would guess that you can either remove the port altogether, or set it to 443, which is the standard https port.  Or if your server is on http, just change the protocol to http.

@prvnsinghal Please reopen if you have any more issues.


Durability bump issue  # ODHACK

What
The issue was related to the required durability when bumping/extending a contract. I removed the durability field from the argument struct in the "soroban-cli/command/key" file. As a result, the durability flag will no longer be required when running the command.
Why
This change was made to resolve the issue of requiring the durability flag during contract extension. Additionally, I implemented default persistent storage, so the durability flag is no longer necessary.
Known limitations
There are currently no known limitations.

Hi @janewang i saw you  reviewed my  pr. I also saw one check failed.
Am i missing an installation process?. Also, is there any issue with my pr?

@KoxyG I just kicked off the tests. Some integration tests are failing

I would change this from clap::ValueEnum to Default, with #[default] above Persistent. Then change the arg to be an option and not use the clap's default value. Then you can use .unwrap_or_default().  TL;DR don't rely on clap for the default value.
https://github.com/stellar/stellar-cli/blob/aad9be9708037e122e8e9ff09a67a09c26168513/cmd/soroban-cli/src/commands/contract/mod.rs#L162-L168

@willemneal If the enum is derive Default, then it won't be necessary to make the value an Option<>.

Hi @KoxyG, thanks for contributing.
The durability option needs to be retained. The issue is that it's default value is not functioning.

So, should i change it back to the initial state?. The  default value is persistent

The initial issue is that, when the command soroban contract bump --id C... --ledgers-to-expire 1000 is used. It doesn't work unless the --durability persistent is used along side with the command.

@leighmcculloch @KoxyG, can either of you reproduce the original issue? I updated the tests to rely on a default durability and it is passing: https://github.com/stellar/stellar-cli/pull/1644

@leighmcculloch @KoxyG, can either of you reproduce the original issue? I updated the tests to rely on a default durability and it is passing: #1644

You updated the default durability as  only "persistent"?

No just updated the tests to test if the default was working: https://github.com/stellar/stellar-cli/pull/1644/files
So I'm questioning if this PR is needed.  If you deploy a contract to testnet and then use extend are you required to use the --durability? When I try it locally and in the test linked above the default seems to be working so perhaps this issue was fixed a while ago. It is from last November so my guess is that the default didn't exist then and was added without closing that issue.

Hi @janewang I noticed you reviewed my pull request. Do i need to work on anything froom my end?


Please add support for interactive chat discordsrv

I tried asking them to support advanced vanish but they said for advanced vanish to support interactive chat discordsrv using meta (no idea what that means but heres the ss) - The interactive chat discordsrv addon adds the ability for players to do /playerlist in discord to shoow the list of players who are in-game. Due to this, it also shows vanished players, and would be amazing if vanish could be supported.
https://gyazo.com/7cd42c38edda21bf1bc458546662ab36
link to plugin:
https://www.spigotmc.org/resources/interactivechat-discordsrv-addon-show-items-and-invs-on-discord-preview-discord-images-in-game.83917/

This should be fixed in v1.2.5


Webpack 5 LoaderContext:  addContextDependency causes  loader to rerun once after any change in watch mode

Our project relies heavily on custom 'heavy' loaders, and fast compilation is crucial. In watch mode, every loader that utilizes addContextDependency reruns one more time after any project change, leading to longer build times. Trying to find a solution to minimize the re-running of these loaders and improve watch mode performance.
Bug report

After initial compilation in watch mode every loader that uses addContextDependency will rerun one more time after any change in the project.
What is the current behavior?
Custom loaders that use addContextDependency will rerun only if supplied context dependencies are changed.
If the current behavior is a bug, please provide the steps to reproduce.
Reproducible example here:
https://github.com/modjke/webpack-5-add-context-dependency-issue
txt-loader.js will run twice: at startup and for the first time index.js is changed

What is the expected behavior?
Loaders with addContextDependency should run only once on initial compilation in watch mode.
What have we tried?

debugging watchpack, as it turns out watchpack reports changes correctly
using async/sync loaders (same bug appears)
increasing aggregateTimeout
disabling hot module reload

Other relevant information:
webpack version:  5.76.3
Node.js version: 18.15.0
Operating System:  Mac OS (M1), Windows 11 H22, Windows 10
Additional tools: ~

Do you use WSL? Do you have something specific? I can't reproduce it on linux (Ubuntu), Windows 11

Webpack logs after step 4
><EMAIL_ADDRESS>start
> webpack watch

[!!!] Running txt-loader.js at ***\projects\webpack-watchbug\source\assets

asset main.js 4.25 KiB [compared for emit] (name: main)
runtime modules 670 bytes 3 modules
cacheable modules 77 bytes
  ./source/index.js 55 bytes [built] [code generated]
  ./source/assets/data.txt 22 bytes [built] [code generated]
webpack 5.76.3 compiled successfully in 129 ms

[!!!] Running txt-loader.js at ***\projects\webpack-watchbug\source\assets

assets by status 4.25 KiB [cached] 1 asset
cached modules 670 bytes [cached] 3 modules
cacheable modules 77 bytes
  ./source/index.js 55 bytes [built]
  ./source/assets/data.txt 22 bytes [built]
webpack 5.76.3 compiled successfully in 26 ms

Run webpack --watch
Observe [!!!] Running txt-loader.js message
Change index.js
Observe [!!!] Running txt-loader.js message once again even thou no dependencies was changed <- bug i'm trying to clear up
Change index.js again, and again, no message - that's correct

I see, the original report was misleading, invessitgate

Something wrong with module.needBuild:

First run we have true and true for index.js and data.txt
Second run the same
Third and etc only true for index.js

Threre is potential fix https://github.com/webpack/webpack/pull/16908, let's look at tests, because logic is really complex

Threre is potential fix #16908, let's look at tests, because logic is really complex

This fix is working fine on our end. Not sure about side effects though.

For future fixes - the problem here:
https://github.com/webpack/webpack/blob/main/lib/FileSystemInfo.js#L1201 for files
https://github.com/webpack/webpack/blob/main/lib/FileSystemInfo.js#L1212 for directories
Shortly - watchpack returns {} for some files and directories (https://github.com/webpack/watchpack/blob/main/lib/DirectoryWatcher.js#L721 ) and return only { safeTime:<PHONE_NUMBER>183 }, so we don't have the timestampHash properties for snapshots
So webpack think they are invalid and rebuild them on the second run and rewrite values on valid, and no problems on the third run.
But it is not for all cases

{} seem to be the "existance only" object. So watchpack doesn't known about anything but that this file/directory exists.
That doesn't seem to be enough for snapshoting, so webpack need to read more information about this file/directory when snapshoting. The snapshoting already have an implementation for that in the case of undefined, but that doesn't seem to be used when {} is found. This should be fixed.


Update Reason
Material content (inkl. recycled material) in the products.
MS1 Criteria

[ ] The model that should be updated exists
[ ] The referenced use case exists
[ ] The potential updates are discussed with all stakeholders
[ ] The potential update will be either

[ ] backward compatible or
[ ] a (chain of) migration strategy(-ies) from all non-deprecated previous versions to the new model will be developed

@bs-jokri redundant with #261 and the corresponding PR. Can be deleted


utcOffset - invalid parsing when no leading sign

The docs for utcOffset says:

Note that the string is required to start with the + or - character. Passing a string that does not start with + or - will be interpreted as if it were "+00:00".

However, I've come across a counterexample:

moment().utcOffset('0300').format()
"2017-02-27T09:53:40+01:00"
moment().utcOffset('+03:00').format()
"2017-02-27T11:53:46+03:00"

These:
console.log( (new Date()).toString())
console.log((new Date()).toLocaleString())
console.log( (new Date()).getTimezoneOffset())
console.log( navigator.userAgent)
console.log(moment.version)

Return:

Mon Feb 27 2017 09:50:21 GMT+0100 (Central European Standard Time)
2/27/2017, 9:50:21 AM
-60
Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
2.17.1

Weird.
I think the documentation is wrong here: any string that is passed that does not contain /[+-]00:?00/ will not set the offset. (If we accepted 0300 and the like, we might catch on years 😬  )

I agree we should change the docs. I think we can just remove the second sentence. Looking at the code, it seems pretty clear it's meant to ignore the "0300" case. Along the same lines, utcOffset also accepts 'Z' but that's not in the docs.

Closing in favor of https://github.com/moment/momentjs.com/pull/410


[Enhanced Monitoring] pglogical sender timeout - watch start replication XLOG ID

A user had a problem where their replication would go down after a couple of days. Checking the logs, they see a disconnect and replication slot repeat startup at the same XLOG ID.
We should be able to point this out in the sender and mark that as a flag for wal_sender_timeout and receiver timeout to be bumped up.

This was not the root cause for their issue, closing this out and will reopen when we get new insights.


Level and Room Traversal Mechanics

Determine when next level should be loaded, or reloaded. Set room size, view size, etc.

This should be done now for arcade mode at least.

Finished for arcade and vs mode.


Bash completion example: unexpected keyword "autocompletion"

The stock bash completion example here appears to be broken.
Here's my steps to reproduce in a virtualenv:
virtualenv vp
source vp/bin/activate
wget https://raw.githubusercontent.com/pallets/click/master/examples/bashcompletion/setup.py
wget https://raw.githubusercontent.com/pallets/click/master/examples/bashcompletion/bashcompletion.py

Now start following the instructions on the readme:
pip install -e .
eval "$(_BASHCOMPLETION_COMPLETE=source bashcompletion)"

Upon execution of the last statement, however, I see a problem:
$ eval "$(_BASHCOMPLETION_COMPLETE=source bashcompletion)"
Traceback (most recent call last):
  File "/temp/py/vp/bin/bashcompletion", line 11, in <module>
    load_entry_point('click-example-bashcompletion', 'console_scripts', 'bashcompletion')()
  File "/temp/py/vp/lib/python3.6/site-packages/pkg_resources/__init__.py", line 480, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/temp/py/vp/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2693, in load_entry_point
    return ep.load()
  File "/temp/py/vp/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2324, in load
    return self.resolve()
  File "/temp/py/vp/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2330, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/temp/py/bashcompletion.py", line 17, in <module>
    @click.argument("envvar", type=click.STRING, autocompletion=get_env_vars)
  File "/temp/py/vp/lib/python3.6/site-packages/click/decorators.py", line 151, in decorator
    _param_memo(f, ArgumentClass(param_decls, **attrs))
  File "/temp/py/vp/lib/python3.6/site-packages/click/core.py", line 1699, in __init__
    Parameter.__init__(self, param_decls, required=required, **attrs)
TypeError: __init__() got an unexpected keyword argument 'autocompletion'

This seems to be related to the autocompletion kwarg used to decorate the cmd1() and subcmd() methods:
@cli.command()
@click.argument("envvar", type=click.STRING, autocompletion=get_env_vars)
def cmd1(envvar):
    click.echo('Environment variable: %s' % envvar)
    click.echo('Value: %s' % os.environ[envvar])

@group.command()
@click.argument("user", type=click.STRING, autocompletion=list_users)
def subcmd(user):
    click.echo('Chosen user is %s' % user)

In fact, the problem is that the version of click I have does not include bash autocompletion!
$ grep "autocompletion" vp/lib/python3.6/site-packages/click/core.py
$

(compare to current source).
I have click version 6.7 installed,
$ python --version
Python 3.6.4

$ python -c 'import click; print(click.__version__)'
6.7

The example readme states

This example requires Click 2.0 or higher.

I'm a little confused about why bash completion is missing from Click 6.7 when it was added in 2.0!

It appears that the autocompletion feature was broken Click version 6.7. However, it's now fixed in the latest master branch since 8ac004f.

I checked 6.6 and 6.0 and there's no mention of autocomplete. I don't think it's ever been included in a release.

Oh right. Agree, it never appeared in the Change Log.


Upgrade Now always displayed - even when no upgrade exists

in 2.1.6+ the 'upgrade now' button shows up even when there is no upgrade

This was closed in the last release