Json Generation Issues

I am using swagger generate spec -o ./swagger.json to create a swagger json file for my annotated go files, but am not getting the desired results.
Here is my go code with annotations:
package main

import (
   "encoding/json"
   "net/http"
)

// a volume containing info on the volume
// swagger:model volumes_info
type Volumes_info_t struct {
   // type of data
   //
   // required: true
   ODATA_TYPE string

   // the schema
   //
   // required: true
   Schema string

   // name of the volume
   //
   // required: true
   Name string

   // description of volume
   //
   // required: true
   Description string

   // count of members in volume
   //
   // required: true
   MembersCount int

}

// A VolumeResponse is the response to an API call that returns the payload
//
// swagger:response volumeResponse
type VolumeResponse struct {
   // swagger:allOf
   // in: body
   payload Volumes_info_t
}

// swagger:route GET /redfish/v1/systems/1/storage/{storage_number}/volumes listVolumes
//
// Show information of one individual volume
//
// Responses:
//    default: volumeResponse
//        200: volumes_info
////        422: validationError
func API_Systems_1_Storage_1_Volumes (w http.ResponseWriter, r *http.Request) {
   var volumes_t Volumes_info_t
   json.NewEncoder(w).Encode(volumes_t)
}

And here is my json output:
{
 "swagger": "2.0",
 "paths": {
   "/redfish/v1/systems/1/storage/{storage_number}/volumes": {
     "get": {
       "description": "Show information of one individual volume",
       "operationId": "listVolumes",
       "responses": {
         "200": {
           "$ref": "#/responses/volumes_info"
         },
         "422": {
           "$ref": "#/responses/validationError"
         },
         "default": {
           "$ref": "#/responses/volumeResponse"
         }
       }
     }
   }
 },
 "responses": {
   "volumeResponse": {
     "description": "A VolumeResponse is the response to an API call that returns the payload"
   }
 }
}

As can be seen, I am missing the entire definition field, as well as information in the responses field, as expected from using the swagger:model annotation.
Also, when I try to make the field in my VolumeResponse struct public to Payload Volumes_info_t from payload Volumes_info_t, I get the following error when running the command to generate the spec: unable to determine package for /root/go/thea/server/temp/temp.go.
I feel that this issue is possibly what is causing the json file to not display everything properly, but I do not know how to resolve. I tried looking at the Petstore example and its associated annotations, but to no success. Do I perhaps need to create separate directories for my models and responses? Any help or pointers in the right direction would be appreciated.
Environment
swagger version: 0.13.0
go version: 1.9.1
OS:   Ubuntu 16.04

try running it with swagger generate spec --scan-models

package main

import (
   "encoding/json"
   "net/http"
)

// a volume containing info on the volume
// swagger:model volumes_info
type Volumes_info_t struct {
   // type of data
   //
   // required: true
   ODATA_TYPE string

   // the schema
   //
   // required: true
   Schema string

   // name of the volume
   //
   // required: true
   Name string

   // description of volume
   //
   // required: true
   Description string

   // count of members in volume
   //
   // required: true
   MembersCount int

}

// A VolumeResponse is the response to an API call that returns the payload
//
// swagger:response volumeResponse
type VolumeResponse struct {
   // in: body
   Payload Volumes_info_t
}

// swagger:route GET /redfish/v1/systems/1/storage/{storage_number}/volumes listVolumes
//
// Show information of one individual volume
//
// Responses:
//    default: genericError
//         200: volumeResponse
//         422: validationError
func API_Systems_1_Storage_1_Volumes (w http.ResponseWriter, r *http.Request) {
   var volumes_t Volumes_info_t
   json.NewEncoder(w).Encode(volumes_t)
}

you're much better off just generating the code from a swagger spec imo. You can look at how it annotates all the code, that will help you figure out what's going on with yours

The problem here was that the code wasn't inside $GOPATH/src


Support custom template paths for New-TestResources.ps1

Add/extend parameters to support:

Custom test-resources.json and/or test-resources.bicep paths
Absolute paths for -ServiceDirectory to enable running the script outside of a repo (for example, when testing changes in the tools directory, or running the script for deployments in the stress infrastructure).

Closing in favor of https://github.com/Azure/azure-sdk-tools/issues/4450


vcap breaking upm compilation on Edison

Hi,
vcap is breaking compilation for me because there is no libjpeg.h in /usr/include and I have not found the package that provides this file :
'In file included from /home/vidal/Logiciels/upm/build/src/vcap/pyupm_vcapPYTHON_wrap.cxx:3462:0: /home/vidal/Logiciels/upm/src/vcap/./vcap.hpp:33:21: fatal error: jpeglib.h: No such file or directory #include <jpeglib.h> ^ compilation terminated. src/vcap/CMakeFiles/_pyupm_vcap.dir/build.make:62: recipe for target 'src/vcap/CMakeFiles/_pyupm_vcap.dir/pyupm_vcapPYTHON_wrap.cxx.o' failed make[2]: *** [src/vcap/CMakeFiles/_pyupm_vcap.dir/pyupm_vcapPYTHON_wrap.cxx.o] Error 1 CMakeFiles/Makefile2:4796: recipe for target 'src/vcap/CMakeFiles/_pyupm_vcap.dir/all' failed make[1]: *** [src/vcap/CMakeFiles/_pyupm_vcap.dir/all] Error 2 Makefile:123: recipe for target 'all' failed make: *** [all] Error 2
'
Can anybody please explain howto add libjpeg.h in yocto.
Many thanks

Easiest way would be to install libjpeg-dev with opkg. Add http://iotdk.intel.com/repos/3.0/iotdk/core2-32/ to your base feeds list in /etc/opkg/base-feeds.conf. Then you can do:
opkg update
opkg install libjpeg-dev

Here's a really good document that goes into more details about Package Management on Intel Platforms. Just keep in mind that some of the links/versions in the examples might be outdated.
I will also update this driver to use Cmake's findJPEG instead and simply not generate the target when the library isn't there.

The vcap driver has been updated as of UPM version 0.7.0 to check for libjpeg. If it's not found on the build system the vcap driver doesn't generate a make target.


Support for comments

It would be great if cost models written in Agora supported comments, allowing indexers to take note of why certain queries are priced in a certain way, why matching rules are placed in a certain order, or simply to structure cost models in neat way.

It's worth noting that Agora already has support for comments, but unfortunately these are in limited position (preceding a statement) https://github.com/graphprotocol/mission-control-indexer/blob/master/guides/agora/language/reference/statements.md#comments We can expand support to include more positions though.

It's worth noting that Agora already has support for comments, but unfortunately these are in limited position (preceding a statement) https://github.com/graphprotocol/mission-control-indexer/blob/master/guides/agora/language/reference/statements.md#comments We can expand support to include more positions though.


Detect logger.log with non-integer first argument

Description
Example:
logger.log("INFO", "Message")

This looks like it could work, but log() only takes an integer such as logging.INFO.

This is a bit duplicative of type-checking, but I think at least checking for strings is worth it.

Meh, log() is not often used.

Actually should be easy if implementing #30.


[SR-14268] nightly main fails to compile SwiftNIO tests: many errors and warnings

Previous ID
SR-14268

Radar
rdar://problem/74687888

Original Reporter
@weissi

Type
Bug

Additional Detail from JIRA

Votes
0

Component/s

Labels
Bug

Assignee
None

Priority
Medium

md5: 5ca4dcbc2f1eab7f724d18329d1a3e5b

Issue Description:
SwiftNIO itself seems to build okay but the tests fail with many errors.
Repro:
cd /tmp
git clone https://github.com/apple/swift-nio.git
git reset 9b230f89a412663901fa06fc214eaa69204def1e # today's main tip
docker run -it --rm --privileged -v "$PWD:$PWD" -w "$PWD" swiftlang/swift:nightly-main-bionic swift build --build-tests

Output:
$ docker run -it --rm --privileged -v "$PWD:$PWD" -w "$PWD" swiftlang/swift:nightly-main-bionic swift build --build-tests
/Users/johannes/devel/swift-nio: warning: Open File failed on file: /root/.cache/clang/ModuleCache/modules.timestamp
Error: No such file or directory
Attempted again: 10 times
[1/1] Planning build

