treewide: Add passthru.updateScript to gnome pkgs

Motivation for this change
For packages that are hosted on the gnome mirror it's very easy.
Inspired by https://github.com/NixOS/nixpkgs/issues/36150
I changed some source URLs but they should be equivalent to the original.
Changed some derivations to use pname instead of name so that causes many package rebuilds :/

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Oh I should base this off of staging right?
Or staging-next? Which branch was it?

Thanks for taking care of this!

GNOME update script ignores the versions with odd minors by default because they are usually considered unstable. For projects where it is not the case, or we want the unstable version, we need to override the versionPolicy attribute.
Yes, staging is the correct branch.

How did you determine for which packages this is not the case?
Those that are in nixpkgs with an odd minor?

How did you determine for which packages this is not the case?
Those that are in nixpkgs with an odd minor?

Yup, just checked the minor part of version. Maybe some of those are unstable by accident, we should probably check the repos.

I looked at the repos and it doesn't seem that any of them use odd versions to indicate unstable. I'm not actually sure it's so common that it should be the default policy for us.
However I noticed that some of the packages have been abandoned for quite a while and aren't used anymore - I'll probably remove them in another PR or start a discussion in an issue.

I looked at the repos and it doesn't seem that any of them use odd versions to indicate unstable. I'm not actually sure it's so common that it should be the default policy for us.

I would say about 90% of packages hosted on GNOME servers, the packages with updateScript should have a correct version policy set so greping nixpkgs can give you pretty acurate image.

However I noticed that some of the packages have been abandoned for quite a while and aren't used anymore - I'll probably remove them in another PR or start a discussion in an issue.

At least glabels and ekiga have a new major release in the works. opal will probably be updated with ekiga.
Maybe we can get rid of pangox-compat.

I looked at the repos and it doesn't seem that any of them use odd versions to indicate unstable. I'm not actually sure it's so common that it should be the default policy for us.

I would say about 90% of packages hosted on GNOME servers, the packages with updateScript should have a correct version policy set so greping nixpkgs can give you pretty acurate image.

What do you mean?
Do we need to add the policy? Do they have that policy upstream?
Ohh okay, this odd policy is just the default for GNOME packages, alright.
I take my statement back, it's probably the right default.

However I noticed that some of the packages have been abandoned for quite a while and aren't used anymore - I'll probably remove them in another PR or start a discussion in an issue.

At least glabels and ekiga have a new major release in the works. opal will probably be updated with ekiga.
Maybe we can get rid of pangox-compat if nothing else depends on it.
I'm speaking about hyena (and the only program that uses it: pdf-mod) and polkit-gnome.

I'll add some more tonight.

Do we actually want to add update scripts to packages that will never receive an update? In particular those under Archive namespace like https://gitlab.gnome.org/Archive/pygtk

Not really no. I'd like to mark them as "non maintained" or "abandoned" somehow, so that it's obvious in nixpkgs.
I think this would be useful in general. Then other general update scripts could ignore those packages.
What would you think if I added a message to meta.knownVulnerabilities?

Not really, no. I'd like to mark them as "non maintained" or "abandoned" somehow, so that it's obvious in nixpkgs.
I think this would be useful in general. Then other general update scripts could ignore those packages.
What would you think if I added a message to meta.knownVulnerabilities?

Well meta.knownVulnerabilities is probably not a good idea since that makes the package opt-in - as ofborg shows.

@JohnAZoidberg I merged https://github.com/NixOS/nixpkgs/pull/60198/commits/393ca4cf70081b09168083cb7acc5b9548835582 in #60548 so you can drop it here.

Alright, I went through each of them and removed the updateScript for abandoned packages.
While I was at it I also corrected the URLs for their hompages and fixed some other meta attributes.

What's the status?

I think it should be fine, (haven't really looked at everything it's a lot) just need to resolve conflicts.

Alright, I rebased. Just needed to fix that one tiny conflict.
Didn't change anything else ;)

Removed the reference to repositories.git.

Thanks @JohnAZoidberg for the fixes :sparkles:


Manually free the computation graph when retains_graph=False

Currently, retains_graph is passed to each call to vmap. The meaning of this parameter should be to free the computation at the end of the computation, not in each individual call. This would require to manually free the computation graph in some cases. Some discussion about this issue is available at https://github.com/TorchJD/torchjd/pull/30/

For reference, I provide a draft implementation of functions to manually free the graph (these could be implemented better, but beware of recursion as it has a limit of 1000 in python).
def _free_computation_graphs(tensors: Sequence[Tensor]) -> None:
    for tensor in tensors:
        _free_computation_graph(root_grad_fn=tensor.grad_fn)

def _get_next_functions(grad_fn):
    return set([next_fn for next_fn, _ in grad_fn.next_functions if next_fn is not None])

def _free_saved_tensors(grad_fn) -> None:
    """
    Set to None all Tensor attributes whose name start by "_saved".

    Disclaimer: this is not future-proof, and we have no guarantee that it works for all Functions.
    """

    for attribute_name in grad_fn.__dir__():
        if attribute_name.startswith("_saved"):
            attribute = grad_fn.__getattribute__(attribute_name)
            if isinstance(attribute, Tensor):
                grad_fn.__setattr__(attribute_name, None)

def _free_computation_graph(root_grad_fn) -> None:
    to_visit = _get_next_functions(root_grad_fn)
    _free_saved_tensors(root_grad_fn)

    while len(to_visit) > 0:
        fn = to_visit.pop()
        _free_saved_tensors(fn)
        to_visit |= _get_next_functions(fn)

Tons of issues with this:

Have to parse the full computation graph of each output one more time.
Does not free tensors that are stored in an attribute that does not start with _saved.
Could potentially break an autograd function that uses a tensor in a _saved attribute that should not be freed by backward.
Not future-proof: we're touching at protected attributes of barely-documented torch objects.
Can't type hint: apparently, grad_fn classes do not inherit from anything else than object.


Fb phishing

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Friends I have been trying to understand th CD part can someone help

My project always stop with one error or the other can someone help


How to implement PushKit

how to implement PushKit with App? when my app is close pushKit will help to run background for incoming call

@saroar hi bro, im stucking like you with pushkit, can you provide something? Thanks so much

yes i have bro<EMAIL_ADDRESS>

i hate ios 14 when the incoming call screen is minimized, that bad and hard to control with multi incoming call TT^TT


feat(type): add support for metric asset

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

4 of 4 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.002%) to 85.14%

Totals

Change from base Build<PHONE_NUMBER>:
0.002%

Covered Lines:
6337

Relevant Lines:
7443

💛  - Coveralls


Ubiquiti: update toggle switch POE state

toggling a POE port off using standard Nodel "on/off" actions
POE management

Added a 'statDeviceBasic' & 'statDevice' to list all devices on site (including switches).
Maintain list of all _portOverrides (e.g. { '3e:2f:b5:28:27:c2': [{"port_idx":2,"poe_mode":"auto"},{"poe_mode":"off","port_idx":3}]}}) and merge with user requested state changes as part of PUT request requirements.
Regularly poll state of switches (every 5 minutes) to get the latest port details.
Provide actions to turn on/off ports.
Add CSRF token management.

Misc

Specify an alternative authenticated user in the parameters, previously only 'api' user.
Label switches with a 'label' field in the 'param_InterestingSwitches' parameter.

There's one issue that has been bothering me, for some reason, in this rev5, as opposed to rev4 where we are using several new API calls it appears that our auth token is expiring every hour.
01-30 03:04:09.14 got exception, will assume auth issue (rebooted recently?) and retry just once more
01-30 04:04:18.53 got exception, will assume auth issue (rebooted recently?) and retry just once more
01-30 05:04:28.33 got exception, will assume auth issue (rebooted recently?) and retry just once more
01-30 06:04:43.64 got exception, will assume auth issue (rebooted recently?) and retry just once more
01-30 07:04:55.38 got exception, will assume auth issue (rebooted recently?) and retry just once more
01-30 08:05:05.32 got exception, will assume auth issue (rebooted recently?) and retry just once more
01-30 09:05:14.61 got exception, will assume auth issue (rebooted recently?) and retry just once more

re-auth each hour, as evident by the console logs
This revision attempts to handle this by hitting /auth/login whenever we receive a 401 Unauthorized (each hour) usually against a simple request such as /stat/device-basic.
As, at this point, the node's http client has already logged in we have a csrf and auth-token available. If we provide the same csrf to the endpoint, we're given a new auth-token to use for the following hour.

This PR has been sitting open for a while now, and I reckon it's high time to land it.


Possible high-pri: wrong images and collisions since 2.2.8

Hey I'm not sure what's going on since 2.2.8 (and 2.2.9) but the wrong image is occasionally loaded from the cache (or stored in the cache). This didn't repro before that.
I traced it through my code:
ImageService.Instance.LoadUrl(ImageSourcePath).Into(ProfilePicture);

ImageSourcePath is correct. I opened the URL on a browser and it shows up correctly. However, ProfilePicture displays a different URL.
This happens when I refresh the app as well (i.e. when loading from memory). But if I kill the app and restart it, it loads the correct image and then occasionally introduces errors in other images.
I suspect it is something at the memory level cache of FFImageLoading.

#527

Let's continue in the other issue.


Improvements to README and Makefile

add required npm packages (at least some of them)
improve readability in steps section
add comments to Make commands (to show them when make runs)
fix trailing whitespaces

thanks for the improvements @wawrzek!


LOSS

Sorry to bother you, I read your comment in ultralytics / yolov3.  Did you changed his loss function to the original YOLOV3 paper version?

Yes, i change the loss,  because i think his loss function is different from original loss in the Darknet.

Yes, i change the loss, because i think his loss function is different from original loss in the Darknet.

OK , Thank you very much.

Yes, i change the loss, because i think his loss function is different from original loss in the Darknet.

OK , Thank you very much.


Update Move-ADObject.md

Added a statement about password when it moves within the object is moved across domains in the forest
Fixes https://github.com/MicrosoftDocs/windows-powershell-docs/issues/3514

@JohanFreelancer9 Please copy review

@tiburd
PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


Leaflet with touchscreen fired an event

[X] I'm sure this is a Leaflet code issue, not an issue with my own code nor with the framework I'm using (Plugin MapPaint)

How to reproduce

Leaflet version I'm using: 1.0.3
Browser (with version) I'm using: Chrome V.56
OS/Platform (with version) I'm using: Windows 10 and Android 6.0
step 1: Drawing to the map from desktop, it working fine.
step 2: Drawing to the map from touchscreen, they are an event from Leaflet that is fired and stop drawing.

What behaviour I'm expecting and which behaviour I'm seeing
When i'm drawing the map from a touchscreen, leaflet need let me drawing to the map like with desktop computer.
Minimal example reproducing the issue

[X] this example is as simple as possible

Using http://www.tekniservice.com/leaflet/leaflet-map.html
You can see a youtube video that explain the issue: https://youtu.be/BZPDzye_qfk

I think it's related with this issue: https://github.com/Leaflet/Leaflet/issues/5262

I've resolve it with this code:
.leaflet-container {   touch-action: none; }


Add definitions of macros to diffkemp-out.yaml

This PR contains the last but one part of #314 (remains enhancements of viewer for visualisation of code/diff for macro-function/function-macro  differences.
The PR adds extracted information about the location of macro definitions to the diffkemp-out.yaml file which is created when diffkemp compare is run. Thanks to the added macro definitions (and thanks to previously merged PRs) it will be now possible to see the code of the macros in the result viewer.

Yeah, it seems that there are many ways to do this. From the first glance, option 3 seems like the best but I think that we should have an in-person discussion on this to better understand what the problem is and what the best solution would be.


Support payloads in text markings

Text marking objects are persistent between edits and we can store our own payloads in those objects, but the feature is not documented or standardized, and we could always break CodeMirror by accidentally putting our payloads in an internal property on the TextMarking object.
Can we support (and document) a "payload" property on TextMarking, or corresponding accessors?
See also: https://discuss.codemirror.net/t/payloads-in-text-markings/1270.

Please don't ask the same question here and on the forum, that just fills my mailbox and this bug tracker with duplicate junk.
Ref: https://discuss.codemirror.net/t/payloads-in-text-markings/1270

I'm starting to see a pattern of quick rejection of my tickets. That is not constructive. If you don't like my suggestions, I'm going to stop making them.
The question was the wrong way to go. A bug is the better way, because this is a feature request. I realized this after writing the suggestions; I'm sorry the world isn't perfect…


Could not find method pluginBundle()

With https://github.com/kazurayam/inspectus4katalon-gradle-plugin/blob/0.4.0/build.gradle, when I executed
$ gradel test

I got an error
$ gradle test

FAILURE: Build failed with an exception.

* Where:
Build file '/Users/kazuakiurayama/github/inspectus4katalon-gradle-plugin/build.gradle' line: 67

* What went wrong:
A problem occurred evaluating root project 'inspectus4katalon'.
> Could not find method pluginBundle() for arguments [build_c9thwwhm8y4mynwaeuz0tfq4m$_run_closure9@987d6d9] on root project 'inspectus4katalon' of type org.gradle.api.Project.

https://plugins.gradle.org/docs/publish-plugin

Plugin Publish plugin v1.0.0 simplifies the configuration of plugin publishing by merging the pluginBundle block into the gradlePlugin one.

Possibly the version of Plugin Publish plugin matters.
Possibly pluginBundle was used prior to the v1.0.0, but since v1.0.0 gradlePlugin block should cover the informatio which was carried in the publicBundle.
So I should rewrite the build.gradle.

I should study

カスタムGradleプラグインをGradle Plugin Portalに公開する手順を詳しく説明します

and revise the build.gradle of the inspectus4katalon-gradle-plugin project


new object - literal vs. constructor notation

Hi,
I just attempted to migrate to MF v2 and came across issue I can't explain. The following code gives different results in v1 and v2:
  var myObject1 = new Object({
    path: "",
    query: "",
    reqType: {
      attr1: "",
      attr2: "",
      attr3: ""
    }
  });
  var myObject2 = {
    path: "",
    query: "",
    reqType: {
      attr1: "",
      attr2: "",
      attr3: ""
    }
  };

  console.log(myObject1);
  console.log(myObject2);

v1:
{ path: '', query: '', reqType: { attr1: '', attr2: '', attr3: '' } }
{ path: '', query: '', reqType: { attr1: '', attr2: '', attr3: '' } }

v2:
{}
{ path: '', query: '', reqType: { attr1: '', attr2: '', attr3: '' } }

When running the same code on Cloudflare it behaves like v1. Is it expected?
Thanks!

Thanks for looking into this!
Actually there is no reason of using the constructor method, was just preference of the person who wrote this code. I replaced all obvious initializations with the literal approach and the situation improved but not everything was working like on v1 and CF. Some logic was still broken and I didn't have time to investigate further - will check next week to see if I missed maybe something or there is another problem.
BTW Happy New Year! And many thanks for the great project :)


azure_stateful_node: Import of existing VMs?

Is it possible to import a existing VM as a stateful node into spot.io via the Ansible module azure_stateful_node?
Or can you use this module just to create a new stateful node?

@jfunke4 - Currently only new stateful node creation is supported. Sharing your request with PMs for their evaluation.

@anuragsharma-123 - Thank you for the clarification.

@jfunke4 - We are adding support for VM Import. Will post here when it is available.


chore(deps): upgrade configuration

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-configuration-k8s-26-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 3361

Questions ?
Please refer to the Backport tool documentation


Results pane shows untruncated HTML values

SQL Operations Studio Version

MacOS
SQL Ops Version 0.31.4 (0.31.4)

Steps to Reproduce:

Have a table with a varchar column containing HTML values.

Query the table within SQL Ops Studio.

Expected:
The columns show in the results pane with the column containing HTML showing only a truncated portion of the HTML string value.
Actual:
The entire HTML value is shown in the results pane, and it makes a mess.

I have the same issue
System

Windows 10
SQL Ops Version 0.31.4 (0.31.4)

@anthonydresser Was this fixed?

Should be fixed as of 0.32.1

@philoushka @zhuochen83 You can try out the latest insider release in the Releases section. This issue should be fixed. Please feel free to reopen the issue if you still find it in the latest release.

This should be fixed in the latest insiders build at https://github.com/Microsoft/sqlopsstudio/releases/tag/<IP_ADDRESS>.  We'll include this fix in the next stable build later in August.  Please reactive if you still hit the issue with these builds.


Functions deployed to nuclio not available in cvat

My actions before raising this issue

[x] Read/searched the docs
[x] Searched past issues

models deployed in nuclio are not available in cvat.
Message "Could not get models from the server Error: Request failed with status code 500. "Server Error (500)." pops up in Chrome. As long as no function is deployed in nuclio project, the error does not occur.
Context
want to auto annotate images using nuclio serverless functions.
Your Environment

Release 1.1.0  commit 8eb7c13619e39d9546ba3807027d30eab9c5ce2b
Docker version 19.03.13
Windows 10
Logs:
chrome console: http://localhost:8080/api/v1/lambda/functions 500 (Internal Server Error)
docker logs cvat:

[Wed Oct 14 17:56:23.169731 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624] ERROR:django.request:Internal Server Error: /api/v1/lambda/functions
[Wed Oct 14 17:56:23.169739 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624] Traceback (most recent call last):
[Wed Oct 14 17:56:23.169742 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624]   File "/usr/local/lib/python3.5/dist-packages/django/core/handlers/exception.py", line 34, in inner
[Wed Oct 14 17:56:23.169744 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624]     response = get_response(request)
[Wed Oct 14 17:56:23.169747 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624]   File "/usr/local/lib/python3.5/dist-packages/django/core/handlers/base.py", line 115, in _get_response
[Wed Oct 14 17:56:23.169749 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624]     response = self.process_exception_by_middleware(e, request)
[Wed Oct 14 17:56:23.169752 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624]   File "/usr/local/lib/python3.5/dist-packages/django/core/handlers/base.py", line 113, in _get_response
[Wed Oct 14 17:56:23.169755 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624]     response = wrapped_callback(request, *callback_args, **callback_kwargs)
[Wed Oct 14 17:56:23.169757 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624]   File "/usr/local/lib/python3.5/dist-packages/django/views/decorators/csrf.py", line 54, in wrapped_view
[Wed Oct 14 17:56:23.169760 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624]     return view_func(*args, **kwargs)
[Wed Oct 14 17:56:23.169763 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624]   File "/usr/local/lib/python3.5/dist-packages/rest_framework/viewsets.py", line 114, in view
[Wed Oct 14 17:56:23.169765 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624]     return self.dispatch(request, *args, **kwargs)
[Wed Oct 14 17:56:23.169768 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624]   File "/usr/local/lib/python3.5/dist-packages/rest_framework/views.py", line 505, in dispatch
[Wed Oct 14 17:56:23.169770 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624]     response = self.handle_exception(exc)
[Wed Oct 14 17:56:23.169773 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624]   File "/usr/local/lib/python3.5/dist-packages/rest_framework/views.py", line 465, in handle_exception
[Wed Oct 14 17:56:23.169776 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624]     self.raise_uncaught_exception(exc)
[Wed Oct 14 17:56:23.169778 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624]   File "/usr/local/lib/python3.5/dist-packages/rest_framework/views.py", line 476, in raise_uncaught_exception
[Wed Oct 14 17:56:23.169781 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624]     raise exc
[Wed Oct 14 17:56:23.169783 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624]   File "/usr/local/lib/python3.5/dist-packages/rest_framework/views.py", line 502, in dispatch
[Wed Oct 14 17:56:23.169786 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624]     response = handler(request, *args, **kwargs)
[Wed Oct 14 17:56:23.169788 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624]   File "/home/django/cvat/apps/lambda_manager/views.py", line 485, in func_wrapper
[Wed Oct 14 17:56:23.169791 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624]     data = func(*args, **kwargs)
[Wed Oct 14 17:56:23.169796 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624]   File "/home/django/cvat/apps/lambda_manager/views.py", line 523, in list
[Wed Oct 14 17:56:23.169799 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624]     return [f.to_dict() for f in gateway.list()]
[Wed Oct 14 17:56:23.169801 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624]   File "/home/django/cvat/apps/lambda_manager/views.py", line 63, in list
[Wed Oct 14 17:56:23.169804 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624]     response = [LambdaFunction(self, item) for item in data.values()]
[Wed Oct 14 17:56:23.169806 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624]   File "/home/django/cvat/apps/lambda_manager/views.py", line 63, in <listcomp>
[Wed Oct 14 17:56:23.169809 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624]     response = [LambdaFunction(self, item) for item in data.values()]
[Wed Oct 14 17:56:23.169812 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624]   File "/home/django/cvat/apps/lambda_manager/views.py", line 89, in __init__
[Wed Oct 14 17:56:23.169814 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624]     kind = data['metadata']['annotations'].get('type')
[Wed Oct 14 17:56:23.169819 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624] KeyError: 'annotations'
[Wed Oct 14 17:56:23.169826 2020] [wsgi:error] [pid 278:tid<PHONE_NUMBER>69824] [remote <IP_ADDRESS>:54624]

I seem to be have the same problem.
Is there any update on this or is there a workaround?

I wasn't able to reproduce the issue.


[Bug]: bal test with data providers fails on Windows environment when code coverage is not enabled

Description
We noticed that the test cases, which include data providers abruptly fail with the following error on Windows environment.
Steps to Reproduce
Add the following code to a Ballerina project and execute tests using bal test. It abruptly stops test execution throwing there are test failures.
If we use bal test --code-coverage the tests get executed and pass without an issue.
source
function foo(int[] requests) returns int[] {
    return [];
}

test
import ballerina/test;
@test:Config {
    dataProvider: data,
    groups: ["sample"]
}
function fooTest(int[] input, int[] expected) returns error? {
    test:assertTrue(foo(input) == expected);
}

Affected Version(s)
Ballerina 2201.2.0
OS, DB, other environment details and versions
Windows OS
Related area
-> Test Framework
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

The error is thrown from https://github.com/ballerina-platform/ballerina-lang/blob/master/cli/ballerina-cli/src/main/java/io/ballerina/cli/task/RunTestsTask.java#L289


Occupancy Binary Sensor vs. Frigate Notification Blueprint behavior

Version of the custom_component

Frigate Lovelace Card v5.2.0
Frigate v0.12.1
Configuration
Describe the bug
I am using the Frigate Notification blueprint to send notifications to my phone.  This works great.  For example, every time a new car shows up in the camera field of view I get a notification.  My experience with the binary_sensor is different however.  The occupancy sensor stays on as long as at least one car is in the field of view.  Is there a binary_sensor that I can use in home assistant that will reproduce the behavior I am getting from the Frigate Notification blueprint?
I want to trigger rules as new cars come into a parking lot.
Debug log

Nothing in the logs relates to this issue.  Not even sure it is a bug.

this is the expected behavior of the binary sensors, sounds like you want to use the /events mqtt topic https://docs.frigate.video/integrations/mqtt#frigateevents

Thanks for the tip on this.  Does the frigate notification blueprint also use this event topic?
Looking at the doc you referenced it not clear to me how I tell when multiple of the same object types are in the frame.  Or when a new object enters or leaves the frame.  Is this even possible?

Yes this is what the blueprint uses.
You can tell when a tracked object is "new" or has left by the type. The type will be new, update, or end


provider seems to fall back to, rather than ignore, kubeconfig_path when kubeconfig_raw is set

I'm using version 0.3.1.
I haven't investigated this completely, but I was setting kubeconfig_raw in the provider, which was invalid in some way (I believe), and it seemed like the plugin fell back to the default context in my local ~/.kube/config.
This seems contrary to the docs, which state

If kubeconfig_raw is set, kubeconfig_path is ignored.

And it's also potentially highly dangerous to use an unexpected kubeconfig.
https://github.com/kbst/terraform-provider-kustomization/blob/2341cf80e4927378c86d9a7822b340ec8a952697/kustomize/provider.go#L83-L95
I fixed my config, but would like:

any error using kubeconfig_raw should be logged
if kubeconfig_raw was set but failed, it should not fallback to kubeconfig_path
any error using kubeconfig_path should be logged
perhaps the docs should suggest specifying a non-default context to prevent accidentally using the wrong kubeconfig

The current implementation is, if kubeconfig_raw and kubeconfig_path are set, kubeconfig_path is ignored. In any case the provider falls back to the default config file on disk like kubectl does and supports the same environment variables. Behaving like kubectl was the original intention of the implementation. Most recently the Kubernetes provider dropped support for a fallback and made it mandatory to specify a config. That's an option too. I'm open to feedback and pull requests to change that.

Here's a few more details on my use case: I'm using terraform-aws-eks to create an EKS cluster. I then configure the kustomization provider like this:
data "aws_eks_cluster" "cluster" {
  name = module.eks.cluster_id
}

data "aws_eks_cluster_auth" "cluster" {
  name = module.eks.cluster_id
}

locals {
  # non-default context name to protect from using wrong kubeconfig
  kubeconfig_context = "_terraform-kustomization-${var.cluster_name}_"

  kubeconfig = {
    apiVersion = "v1"
    clusters = [
      {
        name = local.kubeconfig_context
        cluster = {
          certificate-authority-data = data.aws_eks_cluster.cluster.certificate_authority.0.data
          server                     = data.aws_eks_cluster.cluster.endpoint
        }
      }
    ]
    users = [
      {
        name = local.kubeconfig_context
        user = {
          token = data.aws_eks_cluster_auth.cluster.token
        }
      }
    ]
    contexts = [
      {
        name = local.kubeconfig_context
        context = {
          cluster = local.kubeconfig_context
          user    = local.kubeconfig_context
        }
      }
    ]
  }
}

provider "kustomization" {
  kubeconfig_raw = yamlencode(local.kubeconfig)
  context        = local.kubeconfig_context
}

And I never want to use credentials from my local ~/.kube/config or anywhere other than the given config.

I had the same problem on GCP. Explicitly specifying the context in the provider did the trick.

I would actually favor something like the helm provider does:
provider "helm" {
  kubernetes {
    host                   = "https://${module.testing_gke_core.endpoint}"
    token                  = data.google_client_config.default.access_token
    cluster_ca_certificate = base64decode(module.testing_gke_core.ca_certificate)
  }
}


Better multi-lang class tpool handling

Problem: in the original system there were class texts with translations. Later the texts were deleted. But the translations remained ! Somehow. Maybe because of the fact that this is a standalone system without further transports but not sure. And now the serialized XML contains translation but no texts in the master lang which is a bug.

This PR fixes that.
P.S. Sorry for ZCX_ABAPGIT_EXCEPTION - auto capitalization in 731 ...

👍
just edit ZCX_ABAPGIT_EXCEPTION in github ;-)

just edit ZCX_ABAPGIT_EXCEPTION in github ;-)

Mmm, should I do it for every PR ? :)

isn't it lower case after a pull? anyway, it's on the agenda to automate this annoyance away https://github.com/abapGit/abapGit/issues/5018#issuecomment-951038221


rubygems with native extensions fails to build under darwin sandbox, tries to access /bin/sh

Describe the bug
When building a rubygem that has a native extension with the darwin sandbox on, it fails to build because the synthesized Makefile starts with SHELL = /bin/sh.
It looks like the Makefile is generated by extconf.rb, and I'm pretty sure this is all just done as part of a gem build command, so I don't know how we can go in and patch it. Is there any way to cause gem build to pass additional make flags, or to synthesize a Makefile with a better SHELL to begin with?
I suspect this affects any gem with native extensions, but I've only tested ffi and sassc so far.
I've reproduced this across multiple versions of the ffi gem, and I don't see anything specific to this gem to produce that SHELL line.
FWIW grepping through the ffi source finds a few other hard-coded references to /bin/sh in various .mk files, so those may need to be fixed as well in the case of this gem, but the SHELL issue is the first step.
I'm also not clear if this is a darwin-specific problem, since surely SHELL = /bin/sh is problematic for Linux too, but I'd have expected Linux sandbox issues with rubygems to have been caught before now.
To Reproduce
Steps to reproduce the behavior:

nix-build --no-out-link --option sandbox true -A ruby.gems.ffi on darwin (optionally with --check if you already have the gem built)

Expected behavior
It should build the gem.
Output
Building native extensions. This could take a while...
ERROR:  Error installing /nix/store/zq4aif72vx4y6sx56spyrjs0c538a608-ffi-1.10.0.gem:
        ERROR: Failed to build gem native extension.

    current directory: /nix/store/0gmx45yqhaj9bwpps3dxizblsxc4cq8x-ruby2.6.5-ffi-1.10.0/lib/ruby/gems/2.6.0/gems/ffi-1.10.0/ext/ffi_c
/nix/store/h1jmi5pnsjj8vlnmbzks547a3q83hdwb-ruby-2.6.5/bin/ruby -I /nix/store/h1jmi5pnsjj8vlnmbzks547a3q83hdwb-ruby-2.6.5/lib/ruby/2.6.0 -r ./siteconf20191112-74371-u5y091.rb extconf.rb
checking for ffi_call() in -lffi... yes
checking for ffi_closure_alloc()... yes
checking for ffi_raw_call()... yes
checking for ffi_prep_raw_closure()... yes
checking for shlwapi.h... no
checking for ruby/thread.h... yes
checking for rb_thread_blocking_region()... no
checking for rb_thread_call_with_gvl()... yes
checking for rb_thread_call_without_gvl()... yes
checking for ffi_prep_cif_var()... yes
creating extconf.h
creating Makefile

current directory: /nix/store/0gmx45yqhaj9bwpps3dxizblsxc4cq8x-ruby2.6.5-ffi-1.10.0/lib/ruby/gems/2.6.0/gems/ffi-1.10.0/ext/ffi_c
make "DESTDIR=" clean
Error opening /private/var/select/sh: Operation not permitted
Failed to exec /bin/bash as variant for /bin/sh (1: Operation not permitted).

current directory: /nix/store/0gmx45yqhaj9bwpps3dxizblsxc4cq8x-ruby2.6.5-ffi-1.10.0/lib/ruby/gems/2.6.0/gems/ffi-1.10.0/ext/ffi_c
make "DESTDIR="
Error opening /private/var/select/sh: Operation not permitted
Failed to exec /bin/bash as variant for /bin/sh (1: Operation not permitted).

make failed, exit code 1

Metadata

system: "x86_64-darwin"
host os: Darwin 19.0.0, macOS 10.15.1
multi-user?: no
sandbox: no
version: nix-env (Nix) 2.3.1
channels(lilyball): "nixpkgs-20.03pre199995.895874d2145"
nixpkgs: /Users/lilyball/.nix-defexpr/channels/nixpkgs

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute: ruby
# a list of nixos modules affected by the problem
module:

