Cloning the Repository inside a Container from GitHub

What happened?
My ideal development environment is inside a devcontainer, where the volume is cloned inside, rather than mounted (for performance reasons). Unfortunately I get an error, when I try to clone the repository inside the devcontainer.
What should've happened instead?
The repository should be cloned inside the devcontainer successfully.
Additional details

I've setup a repository to test with here, it's a fresh setup with cookiecutter.
Creating the devcontainer and mounting the volume works just fine - but is very slow.

  Keep-alive process started."  Keep-alive process started." ; export VSCODE_REMOTE_CONTAINERS_SESSION=c841ddbe-f112-4b39-9e8b-26634cff80231724168621578 ; /bin/sh
[2024-08-20T15:44:01.901Z] Exit code 1
[2024-08-20T15:44:01.902Z] Keep-alive process ended.
[2024-08-20T15:44:01.943Z] Start: Run in container: uname -m
[2024-08-20T15:44:02.047Z] Stop (149 ms): Run in container: /bin/sh
[2024-08-20T15:44:02.048Z] Start: Run in container:  (command -v getent >/dev/null 2>&1 && getent passwd 'dev-user' || grep -E '^dev-user|^[^:]:[^:]:dev-user:' /etc/passwd || true)
[2024-08-20T15:44:02.048Z] Stdin closed!
[2024-08-20T15:44:02.049Z] Start: Run: docker rm -f e884d4ec1409be0e55659c71a718e4952695a43bbfa0603eb88fbcb901be92e9
[2024-08-20T15:44:02.058Z] Shell server terminated (code: 1, signal: null)
Error response from daemon: container 34c44327f35af70523c0d1b5ac883f46313e6a0a918b6d8bf1f51f1da3fc5f4b is not running
[2024-08-20T15:44:02.284Z] Stop (12884 ms): Run in container: /bin/sh
[2024-08-20T15:44:02.284Z] Stop (12369 ms): Run in container: /bin/sh
[2024-08-20T15:44:02.285Z] Container server terminated (code: 137, signal: null).
[2024-08-20T15:44:02.794Z] Stop (745 ms): Run: docker rm -f e884d4ec1409be0e55659c71a718e4952695a43bbfa0603eb88fbcb901be92e9
[2024-08-20T15:44:18.325Z] Start: Run: docker volume ls -q
[2024-08-20T15:44:18.457Z] Stop (132 ms): Run: docker volume ls -q
[2024-08-20T15:44:18.459Z] Getting Docker parameters for own remote.
[2024-08-20T15:44:18.583Z] Start: Run: docker version --format {{json .}}
[2024-08-20T15:44:18.783Z] {"Client":{"Version":"27.0.3","ApiVersion":"1.46","DefaultAPIVersion":"1.46","GitCommit":"7d4bcd8","GoVersion":"go1.21.11","Os":"windows","Arch":"amd64","BuildTime":"Sat Jun 29 00:03:32 2024","Context":"desktop-linux"},"Server":{"Platform":{"Name":"Docker Desktop 4.32.0 (157355)"},"Components":[{"Name":"Engine","Version":"27.0.3","Details":{"ApiVersion":"1.46","Arch":"amd64","BuildTime":"Sat Jun 29 00:02:50 2024","Experimental":"false","GitCommit":"662f78c","GoVersion":"go1.21.11","KernelVersion":"<IP_ADDRESS>-microsoft-standard-WSL2","MinAPIVersion":"1.24","Os":"linux"}},{"Name":"containerd","Version":"1.7.18","Details":{"GitCommit":"ae71819c4f5e67bb4d5ae76a6b735f29cc25774e"}},{"Name":"runc","Version":"1.7.18","Details":{"GitCommit":"v1.1.13-0-g58aa920"}},{"Name":"docker-init","Version":"0.19.0","Details":{"GitCommit":"de40ad0"}}],"Version":"27.0.3","ApiVersion":"1.46","MinAPIVersion":"1.24","GitCommit":"662f78c","GoVersion":"go1.21.11","Os":"linux","Arch":"amd64","KernelVersion":"<IP_ADDRESS>-microsoft-standard-WSL2","BuildTime":"2024-06-29T00:02:50.000000000+00:00"}}
[2024-08-20T15:44:18.790Z] Stop (207 ms): Run: docker version --format {{json .}}

Is it a game that you are playing that we need to find the error ourselfs?

Creating the devcontainer and mounting the volume works just fine - but is very slow.

Define "slow" please. Is it slow just the first time or every time? I don't use devcontainers myself, but AFAIU, it uses the main Django image from docker compose, so yeah, it takes a few minutes. The whole config is under .devcontainer/devcontainer.json and it's here in the template:
https://github.com/cookiecutter/cookiecutter-django/blob/master/{{cookiecutter.project_slug}}/.devcontainer/devcontainer.json
We're happy to accept any performance improvements via pull request, if you can provide some, but it's most likely due to Docker being slow.

Is it a game that you are playing that we need to find the error ourselfs?

What kind of reply is that supposed to be? I'm here and try to find guidance and thats how you response to people?

Creating the devcontainer and mounting the volume works just fine - but is very slow.

Define "slow" please. Is it slow just the first time or every time? I don't use devcontainers myself, but AFAIU, it uses the main Django image from docker compose, so yeah, it takes a few minutes. The whole config is under .devcontainer/devcontainer.json and it's here in the template:
https://github.com/cookiecutter/cookiecutter-django/blob/master/{{cookiecutter.project_slug}}/.devcontainer/devcontainer.json
We're happy to accept any performance improvements via pull request, if you can provide some, but it's most likely due to Docker being slow.

On windows there is a massive performance difference between cloning a repository inside a devcontainer or mounting it. The difference becomes exponentially bigger the more files there are, in Django projects, there are quite a few, especially due to the venv and node Modules. In my personal project I've originally created based off of this repository, slow means running simple tests takes about ~30 seconds, which is very frustrating.
I think this is something that must be fixed on your side. I'm not saying it is an error you're having in the code, but the Dockerfile most likely needs some finetuning to work with this devcontainer feature. I'm just not sure what it could be and was hoping there is someone here that is more experienced with it.

 Keep-alive process started."  Keep-alive process started." ; export VSCODE_REMOTE_CONTAINERS_SESSION=c841ddbe-f112-4b39-9e8b-26634cff80231724168621578 ; /bin/sh
[2024-08-20T15:44:01.901Z] Exit code 1
[2024-08-20T15:44:01.902Z] Keep-alive process ended.
[2024-08-20T15:44:01.943Z] Start: Run in container: uname -m
[2024-08-20T15:44:02.047Z] Stop (149 ms): Run in container: /bin/sh
[2024-08-20T15:44:02.048Z] Start: Run in container:  (command -v getent >/dev/null 2>&1 && getent passwd 'dev-user' || grep -E '^dev-user|^[^:]:[^:]:dev-user:' /etc/passwd || true)
[2024-08-20T15:44:02.048Z] Stdin closed!
[2024-08-20T15:44:02.049Z] Start: Run: docker rm -f e884d4ec1409be0e55659c71a718e4952695a43bbfa0603eb88fbcb901be92e9
[2024-08-20T15:44:02.058Z] Shell server terminated (code: 1, signal: null)
Error response from daemon: container 34c44327f35af70523c0d1b5ac883f46313e6a0a918b6d8bf1f51f1da3fc5f4b is not running
[2024-08-20T15:44:02.284Z] Stop (12884 ms): Run in container: /bin/sh
[2024-08-20T15:44:02.284Z] Stop (12369 ms): Run in container: /bin/sh
[2024-08-20T15:44:02.285Z] Container server terminated (code: 137, signal: null).
[2024-08-20T15:44:02.794Z] Stop (745 ms): Run: docker rm -f e884d4ec1409be0e55659c71a718e4952695a43bbfa0603eb88fbcb901be92e9
[2024-08-20T15:44:18.325Z] Start: Run: docker volume ls -q
[2024-08-20T15:44:18.457Z] Stop (132 ms): Run: docker volume ls -q
[2024-08-20T15:44:18.459Z] Getting Docker parameters for own remote.
[2024-08-20T15:44:18.583Z] Start: Run: docker version --format {{json .}}
[2024-08-20T15:44:18.783Z] {"Client":{"Version":"27.0.3","ApiVersion":"1.46","DefaultAPIVersion":"1.46","GitCommit":"7d4bcd8","GoVersion":"go1.21.11","Os":"windows","Arch":"amd64","BuildTime":"Sat Jun 29 00:03:32 2024","Context":"desktop-linux"},"Server":{"Platform":{"Name":"Docker Desktop 4.32.0 (157355)"},"Components":[{"Name":"Engine","Version":"27.0.3","Details":{"ApiVersion":"1.46","Arch":"amd64","BuildTime":"Sat Jun 29 00:02:50 2024","Experimental":"false","GitCommit":"662f78c","GoVersion":"go1.21.11","KernelVersion":"<IP_ADDRESS>-microsoft-standard-WSL2","MinAPIVersion":"1.24","Os":"linux"}},{"Name":"containerd","Version":"1.7.18","Details":{"GitCommit":"ae71819c4f5e67bb4d5ae76a6b735f29cc25774e"}},{"Name":"runc","Version":"1.7.18","Details":{"GitCommit":"v1.1.13-0-g58aa920"}},{"Name":"docker-init","Version":"0.19.0","Details":{"GitCommit":"de40ad0"}}],"Version":"27.0.3","ApiVersion":"1.46","MinAPIVersion":"1.24","GitCommit":"662f78c","GoVersion":"go1.21.11","Os":"linux","Arch":"amd64","KernelVersion":"<IP_ADDRESS>-microsoft-standard-WSL2","BuildTime":"2024-06-29T00:02:50.000000000+00:00"}}
[2024-08-20T15:44:18.790Z] Stop (207 ms): Run: docker version --format {{json .}}

Not sure what's relevant to be honest...

My ideal development environment is inside a devcontainer, where the volume is cloned inside, rather than mounted (for performance reasons). Unfortunately I get an error, when I try to clone the repository inside the devcontainer.

I assume cookicutter django is mounting the volume inside the container?
Can you point out what did you change to switch to the other version?
What else di you try that did not work?

the Dockerfile most likely needs some finetuning to work with this devcontainer feature

That's possible, yes. As I said, we're happy to receive any improvements.

was hoping there is someone here that is more experienced with it.

Fair enough. I don't have much experience with it, but you can perhaps look at what was done in the past:

https://github.com/cookiecutter/cookiecutter-django/pull/4198
https://github.com/cookiecutter/cookiecutter-django/pull/4517
https://github.com/cookiecutter/cookiecutter-django/pull/4708

cc @masavini who initially contributed the feature


STORM-2300 [Flux] support list of references

Please refer STORM-2300 for more details.

introduce reflist
introduce BeanListReference which stores list of id of references
handle BeanListReference properly
modify unit test for testing reflist

This feature supports method which arguments contain List, Type[], Type... (varargs).

+1. Looks good.


The parameter logits has invalid values

Thanks for sharing such an interesting repo. However, when I run the code the following bugs appear:
Traceback (most recent call last):
File "/projappl/project_2008459/InforMARL-dev/onpolicy/scripts/train_mpe.py", line 315, in
main(sys.argv[1:])
File "/projappl/project_2008459/InforMARL-dev/onpolicy/scripts/train_mpe.py", line 300, in main
runner.run()
File "/projappl/project_2008459/InforMARL-dev/onpolicy/runner/shared/graph_mpe_runner.py", line 76, in run
train_infos = self.train()
File "/projappl/project_2008459/InforMARL-dev/onpolicy/runner/shared/base_runner.py", line 168, in train
train_infos = self.trainer.train(self.buffer)
File "/projappl/project_2008459/InforMARL-dev/onpolicy/algorithms/graph_mappo.py", line 298, in train
actor_grad_norm, imp_weights, actor_bt, critic_bt = self.ppo_update(sample, update_actor)
File "/PUHTI_TYKKY_4v1SrvP/miniconda/envs/env1/lib/python3.9/site-packages/torch/cuda/amp/autocast_mode.py", line 139, in decorate_autocast
return func(*args, **kwargs)
File "/projappl/project_2008459/InforMARL-dev/onpolicy/algorithms/graph_mappo.py", line 152, in ppo_update
values, action_log_probs, dist_entropy = self.policy.evaluate_actions(
File "/projappl/project_2008459/InforMARL-dev/onpolicy/algorithms/graph_MAPPOPolicy.py", line 255, in evaluate_actions
action_log_probs, dist_entropy = self.actor.evaluate_actions(
File "/projappl/project_2008459/InforMARL-dev/onpolicy/algorithms/graph_actor_critic.py", line 260, in evaluate_actions
action_log_probs, dist_entropy = self.act.evaluate_actions(
File "/projappl/project_2008459/InforMARL-dev/onpolicy/algorithms/utils/act.py", line 215, in evaluate_actions
action_logits = self.action_out(x, available_actions)
File "/PUHTI_TYKKY_4v1SrvP/miniconda/envs/env1/lib/python3.9/site-packages/torch/nn/modules/module.py", line 889, in _call_impl
result = self.forward(*input, **kwargs)
File "/projappl/project_2008459/InforMARL-dev/onpolicy/algorithms/utils/distributions.py", line 94, in forward
return FixedCategorical(logits=x)
File "/PUHTI_TYKKY_4v1SrvP/miniconda/envs/env1/lib/python3.9/site-packages/torch/distributions/categorical.py", line 64, in init
super(Categorical, self).init(batch_shape, validate_args=validate_args)
File "/PUHTI_TYKKY_4v1SrvP/miniconda/envs/env1/lib/python3.9/site-packages/torch/distributions/distribution.py", line 53, in init
raise ValueError("The parameter {} has invalid values".format(param))
ValueError: The parameter logits has invalid values
Could you please take a look?

Hi @hsvgbkhgbv! Could you please let me know the command you are running to execute, the OS and whether you are running it on a GPU or not?

My OS info is as follows:
NAME="Rocky Linux"
VERSION="8.10 (Green Obsidian)"
ID="rocky"
ID_LIKE="rhel centos fedora"
VERSION_ID="8.10"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Rocky Linux 8.10 (Green Obsidian)"
ANSI_COLOR="0;32"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:rocky:rocky:8:GA"
HOME_URL="https://rockylinux.org/"
BUG_REPORT_URL="https://bugs.rockylinux.org/"
SUPPORT_END="2029-05-31"
ROCKY_SUPPORT_PRODUCT="Rocky-Linux-8"
ROCKY_SUPPORT_PRODUCT_VERSION="8.10"
REDHAT_SUPPORT_PRODUCT="Rocky Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="8.10"

I run it on a slurm server with 1 V100 GPU with CPU cores=40, the same as yours.
The command I used is the slurm file informarl.sh.

I believe informarl.sh is a deprecated script.  Thanks for your help.

@hsvgbkhgbv did it work for you? If yes, could you close this issue?
Thanks!

Following the installation instruction in https://github.com/Jaroan/Fair-MARL can address this issue.


Allow selected prop to override the selected state

Fixes issues when used with react-native-router-flux

Unfortunately this change broke example where initial selected was set (after fixing 'key' exception, i've got red selection not working), i will fix it

I can't fix it easily, maybe you could check...


cli: Add Blast Mainnet

released https://github.com/graphprotocol/graph-tooling/releases/tag/%40graphprotocol%2Fgraph-cli%400.68.5


[iOS] .evn not included in the Archive

I don't know if is the expected behavior,
but I noticed the .env the file is not included in the Archived version,
neither it's values are bundled on main.jsbundle
I understand the values might be scrambled, but I'm having a problem with the Apple Store version,
where the configuration is not available.
While in development mode is working perfectly, when building for release it doesn't work as expected.
Am I supposed to add the .env to XCode ? sorry if I'm missing something.
maybe related to #176?
Thanks.

Hey!
You don't have to add .env to Xcode. In the build process we're going to generate a copy of the environment already in Obj-C that the app uses.
What problem are you having with the apple store version, is the config not set or set to your dev values?

Notice the same behavior since I upgraded from 0.8 to 0.10. In Dev mode no issue but then when I am building for release, it does not work anymore (only on iOS, works on Android). Maybe a regression (0.8 -> 0.10)?
I downgraded to 0.8 and I am building a new release now so I'll tell you if it solves my problem.

I am also having this issue when deploying with Microsoft App Center, seems to work okay in release mode.

hey @kanso-michael so i found a workaround for app center that worked for me, I followed this https://github.com/luggit/react-native-config#ios-1
you need to create the pre build action for archive and create one scheme per environment. then in your build config in app center select the scheme you want to use. Hopefully that works!


mitigate EF docs ROPC

dotnet_EntityFramework_Docs

[ ]  Connection Strings
[ ] Connection strings and models
[ ] Scaffolding (Reverse Engineering)
[ ] Configuration File Settings
[ ] EF Core tools reference (Package Manager Console) - EF Core
[ ] EF Core tools reference (.NET CLI) - EF Core
[ ] Multi-tenancy - EF Core
[ ] Azure Cosmos DB Provider - EF Core
[ ] What's New in EF Core 5.0
[ ] Entity Framework 6 SQL Server provider based on Microsoft.Data.SqlClient
[ ] Visual Studio Releases - EF6
[ ] Applying Migrations - EF Core
[ ] Port from EF6 to EF Core - Detailed Cases
[ ] Using migrate.exe - EF6
[ ] Database Providers - EF Core
[ ] Porting from EF6 to EF Core - Porting a Code-Based Model - EF
[ ] Tools & Extensions - EF Core
[ ] DbContext Lifetime, Configuration, and Initialization - EF Core
[ ] Enum Support - EF Designer - EF6
[ ] Code First Conventions - EF6
[ ] Interceptors - EF Core
[ ] Database First - EF6
[ ] What's New in EF Core 6.0
[ ] Code First to an Existing Database - EF6
[ ] Advanced Performance Topics
[ ] Entity Framework Designer Keyboard Shortcuts - EF6
[ ] Breaking changes in EF Core 7.0 (EF7) - EF Core
[ ] Databinding with WinForms - EF6
[ ] Databinding with WPF - EF6
[ ] The Entity Framework 6 provider model - EF6
[ ] Overview of Entity Framework Core - EF Core
[ ] Upgrading from previous versions to EF Core 2 - EF Core
[ ] Get Started with Windows Forms - EF Core
[ ] Dependency resolution - EF6
[ ] Porting from EF6 to EF Core - Behavior changes
[ ] Porting from EF6 to EF Core - Porting an EDMX-Based Model - EF

For details see:
SFI info in Teams
See CS Dashboard per email thread.

Associated WorkItem - 295456

@Rick-Anderson (cc @tdykstra), checking through the SFI Dashboards own linked spreadsheet, absolutely all items are now set to "fixed".  Do you know who set all to fixed?  Is that the case that they are all fixed?
Looking through the items in that spreadsheet for repo ef docs I am seeing some that do not look fixed, but maybe I am not interpreting the issue correctly:
For example:
Password issue flagged for this topic:
https://github.com/dotnet/EntityFramework.Docs/blob/main//entity-framework/core/managing-schemas/migrations/applying.md
"
The following example applies migrations to a local SQL Server instance using the specified username and password.
.\efbundle.exe --connection 'Data Source=(local)\MSSQLSERVER;Initial Catalog=Blogging;User ID=myUsername;Password=myPassword'
"

Absolutely all items are now set to "fixed". Do you know who set all to fixed? Is that the case that they are all fixed?

I was under the wrong assumption that triaged meant fixed. So I'll change them to NA or "In Progress" as appropriate.

Password issue flagged for this topic:
https://github.com/dotnet/EntityFramework.Docs/blob/main//entity-framework/core/managing-schemas/migrations/applying.md
"
Create an issue  for that (in our repo and the EF repo) link each issue and assign that to Tom for October.

Fixed in https://github.com/dotnet/EntityFramework.Docs/pull/4849

@wadepickett

@Rick-Anderson (cc @tdykstra), checking through the SFI Dashboards own linked spreadsheet for the repo tab for EF docs: Absolutely all items are now set to "fixed".

They're all fixed now


Jwt cookie bis

This is the work I have done based on https://github.com/SimpleJWT/django-rest-framework-simplejwt/pull/157
I addressed all the comments in the pull requests, added some tests, rebased it to master, fixed the built, refactored the code and changed the approach to a "more secure" approach.
In my view, leaving the access and refresh token in the response body defies the purpose of putting the token in a httpOnly cookie.
The only way local storage can be compromised is if your application is already compromised with XSS, in which case it would be easy to call the server and retrieve both the access and refresh token.
Now, if an attacker was able to inject a script in your site, he would also be able to send a request to one of his server and could extract the access and refresh token. This is why if you don't use SameSite with values Strict or Lax, this approach has no real impact on security, since it would only raise the difficulty for attackers to steal the credentials.
Note that the SameSite setting is not available in older browsers like Internet Explorer which still account for around 6% of the global market.
So I would argue that storing the tokens in a httpOnly cookie is better, but only marginally better. In my case I decided to not support IE.
Here is a demo that uses this branch with Angular:
https://github.com/SimpleJWT/drf-SimpleJWT-Angular/pull/1
This pull request still needs doc. But has it a chance to be merged?

@loicgasser Sorry I didn't look at this earlier. Didn't notice it was changed back from [WIP]. I'll take a look at this and also ask David to also look. Not sure if it'll be settled to not use httpOnly cookies based on the referenced PR/issue.
Also updating master branch might be helpful (plus CI checks look fine besides the workflow one).

Yeah, I did rebase it when I first opened it. I can rebase again.

There still seems to be some merge conflicts @loicgasser And yeah, we fixed the initial problem, but when I was trying to fix it, I managed to duck something up so we're back at square one. But they should be working fine soon.

This is not a suggestion veiled as a question; I'm genuinely curious.
Is there a good reason not to make authentication via cookie its own authentication class? So, just as I can choose one or more authentication schemes in DRF through authentication_classes in a view, it could be that I want to choose whether to allow JWT cookie authentication or header authentication on a per-view basis.

Good question. To me, it's just to avoid duplicate code, so it's easier to maintain (especially with a couple of new features that I haven't had time to document).

allow JWT cookie authentication or header authentication on a per-view basis.

I think the code is taking away the need for you to check, so you just don't need to worry about context switching (between mobile Auth header and browser cookies).
Specifically: the if header: return None statement (can't remember the line) was when the Authentication header was not used. Now that there are cookies, if you're not using the Authentication header (it's mostly used for mobile) and instead use cookies (used for your JS frameworks), the if header does not immediately return None but instead checks your cookies.

Any reason why this still isn't merged? Happy to help and contribute as necessary, but I think this is a critical functionality to knowing the fact that most DRF APIs are used with SPAs like React, Vue, and this is one of the most recommended authentication method.

@AfrazHussain This is my preferred PR for JWT cookies. The issue at the moment is 1) resolving merge conflicts and 2) it's just huge. I've never taken the time to look thoroughly through everything. I'm skeptical of tests (I'm always skeptical of tests, so it has nothing specific to do with this PR). And finally, this just needs to be marked as super experimental.
Even though people have been doing cookie stuff with SimpleJWT for awhile, I don't want to encourage people to use cookies with JWTs for their SPAs. But I digress. I just want a very very safe PR for the users, not devs, of Django SPA projects.

Hi! Is there any way how we could support you in speeding up the reviewing process? I took me some while to find out what is the current state of the "Store JWT tokens in Cookies" discussion and finally I've landed here :)

hi this needs to be updated to master and pass tests with updates docs. another swipe through and we can mark it as experimental with some dangers in its use. then it can be merged

@Andrew-Chen-Wang SimpleJWT is currently implemented in a way which reflects the original concept of JWTs and goes against the best practice consistently recommended around the world. It pushes people to manage their tokens in the JS, which in turn requires them to store the tokens in long-term local storage.
I understand your skepticism, but there's a consideration of Opportunity Cost at play here, too. You have 100+ reactions collectively in tickets and PRs about this specific functional gap.
If you can point out specific tasks to complete in order for you to merge this PR, I am available to contribute some or all of them.
I currently use a middleware to work around this functional gap in SimpleJWT, and I'm sure that many others are using this or other forms of ugly wrappings to get this job done, to the detriment of maintainability. This patch is surely going to improve on that.


importing files containing topology_template unsupported

Importing a file containing a topology template seems to be unsupported by Puccini 0.18.0.
Following is the importing template:
tosca_definitions_version: tosca_simple_yaml_1_3
imports:
  - imported_template.yaml
topology_template:
  node_templates:
    node1:
      type: tosca:Compute

Following is the imported template:
tosca_definitions_version: tosca_simple_yaml_1_3
topology_template:
  node_templates:
    node2:
      type: tosca:Compute

A problem is signaled when compiling the importing template:
$ puccini-tosca compile importing_template.yaml
PROBLEMS (1)
  file:........./imported_template.yaml
    @3,1 topology_template: unsupported field
$

What you are experiencing here is exactly the same that happens with SOL001 (maybe you are playing with them).
I already discussed this with TAL and we are about to merge my changes (see PR#72) that provide a new quirk imports.ignore.topology_template.
If you are in a hurry and want to test, you may play with my fork at jpc4242/puccini (but my fork is intended to just prepare pull requests for Tal's main project; I encourage you to stay here)

I forgot to mention the original issue in case you want to look at it: it was #51

What you are experiencing here is exactly the same that happens with SOL001 (maybe you are playing with them).

Yes I am playing with them.

Then you will find useful the other quirk added in the same pull request

Thank you Tal.
Why is it resolved as a quirk?
I see nowhere in TOSCA spec that an imported file can not declare a topology template.
So the default behaviour should be to not produce a problem when an imported file declares a topology template.
Anyway.

Because this seems wrong to me -- there can be only one topology template. There is nothing in the grammar that could explain how two topology templates would be merged together. The spec simply doesn't specify what would happen in this case and in my interpretation, which always errs on the side of being strict, silently ignoring errors is not a good idea by default.
There seems to be agreement to make this interpretation explicit in TOSCA 2.0, where we are focusing much more on building profiles and generally defining how "import" works more clearly and strictly.


"Select all/ Unselect all" for custom icons

The functionality already exists, except for custom icons.

This would be so much helpful!

My workaround is using JS to select 1000 icons, it take some time done
var icons = document.querySelectorAll('.font-custom_icons .selector__glyph-inner:not(.checked)');
icons.forEach(e => e.click());

There's a hidden functionality: You can mark all items with holding down left mouse button.


Boots blocking xpboosted armor

I have xpboost on armor, if i have example xpboosted leggings and i have normal boots it wont give extra xp. But if i remove the boots it works, am i doing wrong or is it a bug?
Kakans-Pyjamasbyxor:
id: Golden_leggings
name: '&9Kakans Pyjamasbyxor'
lore:

'&2'
'&770% XP-Boost'
expBoost: 70.0
jobs:
Wop
levelFrom: 1
levelUntil: 200

Paper
git-Paper-333 (1.15.2)

d151fbec0f65e7800ed85d73513386ab548166f6


WASM builds no longer work?

Thanks for the library.
I started a fresh project with bevy 0.5, bevy_webgl 0.5 and (forked bevy_prototype_lyon, see my PR) based on bevy_webgl2_app_template.
Things are working great in native builds, but panicking in chrome and firefox when compiling shaders in web builds:
wasm.js:369 panicked at 'called `Result::unwrap()` on an `Err` value: "ERROR: 0:1: \'\n\' : invalid version directive\nERROR: 0:5: \'layout\' : syntax error\n\u{0}"', /Users/robparrett/.cargo/registry/src/github.com-1ecc6299db9ec823/bevy_webgl2-0.5.0/src/renderer/webgl2_render_resource_context.rs:77:81

I guess this is due to the new rendering pipeline that (became necessary for bevy 0.5 for some reason)?
I'd be happy to contribute something like a "web" feature that swaps in some opengl es compatible shaders, if that contribution would be welcome.

I can also reproduce this panic in my project bevy_antsim, a github pages hosted WASM build is available here.


prevent MMS message spam regex filtering bypass

Spam can arrive in the form of political ads in images.
intercept MMS messages with no text (only picture) from unknown numbers.
This is a feature request that would intercept MMS messages that contain only pictures from unknown numbers.  I define unknown numbers as either numbers detected as spam numbers from various databases, or from numbers not in your contacts list.
This will prevent bypass of regex filtering of spam text messages by senders simply putting ad text into an image and sending the image as spam.

What about blocking empty messages? ^$


The Following resource does not seem to exist in FlatTabControl

Bitmap updownImage = ((System.Drawing.Bitmap)(resources.GetObject("TabIcons.bmp")));
Bitmap closeImage = ((System.Drawing.Bitmap)(resources.GetObject("CloseIcon.bmp")));

Figured it out!


Add molecule tests for repositories_server and ssh_slave roles

Adding molecule test for remaining core roles:

repositories_server
ssh_slave roles

The following roles cannot be tested in containers, due to limits of docker (error: Device or resource busy)
These roles will be tested in a full virtualized environment with kitchen.

hosts_file
set_hostname

Dear @osmocl
Thanks a lot for this PR.
Merging.


Adds nodes stats API

Fixes #1262
Checklist

[ x] By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Thanks for adding another section into Nodes APIs. This is useful and much needed!
I have some comments:
1) Let's keep the common Nodes API parameters bookmarkable
Right now both the Nodes API request parameters timeout and node_filters are bookmarkable (or I would say directly reference-able). And both existing Nodes API sub-documentation pages (ie. Nodes hot threads, Nodes info) were making use of it.
For example the Nodes info, URL parameters refer to node_filters and timeout in the description column.
Similarly, the Nodes hot threads is referring to node_filters and timeout params in the description column as well.
And I think this is useful because common parameters can be documented in detail in the "parent" document (ie. Nodes API).
With the proposed change in this PR I can see that some of those links are now "broken". For example links that were pointing to ... nodes-apis/index/#node-filters can no longer point to specific filter because there is only ... nodes-apis/index/#path-parameters which node_filters is now part of.
2) Nodes API flat settings
I can see that Nodes API have a new flat_settings parameter in the doc.
I am not sure where it come from. I did not find it in the code and I had issues testing it manually.
I am not sure if I understand it correctly because no specific examples are given but my understanding would be that Path parameters are part of the URL (ie. <host>/_nodes?param1=foo&param2=false) and query parameters are part of the request body JSON (ie. curl -X POST <host>/_nodes -d {"param1":true, "param2":false}). Is that what it should stand for?
If yes then I am a bit confused about the fact that the timeout parameter is put into Query parameters section. IMO it is meant to be a parameter that is part of URL.
Here is an example:
export OSH='localhost:9200'

# The request timeout is set to 300ms which returns nothing
# because the internal threads sample interval to create this response is larger.
curl -X GET \
     -H "Content-Type: application/json" \
     ${OSH}/_nodes/hot_threads\?timeout=300ms

# This returns expected response.
curl -X GET \
     -H "Content-Type: application/json" \
     ${OSH}/_nodes/hot_threads\?timeout=1000ms

4) Others comments
In the Nodes info in the Response fields column: the field "modules." contains a dot in the end.
In Nodes info the SAMPLE RESPONSE WITHOUT FILTERING: IMO it is questionalbe what is the value of adding a large JSON like that into the documentation. This JSON will be different depending on user installation anyway. For example I frequently use the minimal distribution in which many modules and plugins are missing (like alerting or anomaly detection).
(Or maybe it would be useful to have collapse/expand button for such a large JSON/code examples.)
HTH,
Lukáš

Hi Lucas,
Thank you for your comments. We now have an API style guide, so I tried to adhere to it in this PR. Let me address your comments:

Since there are only a couple of parameters (node-filters and timeout), I think naming the section Path parameters is acceptable, because the user will still find the parameter very easily. But if you feel strongly, I can rename the section.
GET _nodes?flat_settings=true worked for me in the Dashboards console. This parameter is listed here - scroll to the "params" section at the very bottom.
Path vs. Query parameters - the distinction is explained in the API style guide. Basically, the path parameter is an endpoint extension that you specify in the URL (for example, _nodes/mynode - mynode is the path parameter), and the query parameter is anything that you specify after the question mark in the URL (for example, _nodes?timeout=30s - flat_settings is a query parameter). Whatever you put in the body is called "request fields".
Unfortunately, expand/collapse is not possible in the current site setup that we use. I agree it would be very valuable. I will remove the full response without filtering. I will also remove the dot - thanks for catching that.

@getsaurabh02 @Dharmesh - could you please review the indexing pressure section of the nodes-stats.md file (lines 956-968) for technical accuracy?

Hi @kolchfa-aws

GET _nodes?flat_settings=true worked for me in the Dashboards console. This parameter is listed here - scroll to the "params" section at the very bottom.

Ok, I think I see what is going on here. The flat_settings is applied only on the settings part of the response (which is about 3% of the whole JSON). I was incorrectly expecting that it should apply on the whole response body. My bad, I am sorry.
Maybe we shall make this more obvious in the description for folks like me? Like:

Filed
Data Type
Description

flat_settings
Boolean
Specifies whether to return settings part of the response in flat format.  Default is false.

Path vs. Query parameters - the distinction is explained in the API style guide.

This makes it clear to me now. I was really confused about the terminology.
BTW, the link from the API style guide to AWS style example https://alpha-docs-aws.amazon.com/awsstyleguide/latest/styleguide/examples.html does not work for me. Is it accessible from public internet?
The only nit-picking bit I would like to point out is that on the "parent" Nodes API page the <node-filters> token is broken like <node- \br filters> but I was not able to find a solution how fix it. There are some useful tips here: https://stackoverflow.com/questions/30308032/markdown-no-break-nobr but nothing worked for me because we are inside the <code> block... anyway.
LGTM,
Thanks for the work!
Lukáš

Hi @lukas-vlcek,
Thank you for following up! I have changed the flat_settings description. Thank you for pointing out the broken link in the API style guide - it is indeed not accessible from the outside.
Regarding <node-filters> I found a workaround - rather than trying not to break the text, I just specified a fixed percentage width for the columns, and it seems to work.
Thanks again for the review.


Transaction shows it was completed on 2/18/2018, but not showing up in my wallet!

Transaction d9c02ec250d039f8e7dd279ff867250e08042258fbe22f24840dd2beefdcc6c7
I sent 0.1051523 BTC from my Gemini wallet to my Throncoin wallet on 2/18/2018 and it hasn't shown up in my Throncoin wallet yet! It's not even showing pending! I included a screenshot of the transaction insight.bitpay.com and cut and paste the email I received say that the withdrawal was successful with 379 confirmations as of 2/20/2018
Can someone please help me with this?
thank you
Peace & Love
Namaste!

This is not the right place to ask this question. Insight is not a wallet.


Website styling

Description
This update introduces multiple improvements to the website’s styling, focusing on enhancing readability, interactivity, and the overall user experience across both light and dark modes. Key updates include:

Dark mode now uses white text for headings and content to make it visible against the dark background.

Light mode text colours were also fine-tuned for better contrast and consistency.

Buttons now have a smooth hover animation that includes a colour change from green to a darker green (palette from the Thoth), the text colour changes to gold on hover.

Additionally, a slight lift with subtle effect has been added to buttons on hover, creating a more dynamic and engaging user experience. The box shadow increases slightly, making the button appear raised.

Cards now have a subtle animation that adjusts the background colour and subtly lifts the card on hover. This includes smooth transitions in both light and dark modes.

In dark mode, the card background turns a darker shade on hover, and the text remains white to maintain contrast.

In light mode, cards change to a light grey background on hover while text colour shifts to white for better readability.

Both light and dark modes have gradient backgrounds applied to the main sections, giving the page a modern look while ensuring the content is readable.

The dark mode gradient consists of subtle blues and black for a sleek appearance, while the light mode gradient uses lighter blue shades to maintain a fresh and clean aesthetic.

Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as
expected)
[ ] Documentation (update or new)

How Has This Been Tested?
Changes were tested locally on the latest versions of Chrome, Safari, and Firefox. Button hover effects, card animations, and text readability were all validated across both light and dark modes.
The hover animations for buttons and cards were checked to ensure smooth transitions and consistent behaviour across browsers. The gradient backgrounds were also tested for proper rendering without distorting the readability of the text.
And there were no issues and warnings when building and running the code.
Testing Checklist

[x] Tested in latest Chrome
[x] Tested in latest Safari
[x] Tested in latest Firefox

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have requested a review from ... on the Pull Request

Closing due to being incomplete.


broken slider on specific map

Describe the bug
beatmap id: 707032 (yaseta - Bluenation [Grace] by Meg), broken slider on 2:32.976. Any replay works.
My replay, just for example: https://drive.google.com/file/d/1xUExlpFidP9XuCumq7BeRl2oW3KoZFKM/view?usp=drivesdk
Desktop (please complete the following information):

OS: Windows 10 Pro 22H2 build 19045.2604

video: https://drive.google.com/file/d/1FZ2e8H8E89ZWV_NVLlP5gUQoQU3DImqm/view?usp=drivesdk

Released and fixed


Error: object 'genome_version' not found

Hello Jan,
First of all thanks for upgrading the package with GRCh38.
I have uninstalled the old package and reinstalled the updated one. However when I am running the package I am getting an issue.
Here is my command-
> RNAseqCNV_wrapper(config = "/media/deepak/jay_doc/config.txt", metadata = "/media/deepak/jay_doc/META.csv", snv_format = "vcf", genome_version == "GRCh38")
[1] "Analysis initiated"
[1] "Normalization for sample: B31 completed"
[1] "Preparing file with snv information for: B31"
Reading in vcf file..
Extracting depth..
Extracting reference allele and alternative allele depths..
Needed information from vcf extracted
Finished reading vcf
[1] "Estimating chromosome arm CNV: B31"
Error: object 'genome_version' not found

Is there any mistake in the parameter? or should I use the shinny app?
Thanks,
Jay

Hi Jay,
you should try: "=" instead of "==" when inputting the parameter:
RNAseqCNV_wrapper(config = "/media/deepak/jay_doc/config.txt", metadata = "/media/deepak/jay_doc/META.csv", snv_format = "vcf", genome_version = "GRCh38")
Let me know if this solves your problems,
Best,
Jan


docs: New experimental UI for Mendable Search

This PR introduces a new Mendable UI tailored to a better search experience.
We're more closely integrating our traditional search with our AI generation.
With this change, you won't have to tab back and forth between the mendable bot and the keyword search. Both types of search are handled in the same bar. This should make the docs easier to navigate. while still letting users get code generations or AI-summarized answers if they so wish. Also, it should reduce the cost.
Would love to hear your feedback :)

Thanks, this is a good improvement


Nested Sampling

[ ] #361
[ ] Algorithm code
[ ] Tests
[ ] Argument configuration
[ ] gm/command.hpp

@betanalpha, want to move this to the wiki?

We might as well drop it until after we implement Adiabatic Monte Carlo.
On Nov 30, 2016, at 6:36 AM, Daniel Lee<EMAIL_ADDRESS>wrote:

@betanalpha, want to move this to the wiki?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I added a line to the longer term wiki page.


[material-ui][docs] Add first batch of v6 migration

[x] I have followed (at least) the PR section of the contributing guide.

Preview: https://deploy-preview-42242--material-ui.netlify.app/material-ui/migration/migration-v5/
Out of scope

Pigment CSS migration (likely to be added after beta release)

Hey @siriwatknp! I merged https://github.com/mui/material-ui/pull/42194. I'll complete the deprecations section as soon as possible.

Decide on the minimum React & TypeScript version

On React, we decided on React 17

@siriwatknp I updated the PR after some breaking changes were added to the migration guide in other PRs. I haven't forgotten about adding the components and componentsProps to the deprecation section 😅 I just haven't had time yet, but I'll get to it.

are we not mentioning React 19 as a v6 highlight?

Not ready yet so I think we can add it when it is

@danilo-leal @samuelsycamore I think this is ready as the first batch of the migration guide.

@samuelsycamore I think we can review the whole migration doc structure and writing before the stable release. This way, we avoid spamming you with notifications and can review it when all content is ready.


TypeScript: Zone#create should have required parameter of type CreateZoneRequest

Currently the TypeScript type of Zone#create is inherited from ServiceObject#create. Effectively the first argument is optional and if present can have any shape. (TypeScript doesn't do the excess property check on assignments to an empty object type.) That doesn't jibe with either the docs or the runtime checks. Instead, the first parameter of Zone#create should be required of type CreateZoneRequest. (Maybe without the "name" property?).

I'm working on this now. Feel free to assign if that's useful.

Actually it's not obvious to me how to proceed here. Zone's create method is inherited from ServiceObject, which knows nothing about dnsNames. I tried to add some appropriate create overloads to the Zone class definition, but encountered Property 'create' in type 'Zone' is not assignable to the same property in base type 'ServiceObject'.

The way to call our child.create() is with the arguments the parent.createChild() method expects, except the first argument, which is always the name.
const zone = dns.zone('...')
zone.create(config, callback)
// ===
dns.createZone('...', config, callback)

The create behavior is defined in ServiceObject.prototype.create, which calls config.createMethod:
https://github.com/googleapis/nodejs-dns/blob/d07673159609f2240394cf2a75a734f9ff546b08/src/zone.ts#L345
A condensed version of all of this functionality:
class ServiceObject {
  constructor(cfg) {
    this.id = cfg.id
    this.createMethod = cfg.createMethod
  }

  create() {
    const args = [this.id]
    // figure out any additional arguments to provide to
    // the create method, i.e. args.push(options)
    this.createMethod.apply(null, args)
  }
}

class DNS extends Service {
  createZone(name, config, callback) {
    config.name = name
    this.request(...)
  }
}

class Zone extends ServiceObject {
  constructor(parentInstance) {
    super({
      methods: {
        create: true
      },
      createMethod: parentInstance.createZone.bind(parentInstance)
    })
  }
}

@stephenplusplus TIL about embedded code snippits. NEAT! The JavaScripty part of all this is working just fine. It's the types that aren't correct. Here is a simplification that illustrates the issue:
class Service {}

interface CreateZoneOptions {
  dnsName: string;
}

class DNS extends Service {
  createZone(options: CreateZoneOptions) {
    if (typeof options === 'undefined') {
      // This code should never be reached by a TypeScript user.
      // Said another way, the type of "options" here is "never".
      // But let's be kind to our JavaScript users and fail fast.
      throw new Error('Expected argument "options"');
    }
    const { dnsName } = options;
    if (typeof dnsName === 'undefined') {
      // This code should never be reached by a TypeScript user.
      // Said another way, the type of "dnsName" here is "never".
      // But let's be kind to our JavaScript users and fail fast.
      throw new Error('Expected argument "options" to include "dnsName"');
    }
    // Do request to /managedZones and so forth ...
  }
}

interface ServiceObjectOptions {
  createMethod: Function;
}

class ServiceObject {
  createMethod: Function;
  constructor(opts: ServiceObjectOptions) {
    this.createMethod = opts.createMethod;
  }

  create(opts?: any) {
    this.createMethod.apply(null, opts);
  }
}

class Zone extends ServiceObject {
  constructor(dns: DNS) {
    super({ createMethod: dns.createZone.bind(dns) });
  }
}

const dns = new DNS();
const zone = new Zone(dns);

// For "dns", everything works as expected.

// Compiler error "Expected 1 arguments, but got 0."
dns.createZone();

// Compiler error: "'dnsLameTypo' does not exist in type 'CreateZoneOptions'."
dns.createZone({ dnsLameTypo: 'carnesen.com' });

// OK!
dns.createZone({ dnsName: 'carnesen.com' });

// For "zone", the typings are not sufficiently strict.

// The following is NOT currently a compiler error. It should be.
// Instead we encounter a runtime error 'Expected argument "options"'
zone.create();

// The following is NOT currently a compiler error. It should be.
// Instead we encounter a runtime error 'Expected argument "options" to include "dnsName"'
zone.create({ dnsLameTypo: 'carnesen.com' });

// OK!
zone.create({ dnsName: 'carnesen.com'});

To continue that example, here is one way we could approach it using TypeScript generics:
interface CreateMethod<T> {
  (opts: T): void;
}

interface BetterServiceObjectOptions<T> {
  createMethod: CreateMethod<T>;
}

class BetterServiceObject<T> {
  private createMethod: CreateMethod<T>;
  constructor(opts: BetterServiceObjectOptions<T>) {
    this.createMethod = opts.createMethod;
  }
  create(opts: T) {
    this.createMethod(opts);
  }
}

class BetterZone extends BetterServiceObject<CreateZoneOptions> {
  constructor(dns: DNS) {
    super({ createMethod: dns.createZone.bind(dns) });
  }
}

const betterZone = new BetterZone(dns);

// Compiler error "Expected 1 arguments, but got 0."
betterZone.create();

// Compiler error "Property 'dnsName' is missing in type '{}'."
betterZone.create({});

// Compiler error "'dnsLameTypo' does not exist in type 'CreateZoneOptions'"
betterZone.create({ dnsLameTypo: 'carnesen.com' });

// OK!
betterZone.create({ dnsName: 'carnesen.com'});

@carnesen I know it's been quite some time since you filed this bug, but it should now be addressed in<EMAIL_ADDRESS>mind taking this for a spin and letting us know if it addresses your issues?

@bcoe Indeed zone.create now expects a config object of type CreateZoneRequest like dns.createZone does! See also though https://github.com/googleapis/nodejs-dns/issues/309


[Watson][b506fadb-9ded-7fda-86e4-531e91197fce]CLR_EXCEPTION_80070002_DirectWriteForwarder.dll! MS.Internal.Text.TextInterface.FontFace.GetDesignGlyphMetrics

Generated issue from Watson
Watson Link:  https://watsonportal.microsoft.com/Failure?FailureSearchText=b506fadb-9ded-7fda-86e4-531e91197fce
ADO Link: https://microsoft.visualstudio.com/DefaultCollection/OS/_workitems#id=29139987&triage=true&fullScreen=true&_a=edit
Process: powerlauncher.exe,
Module: directwriteforwarder.dll v4.800.120.31503

Setting to priority 1 based on hit count:

6
1.10 %

No hits in the past 30 days.


ci: add build env to release job

The release of containerd-shim-wasm crate failed at the cargo publish step saying that protoc was not found. Thus I am adding build env to the release job.

LGTM
Maybe as a follow up after this release we can run the release CI up to the Publishing steps so we can catch issues earlier?

LGTM
Maybe as a follow up after this release we can run the release CI up to the Publishing steps so we can catch issues earlier?

There is a nice flag for cargo publish --dry-run to run all the checks without uploading to crates.io. Is this what you meant?

yes, if we can run that semi regularly then we could catch issues before release time?

yes, if we can run that semi regularly then we could catch issues before release time?

Maybe we should refactor the pipeline to an reusable action and run it at our build (with --dry-run flag on)

@jsturtevant just realized that --dry-run won't be able to catch errors like https://github.com/containerd/runwasi/actions/runs/6715767237/job/18251185616#step:7:794

It can still catch other issues, I think it's still worth adding.


Update docs: include Gentoo source build

Mention the dev-util/rust-analyzer package for building from source.

Thanks!
bors r+


Practice 7 - camera_traffic_light_detector - code comments

comments:

You don't want to do this. It will return from callback if no stop lines on path, but we still want that empty roi images and traffic light status is published.
https://github.com/jaak-peterson/autoware_mini_practice/blob/1e0fda287e9c2caf016b304900605bc52b7a3951/practice_7/nodes/detection/tfl_camera/camera_traffic_light_detector.py#L131-L132

If there are rois then publish_roi_images is called twice!
https://github.com/jaak-peterson/autoware_mini_practice/blob/1e0fda287e9c2caf016b304900605bc52b7a3951/practice_7/nodes/detection/tfl_camera/camera_traffic_light_detector.py#L168-L171

OK, but just one last thing.

Instead of completely removing I would suggest the following:

currently you always try to get the transform and call calculate_roi_coordinates
the condition you removed could have been written if there are stoplines on the path (if len(stoplines_on_path) > 0) only then try to get the transform and do all the rest of the things...

OK, it is not published twice any more. In that sense it is fixed, but in my opinion it would look nicer if you would have only these 2 lines in the end of callback

self.publish_roi_images(image, rois, classes, scores, camera_image_msg.header.stamp)
self.tfl_status_pub.publish(tfl_status)

and not that:
https://github.com/jaak-peterson/autoware_mini_practice/blob/48796e4e9b298f272830c8874ab9e43944d26551/practice_7/nodes/detection/tfl_camera/camera_traffic_light_detector.py#L165-L169

If you would create rois, classes, scores somewhere at the beginning of the callback as empty lists
then if you will have that if (if len(stoplines_on_path) > 0)  from point 1, then inside there you will modify the rois, classes and scores
and then you can have only one line for publishing roi images at the end of the callback outside any if's
self.publish_roi_images(image, rois, classes, scores, camera_image_msg.header.stamp)

The previous comment would make it more efficient, but the code works, so I am closing the issue.


Only build PrometheusSink on Go >=1.3.

This fixes https://github.com/prometheus/client_golang/issues/102

/cc @armon @dachary

cute :-) :+1:

Will this build only on Go1.3 or on anything >= 1.3?

I'm also tempted to move this to a sub-package to avoid breaking builds.

This will build on anything >=1.3. See http://golang.org/pkg/go/build/:
- ...
- "go1.3", from Go version 1.3 onward
- ...

Using sub-packages would work too, but this already removes the entire Prometheus file from anyone's build when they are using Go <1.3.

Cool, merging for now. We can deal with sub-packages later.


Test correct flag for using external boost

When including the cmake file from a parent cmake project, Boost_FOUND may
be set even though we don't want to use an external boost (for example,
because the version of boost is not new enough to support the test code)
Signed-off-by: Richard Chapman<EMAIL_ADDRESS>

Thanks, good catch.


unable to install Ryven because of PySide2

ERROR: Could not find a version that satisfies the requirement PySide2 (from ryven) (from versions: none)
ERROR: No matching distribution found for PySide2
I installed PySide6 but this doesn't solve the issue
Thanks

I am also having this issue now.

Probably because you're using Python 3.11 and PySide2 requires Python version less than 3.11:
https://pypi.org/project/PySide2/

i got around this by:
pip3 install 'pyside6<6.7'
then
ryven --q=pyside6


Unclear how to validate an optional field

What's the proper way to validate an optional field?
For example, I have a field called cvv that's optional, but if filled in should be a min length of 3 with a max of 4 chars