/Users/johannes/devel/swift-nio/Tests/NIOHTTP1Tests/TestUtils.swift:276:25: error: value of type 'sockaddr_in' has no member 'addressDescription'
            return addr.addressDescription()
                   ~~~~ ^~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOHTTP1Tests/TestUtils.swift:279:25: error: value of type 'sockaddr_in6' has no member 'addressDescription'
            return addr.addressDescription()
                   ~~~~ ^~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOHTTP1Tests/TestUtils.swift:276:25: error: value of type 'sockaddr_in' has no member 'addressDescription'
            return addr.addressDescription()
                   ~~~~ ^~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOHTTP1Tests/TestUtils.swift:279:25: error: value of type 'sockaddr_in6' has no member 'addressDescription'
            return addr.addressDescription()
                   ~~~~ ^~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOHTTP1Tests/TestUtils.swift:276:25: error: value of type 'sockaddr_in' has no member 'addressDescription'
            return addr.addressDescription()
                   ~~~~ ^~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOHTTP1Tests/TestUtils.swift:279:25: error: value of type 'sockaddr_in6' has no member 'addressDescription'
            return addr.addressDescription()
                   ~~~~ ^~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOHTTP1Tests/TestUtils.swift:276:25: error: value of type 'sockaddr_in' has no member 'addressDescription'
            return addr.addressDescription()
                   ~~~~ ^~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOHTTP1Tests/TestUtils.swift:279:25: error: value of type 'sockaddr_in6' has no member 'addressDescription'
            return addr.addressDescription()
                   ~~~~ ^~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOHTTP1Tests/TestUtils.swift:276:25: error: value of type 'sockaddr_in' has no member 'addressDescription'
            return addr.addressDescription()
                   ~~~~ ^~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOHTTP1Tests/TestUtils.swift:279:25: error: value of type 'sockaddr_in6' has no member 'addressDescription'
            return addr.addressDescription()
                   ~~~~ ^~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:89:25: error: value of type 'sockaddr_in6' has no member 'addressDescription'
        let s = address.addressDescription()
                ~~~~~~~ ^~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:180:40: error: value of type 'sockaddr_in' has no member 'withMutableSockAddr'
        var firstCopy = firstIPAddress.withMutableSockAddr { (addr, size) -> sockaddr_in in
                        ~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:184:42: error: value of type 'sockaddr_in6' has no member 'withMutableSockAddr'
        var secondCopy = secondIPAddress.withMutableSockAddr { (addr, size) -> sockaddr_in6 in
                         ~~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:225:24: error: value of type 'sockaddr_in' has no member 'withMutableSockAddr'
        firstIPAddress.withMutableSockAddr { (addr, size) -> Void in
        ~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:230:25: error: value of type 'sockaddr_in6' has no member 'withMutableSockAddr'
        secondIPAddress.withMutableSockAddr { (addr, size) -> Void in
        ~~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:275:28: error: value of type 'sockaddr_storage' has no member 'convert'
            return storage.convert()
                   ~~~~~~~ ^~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:281:28: error: value of type 'sockaddr_storage' has no member 'convert'
            return storage.convert()
                   ~~~~~~~ ^~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:287:28: error: value of type 'sockaddr_storage' has no member 'convert'
            return storage.convert()
                   ~~~~~~~ ^~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:318:28: error: value of type 'sockaddr_in' has no member 'withSockAddr'
            firstIPAddress.withSockAddr { innerAddr, innerSize in
            ~~~~~~~~~~~~~~ ^~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:325:29: error: value of type 'sockaddr_in6' has no member 'withSockAddr'
            secondIPAddress.withSockAddr { innerAddr, innerSize in
            ~~~~~~~~~~~~~~~ ^~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:455:17: error: value of type 'sockaddr_storage' has no member 'withMutableSockAddr'
        storage.withMutableSockAddr { (addr, _) in
        ~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:89:25: error: value of type 'sockaddr_in6' has no member 'addressDescription'
        let s = address.addressDescription()
                ~~~~~~~ ^~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:180:40: error: value of type 'sockaddr_in' has no member 'withMutableSockAddr'
        var firstCopy = firstIPAddress.withMutableSockAddr { (addr, size) -> sockaddr_in in
                        ~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:184:42: error: value of type 'sockaddr_in6' has no member 'withMutableSockAddr'
        var secondCopy = secondIPAddress.withMutableSockAddr { (addr, size) -> sockaddr_in6 in
                         ~~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:225:24: error: value of type 'sockaddr_in' has no member 'withMutableSockAddr'
        firstIPAddress.withMutableSockAddr { (addr, size) -> Void in
        ~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:230:25: error: value of type 'sockaddr_in6' has no member 'withMutableSockAddr'
        secondIPAddress.withMutableSockAddr { (addr, size) -> Void in
        ~~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:275:28: error: value of type 'sockaddr_storage' has no member 'convert'
            return storage.convert()
                   ~~~~~~~ ^~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:281:28: error: value of type 'sockaddr_storage' has no member 'convert'
            return storage.convert()
                   ~~~~~~~ ^~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:287:28: error: value of type 'sockaddr_storage' has no member 'convert'
            return storage.convert()
                   ~~~~~~~ ^~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:318:28: error: value of type 'sockaddr_in' has no member 'withSockAddr'
            firstIPAddress.withSockAddr { innerAddr, innerSize in
            ~~~~~~~~~~~~~~ ^~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:325:29: error: value of type 'sockaddr_in6' has no member 'withSockAddr'
            secondIPAddress.withSockAddr { innerAddr, innerSize in
            ~~~~~~~~~~~~~~~ ^~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:455:17: error: value of type 'sockaddr_storage' has no member 'withMutableSockAddr'
        storage.withMutableSockAddr { (addr, _) in
        ~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:89:25: error: value of type 'sockaddr_in6' has no member 'addressDescription'
        let s = address.addressDescription()
                ~~~~~~~ ^~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:180:40: error: value of type 'sockaddr_in' has no member 'withMutableSockAddr'
        var firstCopy = firstIPAddress.withMutableSockAddr { (addr, size) -> sockaddr_in in
                        ~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:184:42: error: value of type 'sockaddr_in6' has no member 'withMutableSockAddr'
        var secondCopy = secondIPAddress.withMutableSockAddr { (addr, size) -> sockaddr_in6 in
                         ~~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:225:24: error: value of type 'sockaddr_in' has no member 'withMutableSockAddr'
        firstIPAddress.withMutableSockAddr { (addr, size) -> Void in
        ~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:230:25: error: value of type 'sockaddr_in6' has no member 'withMutableSockAddr'
        secondIPAddress.withMutableSockAddr { (addr, size) -> Void in
        ~~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:275:28: error: value of type 'sockaddr_storage' has no member 'convert'
            return storage.convert()
                   ~~~~~~~ ^~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:281:28: error: value of type 'sockaddr_storage' has no member 'convert'
            return storage.convert()
                   ~~~~~~~ ^~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:287:28: error: value of type 'sockaddr_storage' has no member 'convert'
            return storage.convert()
                   ~~~~~~~ ^~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:318:28: error: value of type 'sockaddr_in' has no member 'withSockAddr'
            firstIPAddress.withSockAddr { innerAddr, innerSize in
            ~~~~~~~~~~~~~~ ^~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:325:29: error: value of type 'sockaddr_in6' has no member 'withSockAddr'
            secondIPAddress.withSockAddr { innerAddr, innerSize in
            ~~~~~~~~~~~~~~~ ^~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:455:17: error: value of type 'sockaddr_storage' has no member 'withMutableSockAddr'
        storage.withMutableSockAddr { (addr, _) in
        ~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:89:25: error: value of type 'sockaddr_in6' has no member 'addressDescription'
        let s = address.addressDescription()
                ~~~~~~~ ^~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:180:40: error: value of type 'sockaddr_in' has no member 'withMutableSockAddr'
        var firstCopy = firstIPAddress.withMutableSockAddr { (addr, size) -> sockaddr_in in
                        ~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:184:42: error: value of type 'sockaddr_in6' has no member 'withMutableSockAddr'
        var secondCopy = secondIPAddress.withMutableSockAddr { (addr, size) -> sockaddr_in6 in
                         ~~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:225:24: error: value of type 'sockaddr_in' has no member 'withMutableSockAddr'
        firstIPAddress.withMutableSockAddr { (addr, size) -> Void in
        ~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:230:25: error: value of type 'sockaddr_in6' has no member 'withMutableSockAddr'
        secondIPAddress.withMutableSockAddr { (addr, size) -> Void in
        ~~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:275:28: error: value of type 'sockaddr_storage' has no member 'convert'
            return storage.convert()
                   ~~~~~~~ ^~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:281:28: error: value of type 'sockaddr_storage' has no member 'convert'
            return storage.convert()
                   ~~~~~~~ ^~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:287:28: error: value of type 'sockaddr_storage' has no member 'convert'
            return storage.convert()
                   ~~~~~~~ ^~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:318:28: error: value of type 'sockaddr_in' has no member 'withSockAddr'
            firstIPAddress.withSockAddr { innerAddr, innerSize in
            ~~~~~~~~~~~~~~ ^~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:325:29: error: value of type 'sockaddr_in6' has no member 'withSockAddr'
            secondIPAddress.withSockAddr { innerAddr, innerSize in
            ~~~~~~~~~~~~~~~ ^~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:455:17: error: value of type 'sockaddr_storage' has no member 'withMutableSockAddr'
        storage.withMutableSockAddr { (addr, _) in
        ~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:89:25: error: value of type 'sockaddr_in6' has no member 'addressDescription'
        let s = address.addressDescription()
                ~~~~~~~ ^~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:180:40: error: value of type 'sockaddr_in' has no member 'withMutableSockAddr'
        var firstCopy = firstIPAddress.withMutableSockAddr { (addr, size) -> sockaddr_in in
                        ~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:184:42: error: value of type 'sockaddr_in6' has no member 'withMutableSockAddr'
        var secondCopy = secondIPAddress.withMutableSockAddr { (addr, size) -> sockaddr_in6 in
                         ~~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:225:24: error: value of type 'sockaddr_in' has no member 'withMutableSockAddr'
        firstIPAddress.withMutableSockAddr { (addr, size) -> Void in
        ~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:230:25: error: value of type 'sockaddr_in6' has no member 'withMutableSockAddr'
        secondIPAddress.withMutableSockAddr { (addr, size) -> Void in
        ~~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:275:28: error: value of type 'sockaddr_storage' has no member 'convert'
            return storage.convert()
                   ~~~~~~~ ^~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:281:28: error: value of type 'sockaddr_storage' has no member 'convert'
            return storage.convert()
                   ~~~~~~~ ^~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:287:28: error: value of type 'sockaddr_storage' has no member 'convert'
            return storage.convert()
                   ~~~~~~~ ^~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:318:28: error: value of type 'sockaddr_in' has no member 'withSockAddr'
            firstIPAddress.withSockAddr { innerAddr, innerSize in
            ~~~~~~~~~~~~~~ ^~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:325:29: error: value of type 'sockaddr_in6' has no member 'withSockAddr'
            secondIPAddress.withSockAddr { innerAddr, innerSize in
            ~~~~~~~~~~~~~~~ ^~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:455:17: error: value of type 'sockaddr_storage' has no member 'withMutableSockAddr'
        storage.withMutableSockAddr { (addr, _) in
        ~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:89:25: error: value of type 'sockaddr_in6' has no member 'addressDescription'
        let s = address.addressDescription()
                ~~~~~~~ ^~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:180:40: error: value of type 'sockaddr_in' has no member 'withMutableSockAddr'
        var firstCopy = firstIPAddress.withMutableSockAddr { (addr, size) -> sockaddr_in in
                        ~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:184:42: error: value of type 'sockaddr_in6' has no member 'withMutableSockAddr'
        var secondCopy = secondIPAddress.withMutableSockAddr { (addr, size) -> sockaddr_in6 in
                         ~~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:225:24: error: value of type 'sockaddr_in' has no member 'withMutableSockAddr'
        firstIPAddress.withMutableSockAddr { (addr, size) -> Void in
        ~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:230:25: error: value of type 'sockaddr_in6' has no member 'withMutableSockAddr'
        secondIPAddress.withMutableSockAddr { (addr, size) -> Void in
        ~~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:275:28: error: value of type 'sockaddr_storage' has no member 'convert'
            return storage.convert()
                   ~~~~~~~ ^~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:281:28: error: value of type 'sockaddr_storage' has no member 'convert'
            return storage.convert()
                   ~~~~~~~ ^~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:287:28: error: value of type 'sockaddr_storage' has no member 'convert'
            return storage.convert()
                   ~~~~~~~ ^~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:318:28: error: value of type 'sockaddr_in' has no member 'withSockAddr'
            firstIPAddress.withSockAddr { innerAddr, innerSize in
            ~~~~~~~~~~~~~~ ^~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:325:29: error: value of type 'sockaddr_in6' has no member 'withSockAddr'
            secondIPAddress.withSockAddr { innerAddr, innerSize in
            ~~~~~~~~~~~~~~~ ^~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:455:17: error: value of type 'sockaddr_storage' has no member 'withMutableSockAddr'
        storage.withMutableSockAddr { (addr, _) in
        ~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:89:25: error: value of type 'sockaddr_in6' has no member 'addressDescription'
        let s = address.addressDescription()
                ~~~~~~~ ^~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:180:40: error: value of type 'sockaddr_in' has no member 'withMutableSockAddr'
        var firstCopy = firstIPAddress.withMutableSockAddr { (addr, size) -> sockaddr_in in
                        ~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:184:42: error: value of type 'sockaddr_in6' has no member 'withMutableSockAddr'
        var secondCopy = secondIPAddress.withMutableSockAddr { (addr, size) -> sockaddr_in6 in
                         ~~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:225:24: error: value of type 'sockaddr_in' has no member 'withMutableSockAddr'
        firstIPAddress.withMutableSockAddr { (addr, size) -> Void in
        ~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:230:25: error: value of type 'sockaddr_in6' has no member 'withMutableSockAddr'
        secondIPAddress.withMutableSockAddr { (addr, size) -> Void in
        ~~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:275:28: error: value of type 'sockaddr_storage' has no member 'convert'
            return storage.convert()
                   ~~~~~~~ ^~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:281:28: error: value of type 'sockaddr_storage' has no member 'convert'
            return storage.convert()
                   ~~~~~~~ ^~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:287:28: error: value of type 'sockaddr_storage' has no member 'convert'
            return storage.convert()
                   ~~~~~~~ ^~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:318:28: error: value of type 'sockaddr_in' has no member 'withSockAddr'
            firstIPAddress.withSockAddr { innerAddr, innerSize in
            ~~~~~~~~~~~~~~ ^~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:325:29: error: value of type 'sockaddr_in6' has no member 'withSockAddr'
            secondIPAddress.withSockAddr { innerAddr, innerSize in
            ~~~~~~~~~~~~~~~ ^~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:455:17: error: value of type 'sockaddr_storage' has no member 'withMutableSockAddr'
        storage.withMutableSockAddr { (addr, _) in
        ~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:89:25: error: value of type 'sockaddr_in6' has no member 'addressDescription'
        let s = address.addressDescription()
                ~~~~~~~ ^~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:180:40: error: value of type 'sockaddr_in' has no member 'withMutableSockAddr'
        var firstCopy = firstIPAddress.withMutableSockAddr { (addr, size) -> sockaddr_in in
                        ~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:184:42: error: value of type 'sockaddr_in6' has no member 'withMutableSockAddr'
        var secondCopy = secondIPAddress.withMutableSockAddr { (addr, size) -> sockaddr_in6 in
                         ~~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:225:24: error: value of type 'sockaddr_in' has no member 'withMutableSockAddr'
        firstIPAddress.withMutableSockAddr { (addr, size) -> Void in
        ~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:230:25: error: value of type 'sockaddr_in6' has no member 'withMutableSockAddr'
        secondIPAddress.withMutableSockAddr { (addr, size) -> Void in
        ~~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:275:28: error: value of type 'sockaddr_storage' has no member 'convert'
            return storage.convert()
                   ~~~~~~~ ^~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:281:28: error: value of type 'sockaddr_storage' has no member 'convert'
            return storage.convert()
                   ~~~~~~~ ^~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:287:28: error: value of type 'sockaddr_storage' has no member 'convert'
            return storage.convert()
                   ~~~~~~~ ^~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:318:28: error: value of type 'sockaddr_in' has no member 'withSockAddr'
            firstIPAddress.withSockAddr { innerAddr, innerSize in
            ~~~~~~~~~~~~~~ ^~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:325:29: error: value of type 'sockaddr_in6' has no member 'withSockAddr'
            secondIPAddress.withSockAddr { innerAddr, innerSize in
            ~~~~~~~~~~~~~~~ ^~~~~~~~~~~~
/Users/johannes/devel/swift-nio/Tests/NIOTests/SocketAddressTest.swift:455:17: error: value of type 'sockaddr_storage' has no member 'withMutableSockAddr'
        storage.withMutableSockAddr { (addr, _) in
        ~~~~~~~ ^~~~~~~~~~~~~~~~~~~

Fixed by : https://github.com/apple/swift/pull/39252 in 5.5+
@weissi reopen if you still have any problems


parsl.load() with no config parameter can only be called once per python session

Describe the bug
parsl.load() with no config parameter can only be called once per interactive session.
This makes interactive use in notebooks awkward because the notebook cannot be replayed.
To Reproduce
import parsl
parsl.load()
parsl.load()

The second parsl.load() will raise RuntimeError: Config has already been loaded
Expected behavior
This command should work as many times as I want to run it.
Environment
master e282e114ba43c31d9a173895e6cbbc3b4f71531c
The test suite deals with this situation (which happens in local-mode tests) by creating a new config using a fresh config function instead of re-using existing configs.

Actually, this error come from needing to run a parsl.clear() before the second parsl.load().


[FEATURE] SPA style links?

Is it possible to do an SPA-style link such as <nuxt-link> or <router-link> ... or is Saber meant to be used with regular anchor tags?

<router-link> should work

Confirmed. <router-link> does indeed work. Thanks!


Fix compilation errors in VS, add move constructor and assignment operator

Fixes #2
Besides fixing compilation in VS, I have also added a move constructor and a move assignment operator to the Bitmap class. Now the rule of 5 is satisfied and the code may perform better in specific circumstances.

Thank you so much for your contribution  :+1:

And I thank you for instant feedback! I am very happy that I could help improve this project.


Timeout Error After Following Installation Instructions

After installing im receiving this error

I have the locales set in svr cfg, started under ox_lib, basically everything stated in the installation is done including the provides esx_skin and skinchanger

its everytime someone loads in, relogging multiple times does not fix

Issues for actual issues related to code, not for support. Use discord for support


botocore does not ignore credential_process when that configuration value is blank (empty string)

Describe the bug
The AWS CLI documentation on changing configuration settings using commands says:

To remove a setting, use an empty string as the value, or manually delete the setting in your config and credentials files in a text editor.

However, if one sets credential_process to the empty string, botocore neither removes the configuration variable from the configuration file nor ignores its value.  Instead, subsequent invocations of the AWS CLI or botocore library result in an IndexError when botocore.credentials.ProcessProvider._retrieve_credentials_using() passes an empty list derived from the empty string value to subprocess.Popen() at botocore/credentials.py line 1019.
Expected Behavior
botocore (and by extension the AWS CLI) should act as if the credential_process configuration variable is unset when it has an empty string value as described in the AWS CLI documentation linked above.
$ rm ~/.aws/*
$ aws configure set credential_process "" --profile test
$ cat ~/.aws/config
[profile test]
credential_process =
$ aws s3api list-buckets --profile test

Unable to locate credentials. You can configure credentials by running "aws configure".

Current Behavior
One cannot remove the credential_process setting without editing the configuration file.
$ rm ~/.aws/*
$ aws configure set credential_process "" --profile test
$ cat ~/.aws/config
[profile test]
credential_process =
$ aws s3api list-buckets --profile test

list index out of range

Reproduction Steps
I've trimmed the output to focus on the expected behavior (NoCredentialsError in botocore.auth.add_auth() when no credentials are set) versus the current behavior (IndexError in subprocess._execute_child() when credentials_process is set to the empty string).
$ rm -rf ~/.aws
$ python3.11 -m venv .venv
$ source .venv/bin/activate
$ pip install awscli
$ aws configure set credential_process "" --profile test
$ python
>>> import botocore.session
>>> session = botocore.session.get_session()
>>> client = session.create_client('ec2', region_name='us-west-2')
>>> for reservation in client.describe_instances()['Reservations']:
...     for instance in reservation['Instances']:
...         print(instance['InstanceId'])
...
botocore.exceptions.NoCredentialsError: Unable to locate credentials
>>> exit()
$ env AWS_DEFAULT_PROFILE=test python
>>> import botocore.session
>>> session = botocore.session.get_session()
IndexError: list index out of range

Possible Solution
The simplest fix may be to treat the value of credential_process as a boolean when deciding whether to use it in botocore.credentials.ProcessProvider.load() at botocore/credentials.py line 997.  The current behavior of botocore as described above is obviously wrong.
While one might also modify awscli.customizations.configure.writer.ConfigFileWriter._update_section_contents() to delete configuration variables with empty string values, some configuration variables have different behavior when they do not exist versus when they are set to the empty string, e.g., cli_pager.  I think the required logic to handle these cases would require too much effort to maintain for this approach to be worthwhile.  Or one might define an aws configure subcommand that deletes configuration variables, but that just shifts the maintenance burden of when to delete a configuration variable versus when to set it to the empty string from the ConfigFileWriter code to the AWS CLI or botocore documentation.
Additional Information/Context
I didn't realize that AWS CLI version 2 uses its own version of botocore (cf. https://github.com/aws/aws-cli/pull/6494).  However, the problematic behavior is identical.
SDK version used
botocore 1.34.18 and AWS CLI 1.32.18, botocore 2.0.0dev155 and AWS CLI 2.15.10
Environment details (OS name and version, etc.)
Python 3.11.7 installed via MacPorts on macOS 12.7.1 (x86_64)

Hi @rdctmeconomou, thanks for this detailed bug report.  I was able to reproduce this behavior.  After talking with the team, we came to the conclusion that the documentation is pretty misleading here.  Setting a value to an empty string to remove a configuration option does not work for every option, and as you pointed out, causes issues for some.  Given this information, we intend to remove that line from the documentation.  At this time, our intention is to create an aws configure unset command in the future as the official way to remove configuration options.  However, in the meantime, the best way to remove an option would be to manually delete it from the config file in a text editor.  Please let me know if you have any follow-up questions.


AttributeError when connecting to OpenCV-camera

Hi @jacopoabramo ,
I just tested napari-live-recording again and after clicking on "Connect" to my "Default Camera (OpenCV)", there is an error message popping up:
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
~\miniconda3\envs\nap-dev-bio2\lib\site-packages\napari_live_recording\_dock_widget.py in _on_connect_clicked(self=)
    303                 self._set_widgets_enabled(True)
    304                 self.camera_pixel_type_combobox.currentTextChanged.connect(self._on_pixel_format_changed)
--> 305                 self._set_default_roi()
        self._set_default_roi = >
    306             else:
    307                 raise CameraError(f"Error in opening {self.camera.get_name()}")

~\miniconda3\envs\nap-dev-bio2\lib\site-packages\napari_live_recording\_dock_widget.py in _set_default_roi(self=)
    428     def _set_default_roi(self):
    429         self.roi = self.camera.get_sensor_range()
--> 430         self.camera_roi_x_offset_spinbox.setValue(self.roi.offset_x)
        self.camera_roi_x_offset_spinbox.setValue =
        self.roi.offset_x = undefined
    431         self.camera_roi_y_offset_spinbox.setValue(self.roi.offset_y)
    432         self.camera_roi_x_offset_spinbox.setSingleStep(self.roi.ofs_x_step)

AttributeError: 'NoneType' object has no attribute 'offset_x'

To reproduce: I just started napari, the live recoding plugin, selected the camera and clicked on "Connect".

Afterwards, when I click the start recording button, the plugin works nicely.
Let me know if I can help tracing down that error message.
Happy holidays!
Best,
Robert

Hi @haesleinhuepf, I hope you had happy holidays as well. I apologize for the terrible delay, I didn't had much time to spend on this. I've attempted to fix this issue in version 0.1.7, please give it a try to see if it works out.
The ROI handling for OpenCV still is not optimal but now it should nevertheless work (after setting the ROI the first time, the subsequent changes to the ROI are applied immediately. It's not a big of a deal but that's not how it's supposed to work so I will look into that).
Also I should mention that I removed the cv2.waitKey function which was creating some problems as you mentioned in #5, let me know if this fixes it or it breaks things down.

Closing issue.


v4.0.0 just hangs

😦 https://travis-ci.org/ming-codes/ember-ui-kit/builds/239776698
Even in local runs too. It looks like the browser never connects.

Did you include a call to the new start function? https://github.com/ember-cli/ember-cli-qunit#upgrading

😅 just saw there's a bunch of closed issues of the same problem.


Animation recorder: Error in console when recording MonoBehavior scripts or third party plugin components

Having a custom script assign to my object and set the recorder to record it, we get errors in the console. Also true for cinemachine components:
Error:
ArgumentException: Cannot marshal CinemachineMixingCamera to a native Unity::Type!
UnityEditor.Experimental.Recorder.Input.AnimationInput.BeginRecording (UnityEngine.Recorder.RecordingSession session) (at Assets/Unity Technologies/Recorder/Framework/Inputs/Animation/Editor/AnimationInput.cs:17)
UnityEngine.Recorder.Recorder.SignalInputsOfStage (ERecordingSessionStage stage, UnityEngine.Recorder.RecordingSession session) (at Assets/Unity Technologies/Recorder/Framework/Core/Engine/Recorder.cs:155)
UnityEngine.Recorder.RecordingSession.BeginRecording () (at Assets/Unity Technologies/Recorder/Framework/Core/Engine/RecordingSession.cs:72)
UnityEditor.Recorder.RecorderWindow.StartRecording (Boolean autoExitPlayMode) (at Assets/Unity Technologies/Recorder/Framework/Core/Editor/RecorderWindow.cs:254)
UnityEditor.Recorder.RecorderWindow.DelayedStartRecording () (at Assets/Unity Technologies/Recorder/Framework/Core/Editor/RecorderWindow.cs:237)
UnityEditor.Recorder.RecorderWindow.OnGUI () (at Assets/Unity Technologies/Recorder/Framework/Core/Editor/RecorderWindow.cs:92)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

Issue Tracker link: https://issuetracker.unity3d.com/issues/animation-recorder-error-in-console-when-recording-custom-or-third-party-component

Unity issue. closing it here.


Kafka zookeepers support

It would be great if it was possible to provide q list of zookeepers instead of or as another option to brokers while reading Kafka stream.
KafkaSourceConfig
case def apply(brokerList: String, consumerGroup: String, autoOffsetReset: String, enableAutoCommit: Boolean): KafkaSourceConfig
brokerList or zookeeperList (new option)
Thank you.
Roman.

I believe Zookeeper has been dropped from Kafka now.


[aws-json] Migrate SNS ConfirmSubscription API

Now we don't have any smoke test for ConfirmSubscription because to perform the complete ConfirmSubscription feature requires the email destination and HTTP server.
Additionally, currently Subscribe API does not support "pending" status and don't send an email even if the endpoint is an email address.

Hi @Admiral-Piett, we tried to migrate the API but we have few comments. Could you please check them?

Now we don't have any smoke test for ConfirmSubscription because to perform the complete ConfirmSubscription feature requires the email destination and HTTP server. Additionally, currently Subscribe API does not support "pending" status and don't send an email even if the endpoint is an email address.

That's ok since this is an internal endpoint anyway.  I'm fine to skip that one for now.  Thank you!


OpenSSL / Python error during build on OpenSUSE Leap 15.0

I am trying to build Visit from source on an OpenSUSE Leap 15.0 platform. My steps so far:

downloading the Visit 3.0.2 source code
downloading the build_visit3_0_2 installation script
running the script: "./build_visit3_0_2"

I am getting the following error repeatedly:
Processing bsd license.
[build_visit invocation arguments]
Fortran support for thirdparty libraries disabled.
------------------------------------------------------------
./build_visit3_0_2
Started: Mo 14. Okt 16:08:36 CEST 2019
------------------------------------------------------------
enabling any dependent libraries
ERROR: library openssl was not set python depends on it, please enable

"zypper search openssl" shows me that the following openssl versions marked with "i" in the beginning are installed:
`S  | Name                            | Zusammenfassung                                                              | Typ
---+---------------------------------+------------------------------------------------------------------------------+-----------
   | gambas3-gb-openssl              | The Gambas openssl component                                                 | Paket
   | ghc-HsOpenSSL                   | Partial OpenSSL binding for Haskell                                          | Paket
   | ghc-HsOpenSSL-devel             | Haskell HsOpenSSL library development files                                  | Paket
   | ghc-HsOpenSSL-x509-system       | Use the system's native CA certificate store with HsOpenSSL                  | Paket
   | ghc-HsOpenSSL-x509-system-devel | Haskell HsOpenSSL-x509-system library development files                      | Paket
   | ghc-cryptonite-openssl          | Crypto stuff using OpenSSL cryptographic library                             | Paket
   | ghc-cryptonite-openssl-devel    | Haskell cryptonite-openssl library development files                         | Paket
   | ghc-hopenssl                    | FFI Bindings to OpenSSL's EVP Digest Interface                               | Paket
   | ghc-hopenssl-devel              | Haskell hopenssl library development files                                   | Paket
   | ghc-http-client-openssl         | Http-client backend using the OpenSSL library                                | Paket
   | ghc-http-client-openssl-devel   | Haskell http-client-openssl library development files                        | Paket
   | ghc-mysql-haskell-openssl       | TLS support for mysql-haskell package using openssl                          | Paket
   | ghc-mysql-haskell-openssl-devel | Haskell mysql-haskell-openssl library development files                      | Paket
   | ghc-openssl-streams             | OpenSSL network support for io-streams                                       | Paket
   | ghc-openssl-streams-devel       | Haskell openssl-streams library development files                            | Paket
   | ghc-soap-openssl                | TLS-enabled SOAP transport (using openssl bindings)                          | Paket
   | ghc-soap-openssl-devel          | Haskell soap-openssl library development files                               | Paket
   | ghc-tcp-streams-openssl         | Tcp streams using openssl for tls support                                    | Paket
   | ghc-tcp-streams-openssl-devel   | Haskell tcp-streams-openssl library development files                        | Paket
   | libopenssl-1_0_0-devel          | Development files for OpenSSL                                                | Paket
   | libopenssl-1_0_0-devel-32bit    | Development files for OpenSSL                                                | Paket
i  | libopenssl-1_1-devel            | Development files for OpenSSL                                                | Paket
   | libopenssl-1_1-devel-32bit      | Development files for OpenSSL                                                | Paket
i+ | libopenssl-devel                | Enthält Dateien und Bibliotheken, die zum Programmieren benötigt werden      | Paket
i  | libopenssl1_0_0                 | Secure Sockets and Transport Layer Security                                  | Paket
i+ | libopenssl1_0_0-32bit           | Secure Sockets and Transport Layer Security                                  | Paket
   | libopenssl1_0_0-hmac            | HMAC files for FIPS-140-2 integrity checking of the openssl shared libraries | Paket
   | libopenssl1_0_0-hmac-32bit      | HMAC files for FIPS-140-2 integrity checking of the openssl shared libraries | Paket
   | libopenssl1_0_0-steam           | Secure Sockets and Transport Layer Security for steam                        | Paket
   | libopenssl1_0_0-steam-32bit     | Secure Sockets and Transport Layer Security for steam                        | Paket
i  | libopenssl1_1                   | Secure Sockets and Transport Layer Security                                  | Paket
i  | libopenssl1_1-32bit             | Secure Sockets and Transport Layer Security                                  | Paket
   | libopenssl1_1-hmac              | HMAC files for FIPS-140-2 integrity checking of the openssl shared libraries | Paket
   | libopenssl1_1-hmac-32bit        | HMAC files for FIPS-140-2 integrity checking of the openssl shared libraries | Paket
   | libxmlsec1-openssl1             | OpenSSL crypto plugin for XML Security Library                               | Paket
i  | openssl                         | Secure Sockets and Transport Layer Security                                  | Paket
   | openssl                         | Secure Sockets and Transport Layer Security                                  | Quellpaket
   | openssl-1_0_0                   | Secure Sockets and Transport Layer Security                                  | Paket
   | openssl-1_0_0                   | Secure Sockets and Transport Layer Security                                  | Quellpaket
   | openssl-1_0_0-cavs              | CAVS testing framework and utilities                                         | Paket
   | openssl-1_0_0-doc               | Additional Package Documentation                                             | Paket
i  | openssl-1_1                     | Secure Sockets and Transport Layer Security                                  | Paket
   | openssl-1_1                     | Secure Sockets and Transport Layer Security                                  | Quellpaket
   | openssl-1_1-doc                 | Additional Package Documentation                                             | Paket
   | openssl-engine-libp11           | Library Implementing a Small Layer on Top of PKCS#11 API                     | Paket
   | openssl-ibmpkcs11               | OpenSSL Dynamic PKCS #11 Engine                                              | Paket
   | openssl_tpm_engine              | OpenSSL TPM interface engine plugin                                          | Paket
   | perl-Crypt-OpenSSL-Bignum       | OpenSSL's multiprecision integer arithmetic                                  | Paket
   | perl-Crypt-OpenSSL-RSA          | RSA encoding and decoding, using the openSSL libraries                       | Paket
   | perl-Crypt-OpenSSL-Random       | Routines for accessing the OpenSSL pseudo-random number generator            | Paket
   | php7-openssl                    | OpenSSL integration for PHP                                                  | Paket
   | python-pyOpenSSL                | Python wrapper module around the OpenSSL library                             | Quellpaket
   | python-pyOpenSSL-doc            | Documentation for python-pyOpenSSL                                           | Paket
i  | python2-pyOpenSSL               | Python wrapper module around the OpenSSL library                             | Paket
i  | python3-pyOpenSSL               | Python wrapper module around the OpenSSL library                             | Paket
   | xmlsec1-openssl-devel           | OpenSSL crypto plugin for XML Security Library                               | Paket ``

My current python version is 2.7.14.
Thanks in advance!

You need to add "--openssl" to the command line for build_visit. I will enhance build_visit so that you don't need to specify this, since it's required.


'CGrid_geo' object has no attribute 'Vtransform'

Good day.
The above-mentioned error happened shortly after running this code line (from notebook manual) :
lonp, latp, zp, t, T0, U, V = tracpy.run.run(tp, date, lon0, lat0)
error:  'CGrid_geo' object has no attribute 'Vtransform'

Hi @TKzee2027! Unfortunately I'm not developing this package anymore. I would suggest you look into ocean parcels as an actively-developing package.

Hi Kristen
Thank you for getting back to me.
I would certainly explore the ocean parcels.
With kind regards
TK
On Wed, 30 Jun 2021, 00:29 Kristen Thyng, @.***> wrote:

Hi @TKzee2027 https://github.com/TKzee2027! Unfortunately I'm not
developing this package anymore. I would suggest you look into ocean
parcels https://oceanparcels.org/ as an actively-developing package.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kthyng/tracpy/issues/13#issuecomment-870961122, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ATGLESJKP5ZJO6KYXRHFCN3TVJCL5ANCNFSM47OCSGWA
.

NOTE:
Parcels is pretty cool, but there are other options as well. Depending on your use case,  PyGNOME may be a good option:
https://github.com/NOAA-ORR-ERD/PyGnome
Don't be distracted by all the oil spill stuff -- at its core it's a particle tracker that supports a wide variety of ocean model grids.
And it's a framework for adding arbitrary attributes and process to the particles, which can be used for a variety of purposes other than oil :-)

Thank you so much, Chris.
I will explore the PyGnome too - heard about it last night at the
Copernicus MarineData4America workshop.
Once again, many thanks.
Tshikana
On Wed, Jun 30, 2021 at 6:54 PM Chris Barker @.***>
wrote:

NOTE:
Parcels is pretty cool, but there are other options as well. Depending on
your use case, PyGNOME may be a good option:
https://github.com/NOAA-ORR-ERD/PyGnome
Don't be distracted by all the oil spill stuff -- at its core it's a
particle tracker that supports a wide variety of ocean model grids.
And it's a framework for adding arbitrary attributes and process to the
particles, which can be used for a variety of purposes other than oil :-)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kthyng/tracpy/issues/13#issuecomment-871572248, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ATGLESLRR5EBVY6442T3EBDTVND5PANCNFSM47OCSGWA
.

Thanks @ChrisBarker-NOAA — good recommendation.


Support currency swaps with fxLinkedNotionalSchedule in the FpML template

Currently, the FpML template only supports interest rate swaps with the same currency on all legs. We need to extend this to support currency swaps, which is used by an external sample trade.

[x] Implement support for several currencies.
[x] Implement fxLinkedNotionalSchedule, which refers to a base currency notional defined in a different swap leg: https://www.fpml.org/spec/fpml-5-11-3-lcwd-1/html/confirmation/schemaDocumentation/schemas/fpml-ird-5-11_xsd/complexTypes/Calculation/fxLinkedNotionalSchedule.html
[x] Implement sample trade as a test.

This does not yet include principal exchange, which will be solved in a separate PR: https://github.com/digital-asset/daml-finance/issues/312

Implemented here: https://github.com/digital-asset/daml-finance/pull/313


Missing important parameter AzureSignTool

Just a couple of items:
In order to complete the AzureSignTool as its built, you must give the tenant ID with parameter "-kvt (--azure-key-vault-tenant-id)". Without it, it will fail.
So, the command should now look something like this:
AzureSignTool sign -kvt "<tenantID>" -kvu "https://contosoexpenses-blog.vault.azure.net/" -kvi "64fae35e-cb84-4b9f-86eb-5170d169316d" -kvs "this-is-the-secret" -kvc "MyCertificate" -tr http://timestamp.digicert.com -v .\MyContosoApp.msix
Also (suggestion) - should note that these parameters are aliases. If they would like more information on AzureSignTool, run AzureSignTool  sign --help or visit the links provided earlier in the article referencing the Open Source project.
Thank you!

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

ID: c7f544e5-da81-b214-b1c9-76fa0d024f37
Version Independent ID: cc9299c0-cbf0-9283-6f81-11ee96c489c0
Content: MSIX and CI/CD Pipeline signing with Azure Key Vault - MSIX
Content Source: msix-src/desktop/cicd-keyvault.md
Product: msix
GitHub Login: @Huios
Microsoft Alias: tajimha

Any updates on this? Should be a pretty quick fix - or if you have any feedback, please let me know.

The docs have been updated.


[BUG] Open ID and multi auth don't create valid cookies for pre-authenticated requests

What is the bug?
In the authentication handler, the code first looks for an authorization header before looking for credentials in the cookie to determine if the request is authenticated.
Code: https://github.com/opensearch-project/security-dashboards-plugin/blob/main/server/auth/types/authentication_type.ts#L113
If an authorization header is found, a cookie is constructed with the authorization header value as the credentials.
Code: https://github.com/opensearch-project/security-dashboards-plugin/blob/main/server/auth/types/authentication_type.ts#L118
This way, subsequent requests will be unauthenticated even if the authorization header is missing for some reason.
However, for Open ID and when multi auth is enabled, the constructed cookie is not valid and subsequent requests will be unauthenticated.
Open ID
The cookie is constructed here: https://github.com/opensearch-project/security-dashboards-plugin/blob/main/server/auth/types/openid/openid_auth.ts#L146
Then, the cookie is validated here: https://github.com/opensearch-project/security-dashboards-plugin/blob/main/server/auth/types/openid/openid_auth.ts#L158
Please note that the expires_at attribute is missing when the cookie is constructed, which then leads to the cookie being considered invalid.
After a regular login, the expires_at attribute is read from the idToken and added to the cookie.
Multi auth
Here, the constructed cookie is empty.
https://github.com/opensearch-project/security-dashboards-plugin/blob/main/server/auth/types/multiple/multi_auth.ts#L129
I'm not sure if this is intentional. It may be hard to derive the authentication type from just the header value, so maybe that's the reason why the getCookie method does not defer to another auth type in this case.
How can one reproduce the bug?
Steps to reproduce the behavior:

For Open ID, use a valid Bearer token in the authorization header. I used the Chrome extension ModHeader to do this.
Open Dashboards without explicitly logging in. You should be able to see Dashboards as an authenticated user.
Note that the security_authentication cookie is created
Now, remove the authorization header and reload the page.
You will be redirected to the login form

For multi auth, you need to enable it in opensearch_dashboards.yml:
opensearch_security.auth.multiple_auth_enabled: true
opensearch_security.auth.type: [basicauth, openid]

What is the expected behavior?
At least for Open ID I would expect that the user is still logged in, even without the header. The credentials should be in the cookie at this point. This works with e.g. SAML.
For multi authentication, the empty cookie looks a bit more intentional, so maybe this behaviour was by choice. Otherwise I'd have expected to be logged in with a valid cookie.
What is your host/environment?

OS: Mac OS
Version I used the main branch from this repository
Plugins

[Triage] Thank you @jochen-kressin for opening this issue. This seems like an excellent find and something that we should address to have the expected behavior.


[FR] Using globally unique identifiers for most of objects.

Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find a similar feature request

Problem statement
The current solution is that each object in the InvenTree system has ID (primary key) in form of number, which is incremental. Due to, the ID (for example) id=1 is used in many tables. It would be better if the ID were replaced with a globally unique code that would only appear once in the entire database and all other instances of the InvenTree installation.
This aims to solve situations where, for example, one item (label) comes in touch with a different InvenTree instance, which would then consider it as a different item. Due to the architecture of the tool and the use of Django models, there is not much danger of IDs (database links) being mistakenly swapped due to a programming error.
These U-IDs could then be displayed on all reports to make it easy to trace back to the original source. The disadvantage is that all QR/barcodes will be significantly larger in terms of data and complexity.
This approach of handling with codes also creates possibilities for semi-automatic transfer of items between instances (companies) that uses InvenTree.
Suggested solution
In the first phase, I would propose adding the generation of unique objects to selected items through inventree mixins. Due to use of Django and PostgreSQL database, it seems useful to use UUIDs, as they are natively supported.
wiki
Django support
Postgress support
Then (after implementing 1st phase), it is should be considering using these identifiers as primary keys, which would mean replacing (minimally add support) all the links.
I cant quantify the impact on the system/database performance when using UUIDs as primary keys. I think this step can be decided after implementation of UUIDs as a second unique code in the database and are somehow used within the system - being referenced, printed on labels, ...
Describe alternatives you've considered
I don't have an alternative for that. It is very general solution.
Examples of other systems
A similar system is used in the OpenIntranet storage system, where this approach seems to be very successful and efficient. This eliminates the possibility change/confusion of identifiers.
OpenIntranet uses the MongoDB NoSQL database, which natively supports ObjectID identifiers. Subsequently, these ObjectID objects are used for all component/item/position identifications throughout the system.
Do you want to develop this?
I'm not decided yet.

@roman-dvorak this is reasonable, and thanks for your well-reasoned discussion here.
Currently we support two distinct types of barcodes to be associated with a database object:

Simple "JSON" data such as {"part": 3} as you have seen
Association with external barcode (i.e. assign an incoming barcode to a stock item as received from a supplier)

An additional barcode type (UUID) would need to be able to work alongside these existing types. This is fine, we have a plugin system for recognizing different barcodes and can just extend this.

#5208 is related

not stale

not stale


[REVIEW] shrikanta8

GitHub Profile Link
https://github.com/shrikanta8

Nice work!  I think the only thing I would suggest is maybe making the text a little bigger as it seems a bit lost in scale with the other items. 👍

Hey, @shrikanta8 , thank you for opening an Issue.
Here are some of my recommendations -

Add a more descriptive Bio.
Instead of pinning 6 repos, try to pin top 2/4 repos.
Add Twitter handle under bio.
More contributions :)

If you need any kind of help, ping us here or on Discord server

Hey, @shrikanta8 , thank you for opening an Issue.
Here are some of my recommendations -

Add a more descriptive Bio.

Instead of pinning 6 repos, try to pin top 2/4 repos.

Add Twitter handle under bio.

More contributions :)

If you need any kind of help, ping us here or on Discord server

Agree with that :)

tysm @weeyin83 @Pradumnasaraf @schmelto
i will edit it :)

Looks great, some suggestions

profile picture to be of you (or something unique)
add socials to GitHub section on the left
maybe too much is animated


Istio Sidecars adding large amounts of latency

(NOTE: This is used to report product bugs:
To report a security vulnerability, please visit https://istio.io/about/security-vulnerabilities
To ask questions about how to use Istio, please visit https://discuss.istio.io)
Bug description
I've been working on rolling out Istio onto a production setup. We have Istio sidecars with namespace injection. We are still using ALB Ingress in this case. When the sidecars were rolled out we noticed a large increase in p95, p99, p99.9 latency coming from the ALB's reported metrics. These increases of latency are on the order of seconds, which is quite concerning.
[ ] Docs
[X] Installation
[X] Networking
[X] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
Expected behavior
Sidecar injection should only add minimal amounts of latency to our installation.
Steps to reproduce the bug
Create a GraphQL application with an ALB Ingress. Inject Istio Sidecars. Monitor Network performance from Cloudwatch within the AWS console.

This dashboard we have is plotting simple HTTP requests which aren't expected to increase in duration much. We also have websockets for this application but they did not appear to be impacted by the installation.
Version (include the output of istioctl version --remote and kubectl version --short and helm version --short if you used Helm)
client version: 1.10.0
control plane version: 1.9.1
data plane version: 1.9.1 (65 proxies)

How was Istio installed?
Istio operator install with the following manifest
apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
metadata:
  namespace: istio-system
  name: istiocontrolplane
spec:
  values:
    telemetry:
      v2:
        prometheus:
          configOverride:
            outboundSidecar:
              debug: false
              stat_prefix: istio
              metrics:
                - name: request_duration_milliseconds
                  dimensions:
                    cache_status: response.headers['X-Proxy-Cache']
  profile: default
  meshConfig:
    accessLogFile: /dev/stdout
    enableTracing: true
    defaultConfig:
      tracing:
        sampling: 100
        zipkin:
          address: opentelemetry-collector.opentelemetry-collector:9411
  components:
    pilot:
      k8s:
        hpaSpec:
          minReplicas: 2
        replicaCount: 2

Environment where the bug was observed (cloud vendor, OS, etc)
AWS EKS
Server Version: version.Info{Major:"1", Minor:"16+", GitVersion:"v1.16.15-eks-ad4801", GitCommit:"ad4801fd44fe0f125c8d13f1b1d4827e8884476d", GitTreeState:"clean", BuildDate:"2020-10-20T23:27:12Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}

Additionally, please consider running istioctl bug-report and attach the generated cluster-state tarball to this issue.
Refer cluster state archive for more details.

The graph says rolling out of Istio increases latency by hundreds of seconds? That does not seem to be right. Does this agree with Istio stats?

I have some data from Kiali that suggests this is the case. We also noticed that persistent connections may have been killed at the 5 minute mark, but we are unsure if this was related.
Below is two panels of response time for the same service. Slicing the data into response flags could reveal similar data.

We also noticed that persistent connections may have been killed at the 5 minute mark, but we are unsure if this was related.

That seems to be related, because the p99 with UC and UF are at 300s? I am not sure whether Kiali uses server stats or client stats, but have you compared client vs server istio stats latency? Is it possible that the application hangs and does not response properly? Envoy has an native stats upstream_rq_time which measures time spent at upstream application and can be exposed by https://istio.io/latest/docs/ops/configuration/telemetry/envoy-stats/ which should give an idea about whether envoy thinks the upstream app that spends all 300s.

Kiali was using client stats in this case. I took a look at envoy stats and can retrieve the following. I couldn't get upstream_rq_time -- it didn't seem to be exposed.
Here's some stats I retrieved. Note that I am obfuscating naming of our services.
cluster.xds-grpc.upstream_cx_connect_ms: P0(nan,0.0) P25(nan,0.0) P50(nan,0.0) P75(nan,0.0) P90(nan,1.08) P95(nan,7.04) P99(nan,7.088) P99.5(nan,7.094) P99.9(nan,7.0988) P100(nan,7.1)
cluster.xds-grpc.upstream_cx_length_ms: P0(nan,1600000.0) P25(nan,1691666.6666666667) P50(nan,1812500.0) P75(nan,1881250.0) P90(nan,1945000.0) P95(nan,1972500.0) P99(nan,1994500.0) P99.5(nan,1997250.0) P99.9(nan,1999450.0) P100(nan,2000000.0)

reporter=.=destination;.;source_workload=.=unknown;.;source_workload_namespace=.=unknown;.;source_principal=.=unknown;.;source_app=.=unknown;.;source_version=.=unknown;.;source_canonical_service=.=unknown;.;source_canonical_revision=.=latest;.;destination_workload=.=apigw;.;destination_workload_namespace=.=project-apigw-integration;.;destination_principal=.=unknown;.;destination_app=.=apigw;.;destination_version=.=unknown;.;destination_service=.=apigw.project-apigw-integration.svc.cluster.local;.;destination_service_name=.=apigw;.;destination_service_namespace=.=project-apigw-integration;.;destination_canonical_service=.=apigw;.;destination_canonical_revision=.=latest;.;request_protocol=.=http;.;response_flags=.=-;.;connection_security_policy=.=none;.;response_code=.=200;.;grpc_response_status=.=;.;destination_cluster=.=Kubernetes;.;source_cluster=.=unknown;.;istio_request_duration_milliseconds: P0(0.0,0.0) P25(0.0,1.0691546762589927) P50(1.025,54.2) P75(1.0625,200.27472527472528) P90(1.085,363.5000000000002) P95(1.0925,1110.3883495145628) P99(1.0985,1486.999999999989) P99.5(1.09925,3086.999999999989) P99.9(1.09985,5777.399999999989) P100(1.1,11000.0)
reporter=.=destination;.;source_workload=.=unknown;.;source_workload_namespace=.=unknown;.;source_principal=.=unknown;.;source_app=.=unknown;.;source_version=.=unknown;.;source_canonical_service=.=unknown;.;source_canonical_revision=.=latest;.;destination_workload=.=apigw;.;destination_workload_namespace=.=project-apigw-integration;.;destination_principal=.=unknown;.;destination_app=.=apigw;.;destination_version=.=unknown;.;destination_service=.=apigw.project-apigw-integration.svc.cluster.local;.;destination_service_name=.=apigw;.;destination_service_namespace=.=project-apigw-integration;.;destination_canonical_service=.=apigw;.;destination_canonical_revision=.=latest;.;request_protocol=.=http;.;response_flags=.=-;.;connection_security_policy=.=none;.;response_code=.=400;.;grpc_response_status=.=;.;destination_cluster=.=Kubernetes;.;source_cluster=.=unknown;.;istio_request_duration_milliseconds: P0(nan,7.0) P25(nan,7.05) P50(nan,7.1) P75(nan,33.5) P90(nan,33.8) P95(nan,33.9) P99(nan,33.98) P99.5(nan,33.99) P99.9(nan,33.998) P100(nan,34.0)
reporter=.=destination;.;source_workload=.=unknown;.;source_workload_namespace=.=unknown;.;source_principal=.=unknown;.;source_app=.=unknown;.;source_version=.=unknown;.;source_canonical_service=.=unknown;.;source_canonical_revision=.=latest;.;destination_workload=.=apigw;.;destination_workload_namespace=.=project-apigw-integration;.;destination_principal=.=unknown;.;destination_app=.=apigw;.;destination_version=.=unknown;.;destination_service=.=apigw.project-apigw-integration.svc.cluster.local;.;destination_service_name=.=apigw;.;destination_service_namespace=.=project-apigw-integration;.;destination_canonical_service=.=apigw;.;destination_canonical_revision=.=latest;.;request_protocol=.=http;.;response_flags=.=DC;.;connection_security_policy=.=none;.;response_code=.=0;.;grpc_response_status=.=;.;destination_cluster=.=Kubernetes;.;source_cluster=.=unknown;.;istio_request_duration_milliseconds: P0(nan,1000.0) P25(nan,59352.94117647059) P50(nan,59882.35294117647) P75(nan,60437.5) P90(nan,60775.0) P95(nan,60887.5) P99(nan,60977.5) P99.5(nan,60988.75) P99.9(nan,60997.75) P100(nan,61000.0)
reporter=.=destination;.;source_workload=.=unknown;.;source_workload_namespace=.=unknown;.;source_principal=.=unknown;.;source_app=.=unknown;.;source_version=.=unknown;.;source_canonical_service=.=unknown;.;source_canonical_revision=.=latest;.;destination_workload=.=apigw;.;destination_workload_namespace=.=project-apigw-integration;.;destination_principal=.=unknown;.;destination_app=.=apigw;.;destination_version=.=unknown;.;destination_service=.=apigw.project-apigw-integration.svc.cluster.local;.;destination_service_name=.=apigw;.;destination_service_namespace=.=project-apigw-integration;.;destination_canonical_service=.=apigw;.;destination_canonical_revision=.=latest;.;request_protocol=.=http;.;response_flags=.=DC;.;connection_security_policy=.=none;.;response_code=.=101;.;grpc_response_status=.=;.;destination_cluster=.=Kubernetes;.;source_cluster=.=unknown;.;istio_request_duration_milliseconds: P0(nan,64.0) P25(nan,64.5) P50(nan,65.0) P75(nan,1350000.0) P90(nan,1380000.0) P95(nan,1390000.0) P99(nan,1398000.0) P99.5(nan,1399000.0) P99.9(nan,1399800.0) P100(nan,1400000.0)
reporter=.=destination;.;source_workload=.=unknown;.;source_workload_namespace=.=unknown;.;source_principal=.=unknown;.;source_app=.=unknown;.;source_version=.=unknown;.;source_canonical_service=.=unknown;.;source_canonical_revision=.=latest;.;destination_workload=.=apigw;.;destination_workload_namespace=.=project-apigw-integration;.;destination_principal=.=unknown;.;destination_app=.=apigw;.;destination_version=.=unknown;.;destination_service=.=apigw.project-apigw-integration.svc.cluster.local;.;destination_service_name=.=apigw;.;destination_service_namespace=.=project-apigw-integration;.;destination_canonical_service=.=apigw;.;destination_canonical_revision=.=latest;.;request_protocol=.=http;.;response_flags=.=UC;.;connection_security_policy=.=none;.;response_code=.=503;.;grpc_response_status=.=;.;destination_cluster=.=Kubernetes;.;source_cluster=.=unknown;.;istio_request_duration_milliseconds: P0(nan,11000.0) P25(nan,33500.0) P50(nan,61000.0) P75(nan,82500.0) P90(nan,154000.00000000003) P95(nan,189000.0) P99(nan,205799.99999999997) P99.5(nan,207900.0) P99.9(nan,209579.99999999997) P100(nan,210000.0)

Closing this issue as it is resolved.
Istio sidecar injection does not have requests/limits that are equal to each other. Our application was running on Guaranteed QoS due to strict requirements about having enough resources available for GC and other application resource lifecycle management.
https://kubernetes.io/docs/tasks/configure-pod-container/quality-service-pod/#create-a-pod-that-gets-assigned-a-qos-class-of-guaranteed
With the Istio sidecar enabled, the application switched to Burstable QoS without us being aware of it and thus caused the latencies seen here. The fix was to include the following manifest in our Deployment's specification so that our application remains with Guaranteed QoS.
      initContainers: # The init container is defined to override the default injection template to ensure the Pod gets Guaranteed QoS
      - name: istio-init
        image: auto
        resources:
          limits:
            cpu: 1
            memory: 256Mi
          requests:
            cpu: 1
            memory: 256Mi
      containers:
      - name: istio-proxy # This Istio Proxy container is predefined here to override the default injection template to ensure the Pod gets Guaranteed QoS
        image: auto
        resources:
          limits:
            cpu: 1
            memory: 256Mi
          requests:
            cpu: 1
            memory: 256Mi

This is an interesting side effect... To help me understand, what happens is that because of changing of QoS class, your app pods are scheduled on node which does not have enough resources to handle burst CPU from GC, and thus causing the latency? I think this worth documented somewhere on istio.io.

This goes a little beyond the scope of Istio sidecars, but that is the idea. We run a high throughput GraphQL backend service based on NodeJS. We found through performance tuning and testing that we needed dedicated cores to perform event loop and Garbage collection (https://v8.dev/blog/concurrent-marking).
Thus prior to introducing Istio sidecars we created a manifest that gave our application Guaranteed QoS so that it had a dedicated core to perform on instead of several smaller cores
Example this application with guaranteed QoS
kubectl -n my-application-prod exec -it my-application-deadbeef123-xyz12 -c my-application -- /bin/sh -c 'grep Cpus_allowed /proc/self/status; grep . /sys/fs/cgroup/cpuset/cpuset.cpus /sys/fs/cgroup/cpuset/cpuset.cpu_exclusive'
Cpus_allowed:	0000,80000080
Cpus_allowed_list:	7,31

When automatic istio sidecar injection was enabled, the sidecars did not have container requests == limits, which means they will be scheduled with Burstable QoS and have several CPUs available. We believe this impacts GC and event loop lag due to having to switch between each CPU and compete for resources on a node.
kubectl -n my-application-prod exec -it my-application-deadbeef123-xyz12 -c my-application -- /bin/sh -c 'grep Cpus_allowed /proc/self/status; grep . /sys/fs/cgroup/cpuset/cpuset.cpus /sys/fs/cgroup/cpuset/cpuset.cpu_exclusive'
Cpus_allowed:	fff8,8ffff88f
Cpus_allowed_list:	0-3,7,11-27,31,35-47
/sys/fs/cgroup/cpuset/cpuset.cpus:0-3,7,11-27,31,35-47
/sys/fs/cgroup/cpuset/cpuset.cpu_exclusive:0

Because of the number and varying sizes of CPUs available we found this gets in the way of our application being able to perform GC and event loops. The performance degradation metrics are not due directly to Istio in this case, but our application suffering from being Burstable QoS and thus having latency issues.


Feature Request: Dry Run

Would be great if there was a "dry run" mode for this which just printed out which packages would be caught by the filters.

That makes sense, will add :+1:

Implemented in 0.3.0!


nodejs_14: is EOL on 2023-04-30, nodejs_16: goes EOL during 23.05 release

Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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/)
23.05 Release Notes (or backporting 22.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.

I think this warrants some maintainer pings.

Head's up. Your package is using nodejs_14, which we are going to mark vulnerable (because EOL) before the 23.05 branch-off.

onlykey @kalbasit
ldgallery @pacien
ntfy-sh @arjan-s
botamusique @infinisil
airfield @offlinehacker
vadmicn.vscode-lldb @superherointj
archisteamfarm @legendofmiracles
spacegun @kampka
matrix-recorder @7c6f434c
cz-cli @lovesegfault
base16-builder @garbas
mjolnir @jojosch
psitransfer @hyshka
ethercalc @iblech
whitebophir @iblech
haste-server @mkg20001
navidrome @squalus

#229953

jellyfin @nyanloutre @minijackson @purcell @jojosch
mx-puppet-discord @expipiplus1
ariang @Stunkymonkey
newman @freezeboy
elm @turbomack @jonringer

thanks for ping. I will take care of node modules.

We might have to pull nodejs_16 as well, given that it EOLS in 4 months. cc @turboMaCk

Please migrate away from nodejs_16 as well, since its lifetime ends during the NixOS 23.05 release.

n8n @freezeboy @K900
bitwarden @amarshall @Kiwi
meshcentral @lheckemann
plausible @happysalada
hedgedoc @SuperSandro2000
mirakurun @midchildan
outline @cab404 @yrd
epgstation @midchildan
peertube @immae @Izorkin @matthiasbeyer @mohe2015 @stevenroose
code-server @offlinehacker @henkery
audiobookshelf @jvanbruegge
openvscode-server @dguenther @ghuntley @emilytrau
discourse @talyz
whitebophir @iblech
kibana @offlinehacker @basvandijk
docker-compose-language-service @natsukium
electron-fiddle @andersk
github-runner @veehaitch @newAM @kfollesdal @aanderse @zimbatm
netlify-cli @roberth
wiki-js @Ma27

@mweinelt I've stepped away from being a maintainer of nixpkga and I don't feel like picking it up again at the moment. If spacegun blocks this issue feel free to remove it.

Update Peertube - https://github.com/NixOS/nixpkgs/pull/218599

n8n upstream is on 16, it seems to run OK on 18, but I'm inclined to leave it on 16 for now and upgrade to 18 mid-cycle if necessary - there's a lot of plugins I'm not personally using or testing.

I'm no longer able to maintain mx-puppet-discord. Perhaps @GovanifY would care to take over?

hedgedoc @SuperSandro2000

I don't think I have time to look at this, also given that updates to hedgedoc in the past where highly problematic and killed the web editor multiple times due to bugs and oversights in node2nix mixing together prod and dev dependencies.

(I tried to find a matrix-recorder fork updated to the new step in the Node.js treadmill and I have failed)

electron-fiddle: #231557

Currently taking a look at wiki.js (because there are apparently no plans for v2 to fix nodejs 18 support and in fact there's a runtime error that can be trivially reproduced with the VM test in nixpkgs). Since I doubt that v3 will come up soonish, I'll try to fix this on my own.

I'm no longer able to maintain mx-puppet-discord. Perhaps @GovanifY would care to take over?

Ah sure will take a look whenever I have a moment

Since the 23.05 branch-off is happening in the next couple of days, I'm inclined to only mark nodejs_14 as EOL.
What do you think?

We can't support nodejs_16 through NixOS 23.05, so it has to be marked EOL as well, as we cannot really cut support mid-release.

I am in favor of marking Node.js 14, 16 EOL.

yeah, but nodejs_16 will reach EOL at September 11th, a little over a month before the 23.11 release, so I think it's tolerable to maintain it until then

We'll support 23.05 until 2023/12/31.


Area doesn't clear, but no sensor is active

I have a 'main floor' area which is occupied with 4 rooms (they are set by placing those entities in the 'main floor' area, like this:

Now the 'main floor' area remains active, even though the 4 rooms that fill this area are not occupied.

The 'main floor' does see that there are no active sensors, but does not clear the area.
Any ideas what I could try?
I've removed the entities from the area and re-added them, restarted and tried a couple of different settings (clearout, excluding).

Thanks! I thought that would have worked, since there is an 'interior' and 'exterior' as well.
You thoughts have helped though, I just made a group of the 4 binary sensors from the areas on the main floor.
When the 4th becomes inactive (state 'off'), the group has the same state.


Firmeware Dump: Window Sensor

Generic Tuya Window Sensor from aliexpress

ltchiptool_bk72xx_2024-09-14_18-18-53.zip

Added as Tuya Generic IH-MC01 Window Sensor v1.0.10


Use cloudscale.ch Terraform provider datasources when appropriate

Currently, users of the module must specify matching privnet uuid, subnet uuid, and CIDR when wanting to deploy a cluster into an existing cloudscale.ch private network.
In the latest release (3.2.0), the cloudscale.ch Terraform provider supports data sources, cf. https://registry.terraform.io/providers/cloudscale-ch/cloudscale/latest/docs/data-sources/network and https://github.com/cloudscale-ch/terraform-provider-cloudscale/issues/40. Therefore we should refactor the module to make use of the datasources when deploying a cluster into an existing private network.
The privnet cidr and subnet uuid should be optional when an existing privnet uuid is provided. If either cidr or subnet uuid is provided, that value is used to look up the subnet in the privnet datasource. Otherwise the first subnet of the provided privnet is used for the cluster.

This was solved in #58. We used a simpler approach of requiring the subnet uuid, instead of trying to infer the missing variables if one is set. As this feature is rarely used this should be good enough for now.
I do not see any other obvious use cases for datasources, so I will close this issue


Can't execute ninja run on Ubuntu 17.10

I am unable to run ninja run on ubuntu 17.10 as it throughs following error, python version is 2.7.14

[0/1] Running external command run.
exec: No such file or directory
ERROR: "adb push" returned with value 1
FAILED: meson-run
/usr/bin/python3 /usr/share/meson/meson --internal commandrunner /home/ateeb/StudioProjects/scrcpy /home/ateeb/StudioProjects/scrcpy/x '' /usr/share/meson/mesonintrospect scripts/run-scrcpy.sh
ninja: build stopped: subcommand failed.

Do you have "adb" in your path?

thanks @stek29  It worked like a charm :+1: