Update images in UI Overview

Updated images to 1.4.0 version of Monokle.  Added new settings and corrected grammar mistakes.
This PR...
Changes

Fixes

How to test it

Screenshots

Checklist

[ ] tested locally
[ ] added new dependencies
[x] updated the docs
[ ] added a test

I still see the cluster icon in the left toolbar under the Helm icon.  Am I
looking at an old version?
On Tue, Jan 11, 2022 at 6:23 AM Ole Lensmar @.***>
wrote:

@.**** commented on this pull request.
In docs/overview.md
https://github.com/kubeshop/monokle/pull/975#discussion_r782094523:

Left to right:
-- The vertical toolbar to the far left allows you to switch between File and Cluster mode.
+- The vertical toolbar to the far left allows you to switch between File, Kustomize, Helm and Cluster mode.
nice catch @devcatalin https://github.com/devcatalin
—
Reply to this email directly, view it on GitHub
https://github.com/kubeshop/monokle/pull/975#discussion_r782094523, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AXELQIOJUGXPLO5425BGG3TUVQOLDANCNFSM5LU4JO3A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

I see from this morning that 1.5.0 has this change.  I guess this begs the
question - for the work I am doing right now, should I go ahead and work
with 1.5.0 since the release is imminent?
On Tue, Jan 11, 2022 at 8:15 AM Julianne Fermi @.***> wrote:

I still see the cluster icon in the left toolbar under the Helm icon.  Am
I looking at an old version?
On Tue, Jan 11, 2022 at 6:23 AM Ole Lensmar @.***>
wrote:

@.**** commented on this pull request.
In docs/overview.md
https://github.com/kubeshop/monokle/pull/975#discussion_r782094523:

Left to right:
-- The vertical toolbar to the far left allows you to switch between File and Cluster mode.
+- The vertical toolbar to the far left allows you to switch between File, Kustomize, Helm and Cluster mode.
nice catch @devcatalin https://github.com/devcatalin
—
Reply to this email directly, view it on GitHub
https://github.com/kubeshop/monokle/pull/975#discussion_r782094523, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AXELQIOJUGXPLO5425BGG3TUVQOLDANCNFSM5LU4JO3A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

yeah - that's what I was thinking also - perhaps we just make minor high-level changes to the existing 1.4.0 documentation and then double-down on the upcoming 1.5.0...


Body validation does not work?

I'm trying to get validator to work on the body of this route:
  '/filtered':
    put:
      summary: blah
      parameters:
        - in: body
          name: body
          required: true
          schema:
            type: object
            required:
              - filtered
            properties:
              filtered:
                description: status of ssid
                type: boolean

here are my request parameters:
{ uri: 'http://<IP_ADDRESS>/apiv2/filtered',   headers:    { 'x-api-key': 'blah' },   json: { test: 'test' } }
I expect openapi-express to return 400, because body should be an object with filtered prop. Yet I get 200 response. Swaggerize express worked fine with this one. Am I doing something wrong here? I'll edit this to make it more reproducible after lunch....

world.js
module.exports = {
    put: function (req, res, next) {
        console.log(req.body);
        res.json({ok: "ok"});
    }
};

main.js
const apiDoc = {
    swagger: '2.0',
    info: {
        title: 'A getting started API.',
        version: '1.0.0'
    },
    paths: {
        "/world": {
            "put": {
                parameters: [
                    {
                        in: 'body',
                        name: 'body',
                        required: true,
                        schema: {
                            type: "object",
                            properties: {
                                filtered: {
                                    description: "test",
                                    type: "boolean"
                                }
                            },
                            required: ["filtered"]
                        }
                    }
                ],
                responses: {
                    200: {
                        description: "ok",
                    },
                    default: {
                        description: "error",
                    }
                }
            }
        }
    }
};

const bodyParser = require("body-parser");
const express = require("express");
const openapi = require("express-openapi");
const http = require("http");
const app = express();

app.use(
    bodyParser.json(),
    bodyParser.urlencoded({ extended: false })
);

openapi.initialize({
    app,
    apiDoc: apiDoc,
    paths: "./api-v1/paths"
});

app.listen(3200);

setTimeout(function () {
    // Required property filtered is not set
    const postData = JSON.stringify({test: "test"});

    const options = {
        hostname: "<IP_ADDRESS>",
        port: 3200,
        path: "/world",
        method: "PUT",
        headers: {
            "Content-Type": "application/json",
            "Content-Length": Buffer.byteLength(postData)
        }
    };

    console.log("Making request");
    const req = http.request(options, res => {
        console.log("Got response from " + options.path, res.statusCode);
        req.on("data", data => console.log(data));
        req.on("end", data => console.log("END"));
    });

    req.on("error", err => console.log(err));
    req.write(postData);
    req.end();

}, 1000);

Got output:
Making request
{ test: 'test' }
Got response from /world 200

Expected output:
Making request
Got response from /world 400

The schema seems right.   Have you looked at the sample projects?  Here's a spec from the basic-usage project that seems to do what you want: https://github.com/kogosoftwarellc/express-openapi/blob/master/test/sample-projects/basic-usage/spec.js#L77

I was breaking my head for hours as to why this doesn't work.
This unreleased change fixes the issue: https://github.com/kogosoftwarellc/express-openapi/commit/471f9a3909326459fb272f3c8b4918b80bcc4fca#diff-168726dbe96b3ce427e7fedce31bb0bc
how about making a release? @jsdevel

@juliusza done.  published @alrik 's PR as v1.5.0

@juliusza if the latest version works for you, would you mind closing this?  Let us know if you still have problems.  I see why it didn't work for you now, as defining paths in the global apiDoc wasn't added until @alrik 's PR.  Should be good to go now.

Thanks, you're awesome. Looks like I'll be able to replace swaggerize-express lib with this one after all.

  Happy to have you!  Don't hesitate to report issues here.


Creativity pack: fix Accumulative Strike damage not increasing when cards are created

The issue is that OnCreateCardInterface isn't a subscriber, but the main mod file tried to use it like one. Looking at StSLib, it only works on relics/powers/cards/monsters. https://github.com/kiooeht/StSLib/blob/master/src/main/java/com/evacipated/cardcrawl/mod/stslib/StSLib.java#L226

Oops, that one's on me.


Re-Open #18113 for Docker 1.10.1

I seem to have the #18113 issue with Docker 1.10.1!
But it also occurs mostly when using a virtual machine (virtual box) with more than 3G of memory. Then startup of Dockers fails the most time and leaves a /var/lib/docker/network/files/local-kv.db. As long as the file exists, I can not start docker. As soon as I remove it, everything is fine. I have some more hints to reproduce the problem below.
I have the following setup:

Host:

Ubuntu: 15.10
4.2.0-27-generic #32-Ubuntu SMP Fri Jan 22 04:49:08 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Vagrant: 1.7.4 (Default on Ubuntu 15.10)
VirtualBox: 5.0.14 (Default on Ubuntu 15.10)

Create a Vagrant virtual machine with VirtualBox:

Ubuntu 14.04 (LTS)
3.13.0-77-generic #121-Ubuntu SMP Wed Jan 20 10:50:42 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Inside of the VM

Install Puppet (3.4.3) with some modules (apt, docker, epel, etckeeper, stdlib)
Start Docker via Puppet manifest: latest Puppet-Docker (garether-docker) sets up Docker version 1.10.1, build 9e83765

I have a Jenkins starting some of those virtual machines. Most of them require only 2048 MB of assigned RAM. But since yesterday I needed some larger instances and set the memory size for one of them to 4096 MB. This one almost always fails to start Docker and leaves the mentioned local-kv.db. Why only "almost", why not always?
I was trying around with some ideas:

At first I was running the puppet based setup with strace, something like strace -f -o /tmp/docker-problem -ttt puppet apply docker-setup.pp. When run with strace the problem never occured, though I was also never able to see access to the local-kv.db (I guess this happens in the container?).
Then I was trying with different memory sizes:

3072 MB (always works)
3584 MB: Worked some times (1 out of 3)
3800 MB: Failed (only one try)
4095 MB (trying to be slightly below the 4GB): Worked (only one try)
4096 MB: Always fails

Maybe it's something completely different and has nothing todo with memory sizes?
I attach one of the local-kv.db (a bzip2 in a zip) for further investigation:
local-kv.db.zip

If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
For more information about reporting issues, see CONTRIBUTING.md.
You don't have to include this information if this is a feature request
(This is an automated, informational response)

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

docker version:
Client:
 Version:      1.10.1
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   9e83765
 Built:        Thu Feb 11 19:27:08 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.10.1
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   9e83765
 Built:        Thu Feb 11 19:27:08 2016
 OS/Arch:      linux/amd64

docker info:
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 0
Server Version: 1.10.1
Storage Driver: devicemapper
 Pool Name: docker-8:1-267070-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 10.74 GB
 Backing Filesystem: ext4
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 305.7 MB
 Data Space Total: 107.4 GB
 Data Space Available: 40.35 GB
 Metadata Space Used: 733.2 kB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.147 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 WARNING: Usage of loopback devices is strongly discouraged for production use. Either use `--storage-opt dm.thinpooldev` or use `--storage-opt dm.no_warn_on_loop_devices=true` to suppress this warning.
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.77 (2012-10-15)
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
 Volume: local
 Network: null host bridge
Kernel Version: 3.13.0-77-generic
Operating System: Ubuntu 14.04.3 LTS
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 3.861 GiB
Name: devopssquare-full-strace
ID: 45XZ:LNXX:D4SZ:TNGL:B3IF:NCWI:USNB:WFJF:7JSQ:ZCTP:7C5C:HWTD
WARNING: No swap limit support

@ascheman Just to confirm if this is related to #18113, do you see this error in the daemon log : failed to allocate gateway (<IP_ADDRESS>): No available addresses on this pool ?
Thanks for sharing the local-kv.db file. Can you also share the daemon bootup logs ?
FYI there can be other cases (especially when the db is put in an inconsistent state). Hence we cannot assume it is #18113 without knowing all the details.

I was setting the reference to #18113 since the problem was caused by the file local-kv.db which was left over. In fact, the problem occurs during installation of docker and first startup of the daemon through the puppet module.
During that time I get the following log in /var/log/syslog:
Feb 14 17:21:47 vagrant-ubuntu-trusty-64 kernel: [  109.602706] bio: create slab <bio-1> at 1
Feb 14 17:21:47 vagrant-ubuntu-trusty-64 kernel: [  109.610923] bio: create slab <bio-2> at 2
Feb 14 17:21:48 vagrant-ubuntu-trusty-64 kernel: [  110.780651] Bridge firewalling registered
Feb 14 17:21:48 vagrant-ubuntu-trusty-64 kernel: [  110.789882] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Feb 14 17:21:48 vagrant-ubuntu-trusty-64 kernel: [  110.804419] ip_tables: (C) 2000-2006 Netfilter Core Team
Feb 14 17:21:49 vagrant-ubuntu-trusty-64 kernel: [  110.972998] init: docker main process (12420) terminated with status 2
Feb 14 17:21:49 vagrant-ubuntu-trusty-64 kernel: [  111.188388] init: docker main process (12642) terminated with status 1
Feb 14 17:21:49 vagrant-ubuntu-trusty-64 kernel: [  111.188394] init: docker main process ended, respawning
Feb 14 17:21:49 vagrant-ubuntu-trusty-64 kernel: [  111.284999] bio: create slab <bio-1> at 1
Feb 14 17:21:49 vagrant-ubuntu-trusty-64 kernel: [  111.292451] bio: create slab <bio-2> at 2
Feb 14 17:21:49 vagrant-ubuntu-trusty-64 kernel: [  111.359650] init: docker main process (12717) terminated with status 1
Feb 14 17:21:49 vagrant-ubuntu-trusty-64 kernel: [  111.359656] init: docker main process ended, respawning
Feb 14 17:21:49 vagrant-ubuntu-trusty-64 kernel: [  111.462584] bio: create slab <bio-1> at 1
Feb 14 17:21:49 vagrant-ubuntu-trusty-64 kernel: [  111.481806] bio: create slab <bio-2> at 2
Feb 14 17:21:49 vagrant-ubuntu-trusty-64 kernel: [  111.539345] init: docker main process (12841) terminated with status 1
Feb 14 17:21:49 vagrant-ubuntu-trusty-64 kernel: [  111.539351] init: docker main process ended, respawning
Feb 14 17:21:49 vagrant-ubuntu-trusty-64 kernel: [  111.611057] bio: create slab <bio-1> at 1
Feb 14 17:21:49 vagrant-ubuntu-trusty-64 kernel: [  111.616451] bio: create slab <bio-2> at 2
Feb 14 17:21:49 vagrant-ubuntu-trusty-64 kernel: [  111.659566] init: docker main process (12924) terminated with status 1
Feb 14 17:21:49 vagrant-ubuntu-trusty-64 kernel: [  111.659583] init: docker main process ended, respawning
Feb 14 17:21:49 vagrant-ubuntu-trusty-64 kernel: [  111.705675] bio: create slab <bio-1> at 1
Feb 14 17:21:49 vagrant-ubuntu-trusty-64 kernel: [  111.711428] bio: create slab <bio-2> at 2
Feb 14 17:21:49 vagrant-ubuntu-trusty-64 kernel: [  111.754647] init: docker main process (13002) terminated with status 1
Feb 14 17:21:49 vagrant-ubuntu-trusty-64 kernel: [  111.754654] init: docker main process ended, respawning
Feb 14 17:21:49 vagrant-ubuntu-trusty-64 kernel: [  111.799799] bio: create slab <bio-1> at 1
Feb 14 17:21:49 vagrant-ubuntu-trusty-64 kernel: [  111.805659] bio: create slab <bio-2> at 2
Feb 14 17:21:49 vagrant-ubuntu-trusty-64 kernel: [  111.849109] init: docker main process (13079) terminated with status 1
Feb 14 17:21:49 vagrant-ubuntu-trusty-64 kernel: [  111.849128] init: docker main process ended, respawning
Feb 14 17:21:50 vagrant-ubuntu-trusty-64 kernel: [  111.899541] bio: create slab <bio-1> at 1
Feb 14 17:21:50 vagrant-ubuntu-trusty-64 kernel: [  111.904846] bio: create slab <bio-2> at 2
Feb 14 17:21:50 vagrant-ubuntu-trusty-64 kernel: [  111.948785] init: docker main process (13156) terminated with status 1
Feb 14 17:21:50 vagrant-ubuntu-trusty-64 kernel: [  111.948791] init: docker main process ended, respawning
Feb 14 17:21:50 vagrant-ubuntu-trusty-64 kernel: [  111.996065] bio: create slab <bio-1> at 1
Feb 14 17:21:50 vagrant-ubuntu-trusty-64 kernel: [  112.002065] bio: create slab <bio-2> at 2
Feb 14 17:21:50 vagrant-ubuntu-trusty-64 kernel: [  112.044233] init: docker main process (13233) terminated with status 1
Feb 14 17:21:50 vagrant-ubuntu-trusty-64 kernel: [  112.044255] init: docker main process ended, respawning
Feb 14 17:21:50 vagrant-ubuntu-trusty-64 kernel: [  112.092092] bio: create slab <bio-1> at 1
Feb 14 17:21:50 vagrant-ubuntu-trusty-64 kernel: [  112.098328] bio: create slab <bio-2> at 2
Feb 14 17:21:50 vagrant-ubuntu-trusty-64 kernel: [  112.151326] init: docker main process (13310) terminated with status 1
Feb 14 17:21:50 vagrant-ubuntu-trusty-64 kernel: [  112.151333] init: docker main process ended, respawning
Feb 14 17:21:50 vagrant-ubuntu-trusty-64 kernel: [  112.196786] bio: create slab <bio-1> at 1
Feb 14 17:21:50 vagrant-ubuntu-trusty-64 kernel: [  112.202399] bio: create slab <bio-2> at 2
Feb 14 17:21:50 vagrant-ubuntu-trusty-64 kernel: [  112.245816] init: docker main process (13387) terminated with status 1
Feb 14 17:21:50 vagrant-ubuntu-trusty-64 kernel: [  112.245837] init: docker main process ended, respawning
Feb 14 17:21:50 vagrant-ubuntu-trusty-64 kernel: [  112.293325] bio: create slab <bio-1> at 1
Feb 14 17:21:50 vagrant-ubuntu-trusty-64 kernel: [  112.298044] bio: create slab <bio-2> at 2
Feb 14 17:21:50 vagrant-ubuntu-trusty-64 kernel: [  112.341466] init: docker main process (13464) terminated with status 1
Feb 14 17:21:50 vagrant-ubuntu-trusty-64 kernel: [  112.341472] init: docker respawning too fast, stopped

BTW: If I suspend (save state in VBox) and relaunch the VM (Start) after this problem occurs, everything seems to be OK (Docker is up and running after restart).