All fields are optional unless you use the presence spec.
You can also use a conditional constraint if you need CVV based on another attribute: http://validatejs.org/#constraints (see the example, creditCardZip to be specific)

@theogravity Look here: https://github.com/ansman/validate.js/issues/99#issuecomment-239890891


[Bug]: Fullscreen windows do not cover the entire screen when panel bar exists

Before you make the issue, confirm that

[X] You are running the master build from GitHub actions
[X] You have read the FAQ and the usage instructions
[X] You have searched pull requests and issues and have found none similar to your issue
[X] This problem comes from a failure in the tiling system and not a missing feature

Describe the bug
When using a fullscreen application (eg. a Steam game), the window will not extend to cover the whole screen if a panel bar exists on a same screen.
This problem exists only on the Wayland session, and not the X11 one (I have tested), and only when Polonium is active on Wayland.
Certain fullscreen apps (eg. Firefox, Spotify) seem to use a different type of way of achieving fullscreen (probably not a true fullscreen).
To reproduce
On KDE Wayland 6.0.2, Polonium 1.0b1, Arch Linux, start a Wayland session, and try to play / fullscreen any Steam game, while having a panel bar on your monitor. The window should never extend over the whole screen. It might rarely, or try to (jumps to fullscreen and back), but in the majority of cases the window does not extend the whole way.
Expected behavior
App is completely fullscreen, as per the X11 session for example. (With the same versions of all programs.)
Relevant log output
Mar 22 19:13:15 linux kwin_wayland[32067]: qml: Polonium DBG: Window steam_app_2357570 hooked into script
Mar 22 19:13:15 linux kwin_wayland[32067]: qml: Polonium DBG: Not tiling window steam_app_2357570
Mar 22 19:13:15 linux kwin_wayland[32067]: qml: Polonium DBG: Minimized on client steam_app_2357570 set to false
Mar 22 19:13:15 linux kwin_wayland[32067]: qml: Polonium DBG: Adding client steam_app_2357570 to desktops {"desktop":"91426cb6-dc93-4fe8-95dc-c894a26d958c","activity":"d3d97372-e012-41fd-8fa6-120c43f5becf","output":"DP-3"}
Mar 22 19:13:15 linux kwin_wayland[32067]: qml: Polonium DBG: Rebuilding layout for desktops {"desktop":"91426cb6-dc93-4fe8-95dc-c894a26d958c","activity":"d3d97372-e012-41fd-8fa6-120c43f5becf","output":"DP-3"}
Mar 22 19:13:15 linux kwin_wayland[32067]: qml: Polonium DBG: Fullscreen on client steam_app_2357570 set to true
Mar 22 19:13:15 linux kwin_wayland[32067]: qml: Polonium DBG: Removing client steam_app_2357570 from desktops {"desktop":"91426cb6-dc93-4fe8-95dc-c894a26d958c","activity":"d3d97372-e012-41fd-8fa6-120c43f5becf","output":"DP-3"}
Mar 22 19:13:15 linux kwin_wayland[32067]: qml: Polonium DBG: Rebuilding layout for desktops {"desktop":"91426cb6-dc93-4fe8-95dc-c894a26d958c","activity":"d3d97372-e012-41fd-8fa6-120c43f5becf","output":"DP-3"}
Mar 22 19:13:15 linux kwin_wayland[32067]: qml: Polonium DBG: Fullscreen on client steam_app_2357570 set to false
Mar 22 19:13:15 linux kwin_wayland[32067]: qml: Polonium DBG: Adding client steam_app_2357570 to desktops {"desktop":"91426cb6-dc93-4fe8-95dc-c894a26d958c","activity":"d3d97372-e012-41fd-8fa6-120c43f5becf","output":"DP-3"}
Mar 22 19:13:15 linux kwin_wayland[32067]: qml: Polonium DBG: Rebuilding layout for desktops {"desktop":"91426cb6-dc93-4fe8-95dc-c894a26d958c","activity":"d3d97372-e012-41fd-8fa6-120c43f5becf","output":"DP-3"}
Mar 22 19:13:15 linux kwin_wayland[32067]: qml: Polonium DBG: Fullscreen on client steam_app_2357570 set to true
Mar 22 19:13:15 linux kwin_wayland[32067]: qml: Polonium DBG: Removing client steam_app_2357570 from desktops {"desktop":"91426cb6-dc93-4fe8-95dc-c894a26d958c","activity":"d3d97372-e012-41fd-8fa6-120c43f5becf","output":"DP-3"}
Mar 22 19:13:15 linux kwin_wayland[32067]: qml: Polonium DBG: Rebuilding layout for desktops {"desktop":"91426cb6-dc93-4fe8-95dc-c894a26d958c","activity":"d3d97372-e012-41fd-8fa6-120c43f5becf","output":"DP-3"}
Mar 22 19:13:20 linux kwin_wayland[32067]: qml: Polonium DBG: Rebuilding layout for desktops {"desktop":"35e8c006-b90e-40cd-b895-b014362dbdda","activity":"d3d97372-e012-41fd-8fa6-120c43f5becf","output":"DP-3"}

Screenshots and videos
Overwatch (or any other game) not fully extending, leaving the bar visible (and small borders visible across all sides of monitor). The window is effectively not fullscreen.

Additional context
No response

Nevermind, I wasn't using the nightly build, rather the stable one. The issue seems to be fixed in the newest versions, sorry about that.

Nevermind, this is actually still a problem.

I can confirm the same issue, also running nightly although I believe it was the same with v1.0b1 (I will test that). In my case I noticed when hitting F11 to make Firefox full screen, or when making a video in the browser full screen (the video controls end up behind my taskbar, since I have it on the bottom)

It's strange, I have a hybrid laptop with a mux switch and I only encounter this issue on the intel gpu, not the Nvidia one. The fact that it doesn't happen on Nvidia is probably a Nvidia problem and not an Intel problem, but I'll keep looking into this.

Try the latest commit and see if anything has changed

fixed for me!


[SPIKE] App.js cannot pass token to ejs

Token is not shown, it becomes [object Object]

Solved: JSON.stringify()


version comatability of elastic dump

Hello Team,
Can I please know if elastic dump's backup/restore is version compatible w.r.t elastic search ?
Example: Does bumping up and downgrading the Elastic search has any impact on the data while using elastic dump ?
Please advise.

Raw data no.
But mappings/templates/settings might be different. but this is mainly an ES issue which can be rectified easily.

Sure, I am looking for backup/restore of data for now.
Thank you very much for your quick response.


Can't get results

Hello when I run the following code, I get the following error.
        $push = new Sly\NotificationPusher\Model\Push($adapter, $devices, $message);

        $pushManager->add($push);
        $pushManager->push();

        foreach($push->getResponses() as $token => $response) {
            var_dump($token);
            var_dump($response);
        }

