IPAM old pod IPs not released! - IP pool is overflowing.

Expected Behavior
It needs to release old pod ips.
Current Behavior
Old dead pod ip's are not deleted and the ip pool is overflowing.
Errors
kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "a8bd154853bc05d1f066d25d14312fde780ce18477d59adad3e06e2cb773a5c6": failed to request 1 IPv4 addresses. IPAM allocated only 0
error: rpc error: code = Unknown desc = failed to get sandbox ip: check network namespace closed: remove netns: unlinkat /var/run/netns/cni-a97226df-f866-cd53-5403-184784fcb06c: device or resource busy
Context
In my k8s cluster (v1.20.7), I detected that calico does not release old pod ip's. Old dead pod ip's are not deleted and the ip pool is overflowing.

~]# calicoctl ipam show
+----------+----------------+-----------+-------- -----+-----------+
| GROUPING |  CIDR     | IPS TOTAL | IPS IN USE  | IPS FREE |
+----------+----------------+-----------+-------- -----+-----------+
| IP Pool | <IP_ADDRESS>/18 | 16384 | 15381 (94%) | 1003 (6%) |
+----------+----------------+-----------+-------- -----+-----------+

It seems to be using 15381 ip, but that's impossible. When I look at the details, I see that the ips of the dead pods are not released. In this case, it leads to IP address leak and potentially IP pool depletion. I have to manually release the IP pool. But after a while it gets full again.
I need to use --ip parameter to be able to release. I do this with a for loop to unused ip blocks, but it's still unmanageable.

~]# calicoctl ipam release --help
Set the Calico datastore access information in the environment variables or
supply details in a config file.
Usage:
calicoctl ipam release --ip= [--config=]
Options:
-h --help             Show this screen.
--ip=          IP address to release.
-c --config=  Path to the file containing connection configuration in
YAML or JSON format.
[default: /etc/calico/calicoctl.cfg]

Any ideas, what could cause this? Or is there a solution?
Your Environment

Calico version: Image: quay.io/calico/cni:v3.17.4
Orchestrator version (e.g. kubernetes, mesos, rkt): v1.20.7
Operating System and version: CentOS 7
Calicoctl Version : Client Version:    v3.17.4

We have fixed various sources of IPAM leaks over time, including adding an IPAM garbage collector (in v3.18, IIRC).  We also added calicoctl ipam check to help diagnose and clean up leaks when they occur.  Please upgrade to v3.20+ to get the latest IPAM garbage collection and let us know if that solves the problem.

For some in-house reasons I was only able to upgrade the calico version to v3.19.2. But I see that the overflow has stopped in this version as well. Moreover, I can see the problem ip's with the check command.
Thanks. @fasaxc

We had a similar problem with calico 3.19.2.  I found a good way to release all leaked IPs:
sudo /usr/local/bin/calicoctl.sh datastore migrate lock
sudo /usr/local/bin/calicoctl.sh ipam check --show-problem-ips -o report.json
sudo /usr/local/bin/calicoctl.sh ipam release --from-report=report.json
sudo /usr/local/bin/calicoctl.sh datastore migrate unlock

This type of problem can likely be caused by this issue on k8s v1.21:  https://github.com/kubernetes/kubernetes/pull/102344

Had this when upgrade Calico from 3.22 to 3.24, and K8S from 1.23 to 1.24, and also docker migration to containerd

@geotransformer How did you install Calico?  Are you using the kubernetes datastore?  When using the kubernetes datastore, Calico should garbage-collect any leaked IP addresses (the component that does that is calico-kube-controllers, is that component running and healthy in your cluster?)

@geotransformer How did you install Calico? Are you using the kubernetes datastore? When using the kubernetes datastore, Calico should garbage-collect any leaked IP addresses (the component that does that is calico-kube-controllers, is that component running and healthy in your cluster?)

@fasaxc  we do use the "datastore_type": "kubernetes".
Actually in our upgrade, there is also a host OS upgrade. So the 1-node k8s cluster will be reinitialized with old ETCD data. After k8s re-initialized, we found the pods are stuck at container creating.
Even calico-kube-controllers was in ctuck state.
user@xxx-node1:~$ kubectl describe pod -n kube-system calico-kube-controllers-84c476996d-f762r
Pv4 addresses: Assigned 0 out of 1 requested IPv4 addresses; No IPs available in pools: [<IP_ADDRESS>/24]
Warning FailedCreatePodSandBox 63s (x241 over 54m) kubelet (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "9e4b1822702db6a204e852b77a9e4bbd13335be87b35b152c5c38bd2a0ec84c6": plugin type="calico" failed (add): failed to request IPv4 addresses: Assigned 0 out of 1 requested IPv4 addresses; No IPs available in pools: [<IP_ADDRESS>/24]


Theme for tlrc

I made a dracula theme for tlrc: https://github.com/noraj/tlrc-dracula

Does the in trasnfer label means the theme was accepted and I should transfer it to https://github.com/dracula?

Finally, submit an issue with a link to your repository. Once the theme is accepted, we will move the repository under the Dracula organization and give you rights to maintain it 😀

Hey, that's very cool! ✨
I just sent you an invitation to join the organization.
I also cloned your repository for Dracula's organization, so you can go ahead and delete or archive yours:

Your repository.
New repository.

Thanks for building this! 🎉


ibc-apps repo issues are not maintained

Hello Cosmos team
I'm not 100% sure if this is correct place to open this issue, but since ibc-apps was inside ibc-go initially I think it is ok.
In last few months I created 2 issues (https://github.com/cosmos/ibc-apps/issues/189 & https://github.com/cosmos/ibc-apps/issues/187) in ibc-apps repo and they are still pending for comments from core team.
Also I mentioned that most of issues inside https://github.com/cosmos/ibc-apps/issues repo are just ignored.
If possible would be nice to assign someone to be responsible for the repo maintenance

Hi @ysv. Thanks for raising your concerns. We are not the maintainers of those apps in the inc-apps repository (and they were not initially inside ibc-go, but in other repositories). I can contact the maintainers and ask then to take a look though. Is there anything blocking you from the issues that you opened? Having a quick look at the issues you shared, looks like they are questions or documentation related, right?


Separate browser specific and pure JS questions

Hi guys, thanks for questions.
I just want to mention that there are many ReactNative and node.js devs who not so interested in browser specific questions during interview, it would be great to separate them.
Thanks.

Thanks for your input! I try to make most questions not browser specific, but since most JS devs have a (basic) understanding of the DOM, I added them anyway. I feel like separating them would make the questions a bit chaotic - although what I can do is add labels to them to show when a question is browser/node specific.


reference a view and not a table

Hi,
I wanted to reference a view:
models:

name: my_table
description: This table contains our toy model
tests:

dbt_expectations.expect_table_column_count_to_equal_other_table:
compare_model: ref("my_table_view")

resulting in:
Failure in test dbt_expectations_expect_table_column_count_to_equal_other_table_my_table_ref_my_table_view_ (models/my_first_folder/schema.yml)
Got 7 results, expected 0.
are the tests only working with tables?

Hey @misteliy sorry just saw this, somehow I didn't set up GH notifications correctly.
No, there's no reason the tests shouldn't work with views, in fact my initial integration tests were using views. Any chance this is an underlying data problem? Which platform (BG, Snowflake..) are you on?
I'll check this out locally, but please let me know if you're still seeing this.

Confirmed this works on BQ and Snowflake:

Created a view that selects from test table
data_test_view.sql

{{
    config(
    materialized = 'view'
    )
}}

select * from {{ ref('data_test') }}

Confirmed that test works in both directions:
  - name: data_test_view
    tests:
        - dbt_expectations.expect_table_column_count_to_equal_other_table:
            compare_model: ref("data_test")

  - name: data_test
    tests:
        - dbt_expectations.expect_table_column_count_to_equal_other_table:
            compare_model: ref("data_test_view")

Closing this, but feel free to reopen if you're still having this issue. Thanks!


WIP: Better memory info parse patterns, so that only lines with memory slo…

1663

 Quality gate: Failed
1 Issues

 1 Code issues

Details

 Quality gate: Failed
1 Issues

 1 Code issues

Details


Not all handouts are shown

When I try to download the handouts for mongdb nodejs course. It lists only first 6 weeks.
So no week 7 and final exam. But if I decide to download all handouts , it will download week 7 and exam handouts.

Can't replicate on my side. Just tested against 0.2.5 and M101JS handouts and I can see all handouts listed from week 1 to week 7 including final exam. Selecting All downloads all listed items as expected.

My mistake, I needed to scroll the page in order to see all the results.


README doesn't mention how to run neovim

Here's what I tried:
% brew install neovim/neovim/neovim
% neovim
zsh: command not found: neovim
After some digging around I found out that you run it with nvim. Why not just say so?

Doesn't the brew advice message say so when you install?

I don't remember but it's a strange thing to leave out of the readme either
way.
On Thu, Jul 21, 2016 at 5:44 PM Justin M. Keyes<EMAIL_ADDRESS>wrote:

Doesn't the brew advice message say so when you install?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/neovim/homebrew-neovim/issues/168#issuecomment-234425492,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAA8qk-FTf_eiywc9DDx1TBFV07B_Uh8ks5qYBJ7gaJpZM4JSTQB
.


Add no_auth flag

Add NONE as an AuthType.

Codecov Report

Merging #1158 into master will decrease coverage by 0.09%.
The diff coverage is 56.25%.

@@             Coverage Diff             @@
##             master    #1158     +/-   ##
===========================================
- Coverage     86.16%   86.06%   -0.1%
  Complexity     3653     3653
===========================================
  Files           369      369
  Lines         14385    14378      -7
  Branches       1603     1604      +1
===========================================
- Hits          12395    12375     -20
- Misses         1556     1569     +13
  Partials        434      434

Impacted Files
Coverage Δ
Complexity Δ

...le/api/codegen/DiscoveryFragmentGeneratorTool.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...gle/api/codegen/DiscoveryFragmentGeneratorApi.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

.../google/api/codegen/discovery/config/AuthType.java
100% <100%> (ø)
1 <0> (ø)
:arrow_down:

...oogle/api/codegen/discovery/ViewModelProvider.java
85% <100%> (-5.17%)
11 <2> (ø)

...odegen/discovery/MainDiscoveryProviderFactory.java
88.67% <100%> (ø)
6 <0> (ø)
:arrow_down:

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 0e49ab2...e44efed. Read the comment docs.

Also, do we need to add snippet support for the NONE option?

The motivation for this flag is to avoid calling auth code in the mock tests - but it could also be used to generate samples without auth boilerplate.
I will add snippet support language by language, I didn't want to make this PR too big.

Is this still in flight?


invoice datepicker added

datepicker added for the invoice.

Checklist:

[ ] I have manually tested all workflows
[ ] I have performed a self-review of my own code
[ ] I have added automated tests for my code

@apoorv1316 please test


restic engine: check if bucket exists before init (#148)

cf: https://github.com/restic/restic/issues/1690#issuecomment-377496565

Coverage decreased (-0.1%) to 12.961% when pulling d73b00c89df050572d52abf01d0309cecc5b029c on cryptobioz:restic-check-init into 18550297f759344d4b3cffcd17ded4df0d0b2d07 on camptocamp:master.

LGTM


Removes unused de.json and es.json files

Considering we're not currently localizing locales, there is really no need to keep the unused es.json and de.json files in sync.
When we begin localization, we can reintroduce these files. At that time, the syncLocales script will ensure the files are kept in sync, just as it does now.
Fixes https://github.com/project-koku/koku-ui/issues/620

Codecov Report

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

@@           Coverage Diff           @@
##           master     #621   +/-   ##
=======================================
  Coverage   81.27%   81.27%
=======================================
  Files         194      194
  Lines        3001     3001
  Branches      499      499
=======================================
  Hits         2439     2439
  Misses        495      495
  Partials       67       67

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 5b2f108...e56bbfe. Read the comment docs.


Electron keeps main menus underlined if Windows are switched using Alt+Tab

Refs: #25326
OS: Windows
Steps:

VS Code in focus
press and hold Alt (observe: main menu mnemonics get underlined)
press tab and switch to other application. Observe: VS Code main menu still underlined
press Alt+tab again to focus back on VS Code. Observe: main menu still underlined.

Yeah, looks like an Electron issue with the non-native menus being used.

We will change to custom menus on Windows. For now you can set "window.titleBarStyle": "custom".


Numerous user settings added

Major changes

all package versions updated to May 2017

cli-color now allows color nesting

Bugfixes

error report counter resets to 1 on subsequent run (https://github.com/dgarlitt/karma-nyan-reporter/issues/31)
don't hide errors that occur (https://github.com/dgarlitt/karma-nyan-reporter/issues/26)

Angular 2 template parse errors no longer hidden

User options

colors for error report
exclude from error report lines that contain user-chosen strings
underline all filenames of any user-chosen filetype
hide browser version information from error log
clear screen before every run

A diff for passing tests, 100% coverage, and more tests for added functionality coming

Coverage decreased (-26.0%) to 74.005% when pulling 3a0c107b7717355bccdffdc00a8e64317a9bb8ed on whyboris:nyannyan into 68da8261defe424c4ecf7805034f2de778c06d96 on dgarlitt:master.

Coverage decreased (-7.5%) to 92.506% when pulling 5dce68b365b584277ce6a3c27c7e8c50fb749a1e on whyboris:nyannyan into 68da8261defe424c4ecf7805034f2de778c06d96 on dgarlitt:master.

Coverage decreased (-7.03%) to 92.974% when pulling 81ebc137ffca7146b12e2d4f45962611c5006200 on whyboris:nyannyan into 68da8261defe424c4ecf7805034f2de778c06d96 on dgarlitt:master.

Coverage decreased (-3.7%) to 96.253% when pulling 8f33ff2ecadd81ba430b42dfe4860f3b3d27fba6 on whyboris:nyannyan into 68da8261defe424c4ecf7805034f2de778c06d96 on dgarlitt:master.

Coverage decreased (-1.6%) to 98.361% when pulling a12b8f4f28b87cef84ea585feafa95eac1a1ef52 on whyboris:nyannyan into 68da8261defe424c4ecf7805034f2de778c06d96 on dgarlitt:master.

Coverage decreased (-0.7%) to 99.297% when pulling 90bc1e78885d86f2bfc4062da3b3f9ea3c652e32 on whyboris:nyannyan into 68da8261defe424c4ecf7805034f2de778c06d96 on dgarlitt:master.

Coverage decreased (-0.7%) to 99.297% when pulling dbfc1e87bd545b9f185c9af2256e03f8bb5cb36e on whyboris:nyannyan into 68da8261defe424c4ecf7805034f2de778c06d96 on dgarlitt:master.

Coverage remained the same at 100.0% when pulling bd5f73dd1283c4fe080e43a2ac75675e6edcd963 on whyboris:nyannyan into 68da8261defe424c4ecf7805034f2de778c06d96 on dgarlitt:master.

Coverage remained the same at 100.0% when pulling bd5f73dd1283c4fe080e43a2ac75675e6edcd963 on whyboris:nyannyan into 68da8261defe424c4ecf7805034f2de778c06d96 on dgarlitt:master.

Coverage remained the same at 100.0% when pulling bd5f73dd1283c4fe080e43a2ac75675e6edcd963 on whyboris:nyannyan into 68da8261defe424c4ecf7805034f2de778c06d96 on dgarlitt:master.

Coverage remained the same at 100.0% when pulling bd5f73dd1283c4fe080e43a2ac75675e6edcd963 on whyboris:nyannyan into 68da8261defe424c4ecf7805034f2de778c06d96 on dgarlitt:master.

Coverage remained the same at 100.0% when pulling bd5f73dd1283c4fe080e43a2ac75675e6edcd963 on whyboris:nyannyan into 68da8261defe424c4ecf7805034f2de778c06d96 on dgarlitt:master.

Coverage remained the same at 100.0% when pulling bd5f73dd1283c4fe080e43a2ac75675e6edcd963 on whyboris:nyannyan into 68da8261defe424c4ecf7805034f2de778c06d96 on dgarlitt:master.

Coverage remained the same at 100.0% when pulling bd5f73dd1283c4fe080e43a2ac75675e6edcd963 on whyboris:nyannyan into 68da8261defe424c4ecf7805034f2de778c06d96 on dgarlitt:master.

Coverage remained the same at 100.0% when pulling bd5f73dd1283c4fe080e43a2ac75675e6edcd963 on whyboris:nyannyan into 68da8261defe424c4ecf7805034f2de778c06d96 on dgarlitt:master.

Coverage remained the same at 100.0% when pulling bd5f73dd1283c4fe080e43a2ac75675e6edcd963 on whyboris:nyannyan into 68da8261defe424c4ecf7805034f2de778c06d96 on dgarlitt:master.

Please let me know if you would like to assimilate the functionality I am trying to add in this PR before I spend more time fixing tests (there are a few left).

Coverage decreased (-0.2%) to 99.774% when pulling 85cd42a13da61037968e74f732a23cd8328c6dbc on whyboris:nyannyan into 68da8261defe424c4ecf7805034f2de778c06d96 on dgarlitt:master.

Coverage remained the same at 100.0% when pulling b27b42ee34ad36d32a4ac52f7e4b14ce9400d44e on whyboris:nyannyan into 68da8261defe424c4ecf7805034f2de778c06d96 on dgarlitt:master.

@whyboris I would rather go back to addressing each of these additions individually. I have procrastinated on this for a while because there are several items I'd like to discuss. It seems like the  template parse errors in Angular 2 are more important, so I you could open a single pull request for that, that would be great. Then we can address the remaining items one at a time.
The main items that I'd like to discuss are

exclude from error report lines that contain user-chosen strings
underline all filenames of any user-chosen filetype
new rainbow

But, again, it would be nice to address your open issue (#26) by itself, first.

Thank you for your willingness to include changes into your project.
I'll extract the functionality from this PR and break it into pieces. I'll create a single pull request addressing these two:

Template parse errors in Angular 2 (https://github.com/dgarlitt/karma-nyan-reporter/issues/26)
Reset numbering of tests on each re-run (https://github.com/dgarlitt/karma-nyan-reporter/issues/31)


boards: nrf52840_pca10059: Fix pyOCD configuration

Use the correct pyOCD target type for the NRF52840.
This fixes b92436a13f39df93029e881994ebf5d7b071bc4e.
Tested with: Atmel ICE Debugger
Signed-off-by: Henrik Brix Andersen<EMAIL_ADDRESS>

Codecov Report

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

@@           Coverage Diff           @@
##           master    #9632   +/-   ##
=======================================
  Coverage   52.16%   52.16%
=======================================
  Files         212      212
  Lines       25919    25919
  Branches     5584     5584
=======================================
  Hits        13520    13520
  Misses      10148    10148
  Partials     2251     2251

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 2af8dc9...de7cfd2. Read the comment docs.


Container with Most Water Problem -Leetcode

Kindly assign this under hacktober fest to me.

I would like to contribute.
Kindly assign it to me.
Thank! @sherigar

could you please assign this issue to me.? I want to work on this problem.!


[Blazor p8] OnInitializedAsync is executed for twice on pre-render

Issue
OnInitializedAsync is executed for twice on pre-render
General
[dani@localhost tw]$ dotnet --version
3.0.100-preview8-013656

I wrote this code:
@page "/"
@inject IUriHelper UriHelper

Hello, world!

Welcome to your new app.

@code{

    protected async override Task OnInitializedAsync()
    {
        System.Console.WriteLine("_*   ");
        System.Console.WriteLine("_**************************");
        System.Console.WriteLine("_***** Pre render ******");
        System.Console.WriteLine("_**************************");
        System.Console.WriteLine("_   ");
        return;
    }
}

And I see is executed for twice only on pre-render:

Has it some explanation?
The question on stackoverfow: Blazor UriHelper.NavigateTo is calling the page twice

I think blazor related issues should be posted in AspNetCore repo:
https://github.com/aspnet/AspNetCore

Of course @hez2010 , thanks: https://github.com/aspnet/AspNetCore/issues/13607


-e should parse  tags

so I have been using feroxbuster for a while and it has been my go-to tool replacing dirb and gobuster I used in the past.
There is something that I couldn't do with feroxbuster, however. I wonder if there is an option I miss.
I tested it on HTB openadmin. In this machine, the key is the /ona path (which is linked from /music -> login).
Feroxbuster missed this path while dirbuster (with default config) can get /ona quickly.
I thought I just need to pass -e on feroxbuster and it should find it; However it doesn't work.
dirbuster by default will do "parse html" - if I disable this, then it won't find it as well.
So what would be the equivalent of "parse html" in feroxbuster?
Originally posted by @hartoyob in https://github.com/epi052/feroxbuster/discussions/236
My reply is linked below
https://github.com/epi052/feroxbuster/discussions/236#discussioncomment-433443

fixed; -e now extracts <a> as well as other html tags


Exception during training - unexpected keyword max_dets_per_image

Instructions To Reproduce the 🐛 Bug:

I am using the d2go python API with the ballon example except for adding a change to evaluating it after every 500 iterations & to detect only 15 objects per test image

cfg.TEST.DETECTIONS_PER_IMAGE = 500
cfg.TEST.DETECTIONS_PER_IMAGE = 15

Full logs or other relevant observations:
Error log uploaded here:
https://storage.googleapis.com/guardian_dataset/max_dets_per_image_error.log

The evaluation parameters gives the following error during runtime
  File "/usr/local/lib/python3.7/dist-packages/d2go/runner/default_runner.py", line 538, in get_evaluator
    max_dets_per_image=cfg.TEST.DETECTIONS_PER_IMAGE,
TypeError: __init__() got an unexpected keyword argument 'max_dets_per_image'

Expected behavior:
Evaluation at every 500 iterations.
The same configuration was working a few days earlier. But now is raising an error

This was solved by installing the nightly version of pytorch


Problem with multicast Timeout

Good morning,
i have an issue caused by multicastTimeout.
In my environ, i do a coap multicast get request in order to get info from all devices. The get return successful, but the socket closes after the multicastTimeout causing that can't reuse the agent (i my case the globalAgent) for other requests.

Hi @straccio, could you provide an example code?

Hi @GiedriusM
My issue is related to this. I don`t receive a 'timeout' event on my multicast-request.
coap-version: 0.23.1
Setup:

1 rpi with openthread borderRouter connected to nrf52-DK with NCP
2 nrf52 DK with openthread/coap stack.

I send a GET multicast-message from rpi to my thread-network.
I then receive a coap-response from both thread-devices, but my 'timeout'-handler never fires.
See code below:
`coap_server.listen({}, () => {
console.log("COAP Server listening on " + SERVER_HOST + ":" + SERVER_PORT);
incoming_message_count = 0;
const options = {
host: 'ff03::1',
multicast: true,
multicastTimeout: 10000,
confirmable: true,
port: SERVER_PORT,
method: "GET",
pathname: "/question"
};
const payload = Buffer.from([0x04]);
var req = coap.request(options);
req.write(payload);
console.log('\n\nsending "quizStart" multicast message');
req.on("response", res => {
// message received from end-device
if (res.code == "2.00") {
incoming_message_count++;
console.log("response ok from device: ", res.rsinfo.address.slice(-19));
}
});
req.on("timeout", () => {
console.log("message timed out.");
console.log(got response from ${incoming_message_count} devices);
});
req.on("end", () => {
console.log("request sent");
process.exit(0);
});
req.end();
});`


Update volcano-0.1.tgz to use v0.1 tag

Changed the below content in values.yaml and made a new package
  image_tag_version: "v0.1"
  controller_image_name: "volcanosh/vk-controllers"
  scheduler_image_name: "volcanosh/vk-kube-batch"
  admission_image_name: "volcanosh/vk-admission"

https://github.com/volcano-sh/volcano/issues/347

/lgtm
/approve


Add singularity installation in slurmd via .deb and .rpm

This new feature adds the singularity installation in the slurmd setup process.
The installation can be done with .deb (Ubuntu) or .rpm (Centos7)
This PR requires an updated branch of slurm-ops-manager:
https://github.com/jaimesouza/slurm-ops-manager/tree/jaime-dev-singularity
And also an updated branch of slurm-bundles:
https://github.com/jaimesouza/slurm-bundles/tree/jaime-dev-singularity
How was the code tested?
The code was tested with the following commands:
juju deploy ./slurmd.charm dev--resource singularity-deb=../slurm-bundles/singularity-ce_3.10.2-focal_amd64.deb
juju deploy ./slurmd.charm dev --resource singularity-rpm=../slurm-bundles/singularity-ce-3.10.2-1.el7.x86_64.rpm --series centos7
A simple test can be found in tests/80-singularity.bats.
Final checklist

[ x ] I am the author of these changes, or I have the rights to submit them.
[ ] I added the relevant changed to the README and/or documentation.
[ x ] I self reviewed my own code.
[ ] I updated the CHANGELOG according to the contributing
guide

Hi @heitorPB ,
Thanks for the comments and suggestions. I agree with you.
I am gonna move the class to slurm-ops-manager and also update this PR according to your suggestions.


Take Fresca YAML as input?

FRESCA supports YAML as input, would HackMyResume want to extend it's engine to support taking .yml files as input?

Yes. Starting in v1.7.0 HMR will accept "equivalent" YML and/or XML for any resume input -- including both FRESH/FRESCA and JSON Resume formats.

Also mentioned in #11.

Will this support multiple yaml files, e.g. hackmyresume build resume1.yml resume2.yml TO resume.json ? also is there a format assumed (jrs or fresh)?

I like the idea of yaml as authoritative input. Here's my shell one-liner to get that ability:
cat resume.yml |python3 -c 'import json,sys;from ruamel.yaml import YAML;yaml=YAML(); print(json.dumps(yaml.load(sys.stdin)))' |hackmyresume build /dev/stdin TO index2.html

Note: requires pip3 install ruamel.yaml


When it's fixed of "Program Compability Assistant"?

When Installation has finished, it keeps showing even it's installed properly/correctly
I don't know how about windows 8 and later, it occured on Windows 7.

It's normal since it's targeted to an older OS than you're using, so it will show that dialog as it thinks you're installing a program designed for an older version of Windows.

The issue in the OP has also been encountered in #595 :

Also I've been getting a prompt to reinstall with recommended setting including previous versions when the installer worked. Here's a basic image of the error:

... also under Win7 SP1:

Notably, the previous installation of R5 did indeed issue a warning about "This program might not have installed correctly, etc.", which I ignored, as, subsequently, R5 worked absolutely fine. Installation of R6 atop of R5 did not produce this warning. I suppose you'd better fully uninstall it and install it afresh.

and:

With R6 i got it once but afterwards it didn't appear again, even after the reboot.

The problem would originate with the 7z SFX installer stub. It appears that the fix would be to increase the value of the MajorOSVersion field in the installer from 4 to 6. This would not impact the ability for the installer to run on NT 5.x (presently its minimum is XP SP2/2003 SP1, although the browser itself works at slightly lower update levels than those).


How to use external css class in shortcuts？

i have a css class  .use-click
it's
use.css
.use-click {
    cursor: pointer;
}

.use-click:hover {
    opacity: 0.9;
}

.use-click:focus {
    opacity: 0.9;
}

.use-click:active {
    opacity: 0.6;
}

i want use it in  shortcuts
vite.config.js
shortcuts: [
                [/^btn-(.*)$/, ([, c]) => `bg-${c} color-white py-10 px-20 bd-radius-20 use-click`],
            ]

it not work
Is it a problem with the way I use it, or does unocss not support external css classes?

console tips : unmatched utility "use-click" in shortcut "btn-theme"

Mixed use is not recommended. You can try to add outside class to shortcuts
Playground

Mixed use is not recommended. You can try to add outside class to shortcuts
Playground

External style classes are very numerous, I would be exhausted to write a rule for each style, can we support external style classes in the future? Is there any consideration for not supporting it? I was curious so I asked, thanks for your answer

By default, your shortcut is not supported because for what I understand you want the btn-x to add class use-click, which basically is a transformer behavior. Your option are:

Remove use-click from the shortcut, and write a transformer to add the required classes (ex. class="btn-x" -> class="btn-x use-click")
Remove use-click from the shortcut, but use separate class class="btn-x use-click", and add your custom css either via <link> or preflight
Register use-click as fully controlled rule so that use-click will be matched & applied with your existing shortcut of [/^btn-(.*)$/, ([, c]) => bg-${c} ... use-click],

默认情况下，shortcut不支持您的，因为据我所知，您希望btn-x添加 class use-click，这基本上是一种转换器行为。您的选择是：

从快捷方式中删除use-click，并编写一个转换器来添加所需的类（例如class="btn-x"-> class="btn-x use-click"）
use-click从快捷方式中删除，但使用单独的 class ，class="btn-x use-click"并通过<link>或preflight添加您的自定义 css
注册use-click为完全受控的规则，以便use-click与您现有的快捷方式匹配并应用[/^btn-(.*)$/, ([, c]) => bg-${c} ... use-click],

The way you said can solve my problem, thank you,
But I think the use of css class in rule is a very common requirement, I hope to consider supporting it, I can't think of any valid reasons not to support it


[Resource] Memberships

@did which actions should be implemented?  I currently have only list/index.


Implement state_class total for grouped energy sensor

Also have a look into introducing a service to reset the sensor.

Implemented with #804


Motivation

It’s not used anywhere.

@andrefmrocha you have added this code as part of https://github.com/bazelbuild/rules_scala/pull/1068 but PR https://github.com/bazelbuild/bazel/pull/11766 for which this code was added is stuck.
Do we still need to keep this code around? Are there any plans to progress with https://github.com/bazelbuild/bazel/pull/11766?

@andrefmrocha you have added this code as part of #1068 but PR bazelbuild/bazel#11766 for which this code was added is stuck.
Do we still need to keep this code around? Are there any plans to progress with bazelbuild/bazel#11766?

Unfortunately I've had very little feedback on bazelbuild/bazel#11766, even after various attempts to reach out. So I think it's okay to remove it.

However, the ProtoReporter's output as a whole is already being used in bazel-bsp, so I hope we can maintain that

However, the ProtoReporter's output as a whole is already being used in bazel-bsp, so I hope we can maintain that

absolutely, I’m not trying to get rid of the proto output. Just of code that isn’t contributing to producing the output.


Fix WS disconnection handling

The following reconnections scenarios are handled in this PR

[x] The server closes the connection, gun_down is handled correctly
[x] The gun process crashes, the monitor message is used to react to it
[x] Ping timeout, if the server is not pinging, the client throws away the connections and re-attempts it.

This PR requires https://github.com/stritzinger/kraft/pull/3 to go in production

Oh the previous comment only refers to the tests. I missed the commits before. Wait for another approval!

Looks good. What would also be important to test, but maybe only manually is how grisp_connect handles a longer disconnect or a random sequence of different kinds of disconnects. Do we get some queue up of gun instances for example? I can't think of a test case, but manually we should just unplug and replug the ethernet cable a lot to test the handling of this kind of disconnect as well. (Is it the same as crashing gun? I don't think so.)

Quick network interrruptions are unhandled (undetected) by gun. So an API call will just timeout but gun will not generate errors. That is why the ws_ping_timeout I am introducing in this PR is so important. It forces gun to reconnect.


Insert shell env var into env var priority order

As mentioned in lines 115 through 117, "Values in the shell take precedence over those specified in the .env file. If you set TAG to a different value in your shell, the substitution in image uses that instead:".
This context should also be represented in the order of priority in which variables are processed.

Deploy preview for modest-edison-79d82e ready!
Built with commit 1b85085ca90581a86a638080b8dc093436875afe
https://deploy-preview-7107--modest-edison-79d82e.netlify.com


Misleading subdevice type for Osram Lightifiy Smart+ Plug

Home Assistant release (hass --version):
0.62.1 (also prior versions)
Python release (python3 --version):
3.6.3
Component/platform:
osramlightify
Description of problem:
An Osram Smart+ Plug connected to Lightify Gateway gets a misleading entity type.  It's discovered as "light.plugname". In the UI, the device also has light controls (brightness, color select etc..) where it should only be treated like a switch (on/off)
Expected:
Should be discovered as switch.plugname. But the component only accepts "light" as platform.
There should be also a "Osram Lightify Switch" component

Hello Does the LIGHTIFY ZigBee 2 Button Wireless Dimmer Switch work with home assistant?

Hello, I’m using Home Assistant with hassio image since yesterday and the issue with the Osram Smart+ Plug as light is still there.

Issue is still present in 0.76.1

The same thing occurs with the lightify dimmer switch in the latest release.  The switch shows up as a light that cant be controlled.

the lightify component was initially setup as a light platform so what you guys are asking seems to be more of a feature request as it was never designed to be a switch  the upstream library does support switch and motion sensors so someone will need to submit a PR for this.
https://github.com/home-assistant/home-assistant/blob/master/homeassistant/components/light/osramlightify.py

Is there any progress on this issue?
I have the same problem with my osram smart+ plugs which are shown as lights. Really annoying.

I am going to look into this when I have the time.
However I don't think you will be able to make much use of the switches in home assistant since the gateway already triggers the lights and there's no mechanism for home assistant to get notified instantly about state changes. So it has to regularly poll the gateway to get the state.
If the only problem is that the switches appear in the UI as lights, that should be fixable.

At the moment is the only problem that the switches appear in the ui as lights. Would be awesome if you could look  into this.

Some here with 0.77something ;)
I can change settings like brightness, color and so on on my two plugs.

sorry, it seems I will not have time for this. I looked into it for an hour, but I can't easily figure out how to make switches, motion detectors and plugs known to home assistant as these kind of components. The whole osramlightify.py module is only made for lights and not my own code.
The easiest solution would be to not return non-light objects in the lightify component. However both motion detector and plug still have some functionality if used as a "light" in home assistant. So for those I wouldn't want to do this.

Hello @tfriedel,
I'm irritated - Why not using your commit https://github.com/tfriedel/python-lightify/commit/a9617a5f845f85afd0c5f213af3fb515ed0f8afb#diff-6bd9ebefac120a106919b1e2edf720d8, that we can isolate lights as lights and switches as switches (There should be a new switch component needed)
Thanks, Thomas

@tfriedel @tringler
Hey, I'm the one who wrote the code for the lightify groups, but I did so picking up on code already existing in HA. So in other words, the strange class structure @tfriedel saw, is my fault (sorry for that) but I decided doing so because it removed redundant code.
First questions first, I don't think I will/can do all this on my own any soon, so are there people willing to help me out with this?
As @dshokouhi mentioned, the component was only written for lights, because that is all I had up to that point. By now I have also switches, and I started to think about implementing them as well. However, I'm not sure how to do this. As a roadmap, I would suggest doing it in two phases.

Implement a new switch/lightigy.py component. (quick and dirty)
Rewrite code into some kind of separate component (taking the hue component as a reference)
I don't know about the full capabilities of the hue component, but I think it handles switches and stuff correctly.

I think the hardest is 1., because we will, as @tfriedel  mentioned, need to make python-lightify aware of switches. As far as I remember this is not implemented yet. The good news is binary-protocol has already done the hard work of reverse engineering the protocol itself. Thus  we should be able to add the device types to python-lightify.
My vision for 2. is:

auto detection of lightify bridges
implementation of all device types
rewrite of the way we handle groups of lights in HA

Auto detection and implementation of further device classes should be straight forward, but the rewrite of the light groups puzzles me. The problem with the current system is a mismatch between the way HA handles lightify light groups and how lightify handles groups itself. Namely lightify light groups don't have a state. They can't be on or off, you can only switch them on or off, however, HA assigns a state to these groups, by looking at the state of the first light in the group and assuming the state of that light is the same as the group itself. This leads to quite some strange behaviour when dealing with groups of lights.
I started to believe it would be better to remove the state from the lightify light groups as well and not assume anything about it, since it is wrong about half of the time anyways. Of cource this would be a breaking change for some people, because automations using the state of a lightify light group would not work any more.


unique_together doesn't work

Hello!
I have the following code:
models.py
class Fulfillment(models.Model):
	percentage 	= models.FloatField()
	month 		= models.ForeignKey(Month)
	year 		= models.ForeignKey(Year)
	company 	        = models.ForeignKey(Company)
	country 	        = models.ForeignKey(Country)
	class Meta:
		verbose_name 		= 'Budget Fulfillment'
		verbose_name_plural = 'Budget Fulfillments'
		get_latest_by 		= 'year'
		unique_together 	= (('company','country','year', 'month'),)

admin.py
class FulfillmentResource(resources.ModelResource):
	company = fields.Field(column_name='company', attribute='company',widget=widgets.ForeignKeyWidget(Company,'name') )
	country = fields.Field(column_name='country', attribute='country',widget=widgets.ForeignKeyWidget(Country,'name') )
	class Meta:
		model = Fulfillment
		fields = ('id','company','country','year','month','percentage')
		export_order = ('id','company','country','year','month','percentage')

so, when I import a xls with the duplicate data, unique_together does not work (the duplicate data is added to database).
can you help me with this?

did you add unique_together after creating table? It should be enforced at the database level
https://docs.djangoproject.com/en/1.8/ref/models/options/#unique-together

Hi @cfarfan, @bmihelac is right, you should be getting a database error. Anyway, try setting the import_id_fields option in the resource to your unique_together fields, and see if it helps. See here: https://django-import-export.readthedocs.org/en/latest/getting_started.html#customize-resource-options

in case anyone is looking into using the unique_together fields as the primary key implicitly while keeping a numeric primary key, one needs to set unique_together at the database level as well as exclude=('id', ) to disengage the actual primary key from the identification process.
Basically, the import workflow identifies the candidate hit in the database through import_id_fields, cache the candidate as original, then overwrite the specified fields using values from xls and save as a new object. So if the 'id' attribute is included, it gets overwritten and causes an IntegrityError when the new object is saved for violating the unique_together field. But if 'id' field has been excluded, then the new object is saved with the old 'id' un-touched.
Therefore it is necessary to exclude ('id',) here, by modifying the Resource as
class FulfillmentResource(resources.ModelResource):
    company = fields.Field(column_name='company', attribute='company',widget=widgets.ForeignKeyWidget(Company,'name') )
    country = fields.Field(column_name='country', attribute='country',widget=widgets.ForeignKeyWidget(Country,'name') )
    class Meta:
        model = Fulfillment
        exclude = ('id',)
        import_id_fields = ('company','country','year', 'month')
        #fields = ('company','country','year','month','percentage')
        #export_order = ('company','country','year','month','percentage')


Make fetching related images on the client non-blocking

Fixes

Related to #1516 by @obulat
Description

The comment from @sarayourfriend in #1516 made me realize how to improve the loading of the single result pages so that they fully loa on SSR, but also do not block on the related media fetch call when being rendered client-side:
Awaiting the related media request on the server makes sure that the server-rendered page has the related media.
Not awaiting the related media request on the client makes the other parts of the page load quickly, and we can render a loading icon while fetching the related media.
Testing Instructions

Try opening the single detail page for images directly, and from the search page. It should load the related items when opened directly, but on client-side, it should open the page and show a loading icon for the related images until they are fetched.
Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the default branch of the repository (main) or a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

LGTM! In the future we should upgrade our image grids to use the skeleton components that @krysal made—we're currently only using them on the 'all' and 'audio' results and it'd be nice to build it into the VImageGrid.

I'll make an issue for that!

Did you see if you were able to remove the .then(() => Promise.resolve())? That was only necessary due to an IDE warning, right?

I can remove the IDE warning if I add the catch, empty then is not necessary :)

Also—do we need error handling on the server side for the related images? Have we tested what happens if they fail in SSR?

I added the error handling, thank you for catching it!


Not able to catch exception in Xcode 9.4 and swift 4

Hi,
I am using the code to handle swift exception but unfortunately its not woking.
Here is the code i am trying.
var array = [String] ();
SwiftTryCatch.try({
var val = array[40]
}, catch: { (error) in
// code to handle exception
print("in catch")
}, finallyRun: {
// code to do any way
print("in finally")
})
Its just crashing on line var val = array[40] and not catch the exception in catch clause
Can anyone help me please?

any ideal? same problem here, exception belong to runtime exception can not catched

This is a Swift runtime crash rather than a thrown Objective-C exception. I don't believe this project can be used how you're using it.


Installing the plugin in HeadlessMode

How is it possible to install the plugin in the Headless Mode - meaning without the use of GUI for the installation?

How is it possible to install the plugin in the Headless Mode - meaning without the use of GUI for the installation?

I'm not 100% sure. I did recently make changes to allow it to work in headless mode though so it should be possible. Try extracting the plugin to the extensions folder. Either of the two locations should work {ghidra_root}/Ghidra/Extensions or the .ghidra/{ghidra_version}/Extensions. Paths are not fully accurate since this response came from my phone.

I tried it both in Unix and Windows and it doesn't work. it looks like the installation is partial - I am able to call:
from cppclassanalyzer.utils import CppClassAnalyzerUtils
but
CppClassAnalyzerUtils.getManager(currentProgram)
Returns None.
Only if installing through the GUI, and through the dialog prompted by Ghidra:

"New extension plugins detected. Would you like to configure them?"

it is fully installed.
I did it at 2.5 tag.

As a sanity check, what does ghidra.util.SystemUtilities.isInHeadlessMode() return? Here is the relevant code for getting the manager which depends on said result:
https://github.com/astrelsky/Ghidra-Cpp-Class-Analyzer/blob/c712bc1f46ac59582e546d451b1afe0cccca15c6/src/main/java/cppclassanalyzer/utils/CppClassAnalyzerUtils.java#L139-L147

Yes, it returns True.

Yes, it returns True.

This shouldn't be possible then. You confirmed that you are able to retrieve a manager for the same program in the GUI but not in headless mode? The only way for it to return null is if no RttiManagerProvider supports the program.

I suggest the following scenario to reproduce the issue (Windows machine):

Download and extract a fresh copy of Ghidra.
Rename .ghidra to .ghidra_bup
Copy the plugin to <ghidra_home>\Ghidra\Extensions
Create the following script file:

from cppclassanalyzer.utils import CppClassAnalyzerUtils

CppClassAnalyzerUtils.getManager(currentProgram).getTypeCount()

Save the file in \script.py
Run the following from the command line:
<ghidra_home>\support\analyzeHeadless <home> myproject -import <path_to_any_file>  -overwrite  -postscript <home>\script.py
You will see in the console output:

Traceback (most recent call last):
  File <home>\script.py, line 14, in <module>
    CppClassAnalyzerUtils.getManager(currentProgram).getTypeCount()
AttributeError: 'NoneType' object has no attribute 'getTypeCount'

If I install it once from the GUI - it will work afterward from the Headless mode too. But without GUI it never works.

I will take a look tonight to see what is going on. This shouldn't be occurring.


Chained HOC

This should pass...

@villesau Do you have any ideas how to make this pass?
The issue is that whenever we chain multiple higher-order components together we're losing information regarding required props i.e. You can omit them and Flow won't pick-up on it. So I've added a test that intentionally omits requiredProp and added $ExpectError, but Flow doesn't  error, as expected.
This demonstration is with respect to @material-ui/core (withStyles & withTheme) as it makes sense to chain these methods. However, @jmtoung has created a thorough repository reproducing this issue when chaining withStyles against react-redux's connect (https://github.com/jmtoung/flow-hoc-issue).
I've tried to use the same HOC pattern as you've done with react-redux's libdefs, however it's very possible I've messed up. If you have any ideas how we could address this, that would be hugely appreciated.

@cesardeazevedo re: https://github.com/flow-typed/flow-typed/pull/2632#discussion_r212813677
I just had a crack at swapping $ElementConfig<Component> out for $ElementConfig<$Supertype<Component>> but once I do I get a lot of other errors elsewhere. It may well be that other flow types are messed up, but issues were being silently ignored.
When I get some more time I'll come back to this, however if anyone else has time to take a look and make this test pass then that would be fantastic.

Hi @Benjamin-Dobell, i made it pass. 🎉
I wrapped both $ElementConfig<Component> with $ElementConfig<$Supertype<Component>>, and i started getting new errors as you said, i started investigating the errors and i realized that the classes and theme props on tests was defined  by {}, which flow wasn't be able to inferred.
So i think all these new errors that $Supertype just shown was likely to be correct, so i changed all references of {classes: {}, theme: {}} to {classes: *, theme: *}, and lots of errors disappear, with only a few remaining related to the injection of the prop types.
Looking at your code you are defining the injection props as follows.
  declare export type WithStyles = {
    classes: { +[string]: string },
    innerRef: React$Ref<React$ElementType> | {current: null | React$ElementRef<React$ElementType>}
  };

And since the injected props are been diffed with $Diff<React$ElementConfig<$Supertype<WrappedComponent>>, WithStyles>
the $Diff<A, B> function will throw a error if you try to remove a property defined in B that doesn't exists in A.
This is what the docs says regarding injecting props with a high order component
(https://flow.org/en/docs/react/hoc/#toc-injecting-props-with-a-higher-order-component)

Note: If foo does not exist in Props you will get an error! $Diff<{}, { foo: number }> will be an error. To work around this use a union with void, see: $Diff<{}, { foo: number | void }>. An optional prop will not completely remove foo. $Diff<{ foo: number }, { foo?: number }> is { foo?: number } instead of {}.

I changed the injected properties to be unied with a void as follows
  declare export type WithStyles = {
    classes: void | { +[string]: string },
    innerRef: void | React$Ref<React$ElementType> | {current: null | React$ElementRef<React$ElementType>}
  };

And everything passed. 🎉

@cesardeazevedo Nice work!
If you'd like, feel free to submit a PR either here (chained-hoc branch) or directly to flow-typed. Otherwise, I'll happily set about recreating the changes.

Unfortunately, I've found the void |  approach doesn't really do what we want in real-world apps, as every time you access this.props.classes you have to check that it's non-void, when in reality it can never be null. 😞
I've updated the tests demonstrating the problem.

I'm presently trying something like:
  declare export type WithStyles = {|
    classes: { +[string]: string },
    innerRef: React$Ref<React$ElementType> | {current: null | React$ElementRef<React$ElementType>}
  |};

  declare type WithStylesHOC = {|
    classes: void | { +[string]: string },
    innerRef: void | React$Ref<React$ElementType> | {current: null | React$ElementRef<React$ElementType>}
  |};

  declare module.exports: (
    stylesOrCreator: StyleRules | StyleRulesCallback,
    options?: WithStylesOptions,
  ) => <WrappedComponent: React$ComponentType<*>>(
    Component: WrappedComponent
  ) => React$ComponentType<$Diff<React$ElementConfig<$Supertype<WrappedComponent>>, WithStylesHOC>>;

To work around the issue, but running into more issues 😞

Ideally WithStyles and WithTheme should be exported as they are in material-ui's official TypeScript types. They were also exported in the past directly from the material-ui project (pre 1.0) when the maintained Flow types within the project.
However, I agree with the sentiment with respect to not exporting the types containing void |, and simply using them internally. That's why in my comment above I mentioned I was attempting to use WithStylesHOC internally, but exporting WithStyles (without the void |) types.
To my surprise, I'm having trouble getting that working. It's something to do with innerRef, because if I omit it from WithStyles and WithThemes it works 😕 I don't know if anyone our there actually uses innerRef anyway, so I can probably omit it. However, I'd love to understand why it's not working.

...and as I write that. I work it out.


CMake: Make unit test optional & nv2a_vsh_emulator public for external project usage

Not everyone will be using unit test projects from external project. It is recommended to add an option function to turn off unit tests for allow use libraries' project usage directly. With this change, some of us from cxbxr team don't need to install boost library.
Due to difference of PRIVATE and PUBLIC for include directories command. We need nv2a_vsh_emulator library set to PUBLIC in order allow other targets such as cxbxr to use include ability for compile process.

Thanks!


Speech unit tests cleanup.

Some test cleanup that was missed or not relevant on the #2663 PR.

Still LGTM

@dhermes I had to update this since GAPICSpeechAPI needs proper credentials.
Just saw your LGTM. Just waiting on Travis.

@dhermes, these were the last changes I made before squashing.


Error msg when starting nvim

I see this at startup of nvim.
[mason-lspconfig.nvim] failed to install nil_ls. Installation logs are available in :Mason and :MasonLog

When I go  :MasonLog I see
[INFO  Sun 23 Jul 2023 02:01:23 AM EDT] ...e/nvim/lazy/mason.nvim/lua/mason-core/installer/init.lua:184: Executing installer for Package(name=nil) {}
[ERROR Sun 23 Jul 2023 02:01:38 AM EDT] ...e/nvim/lazy/mason.nvim/lua/mason-core/installer/init.lua:249: Installation failed for Package(name=nil) error=spawn: cargo failed with exit code 101 and signal 0.

Running nvim on Ubuntu 22.04
nvim --version
NVIM v0.10.0-dev
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Run "nvim -V1 -v" for more info

The install failed because nix command was not available.

Hi @aphsa, thanks for your feedback. I have to figure out a way to distinguish "sane defaults" and additional (user) configuration.


C#: Minor updates for consistency (SD-2778)

This PR updates a few queries/query help files for consistency.
These changes were prompted by the change in how we will upload qhelp to the wiki for 1.19.

@tom - apologies. I hadn't noticed that this had a test failure. It should now be fixed.


Failed to run outputted code

As title says, at the end the program fails to run. Error attached -

It seems like generated unix shell command under Windows OS. I think it could be improved.

If you wish to reopen the issue please do following the new issue template.


Enable passing tests

Enabled PyTests that are now passing and labeled some still failing tests with links to their issues

Codecov Report

:exclamation: No coverage uploaded for pull request base (datafusion-sql-planner@7030909). Click here to learn what that means.
The diff coverage is n/a.

@@                    Coverage Diff                    @@
##             datafusion-sql-planner     #539   +/-   ##
=========================================================
  Coverage                          ?   55.58%
=========================================================
  Files                             ?       70
  Lines                             ?     3456
  Branches                          ?      693
=========================================================
  Hits                              ?     1921
  Misses                            ?     1409
  Partials                          ?      126

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Splitting the LICENSE file?

Hi Glob folk,
I'm a part of the Open Source Program Office at AWS and wanted to let you know of a licensing painpoint. When pulling down updated npm packages, the glob package, and packages that include glob, always raise an eyebrow because of the CC-BY-SA license for the logo being mentioned. CC-BY-SA is a curious license for software, thus I get alerts to review. It's the more frustrating because the logo isn't included in the npm package file :)
I thought I'd share this because it's very unique to this project. "Oh, it's the glob text" might be something I mutter on a whole bunch of import-alerts :) I don't expect you to rate my pain highly, frankly the logo is awesome and it's great that it's being called out. But I did wonder if the license of the logo could move out into a separate LOGO-LICENSE file, which then isn't included in the npm package?
Apologies if this is too selfish a suggestion.

Would it solve your problem if the CC-BY-SA was called out in the README.md but not in the license file?  Since it's not distributed with the code on npm, that seems like it'd be fine.  Though, I guess it is distributed with the code via GitHub.  @tanyabrassie you own the copyright on that little guy, what's your thoughts?

Hello glob people!
Another friendly AWS dev here - I'm unrelated to the team that validates licensing at AWS but I am a consumer of packages that consume glob as a dependency. For some more context, we have automated (and non-automated) systems that review open source licensing to make sure that we're in compliance, and because they're unusual for software, the Creative Commons licenses require manual review. Other packages (for example, @vercel/ncc) are bundling glob's LICENSE file in their distribution, which is flagging the licensing exception - as well as any AWS package that includes glob as a first level dependency.
I've created a simple PR (#463) that removes the information from the LICENSE file. Please let me know if this isn't appropriate.

Thank you @isaacs and @tanyabrassie for being so understanding :)


Stable Diffusion - Image generation Tool

This has been implemented and can be found in the ToolKit Marketplace.


Comment out year.name until updated info is added

PROD:

DEV:

 Arthur Ashe wrong year showing on top of the page.


1.6 - Talent ranks not being properly set

It looks like talents are multiplying instead of increasing the rank.
Here's a picture where I dragged the talent adversary over to a character twice, which resulted in a console-reported rank of 1 (and a sheet-reported rank of 2). I then manually updated one of the talents to be rank 2 (to test my own module properly reading the talents as part of 0.8.x compatibility)

Reproduction steps:
Add any ranked talent (I used adversary) to a character more than once, then, using the API, read the current rank. It should read >1, and it does read 1.

You currently have 2 copies of a single talent, one at rank 1 and one at rank 2 adding up to a total of 3. That seems to be working correctly to me. When I tested the tier changed when the ranked was changed when there was more than one copy of a talent. That seems like an issue to me.

Ah, my bad. I thought it properly blocked duplicates since there is a rank attribute on each item. I'll close this out.


[feature] ability to create cloud sql database

So, I'm trying to use the CLI tool to create a database on Google Cloud SQL and it is failing because set session_replication_role = 'replica'; is only available to superusers and GCSQL doesn't allow any commands that require superusers. Lovely. Can you make it a flag to turn it off?
mikro-orm schema:create -r --fk-checks=false
Warning, FIREBASE_CONFIG and GCLOUD_PROJECT environment variables are missing. Initializing firebase-admin will fail
mikro-orm schema:create

Create database schema based on current metadata

Options:
  -r, --run      Runs queries                                          [boolean]
  -d, --dump     Dumps all queries to console                          [boolean]
  --fk-checks    Do not skip foreign key checks                        [boolean]
  -v, --version  Show version number                                   [boolean]
  -h, --help     Show help                                             [boolean]

error: permission denied to set parameter "session_replication_role"
    at Connection.parseE (/functions/node_modules/pg/lib/connection.js:604:11)
    at Connection.parseMessage (/functions/node_modules/pg/lib/connection.js:401:19)
    at Socket.<anonymous> (/functions/node_modules/pg/lib/connection.js:121:22)
    at Socket.emit (events.js:209:13)
    at Socket.EventEmitter.emit (domain.js:476:20)
    at addChunk (_stream_readable.js:305:12)
    at readableAddChunk (_stream_readable.js:286:11)
    at Socket.Readable.push (_stream_readable.js:220:10)
    at TCP.onStreamRead (internal/stream_base_commons.js:182:23) {
  name: 'error',
  length: 121,
  severity: 'ERROR',
  code: '42501',
  detail: undefined,
  hint: undefined,
  position: undefined,
  internalPosition: undefined,
  internalQuery: undefined,
  where: undefined,
  schema: undefined,
  table: undefined,
  column: undefined,
  dataType: undefined,
  constraint: undefined,
  file: 'guc.c',
  line: '6329',
  routine: 'set_config_option'
}

Use just --fk-checks, true means that those statements won't be there (fk checks are allowed), false (default) means all queries will be wrapped between those FK statements.

Oh, I had it inverse. Started reading through the code but got distracted by dinner. =) Thanks man!

@B4nan Is there a way to do this using SchemaGenerator programmatically?

https://mikro-orm.io/docs/schema-generator#using-schemagenerator-programmatically

@B4nan Thanks for the quick response, but I meant using the --fk-checks. I'm using Google SQL too and I'm having the same issue with set session_replication_role = 'replica';

There is a wrap parameter, pass false there to omit those session_replication_role queries. I think I will change the default, it should be no longer needed as we now use the CommitOrderCalculator to get the right order of entities in schema generator too.

That did it, thank you!

@B4nan Sorry to bother you again, is this possible for Migrator too? When running migrator.up() I'm getting the same error and I can't seem to find the same wrap parameter. I'm new to TS so I might not be looking in the right places

Nevermind I got it!
migrations: { path: ORM_MIGRATIONS_PATH,         disableForeignKeys: false}

Got the same error this morning, running migrations via migration.up() on Heroku PostgresQL.
Fixed by disableForeignKeys: false as mentioned by @MehdiHamidi :)

I've run the example on this repo:https://github.com/driescroons/mikro-orm-graphql-example/issues/3#issue-744600923 and I'm still getting this. I am on pg 13. Any ideas would be greatly appreciated. Thank you.

Nevermind I got it!
migrations: { path: ORM_MIGRATIONS_PATH, disableForeignKeys: false}

@MehdiHamidi This worked for me! Do you mind explaining how this fixes the issue?

I don't understand. But it worked for me.

I imagine that what I am going to explain now, does not apply to production environments where there are some limitations, however, I am going to comment it in case it happens to someone during development (as it was my case) and it helps to solve it. <3
Had the same problem when trying to create a second DB in my main DB Docker container (until now I was starting a separate new container, exclusively for tests).
Then, I encountered this error during the process of running migrations and after some internet searches, run the statement:
GRANT SET ON PARAMETER session_replication_role TO <username>;

Stopped giving the error!!!


Segmentation violation when running ddev list with invalid entry in global_config.yaml

Describe the bug
I somehow had an invalid entry in the global_config.yaml similar to this one:
project_info:
  Test:
    approot: ""

Running ddev list in my home directory caused a panic:
$ ddev list
unable to create project at project root : ddev config is not useful in your home directory (/home/XXX)
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x9e9af9]

goroutine 1 [running]:
github.com/drud/ddev/pkg/ddevapp.GetProjects(0xbfcb9659b19b2800, 0x2190f1c, 0x11952a0, 0xc89a3d, 0x9, 0xcdc178)
	/workdir/pkg/ddevapp/utils.go:355 +0x619
github.com/drud/ddev/pkg/ddevapp.List(0x0, 0x1)
	/workdir/pkg/ddevapp/ddevapp.go:123 +0xa5
github.com/drud/ddev/cmd/ddev/cmd.glob..func26(0x1188cc0, 0x11c6870, 0x0, 0x0)
	/workdir/cmd/ddev/cmd/list.go:26 +0x45
github.com/spf13/cobra.(*Command).execute(0x1188cc0, 0x11c6870, 0x0, 0x0, 0x1188cc0, 0x11c6870)
	/workdir/vendor/github.com/spf13/cobra/command.go:846 +0x2c2
github.com/spf13/cobra.(*Command).ExecuteC(0x1189f20, 0x5f4de1e6, 0x319a241d, 0xc22ad2c278)
	/workdir/vendor/github.com/spf13/cobra/command.go:950 +0x375
github.com/spf13/cobra.(*Command).Execute(...)
	/workdir/vendor/github.com/spf13/cobra/command.go:887
github.com/drud/ddev/cmd/ddev/cmd.Execute()
	/workdir/cmd/ddev/cmd/root.go:153 +0x3c
main.main()
	/workdir/cmd/ddev/main.go:21 +0xf4

To Reproduce

Create an (additional) project entry with an empty approot in the global_config.yaml
Start Terminal in home directory
Run ddev list
See error

Expected behavior
The list of all projects should be shown (and ddev config should not be called).
Additionally it might be good to notify the user on the invalid entry and give an option to delete it or just delete the entry and notify the user that it was deleted?
I did not add this entry manually, so it is possible that this entry is generated by ddev also this should be prevented.
Version and configuration information (please complete the following information):

Host computer OS and Version: Ubuntu 20.04.1
DDEV-Local version	v1.16.0-alpha2

Additional context
Trying to delete the entry with ddev stop --unlist Test does not work (also causes a segmentation violation).

Thanks for this report - with this good detail it ought to be solvable.


error on importing plugin

hexchat 2.14
Traceback (most recent call last):    File "/home/xxx/.config/hexchat/addons/emojis/emojis.py", line 3, in <module>      from . import db  ImportError: cannot import name 'db'  Error loading module /home/xxx.config/hexchat/addons/emojis/emojis.py

I'm not able to reproduce this error.
You need to reinstall emojis or upgrade your Python to 3.x.

If you don't know how to report an issue I can't do anything about it.
Closing this as there's no data to debug and or back that this is a real issue.


Extract CSS

The bundle should not be responsible to inject the CSS, we should extract it and publish it as a separate file, the consumer can choose how to bundle it.
This will be a breaking change

Closed by https://github.com/obartra/reflex/pull/172


Cleanly shutdown IM engine

Problem
The InteractionModelEngine is not cleanly clearing up mpFabricTable and mpExchangeMgr today on Shutdown. Doing so invites a world of problems in the SDK:

ReadClient continues to depend on those members being non-null in its destruction due to its call into in the IM engine in ReadClient::CancelLivenessCheckTimer. This is not a problem in and of itself, but it does alter the paradigm that ReadClient instances can continue to exist well-past IM engine shutdown, which is implied here in InteractionModelEngine::Shutdown:

    //
    // We hold weak references to ReadClient objects. The application ultimately
    // actually owns them, so it's on them to eventually shut them down and free them
    // up.
    //
    // However, we should null out their pointers back to us at the very least so that
    // at destruction time, they won't attempt to reach back here to remove themselves
    // from this list.
    //

We need to fix this, and consequently, fix the various tests that depend on this premise.

Lots of test (TestReadInteraction and TestWriteInteraction) manually Init and Shutdown the engine repeatedly in their tests. At the end of the test, the AppContext does a second Shutdown of the engine as well, which causes problems since Shutdown today is not meant to be called multiple times.

FYI @bzbarsky-apple @yunhanw-google


It has different ways of expression when click the select between win10 and macOs

Bug Report or Feature Request (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request

Area
- [ ] devkit
- [ ] schematics

Versions

Repro steps

This is the repository source https://github.com/simonchenxy/angular4-Pagination
1). Please get the code from above link.
2). npm install and npm start.
The log given by the failure

Desired functionality

Mention any other details that might be useful

It has different ways of expression when run it on Win 10 and macOs(Sierra).
I bind a click function 'getCurrentCount()' on select label in 'src/app/pagination/pagination.component.html'.
This function can success when I click the select on Chrome of Win 10.
But it failed on Chrome of macOs(Sierra), because it seems like this function doesn't emit the parameter to father component or maybe it work when the select blur.

Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on StackOverflow using tag angular-cli.
If you are wondering why we don't resolve support issues via the issue tracker, please check out this explanation.


Use Travis-CI and Appveyor for CI

Change the test/development expectations in preparation for adding to conda-forge.

Changes Unknown when pulling 4afbe38a1409098784f543edfa819d21a7f46328 on travis-appveyor into ** on master**.

appveyor fails appear to be temporary network issues... we'll go ahead and merge this.


runOn folderOpen option does not work

Version: 1.42.0
Commit: ae08d5460b5a45169385ff3fd44208f431992451
Date: 2020-02-06T10:51:23.649Z
Electron: 6.1.6
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Linux x64 5.3.0-29-generic
Version: 1.43.0-insider
Commit: beaf391bc53136912e4f0bbdfb7844ad954247db
Date: 2020-02-07T05:34:00.212Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Linux x64 5.3.0-29-generic
Steps to Reproduce:
1.I wrote tasks.json with folderOpen option.
{
  // See https://go.microsoft.com/fwlink/?LinkId=733558
  // for the documentation about the tasks.json format
  "version": "2.0.0",
  "tasks": [
    {
     "label": "webpack build (watch)",
      "command": [
        "${workspaceFolder}/node_modules/.bin/webpack -w"
      ],
      "type": "shell",
      "problemMatcher": [
        "$tsc"
      ],
      "isBackground": true,
      "runOptions": {
        "runOn": "folderOpen",
      }
    },
]

2.Execute Reload Window
But, task does not work anywhere.
The "runOn": "folderOpen" option thought that the task would be executed automatically when opening VSCode. However, the task has not been performed.
Is the intent of this option different?

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

This is resolved to execute Manage Automatic Tasks in Folder command.


libselinux does not build with pkgsMusl

Describe the bug
pkgsMusl.libselinux does not build because of:
builder for '/nix/store/bw1k61ngsnhqa9lz2rvrk0y05rka0pkf-libselinux-3.0.drv' failed with exit code 2; last 10 log lines:
  procattr.c:38:14: error: static declaration of ‘gettid’ follows non-static declaration
     38 | static pid_t gettid(void)
        |              ^~~~~~
  In file included from procattr.c:2:
  /nix/store/k515dcqzlwncg8flh97l9dq3vwxn7jvl-musl-1.2.2-dev/include/unistd.h:194:7: note: previous declaration of ‘gettid’ was here
    194 | pid_t gettid(void);
        |       ^~~~~~
  make[1]: *** [Makefile:158: procattr.o] Error 1
  make[1]: Leaving directory '/build/libselinux-3.0/src'
  make: *** [Makefile:44: all] Error 1
[0 built (1 failed)]
error: build of '/nix/store/bw1k61ngsnhqa9lz2rvrk0y05rka0pkf-libselinux-3.0.drv' failed

To Reproduce
Steps to reproduce the behavior:

nix repl
:l https://github.com/NixOS/nixpkgs/archive/6802c2e2ce9ef37976a306ada908e121409093ad.tar.gz
:b pkgsMusl.libselinux

Expected behavior
The library is built
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Notify maintainers

@Phreedom
Metadata

system: "x86_64-linux"
host os: Linux 5.4.108, NixOS, 20.09.3777.ad7604ddbd9 (Nightingale)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.10
channels(kpg): ""
channels(root): "nixos-20.09.3777.ad7604ddbd9"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

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

fixed in fc141a889d05b05719f6b70f617cc500beea3c38

*fixed on staging, but master is still broken


Cannot get names + values from term of type AnyNamedTuple

Given a term of type AnyNamedTuple, I would like to be able to extract the names and values as tuple terms.
Compiler version
3.5.0-RC1-bin-SNAPSHOT
Minimized code

import NamedTuple.AnyNamedTuple
def getValues(t: AnyNamedTuple) = t.toTuple // current workaround: NamedTuple.toTuple(p.$a.asInstanceOf[NamedTuple[Tuple, Tuple]]).toTuple
def getNames(t: AnyNamedTuple) = compiletime.constValue[NamedTuple.Names[t.type]] // I wouldn't necessarily expect this to work but I don't know what else would be correct

Output
[error] 6 |def getValues(t: AnyNamedTuple) = t.toTuple
[error]   |                            ^^^^^^^^^
[error]   |        value toTuple is not a member of NamedTuple.AnyNamedTuple.
[error]   |        An extension method was tried, but could not be fully constructed:
[error]   |
[error]   |            NamedTuple.toTuple[N, V](t)

and
[error] 8 |def getNames(t: AnyNamedTuple) = compiletime.constValue[NamedTuple.Names[t.type]]
[error]   |                                                        ^^^^^^^^^^^^^^^^^^^^^^^^
[error]   |NamedTupleDecomposition.Names[(t : NamedTuple.AnyNamedTuple)] is not a constant type; cannot take constValue
[error]   |
[error]   |Note: a match type could not be fully reduced:
[error]   |
[error]   |  trying to reduce  NamedTupleDecomposition.Names[(t : NamedTuple.AnyNamedTuple)]
[error]   |  failed since selector (t : NamedTuple.AnyNamedTuple)
[error]   |  does not match  case NamedTuple.NamedTuple[n, _] => n
[error]   |  and cannot be shown to be disjoint from it either.

Expectation
There are many cases where we need to extract the names and values from a term that is a subtype of AnyNamedTuple. I would potentially even expect a helper method ala toTuple like toNames that would reify the names into a term.
I'm not sure if names vs. values should be separate tickets, but both issues stem from the way that AnyNamedTuple is defined.

Likely obvious, but the minimised snippet needs the NamedTuple.AnyNamedTuple import.
import NamedTuple.AnyNamedTuple
def getValues(t: AnyNamedTuple) = t.toTuple // current workaround: NamedTuple.toTuple(p.$a.asInstanceOf[NamedTuple[Tuple, Tuple]]).toTuple
def getNames(t: AnyNamedTuple) = compiletime.constValue[NamedTuple.Names[t.type]] // I wouldn't necessarily expect this to work but I don't know what else would be correct

Thanks, sorry I have added it now

should we add some kind of type class that can recover the type to NamedTuple[N,T]?
import NamedTuple.{AnyNamedTuple, NamedTuple}

trait AsNamedTuple[T]:
  type Names <: Tuple
  type Values <: Tuple
  extension (t: T) def repr: NamedTuple[Names, Values]
object AsNamedTuple:
  given [N <: Tuple, T <: Tuple, R <: NamedTuple[N, T]]
    : (AsNamedTuple[R] { type Names = N; type Values = T} ) =
    new AsNamedTuple[R]:
      type Names = N; type Values = T
      extension (t: R) def repr: NamedTuple[Names, Values] = t

then the methods in the original can be adapted as follows:
inline def getValues[T <: AnyNamedTuple: AsNamedTuple](t: T) =
  t.repr.toTuple
inline def getNames[T <: AnyNamedTuple](t: T)(using ant: AsNamedTuple[T]) =
  compiletime.constValueTuple[ant.Names]

and some examples:
scala> getValues((x = 23, y = 47))
val res3: (Int, Int) = (23,47)

scala> getNames((x = 23, y = 47))
val res4: ("x", "y") = (x,y)

Alternatively we also define extensions on AnyNamedTuple, but I wonder if there would be ambiguity

Quick summary of the discussion: we can't redefine AnyNamedTuple as NamedTuple[Any, Any] because the variance, but we could potentially define extensions on AnyNamedTuple, or we could just parameterize with [N, T] wherever AnyNamedTuple is used and replace it with NamedTuple[N, T], but I also like @bishabosha solution a lot. The conclusion was to not make changes just yet but see if the request comes up again and then reconsider.


--explain ?

Or maybe we could just do " ".join(message[1:]), so !a ... message would have an explain of message

Forgot to close!


layout.size and layout.align - both methods not found

Hi - thanks for the really informative series - awesome work - thanks!!!
However (there had to be a however...)
when building post 11 allocator/linked_list.rs, I am getting these errors - both from my repository, and the same when I cloned yours:
error[E0599]: no method named `size` found for type `core::result::Result<core::alloc::Layout, core::alloc::LayoutErr>` in the current scope
   --> src/allocator/linked_list.rs:116:27
    |
116 |         let size = layout.size().max(mem::size_of::<ListNode>());
    |                           ^^^^ method not found in `core::result::Result<core::alloc::Layout, core::alloc::LayoutErr>`

error[E0599]: no method named `align` found for type `core::result::Result<core::alloc::Layout, core::alloc::LayoutErr>` in the current scope
   --> src/allocator/linked_list.rs:117:23
    |
117 |         (size, layout.align())
    |                       ^^^^^ method not found in `core::result::Result<core::alloc::Layout, core::alloc::LayoutErr>`

error: aborting due to 2 previous errors

I had another error yesterday where linked_list_allocator 0.6.6 broke things, so I had to explicitly specify version 0.6.5 to get things to compile, but I'm a bit lost on this one...
As I said I get the same errors with your code and mine...
hope you have some idea what might be going wrong?
Cheers,
Tim.

I think I had the same problem last week.
As @phil-opp pointed it out to me, the nightly is unstable prone to changes.
Try to update your toolchain to see if it solves the problem.
The command for that is rustup update, or something like similar.
Hope it helps !

@AntoineSebert - thanks for the tip, I thought I had already tried this, however this morning, the previous errors are gone, to be replaced with this:
error[E0432]: unresolved import `alloc::alloc::Alloc`
  --> /home/timc/.cargo/registry/src/github.com-1ecc6299db9ec823/linked_list_allocator-0.6.4/src/lib.rs:14:20
   |
14 | use alloc::alloc::{Alloc, AllocErr, Layout};
   |                    ^^^^^
   |                    |
   |                    no `Alloc` in `alloc`
   |                    help: a similar name exists in the module: `alloc`

error: aborting due to previous error

I get this with my own and @phil-opp   code (as before)...
Any more ideas?

Alloc recently got renamed to AllocRef.

OK - I seem to have fixed it - I put this in my Cargo.toml:
linked_list_allocator = "=0.6.6"
(even though linked_list_allocator 0.6.6 was giving errors a few days ago)...
and now the code compiles...

closing

issue was "fixed"

@tcaudrey Good to hear that you got it working! The breakage in this case was caused directly by Rust, so there was no way to avoid it in the libraries unfortunately.


Inspect command wip

Don't even review this seriously yet. The code is quite horrible. I will fix it up, add tests, etc soon. Pushing early version since it kind of works.
FYI @zregvart I copy/pasted quite a lot from your npm module.

Example usage:
$ go run main.go inspect-policy --source github.com/hacbs-contract/ec-policies/policy --work-dir -o yaml | head
github.com/hacbs-contract/ec-policies/policy:
- annotations:
    custom:
      failure_msg: Unexpected kind '%s'
      short_name: unexpected_kind
    description: A sanity check to confirm the input data has the kind "Pipeline"
    scope: rule
    title: Input data has unexpected kind
  location:
    col: 1

Thanks Zoran. I didn't go through your suggestions yet, will do that soon.

I'm still being lazy about the tests, but I think I'll pull it out of draft. Recent changes:

Move the "inspect output to text" code to its own package (internal/rego_text).
Remove the yaml output option since json is fine, and I was having trouble making it work as I wanted. Also you can use yq -P very easily.
Simplify the command flags based on Zoran's suggestion
Remove the commit about storing the dest dir for each policy source url.
Misc tweaks.

have an intermediate struct/array in opa_inspect

I think it's probably a good idea, but I think it can be done in future. Once we try to integrate this data with the ec validate it might be more clear what is needed.

FYI, go prescribes a somewhat unique way to name packages: https://go.dev/blog/package-names
Something like opa_inspect could be called just opa. This makes the usage side of things a bit nicer: opa.InspectDir.

FYI, go prescribes a somewhat unique way to name packages: https://go.dev/blog/package-names
Something like opa_inspect could be called just opa. This makes the usage side of things a bit nicer: opa.InspectDir.

Thanks. I did move things around a little based on that:
internal/opa/inspect.go
internal/opa/output.go


Redesign Execute Page UI

Redesign Execute Page UI
Description
Completely redesigned Execute Page
Features:

static sidebar: contains connection info, database switcher, procedure switcher, and execute area
main content: divided into three tabs (rule groups, unit tests, results)
Rule groups / unit tests: "add" button to add, each added quantity will appear in a black box (scrolls if overflowing). expandable quantities are in accordions
Delete entries with trash icon
Add Rule Group Form: name, procedure in disabled input, procedure parameters
Add Unit Test Form: name, table -> select level -> fill out remaining conditional fields
Error checking in both forms

Code Niceties:

custom hook for modals (useModal) which provides isOpen / toggle
helper function to create connection string

TO BE DONE:

Add unit tests to rule groups
Edit rule groups/unit tests that have been added (stretch goal)
Remove conditionList variable from execute as only rules should know about their unit tests
Save created tests / rules to backend
Fix logic for executing - it's still very much hard coded

Link to the issue you are closing
Fixes #169
Screenshot or other testing that you have completed
https://user-images.githubusercontent.com/29695042/199619732-04cd036c-4e45-4470-9704-9945d0f13612.mp4
Checklist:

[x] ESLint passes
[x] Prettier passes
[x] Included comments where necessary
[ ] Updated README if needed
[x] Verified that code runs and generates no errors/warnings

Looks good to me, maybe we could change test level to be test type instead, I think it might make more sense


schema.description in ISchemaFilter seems not work

    public void Apply(Schema schema, SchemaRegistry schemaRegistry, Type type)
    {
        schema.example = new Login
        {
            Username = "root",
            Password = "password",
            RememberMe = false
        };
        schema.description = "To authenticate a given username and password, use this model";
    }

schema.example work great but schema.description not :(
XML comment  blahblah can resolve the problem but i prefer to declare the description in my SchemaFilter...
Regards,

I think this is an ordering issue. This is a little obscure I know, but in your SwaggerConfig, you'll need to ensure that your custom Schema and Operation filters are called after the call to IncludeXmlComments.
This is because under the hood, IncludeXmlComments simply wires up Schema and Operation filters to extract Xml comments and apply them. In your case, I have a feeling that your schema filter is executing before the built-in Xml filters, and so ends up getting overwritten

Closing due to inactivity - feel free to re-open if you have more info on this issue

I'm running into this issue. I'm not sure what to try next.
I believe by "ensure that your custom Schema and Operation filters are called after the call to IncludeXmlComments", you mean:
services.AddSwaggerGen(c =>
{
    ...
    c.IncludeXmlComments(assemblyXML);
    ...
    c.SchemaFilter<MySchemaFilter>();
    ...
}

I'm doing that, but changing the order makes no difference.
MySchemaFilter always runs, but the schema.Description is blank at the beginning of public void Apply(Schema schema, SchemaFilterContext context), as if it is running first. Other properties are already set though. If i remove the c.IncludeXmlComments(assemblyXML); my schema filter descriptions shows up. c.MapType appears to work fine.
But, if I'm reading the source code right. It shouldn't matter anymore.
https://github.com/domaindrivendev/Swashbuckle.AspNetCore/blob/395053f49bcc63904a73f931314824574543b0a4/src/Swashbuckle.AspNetCore.SwaggerGen/Application/SwaggerGenOptions.cs#L235
// filters AND so they can share the same XPathDocument (perf. optimization)
foreach (var xmlDocFactory in _xmlDocFactories)
{
  var xmlDoc = xmlDocFactory();
  swaggerGeneratorSettings.OperationFilters.Insert(0, new XmlCommentsOperationFilter(xmlDoc));
  schemaRegistrySettings.SchemaFilters.Insert(0, new XmlCommentsSchemaFilter(xmlDoc));
}

Using  Assembly Swashbuckle.AspNetCore.SwaggerGen, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=d84d99fb0135530a


List a few projects using Equinox

People are starting to build cool stuff with Equinox. It might be worth adding links to these in the documentation for examples.

Diffrax
sympy2jax
Lucidrains' work
Winnie's inception work
Ben's UNet work
dLux
All the stuff appearing in the "used by" list.

Hi Patrick, do you mind sharing a link to Ben's UNet work? Thanks in advance!

Hey there - I'm afraid that's from a project that hasn't been released yet. Give it a few months and watch this space!

The implementation is now available here:
https://github.com/patrick-kidger/equinox/blob/main/examples/unet.py


Remove warning filters from pyproject.toml, add local warning

suppressions.
We want to support running Bazel tests with PYTHONWARNINGS=error. In preparation for that change, move warning suppressions from pyproject.toml into the individual test cases that generate them, which is a reasonable cleanup anyway.

Looks good – I think some of these are done globally because we need them to be ignored in doctests, and I'm not sure how to do that locally.

Looks good – I think some of these are done globally because we need them to be ignored in doctests, and I'm not sure how to do that locally. CI tests should reveal if I'm remembering this correctly 😁

It's not a problem to readd warnings here if they're needed for doctests. I guess I only care about our main tests, here.

I noticed the array API CI job wasn't running. That should be fixed in #23862


Support multiple versions of python

How can I use a multiple topologies some of which use python2 and some python3. Easiest way I can think is that "virtualenv" command should be configurable so user can point it to correct path.
Also python3 doesn't have virtualenv command, so it would also help there if I can just say
"virtualenv": "python3 -m venv" in config

Any updates on this, ability to set virtualenv command would be great.

Currently there is no support for doing this. I would welcome a PR to add virtualenv command customization but that would be per config file and not per topology.
Figuring this out on a per topology basis is high on my list of priorities right now because I also need this functionality. I would also love to extend it to address #183 as well, but we'll see if I can do that on the first pass.
All that said, you can currently specify the path to the Python interpreter you want to use in your config file as shown here with the -p virtualenv flag. It works fine with Python 3 even without changing the command to use venv.

@anuraguniyal We merged a change into master that will be in the next release. You can override the virtualenv_flags to specify the version of python used during virtualenv creation. If the virtualenv name already exists on the machines you should delete it prior to deploying with this new setting.
class WordCount(Topology):
    # WordCount only will use python3, everything else will use virtualenv_flags in config.json
    config = {"virtualenv_flags": "/path/to/python3"}

cool thanks.

In the https://github.com/Parsely/streamparse/releases/tag/v3.11.0 release


FlatList cannot be tested

It does not work to render a FlatList with react-test-renderer. This error appears:
$ jest flatList.js
 FAIL  __tests__/flatList.js
  FlatList
    ✕ renders (276ms)

  ● FlatList › renders

    TypeError: Cannot read property 'Consumer' of undefined

      at VirtualizedList.render (node_modules/react-native/Libraries/Lists/VirtualizedList.js:1044:29)
      at finishClassComponent (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:7693:31)
      at updateClassComponent (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:7648:24)
      at beginWork$1 (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:9159:16)
      at performUnitOfWork (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:12981:12)
      at workLoopSync (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:12955:22)
      at renderRoot (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:12648:11)
      at runRootCallback (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:12420:20)
      at node_modules/react-test-renderer/cjs/react-test-renderer.development.js:1935:24
      at unstable_runWithPriority (node_modules/scheduler/cjs/scheduler.development.js:643:12)
      at runWithPriority (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:1887:10)
      at flushSyncCallbackQueueImpl (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:1931:7)
      at flushSyncCallbackQueue (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:1920:3)
      at scheduleUpdateOnFiber (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:12297:9)
      at scheduleRootUpdate (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:15087:3)
      at updateContainerAtExpirationTime (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:15115:10)
      at updateContainer (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:15134:10)
      at Object.create (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:15824:5)
      at Object.<anonymous> (__tests__/flatList.js:35:25)

  console.error node_modules/react-test-renderer/cjs/react-test-renderer.development.js:10695
    The above error occurred in the <VirtualizedList> component:
        in VirtualizedList (created by FlatList)
        in FlatList

    Consider adding an error boundary to your tree to customize error handling behavior.
    Visit https://fb.me/react-error-boundaries to learn more about error boundaries.

React Native version: 0.61.4

$ react-native info
info Fetching system and libraries information...
System:
    OS: macOS Mojave 10.14.6
    CPU: (8) x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
    Memory: 2.23 GB / 16.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 12.13.0 - ~/.nvm/versions/node/v12.13.0/bin/node
    Yarn: 1.12.3 - ~/.yarn/bin/yarn
    npm: 6.12.0 - ~/.nvm/versions/node/v12.13.0/bin/npm
  SDKs:
    iOS SDK:
      Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
    Android SDK:
      API Levels: 23, 25, 26, 27, 28
      Build Tools: 23.0.1, 25.0.0, 25.0.2, 27.0.1, 28.0.3
      System Images: android-27 | Google Play Intel x86 Atom
  IDEs:
    Android Studio: 3.5 AI-191.8<IP_ADDRESS>10548
    Xcode: 11.2.1/11B500 - /usr/bin/xcodebuild
  npmPackages:
    react: 16.9.0 => 16.9.0
    react-native: ^0.61.4 => 0.61.4

react-dom and react-test-renderer are also version 16.9.0.
Steps To Reproduce

Create a test suite with this content:

import React from "react"
import {
    Text,
    FlatList,
} from "react-native"
import renderer from "react-test-renderer"

describe("FlatList", () => {
    it("renders", () => {
        expect(renderer.create(
            <FlatList
                data={["foo"]}
                renderItem={item => <Text>{item}</Text>}
                keyExtractor={item => item}
            />
        )).toMatchSnapshot();
    });
});

Run jest flatList.js.

Describe what you expected to happen: I expected the test to create a DOM tree that then would be compared against a snapshot.
This problem arose when I updated React Native from 0.55.3. In the earlier version, it worked fine.
Snack, code example, screenshot, or link to a repository: See above. This problem exists with a proprietary project, so I cannot disclose exact details about how FlatList is used. However, it is not much more complicated than the example.

I have circumvented the problem by mocking FlatList in this manner:
jest.mock("react-native", () => {
    const React = require.requireActual("react");
    const actual = require.requireActual("react-native");
    const View = actual.View;
    function MockedFlatList(props) {
        const items = props.data.map(item => {
            const key = props.keyExtractor(item);
            return (
                <View key={key}>
                    {props.renderItem(item)}
                </View>
            );
        });
        return (
            <View>
                {items}
            </View>
        );
    }
    Object.defineProperty(actual, "FlatList", {
        get: () => MockedFlatList,
    });
    return actual;
});

When this mock is used, the test passes and this is output instead:
$ jest flatList.js
 PASS  __tests__/flatList.js
  FlatList
    ✓ renders (212ms)

The snapshot file contains this:
// Jest Snapshot v1, https://goo.gl/fbAQLP

exports[`FlatList renders 1`] = `
<View>
  <View>
    <Text>
      foo
    </Text>
  </View>
</View>
`;


Insecure MemSet

This is @zlaski's insecure memset query, based on top of my PR to add the AliasedUse instruction. I've switched the dead code detection portion to be more general, which the AliasedUse instruction makes possible. I also extended the pointsIntoStack predicate to handle pointer arithmetic. Finally, I added an aliasing model for strcpy. With these three changes, the query detects 13 apparent true positives on the test cases, as opposed to 3 before the changes.

Please could you link to the page for the original version, so I can see what was discussed there?

If you mean the original version of the memset query, it's #1933.