Just calling service docker start (before restart of the VM) always shows the mentioned logs and docker aborts.
Starting docker manually with docker daemon prints the following:
WARN[0000] devmapper: Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.thinpooldev` or use `man docker` to refer to dm.thinpooldev section.
WARN[0000] devmapper: Base device already exists and has filesystem ext4 on it. User specified filesystem  will be ignored.
INFO[0000] [graphdriver] using prior storage driver "devicemapper"
INFO[0000] Graph migration to content-addressability took 0.00 seconds
INFO[0000] Firewalld running: false
INFO[0000] Default bridge (docker0) is assigned with an IP address <IP_ADDRESS>/16. Daemon option --bip can be used to set a preferred IP address
FATA[0000] Error starting daemon: Error initializing network controller: Error creating default "bridge" network: failed to allocate gateway (<IP_ADDRESS>): Address already in use

Last night the variant with 4096 MB for the VM also was build successfully for one time. So my thesis that it has something to do with the memory of the VM has proven wrong ... Maybe it also depends on the load of the hosting server (at that time it was the only build job at the physical server)?

@ascheman yes. could you pls share the full daemon log during bootup ?
Can you also make sure there arent multiple docker daemons running at the same time sharing the graph folder (-g) corrupting the db ?
Please read my earlier comment on this topic : https://github.com/docker/docker/issues/17939#issuecomment-157137616
Also, can you share the docker daemon configuration ?

@mavenugo I will attach a ZIP with two tars, one of a non-working instance and one of a working one. Both contain the docker.log, some other logs and the docker configuration.
As I pointed out earlier, I am setting up Docker on fresh VM instances. Sometimes the initial installation fails due to the mentioned problem. Then I stop the complete setup of the VM (the state you will get from the one tar in the ZIP). If the installation works well, other steps are performed afterwards (so the logs become much longer, this is the case for the other tar).
docker-differences.zip

BTW: During the mentioned builds the one which was working had a VM RAM size of 4GB while the non-working one had only 2 GB.

I've experienced the same problem with Docker 1.10 and 1.10.1.  We're doing hourly and triggered CI runs and we see about a 30-40% failure rate due to this issue since upgrading to Docker 1.10.
docker version:
Client:
 Version:      1.10.1
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   9e83765
 Built:        Thu Feb 11 19:27:08 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.10.1
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   9e83765
 Built:        Thu Feb 11 19:27:08 2016
 OS/Arch:      linux/amd64

docker info:
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 0
Server Version: 1.10.1
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 0
 Dirperm1 Supported: false
Execution Driver: native-0.2
Logging Driver: son-file
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 3.13.0-67-generic
Operating System: Ubuntu 14.04.3 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.548 GiB
Name: dev01-build-001
ID: YGVH:QXXZ:YE7E:BBBO:HMOA:HD6Z:6HJB:DYWN:DGN3:DNLX:5HWA:FNTC
WARNING: No swap limit support

/var/log/upstart/docker.log:
Waiting for /var/run/docker.sock
INFO[0000] Graph migration to content-addressability took 0.00 seconds
WARN[0000] Running modprobe bridge br_netfilter failed with message: modprobe: WARNING: Module br_netfilter not found.
insmod /lib/modules/3.13.0-67-generic/kernel/net/llc/llc.ko
insmod /lib/modules/3.13.0-67-generic/kernel/net/802/stp.ko
insmod /lib/modules/3.13.0-67-generic/kernel/net/bridge/bridge.ko
, error: exit status 1
/var/run/docker.sock is up
INFO[0000] Firewalld running: false
INFO[0000] Default bridge (docker0) is assigned with an IP address <IP_ADDRESS>/16. Daemon option --bip can be used to set a preferred IP address
INFO[0000] [graphdriver] using prior storage driver "auks"
INFO[0000] Graph migration to content-addressability took 0.00 seconds
INFO[0000] Firewalld running: false
WARN[0000] Could not find endpoint count key docker/network/v1.0/endpoint_count/3b8db9905f9ebe4fba7733b6b29b2e2a61deb5c990d4314362442c9f9ac5ef50/ for network bridge while listing: Key not found in store
WARN[0000] could not find endpoint count key docker/network/v1.0/endpoint_count/3b8db9905f9ebe4fba7733b6b29b2e2a61deb5c990d4314362442c9f9ac5ef50/ for network bridge while listing: Key not found in store
INFO[0000] Default bridge (docker0) is assigned with an IP address <IP_ADDRESS>/16. Daemon option --bip can be used to set a preferred IP address
FATA[0000] Error starting daemon: Error initializing network controller: Error creating default "bridge" network: failed to allocate gateway (<IP_ADDRESS>): Address already in use
INFO[0000] [graphdriver] using prior storage driver "auks"
INFO[0000] Graph migration to content-addressability took 0.00 seconds
INFO[0000] Firewalld running: false
WARN[0000] Could not find endpoint count key docker/network/v1.0/endpoint_count/3b8db9905f9ebe4fba7733b6b29b2e2a61deb5c990d4314362442c9f9ac5ef50/ for network bridge while listing: Key not found in store
WARN[0000] could not find endpoint count key docker/network/v1.0/endpoint_count/3b8db9905f9ebe4fba7733b6b29b2e2a61deb5c990d4314362442c9f9ac5ef50/ for network bridge while listing: Key not found in store
INFO[0000] Default bridge (docker0) is assigned with an IP address <IP_ADDRESS>/16. Daemon option --bip can be used to set a preferred IP address
FATA[0000] Error starting daemon: Error initializing network controller: Error creating default "bridge" network: failed to allocate gateway (<IP_ADDRESS>): Address already in use
INFO[0000] [graphdriver] using prior storage driver "auks"
INFO[0000] Graph migration to content-addressability took 0.00 seconds
INFO[0000] Firewalld running: false

@dvorak Probably be unrelated to the issue, but something is really weird with your setup: there is no auks storage driver...

Thanks @ascheman @dvorak for the logs, but one request: In order to debug this further, we need the debug level logs (start daemon with the -D option).

@ascheman
I checked the local-kv.db file you provided. I could not find any anomalies.
The bitsequence structure backing the allocated IP addresses is correct.
The network object referring to the default network has the correct IP information (including network gateway IP).
Therefore on daemon start, when the default network is being deleted, the network gateway and the <IP_ADDRESS>/16 pool should be released and later reallocated.
If you check you debug level logs on daemon start, you should see one like:
`"releasing IPv4 pools from network  ()
before this one is printed:
log.Debugf("Allocating IPv4 pools for network <name> (<ID>)
Can you please confirm you see the above two logs. Thanks.

We actually use the default pool <IP_ADDRESS>/16 and <IP_ADDRESS>/17 in our development environments.
 Daemon option --bip can be used to set a preferred IP address
DEBU[0000] Allocating IPv4 pools for network bridge (52cad9c52af1fe0ee72089bbd2a5fe10055084c14d47d524159c59051312739f)
DEBU[0000] RequestPool(LocalDefault, <IP_ADDRESS>/16, , map[], false)
DEBU[0000] RequestAddress(LocalDefault/<IP_ADDRESS>/16, <IP_ADDRESS>, map[RequestAddressType:com.docker.network.gateway])
DEBU[0000] ReleasePool(LocalDefault/<IP_ADDRESS>/16)
DEBU[0000] Cleaning up old shm/mqueue mounts: start.
FATA[0000] Error starting daemon: Error initializing network controller: Error creating default "bridge" network: failed to allocate gateway (<IP_ADDRESS>): Address already in use

Also, if I delete the docker0 bridge (ip link del docker0) then the daemon starts up fine afterwards.  We have a work around for the issue, but that doesn't help in CI environments where this is happening unpredictably.

I will look into this as soon as I have access to my test environment again during the next days.
The problem will be that I just run a lot of CI jobs which build up a Vagrant/VirtualBox environment with Ubuntu 14.04 LTS. These boxes set Docker up by a Puppet module (https://github.com/garethr/garethr-docker by @garethr) which simply calls a dpkg install as far as I can see. To make any change to this setup with Docker debugging switched on would require to prepare a patched version of the Puppet module and the respective infrastructure to inject it into my provisioning chain. I am not that deep into Puppet and do not have the time to prepare this in short term. Maybe @garether can assist here?
In general it seems to be the same problem as @dvorak pointed out.
On 22.02.2016, at 20:56, aboch<EMAIL_ADDRESS>wrote:

@ascheman
I checked the local-kv.db file you provided. I could not find any anomalies.
The bitsequence structure backing the allocated IP addresses is correct.
The network object referring to the default network has the correct IP information (including network gateway IP).
Therefore on daemon start, when the default network is being deleted, the network gateway and the <IP_ADDRESS>/16 pool should be released and later reallocated.
If you check you debug level logs on daemon start, you should see one like:
`"releasing IPv4 pools from network ()
before this one is printed:
log.Debugf("Allocating IPv4 pools for network  ()
Can you please confirm you see the above two logs. Thanks.
—
Reply to this email directly or view it on GitHub.

--
Gerd Aschemann --- Veröffentlichen heißt Verändern (Carmen Thomas)
+49/173/3264070 --<EMAIL_ADDRESS>-- http://www.aschemann.net

@dvorak: As I pointed out, my CI setup is driven by a Puppet module. However, my workaround is the following, maybe it also works in your case?
# Workaround for https://github.com/docker/docker/issues/20312
sleeptime=10
maxtries=5
try=0
echo "Sleeping ${sleeptime}s until Docker is up and running (first)"
sleep $sleeptime
until $dir/test.sh || test $try -ge $maxtries
do  sudo /bin/rm -f /var/lib/docker/network/files/local-kv.db
    sudo service docker start
    try=`expr $try + 1`
    echo "Sleeping ${sleeptime}s until Docker is up and running (try #$try)"
    sleep $sleeptime
done
echo "Sleeping ${sleeptime}s until Docker is up and running (final)"
sleep $sleeptime
$dir/test.sh

The mentioned test.sh in $dir is simply
#!/bin/bash

set -eu

if status docker 2>/dev/null | grep -q 'process '
   then echo "Docker is up and running"
   else echo "Docker is not running!" >&2
        exit 1
fi

If it does not work after n (=5) retries I give up and stop the overall CI box setup. Usually this works (sometimes with 3 or 4 retries, but it works.
On 23.02.2016, at 15:43, dvorak<EMAIL_ADDRESS>wrote:

Also, if I delete the docker0 bridge (ip link del docker0) then the daemon starts up fine afterwards. We have a work around for the issue, but that doesn't help in CI environments where this is happening unpredictably.
—
Reply to this email directly or view it on GitHub.

--
Gerd Aschemann --- Veröffentlichen heißt Verändern (Carmen Thomas)
+49/173/3264070 --<EMAIL_ADDRESS>-- http://www.aschemann.net

@ascheman you can pass arbitrary options to the docker daemon on startup using the extra_paramemters param on the docker class, mentioned here: https://github.com/garethr/garethr-docker/blob/master/manifests/init.pp#L158-L160. These end up in the docker engine config here: https://github.com/garethr/garethr-docker/blob/master/templates/etc/conf.d/docker.erb#L43. That should allow you to enable debugging with the -D flag.

@garethr: Thanks for the hint
@aboch: Added two docker debug logs, one from an instance that failed and one from a working one.
docker-logs-20160304.zip

Thanks @ascheman for the debug logs.
They confirm you are hitting the same issue reported by @dvorak.
The fact that the following logs are missing when docker reboots is a hint to the issue:
DEBU[0001] releasing IPv4 pools from network bridge (<id>)
DEBU[0001] ReleaseAddress(LocalDefault/<IP_ADDRESS>/16, <IP_ADDRESS>)
DEBU[0001] ReleasePool(LocalDefault/<IP_ADDRESS>/16)

The default bridge network's gateway IP allocated during the previous daemon instance is not being removed, therefore the subsequent allocation failure.
Thanks for now,
will let you know when we find something or if we need more info.

Running docker with latest libnetwork using @ascheman's local-kv.db file (thanks @ascheman for providing the file and for the extra logs) explains why daemon does not find the bridge network, and therefore does not delete it at https://github.com/docker/docker/blob/master/daemon/daemon_unix.go#L596
DEBU[0000] Registering ipam driver: "default"
DEBU[0000] Registering ipam driver: "null"
WARN[0000] Could not find endpoint count key docker/network/v1.0/endpoint_count/a18d34c84f16467a2555bb3c834f192a567b4a6a14692a11a728e482cd4bdcbf/ for network bridge while listing: Key not found in store
WARN[0000] could not find endpoint count key docker/network/v1.0/endpoint_count/a18d34c84f16467a2555bb3c834f192a567b4a6a14692a11a728e482cd4bdcbf/ for network bridge while listing: Key not found in store

(This log was not present in docker/docker 1.10.1 code)
Not sure how we ended in this state where the network object is present but not the correspondent endpoint_count object. (Maybe because of a well-timed ungraceful shutdown of the daemon ?)
We'll check if some code change can be done to avoid or limiting the chances to get into this scenario.

In my case the sequence is such:

Package is installed by puppet.
Docker engine started by packaging
Puppet changes /etc/default/docker
Puppet stops docker engine
Puppet starts docker engine
Start fails.

There is no manual steps for me.  This doesn't happen 100% of the time.

Same here, sometimes it works, sometimes not ...
On 05.03.2016, at 13:00, dvorak<EMAIL_ADDRESS>wrote:

In my case the sequence is such:
Package is installed by puppet.
Docker engine started by packaging
Puppet changes /etc/default/docker
Puppet stops docker engine
Puppet starts docker engine
Start fails.
There is no manual steps for me. This doesn't happen 100% of the time.
—
Reply to this email directly or view it on GitHub.

--
Gerd Aschemann --- Veröffentlichen heißt Verändern (Carmen Thomas)
+49/173/3264070 --<EMAIL_ADDRESS>-- http://www.aschemann.net

@dvorak @ascheman  for those of us who are not familiar with puppet, it would be good if you can make it easier by providing the scripts and steps to reproduce it (with the most bare-minimal steps). The above steps are useful, but we dont know what all it takes to reproduce this exact same scenario.

The problem still exists with docker-10.0.3.
I have provided a minimal setup in https://github.com/ascheman/minimal4dockerproblem
Just run vagrant up (maybe several times to reproduce)

@ascheman I see a PR was just merged to resolve this issue, and will be included in docker 1.11

Thanks for the Info, I was thinking it was resolved with 1.10.3 ... So I will wait for the next Minor release.
BTW: : is there a release roadmap somewhere?
On 18.03.2016, at 12:11, Sebastiaan van Stijn<EMAIL_ADDRESS>wrote:

@ascheman I see a PR was just merged to resolve this issue, and will be included in docker 1.11
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

--
Gerd Aschemann --- Veröffentlichen heißt Verändern (Carmen Thomas)
+49/173/3264070 --<EMAIL_ADDRESS>-- http://www.aschemann.net

We usually use the wiki for that; https://github.com/docker/docker/wiki. But the project is always moving fast, so sometimes it may be out of date, or not yet include longer term goals

@ascheman could you please try master build to make sure this is infact fixed ?

It is not a question of running the test once. I have set up a Jenkins job building a Vagrant machine with Docker on Ubuntu every few minutes. ~15% of the builds fail due to this bug.
The install uses the following chain/nested setup: Vagrant->Ubuntu->Puppet->Docker Debian Package (see my mentioned minimal Puppet install setup). If you could provide me with a current master build as an Ubuntu/Debian package I could easily phase this into my regular test build. On the other hand you could easily run this on your own if you have some Continuous Integration set up for Docker? This would allow for permanent testing of the minimal Docker setup as well as for more sophisticated tests (compositions of the different Docker tools etc.). I wonder if a project like Docker does not use CI?
On 18.03.2016, at 17:41, Madhu Venugopal<EMAIL_ADDRESS>wrote:

@ascheman could you please try master build to make sure this is infact fixed ?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

--
Gerd Aschemann --- Veröffentlichen heißt Verändern (Carmen Thomas)
+49/173/3264070 --<EMAIL_ADDRESS>-- http://www.aschemann.net


Add additional go install step as go build doesn't install binaries

Add go install ./... step that actually installs the binaries into $GOPATH/bin/ as mentioned.

Thanks @ctrlrsf -- can you please sign the CLA? I will then merge.

CLI signed. Thanks @otoolep


WV-268: WeVoteServer/import_export_targetsmart/models.py: Convert methods with warning to @staticmethod

WV-268: WeVoteServer/import_export_targetsmart/models.py: Convert methods with warning to @staticmethod
Status: FIX IN PROGRESS
Priority: Medium
Made the following changes:

converted methods create_counter_entry and retrieve_daily_summaries to static methods.

NOTE: Did not put every input to the method on its own line because the method declaration had not already wrapped to the second line.

👍


Version 3 to 4 (and .scss to .sass): license causes build fail

I'm using webpack 4.10.2 with sass-loader 6.0.7. After updating my include for the new version to have /sass, my build now fails with:
ERROR in Module build failed:
   License: none (public domain)
                                  ^
      Invalid CSS after "...blic domain) */": expected 1 selector or at-rule, was "*/ {}"
      in (myBuildPath)/node_modules/reset-css/sass/_reset.sass (line 3, column 36)

I didn't inspect the file terribly closely, but I believe the only real difference between version 3 and version 4 is that the extension changed. If I manually switch the extension back to .scss, the build succeeds.
Lastly, plugging the file into https://www.sassmeister.com/ switches the comment to look like this:
/* http://meyerweb.com/eric/tools/css/reset/
 * v4.0 | 20180602
 * License: none (public domain)

html, body, div, span, applet, object, iframe,

but then upon compile, it switches to
/* http://meyerweb.com/eric/tools/css/reset/
 * v4.0 | 20180602
 * License: none (public domain) */
html, body, div, span, applet, object, iframe,

(The comment closing characters being the important difference). Manually altering the .sass file to have this comment style ends up breaking the build further down the file (at time, mark, audio, video {), which leads me to believe the extension switch may have been by mistake.
Was the change from .scss to .sass intentional? And if so, is there anything else I should try here?

Total bug! Thank you! Fixed and released as v4.0.1. My apologies.


Installation of you Software on PC

Do you have any feature or idea how to create a setup for installation of your software on

Window system (MUST)
Mac System  and so on...

For a first version of your application: It s better to  find  the way  to use your software without GITHUB site.

This step i will do it went the project will be at 80%

You cannot close the issue when you want to solve it in future!!!

We  close an issue when it  is solved!!  am i m not right?


"Let Windows Decide" prefers Conhost over Terminal Preview

Windows Terminal version
1.16.2642.0
Windows build number
10.0.22621.819
Other Software
No response
Steps to reproduce

In Settings -> Privacy & security -> For developers, given the pictured options, choose "Let Windows decide"

Run cmd from the start menu

Expected Behavior
Windows chose Windows Terminal Preview.
Actual Behavior
Windows chose conhost.

Pretty sure this is by design, and Windows will only prefer the Stable version of the Terminal, not the Preview one.

Yep that's correct. The "Let Windows decide" option only checks for the non-Preview variant at the moment. The code responsible for this can be found here: https://github.com/microsoft/terminal/blob/437b5ac595915830194498eca8825e6037e288c0/src/host/srvinit.cpp#L82-L89


Make the non-thread-safety of DbContext more visible

We already have a paragraph on this in the "Configuring a DbContext" page, but this may not be enough (e.g. see https://github.com/aspnet/EntityFrameworkCore/issues/18148).
Could be part of a general rethinking of fundamentals/getting started (https://github.com/aspnet/EntityFramework.Docs/issues/1726). The non-safety is definitely "getting started" information we want to surface to new users right away.
Also maybe add thread-safety notes into our API documentation, which seems pretty common in .NET in general?

Note from triage: in the conceptual docs now; also add to API docs for DbContext.


Adds a San Jose, CA favourite of mine

Thank you @noffle :), would you mind rebasing to latest master for a clean merge?

Done!


PAR-520

LGTM

@kfateem if you want to have a look before we merge, this is the solution for push notifications when the app isn't open on iOS

Please see comment on:
https://github.com/Parlio/web/pull/349

Thanks for moving to an event-driven paradigm.
Please register and unregister for "WEBCLIENTREADY" in the register/unregister methods - not notificationReceived.
When WEBCLIENTREADY check if you have a notification then handle.

@aYoussef after our discussion please:

add an observer "WEBCLIENTREADY" in AppDelegate+notification.m swizzled_init with callback to onWebClientReady()
Maintain a boolean flag isWebClientReady
in onWebClientReady()
i) updated isWebClientReady to true
ii) call notificationReceived
iii) unregister the observer
modify notificationReceived to check isWebClientReady flag before attempting to communicate with web:

 if (notificationMessage && self.callback && isWebClientReady) {
...
}

1 comment otherwise LGTM :+1:
Thank you for handling!


Scroll Bar in Windows binary

Scroll bar is not able to be controlled by mouse click on Windows binary.
Works fine with scroll wheel or up and down keys
Thanks

Thanks,
Fixed in 4da7500dbdef645228588d545c4210fc315d035c


Not work in bootstrap modal

time picker not show in bootstrap modal

Add this css
.dtp {
    z-index: 2050 !important;
}

@rodmarzavala can you help me disable hours in timepicker? Thank you


Cleanup of grafana & prometheus

Follow-up of #3524, these DNS records have to be deleted from Azure:

[ ] grafana.jenkins.io
[ ] grafana.publick8s.jenkins.io
[X] the corresponding namespaces have to be deleted from prodpublick8s cluster.
Done while working on https://github.com/jenkins-infra/helpdesk/issues/2844

Done, ref: https://github.com/jenkins-infra/helpdesk/issues/3351#issuecomment-1564595767


Node 2566/get-rid-of-readpreference.preference

@mbroadst updated with your edits, thanks!

Closed: Reasoning in ticket here.


Update Photos - Zubin Oommen

Current photos are from last year, update to this year because Zubin is cool and matches with Evan
Submitted via Form by<EMAIL_ADDRESS>

@thesuperRL I think @Auberti may be interested in working on this. I think someone just needs to run photos.py, assuming @JonBriggs has put the new files in 411.

@JonBriggs I think we need a new version of the CSV file from 411 that maps students to photos, like this file from 2021: https://github.com/EastsidePreparatorySchool/epschedule/commit/b34b0d08b694a356866670840b258af54e0a6d2b. Can you remind me how we did this last year?

@JonBriggs did you get a chance to make the new CSV file (or an API) for student photos?

2023 photos have been updated, closing this issue.


0.8.3 not pushed to docker yet?

SSIA
latest from quay gives 0.8.2

The same with dockerhub 0.8.2

The same with dockerhub 0.8.2

Just pushed those; something must be wrong with the .goreleaser.yml settings, which I'll figure on next releaser (prev one's logs are expired).


Memory only storage engine

For Node.js. I need it because Este is universal and a lot of actions can depend on storage even on the server. Implementation should be super easy.

Hmm, maybe server storage should do nothing, because app doesn't live on the server. Ok.


[bucketing overhaul 2/n] Delegate bucket management to HPUBucketingContext

This PR is a follow-up to #395. I cherry-picked commit f66c9c3 and fix it.
The motivation here is to move entire bucketing logic into separate class HPUBucketingContext. As a next step this class could be moved into vllm-hpu-extension.

hi @kdamaszk #395 needs rebase, I understand its still valid for merging before this one?


[SPARK-28087][SQL] Add string function support for split_part

What changes were proposed in this pull request?

Function
Return Type
Description
Example
Result

split_part(string text,delimiter text, field int)
text
Split string on delimiter and return the given field (counting from one)
split_part('abc~@~def~@~ghi', '~@~', 2)
def

split_part(string text, delimiter text, field int)
Arguments:
text - the original string, results null if it is null
delimiter - string literal, results null if it is null; results the text itself if it is empty and field=1
field - the give field index, start from 1
Why are the changes needed?

https://www.postgresql.org/docs/11/functions-string.html
http://prestodb.github.io/docs/current/functions/string.html
Does this PR introduce any user-facing change?

add one new functions
How was this patch tested?

add ut

Test build #112447 has started for PR 26202 at commit b2e7d45.

Merged build finished. Test PASSed.

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

Test build #112447 has finished for PR 26202 at commit b2e7d45.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class SplitPart(text: Expression, delimiter: Expression, field: Expression)

Merged build finished. Test FAILed.

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

spark-sql> select element_at(split('abc~@~def~@~ghi', ''), 1);
a

postgres=# select split_part('abc~@~def~@~ghi', '', 1);
   split_part
-----------------
 abc~@~def~@~ghi

some cases as I show one example above not fit such replacement
split takes regex, split_part take string literal as parameter
3.the idx in split_part can be null, but not in element at

close this because it seems pg only


Refused

Refused to display 'my_server_url' in a frame because it set 'X-Frame-Options' to 'sameorigin

Your report server url is returning a "X-Frame-Options" value that does not allow it to be embeded in other websites/apps.
See more:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options


How do you incorporate PSScriptAnalyzer as part of your dev process?

My team wants to leverage this utility to ensure consistent coding practices for all of our custom commandlets. I was hoping to have a discussion and get some insight into how other teams and developers use PSScriptAnalyzer as part of their dev process.
Some questions to get this going:

What triggers your analysis? Is it manually run by developers as needed? Does it run as part of your postbuild process? Only in certain build configurations? If it does run with each build, does the build fail if Warnings or Errors are generated?

Are the results only for the developer running the analysis to review in their console, or do you take the results and do something with them?

How have you addressed performance issues / slowdowns caused by analysis of many Powershell scripts at once?

I realize all teams and organizations are different, and one team's process isn't necessarily going to work for everyone, but I am interested in recommendations for what processes you find work well for yourself and your team.

This is a great question, one I am interested in following. As a newcomer to continuous delivery I have adopted PSScriptAnalyzer as part of my post build process. If warnings / errors are encountered it prevents the powershell module from being sent into its final destination (repository).

I add in ScriptAnalyzer into my Pester Tests - that way I know whether they are passing or not - throughout my test cycles and I can see where I have to spend time working on. I'm just about to publish a blog post on this with some sample code that can be run as well and will pop a link back in here as another response

@albvar How is your environment/project set up? Currently, our modules are built into various solutions based on their product type and functionality. I'm currently modifying the build process so that the script analyzer runs post-build, and the results are output to the console for the developer to see. This is just phase one to get something going.
Next up will be to process these results and do something with the output (fail the build, inform the dev, etc). Pester Tests seem like they might be the next logical place to go with this, so I would be really interested in reading @kilasuit's blog post as well.

As promised - blog post is here http://blog.kilasuit.org/2016/03/29/invoking-psscriptanalyzer-in-pester-tests-for-each-rule/


Fix make lint on Python 3.10

In practice this means upgrading pylint which was failing on 3.9 and 3.10.
I would like to use Python 3.10 as my daily driver to avoid discovering issues like https://github.com/elastic/rally/issues/1484 only through our users, but I could not run make lint on Python 3.10 which made this impractical.

The precommit check failed because the similarities checker found several violations of duplicate-code.
Do you want to disable this for now?

For now I'm more concerned by the fact that I'm not seeing those errors locally! Do you see them when running make lint?

For now I'm more concerned by the fact that I'm not seeing those errors locally! Do you see them when running make lint?

I also don't see the above mentioned errors when I run this PR locally with a clean venv using make lint or make precommit.
I am using Python 3.8.13.
Kind of unrelated, make install reports:
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
hatchling 1.6.0 requires pluggy>=1.0.0, but you have pluggy 0.13.1 which is incompatible.

I ended up just disabling that check like I've done in esbench as it's of low value anyway.

Kind of unrelated, make install reports:
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
hatchling 1.6.0 requires pluggy>=1.0.0, but you have pluggy 0.13.1 which is incompatible.

Thanks! I opened https://github.com/elastic/rally/pull/1567 to address this.


feat(forge): [ALPHA] add soldeer as an optional package manager.

Motivation
This pull request is related to issue https://github.com/foundry-rs/foundry/issues/5966, which essentially outlines the reasons I believe a dedicated dependency manager for Solidity is necessary.
To summarize, relying on git submodules is not a reliable solution. As a security researcher, I've observed numerous projects defaulting to using npmjs to avoid dealing with git submodules. Considering npmjs was designed for the JavaScript ecosystem, why not create a package manager specifically tailored for Solidity?

Solution
My proposal involves developing an open-source Rust-based dependency manager that functions similarly to crates.io or npmjs for Solidity. I'm introducing Soldeer, a straightforward package manager with four key features:

install: This function allows the installation of dependencies from https://soldeer.xyz/, or from a custom link provided by the user. The dependency must be pre-zipped. For instance, you could zip your dependency, host it on a CDN, and share the link with your team.
update: This function is designed to update the existing dependencies specified in the project.
login: Enables users to log into the repository, allowing them to push new dependencies.
push: Allows users to push a directory to their account on https://soldeer.xyz/ as a new project version.

Integration
Soldeer is built as a library that can be also used standalone.
For foundry, i've just integrated the library and based on the commands, i redirect the logic to the library. The integration is not that big.
For reviewing probably one will need to check the open-source github repository to see how it works.
https://github.com/mario-eth/soldeer
Future Plans:

Integrate Solidity-based tools such as Slither and Mythril runners to identify and report errors before pushing changes.
Implement audit report features for each version directly on the platform, allowing users to easily verify whether a specific version has been audited.
Collecting feedback and listening to the community.

ALPHA STAGE
The current implementation of Soldeer is intended to serve as an alternative to git submodules, rather than a replacement, until it matures sufficiently to become the default package manager.

I've updated the pull request with version 0.2.6 of soldeer.
This version does the following things:

Previously i was using sdependencies tag to store the dependencies in the foundry.toml but after a discussion with the foundry team, they suggested that it should be renamed to dependencies.
The dependency config in foundry.toml has been changed to
[DEP-NAME]~[DEP-VERSION] = {version = "", url=""} respecting Cargo.toml.
I had to include the version in the dependency key because one project might want to use 1 dependency with multiple versions and Cargo.toml does not support that, the only way to do it is to have different keys pointing to different versions.

Updated to version 0.2.7.
Now the dependency name is the key in the config file, previously was [DEP-NAME]~[DEP-VERSION]. This was needed to respect the cargo way.
If the need for multiple versions for the same dependency, an issue has been opened for that https://github.com/mario-eth/soldeer/issues/34

if possible, can we also add a simple integration test? see e.g. https://github.com/foundry-rs/foundry/tree/master/crates/forge/tests/it

I have some issues on how to approach this, most of the integrations are related with cheatcodes as i can see.
Do you want me to do a full integration test? like running the soldeer command for install for example, then check if it was installed correctly and so on?

@mario-eth Sorry about that I meant to link https://github.com/foundry-rs/foundry/tree/master/crates/forge/tests/cli which has some CLI tests

if possible, can we also add a simple integration test? see e.g. https://github.com/foundry-rs/foundry/tree/master/crates/forge/tests/it

Added cli tests here

Some comment on the dependency format
I also think we ideally ditch the "v" prefix so we can support semver operators later, see e.g. https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#specifying-dependencies-from-cratesio

Removed the v as well.

@mario-eth, before this is merged, wanted to ask on the concept of nested dependencies.
I'm using soldeer to install @uniswap-v2-periphery-1.1.0-beta.0, yet it's not usable since it has @uniswap/lib dependency which is not being resolved automatically.
Moreover, the imports from such and similar contracts often use other "package" names, so that if you even install one, you have to remap them manually.
Is that something that's being tackled or planned to do after the merge?

@mario-eth, before this is merged, wanted to ask on the concept of nested dependencies.
I'm using soldeer to install @uniswap-v2-periphery-1.1.0-beta.0, yet it's not usable since it has @uniswap/lib dependency which is not being resolved automatically.
Moreover, the imports from such and similar contracts often use other "package" names, so that if you even install one, you have to remap them manually.
Is that something that's being tackled or planned to do after the merge?

Hey,
Unfortunately soldeer for now does not track nested dependencies for now, this is just the first step to making an actual package manager.
The reason why it does not track it's because, in your example, what version of @uniswap/lib-dependency does the uniswap-v2-periphery-1.1.0-beta.0 uses? We can't assume it's the last one.
While this is the first step, we must start define how we want these dependencies to be tracked, a step towards that i tried to do in soldeer, in the remappings, i tried to map the package+version as a path that it will be hardcoded in the solidity files so that instead of using
import<EMAIL_ADDRESS>we should do
import<EMAIL_ADDRESS>In this way we can infer the dependency version.

Any timeline when this would be released? Really exited to not use submodules

Bumped the Soldeer version to v0.2.15.
I had to solve two bugs:

One was regarding replacing versions in the config files. I was using append instead of overwrite, which would have broken the config if the new version string length was smaller than the old one.
When pushing, zipping new files would have created an empty directory due to the zip dependency bump.

okay last rebase then I'm sending it


checkov: 3.2.69 -> 3.2.72

Diff: https://github.com/bridgecrewio/checkov/compare/refs/tags/3.2.69...3.2.72
Changelog: https://github.com/bridgecrewio/checkov/releases/tag/3.2.72
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

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

2 packages built:

checkov
checkov.dist


[Feature Request]: Extend testing of EventGrid/eventSubscriptions to different scopes

Description
The current tests on eventSubscriptions is only testing one scenario. This issue is to investigate and if so create tests to use the eventSubscriptions resource to deploy into the other scopes that support eventSubscriptions:

domains
domainTopics
systemTopics
topics (already covered, currently called common)

Suggestion on tests that can be created.

@MariusStorhaug  Can all those scopes be tested in one go (common)?

#3107 changed a bit how those subscriptions are handled.


Docs/font documentation improvements

Fixes #50 and #34

Coverage increased (+3.2%) to 49.457% when pulling f7b6fd9082f4d7f21bbc2b4443e6dc4694b6a772 on docs/font-documentation-improvements into 9f8538722c3e6a389a6ea24fd1d134e4dc48b350 on master.


Fix empty return for route "report_errors_to_github".

Now returns "OK".

Are the unit tests working now, or do they need fixing? We should try to make sure the build is always green

I've had unit tests fail multiple times for different reasons in the last few pushes - so definitely a few sources having intermittent errors.


improve handling of private methods in polymer code generation

 Issue by sigmundch
Originally opened as dart-lang/sdk#18490

See: https://code.google.com/p/dart/issues/detail?id=18481
Options:
(a) give better error messages in cases like _highlightChanged
(b) add support for private methods. This would require:
  - switching smoke to use strings instead of symbols (#_foo is not supported)
  - switching codegeneration to generate code on each library (requires issue dart-lang/code_transformers#17), we then can generate the getters for these private symbols in the context of the same library

 Comment by sigmundch

Marked this as blocking dart-lang/polymer-dart#171.

 Comment by sigmundch

Removed Type-Defect label.
Added Type-Enhancement label.

 Comment by sigmundch

Issue dart-lang/sdk#13881 has been merged into this issue.

cc @jmesserly.

 Comment by jmesserly

Removed Library-PolymerBuild label.

 Comment by jmesserly

Added Pkg-Polymer label.

 Comment by sigmundch

Removed Priority-Unassigned label.
Added Priority-Medium label.

 Comment by jmesserly

Removed Pkg-Polymer label.
Added Pkg-PolymerBuild label.

 Comment by sigmundch

Added this to the Later milestone.

 Comment by jmesserly

Removed Area-Polymer label.
Added Area-Pkg label.

 Comment by sigmundch

Added Polymer-P-2 label.

 Comment by sigmundch

Removed Polymer-P-2 label.
Added Polymer-Milestone-Later label.

 Comment by sigmundch

Removed Priority-Medium label.
Added Priority-Low label.

 Comment by sigmundch

Removed this from the Later milestone.

 Comment by sigmundch

Removed Polymer-Milestone-Later label.
Added PolymerMilestone-Later label.


Primitive, non boxing, long array based MStack

Supersede #447 this is a complete implementation, already passing all the tests up to the interpreter, can be tested with something like:
 mvn clean install -pl runtime-tests -am

I started, but got a bit confused about the changes necessary in "aot", @electrum or @danielperano I would love some help in finalizing this PR :pray: and learning a bit more how asm works ...
This is a prerequisite to avoid arrays construction here, the plan is to open up the underlying array so that we can perform operations just using the offset :crossed_fingers:

update: I benchmarked the interpreter and got good improvements on this branch, I think it's in the right direction!
Regarding the AOT, the changes seem to be a bit more invasive than expected, it would be great to have some help.

I did a little benchmarking on my super noisy machine(take the results with a lot of salt):
Chicory 0.0.12:

With GraalJIT:
Benchmark                                      Mode  Cnt      Score        Error  Units
ChicoryAotTest.chicoryAotTest                  avgt    3   1282.401 ±    51.518  ns/op
ChicoryInterpreterTest.chicoryInterpreterTest  avgt    3  63086.906 ± 18526.425  ns/op

Without GraalJIT:
Benchmark                                      Mode  Cnt      Score        Error  Units
ChicoryAotTest.chicoryAotTest                  avgt    3   1222.858 ±    326.915  ns/op
ChicoryInterpreterTest.chicoryInterpreterTest  avgt    3  87630.869 ± 138021.856  ns/op

---

Current main:

With GraalJIT:
Benchmark                                      Mode  Cnt      Score       Error  Units
ChicoryAotTest.chicoryAotTest                  avgt    3   1237.301 ±   423.694  ns/op
ChicoryInterpreterTest.chicoryInterpreterTest  avgt    3  71274.055 ± 11410.525  ns/op

Without GraalJIT:
Benchmark                                      Mode  Cnt       Score       Error  Units
ChicoryAotTest.chicoryAotTest                  avgt    3    1349.806 ±   945.091  ns/op
ChicoryInterpreterTest.chicoryInterpreterTest  avgt    3  101900.141 ± 38884.734  ns/op

---

Primitive longs (this branch):

With GraalJIT:
Benchmark                                      Mode  Cnt      Score       Error  Units
ChicoryAotTest.chicoryAotTest                  avgt    3   1153.859 ±   984.977  ns/op
ChicoryInterpreterTest.chicoryInterpreterTest  avgt    3  41791.372 ± 43360.065  ns/op

Without GraalJIT:
Benchmark                                      Mode  Cnt      Score       Error  Units
ChicoryAotTest.chicoryAotTest                  avgt    3    899.077 ±   483.678  ns/op
ChicoryInterpreterTest.chicoryInterpreterTest  avgt    3  49629.772 ± 88844.628  ns/op

CI is green, ready for final review!

this is exciting!

Begging for review here :pray: cc. @bhelx @electrum @danielperano

ok, let's merge this, any follow up comment will be fixed on top.


Improve compatibility with old numpys

The axis argument was required in np.flip before numpy 1.15.

Thank you for this, once again! I’ll push the new version to PyPI in less than twelve hours.


Fix bug #200: css.walkRules is not a function

I commit 2 changes:

to fix npm install with the problem of dependencies npm ERR! peerinvalid The package eslint does not satisfy its siblings' peerDependencies requirements! npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>- 0.24 || ~1.0.0-rc-0
to fix the #200 with invalid version upgrade of node-pixrem

BTW, npm test is freezed on 51:
Hash: 6f7d6564bb5071230c2c
Version: webpack 1.11.0
Time: 8967ms
     Asset     Size  Chunks             Chunk Names
cssnext.js  9.53 MB       0  [emitted]  main
    + 1463 hidden modules

><EMAIL_ADDRESS>tape /home/enguerran/Development/cssnext
> tape 'dist/__tests__/*.js'

TAP version 13
# cssnext API
ok 1 should return a string
ok 2 should return a string, even if the given string is empty
ok 3 simple example with multiples features should work with cssnext API
ok 4 should return a postcss instance
ok 5 simple example with multiples features should work with postcss API
ok 6 doesn't mutate options object
# use case: color plugins together
ok 7 all color plugins should works together
# use case: use plugin options
ok 8 should be able to pass options to plugins
# cli
ok 9 should return an error when input file is unreadable
ok 10 should show that the input file is not found
ok 11 should not modify input of 'color hex alpha' fixture if all features are disabled
ok 12 should not modify input of 'pseudo class matches' fixture if all features are disabled
ok 13 should not modify input of 'color gray' fixture if all features are disabled
ok 14 should not modify input of 'font variant' fixture if all features are disabled
ok 15 should throw an error
ok 16 should output a readable error
ok 17 should show the url where to report bugs
ok 18 should not modify input of 'color rebeccapurple' fixture if all features are disabled
ok 19 should not modify input of 'color hwb' fixture if all features are disabled
ok 20 should not modify input of 'media queries range' fixture if all features are disabled
ok 21 should not modify input of 'rem' fixture if all features are disabled
ok 22 should rebase url
ok 23 should not modify input of 'color rgba' fixture if all features are disabled
ok 24 should not modify input of 'pseudo elements' fixture if all features are disabled
ok 25 should not modify input of 'custom selectors' fixture if all features are disabled
ok 26 should not modify input of 'pseudo class any link' fixture if all features are disabled
ok 27 should not modify input of 'autoprefixer' fixture if all features are disabled
ok 28 should not modify input of 'custom media' fixture if all features are disabled
ok 29 should not modify input of 'custom properties' fixture if all features are disabled
ok 30 should not modify input of 'calc' fixture if all features are disabled
ok 31 should return an error when <input> or <output> are missing when `--watch` option passed
ok 32 should show an explanation when <input> or <output> are missing when `--watch` option passed
ok 33 should read config file on --config
ok 34 should not modify input of 'filter' fixture if all features are disabled
ok 35 should not modify input of 'color function' fixture if all features are disabled
ok 36 should return an error when <output> is missing when `--watch`option passed
ok 37 should show an explanation when <output> is missing when `--watch` option passed
ok 38 should log on --verbose
ok 39 should not modify input of 'pseudo class not' fixture if all features are disabled
ok 40 should read from stdin and write to stdout
ok 41 should have a --browsers option
ok 42 should read from a file and write to a file
ok 43 should not adjust url on --no-url
ok 44 should read from a file and write to stdout
ok 45 should add sourcemap on --sourcemap
ok 46 should not import on --no-import
not ok 47 should compress on --compress
  ---
    operator: equal
    expected: |-
      '/*! sha */body{color:red}'
    actual: |-
      '/*! sha */\n/* blah */\nbody {\n    color  : red;\n}'
    at: maybeClose (internal/child_process.js:764:16)
  ...
# cli/watcher
ok 48 should output error messages when `--watch` option passed
ok 49 should update the file
ok 50 should update the file, again
ok 51 should not modify a file if a previously imported file is modified

Thank   @enguerran , but it's no longer necessary. pixrem Version 1.3.2 was unpublished on npm. So if you reinstalled cssnext there will be no error.

ok, that would be enough for our needs. Thanks

@enguerran fyi, I fixed the other issue this morning. Thanks for reporting.


template improvements

Handles #25 Needs more tests/docs before ready to merge.
This PR has a bunch of changes around testing because the travis-ci builds keep failing in new and exciting ways. Also I added a pile of (mostly integration) tests.

Incorporated @ericfode 's feedback so will merge now... 🍰


fix(yankee): refactor yankee! make it simpler, and it now works

did some local testing, and successfuly wrote the first travel time to dynamo. it was for a bus travelling down masspike that happened to be on the shuttle route, so not very accurate, but exciting nonetheless.

TODO: make it not over-write the bus positions whenever none of the buses are at a stop

I moved all the yankee stuff to a dedicated repo: https://github.com/transitmatters/yankee-shuttle-ingestor
I haven't really worked on it since I realized that Yankee subcontracts out to operators (like a Peter Pan red line shuttle bus I was on), for which this API doesn't have data :sob: but if anyone wants to pick it up and run with the code, feel free. Also might be instructive for future stuff


add fractional values as main quantities

I really like this package! I found myself needing whole fractions as the primary number in some cases and have added that feature here. So you could use something like
num("1/100")
or
qty("2/3", "erg/cm^2/s")
or even
num("1/100+-0.03")
but it doesn't support using fractions in uncertainties, something num("1/100+-1/100") wouldn't be allowed (at least for now). I added a couple examples to the example.typ file. Let me know if this is a worthwhile contribution.

On reflection, fractions are not enough when all results need to be given in an exact form (which happens mainly in mathematics, very rarely in physical and engineering sciences). We can quickly end up with results such as 58pi cm, 3 + sqrt(2) m, 5 sin(35°) km, or even a mixture of all of these. And I come to wonder if it would not be simpler to respond to all these cases to authorize the entry of a math block for the body of the functions qty, numrange and qtyrange. Examples: qty($2/3$, "erg/cm^2/s"), qty($58 pi$, "cm").
However, it would not be possible to mix with error intervals (like in num("1/100+-0.03")). So I wonder who needs error intervals with an exact value?

Yeah I understand your reasoning there. One example is when dealing with whole numbers with units and then taking an inverse. So yes, there would be no uncertainty there, say with speed of light, but having the ability to take its inverse and still share that with units would be important. Maybe I could update this PR to only allow fractions but not with uncertainties?

I reread this part of the documentation:

num uses string parsing in order to typeset numbers, including separators between the thousands. They can have the following form:
- float or integer number
- either ({} stands for a number)
    - symmetric uncertainties with +-{}
    - asymmetric uncertainties with +{}-{}
- exponential notation e{}

and I think that maybe the best way to keep things simple from a user perspective is to make the line “float or integer number” become “float, integer number or math formula”. It might not even be necessary to surround it with dollar signs: once the string has been broken down into its three parts, if it turns out that the first one is not a float or an integer, then the script should try to interpret it as a math formula. And in case of ambiguity which would lead to a bad division into three parts, adding parentheses around the first part could solve the problem. Examples: qty("2/3", "erg/cm^2/s"), num("1/100+-0.03"), qty("58 pi", "cm"), num((sin(35)+5)+0.05-0.2e-6).
The principle could even be extended to the second part (even if I don't see any use cases).


no Particles while vim-mode enabled

Very impressive! Greate job! I love this plugin.
And while I am using this plugin, I found when vim-mode is enabled, while typing, only shake but no paticles shown.
I wonder if this is a problem and if I can use both vim-mode and activate-power-mode, it would be greate.
Thanks again for your good job!

Same here

this is issue is still happening with the latest version?

Closing issues on old versions of this package.
Open again if the problem persists with the latest release.


Implement HPack static compression

Today Kestrel does not use any of the HPack compression features when serializing response headers. Static compression looks like the easiest place to start.
Design notes:

The static table is here: https://tools.ietf.org/html/rfc7541#appendix-A
Make an enum that maps to the static header names. Associate this with the known headers in the response header collection.
Rather than passing in an enumeration of <string, string> to the encoder, come up with another structure that allows passing in either the enum values or the strings.
Stretch: the :status pseudo header has 7 static entries that include common values. All of the other static header values are request headers (though shared code with HttpClient would want to take advantage of those).

Related work:

Dynamic compression #2951
Huffman encoding https://github.com/aspnet/KestrelHttpServer/issues/2683

Another HTTP/2 perf improvement to be driven by @aspnet/grpc

Backlogging as per above. Keep us posted gRPC folks ;)


Feature: Add the ability to search for items in the table with optional search bar.

Add the ability to search for items in the table with optional search bar.

working on it https://github.com/LeeWannacott/table-sort-js/pull/117


[macOS] Ignore mouse move event caused by mouse mode switch.

Fixes issue caused by #42327 (moving mouse cursor to the center of screen on mouse capture, which was producing unwanted mouse move event with large deltas).
Fixes #45966 and fixes #46030

Thanks!


SHA+HMAC is not "storing passwords securely"

Please don't tell people using HMAC with SHA is a synonym for storing passwords securely. It is not.
There are algorithms specifically designed for storing passwords securely like bcrypt or argon2. Use them.
The SHA algorithm is designed to calculate a hash of huge amounts of data as fast as possible. A salt can protect you from rainbow tables but not from brute forcing or dictionary attacks.
Bcrypt and Argon2 are designed to be expensive and are adaptable to increasing computational power.
If you don't change the encryption in your tutorials at least remove the sentence "Perform HMAC operation on password using crypto module of node.js for storing password securely." from day 13 and add a security warning that encrypting passwords with SHA is unsafe and should not be used in production systems, that it is only used for demonstration purpose or something.

hello,
We appreciate your concern and we have removed the content which beginners might misunderstood.
This will be visible on https://nodejsera.com within 30 mins.
Regards
Team Nodejsera

You did not add the warning but thanks for removing the sentence.

Hello,
Thanks for reaching out. We added the warning but due to some reasons we were not able to update the live website yet. The changes will be visible within next 12 hours.
We appreciate your concern.
Regards
Team Nodejsera


Feature discussion - Eclipse

Background
The core/perturbations.py module has an existing shadow_function which uses geometrical manipulation to calculate whether a satellite is in earth's shadow or not. This binary switching function assisted in turning solar radiation pressure "on" and "off" based on the shadow function.
For determining if a satellite is in eclipse or not and their entry and exit times, having a model that accounts for umbral and penumbral regions might be good to have. First, we could find out if the satellite is in sunlight or is in the umbra or the penumbra region. Further, we could also determine the entry and exit times of the eclipse for a satellite.
For the latter idea, the book by Vallado assumes a cylindrical earth shadow (effectively not considering the shadow as umbra or penumbra but a single type of earth shadow of zero solar pressure). This assumption might have been made to ease the complexity of the analysis since determining times of eclipse requires integration operations, which seems to be trickier by itself.
The paper On Satellite Umbra/Penumbra Entry and Exit Positions dealt with eclipse times for both cylindrical and conical earth shadow.
Question
If we intend to focus on umbral and penumbral regions (and not just a cylindrical earth shadow), we could detect and find times of entry and exit times within these regions. In such a case, there most likely will be a need to modify the radiation_pressure to account for umbral (zero solar pressure) and penumbral (minute non-zero solar pressure) regions.
This feature of dealing with umbral and penumbral regions is good to have. Still, I wondered if it adds some complexity, given the above points, for example.
Summary
Do we go with umbra and penumbra analysis (and consider everything that is needed to accompany it, for example, the solar pressure variations) or stick with a cylindrical earth shadow assumption as is currently done in poliastro?
Thanks!

I have some relatively simple logic coded up from algorithms in the book Mission Geometry written by James Wertz that calculates whether a satellite is currently in eclipse and what type of eclipse (umbra, penumbra, annular).  It's just trig functions, no integration required.  But it requires position vectors for the Sun, Earth, and the satellite.  Would that be of interest?  You can't predict entry or exit times using it.  It just tells you the instantaneous eclipse status.

Thank you for reaching out @apogeecmb ! Based on what you said, it seems that the algorithm you propose is similar to the one in Vallado since it too works on simple trigonometric calculations and returns a boolean value, whether the satellite is in eclipse or not. Since poliastro uses scipy's solve_ivp, it turned out that we do not need to manually integrate the system of equations (although there are pure mathematical treatments in the literature to do that).
Since scipy's solve_ivp expects a continuous output which it can use to detect events, the task has effectively boiled down to return a value that continuously varies with time and use that as a basis for detecting eclipse conditions for a propagating orbit.
If you would have any thoughts/suggestions on the on-going discussion in #1246, it would be great!
Thanks again.

Some inspiration from Orekit: https://gitlab.orekit.org/orekit/orekit/-/blob/develop/src/37d6c3d1/java/org/orekit/propagation/events/EclipseDetector.java#L173-191 looks like a continuous function?

Orekit's implementation seems to be relatively shorter and cleaner. Although, there's the method pointOnLimb being used in EclipseDetector here: https://gitlab.orekit.org/orekit/orekit/-/blob/develop/src/main/java/org/orekit/propagation/events/EclipseDetector.java#L182 whose code is here: https://gitlab.orekit.org/orekit/orekit/blob/develop/src/main/java/org/orekit/bodies/Ellipsoid.java#L246. There seems to be a bit of geometry involved. I think poliastro doesn't deal with an attractor's limb yet.
As a result, there might be a need of adding a pointOnLimb like method in perhaps, spheroid_location.py? In such a case, the logic again gets complicated. So the question is whether to:

Add "limb" capabilities in poliastro  and make the eclipse implementation totally inspired from orekit, or
Stick with vallado's treatment of eclipse.

I also saw that using the shadow_function in current main (here) inside eclipse events seems to be in close agreement with orekit's validation case (poliastro/validation#29) even though orekit's implementation uses the star's radius but shadow_function doesn't.
So there might be a need to check if the current main's shadow_function might suffice to use in eclipse events and we could get away with pointOnLimb...

Closed in #1246 🎉  @Yash-10 will add some extra documentation soon 💪🏽


Table for conversion tools

We need to add a table or a page dedicated to conversion tools

https://github.com/FrancisCrickInstitute/OmeSliCC
https://www.glencoesoftware.com/products/ngff-converter/
bf2raw cli usage

see also https://wiki-biop.epfl.ch/en/IPA/conversion-ometiff


Fix capitalization issue

Description
Incremental tables were potentially not running incrementally if components were specified with capitalization, as in information_schema they are always present in lowercase.  Talking to dbt to see if there is a better way to do this, but for now, ensure lower case when used in queries.
Checklist

[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[ ] I have updated the CHANGELOG.md and added information about my change to the "dbt-databricks next" section.

Going to merge (after changelog) and if dbt has a better option, will do that as a separate PR.


Create only one parser function as 'global_parser(DETAILS)`

Describe
We are having code redudancy while parsing those two functions for parsing country details and state details have same cloned code
Solution
Instead we can have only one global parser function called from functions.py for both of the parsings

@KulkarniSuraj Wanna give a try?

NO worries :)


Building an application with cbl, cbl_flutter_ee downloads x86 native executables

An application that includes these cbl libraries will download and bundle an x86 native couchbase library. Flutter does not support the x86 ABI (only x86_64, so this is entirely wasted.
name: cbl_example
description: A new Flutter project.

environment:
  sdk: '>=2.18 <3.0.0'

dependencies:
  flutter:
    sdk: flutter
  cbl: ^2.1.1
  cbl_flutter: ^2.0.2
  cbl_flutter_ee: ^2.1.2

flutter build apk --target-platform=android-arm64 --analyze-size
dart devtools --appSizeBase=path/to/output_from_previous_command (ignore flutter pub global run)
Notice that there is an x86 architecture slice.

I guess ... it does support it in debug mode. But then these are also getting packaged into release applications, which seems like more of an issue

Thanks for letting me know!
I doubt there are any users who rely on being able to use the x86 binaries in debug mode, so removing entirely them should be fine.

I believe the flutter tool would have to set ndk.abiFilters to control which ABIs for native libraries from plugins should be included, but it does not seem to do that.
Advice I've seen a few times is to add abiFilters manually to exclude x86.


REFACTOR: add pok validation file

Done by splitting pok functions into global, preGame and inGame functions with validator script for each one of them


FileArchiveModeFactory - Extracted from FileTarget

Attempt to resolve the issues #1670 and #1681, which is mostly caused not understanding how to configure the NLog Archive Logic (And also major refactoring of the archive logic in FileTarget).
I guess more effort could be applied to FileArchiveModeDynamicSequence.GenerateFileNameMask() to better recognize any date-format-output.
Enabled the unit-tests from #1788, but had to modify them, so they would work with Mono on Linux (Changed hardcoded windows-backslash to Path.Combine). The tests also suffered from confusing debug- and trace-level (Logged to debug-level and didn't expect it to reach trace-level).
!! Breaking change !!
If using ArchiveNumberingMode.Sequence (default) and not having configured an ArchiveFileName (default) and have enabled archiving (MaxArchiveFiles > 0). Then it will now enable dynamic-sequence mode, instead of strict-sequence-mode.
Dynamic-sequence-mode will use the same archive-filename-format (as strict-sequence-mode), but its filemask-wildcard for doing archive-cleanup is a little more greedy as it replaces the largest range of digits (must be more than one) with a wildcard (and not just the sequence-no).
This improves the out-of-box archive-cleanup, when the FileTarget.FileName-Layout includes date-renderer.
New behavior for dynamice sequence-mode
New behavior when ArchiveFileName does not contain sequence-no-pattern (#}:

More adaptive filemask-wildcard used when doing archive-cleanup. Before it was just all files with the same file-extension. Now also using the actual LogEvent (Instead of Null-LogEvent), so the filemask for cleanup is a lot better.
Now delays archive cleanup until first write-operation occurs, instead of FileTarget.Initialize(). This allows archive-cleanup to work properly as it will use the actual LogEvent for rendering archive filemask for cleanup (Instead of Null-LogEvent).

This also removes extra overhead at startup where all FileTarget would scan their archive-folders.
This generates extra overhead at first new file write, where archive-cleanup occurs. But the archive-cleanup is skipped if new file write is caused by just having executed a file-archive-operation.

This improves the out-of-box archive-cleanup, when the ArchiveFileName-Layout includes date-renderer.
Other changes:

Now delays the monitoring of the archive-folder until the first-write. And the filemask monitored is generated from the actual logevent instead of Null-LogEvent (More correct).
ArchiveNumberingMode.Date now skips an unnecessary archive-cleanup when moving to new file after just having performed archive of the previous file (with cleanup).
Attempt to handle that logging-folder and archive-folder is the same folder. Crude Path.GetDirectoryName-comparison that probably can be cheated.
Attempt to handle file-creation-date-issue on Linux for archiving. This should improve how NLog performs archive-cleanup of dated-archives.

This change is

It's the limited silverlight api.

Targets\FileArchiveStyleFactory.cs(583,81): error CS1061: 'System.IO.FileInfo' does not contain a definition for 'CreationTimeUtc' and no extension method 'CreationTimeUtc' accepting a first argument of type 'System.IO.FileInfo' could be found (are you missing a using directive or an assembly reference?)

There's maybe a helper for this already.

Codecov Report

Merging #1993 into master will increase coverage by <1%.
The diff coverage is 88%.

@@           Coverage Diff           @@
##           master   #1993    +/-   ##
=======================================
+ Coverage      82%     82%   +<1%
=======================================
  Files         285     286     +1
  Lines       19589   19616    +27
  Branches     2290    2307    +17
=======================================
+ Hits        15983   16053    +70
+ Misses       3040    3023    -17
+ Partials      566     540    -26

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 e4ddeef...cf074c5. Read the comment docs.

@304NotModified Thanks that fixed the appveyor-build. The travis-build required some changes to the unit-tests. But now things are looking green. And I have implemented a fix for my worries about performing too many archive cleanups.

Please move all the classes to their own file :)

Have now moved the classes into their own individual file.

@304NotModified Discovered that the "bugs" reported for the NLog-Archive-Logic is actually caused by the problems with understanding how to use the enum ArchiveNumberingMode together with ArchiveFileName-layout (Failing to use the {#} properly).
I have now modified this PR into improving the out-of-box experience, when using the NLog-Archive-Logic. And removed the bad behavior of doing cleanup of all files with same file-extension, when failing to use the {#} properly.

Sounds great! Will include into 4.5 due to the large redactor. Is it OK if I merge #2000  first?

Is it OK if I merge #2000 first?

Sure no problem with that.

@snakefoot

If using ArchiveNumberingMode.Sequence (default) and not having configured an ArchiveFileName (default) and have enabled archiving (MaxArchiveFiles > 0). Then it will now enable dynamic-sequence mode, instead of strict-sequence-mode.

Dynamic-sequence-mode will use the same archive-filename-format (as strict-sequence-mode), but its filemask-wildcard for doing archive-cleanup is a little more greedy as it replaces the largest range of digits (must be more than one) with a wildcard (and not just the sequence-no).

This improves the out-of-box archive-cleanup, when the FileTarget.FileName-Layout includes date-renderer.

Do you have an example for this? (e.g. what is changed). Need that for the news post :)

Do you have an example for this?

I guess the most simple example is that you can now get correct archive cleanup when just using the two FileTarget parameters FileName and MaxArchiveFiles, eventhough FileName depends on layout-renders (Like date, logger-name, log-level, etc.). Before it would try and cleanup according to rendering of Null-LogEvent.
The more advanced example is when using archiveFileName without {0}, then one will also get correct archive cleanup. Before it would try and cleanup anything matching the log-file-extension.

fixes #2050

@snakefoot any idea if this also fixes #1748?

@304NotModified No don't think so, just scanned the code to see if there was any obvious bugs, but didn't find any.

Any idea if this also fixes #1748?

@304NotModified Just tested with the provided nlog.config. It rolls every day (as configured), so the result becomes:

01_AppName.0.log (Two days ago)
02_AppName.0.log (Previous day)
03_AppName.log (Active)

I think the wanted behavior is this:

01_AppName.log (Two days ago)
02_AppName.log (Previous day)
03_AppName.log (Active)

This PR can give this result by removing ArchiveEvery="Day" and ArchiveNumbering="Rolling". And then change the existing parameter to MaxArchiveFiles="27" (Cater for february).

@304NotModified Have now implemented a unit test that verifies that the above solution actually works for  #1748

fixes  #1670, fixes #1681, fixes https://github.com/NLog/NLog/issues/1748


Could not find com.android.tools.build:gradle:8.11.1.

**Hello,
I am trying to run ./gradlew build and everytime is showing these issue, and I have no idea why:**
_* What went wrong:
A problem occurred configuring root project 'android'.

Could not resolve all artifacts for configuration 'classpath'.
Could not find com.android.tools.build:gradle:8.11.1.
Searched in the following locations:
- https://dl.google.com/dl/android/maven2/com/android/tools/build/gradle/8.11.1/gradle-8.11.1.pom
- https://repo.maven.apache.org/maven2/com/android/tools/build/gradle/8.11.1/gradle-8.11.1.pom
Required by:
root project :_

this is my gradle.properties:
org.gradle.jvmargs=-Xmx4G -XX:MaxMetaspaceSize=2G -XX:+HeapDumpOnOutOfMemoryError
android.useAndroidX=true
android.enableJetifier=true
org.gradle.java.home=C:\Program Files\Java\jdk-23
this is android/build.gradle:
_buildscript {
repositories {
google() // Este es el repositorio de Google.
mavenCentral() // Este es opcional pero recomendable.
}
dependencies {
classpath 'com.android.tools.build:gradle:8.11.1' // Asegúrate de tener la versión correcta.
classpath 'com.google.gms:google-services:4.4.2' // O usa la última versión: 4.3.15.
}
}
allprojects {
repositories {
google()
mavenCentral()
}
}_
this is my gradle-wrapper-properties:
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https://services.gradle.org/distributions/gradle-8.11.1-all.zip
this is my android/app/build.gradle:
_plugins {
id "com.android.application"
id "kotlin-android"
// The Flutter Gradle Plugin must be applied after the Android and Kotlin Gradle plugins.
id "dev.flutter.flutter-gradle-plugin"
}
android {
namespace = "com.example.recetas_fit"
compileSdk = flutter.compileSdkVersion
ndkVersion = flutter.ndkVersion
compileOptions {
    sourceCompatibility = JavaVersion.VERSION_1_8
    targetCompatibility = JavaVersion.VERSION_1_8
}

kotlinOptions {
    jvmTarget = JavaVersion.VERSION_1_8
}

defaultConfig {
    // TODO: Specify your own unique Application ID (https://developer.android.com/studio/build/application-id.html).
    applicationId = "com.example.recetas_fit"
    // You can update the following values to match your application needs.
    // For more information, see: https://flutter.dev/to/review-gradle-config.
    minSdk = flutter.minSdkVersion
    targetSdk = flutter.targetSdkVersion
    versionCode = flutter.versionCode
    versionName = flutter.versionName
}

buildTypes {
    release {
        // TODO: Add your own signing config for the release build.
        // Signing with the debug keys for now, so `flutter run --release` works.
        signingConfig = signingConfigs.debug
    }
}

}
flutter {
source = "../.."
}
apply plugin: 'com.google.gms.google-services'_
Would appreciate any help or insight.
Thanks

@MimMoussa The latest stable version of Android Gradle Plugin is 8.7.3, for begginers its easy to confuse it with gradle itself.
Just use com.android.tools.build:gradle:8.7.1

thank you. I have did that change and also I have changed the Java to JDK17. And it worked. Issue now is when I want to build the apk I have this:
Gradle build failed to produce an .apk file. It's likely that this file was generated under D:\apps\recetas_fit\build, but the tool couldn't find it.

Your issue appears to be a question about how to use Gradle. They should be asked in a different channel, so we will close it. Your question might be answered in Gradle documentation or on our community Slack or forums. Find links to these resources on help.gradle.org.
If you think our analysis is wrong, please provide us with more detailed information explaining why.


Update the README

Checklist

[ ] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

The readme is automatically generated and will be re-written with every re-render.


add deodorant left days + add litter percent + fix pet weight

Nice, any example configs for this or works out of the box?


R.is implementation has the problematic characteristics of instanceof

Long story short: http://bit.ly/1I3wwqf
This isn't an issue in node.js environments (at least not in non-esoteric usage... I guess one could get multiple globals through the vm modules), because node uses a single global object for all modules. However, in browser environments, and probably in some other JS environments, having to deal with multiple global scopes is a quite common obstacle, and also one of the reasons why some developers avoid using instanceof.
There is no perfect solution for this, but I think that at least for native js types, Ramda should work "as expected" (i.e. in the practical manner ;-)). The obvious example is arrays: I don't think the current difference between Array.isArray to R.is(Array) is something that can ever be beneficial to anyone.
On a side note, an interesting edge case is |R.is(Object, Object.create(null))|, which returns false (as expected) even though Object.create(null)| walks and does almost all of the things an object does - it's just not an Object (Object.create(null) is often used to avoid accidentally picking Object.prototype keys when using an object in the role of a map).

Somehow I missed this one when it was posted.  You're right that this is unfortunate.  Obviously we can switch to the sort of solution kangax gave some years ago for the known types, but it would be some pretty ugly code, involving something like:
Object.prototype.toString.call(val) === '[object Array]'

Object.prototype.toString.call(val) === '[object Date]'

etc., with a separate path for anything other than the known types.  Do you have any other suggestion?

This seems to work ok:
http://tinyurl.com/o3eab7p
("Make short URL" doesn't work there for whatever reason)

@asaf-romano Function.name does not work in IE.
var fixedIsImpl = R.curry((ctor, obj) => {
  if (R.type(obj) == "Object" && ctor != Object) {
    return R.is(ctor, obj);
  }

  return R.type(obj) == ctor.name;  // I mean ctor.name
});

@CrossEye I can not find any documentation about the browser compatibility of Ramda. Is that OK?

@benjycui we have a sauce suite, we just have to get it running again. the problem was it was running too much (and timing out). Anyways, ramda should be ES3-compatible, for better or worse.

The reason I used Function.name is because Object.toString.apply is only useful when it runs on an instance. That is, it will only return "...Array..." if it runs on []. Running it on |Array| just returns "...Function...".
So, indeed, if constructor.name cannot be used, all the native object have to be hardcoded in the implementation.

@buzzdecafe THX!
@asaf-romano You can try toString, and then slice the function name. :-)
Array.toString()  // => "function Array() { [native code] }"

Nice, just need to double check that all browsers return a similar result for native functions like this.

http://tinyurl.com/ob9t7pl

On a side note, I think R.toString is using .constructor.name

plaid/sanctuary#105 demonstrates a solution to this problem. The one thing we would lose is knowledge of the type hierarchy: R.is(Error, new TypeError()) currently evaluates true, but would evaluate false were we to abandon instanceof checks. Also, for R.is(Foo, new Foo()) to evaluate true, Foo would need to define a '@@type' property on its prototype.

I've never really understood the point of having instanceof in a language that doesn't have classes.

This seems to be a deal-breaker:

Also, for R.is(Foo, new Foo()) to evaluate true, Foo would need to define a '@@type' property on its prototype.

That sounds far too intrusive.

For what it's worth, I had this issue with my repl tool not working for example with Ramda functions that use R.is  against function values produced in repl context. The built-in node repl didn't exhibit this issue so I dug in the code a bit and found the option useGlobals: true for repl.start(opts). It has the effect of using same globals (Function etc.) for repl context and required modules.

That's a nice find, @raine.
I do think we should solve the underlying problem as best we can in Ramda.  There are clear enough solutions for native types, but I haven't seem anything great fir user types.   I find the @@type solution both too intrusive and to fat from robust.