Call to undefined method Sly\NotificationPusher\Model\Push::getResponses()

anyone try to sort this issue?

It looks like an autoloading configuration issue. Also, please be sure to use the latest version.


Initial support for some Prometheus Metrics

Two metrics currently implemented:

calls of the "Sender", seen here:

calls to the "Device registration"

NOTE: The URL of the endpoint is HOST:PORT/ag-push/rest/prometheus/metrics
So, calling curl http://<IP_ADDRESS>:9191/ag-push/rest/prometheus/metrics will give you something like this:
# HELP device_register_requests_total Total number of Device register requests.
# TYPE device_register_requests_total counter
device_register_requests_total 2.0
# HELP push_requests_total Total number of push requests.
# TYPE push_requests_total counter
push_requests_total 1.0

@philbrookes can the prometheus auto-discovery work with the url /ag-push/rest/prometheus/metrics?

that needs to be configured, for the ups job   - we can not have vanilla
URLs - the best we can get here is /ag-push/rest/metrics  (but we have
already some other metrics, hence that URL)
On Mon, Dec 11, 2017 at 4:22 PM, David Martin<EMAIL_ADDRESS>wrote:

@philbrookes https://github.com/philbrookes can the prometheus
auto-discovery work with the url /ag-push/rest/prometheus/metrics?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aerogear/aerogear-unifiedpush-server/pull/949#issuecomment-350755412,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJnzuN-yQ4Xm85HWq99y3sROJar_v6kks5s_UiggaJpZM4Q9XLr
.

--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf

EDIT: @philbrookes is there a way to make prometheus look for some annotation on a service to discover what the metrics endpoint is for that service?

@david-martin @philbrookes perhaps, in the APB for the UPS, we can annotate this, and define/hint the 'special' URL ?

@david-martin It won't as it is currently configured, a new block would need to be added to the prometheus configuration configmap, like this block: https://github.com/feedhenry/prometheus-apb/blob/master/roles/provision-prometheus-apb/templates/prometheus-config-map.yml.j2#L41-L67
But with a different value to identify it here: https://github.com/feedhenry/prometheus-apb/blob/master/roles/provision-prometheus-apb/templates/prometheus-config-map.yml.j2#L51
And a new end-point value here: https://github.com/feedhenry/prometheus-apb/blob/master/roles/provision-prometheus-apb/templates/prometheus-config-map.yml.j2#L48

@matzew hmm, maybe we can, it's hinted at here! https://github.com/prometheus/prometheus/blob/master/documentation/examples/prometheus-kubernetes.yml#L85

maybe changing the format of the prometheus annotation to:
org.feedhenry.mcp/ssl_metric_endpoint: /path/to/metrics

or
org.feedhenry.mcp/plain_metric_endpoint: /path/to/metrics

WDYT?

@philbrookes I like this idea of the changed annotaiton

@philbrookes +1.
I'd even go as far as saying the annotation should be something like
io.prometheus/plain_metric_endpoint: /path/to/metrics

It's a bit off topic here ;-)
for UPS metrics to function, of course, I had to change the metrics_path in
the prometheus.yml file
About the annotation namespace - let's chat via mail thread ? :)
On Mon, Dec 11, 2017 at 5:49 PM, David Martin<EMAIL_ADDRESS>wrote:

@philbrookes https://github.com/philbrookes +1.
I'd even go as far as saying the annotation should be something like
io.prometheus/plain_metric_endpoint: /path/to/metrics
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aerogear/aerogear-unifiedpush-server/pull/949#issuecomment-350783993,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJnzs3i5Az7UpiSR5qd8YgiLw3Gz1fLks5s_V0xgaJpZM4Q9XLr
.

--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf


Works on iOS safari in the browser but not as a PWA

Unless I'm doing something wrong I cannot get it to run in the standalone PWA version.

The methods to keep the page from scrolling do not seems to work in the PWA. I'm up against the limitations of the PWA at the moment. [I'll note that fixed position elements work different on safari iOS than chromium.] [Also when the page pulls down on mobile the visible height compute is still the same, even if you pull half way down.] Must be outside of the DOM.

The methods to keep the page from scrolling do not seems to work in the PWA. I'm up against the limitations of the PWA at the moment. [I'll note that fixed position elements work different on safari iOS than chromium.] [Also when the page pulls down on mobile the visible height compute is still the same, even if you pull half way down.] Must be outside of the DOM.


PathParam: Missing functionality

Following problems were identified:
Not throw IllegalArgumentException when wrong path params (now throw Runtime exception)

Can’t pass INT type to value path param (now in this case throw Runtime Exception)