The other possibility is that we're allowing access to /bin/sh for some reason, though I don't see any references to that in the sandbox. On macOS 10.15 /bin/sh actually access /private/var/select/sh which then causes it to execute /bin/bash.

Come to think of it, this seems very plausible based on the error message above, as it's barfing on /private/var/select/sh rather than /bin/sh directly.
I still think it's a rubygems problem that it's running /bin/sh at all, but I'd love some pointers as to whether /bin/sh is supposed to be accessible to derivations.

We do in fact allow /bin/sh in the profile, interesting. So this is specifically a macOS 10.15 issue.

I still think this is problematic, but access to /bin/sh has been fixed for macOS 10.15 in general so it's no longer pressing. I'll close this out now and someone can reopen it if there's still a practical issue.


Click Events passing through Buttons if there is a Viewport underneath

Godot version:
<IP_ADDRESS>
Issue description:
Clicks seem to pass right through a Button without triggering it if there is a sub Viewport underneath the area of the button that's clicked. It happens even if the Button has a Mouse Filter set to 'Stop'. If there's a Button within the Viewport, directly below, it receives the Event without a problem.
Steps to reproduce:
Place a button partially over a sub viewport and click area where they both overlap.

Viewport_Issue.zip

This has become a big issue for me too. What makes it especially tricky is that it seems like any node inside the viewport can block input as well, even if the viewport itself doesn't cross boundaries with that node.
For example, If button 2 is inside a viewport, with button 1 and 3 adjacent, everything works as expected.

But if I then drag button 2 e.g. upward inside the viewport, then button 2 blocks input to button 1, EVEN THOUGH it's not even onscreen and should be contained by the bounds of its viewport.

This also occurs if you drag button 2 down toward button 3.
Here's a sample project in C#/Mono
ViewportBug.zip

This bug report has two duplicates: #45400 and #48401

Still happening in v3.5.stable.official [991bb6ac7]


Wildcards in subdomains for redirect urls without development mode

Preflight Checklist

[X] I could not find a solution in the existing issues, docs, nor discussions
[X] I have joined the ZITADEL chat

Describe your problem
We are building SaaS application which uses "subdomain-per-account": we have a separate domain (for example, our.app), all of which subdomains (some-client.our.app, another-client.our.app) are pointing to the same application.
Currently if we want to have wildcards in subdomains for redirect-urls we have two options:

Manually or programmatically add all of the possible subdomains as a separate redirect urls

A huge burden to properly maintain
There is no way to "add one url" in API, only to replace whole list

Running in production with development mode enabled for redirect urls

Describe your ideal solution
I propose to allow wildcards in redirect urls without enabling development mode when some conditions are met:

Protocol is https
Wildcard is a part of subdomain (for example, *.our.app, some-*-thing.our.app, but not our.app/*)
Wildcard must be in the left-most part of the subdomain: some.*.our.app is not allowed
Wildcard should only match one subdomain level: a.b.our.app is not covered under *.our.app

Maybe it can be feature-flagged and not enabled by default, with proper notice about possibility of subdomain hijacking
Version
No response
Environment
Self-hosted
Additional Context
No response

A little bit more of a context:
I've considered just enabling development mode in production deployment and configuring redirect url exactly as I wanted, but I'm unsure of other implications of enabling it. Especially "in the future", when something else can possibly be tied to that setting.

Previously we have denied this, as the OpenID connect standard specifies direct string comparison:

... with the matching performed as described in Section 6.2.1 of [RFC3986] (Simple String Comparison).

However, as this is a recurring request we can consider allowing it. Anyway it is the admin's responsibility to allow only redirects to domains they control. If they are in full contoll of the top-level domain and all it's subdomain (admin knows best) there shouldn't be a security issue.
We / they just need to take care not to set https://example.com* , such a URL might be hijacked by https://example.com.bad.com

A front-end message about caveats and lots of warnings in docs can be useful, just like now there is a message when using http url without development mode enabled

This is pretty ideal, we also have the same model with subdomains representing premium tier b2b clients. It's been a pain so far to maintain this url list, both redirect and logout.
I appreciate it's not in the spirit of the RFCs, but implementing a superset rather than a subset of the functionality is as everyone has pointed out - up to the admin using the system to utilise.
As long as a feature design doesn't fall short of the RFC everything else is a nice bonus.


Respect KUBECONFIG env for get-credentials

Describe the solution you'd like
Currently, to override the system default ~/.kube/config path there is an optional parameter --file for the az aks get-credentials command. When the parameter is not provided, the CLI should respect the value of KUBECONFIG environment variable in the current shell context.
Additional context
This is useful for workflows with direnv, etc. and providing isolated kubectl contexts with az.

aks

@garthkerr Apologies for the late reply. Use one of the following options to change where kubectl looks for configuration parameters:
Modify the KUBECONFIG environment variable to point to the config file's current location. For more information, see Set the KUBECONFIG environment variable.
Run the kubectl config command with the --kubeconfig= parameter.
Could you please use the most recent version of the Azure CLI and check if the KUBECONFIG is still getting ignored ? Awaiting your reply.


Fix extensions runner when using async resolvers

Had to duplicate the code because I needed to run the await inside runner.request. Also simplified the runner and removed the broken run_on_all_extension decorator

Thanks for adding the RELEASE.md file!

Here's a preview of the changelog:

This release fixes an issue with the extension runner and async resolvers


Title mismatch on content pages and main page

Existing documentation URL(s)
Main Page:

https://developers.cloudflare.com/api-shield/

Content Pages:

Basically every content page, for example https://developers.cloudflare.com/api-shield/

Section that requires update

On the main docs page (https://developers.cloudflare.com/) the title in the top right is Cloudflare Developers.
However, on any subpages (for example, https://developers.cloudflare.com/api-shield/) the title in the top right is Cloudflare Docs.

What needs to change?

This is a small issue, but one or the other should likely be changed so they match.

How should it change?

Either Cloudflare Developers should change to Cloudflare Docs on the main page, or...
Cloudflare Docs should change to Cloudflare Developers on the subpages.

Thanks for providing this feedback! This is a known issue and will be addressed through an update later this year. Thanks!


Added Suppress rule for this line / Suppress rule for file quick actions / Show documentation

Added Suppress rule for this line / Suppress rule for file quick actions (#245)

Added show documentation quick action

Fix possible issue with incorrect command run when 2 rule single fixes are available. This is due to CommandIds.applySingleFix getting overriden inside commands by the last added single fix quick action. The fix is to include the ruleId in the key when adding to commands.

@dbaeumer any chance this could be merged? Thanks

Very nice work.

Thanks @dbaeumer !

I did some minor tweaks. One thing I forgot about is that different files can have different .eslintrc files (in different workspace folders) so we need to remember the rules per file. Changed this and pushed.
Will publish a new version of ESLint beginning of next week.

Great improvement! Thanks a lot for this!

Is there an option to hide those additional menu items?
I usually don't suppress rules at all and I don't need the Documentation link. When I open Light Bulb menu I want to only see recommendations and for me those new menu items are just noise.

Actually that is a fair request. @loune would you be willing to add such a setting ?

@dbaeumer hereby: https://github.com/Microsoft/vscode-eslint/issues/573

Sure, I can have a look at adding a setting.

Hello, great addition, but what happened to Fix All of a specific problem?
The Fix all auto-fixable problems could be problematic if you don't know what it will fix.
thank you.

@alexiosd this patch shouldn't change how Fix All of a specific problem works. I'll see what's wrong with that as well.


build from FROM buildpack-deps:jessie-scm instead?

I figured out that java is not based on jessie-scm but on jessie-curl (directly) (which doesn't include git).
I ran into this when using drone for building, as it assumes git in the container. Is there a reason why node and others include scm but java doesn't?

@bradrydzewski, this is probably also interesting for you to know/understand.

This is actually JRE vs JDK: https://github.com/docker-library/java/blob/d7d3337acfb3918ef23b3364b2dbf425d5b068cd/openjdk-8-jre/Dockerfile#L1 and https://github.com/docker-library/java/blob/d7d3337acfb3918ef23b3364b2dbf425d5b068cd/openjdk-8-jdk/Dockerfile#L1
If you use the JRE, it's based on -curl, but the JDK is based on -scm.

(which are actually two of the examples in the description itself: https://github.com/docker-library/docs/blob/9a3c64afc13ef2949b626dc7750b98158b14eef0/buildpack-deps/content.md#whats-included)

Thanks @tianon!


Negation of Mana Function in Query Shows Invalid

The template function does not allow for negation with the keyword "mana".
See the photo below.

Note the function only contains negation mana functions.

The issue is with non caps lock mana symbols. It will be fixed in the next release


Language detection still operating on paste despite "workbench.editor.languageDetection": false

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.66.0
OS Version: macOS 12.3.1

Steps to Reproduce:

"workbench.editor.languageDetection": false
Open a JSON file
Copy part of the file
Open a new untitled file
Paste

Expected: language is not detected as per setting
Actual: language is not detected as per setting
https://user-images.githubusercontent.com/921609/162072531-a5cadb3b-12ab-4337-b5c2-f6600c30bc2c.mov

Yes as designed, copy from our editor preserves the source language mode.


add image chache

sbit cache is much more memory efficient for small bitmaps(font size < 256) ，but  if font size >= 256, must be configured as image cache.
reference link

Thank you!


feat: wire up exchange UI

Description
Wire up some of the missing/hardcoded fields in the exchange API.
Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[x] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)
N/A
Risk
Very small - all changes are behind the "multi-hop" feature flag.
Testing
None needed by ops.
Engineering
With the multi-hop flag enabled, we should now show:

Gas for the selected swapper in the unexpanded view
Fiat amount for the "You get" section
Rate for the selected swapper in the unexpanded view

Operations
N/A
Screenshots (if applicable)

Current dependencies on/for this PR:

develop

PR #4890   👈

This comment was auto-generated by Graphite.

Noticed a bit of a weird one here, while changing buy/sell assets, the previously input amount stays selected, and the fiat amount is actually the one of the initially selected sell asset. This stays dangling like so until the sell amount is eventually changed.

Fixed in 11f9ca7ac4c9f19edeb0092fbe658340925fdbb0


fix(deps): :arrow_up: update angular monorepo to v17.0.2

This PR contains the following updates:

Package
Change
Age
Adoption
Passing
Confidence

@angular/animations
17.0.1 -> 17.0.2

@angular/common
^17.0.1 -> ^17.0.2

@angular/common
17.0.1 -> 17.0.2

@angular/compiler
17.0.1 -> 17.0.2

@angular/compiler-cli (source)
17.0.1 -> 17.0.2

@angular/elements
17.0.1 -> 17.0.2

@angular/forms
17.0.1 -> 17.0.2

@angular/language-service
17.0.1 -> 17.0.2

@angular/platform-browser
^17.0.1 -> ^17.0.2

@angular/platform-browser
17.0.1 -> 17.0.2

@angular/platform-browser-dynamic
^17.0.1 -> ^17.0.2

@angular/platform-browser-dynamic
17.0.1 -> 17.0.2

@angular/router (source)
^17.0.1 -> ^17.0.2

@angular/router (source)
17.0.1 -> 17.0.2

@angular/service-worker
17.0.1 -> 17.0.2

Release Notes

angular/angular (@angular/animations)
v17.0.2
Compare Source
compiler-cli

Commit
Type
Description

7a95cccf50
fix
add interpolatedSignalNotInvoked to diagnostics (#52687)

a548c0333e
fix
incorrect inferred type of for loop implicit variables (#52732)

core

Commit
Type
Description

2cea80c6e2
fix
error code in image performance warning (#52727)

b16fc2610a
fix
limit rate of markers invocations (#52742)

44c48a4835
fix
properly update collection with repeated keys in @for (#52697)

v17.0.1
Compare Source
http

Commit
Type
Description

5c6f3f8ec0
fix
Don't override the backend when using the InMemoryWebAPI (#52425)

migrations

Commit
Type
Description

70d30c28e0
fix
Add support for ng-templates with i18n attributes (#52597)

4f125c5f9a
fix
Switches to multiple passes to fix several reported bugs (#52592)

Web Frameworks: the internet frontier.
These are the voyages of the framework Angular.
Its continuing mission:
To explore strange, new technologies.
To seek out new users and new applications.
To boldly go where no web framework has gone before.
In honor of v17.0.1
                                                  ______
                                     ___.--------'------`---------.____
                               _.---'----------------------------------`---.__
                             .'___=]===========================================
,-----------------------..__/.'         >--.______        _______.---'
]====================<==||(__)        .'          `------'
`-----------------------`' ----.___--/
     /       /---'                 `/
    /_______(______________________/
    `-------------.--------------.'
                   \________|_.-'

Live long and prosper 🖖🏻

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package-lock.json
npm WARN cli npm v10.2.3 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2023-11-12T20_13_14_742Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2023-11-12T20_13_14_742Z-debug-0.log


test: Package Manager Support for deploy

Problem

Setup e2e test with supported Package Managers (npm, yarn-classic, yarn-modern, pnpm) for amplify deploy.
Issue number, if available:
Changes

Major change

run deployment.test.ts with PACKAGE_MANAGER_EXECUTABLE

Other changes

move test folder from the package folder ./ to a temporary folder tmp to create a fresh project
remove stop:npm-proxy
install packages for test projects

Corresponding docs PR, if applicable:
Validation

Validating in the PR check
Checklist

[ ] If this PR includes a functional change to the runtime behavior of the code, I have added or updated automated test coverage for this change.
[ ] If this PR requires a change to the Project Architecture README, I have included that update in this PR.
[ ] If this PR requires a docs update, I have linked to that docs PR above.
[ ] If this PR modifies E2E tests, makes changes to resource provisioning, or makes SDK calls, I have run the PR checks with the run-e2e label set.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

As discussed, I'm closing the PR and create a new PR to add deployment step for in the create amplify test


Add support for local Helm Charts, copy charts from control to remote host

@mbilal92 please rebase your PR because there are a couple of changes that are not needed anymore.

Overall, it looks good. A similar approach we need to implement for the sdran and roc Helm Charts. For the upf Helm Charts, we copy the same directory (not parent directory)


NOTIFY/LISTEN support?

Hello, just found this neat project.  I currently use queue_classic to process jobs, which doesn't use advisory locks but does use NOTIFY/LISTEN for efficiently picking up new jobs.  It looks like que currently uses polling to detect new jobs.
I see there has been some consideration for NOTIFY/LISTEN in #8 and #22 and the "experimental" branch.  Just wondering if that's still a feature being considered?  Polling works fine for my use case, but I'm just curious.  Thanks!

There was some work to support listen/notify, but it's incomplete, as far as I know.
Polling is super fast though, and works with connection balancers.

Thanks, yeah I should be perfectly fine just using polling.  And yeah I see there is an open issue on queue_classic in regards to issues w/ pgBouncer: https://github.com/QueueClassic/queue_classic/issues/184

The experimental branch (which replaces single-job polling with a mixture of LISTEN/NOTIFY and batch polling) is functional, though out of date with the changes made to master since that time. The main hurdle that's left, I think, is benchmarking to make sure its design works at scale, and to see what kind of improvement (if any?) it gives over master.
I'd like to get back to it at some point, but since I've been busy and master seems to have been fast enough for everyone's purposes, it just hasn't been a priority.

Thanks for the info!


Cant find model for this part

Cant find model for this part

Make sure the model is in your models/text_encoders folder

For me, simply copying the file didn't solve the problem, so I chose to run
git clone https://huggingface.co/PixArt-alpha/PixArt-XL-2-1024-MS
in ..\comfyui\models\text_encoders\ folder
(be advised, the size is ~40.7 GB)


Question

When will it be launched in the app store

Never😭

Never😭

😨😨😨😨😨i need it

THX! I'll try😭

😨😨😨😨😨i need it

THX! I'll try😭


'The string "claw" was not found' or - COMPLETE DECLAW #1267 #1314

GitHub Issue: https://github.com/Islandora/documentation/issues/1267 and https://github.com/Islandora/documentation/issues/1314
What does this Pull Request do?
Cleans out the last few traces of CLAW in urls and references, including the last holdout: ~claw-playbook~ islandora-playbook
What's new?
Not much! Just some url updates.
How should this be tested?
Preview the files and verify that the links still work.
Additional Notes:
I left the irc reference in CONTRIBUTING.md because it has not officially been deprecated yet, and this keeps CONTRIBUTING.md consistent across the board. It will probably need to be updated again for the irc -> Slack move, but I didn't see any need to hold up the deCLAWing for that.
Interested parties
@whikloj as maintainer

@manez totally not what you did, but we seem to have a duplicate "Development" section in the README.md. Could you remove the second one and then I'll merge this.

Or maybe the first one, the second section has an additional line.

@whikloj de-duped now


Feature request: provide a PyPI package

Although I appreciate the allure of getting loader code quickly and easily, I think the download_loader method of library distribution is problematic for many reasons:

It violates the principle of least astonishment.
It creates unnecessary runtime complexity and latency.
Makes it difficult to version dependencies.
Cannot be used in a secure environment because it increases the possibility for supply chain attacks.
Makes LlamaHub more difficult to use inside containers because it requires writeable disk cache.

It also looks like download_loader is already causing many issues, reported here (#81, #150, #209, etc.) and on Discord.
Perhaps I'm missing something, but the entire llama-hub code base is 1.6 MB so it seems that there's no reason it couldn't be built, versioned, and distributed using a well-understood mechanism like PyPI.

This happened today actually!

https://twitter.com/llama_index/status/1663703770893783040?s=20

Awesome! Huge props to the @jerryjliu for moving so fast. I will go ahead and close this.

yeah @krokicki tahnsk for flagging this, this issue was one of the motivations for creating the llama-hub package :)


itemIsObscuredByHeader() padding fix

While working on some code to add a shadow to headers I found an issue with the itemIsObscuredByHeader() function.  It didn't seem to consider the Recycler's padding like some of the other functions do.

Seems like a reasonable fix - can you say definitively that this is a bug and this is the fix?

Yep!

thanks a lot!


Target IP

Hello,
unfortunately I can't get any further with the setup...
We have an Aten VM0404HA this I have connected via RS323 to USB with the computer. How do I now get the target IP address? I can control the device via PuTTY without any problems.

Hi @micha122.  Since that model does not have an Ethernet port (as you've noted, just USB and RS232) you won't be able to control it with Companion.  Companion only supports control of devices via network control.


Fixed Python3.12 failing CI tests

Description
CI tests are failing in python3.12 on this workflow action under unit/coverage tests. Looking at the noxfile there was a temporary fix included for python3.12 in this commit which I included in other nox.sessions as well. Though it is a temporary fix, I tested it on my branch and it seems to be working.
Fixes # (issue)
Type of change
Please add a line in the relevant section of CHANGELOG.md to document the change (include PR #) - note reverse order of PR #s. If necessary, also add to the list of breaking changes.

[ ] New feature (non-breaking change which adds functionality)
[ ] Optimization (back-end change that speeds up the code)
[x] Bug fix (non-breaking change which fixes an issue)

Key checklist:

[x] No style issues: $ pre-commit run (or $ nox -s pre-commit) (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)
[x] All tests pass: $ python run-tests.py --all (or $ nox -s tests)
[x] The documentation builds: $ python run-tests.py --doctest (or $ nox -s doctests)

You can run integration tests, unit tests, and doctests together at once, using $ python run-tests.py --quick (or $ nox -s quick).
Further checks:

[x] Code is commented, particularly in hard-to-understand areas
[x] Tests added that prove fix is effective or that feature works

Thanks, @santacodes!


Improve tracking for rollback revisions

Problem
Tracking information about rollbacks is difficult because the actual rollback revision is only presented as string, as part of the "DESCRIPTION" column of helm history command.

The .Release.Revision field is no enough to do such tracking. In the example above, both "rev6" and "rev4" has .Release.Revision equals 2

@batiati thanks for the feature request. Is there a particular situation or use case this would be used in? We'd like to understand the broader context of the need.

@mattfarina
It's mainly because I'm managing a stateful application from a Helm Chart, using upgrade/rollback hooks to backup and restore some application data during its maintenance.

pre-upgrade => take a backup of the app data (saves it as rev_xx.bak where xx is the current rev number)

pre-rollback => take the same backup performed by pre-upgrade and then restore the rev_yy.bak file, where yy is now the rollback revision number.

As the hook manifest is already rendered during the rollback, I see that is not possible to access this value from {{ .Release.Revision }}, so I had to read it from api/command line.
Those jobs rely on the "rollback to ..." description message to identify which revision was ordered  by the user during the helm rollback command, but it's fragile, because this message can change in any future release.
Besides that, I have a little tracking tool that that uses this information to create reports for my team.

If we need to support this feature, we should need to adjust
https://github.com/helm/helm/blob/master/pkg/release/release.go#L22
https://github.com/helm/helm/blob/master/cmd/helm/history.go#L86
From the perspective of kubernetes, this information is independent. Is there any special reason for helm to combine Description and previousVersion?
@mattfarina @bacongobbler
I personally think that separate display may be more user-friendly and have more clear semantics. I look forward to your reply, if ok, I can try to contribute pr


chore: pkg imported more than once

[ ] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Changes

Verification

thanks @testwill :)))


basic jsonp support, useful for cross-domain without websockets

a little simpler than the other PR

Closing, thanks!


Some User model, different JSON keys?

I am using JSONJoy and SwiftHTTP, both are awesome, thanks!
Everything works great when using SwiftHTTP to create a local account (ie not using FB). However when using facebook login, the JSON object returns slightly different keys
For example, our local API returns firstName : Travis  FB returns first_name : Travis
I would like to use the same User model if possible and was wondering if there is a way I can assign firstName to either decoder["firstName"].string or decoder["first_name"].string depending on if I sent the local User object or the FB user object.
Cheers,
-Travis

Glad to hear it is helping out! Could you do something as simple as:
struct User {
    var objID: Int?
    var firstName: String?
    var lastName: String?
    init(_ decoder: JSONDecoder) {
        objID = decoder["id"].integer
        if let first = decoder["first_name"].string {
            firstName = first
        } else {
            firstName = decoder["firstName"].string
        }
        lastName = decoder["last_name"].string
        age = decoder["age"].integer
        address = Address(decoder["address"])
    }
}

Might be the fastest reply to a Github issue I've ever had!
That worked perfectly, thanks so much!


Make file data provider interface more precise [phab:D1345]

Created by salguarnieri at 2017-02-17 18:08:59:
The file data provider interface was not precise on how the two
parameters would be used, so I wrote documentation that matches what the
implementations were already doing. They both could be null and it is up
to the implementation to handle that since each implementation uses the
parameters in different ways.
There may be a few functional changes here since we are validating input
and throwing early if it is null.
I also added a test for FileDataCache. I wanted to add tests for the
other file data providers, but they are hardwired to file system
implementations that are too much work to abstract in this diff.

craigbarber accepted this revision at 2017-02-17 21:19:06

salguarnieri closed via commit e715918cfab513d5edecd22c0e08619a934661e5 at 2017-02-17 23:06:25


Options: Inherit LibSass defaults

As per this discussion which transpired here: https://github.com/sass/node-sass/issues/673, we need to inherit all options defaults from LibSass (except for paths). The key is to have conditional setting of those options in binding.cpp.
//cc @sindresorhus

We have two options, add ifs on setting every option, set all options for all cases and set default (the current behavior). I think the current behavior is better, i.e. not uglifying C++ code.
@xzyfer, thoughts?

The current behavior is less noisy at C++ side, so closing this one..


mitmdump memory grows

Steps to reproduce the problem:

Launch mitmdump, the options don't really seem to matter much(I've tried transparent, and regular proxy, with and without scripts)
Run htop or similar and filter for the mitmdump process, observe Res/Virt memory usage.
Load fast.com, or literally any website
Check memory usage again, observe that it's gone up(and will continue to increase as more requests are made).
Wait a while, and observe that the memory usage never goes back down.

Given ~10 minutes I'm able to grow the process from ~50MiB(when it initially starts before receiving any requests) to around ~550MiB(By just going to e.g. news.ycombinator.com and clicking through to every article link on the page). It seems to grow more when loading unique pages, refreshing the same page over and over again grows the resource usage, but not as quickly as loading different sites.
Any other comments? What have you tried so far?
I've tried setting websocket streaming to true, stream_large_bodies to 1, and different requests: I can trigger this behavior by just running curl to a local http-only(non-ssl) site in a loop. I also tried disabling http2.
I've seen a number of tickets about this, but nothing recent-ish. I saw there were great strides made in the past to fix these memory issues with mitmdump, so I'm curious if this bug report is useful to you.
https://github.com/mitmproxy/mitmproxy/issues/2828 - related recent issue
https://discourse.mitmproxy.org/t/mitmdump-large-memory-consumption/197
I am happy to run any additional tests/test out any patches/config options/etc. I'd also appreciate any pointers in the right direction to help narrow down the cause of the memory usage myself.
System information
I'm running inside a generic ubuntu:18.04 docker image, using system python and just doing pip3 install mitmproxy. I believe I've also tried the latest from git with the same issue.

# mitmdump --version
Mitmproxy: 4.0.4
Python:    3.6.7
OpenSSL:   OpenSSL 1.1.0g  2 Nov 2017
Platform:  Linux-4.15.0-43-generic-x86_64-with-Ubuntu-18.04-bionic

see the related issue
#3191
https://github.com/mitmproxy/mitmproxy/issues/3191#issuecomment-469557156

Come on, this turns this awesome software kind of useless.

A lot of improvement has been made since this was opened, most notably but not only because of the efforts in https://github.com/mitmproxy/mitmproxy/issues/4456


raretoshi panel support for unicode characters

See the following log output
Getting Raretoshi information for user RRizzling
Using cached data from<PHONE_NUMBER>
Holding 89 is video/mp4 which is unsupported.
Picking another at random. Check count 1.
Holding 83 is image/gif which is unsupported.
Picking another at random. Check count 2.
Picked holding 75 titled Un₿eliever V with ipfshash QmXwt9GFbe6R8R9giVMcqeavAsrUsjnh51V5kHLS5VCPdH

The title of the work is Un₿eliever V with the bitcoin symbol.
However the generated image ends up showing the empty box for unicode characters like this.
The font in use in the vicarioustext file is /usr/share/fonts/truetype/dejavu/DejaVuSans.ttf
May need to use a different font, at least for raretoshi.
Run with the following to reproduce
./raretoshi.py RRizzling 75

Tested with the /usr/share/fonts/truetype/noto/NotoMono-Regular.ttf font but it also fails

See also from
https://ourpython.com/python/does-pillow-want-my-text-parameters-to-be-unicode-or-strings

You're usually better off using explicit backslash escapes, like \u250c instead of ??, especially if you don't even know how to tell if the file is UTF-8, much less how to fix it.
Second, you almost never want to put non-ASCII characters into a str literal; use a unicode literal unless you have a good reason to do otherwise.
On top of that, if you pass draw.text a str, PIL will decode it with your default charset—which again is probably not UTF-8. So, even if everything else so far were correct, your code would be handing over some UTF-8 to be parsed as cp1252, so mojibake again. Using a unicode literal would avoid this problem entirely; otherwise, you need to pass text.decode('utf-8').
Putting that all together:
text = u"\u250c\u2500\u2510\u2502\u2514\u2518\u255e\u2550\u2561\u2564\u2567\u2558\u255b"
And now the coding declaration and the actual encoding used to save the file don't matter, because the file is pure ASCII.

will try multiple fonts installed with
sudo apt-get install ttf-mscorefonts-installer


distribution parameterization by keyword arguments

This is not really a feature request but rather a discussion item that concerns distributions like  NormalMeanVariance(), NormalMeanPrecision() etc.
Rather than
xt_min ~ NormalMeanVariance(xt_min_mean, xt_min_var)

is there a reason why we dont write
xt_min ~ Normal( mean=xt_min_mean, var=xt_min_var)

This way you can also write
xt_min ~ Normal( natural_mean=xt_m, precision=xt_v)

You get the idea. The parameter list determines whether you have the moment or information parameterization scheme.
I think it's cleaner and more consistent with other notation. Eg, we dont write GammaShapeScale but just Gamma for the Gamma distribution and all the exponential family distributions have moment and canonical parameterizations, so the user would not know if you use GammaShapeScale or GammaShapeRate. Here, I would also recommend
Gamma(shape= ..., scale= ...)

to make the chosen parameterization clear.

Added in https://github.com/biaslab/GraphPPL.jl/pull/18


build(git): use setup-git-credentials for auto-merge workflow

Pull Request Test Coverage Report for Build 18b2bdc2-5d54-482b-9453-d4776472a19a

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

Totals

Change from base Build 754aa3f5-7e69-4399-8d10-042e9ba1996d:
0.0%

Covered Lines:
1453

Relevant Lines:
1506

💛  - Coveralls


Graphics and 2 WebGLRenderers

https://github.com/pixijs/pixi.js/blob/dev/src/core/graphics/webgl/GraphicsRenderer.js#L84
This part of code assumes that we have only one webgl renderer. We need to switch "dirty" to versions, and update current version of webglGraphicsData.

we do! good catch

Issue found at "tankwars.io" project. We thought its a mask problem, but it turns that it isnt: http://imgur.com/a/wOvYC

Same in Mesh (dirty, indexDirty)

fixed! 👍


[Bug] Wrong device name for ZenWiFiAX XT8

The problem
Since HA 2023.3 and last 2 versions of AsusRouter my ZenWiFiAX XT8 (router + node) is being added as a RT-AX95Q and it seems my mesh node is being added as a ZenWiFiAX. They used to have the same name in earlier versions. But now they are completely different.
I also lost the some entities like my Guest WLAN switches.
Tried to reinstall 0.22.0 but problem stays the same.
Older versions don't seem to work with HA 2023.3 any more, so I cannot test those.
Also after rebooting HA, it keeps finding new integrations for the ZenWiFiAX router even though both the router and node are already installed.
Your device model
ZenWiFi AX (XT8)
Firmware type
Stock
Firmware version
<IP_ADDRESS>.388_22525
Integration version with the issue
0.22.0
Method of the integration installation
HACS
What version and type of Home Assistant installation do you use
Frontend 20230306.0
Is there anything useful in the logs?
No response
Diagnostics information
No response
Additional information
No response

Hello, @EBassie,
Can you please append diagnostics for both devices? Actually, RT-AX95Q is one of the names for Zen WiFi. And some devices are reporting it exactly this way. But would be strange, if it changed with the integration update since integration is not deciding anything - just asks the device for a name explicitly. Did you maybe also update firmware only on one of the devices?

Hi Vaskivskyi,
thanks for you reply. I don't really care about the devices being named different than before, but the troublesome thing is that I have lost a bunch of sensors, like the WiFi Toggles.
When I download the diagnostics for both devices, the file is identical for both:
config_entry-asusrouter.txt
But I find it weird that the names are not identical:

Both devices are on the same firmware: <IP_ADDRESS>.388_22525
Also the diagnostics show installed version of AsusRouter is 0.21.1, while HACS shows 0.22.0

Hello. Sorry for the late reply. If you are up to it, please, check the latest beta release 0.23.0b1 of the integration and let me know whether you got access to the sensors missing before or you still have the same / other issues

With 0.27.0 the model name should now correspond to the UI Model Name as defined by Asus. Also, it should now be the same for the main device added to HA and AiMesh node devices created automatically for each node.


Fix small docs typo

In docs/basics.rst I changed new package your provided. to new package you provided.

🌀


tighter dependency versions or package lockfile?

The loose versioning in package.json combined with a lack of lockfile can cause tricky to track down issues.  We recently had some specs start to fail in CI due to zip.js updating itself causing a failure due to the inclusion of TransformStream.
Have you considered either tightening the versions of dependencies or including a lockfile?
Our workaround: https://github.com/PropellerAero/cesium/commit/d951fe303f7b8bfe19a2b489284abe79e4121005

Hi @chris-cooper, thanks for bringing this up.
We moved to looser versioning a few years ago in order to prevent conflicts. However, given that we've just changed our strategy around third party modules and have moved several devDependencies to dependencies, it may be time to consider a lockfile to ensure consistency.

Looking into this a bit more, while they work well for application development, lockfiles are not a recommended best practice for libraries. So we're unlikely to go with a full lockfile approach. However, there was another issue related to the zip library which we fixed by pinning a specific version. In the future, we'll likely stick with the pinning approach where needed. As of part of that fix, we are introducing more tests to our CI to catch such issues as they arise.


Run API (Request, Response) Executions

ZITADEL is able to run configured request and response executions whenever an API is called.
Acceptance Criteria

[ ] When an API endpoint is called the configured requests/ response executions are executed
[ ] ZITADEL decides which condition is triggered like a proxy, the most exact match is executed
[ ] Request Executions are triggered as before any ZITADEL business logic is done
[ ] Response Executions are triggered after ZITADEL business logic is done
[ ] All endpoints are included, this means Admin, Mgmt, Auth, Assets, OIDC, SAML, New Ressource Services such as User, Session, etc
[ ] Response codes from target are handled as follow:
successful: >= 200, < 300
follow redirect: >= 300, < 400
failure >= 400
[ ] Documentation is extended

[ ] Include an example for a trigger that should be run when a user has been added

Questions to answer before estimation
What information should be sent to target?
How do we handle secret? Should there be a possibility to enable/disable sending secrets?
Additional Information
Example for tiggering:
Given the endpoint User.Human.Added is called
and execution configuration for User.Human.* and for User.Human.Added exist
only User.Human.Added will be executed
Given the endpoint User.Human.Added is called
and execution configuration for User.Human.* and for User* exist
only User.Human.* will be executed

@peintnermax @stebenz
There are some open questions that should be answered before we can estimate and start with the issue. Can you please have a look at it.

Estimation:

definition of sent and received data: 1d
logic to handle calls to target: 1d
integration tests with external target: 1d
interceptor with check for available conditions: 0.5d
unit tests for the interceptor best match: 0.5d
example documentation: 0.5d


[SPARK-20688][SQL] correctly check analysis for scalar sub-queries

What changes were proposed in this pull request?
In CheckAnalysis, we should call checkAnalysis for ScalarSubquery at the beginning, as later we will call plan.output which is invalid if plan is not resolved.
How was this patch tested?
new regression test

cc @rxin @gatorsmile

Test build #76725 has started for PR 17930 at commit 3ccff2e.

LGTM

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76725/
Test FAILed.

retest this please

Test build #76733 has started for PR 17930 at commit 3ccff2e.

Not introduced by this pr, but I just saw a style nit here
             if (conditions.isEmpty && query.output.size != 1) {
                failAnalysis(
                 s"Scalar subquery must return only one column, but got ${query.output.size}")
             }
             else if (conditions.nonEmpty) {

Test build #76739 has started for PR 17930 at commit 013137f.

Test build #76733 has finished for PR 17930 at commit 3ccff2e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76733/
Test PASSed.

Test build #76739 has finished for PR 17930 at commit 013137f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76739/
Test PASSed.


WIP: Update ApplicantBadge and include ApplicantGrid

This PR updates the ApplicantBadge API to
<ApplicantBadge
  id={123123}
  onClick={id => console.log('Applicant selected: ' + id)}
  name={'Ryan Chartrand'}
<EMAIL_ADDRESS>  info={[
    {
      label: 'Avail. date:',
      value: '11/05/2018',
      tip: 'I\'m not currently seeking opportunities.'
    },
    {
      label: 'Timezone:',
      value: 'UTC+7'
    },
    {
      label: 'Rate:',
      value: '$40'
    }
  ]}
  tags={[
    'JavaScript',
    'ES2015',
    'Node',
    'Express',
    'React',
    'Redux',
    'Webpack'
  ]}
/>

and includes the ApplicantGrid:
// items is an array of ApplicantBadge's
<ApplicantGrid
  items={items}
  visible={3}
  increment={2}
/>

Note: I made this components compatible with the following task https://zube.io/x-team/xp-formerly-auto/c/1638. Both the ApplicantBadge and ApplicantGrid should be compatible with tabular view. The ApplicantBadge was made using CSS Grid and Flexbox in a way that is possible to rearrange elements and update styles.

Hi @bernardodiasc Please note that I updated PR title to denote the fact it's a work in progress, in addition to the PR label. Once the work is finished, please remove that prefix from the title 😏 Thanks.

@bernardodiasc what are these .snap files? Do we need to have them in the PR or it's something can be generated separately? Would be easier to review this without them so we can focus on what's changed in the code


Big delete icon in cart if the cart is not empty

url is /cart/
The icon is huge ............... LOL

@osess Yes, there is a bug with this icon, we're already working on it.


coq2html: 20170720 -> unstable-2021-04-22

Motivation for this change
Bump a very outdated version
cc maintainer @jwiegley
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 121241 at 825e890d run on x86_64-linux 1

2 packages built successfully:

compcert
coq2html

1 suggestion:

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/applications/science/logic/coq2html/default.nix:16:3:
   |
16 |   installPhase = ''
   |   ^

@SuperSandro2000 this is an OCaml package

I am not comfortable in Coq or ocaml. Sorry.


automated summary graf of insights

this would go below the map, and could function like a descriptive takeaway of what is in the map/data. it could be a few sentences, essentially a visually glorified figcaption. it would be a little bit of dynamic language depending on the situation and give it some more plain language feel.

could make it dynamic, like "Although Cambridge (Canada) is the biggest place, Cambridge, MA has a combination of proximity and Wiki size to make it the most likely referenced place"

there are 23 pittsfields, it probably means MA in most places, and maybe in X (with color encoding)

Now that i'm looking at it, I don't think you need the text description, although it could be good as just a figcaption. But i'm curious what someone with fresher eyes would think, like if the text description helps you read the map


[AttributeError] module 'wandb' has no attribute 'init'

  I try to search on the Internet ,ask chat GPT and turn to my friend for help but didn‘t solve the problem.

install the 0.15.6 version of wandb in my anaconda python environment , and successfully login my account. Then i wrote a simple test code using wandb. everything was fine, i got the plot.
Question: But when I added wandb code to my project code , An attribute Error was reported.

I did import the package wandb and write wandb.init(project="project_name") in the right place.
Also I can find the function init() in wandb code.
The version of wandb I'm using doesn't conflict with other dependent packages(tensorflow==1.14.0,gym==18.3,torch==1.10.0)
The sample code given in the official documentation is available

this is the code that reported error
`from .Enterprise import Enterprise
from .Bank import Bank
import matplotlib
matplotlib.use('agg')
import matplotlib.pyplot as plt
import os
import time
import shutil
from pandas import DataFrame
import wandb
wandb.init(project="cortex22_anna")
plt.rcParams["font.sans-serif"]=["SimHei"] #设置字体
plt.rcParams["axes.unicode_minus"]=False #该语句解决图像中的“-”负号的乱码问题
base_path_default =  'E:\run'
class Logger:{...}
`

My guess is that you have a wandb directory that contains an __init__.py or a wandb.py file in your working directory which causes the import to resolve to the local files instead of the installed wandb. If that is the case, you will have to rename or remove these files or folders in the local working directory.

thanks for your kind help

I do have a a wandb directory that contains an init.py ,this is the path of the init.py. C:\Users\lyk.conda\envs\sevenpython36\Lib\site-packages\wandb .  I try to remove it but still has error.

my working directory only has one wandb directory contains some running logs.

Also I find when I run a single python file are fine ,but This problem only occurs when my project code has referential relationship. Such as I wrote it in Logger.py and used in environment.py

My guess is that you have either:

a wandb directory that contains an __init__.py, or
a wandb.py file in your working directory.

These would cause the import to resolve to the local files instead of the installed wandb. If that is the case, you will have to rename or remove these files or folders in the local working directory.

thanks for your kind help

I do have a a wandb directory that contains an init.py ,this is the path of the init.py. C:\Users\lyk.conda\envs\sevenpython36\Lib\site-packages\wandb .  I try to remove it but still has error.

my working directory only has one wandb directory contains some running logs.

Also I find when I run a single python file are fine ,but This problem only occurs when my project code has referential relationship. Such as I wrote it in Logger.py and used in environment.py

I did another test , it proves code has referential relationship dose not cause the error . crazy!!!!

My guess is that you have either:

a wandb directory that contains an __init__.py, or
a wandb.py file in your working directory.

These would cause the import to resolve to the local files instead of the installed wandb. If that is the case, you will have to rename or remove these files or folders in the local working directory.

thanks for your kind help

I do have a a wandb directory that contains an init.py ,this is the path of the init.py. C:\Users\lyk.conda\envs\sevenpython36\Lib\site-packages\wandb .  I try to remove it but still has error.
my working directory only has one wandb directory contains some running logs.
Also I find when I run a single python file are fine ,but This problem only occurs when my project code has referential relationship. Such as I wrote it in Logger.py and used in environment.py

I did another test , it proves code has referential relationship dose not cause the error . crazy!!!!

I am sorry I did not make it clear. Do not remove the __init.py__ file in that wandb directory. If you did that, you will have to uninstall and reinstall wandb.
I only meant to delete those in your working directory, if they exist.
You may run print(wandb.__file__) before wandb.init to see what files are interfering with the process.

I am sorry I did not make it clear. Do not remove the __init.py__ file in that wandb directory. If you did that, you will have to uninstall and reinstall wandb. I only meant to delete those in your working directory, if they exist. You may run print(wandb.__file__) before wandb.init to see what files are interfering with the process.

Thank you so much.
I try to run the code you gave but in the project code it reported an AttributeError: module 'wandb' has no attribute '__file__' .
I also try it in another useable test code and the result are correct C:\Users\lyk\.conda\envs\sevenpython36\lib\site-packages\wandb\__init__.py
P.S. both these two codes are in the same conda environment

Then I guess the python you used in your project code is not finding wandb correctly.
You may try printing __path__ attribute of wandb to confirm. However, I cannot know the root cause now.
You may try moving the wandb directory that contains run files inside the working directory to somewhere else and try again.
If that works, it is a name resolution order issue; if that did not work with 'no module named wandb', then the path to conda is corrupted in your project. In either case you should check for files that modified sys.path and fix them to fix the problem completely.
If that still fails with the same AttributeError, and printing __path__ also fails, I recommend you posting a minimal version of your project here for reproducing the problem.

Then I guess the python you used in your project code is not finding wandb correctly.
You may try printing __path__ attribute of wandb to confirm. However, I cannot know the root cause now.
You may try moving the wandb directory that contains run files inside the working directory to somewhere else and try again.
If that works, it is a name resolution order issue; if that did not work with 'no module named wandb', then the path to conda is corrupted in your project. In either case you should check for files that modified sys.path and fix them to fix the problem completely.
If that still fails with the same AttributeError, and printing __path__ also fails, I recommend you posting a minimal version of your project here for reproducing the problem.

I tried everything you said,

the path of  wandb in my working directory is: ['C:\\Users\\\lyk\\\Desktop\\\\\Cortex22_Anna\\real_System_remake\\\wandb'],
and after I moved the directory where run files are located in wandb, it says no module named wandb,
then I checked sys.path and found that there is a problem with the path and added the path of wandb in my conda environment: C:/Users/lyk/.conda/envs/sevenpython36/Lib/site-packages/wandb", then the error is still exist

Sadly , my project is so coupled it's hard to take out the smallest part of the instances.
Anyway thanks so much for your help. As much as this bug is killing me, I feel very lucky to have your answer.
P.S.
this is part of my sys.path
path = [
    'F:\\pycharm\\PyCharm 2022.1.1\\plugins\\python\\helpers',
    'F:\\pycharm\\PyCharm 2022.1.1\\plugins\\python\\helpers\\generator3',
    'C:\\Users\\lyk\\.conda\\envs\\sevenpython36\\python36.zip',
    'C:\\Users\\lyk\\.conda\\envs\\sevenpython36\\DLLs',
    'C:\\Users\\lyk\\.conda\\envs\\sevenpython36\\lib',
    'C:\\Users\\lyk\\.conda\\envs\\sevenpython36',
    'C:\\Users\\lyk\\.conda\\envs\\sevenpython36\\lib\\site-packages',
    'C:\\Users\\lyk\\.conda\\envs\\sevenpython36\\lib\\site-packages\\wandb',
    'C:/Users/lyk/.conda/envs/sevenpython36/DLLs',
    'C:/Users/lyk/.conda/envs/sevenpython36/Lib',
    'C:/Users/lyk/.conda/envs/sevenpython36/Lib/site-packages',
    'C:/Users/lyk/.conda/envs/sevenpython36/Lib/site-packages/wandb'
]

Did you print that sys.path just before the wandb.init that is causing the error? If not please do so.

OMG, I think I found the difference between the correct code and the error code sys.path, in the test code sys.path is correct, but in the error code the path is really the local python environment path. 'F:\\python\\python36.zip', 'F:\\python\\DLLs', 'F:\\python\\lib', 'F:\\python', 'F:\\python\\lib\\site-packages']
I find that though my pycharm environment is set up as my conda environment but my project code 's run configuration has been set up as local python interpreter!!
Now it is working!!
thank you so much!!
very happy to met you !!
have a good day!

See, you are missing C:/Users/lyk/.conda/envs/sevenpython36/Lib/site-packages (where wandb is located). Most probably you are actually activating a wrong conda environment somewhere. Or perhaps you have some code that wrongly modifies sys.path, or installed a library that does it wrongly.
You should fix these root causes. If you still cannot figure it out though, a workaround could be:
import sys
sys.path.insert(0, 'C:/Users/lyk/.conda/envs/sevenpython36/Lib/site-packages')
import wandb
wandb.init(project="cortex22_anna")

OMG, I think I found the difference between the correct code and the error code sys.path, in the test code sys.path is correct, but in the error code the path is really the local python environment path. 'F:\python\python36.zip', 'F:\python\DLLs', 'F:\python\lib', 'F:\python', 'F:\python\lib\site-packages']
I find that though my pycharm environment is set up as my conda environment but my project code 's run configuration has been set up as local python interpreter!!
Now it is working!!
thank you so much!!
very happy to met you !!
have a good day!

@eliphatfs Thanks a lot for your help!
@hugo4777 Glad to see that your issue is resolved closing this issue!


Updating custom OpenAI Gym environment developed with version 0.13.0 to Gymnasium version 0.29.0 ?

Question
Hello dear members of Farama-Foundation Team!
I have been using a custom OpenAI Gym environment that was developed using the version 0.13.0 of the Gym library. What would be the necessary steps that I would have to follow in order to update the environment to the latest Gymnasium 0.29.0 spec? Can you provide me with any supporting material or guide for achieving this goal?
Thank you very much for your valuable help!
Kind regards,
Christos Peridis

Hi @ChristosPeridis,
Thanks for wanting to update
V0.13.0 is so old that I have no idea what the API is
https://gymnasium.farama.org/content/migration-guide/
This is a migration guide for v0.21 to the latest API


Add 'post_condition' arg in CI script

Part of Issue
New argument: post_condition
Could be:
post_condition:'{"always":"true"}' - always post comments
post_condition:'{"has_diff":"true"}' - post comments if it has output
post_condition:'{"percentage_threshold":"2"}' - post comment if absolute_percent more than percentage_threshold

@aliscott what were the steps you ran to test this script locally?
@ekifel great start! here are my suggestions:

see post_condition as a new parameter so we don't break this for existing users.
if someone uses percentage_threshold, output this Warning: The percentage_threshold parameter is deprecated and will be removed in v0.9.0, please use post_condition='{"percentage_threshold":"2"}'.
if someone sets percentage_threshold && post_condition, then only use post_condition and output this Warning: The percentage_threshold parameter is deprecated, using post_condition instead.

Also, https://www.shellcheck.net/ might be useful too

@aliscott what were the steps you ran to test this script locally?

I'm just running scripts/ci/diff.sh examples/terraform just now and then echoing out some vars.

@ekifel sorry this took a while to review, testing it isn't quick... I've pushed a commit that fixes a few things, feel free to review.


Add pascals-triangle exercise

@dalexj nice! A coulomb small issues, but it looks good!

changed to match your comments @parkerl

Looks good to me, @rubysolo?

cou·lomb
ˈko͞oˌläm,-ˌlōm`
noun
the SI unit of electric charge, equal to the quantity of electricity conveyed in one second by a current of one ampere.

Autocorrect is just making sure you are up on your SAT words. 😠


i cant find how to open the ui

im kinda new to this, but how can i open the "gradio link", i ran the unified code but i cant find how to open the actual ai

thewre was a error occuring, i tried removing some models and it worked out.


Approval needed for Pull Request #48 to improve user privacy

Hello,
I would like to request approval for Pull Request #48, which modifies the code related to allowing users to share a conversation publicly. This change is aimed at improving user privacy and preventing accidental sharing.
The commit includes code changes that display a confirmation dialog to the user when they click the "Share" button. The dialog informs the user that they are about to share the conversation publicly and asks them to confirm their choice. Additionally, the dialog includes a notice telling the user that they need to click "OK" before sharing.
With these changes, it will be clearer to users that they are sharing their conversations publicly and give them an opportunity to reconsider their choice before sharing.
I believe this is an important improvement to the user experience and privacy of our platform, and I kindly request approval for the pull request.
Thank you.

Thanks for this @saliksik. Improving user security is a top priority but we're looking into other ways to achieve this (for example, via onboarding when a user first signs into an app) so I'm closing for now.


[FEATURE] Provide support for installing global node modules

I don't see any interface to installing node_modules during docker-compose up action.
I am thinking these can be added to the docker-compose.yml something like the following:
    workspace:
        build:
            context: ./workspace
            args:
                - INSTALL_NODE=true
        tty: true
        node_modules:
          - karma
          - mocha
          - gulp

All the modules will be installed if the INSTALL_NODE flag is true.
If you are interested in having this added, i will take care of it and submit a new PR accordingly

@mikeerickson Good idea to install node modules when building containers.
I have to say however that I don't think we should keep node modules in the compose file.
I'd say we could have a build argument INSTALL_NODE_MODULES that when turned to true installs the node modules (in the package.json) using YARN/NPM depending on the package manager selected.
Does that make sense to you?

@mikeerickson Btw no need to use a prefix for your issues, we have labels to categorize them :)

@philtrep in this case, these are global modules, not specific to project.
For example, I have a number of modules which I install globally on local development which I keep reaching for but aren't installed (available from workspace)
$ npm i -g npms-cli
$ npm i -g package-menu-cli
$ npm i -g np
etc

@philtrep regarding prefix, will do :)

@mikeerickson I see, I would still keep them as build arguments but adding the options to have these 3 modules globally available is definitely a good idea.

@philtrep I get what you are saying. I will go down that and see how it flows. Making this the "official" docker project one feature at a time :)

@philtrep Starting work on this item....