Can’t pass nonStandardChars with path param(for example \\$£@\"){¤$ , John: å)

Can’t pass unnamed path param (for example in restassured get("http://www.google.se/search?q={query}&hl=en", "query"))

Failed when pass space in value(example - requestPathParams(new Object[][]{{"firstName", "John"}, {"lastName", " "}}

Expected:
Check if every bullet is actual and cannot be resolved with existed framework API
Find solution for every identified problem remaining in list
Discuss proposed solution w/Team if someone from review team agrees, create a dedicated task for implementation and link it to the current issue (that include implementation of the proposed solution, test covering and documentation creation)

now in log url  view in this case http://localhost:8080/{firstName}/{lastName},

Demo has been done.


ERROR: Could not build wheels for fused-dense-lib, which is required to install pyproject.toml-based projects

When I install and compile flash-attention from the source code in the dockerfile, I implemented the following command:
cd flash-attention/csrc/fused_dense_lib && /opt/conda/bin/pip install .
And I met the problem:
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
2128.6 Processing /InternLM/flash-attention/csrc/fused_dense_lib
2128.6   Preparing metadata (setup.py): started
2133.5   Preparing metadata (setup.py): finished with status 'done'
2133.5 Building wheels for collected packages: fused-dense-lib
2133.5   Building wheel for fused-dense-lib (setup.py): started
2138.5   Building wheel for fused-dense-lib (setup.py): finished with status 'error'
2138.5   error: subprocess-exited-with-error
2138.5
2138.5   × python setup.py bdist_wheel did not run successfully.
2138.5   │ exit code: 1
2138.5   ╰─> [61 lines of output]
2138.5       No CUDA runtime is found, using CUDA_HOME='/usr/local/cuda'
2138.5       running bdist_wheel
2138.5       running build
2138.5       running build_ext
2138.5       building 'fused_dense_lib' extension
2138.5       creating /InternLM/flash-attention/csrc/fused_dense_lib/build
2138.5       creating /InternLM/flash-attention/csrc/fused_dense_lib/build/temp.linux-x86_64-cpython-310
2138.5       Traceback (most recent call last):
2138.5         File "<string>", line 2, in <module>
2138.5         File "<pip-setuptools-caller>", line 34, in <module>
2138.5         File "/InternLM/flash-attention/csrc/fused_dense_lib/setup.py", line 26, in <module>
2138.5           setup(
2138.5         File "/opt/conda/lib/python3.10/site-packages/setuptools/__init__.py", line 107, in setup
2138.5           return distutils.core.setup(**attrs)
2138.5         File "/opt/conda/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 185, in setup
2138.5           return run_commands(dist)
2138.5         File "/opt/conda/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 201, in run_commands
2138.5           dist.run_commands()
2138.5         File "/opt/conda/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 969, in run_commands
2138.5           self.run_command(cmd)
2138.5         File "/opt/conda/lib/python3.10/site-packages/setuptools/dist.py", line 1234, in run_command
2138.5           super().run_command(command)
2138.5         File "/opt/conda/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
2138.5           cmd_obj.run()
2138.5         File "/opt/conda/lib/python3.10/site-packages/wheel/bdist_wheel.py", line 325, in run
2138.5           self.run_command("build")
2138.5         File "/opt/conda/lib/python3.10/site-packages/setuptools/_distutils/cmd.py", line 318, in run_command
2138.5           self.distribution.run_command(command)
2138.5         File "/opt/conda/lib/python3.10/site-packages/setuptools/dist.py", line 1234, in run_command
2138.5           super().run_command(command)
2138.5         File "/opt/conda/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
2138.5           cmd_obj.run()
2138.5         File "/opt/conda/lib/python3.10/site-packages/setuptools/_distutils/command/build.py", line 131, in run
2138.5           self.run_command(cmd_name)
2138.5         File "/opt/conda/lib/python3.10/site-packages/setuptools/_distutils/cmd.py", line 318, in run_command
2138.5           self.distribution.run_command(command)
2138.5         File "/opt/conda/lib/python3.10/site-packages/setuptools/dist.py", line 1234, in run_command
2138.5           super().run_command(command)
2138.5         File "/opt/conda/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
2138.5           cmd_obj.run()
2138.5         File "/opt/conda/lib/python3.10/site-packages/setuptools/command/build_ext.py", line 84, in run
2138.5           _build_ext.run(self)
2138.5         File "/opt/conda/lib/python3.10/site-packages/setuptools/_distutils/command/build_ext.py", line 345, in run
2138.5           self.build_extensions()
2138.5         File "/opt/conda/lib/python3.10/site-packages/torch/utils/cpp_extension.py", line 843, in build_extensions
2138.5           build_ext.build_extensions(self)
2138.5         File "/opt/conda/lib/python3.10/site-packages/setuptools/_distutils/command/build_ext.py", line 467, in build_extensions
2138.5           self._build_extensions_serial()
2138.5         File "/opt/conda/lib/python3.10/site-packages/setuptools/_distutils/command/build_ext.py", line 493, in _build_extensions_serial
2138.5           self.build_extension(ext)
2138.5         File "/opt/conda/lib/python3.10/site-packages/setuptools/command/build_ext.py", line 246, in build_extension
2138.5           _build_ext.build_extension(self, ext)
2138.5         File "/opt/conda/lib/python3.10/site-packages/setuptools/_distutils/command/build_ext.py", line 548, in build_extension
2138.5           objects = self.compiler.compile(
2138.5         File "/opt/conda/lib/python3.10/site-packages/torch/utils/cpp_extension.py", line 649, in unix_wrap_ninja_compile
2138.5           cuda_post_cflags = unix_cuda_flags(cuda_post_cflags)
2138.5         File "/opt/conda/lib/python3.10/site-packages/torch/utils/cpp_extension.py", line 548, in unix_cuda_flags
2138.5           cflags + _get_cuda_arch_flags(cflags))
2138.5         File "/opt/conda/lib/python3.10/site-packages/torch/utils/cpp_extension.py", line 1780, in _get_cuda_arch_flags
2138.5           arch_list[-1] += '+PTX'
2138.5       IndexError: list index out of range
2138.5       [end of output]
2138.5
2138.5   note: This error originates from a subprocess, and is likely not a problem with pip.
2138.5   ERROR: Failed building wheel for fused-dense-lib
2138.5   Running setup.py clean for fused-dense-lib
2143.5 Failed to build fused-dense-lib
2143.5 ERROR: Could not build wheels for fused-dense-lib, which is required to install pyproject.toml-based projects

Finally, I solved this problem successfully by adding the following line in front of flash-attention installation in the dockerfile:
'''
ARG TORCH_CUDA_ARCH_LIST="3.7;5.0;6.0;7.0;7.5;8.0;8.6+PTX"
'''
Refer to:
https://github.com/Dao-AILab/flash-attention/issues/344#issuecomment-1641701568
https://github.com/pytorch/extension-cpp/issues/71


feat(name): rename project into bright-cli

BREAKING CHANGE: cli tool renamed to bright-cli
closes #378

@aborovsky There are a few additional notes:

What does the "name" scope refer to, and what are its boundaries?

-feat(name): rename project into bright-cli
+feat: rename project into `bright-cli`

The breaking changes in the footer must include information on migrating to the new major version.

-BREAKING CHANGE: cli tool renamed to `bright-cli`
+BREAKING CHANGE:  The command-line interface previously known as `nexploit-cli` is no longer supported. It has been renamed to `bright-cli`.
+
+**Before**
+```
+$ nexploit-cli -h
+```
+**After**
+```
+$ bright-cli -h
+```

closes #378


Revert to 2.2-SNAPSHOT to be compatible with release versions

retest this please

retest this please

Same failure as #1353...

Weird.

retest this please

retest this please

retest this please

[merge]


Flag for separation vim and neovim specific plugins

Hey. I have idea about new feature for vim-plug. Many people sharing their configs between vim and neovim. But unfortunately some of plugins works with neovim or with vim only. How about flag which will prevent loading plugin if user start editor which not support it?
It would looks something like this:
Plug 'author/repo' [n]; - it should signal to load it only with neovim and ignore with vim.
Or you can create better syntax. It's just example.
What do you think about it?

It is possible to do this wrapping
if has('nvim')
  Plug 'neovim-plugin'
endif

You might want to check out https://github.com/junegunn/vim-plug/wiki/tips#conditional-activation


500 Error at launch (KeyError: 'terminals_available' in self.settings)

Also reported on discourse.
macOS 13.5, Python 3.11.4 (homebrew)
With the recent move to notebook 7, I have been having issues with both notebook (documented here and here) and nbclassic.
For the latter, I am seeing a traceback, followed by a 500 error in the browser:
[E 2023-07-26 08:40:30.645 ServerApp] Uncaught exception GET /nbclassic/tree?token=e2a5e04ac6410a588e1132bac555b4f1fce1c781e1c9b4e0 (::1)
    HTTPServerRequest(protocol='http', host='localhost:8888', method='GET', uri='/nbclassic/tree?token=e2a5e04ac6410a588e1132bac555b4f1fce1c781e1c9b4e0', version='HTTP/1.1', remote_ip='::1')
    Traceback (most recent call last):
      File "/opt/homebrew/lib/python3.11/site-packages/tornado/web.py", line 1786, in _execute
        result = await result
                 ^^^^^^^^^^^^
      File "/opt/homebrew/lib/python3.11/site-packages/tornado/gen.py", line 786, in run
        yielded = self.gen.send(value)
                  ^^^^^^^^^^^^^^^^^^^^
      File "/opt/homebrew/lib/python3.11/site-packages/nbclassic/tree/handlers.py", line 69, in get
        terminals_available=self.settings['terminals_available'],
                            ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^
    KeyError: 'terminals_available'

If I change "/opt/homebrew/lib/python3.11/site-packages/nbclassic/tree/handlers.py", line 69 from
terminals_available=self.settings['terminals_available'],

to
terminals_available=self.settings.get('terminals_available', False),

(as is done in notebook/app.py) it works (no errors, no 500), but I assume this shouldn't be necessary?
I assume it is a local config issue somehow, but in fact even if I get rid of all of the current directories listed with jupyter --paths it does not seem to help.
(There seem to be other interface problems as documented in my jupyter/notebook issue. Also, if relevant: Python 3.11 is installed by homebrew, but all packages, including jupyter, notebook, etc. are installed with pip.)
Any ideas?

Partial fix:
JUPYTER_PATH=/opt/homebrew/share/jupyter jupyter nbclassic

seems to fix it.
This appears to be a config problem in some interaction between how homebrew and jupyter set paths?
(As such, I suspect that this is closely related to https://github.com/jupyter/notebook/issues/6974)

cc @echarles @RRosio @ericsnekbytes for awareness

See also https://github.com/jupyterlab/jupyterlab/issues/14890

jupyter_server_terminals's latest update added the following to respect terminal setting:
        """Initialize settings."""
        if not self.serverapp.terminals_enabled:
            return
        self.initialize_configurables()
        self.settings.update(
            {"terminals_available": True, "terminal_manager": self.terminal_manager}
        )```
So if it is set to false then it is guaranteed to fail the nbclassic/tree.
the latest code will fix this. Will we have a release soon?


MAINT: forward port 1.7.3 relnotes.

Forward port SciPy 1.7.3 release notes after the release this morning.

Thanks Tyler. And thanks for pushing the release!


Upgrade surefire and failsafe plugins to 2.18.1

Same version as used by KIE projects. I am hoping this could mitigate the intermittent build failures like this one https://kie-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/uberfire-extenstions-pullrequests/66/console

+1

https://github.com/uberfire/uberfire/commit/b03c1eaafdae501c8f5f0889d655ed941d2f0e71


Move configuration into a sub-folder

I think I found a bug with sorbet-coerce that is preventing us from upgrading
sorbet-rails (as newer versions have a dependency on sorbet-coerce). Because
configuration.rb is in the top-level lib/ folder, it is part of the ruby load-path
so require "configuration" will load sorbet-coerce/configuration. This is
breaking for us as we have an engine also called configuration, but it now
cannot be loaded without specifying the full path. After monkey-patching bundler
to be more verbose, I see:
Loading gem configuration
load paths for configuration/*:
"configuration.rb" => "/Users/kevinmiller/.rvm/gems/ruby-2.6.2/gems/sorbet-coerce-0.2.4/lib"
"configuration/engine.rb" => "/Users/kevinmiller/flexport/engines/configuration/lib"
"configuration/version.rb" => "/Users/kevinmiller/flexport/engines/configuration/lib"
resolved configuration to /Users/kevinmiller/.rvm/gems/ruby-2.6.2/gems/sorbet-coerce-0.2.4/lib/configuration.rb

Showing that require "configuration" is loading
/Users/kevinmiller/.rvm/gems/ruby-2.6.2/gems/sorbet-coerce-0.2.4/lib/configuration.rb
To fix, move configuration to a public subfolder. Ideally all of this
gem would be under a subfolder as require "public/configuration" is
less clear than require "sorbet-coerce/public/configuration", but that
is a more invasive change (happy to do a followup PR enforcing that if
y'all agree with me)

Codecov Report

Merging #40 into master will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #40      +/-   ##
==========================================
- Coverage   99.66%   99.65%   -0.01%
==========================================
  Files           6        6
  Lines         295      293       -2
==========================================
- Hits          294      292       -2
  Misses          1        1

Impacted Files
Coverage Δ

lib/public/configuration.rb
100.00% <ø> (ø)

lib/sorbet-coerce.rb
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

Ah, thanks for flagging this! I guess we should probably create a directory lib/sorbet-coerce, and move everything except sorbet-coerce.rbi and bundled_rbi into lib/sorbet-coerce?
Then we can require "sorbet-coerce/configuration without adding the public part.

I guess we should probably create a directory lib/sorbet-coerce, and move everything except sorbet-coerce.rbi and bundled_rbi into lib/sorbet-coerce

Yep that should do the trick (similar to how https://github.com/chanzuckerberg/sorbet-rails/tree/master/lib has nothing but the sorbet-rails.rb in the lib folder). I can ammend this PR to do it if you'd like

That'd be great!

Done in 8c5b55a


Start a channel on Slack, Gitter, or Discord

This is more of a community request. I notice that some questions that come in as issues are more inquiries and can easily be answered in a chat conversation than through an issue thread. I think it would improve the project if there was a channel on either Slack, Gitter, or Discord to answer small or frequently asked questions to reduce a lot of noise under issues.

I think this is a fine idea 👍 I don't have a ton of time to spend there, but if folks wnat to put something together i'm happy to promote it here

Okay, I will look into setting something up on one of the services mentioned.

Deployed in #767


[Parameter Request] codeunit 99000787 "Create Prod. Order Lines" publisher OnBeforeCopyFromSalesOrder parameter NextProdOrderLineNo

Can we please add the parameter NextProdOrderLineNo by reference in the publisher OnBeforeCopyFromSalesOrder of codeunit 99000787 "Create Prod. Order Lines"?
    local procedure CopyFromSalesOrder(SalesHeader: Record "Sales Header"): Boolean
    var
        SalesPlanLine: Record "Sales Planning Line" temporary;
        Location: Record Location;
        LeadTimeMgt: Codeunit "Lead-Time Management";
        ItemTrackingMgt: Codeunit "Item Tracking Management";
        SalesLineReserve: Codeunit "Sales Line-Reserve";
        ErrorOccured: Boolean;
    begin
        // >>>>>>>>>>>>>>>>>>>>
        //OnBeforeCopyFromSalesOrder(SalesHeader, SalesLine, ProdOrder);
        OnBeforeCopyFromSalesOrder(SalesHeader, SalesLine, ProdOrder, NextProdOrderLineNo);
        // <<<<<<<<<<<<<<<<<<<<

        SalesLine.SetRange("Document Type", SalesHeader."Document Type");
        SalesLine.SetRange("Document No.", SalesHeader."No.");

    [IntegrationEvent(false, false)]
    local procedure OnBeforeCopyFromSalesOrder(SalesHeader: Record "Sales Header"; var SalesLine: Record "Sales Line"; var ProductionOrder: Record "Production Order"; var NextProdOrderLineNo: Integer)
    begin
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Install Google Chrome, Chromedriver and Selenium

In this PR we changed Google Chrome installation logic in order to acquire the latest stable Google Chrome release from the official site. Also we implemented logic with installation of latest stable Selenium Server standalone. Finally we reworked ChromeWebDriver installation logic by implementing downloading of driver binaries from the official site. Version of ChromeWebDriver is selected based on Google Chrome browser version.

Our team authored some of these scripts when they were part of the azure-pipelines-images repo. We'll review them.


Minor grammar fix for pandas.rst

Changed "Plot the result as a bar graph like follows" to "Plot the result as a bar graph like this one" in Exercise 1.

Nice work @mtiley.  I'll go ahead and merge.


Bleak not found

Hi,
Thanks for this great feature.
After the integration worked great for me for several days, now the following error appears:
Here is my log:
Logger: homeassistant.setup
Source: setup.py:184
First occurred: 4. August 2022, 08:09:22 (1 occurrences)
Last logged: 4. August 2022, 08:09:22
Setup failed for custom integration delonghi_primadonna: Requirements for delonghi_primadonna not found: ['bleak==0.14.3'].

The new home assistant release need bleak 0.15.1 but the addon force the system to install the old version

Okay good to know, but what can I do to get the integration working?

try to do this:
open .homeassistant/custom_components/delonghi_primadonna/manifest.json and change
"requirements": ["bleak==0.14.3"],
to
"requirements": ["bleak>=0.14.3"],

its working! thank you

1.2.1 should completely remove this issue


Inject imagePullSecrets into the Helmchart

Pull Request Template
Prerequisites

If there is no issue related to your pull request - open one and assign yourself to it. If you're proposing a solution to an already opened issue - simply assign yourself to it.

Motivation
There should be a possiblity to add 'imagePullSecrets' to the Deployments to avoid any pulling rate-limiting issue.
Approach
This change adds 'imagePullSecrets' section into the Deployments and makes it configurable in the values.yaml file to be filled in by the consumer of the Helmchart.
Pull Request status

[x] Initial implementation
[ ] Refactoring
[ ] Unit tests
[ ] Integration tests

Feel free to construct the checklist with whatever items seem most reasonable for your change. You could disassemble the Implementation part to even smaller separate checklist items if you're working on something big for example. But do make the effort to provide a checklist of some sort so that the core team as well as the community can have an idea about the progress of your Pull Request.
Third-party code
If you use third party code with your contribution such as, components, libraries, or snippets make sure to mention that.
Work in Progress label
For as long as development of your Pull Request is still ongoing you MUST label it with a wip label as well as prefix the name of the PR with [WIP].
For example: [WIP] Service brokers API

Closing this PR as similar PR is merged https://github.com/SAP/sap-btp-service-operator/pull/188


backIconButtonProps and nextIconButtonProps don't work in  TablePagination

backIconButtonProps and nextIconButtonProps don't work in  TablePagination

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior
Removing backIconButtonProps={{'aria-label': 'Previous Page',}} from Sorting & Selecting sample table should not display previous page icon.
Changing backIconButtonProps={{'aria-label': 'Previous Page',}} to backIconButtonProps={{'aria-label': 'First Page',}} should display the first page icon.
Current Behavior
Changing backIconButtonProps={{'aria-label': 'Previous Page',}} in Sorting & Selecting sample table has no effect in the pagination icon.

Steps to Reproduce (for bugs)
Please change backIconButtonProps={{'aria-label': 'Previous Page',}} in Sorting & Selecting sample table.
https://codesandbox.io/s/34m25wk0o1

Context
I am trying to increase the size of the previous and next icon on table pagination.

Your Environment

Tech
Version

Material-UI
v1.0.0-beta.35

React
^16.2.0

browser
NA

etc
NA

Sorry, I don't understand your point. The reproduction demo doesn't show any issue.

What is the purpose of backIconButtonProps={{'aria-label': 'Previous Page',}}?  Changing "Previous Page" to "First Page" doesn't do anything.  Isn't changing "Previous Page" to "First Page" supposed to change the icon from "<" to "|<".


2.6.1 is broken: registry not found

$ docker run --rm -it registry:2.6.1 --help
/entrypoint.sh: exec: line 10: registry: not found

/bin/registry is missing. 😞
registry:2.6.0 works.

Closing as outdated.


Error #3500: The extension context does not have a method with the name init.

I get this error when i try to use the extension:
Error #3500: The extension context does not have a method with the name init.
I am using:
AIR 20.0.0 build 233
Other extensions like milkmangames GoViral work fine. i get the same error when air-ane-fullscreen is the only ane in the project
when i replace the ane with v1.3.3 everything works fine

Same here, happens with the last published ANE.

Can you confirm which version of Android you're using?

The error appears even before deploying the app to the device so i think the Android version does not matter.
There is no binary attached to the 1.4.0 realease. I only tested 1.4.1 and 1.3.3

I tested with Android 4.2 and Adobe AIR 20 and 19. I used the last published ANE and the 1.3.3 works fine as fknr stated.

I've rebuilt and updated the 1.4.1 binary: can you try downloading the updated ANE and let me know if you're still seeing the issue? It seems to be working fine here on our test devices.
https://github.com/mesmotronic/air-ane-fullscreen/releases/tag/v1.4.1

I tested your new build but unfortunately i still get the same error when i try to build the app.

Thanks for taking a look.
Version 1.4.x targets Android SDK 23 (previous versions targeted 19), so does your app.xml include any target SDK settings in the Android <manifestAdditions>? It would looks something like this:
<uses-sdk android:minSdkVersion="14" android:targetSdkVersion="23" />

If so, can you let me know what the settings are that you're using? And if the targetSdkVersion is <23, can you try setting it to 23 and building your app?

Tested new build everything works fine for me. But I am building with adobe flash professional. (air sdk 21) Have been using your extension for quite a while so wanted to say thanks anyway :)

Cheers @nitacawo, thanks for letting me know.

I tested a little more and found out that the ane works on an actual device. the error only happens in emulator mode. 1.3.3 works in emulator mode. I think that changed when you consolidated the default SWC into single file.
in 1.3.3 you use
	static public function get isSupported():Boolean
	{
		return false;
	}

and in > 1.4.0 you use:
	static public function get isSupported():Boolean
	{
		return !!context;
	}

for now a simple workaround is to check
	public static function isAndroid():Boolean
	{
		return (Capabilities.version.substr(0, 3) == "AND");
	}

before calling isSupported() in my code
It would be cool if you could fix this in one of the next versions. Thanks for your effort in provding this  very helpful ane

Thanks for the info: should be an easy fix now we know what the problem is.


AddDevice Support for TRV Moes ZTRV-ZX-TV01-MS _TZE200_7yoranx2 #1758

[Device Support Request] for TRV Moes ZTRV-ZX-TV01-MS _TZE200_7yoranx2 #1758

Looks good to my and i have adding it in the tuya TRV matrix https://github.com/zigpy/zigpy/discussions/653#discussioncomment-314395.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5269

Relevant Lines:
7358

💛  - Coveralls

Codecov Report
Base: 71.60% // Head: 71.60% // No change to project coverage :thumbsup:

Coverage data is based on head (c0f6d44) compared to base (a072ca3).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##              dev    #1770   +/-   ##
=======================================
  Coverage   71.60%   71.60%
=======================================
  Files         239      239
  Lines        7358     7358
=======================================
  Hits         5269     5269
  Misses       2089     2089

Impacted Files
Coverage Δ

zhaquirks/tuya/ts0601_trv.py
33.21% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Custom dropdown width (not the same as the button width)

Hi, is it possible to set a custom dropdown width (see attached screenshot)?
Tried to find it in docs or examples, but was unsuccessful.
It would be a great feature to have such an opportunity.

Same issue


Mark repo as [DEPRECATED] and "abandoned" on GitHub

This has been done on Packagist only, but not on GitHub, like https://github.com/php-http/utils.

Ping. :)

Done


Option for alternate sizing

Is it currently possible to specify an alternate size for the elements while still maintaining the current sizes?
I have my own theme and have identified a few select boxes throughout my website that I would like to be smaller than the default design (but still want to maintain the default design for the majority of select boxes).
I'm not able to identify a way to have two different sizes/design/look for select boxes. Any ideas would be greatly appreciated.

With the current version I don't think this is possible.  He may be working on a fix in 2.0


improve ChannelPipeline debug print

Calling print and debugPrint on a ChannelPipeline currently yields the following output:
ChannelPipeline (ObjectIdentifier(0x0000000101f26ea0)):
        handler0 (OpenSSLServerHandler) [IO]
        handler2 (HTTPResponseEncoder) [O]
        handler3 (HTTPRequestDecoder) [I]
        handler4 (HTTPServerRequestDecoder) [I]
        handler5 (HTTPServerResponseEncoder) [O]
        handler6 (HTTPServerUpgradeHandler) [IO]
        handler7 (HTTPServerHandler) [I]

This output is very handy, but I think it could be even better. I had some ideas:

Line up values so it's easier for the eye to scan
Get rid of redundant info (like repeating handler in handler1, handler2)
Make incoming vs. outgoing handlers more separated.
Add arrows so handler order is immediately clear.

Combining these ideas, I came up with this format:
ChannelPipeline[0x0000000101f26ea0]:
 #                      [I] ↓↑ [O]
 0     OpenSSLServerHandler ↓↑ OpenSSLServerHandler
 2                          ↓↑ HTTPResponseEncoder
 3       HTTPRequestDecoder ↓↑
 4 HTTPServerRequestDecoder ↓↑
 5                          ↓↑ HTTPServerResponseEncoder
 6 HTTPServerUpgradeHandler ↓↑ HTTPServerUpgradeHandler
 7        HTTPServerHandler ↓↑

Given this print out would require some additional calculations, I think it could make sense under debugPrint. But being the default print would be even better.
Thoughts? I'd be happy to submit a PR for this.

Sounds great, I love it!

Looks awesome, 👍

Thats a really cool idea.. I really love the "arrows" :)

really awesome, should we still print the name somewhere? I realise it's mostly handlerN but some people may actually name them?

@weissi +1

PR submitted. I updated the formatting slightly to include the handler name since as @weissi mentioned it may be unique.

PR merged, thanks @tanner0101


Export linker scripts in the bazel build.

Export linker scripts in the bazel build.
Make the rp2040 and rp2350 linker scripts available in downstream projects bazel builds.

nit: Commit-message says "rp2024" instead of "rp2040", but that probably doesn't matter.

nit: Commit-message says "rp2024" instead of "rp2040", but that probably doesn't matter.

fixed.

You edited the PR message, not the commit message :wink:

You edited the PR message, not the commit message 😉 But like I said, this doesn't really matter.

sorry, should have said "sort of fixed" :) Fixing up old commit message is a bit of a pain, and I don't know if this repo allows force commits.


[Feature] Refactored Github Addon

Purpose
https://github.com/CenterForOpenScience/osf.io/pull/2490
To bring Harris' work on the GitHub addon (#2490) up to date, and then use that as a baseline to create a generalized system for flat addons (currently only GitHub and S3) based on it (Much like tree-structured addons have addonNodeConfig.js and other files).
Changes
To be updated
Side-effects (and issues being worked on)
- [ ] Due to how merge conflicts were solved, model AddonGithubOauthSettings was deleted, which makes the script migrate_github_oauth_settings.py (and potentially others) unusable.

[x] The refactored github does not go to the request permissions page, it simply asks the users to login. (it goes to the request permissions page the first time a user is requested, probably handled github-side)

[x] Sometimes (maybe) Safari gives an error when attempting to request a token:

- [ ] UI looks different, first is production (github looks like others), second is local:

[x] "Test “ gets converted to “test-“, with no warning message. (Regex problem)

[x] Solve merge conflicts on tests/test_addons.py

[x] Fixes on node-cfg.js need to be transferred to GithubNodeConfig.js

[x] When attempting to connect on safari… (sometimes)

[x] Deleting access token does not reload page, if done after connecting account it leaves the success message up. This can be improved by simply deleting message when Delete token button is used

[x] Default user settings probably needs to be refactored.

[x] user-cfg.js is not being used

[x] Connect account no longer working through project settings (Could not retrieve Github settings at this time. Please refresh the page. If the problem persists, email support@osf.io.).

[x] inv test_addons giving 'cannot find folder_name and selected_folder_name' errors

[x] travis does not like my work (I was being dumb and made changes to my local.py without changing defaults.py)

re: the UI being different - The OAuth addon system means that the user settings shouldn't have to be defined by the addon. The user settings should look like Mendeley and Zotero, not how GitHub looks today.
This also applies to AddonGithubOauthSettings - that's a proxy object that was added by myself and @chennan47 after a bug was discovered in how we were handling OAuth. The OAuth system and the corresponding base classes for addon settings were based on the concepts introduced by that object. Its deprecation and removal is intended and expected :)

I believe this might be ok for review, I did not remove user-cfg.js or create a githubUserConfig.js, as it did not seem necessary (or wanted).

Ok, I think this might be good to go @lyndsysimon


Added Java solution for Find_in_mountain_array

Fixes #337
Issue
Given a mountain array mountainArr, return the minimum index such that mountainArr.get(index) == target. If such an index does not exist, return -1.
Describe the changes
I have firstly find out the index of max.(peak) element. Lastly, search target element in between 0th index to peak and then peak to last index element using Binary Search.

They are not considering dsa,cp,algorithm repository :(
all the pr will not be considered in hacktoberfest but your contribution will be for lifetime, this will help many students to practice dsa .
Thank you for your contribution :)
you can contribute to other repo


Errors in template

Anytime there's an error in a template, I get a huge aurelia-lib stacktrace. It would be nice if it caught those, and added the view name that's causing the issue. Maybe maintain the context?

Would you like to provide a pull request for it @RWOverdijk ?