Build failure: kdsoap

error: 1 dependencies of derivation '/nix/store/zfzm5x1vdp3n3ii6c87v0f4iyn9zixz9-kio-extras-24.01.90.drv' failed to build
error: 1 dependencies of derivation '/nix/store/87pcm9hrk09ynf34b8hb4mzadgsnqr9v-plasma-workspace-5.92.0.drv' failed to build
error: 1 dependencies of derivation '/nix/store/49li22brk3x3ydg4w9pa6swhajiibawv-system-path.drv' failed to build

$ nix log /nix/store/jdzknnw210fsz9mm9zp6zmhpn3a0hwr6-kdsoap-ws-discovery-client-0.3.0.drv
warning: The interpretation of store paths arguments ending in `.drv` recently changed. If this command is now failing try again with '/nix/store/jdzknnw210fsz9mm9zp6zmhpn3a0hwr6-kdsoap-ws-discovery-client-0.3.0.drv^*'
@nix { "action": "setPhase", "phase": "qtPreHook" }
Running phase: qtPreHook
@nix { "action": "setPhase", "phase": "unpackPhase" }
Running phase: unpackPhase
unpacking source archive /nix/store/1ncca5swmn902l9b8ba9yn13xfn7mm0y-kdsoap-ws-discovery-client-0.3.0.tar.xz
source root is kdsoap-ws-discovery-client-0.3.0
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file kdsoap-ws-discovery-client-0.3.0/wsdl/www.w3.org/2006/03/addressing/ws-addr.xsd.license
@nix { "action": "setPhase", "phase": "patchPhase" }
Running phase: patchPhase
@nix { "action": "setPhase", "phase": "updateAutotoolsGnuConfigScriptsPhase" }
Running phase: updateAutotoolsGnuConfigScriptsPhase
@nix { "action": "setPhase", "phase": "configurePhase" }
Running phase: configurePhase
fixing cmake files...
cmake flags: -DCMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_BUILD_TYPE=Release ->
-- The C compiler identification is GNU 13.2.0
-- The CXX compiler identification is GNU 13.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /nix/store/xq8920m5mbd83vdlydwli7qsh67gfm5v-gcc-wrapper-13.2.0/bin/gcc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /nix/store/xq8920m5mbd83vdlydwli7qsh67gfm5v-gcc-wrapper-13.2.0/bin/g++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
--

Installing in /nix/store/8dmy0ghmbqb2rpssxz3fdpri8c7sd6hm-kdsoap-ws-discovery-client-0.3.0. Run /build/kdsoap-ws-discovery-client-0.3.0/build/prefix.sh to set the>
-- Looking for __GLIBC__
-- Looking for __GLIBC__ - found
-- Performing Test _OFFT_IS_64BIT
-- Performing Test _OFFT_IS_64BIT - Success
-- Performing Test HAVE_DATE_TIME
-- Performing Test HAVE_DATE_TIME - Success
-- Performing Test HAVE_STDATOMIC
-- Performing Test HAVE_STDATOMIC - Success
-- Found WrapAtomic: TRUE
-- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY
-- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY - Success
-- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY
-- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY - Success
-- Performing Test COMPILER_HAS_DEPRECATED_ATTR
-- Performing Test COMPILER_HAS_DEPRECATED_ATTR - Success
lines 1-45...skipping...
@nix { "action": "setPhase", "phase": "qtPreHook" }
Running phase: qtPreHook
@nix { "action": "setPhase", "phase": "unpackPhase" }
Running phase: unpackPhase
unpacking source archive /nix/store/1ncca5swmn902l9b8ba9yn13xfn7mm0y-kdsoap-ws-discovery-client-0.3.0.tar.xz
source root is kdsoap-ws-discovery-client-0.3.0
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file kdsoap-ws-discovery-client-0.3.0/wsdl/www.w3.org/2006/03/addressing/ws-addr.xsd.license
@nix { "action": "setPhase", "phase": "patchPhase" }
Running phase: patchPhase
@nix { "action": "setPhase", "phase": "updateAutotoolsGnuConfigScriptsPhase" }
Running phase: updateAutotoolsGnuConfigScriptsPhase
@nix { "action": "setPhase", "phase": "configurePhase" }
Running phase: configurePhase
fixing cmake files...
cmake flags: -DCMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTING=OFF -DCMAKE_INSTALL_LOCALEDIR=/nix/>
-- The C compiler identification is GNU 13.2.0
-- The CXX compiler identification is GNU 13.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /nix/store/xq8920m5mbd83vdlydwli7qsh67gfm5v-gcc-wrapper-13.2.0/bin/gcc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /nix/store/xq8920m5mbd83vdlydwli7qsh67gfm5v-gcc-wrapper-13.2.0/bin/g++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
--

Installing in /nix/store/8dmy0ghmbqb2rpssxz3fdpri8c7sd6hm-kdsoap-ws-discovery-client-0.3.0. Run /build/kdsoap-ws-discovery-client-0.3.0/build/prefix.sh to set the environment for kdsoap-ws-discovery-client.
-- Looking for __GLIBC__
-- Looking for __GLIBC__ - found
-- Performing Test _OFFT_IS_64BIT
-- Performing Test _OFFT_IS_64BIT - Success
-- Performing Test HAVE_DATE_TIME
-- Performing Test HAVE_DATE_TIME - Success
-- Performing Test HAVE_STDATOMIC
-- Performing Test HAVE_STDATOMIC - Success
-- Found WrapAtomic: TRUE
-- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY
-- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY - Success
-- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY
-- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY - Success
-- Performing Test COMPILER_HAS_DEPRECATED_ATTR
-- Performing Test COMPILER_HAS_DEPRECATED_ATTR - Success
-- Found Doxygen: /nix/store/bna88qwfx5h49di8a8ixcz4ijgknblbm-doxygen-1.9.8/bin/doxygen (found version "1.9.8") found components: doxygen missing components: dot mscgen dia
-- The following OPTIONAL packages have been found:

 * Qt6Xml (required version >= 5.9.0)
 * Qt6CoreTools (required version >= 6.6.1)
 * Doxygen

-- The following REQUIRED packages have been found:

 * ECM (required version >= 5.54.0), Extra CMake Modules., <https://develop.kde.org/products/frameworks/>
 * Qt6Core (required version >= 6.0.0)
 * Qt6Network (required version >= 6.0.0)
 * KDSoap-qt6 (required version >= 2.0.0), A Qt-based client-side and server-side SOAP component, <http://www.kdab.com/products/kd-soap>
   Support for SOAP client protocol
 * Qt6

-- The following features have been disabled:

 * QCH, API documentation in QCH format (for e.g. Qt Assistant, Qt Creator & KDevelop)

-- Configuring done (2.1s)
-- Generating done (0.0s)
CMake Warning:
  Manually-specified variables were not used by the project:

    CMAKE_EXPORT_NO_PACKAGE_REGISTRY
    CMAKE_POLICY_DEFAULT_CMP0025

-- Build files have been written to: /build/kdsoap-ws-discovery-client-0.3.0/build
cmake: enabled parallel building
cmake: enabled parallel installing
@nix { "action": "setPhase", "phase": "buildPhase" }
Running phase: buildPhase
build flags: -j32 SHELL=/nix/store/9vafkkic27k7m4934fpawl6yip3a6k4h-bash-5.2-p21/bin/bash
[  4%] Generate API documentation for docs
[  8%] Automatic MOC for target KDSoapWSDiscoveryClient
Doxygen version used: 1.9.8
Searching for include files...
Searching for example files...
Searching for images...
Searching for dot files...
Searching for msc files...
Searching for dia files...
Searching for files to exclude
Searching INPUT for files to process...
Reading and parsing tag files
Parsing files
Reading /build/kdsoap-ws-discovery-client-0.3.0/README.md...
Preprocessing /build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoveryclient.h...
Parsing file /build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoveryclient.h...
Preprocessing /build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoveryprobejob.h...
Parsing file /build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoveryprobejob.h...
Preprocessing /build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h...
Parsing file /build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h...
Preprocessing /build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoveryserviceaggregator.h...
Parsing file /build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoveryserviceaggregator.h...
Building macro definition list...
Building group list...
Building directory list...
Building namespace list...
Building file list...
Building class list...
Building concept list...
Computing nesting relations for classes...
Associating documentation with classes...
Associating documentation with concepts...
Associating documentation with modules...
Building example list...
Searching for enumerations...
Searching for documented typedefs...
Searching for members imported via using declarations...
Searching for included using directives...
Searching for documented variables...
Building interface member list...
Building member list...
Searching for friends...
Searching for documented defines...
Computing class inheritance relations...
Computing class usage relations...
Flushing cached template relations that have become invalid...
Computing class relations...
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:15: warning: Compound WSDiscoveryTargetService is not documented.
Add enum values to enums...
Searching for member function documentation...
Creating members for template instances...
Building page list...
Search for main page...
Computing page relations...
Determining the scope of groups...
Computing module relations...
Sorting lists...
Determining which enums are documented
Computing member relations...
Building full member lists recursively...
Adding members to member groups.
Computing member references...
Inheriting documentation...
Generating disk names...
Adding source references...
Adding xrefitems...
Sorting member lists...
Setting anonymous enum type...
Computing dependencies between directories...
Generating citations page...
Counting members...
Counting data structures...
Resolving user defined references...
Finding anchors and sections in the documentation...
Transferring function references...
Combining using relations...
Adding members to index pages...
Correcting members for VHDL...
Computing tooltip texts...
Generating style sheet...
Generating search indices...
Generating example documentation...
Generating file sources...
Generating code for file src/wsdiscoveryclient.h...
Generating code for file src/wsdiscoveryprobejob.h...
Generating code for file src/wsdiscoveryserviceaggregator.h...
Generating code for file src/wsdiscoverytargetservice.h...
Generating file documentation...
Generating page documentation...
Generating docs for page md_README...
Generating group documentation...
Generating class documentation...
Generating docs for compound WSDiscoveryClient...
Generating docs for compound WSDiscoveryProbeJob...
Generating docs for compound WSDiscoveryServiceAggregator...
Generating docs for compound WSDiscoveryTargetService...
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:19: warning: Member WSDiscoveryTargetService(const QString &endpointReference) (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:20: warning: Member WSDiscoveryTargetService(const WSDiscoveryTargetService &other) (function) of class WSDiscoveryTargetService is not docum>
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:23: warning: Member setEndpointReference(const QString &endpointReference) (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:24: warning: Member endpointReference() const (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:25: warning: Member typeList() const (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:26: warning: Member setTypeList(const QList< KDQName > &typeList) (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:27: warning: Member scopeList() const (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:28: warning: Member setScopeList(const QList< QUrl > &scopeList) (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:29: warning: Member xAddrList() const (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:30: warning: Member setXAddrList(const QList< QUrl > &xAddrList) (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:31: warning: Member lastSeen() const (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:32: warning: Member setLastSeen(const QDateTime &lastSeen) (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:33: warning: Member updateLastSeen() (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:35: warning: Member isMatchingType(const KDQName &matchingType) const (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:36: warning: Member isMatchingScope(const QUrl &matchingScope) const (function) of class WSDiscoveryTargetService is not documented.
Generating concept documentation...
Generating module documentation...
Generating namespace documentation...
Generating graph info page...
Generating directory documentation...
Generating index page...
Generating page index...
Generating topic index...
Generating module index...
Generating module member index...
Generating namespace index...
Generating namespace member index...
Generating concept index...
Generating annotated compound index...
Generating alphabetical compound index...
Generating hierarchical class index...
Generating member index...
Generating file index...
Generating file member index...
Generating example index...
finalizing index lists...
Preprocessing /build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoveryprobejob.h...
Parsing file /build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoveryprobejob.h...
Preprocessing /build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h...
Parsing file /build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h...
Preprocessing /build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoveryserviceaggregator.h...
Parsing file /build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoveryserviceaggregator.h...
Building macro definition list...
Building group list...
Building directory list...
Building namespace list...
Building file list...
Building class list...
Building concept list...
Computing nesting relations for classes...
Associating documentation with classes...
Associating documentation with concepts...
Associating documentation with modules...
Building example list...
Searching for enumerations...
Searching for documented typedefs...
Searching for members imported via using declarations...
Searching for included using directives...
Searching for documented variables...
Building interface member list...
Building member list...
Searching for friends...
Searching for documented defines...
Computing class inheritance relations...
Computing class usage relations...
Flushing cached template relations that have become invalid...
Computing class relations...
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:15: warning: Compound WSDiscoveryTargetService is not documented.
Add enum values to enums...
Searching for member function documentation...
Creating members for template instances...
Building page list...
Search for main page...
Computing page relations...
Determining the scope of groups...
Computing module relations...
Sorting lists...
Determining which enums are documented
Computing member relations...
Building full member lists recursively...
Adding members to member groups.
Computing member references...
Inheriting documentation...
Generating disk names...
Adding source references...
Adding xrefitems...
Sorting member lists...
Setting anonymous enum type...
Computing dependencies between directories...
Generating citations page...
Counting members...
Counting data structures...
Resolving user defined references...
Finding anchors and sections in the documentation...
Transferring function references...
Combining using relations...
Adding members to index pages...
Correcting members for VHDL...
Computing tooltip texts...
Generating style sheet...
Generating search indices...
Generating example documentation...
Generating file sources...
Generating code for file src/wsdiscoveryclient.h...
Generating code for file src/wsdiscoveryprobejob.h...
Generating code for file src/wsdiscoveryserviceaggregator.h...
Generating code for file src/wsdiscoverytargetservice.h...
Generating file documentation...
Generating page documentation...
Generating docs for page md_README...
Generating group documentation...
Generating class documentation...
Generating docs for compound WSDiscoveryClient...
Generating docs for compound WSDiscoveryProbeJob...
Generating docs for compound WSDiscoveryServiceAggregator...
Generating docs for compound WSDiscoveryTargetService...
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:19: warning: Member WSDiscoveryTargetService(const QString &endpointReference) (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:20: warning: Member WSDiscoveryTargetService(const WSDiscoveryTargetService &other) (function) of class WSDiscoveryTargetService is not docum>
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:23: warning: Member setEndpointReference(const QString &endpointReference) (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:24: warning: Member endpointReference() const (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:25: warning: Member typeList() const (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:26: warning: Member setTypeList(const QList< KDQName > &typeList) (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:27: warning: Member scopeList() const (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:28: warning: Member setScopeList(const QList< QUrl > &scopeList) (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:29: warning: Member xAddrList() const (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:30: warning: Member setXAddrList(const QList< QUrl > &xAddrList) (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:31: warning: Member lastSeen() const (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:32: warning: Member setLastSeen(const QDateTime &lastSeen) (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:33: warning: Member updateLastSeen() (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:35: warning: Member isMatchingType(const KDQName &matchingType) const (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:36: warning: Member isMatchingScope(const QUrl &matchingScope) const (function) of class WSDiscoveryTargetService is not documented.
Generating concept documentation...
Generating module documentation...
Generating namespace documentation...
Generating graph info page...
Generating directory documentation...
Generating index page...
Generating page index...
Generating topic index...
Generating module index...
Generating module member index...
Generating namespace index...
Generating namespace member index...
Generating concept index...
Generating annotated compound index...
Generating alphabetical compound index...
Generating hierarchical class index...
Generating member index...
Generating file index...
Generating file member index...
Generating example index...
finalizing index lists...
Building file list...
Building class list...
Building concept list...
Computing nesting relations for classes...
Associating documentation with classes...
Associating documentation with concepts...
Associating documentation with modules...
Building example list...
Searching for enumerations...
Searching for documented typedefs...
Searching for members imported via using declarations...
Searching for included using directives...
Searching for documented variables...
Building interface member list...
Building member list...
Searching for friends...
Searching for documented defines...
Computing class inheritance relations...
Computing class usage relations...
Flushing cached template relations that have become invalid...
Computing class relations...
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:15: warning: Compound WSDiscoveryTargetService is not documented.
Add enum values to enums...
Searching for member function documentation...
Creating members for template instances...
Building page list...
Search for main page...
Computing page relations...
Determining the scope of groups...
Computing module relations...
Sorting lists...
Determining which enums are documented
Computing member relations...
Building full member lists recursively...
Adding members to member groups.
Computing member references...
Inheriting documentation...
Generating disk names...
Adding source references...
Adding xrefitems...
Sorting member lists...
Setting anonymous enum type...
Computing dependencies between directories...
Generating citations page...
Counting members...
Counting data structures...
Resolving user defined references...
Finding anchors and sections in the documentation...
Transferring function references...
Combining using relations...
Adding members to index pages...
Correcting members for VHDL...
Computing tooltip texts...
Generating style sheet...
Generating search indices...
Generating example documentation...
Generating file sources...
Generating code for file src/wsdiscoveryclient.h...
Generating code for file src/wsdiscoveryprobejob.h...
Generating code for file src/wsdiscoveryserviceaggregator.h...
Generating code for file src/wsdiscoverytargetservice.h...
Generating file documentation...
Generating page documentation...
Generating docs for page md_README...
Generating group documentation...
Generating class documentation...
Generating docs for compound WSDiscoveryClient...
Generating docs for compound WSDiscoveryProbeJob...
Generating docs for compound WSDiscoveryServiceAggregator...
Generating docs for compound WSDiscoveryTargetService...
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:19: warning: Member WSDiscoveryTargetService(const QString &endpointReference) (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:20: warning: Member WSDiscoveryTargetService(const WSDiscoveryTargetService &other) (function) of class WSDiscoveryTargetService is not docum>
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:23: warning: Member setEndpointReference(const QString &endpointReference) (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:24: warning: Member endpointReference() const (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:25: warning: Member typeList() const (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:26: warning: Member setTypeList(const QList< KDQName > &typeList) (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:27: warning: Member scopeList() const (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:28: warning: Member setScopeList(const QList< QUrl > &scopeList) (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:29: warning: Member xAddrList() const (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:30: warning: Member setXAddrList(const QList< QUrl > &xAddrList) (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:31: warning: Member lastSeen() const (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:32: warning: Member setLastSeen(const QDateTime &lastSeen) (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:33: warning: Member updateLastSeen() (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:35: warning: Member isMatchingType(const KDQName &matchingType) const (function) of class WSDiscoveryTargetService is not documented.
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:36: warning: Member isMatchingScope(const QUrl &matchingScope) const (function) of class WSDiscoveryTargetService is not documented.
Generating concept documentation...
Generating module documentation...
Generating namespace documentation...
Generating graph info page...
Generating directory documentation...
Generating index page...
Generating page index...
Generating topic index...
Generating module index...
Generating module member index...
Generating namespace index...
Generating namespace member index...
Generating concept index...
Generating annotated compound index...
Generating alphabetical compound index...
Generating hierarchical class index...
Generating member index...
Generating file index...
Generating file member index...
Generating example index...
finalizing index lists...
writing tag file...
Running plantuml with JAVA...
type lookup cache used 65/65536 hits=68 misses=66
symbol lookup cache used 76/65536 hits=245 misses=76
finished...
[  8%] Built target docs
[  8%] Built target KDSoapWSDiscoveryClient_autogen
[ 12%] Generating wsdl_ws-discovery.h
[ 16%] Generating wsdl_wsdd-discovery-1.h
Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
Qt depends on a UTF-8 locale, and has switchedDetected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
If this causes problems, reconfigure your locale. See the locale(1) manual
for more information.
 to "C.UTF-8" instead.
If this causes problems, reconfigure your locale. See the locale(1) manual
for more information.
importing schema at http://schemas.xmlsoap.org/ws/2005/04/discovery/ws-discovery.xsd
importing schema at http://docs.oasis-open.org/ws-dd/discovery/1.1/os/wsdd-discovery-1.1-schema-os.xsd
Using import path '/build/kdsoap-ws-discovery-client-0.3.0/wsdl/schemas.xmlsoap.org//ws/2005/04/discovery/ws-discovery.xsd'
Using import path '/build/kdsoap-ws-discovery-client-0.3.0/wsdl/docs.oasis-open.org//ws-dd/discovery/1.1/os/wsdd-discovery-1.1-schema-os.xsd'
importing schema at http://schemas.xmlsoap.org/ws/2004/08/addressing
importing schema at http://www.w3.org/2006/03/addressing/ws-addr.xsd
Using import path '/build/kdsoap-ws-discovery-client-0.3.0/wsdl/schemas.xmlsoap.org//ws/2004/08/addressing'
Using import path '/build/kdsoap-ws-discovery-client-0.3.0/wsdl/www.w3.org//2006/03/addressing/ws-addr.xsd'
No service or binding tag found in the wsdl file, generating only messages
No service or binding tag found in the wsdl file, generating only messages
Converting 2 simple types
Converting 2 simple types
Converting 15 complex types
Converting 13 complex types
[ 20%] Generating moc_wsdl_ws-discovery.cpp
[ 25%] Generating wsdl_wsdd-discovery-1.cpp
[ 29%] Generating moc_wsdl_wsdd-discovery-1.cpp
[ 33%] Generating wsdl_ws-discovery.cpp
/build/kdsoap-ws-discovery-client-0.3.0/build/src/wsdl_ws-discovery.h: note: No relevant classes found. No output generated.
/build/kdsoap-ws-discovery-client-0.3.0/build/src/wsdl_wsdd-discovery-1.h: note: No relevant classes found. No output generated.
Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
If this causes problems, reconfigure your locale. See the locale(1) manual
for more information.
importing schema at http://docs.oasis-open.org/ws-dd/discovery/1.1/os/wsdd-discovery-1.1-schema-os.xsd
Using import path '/build/kdsoap-ws-discovery-client-0.3.0/wsdl/docs.oasis-open.org//ws-dd/discovery/1.1/os/wsdd-discovery-1.1-schema-os.xsd'
importing schema at http://www.w3.org/2006/03/addressing/ws-addr.xsd
Using import path '/build/kdsoap-ws-discovery-client-0.3.0/wsdl/www.w3.org//2006/03/addressing/ws-addr.xsd'
No service or binding tag found in the wsdl file, generating only messages
Converting 2 simple types
Converting 13 complex types
Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
If this causes problems, reconfigure your locale. See the locale(1) manual
for more information.
importing schema at http://schemas.xmlsoap.org/ws/2005/04/discovery/ws-discovery.xsd
Using import path '/build/kdsoap-ws-discovery-client-0.3.0/wsdl/schemas.xmlsoap.org//ws/2005/04/discovery/ws-discovery.xsd'
importing schema at http://schemas.xmlsoap.org/ws/2004/08/addressing
Using import path '/build/kdsoap-ws-discovery-client-0.3.0/wsdl/schemas.xmlsoap.org//ws/2004/08/addressing'
No service or binding tag found in the wsdl file, generating only messages
Converting 2 simple types
Converting 15 complex types
[ 37%] Building CXX object src/CMakeFiles/KDSoapWSDiscoveryClient.dir/wsdiscoveryclient.cpp.o
[ 41%] Building CXX object src/CMakeFiles/KDSoapWSDiscoveryClient.dir/wsdiscoveryprobejob.cpp.o
[ 50%] Building CXX object src/CMakeFiles/KDSoapWSDiscoveryClient.dir/wsdiscoveryserviceaggregator.cpp.o
[ 50%] Building CXX object src/CMakeFiles/KDSoapWSDiscoveryClient.dir/KDSoapWSDiscoveryClient_autogen/mocs_compilation.cpp.o
[ 54%] Building CXX object src/CMakeFiles/KDSoapWSDiscoveryClient.dir/wsdiscoverytargetservice.cpp.o
[ 58%] Building CXX object src/CMakeFiles/KDSoapWSDiscoveryClient.dir/loggingcategory.cpp.o
[ 62%] Building CXX object src/CMakeFiles/KDSoapWSDiscoveryClient.dir/wsdl_wsdd-discovery-1.cpp.o
[ 66%] Building CXX object src/CMakeFiles/KDSoapWSDiscoveryClient.dir/moc_wsdl_wsdd-discovery-1.cpp.o
[ 75%] Building CXX object src/CMakeFiles/KDSoapWSDiscoveryClient.dir/wsdl_ws-discovery.cpp.o
[ 75%] Building CXX object src/CMakeFiles/KDSoapWSDiscoveryClient.dir/moc_wsdl_ws-discovery.cpp.o
In file included from /build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoveryprobejob.cpp:5:
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoveryprobejob.h:9:10: fatal error: KDSoapClient/KDQName: No such file or directory
    9 | #include <KDSoapClient/KDQName>
      |          ^~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [src/CMakeFiles/KDSoapWSDiscoveryClient.dir/build.make:136: src/CMakeFiles/KDSoapWSDiscoveryClient.dir/wsdiscoveryprobejob.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
In file included from /build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.cpp:5:
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:9:10: fatal error: KDSoapClient/KDQName: No such file or directory
    9 | #include <KDSoapClient/KDQName>
      |          ^~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
In file included from /build/kdsoap-ws-discovery-client-0.3.0/build/src/wsdl_wsdd-discovery-1.cpp:7:
/build/kdsoap-ws-discovery-client-0.3.0/build/src/wsdl_wsdd-discovery-1.h:8:10: fatal error: KDSoapClient/KDSoapValue.h: No such file or directory
    8 | #include <KDSoapClient/KDSoapValue.h>
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [src/CMakeFiles/KDSoapWSDiscoveryClient.dir/build.make:150: src/CMakeFiles/KDSoapWSDiscoveryClient.dir/wsdiscoverytargetservice.cpp.o] Error 1
make[2]: *** [src/CMakeFiles/KDSoapWSDiscoveryClient.dir/build.make:192: src/CMakeFiles/KDSoapWSDiscoveryClient.dir/wsdl_wsdd-discovery-1.cpp.o] Error 1
In file included from /build/kdsoap-ws-discovery-client-0.3.0/build/src/wsdl_ws-discovery.cpp:7:
/build/kdsoap-ws-discovery-client-0.3.0/build/src/wsdl_ws-discovery.h:8:10: fatal error: KDSoapClient/KDSoapValue.h: No such file or directory
    8 | #include <KDSoapClient/KDSoapValue.h>
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [src/CMakeFiles/KDSoapWSDiscoveryClient.dir/build.make:220: src/CMakeFiles/KDSoapWSDiscoveryClient.dir/wsdl_ws-discovery.cpp.o] Error 1
In file included from /build/kdsoap-ws-discovery-client-0.3.0/build/src/KDSoapWSDiscoveryClient_autogen/EWIEGA46WW/moc_wsdiscoveryclient.cpp:9,
                 from /build/kdsoap-ws-discovery-client-0.3.0/build/src/KDSoapWSDiscoveryClient_autogen/mocs_compilation.cpp:2:
/build/kdsoap-ws-discovery-client-0.3.0/build/src/KDSoapWSDiscoveryClient_autogen/EWIEGA46WW/../../../../src/wsdiscoveryclient.h:13:10: fatal error: KDSoapClient/KDQName: No such file or directory
   13 | #include <KDSoapClient/KDQName>
      |          ^~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
In file included from /build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoveryserviceaggregator_p.h:9,
                 from /build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoveryserviceaggregator.cpp:7:
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoverytargetservice.h:9:10: fatal error: KDSoapClient/KDQName: No such file or directory
    9 | #include <KDSoapClient/KDQName>
      |          ^~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [src/CMakeFiles/KDSoapWSDiscoveryClient.dir/build.make:108: src/CMakeFiles/KDSoapWSDiscoveryClient.dir/KDSoapWSDiscoveryClient_autogen/mocs_compilation.cpp.o] Error 1
make[2]: *** [src/CMakeFiles/KDSoapWSDiscoveryClient.dir/build.make:164: src/CMakeFiles/KDSoapWSDiscoveryClient.dir/wsdiscoveryserviceaggregator.cpp.o] Error 1
In file included from /build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoveryclient.cpp:5:
/build/kdsoap-ws-discovery-client-0.3.0/src/wsdiscoveryclient.h:13:10: fatal error: KDSoapClient/KDQName: No such file or directory
   13 | #include <KDSoapClient/KDQName>
      |          ^~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [src/CMakeFiles/KDSoapWSDiscoveryClient.dir/build.make:122: src/CMakeFiles/KDSoapWSDiscoveryClient.dir/wsdiscoveryclient.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:233: src/CMakeFiles/KDSoapWSDiscoveryClient.dir/all] Error 2
make: *** [Makefile:136: all] Error 2

I'm still getting this error (I updated my flake to the latest nixpkgs and kde2nix)

nixos-unstable has not advanced past the fix yet.


fix content-type of response for /commit

this one changes the api docs for /commit to the actually used response content-type "application/json".
Signed-off-by: Tobias Gesellchen<EMAIL_ADDRESS>

@gesellix does this mean 1.19 used application/vnd.docker.raw-stream and since 1.20 it's application/json ? If you're able to would you mind referencing in the description the PR that introduced the actual change?

@tiborvass I wouldn't expect that the behaviour ever changed - but I didn't have a chance to verify an api <= 1.19, yet. I'll try if you like, but then the question arises at which version to stop checking for an actual change. Is 1.19 enough to check? Is 1.18 still in major use?
I'll try to find out as far backwards as possible and leave a note here, including an extended PR when necessary.

@gesellix you can force push on your existing branch to update this PR here no worries.
Yeah you'd have to go back till 1.12 i believe :S

@tiborvass I checked the source code down to v1.0.0/api 1.12 and updated the docs accordingly. I guess the application/vnd.docker.raw-stream content-type has been introduced through copy&paste.

@gesellix ok thanks LGTM

This is funny :)  LGTM

Could you please squash your commits down to one also?

@runcom sure, done.
@tiborvass welcome :)

Ping @thaJeztah for the merge :)

LGTM

thanks for the quick merge! afaik the commit needs to be cherry-picked into the docs branch, this is tracked somewhere else, right?


Warning: Management API authentication is disabled.

Bug Report
Current behavior
Prisma server deployed to ECS/Fargate emits the following log message constantly:
Warning: Management API authentication is disabled. To protect your management server you should provide one (not both) of the environment variables 'CLUSTER_PUBLIC_KEY' (asymmetric, deprecated soon) or PRISMA_MANAGEMENT_API_JWT_SECRET' (symmetric JWT).

Reproduction

MySQL CloudFormation template
ECS container running prismagraphql/prisma:1.8.3 image, RDS instance is mysql.
fargate CloudFormation template

Expected behavior?
I expect the management api auth mechanism to work as described.
Please let me know if more info is needed.
Thanks,
Peter

Thanks a lot for bringing this up! This is covered in this issue already: https://github.com/prismagraphql/prisma-templates/issues/7.
We'll soon look into improving this part of the template 🙂


Step 6.3 Issue

Good afternoon,
After completing all the steps, when I want to add the application to the teams catalog I get an error saying that there is already an application with the same app ID.

Could you help me?
Thank you.
Regards.

Hi @fbosiocedi ,
Thanks for raising the query. It seems that there is already an application installed to the same tenant with the same id. Please change the id parameter in the manifest and re-upload. Here is the reference.

Hi @fbosiocedi , Thanks for raising the query. It seems that there is already an application installed to the same tenant with the same id. Please change the id parameter in the manifest and re-upload. Here is the reference.

Thank you gsv022, I think that I need to change de ID in the appservice configuration. This ID should be the same, right?

Hi @fbosiocedi ,
If it is a user app that is giving the issue. Please create a new GUID, update the same in manifest and in app service configuration. Here is the reference.


Using tree packages of anvil

Hello, I'm starting to use Anvil and porting an existing app that use XML only. I need to use anvil-appcompat-v7, anvil-design and anvil-sdk15 packages, I have added the next code to gradle:
compile 'co.trikita:anvil-sdk15:0.2.0'
compile 'co.trikita:anvil-design:0.3.4'
compile 'co.trikita:anvil-appcompat-v7:0.3.4'

But, building throws this error: Error: more than one library with package name 'trikita.anvil', I'm doing it in the wrong way?

Currently the Anvil artefacts are a little bit broken since they do not have the latest fixes to deal with the clashing package names.
Ping @zserge - please update them :)

@carloslfu Published Anvil 0.3.5 with the support libraries included and having separate packages.
@tilal6991 Sorry, 0.4.0 will be released once we add recyclerview-v7 and thus finalize the support libraries in Anvil.

No need to apologise - the version number doesn't matter as long as there's some version out which works :)

Thanks @zserge .


Is it possible to set viewport instead of windowSize?

View port is much meaningful than window size.
When I set windowSize to 1024x768, I actually get the view port at size 991x768 which is not what I expected. If I can set the view port directly, it will be very helpful.
Thanks

no, there are no such ability because you need to do one more request to browser to calculate sizes for viewport. It's redundantly.
You can do it yourself in test by getting current viewport size and change window size you need

I see, thank you
-------- Original Message --------
On Oct 11, 2017, 5:40 PM, sipayrt wrote:

no, there are no such ability because you need to do one more request to browser to calculate sizes for viewport. It's redundantly.
You can do it yourself in test by getting current viewport size and change window size you need
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


[Feature][Task Plugin] add java task plugin.

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
The Java type plugin supports the Jar approach, providing dynamic parameter input for Resources, Libs resource files, and JVM parameters
The Java type plugin supports the WebUI custom Java code approach, providing Java classes to be compiled and executed on the fly
Use case
No response
Related issues
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

good job


ECS-Optimized AMIs don't report metrics to ECS

When I upgrade from my manual implementation of an ECS agent on RancherOS 0.3.3 to the ECS-Optimized RancherOS 0.4 version, my metrics drop off the face of the earth:

This may be an Amazon issue but I'm posting it here in case the new optimized implementation isn't capturing the host machine metrics correctly.
Amazon CloudWatch is still capturing CPU/Memory load correctly from the ec2 instances themselves and this is consistent across four different cluster implementations I've started with ros 0.4. I think the issue lies within the ECS agent implementation. Obviously this is a problem for anyone who uses ECS metrics on their CloudWatch alarms or auto-scaling configurations.

I find the same with the out of the box, ami-11740e7b :(

Reporting this is still an issue, ami-2504524f

Looks like v0.4.4 solves this issue. My metrics sprang back to life!


Error when enter random value during the begining of the game.

So during the begining of the game, there is a guy willing to give the player money. If you enter a random value, it causes and error.
Here is the error when I didn't enter anything.
Traceback (most recent call last):
  File "/data/data/com.termux/files/home/Documents/python_project/PythonTextRPG/main.py", line 5, in <module>
    E.start()
  File "/data/data/com.termux/files/home/Documents/python_project/PythonTextRPG/engine.py", line 1029, in start
    self.run()
  File "/data/data/com.termux/files/home/Documents/python_project/PythonTextRPG/engine.py", line 1033, in run
    self.update()
  File "/data/data/com.termux/files/home/Documents/python_project/PythonTextRPG/engine.py", line 1003, in update
    elif self.state == "quest": self.quest_menu()
                                ^^^^^^^^^^^^^^^^^
  File "/data/data/com.termux/files/home/Documents/python_project/PythonTextRPG/engine.py", line 384, in quest_menu
    if 'part' in quest[self.selected_quest][part]['option'][sel]:
                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^
KeyError: ''

I fixed this bug, thanks for pointing it out for me.


SQL start

create structs according to SQL schema in a separate package
Initialize Database and Setup Schema

i'm on it

schema and tables created, SQLite
no FK constraints

Done

schema and tables created, SQLite
no FK constraints


binexport: add typing where applicable

see https://github.com/mandiant/capa/pull/2106

closed by cbe83dd


YouTube links that start the video at a certain point don't work.

Title. The "?t=34" part of a YT link is ignored, and any track on YT is always played from the start.

This is more of an issue with the library we use to play audio from YouTube: https://github.com/Walkyst/lavaplayer-fork
Not sure if it's even an issue though, and I don't think that it's something that I would like to be fixed.

Would be nice so you don't have to download the video and edit it manually.


DeprecationWarning

Hi,
I am geting DeprecationWarning when trying to install it:
npm install -g homebridge-camera-rpi
(node:1196) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
<EMAIL_ADDRESS>/usr/local/lib/node_modules/homebridge-camera-rpi
└──<EMAIL_ADDRESS>is it Deprecated and gone for ever? ;-(

It should still work just fine, it just warns that one of the dependencies is using a method that is deprecated (i.e. this method will not be available soon).
This warning will probably be fixed by the next release using updated dependencies.

@moritzmhmk Thanks for the reply!
when i try to installing it all i get is that line.. is there a special way to install it?

what is the output of npm list -g --depth 0

(node:5736) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
/usr/local/lib
└──<EMAIL_ADDRESS>

and npm -v?
It looks like there is something outdated with your npm or node installation.
But it should not affect homebridge-camera-rpi, which according to that output did install properly.

1.4.21
(node:5765) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.

npm 1.4.21 is about 5 years old. Consider installing an up to date version of node and npm.
Instructions can be found here.
If you use a Raspberry Pi B, B+ or Zero google for an up to date tutorial on installing without the package manager. The latest release for armv6 seems to be 11.x (for 12.x there are no builds for this arch)
Even without installing an up to date version (which I highly recommend anyway!) homebridge-camera-rpi should work and your installation has been successfull so far just yielding that confusing deprecation warning.

I am using pi 3B and HOOBS Release... however this means they are using outdated packages ...
Thank you so much ;-)


Fix some duping

Fixes some cases where the plugin is too trigger happy when using / inside comments and attempting to extend the end of a comment.

Coverage remained the same at 40.984% when pulling 1605811d8815ea6da67039971baed7e74317c2c3 on PJB3005:fix-some-duping into a35ed46b49ad91808d0ed28b91f10e233dd11691 on k--kato:master.


API client implementation does not fully compliance with the specs

Describe the bug
The API client implementation is not fully compliance with the API specs. There are following observations.

The API specs tend to specify two key information 1) Status Code 2) Response body
The API client implementation only resolves with the response body and skip the the other piece of information
For endpoints which are not returning body API client resolves to undefined
For the endpoints which are returning multiple status codes e.g. GET /eth/v1/node/health, POST /eth/v1/beacon/blocks  there are no way to identify what response code was returned the API call.

With these observations, it's not easy to use the API client with any CL node which have fully compliance implementation.
Lodestar is missing some edge cases on implementation e.g. Lodestar writes the node health code as response body as well as status code. While reading it just reads the body and ignore the status code.
Proposals
There are two approaches we can fix this issue.

Resolve API calls with the either response body or status code. When response is available we resolve with it otherwise status code. This will introduce minimum change, but could introduce some confusion the API client users.

Create a new structure given below and always resolves with it.

{ok: boolean, status: number, [body,result]?: T}

With this approach API client user can get both information as response body and status code and use on his convenience. This approach would require a bit extra refactoring compared to option 1, but is more steady and future proof approach.
We can additionally create an optional config parameter for the API client resolveErrorResponse: boolean, if user set we can also resolve error response with ok: false. That should be a optional flag, if user want to avoid try/catch and alway check the response in data centric approach.

Based on the discussion @wemeetagain agrees to the second approach.


ERROR: chatGPT_answer failed

I tried to use the script but as I clicked CTRL + ALT + T the Console says the Question and Anwers but then there is:
Something went wrong.
chatGPT_answer failed

and the API says at the API KEY: never used
can someone pls help me fix this?

Can you take a screenshot of the code where you define your api key (you can blur or mark out the key)

Thank you for the quick responce here is the screenshot:

regarding the 0 uses thing on the api key, that can happen because openai takes a little bit to register everything

The Error is:
Something went wrong.
chatGPT_answer failed with error: cannot access local variable 'response' where it is not associated with a value

can you try setting your tesseract path to this? Not sure if it will work just a guess:
C:\Program Files\Tesseract-OCR\tesseract.exe

But the response Variable is the responce of response = openai.ChatCompletion.create(model="gpt-4", messages=conversation) that gets a value when the openai command gets ran

right but since I dont see how that could be causing an error I'm just checking whats different between your code and mine since mine works

can you try setting your tesseract path to this? Not sure if it will work just a guess: C:\Program Files\Tesseract-OCR\tesseract.exe

Tesseract gets the Question and Anwers, but the responce variable doesn´t get a value

are you sure your api is correct then?

can you try setting your tesseract path to this? Not sure if it will work just a guess: C:\Program Files\Tesseract-OCR\tesseract.exe

Tesseract gets the Question and Anwers, but the responce variable doesn´t get a value

I have created a new API token but there is still the same error

try changing 'gpt-4' to 'gpt-3.5-turbo'

same Error

ok I´ll test it

import keyboard
import pyautogui
import pytesseract
import openai

pytesseract.pytesseract.tesseract_cmd = r"C:\Program Files\Tesseract-OCR\tesseract.exe"  # Path to tesseract.exe example path: r"C:\Program Files\Tesseract-OCR\tesseract.exe"
openai.api_key = "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"

def click_button(button):
    # Coordinates for each button
    button_coords = {1: (579, 1040), 2: (1562, 1037), 3: (528, 1261), 4: (1803, 1255)}
    x, y = button_coords[button]
    pyautogui.click(x, y)

def chatGPT_answer(question_and_answers):
    # Adding explicit instruction to the prompt
    # Modify the instruction to the model to fit your needs
    conversation = [
        {
            "role": "system",
            "content": "You are a helpful assistant specialized in answering multiple-choice questions who only responds with the button number corresponding to the most likely answer do not respond with words only a integer. You'll do this even if the question involves content you can't analyze, such as videos or images. If you cannot answer the question, you'll respond with an educated guess. Remember only respond with an integer between 1 and 4 that corresponds to the answer.",
        },
        {"role": "user", "content": question_and_answers},
    ]
    try:
        response = openai.ChatCompletion.create(model="gpt-3.5-turbo", messages=conversation) # can be set to 'gpt-4' if needed

        # Extract the assistant's reply
        reply = response["choices"][0]["message"]["content"].strip()
        # Return the button number as an integer
        return int(reply)
    except ValueError:
        # Handle exception here if the reply is not an integer
        print(f"Unexpected reply: {reply}")
        return int(reply[0])
    except:
        # Handle exception here if something else goes wrong
        print("Something went wrong.")
        print(response)
        return None

def kahoot_god():
    # Coordinates for kahoot question and answers
    question_and_answers = {
        0: {"top_left": (0, 72), "bottom_right": (2475, 200)},
        1: {"top_left": (105, 1000), "bottom_right": (1219, 1118)},
        2: {"top_left": (1370, 1000), "bottom_right": (2500, 1127)},
        3: {"top_left": (100, 1200), "bottom_right": (1260, 1361)},
        4: {"top_left": (1370, 1175), "bottom_right": (2000, 1353)},
    }
    res = ""
    for element in question_and_answers:
        coords = question_and_answers[element]
        x1, y1 = coords["top_left"]
        x2, y2 = coords["bottom_right"]

        # Calculate width and height for each element for screenshot
        width = x2 - x1
        height = y2 - y1

        screenshot = pyautogui.screenshot(region=(x1, y1, width, height))
        screenshot_text = pytesseract.image_to_string(screenshot)
        if not screenshot_text.strip():
            print("No text detected.")
            continue
        if element == 0:
            res += f"Question: {screenshot_text}"
        else:
            res += f"{element}: {screenshot_text}"
    print(res)
    try:
        answer = chatGPT_answer(res)
        click_button(answer)
        print(f"Answer: {answer}")
    except:
        print("chatGPT_answer failed")

# Bind the function to a hotkey
keyboard.add_hotkey("ctrl+alt+t", kahoot_god)
# Keep the program running
keyboard.wait()

if you choose to use all 53 of my cents then go ahead

no, i´ll do just one request

My reselution broke, but it has functioned

wdym ur resolution settings

could be thats your code and reselution settings

now try adding that api key into your previous code

ok

still doesn´t worked
but where do you create the API key? on: https://platform.openai.com/account/api-keys right?

yes

try adding a print(response) line after you request the chatgpt completion

I think i found the problem with the responce. I thought I can use the API for free but you must pay it to use it. Thank you for your help


Don't write startup message into stderr

When Spark ignites, many messages get written to standard error. In my opinion, these should be written to standard out instead. My logs show errors as red text so it always looks like something failed when actually everything started successfully. These messages include:

[main] INFO spark.staticfiles.StaticFilesConfiguration - StaticResourceHandler configured with folder = /public
[Thread-0] INFO org.eclipse.jetty.util.log - Logging initialized @180ms
[Thread-0] INFO spark.embeddedserver.jetty.EmbeddedJettyServer - == Spark has ignited ...
[Thread-0] INFO spark.embeddedserver.jetty.EmbeddedJettyServer - >> Listening on <IP_ADDRESS>:8080
[Thread-0] INFO org.eclipse.jetty.server.Server - jetty-9.3.z-SNAPSHOT
[Thread-0] INFO org.eclipse.jetty.server.ServerConnector - Started ServerConnector@11343699{HTTP/1.1,[http/1.1]}{<IP_ADDRESS>:8080}
[Thread-0] INFO org.eclipse.jetty.server.Server - Started @278ms

Agreed, these should be set as INFO log level. I will look at making a PR and changing this tonight.

Jut a quick update, I have had a look and because we use sfl4j-simple this passes all logs no matter what they are to the System.err. I propose that we migrate to Logback.
Logback is the successor to log4j. We can still use the sfl4j api but as a backend and extensively configurable Logback is the best way to go.
Thoughts @tipsy @perwendel ?

slf4j-simple is a test dependency of spark (only used for tests) therefore it should not be in the classpath when running a project with spark as a dependency (unless you add it explicitely in your pom.xml). Without slf4j-simple or any slf4j binding, the console only prints :
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

You can use any binding with slf4j such as log4j, logback or slf4j-simple. Do not mix the standard error output and the log levels. slf4j-simple writes everything with info log level (and below) to System.err by default; @mastertinner if you want the output to go to System.out while using the slf4j-simple binding, see http://www.slf4j.org/api/org/slf4j/impl/SimpleLogger.html and set the system properties (or a simplelogger.properties file in the classpath) accordingly.
Being a library project, spark do not use any log implementation, only the slf4j API which is the right way to go. It's only needed in the test phase in which slf4j-simple is sufficient.

Thanks for your help, @MouettE-SC! I chose slf4j-nop and now it works without writing into stderr. I'll close this issue since the problem described by me was not one of Spark.


ColumnLayout does not like 0-factor Scale in AddingAnimation

Put N items with behaviors like this in a scrollview.
	<AddingAnimation>
		<Scale Factor="0" Duration="0.2"/> <!-- This ruins the layout -->
	</AddingAnimation>

I wind up having to scroll out of view and back again for items to appear.
A factor of 0.01 works fine, however.

The forum thread AddingAnimation on Grid elements does not work posted by<EMAIL_ADDRESS>was linked to this issue.


What is your opinion about removing the curly brackets?

seq(100) | |x|
  if x % 15 == 0
    "FizzBuzz"
  else if x % 3 == 0
    "Fizz"
  else if x % 5 == 0
    "Buzz"
  else
    x
| STDOUT

Indentation could be used instead.

Curly braces are fine for scoping. The C-Style will help with adoption as well.


Question : find a resource based on its internal id

Hello all
first thank you for this python library very convenient and useful.
I have a question about getting a ressource from its internal id.
I found a workaround using get_json method:
bd = Client(base_url=args.url, token=args.token)
json = bd.get_json(f'api/components/{component_id}')

But I would prefer to not be dependent to the URL structure I would prefer something like that but I did not succeed to write the correct query:
bd = Client(base_url=args.url, token=args.token)
params = {
        'q': [f"<someting_UUID_guid???>:{component}"],
        'limit': 1
}
components = [c for c in bd.get_resource('components', params=params) if c['<someting_UUID_guid???>'] == component]

Is it possible to have the unique id as a parameter of the query ? If not is it possible to add it ?
Regards

Although there are some blackduck folks among us maintainers, for product enhancements & feedback you'd be better off reaching out to Sig support or your technical account manager.
That said, the API is not designed to work that way, it would require fundamental changes which we are unlikely to see.
There are very few scenarios where you'd need to cut and paste uuids, have you considered just using the full url for each resource? It is available via the built-inhref field.

Thanks for your answer
Yes I will reach my support team.
Actually why I wanted to used uuid is because I want to implement an export / import process :
as a user I export blackduck data in csv format
as a user i edit the csv to update values (particularly custom fields)
as a user i run a script to import updated data.
Because uuids are generated in the blackduck csv report it was convenient for me to reuse them to find my objects to update


FSDP Overlap Investigation

The problem is that on LUMI, FSDP doesn't overlap computation and communication like it should. Evidence comes from this profiler trace:

It may be noteworthy that the NCCL GPU stream does not have an ID:

The problem persists on LUMI with torch 2.0.1, torch 2.1, and torch-nightly (to be torch 2.2) on 24 nodes.
There is no problem on a single 4x A100 node in Cirrascale.
Problem is also visible on a single AMD node in AAC.

@2015aroras @dirkgr great thread! Is there any update you could provide on this issue? Did you trace it back to something in the AMD stack?

Marking the items prior to Feb 29th as "closed".


Can't restore panel (e.g. debug panel) position back to default( it doesn't respect its setting )

VSCode Version: 1.25.1
OS Version: Windows 10 (1607)

Steps to Reproduce:

Change Panel default location to right by: "workbench.panel.defaultLocation": "right"
after opening terminal then split terminal (perhaps delete them after split.)
now set the panel back to default which is bottom by "workbench.panel.defaultLocation": "bottom"
panels (such as terminal) now opens only in right and doesn't respect new setting. (ctrl + ` )

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

Do you see the same in the latest Insiders?

I have not checked that
Get Outlook for iOShttps://aka.ms/o0ukef

From: Ramya Rao<EMAIL_ADDRESS>Sent: Wednesday, August 8, 2018 1:58 PM
To: Microsoft/vscode
Cc: Sepehr Pakbaz; Author
Subject: Re: [Microsoft/vscode] Can't restore panel (e.g. debug panel) position back to default( it doesn't respect its setting ) (#56010)
Do you see the same in the latest Insidershttps://code.visualstudio.com/insiders?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/vscode/issues/56010#issuecomment-411496509, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AEIg9z0XhCr0HUOFQc3v0BTIlxRPYL2iks5uOybSgaJpZM4V0RZX.

Please do check the latest Insiders and let us know if you see the same there.


incorrect name virtualenv in Install.bat script

Looks like line no 40 (python -m virtualenv gimpenv3) in install.bat script has to be changed to python -m venv gimpenv3

Were you able to edit this yourself? Does this error cause the install of the OpenVINO NPU models to fail?

venv should be valid. Are you having issues with it vs virtualenv?

Yes, with virtualenv it does not work (at least on windows + install.bat). If I modify it as venv it runs fine.

Which version of Python are you using?

python 3.11


Adding functionality for modifying map options

using setOptions(), a map's object can be changed (e.g., disableZoom, disablePan, etc.)

Please create a new pull request from a feature branch instead of a development branch. This allows us to keep track of feature changes and their sources. Also, rejecting this PR because it contains an incomplete fix for global map config options


Obtain github token from a command

The problem I'm trying to solve:

I'd like a more secure way to store my token for hub. I already use pass to store my credentials, all I need is a way to invoke it from hub.
Technically right now I could alias hub="GITHUB_TOKEN=$(pass hub) hub", but it would be preferable to not have my token in the env at all.
How I imagine hub could expose this functionality:

git config --global hub.tokencmd = "pass hub"

If a token is not set in the hub config file or the environment, hub will attempt to invoke hub.tokencmd and use the stdout as your token. hub will not store the result of this -- it will invoke the command every time it needs a token.
I'm happy to implement this if there is an interest. This relates to https://github.com/github/hub/issues/463:

Yes I would be open to PRs that improve security, but in a way that potentially helps the majority of hub users and across different platforms.

I think this satisfies all of those requests. If someone wants to use gpg, they can set hub.tokencmd="gpg -d hub.gpg" and get that functionality without hub having to implement anything specific for gpg.

Thanks! Going to mark this as a duplicate of https://github.com/github/hub/issues/1217
I plan to support reading from a credentials cache command, but the command will likely be configurable so you can use pass as well.


Editor Crash when using [Command] with ScriptableObject containing self-type references.

create ScriptableObject class with data of own type
use as parameter in [Command] function
editor crashes upon recompile

see repro project
reproduced on 2018.3.0b3 and 2018.3.0b6
MirrorBug.zip

The editor crashes as in the entire editor dies?
I would expect just an error from Mirror.
per Unity's documentation,  you cannot pass scriptable objects in [Commands]  see docs here:
https://docs.unity3d.com/ScriptReference/Networking.CommandAttribute.html

Yeap, the editor crashes. Makes sense it can't be handled, but maybe avoiding crash would be nice.

Found in the editor log:
Stack overflow in unmanaged: IP: 0x13feae7db, fault addr: 0x7ffeef408fe8

Unhandled Exception:
StackOverflowException

It does look like the weaver is causing the crash.  If I remove Mirror's weaver Unity loads.

@kalineh  please test this build to validate that it resolves the issue:
https://ci.appveyor.com/project/vis2k73562/hlapi-community-edition/builds/19740341/artifacts

Thanks for report @kalineh ! Really strange, please let us know if the fix works.

This bug is inherited from HLAPI.   They check for infinite recursion during GetWriteFunc,  but for some reason they forgot to put the check in GetReadFunc.   I do believe they intended it to be there too,  they just missed it.

:tada: This issue has been resolved in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add my first file

I have created a new branch, created a file and made a commit!

I have created a new branch, created a file and made a commit!

I have created a new branch, created a file and made a commit!


$ref to external files raise RefResolutionError: unknown url type

The OpenAPI Specification allow to reference to external files: https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#reference-object
But this validator is not fully implement the Reference Object of the specification. This shortcoming makes this library practically useless.
By the way, I did not see the full implementation of this object in other similar libraries.

@viczem
Yes, it allows but you need to specify spec_url keyword argument to resolver know what is the relative path


Is it possible to slide menu up from bottom of screen?

Hello, I hope all is well. I'm attempting to create something similar to the Twitters , "Compose tweet" view where  once a user swipes upwards a gallery view appears oever and takes the place of the compose tweet view.

Unfortunately I don't think it's currently supported in this library.
I made an alternative class (currently slides only from top, but shouldn't be a problem to extend the functionality), should satisfy your requirements. SlidingTopPanel


Double tap Apple Pencil to switch to right click

I implemented the very basic behavior as follows: double tapping the Apple Pencil 2 (API doc) enables "one time right click" mode. In this mode, tapping the screen with a single touch like Pencil then results in a right click triggered instead of left click and the mode is disabled.
Unfortunately, I don't have an iPad with Apple Pencil 2 support. So I can't test if it really works. I mocked it by setting the mode when two-finger-tapped and then tapping with my Apple Pencil 1, which works:
- (IBAction)gestureTwoTap:(UITapGestureRecognizer *)sender {
    if (sender.state == UIGestureRecognizerStateEnded &&
        self.twoFingerTapType == VMGestureTypeRightClick) {
//        [self mouseClick:SEND_BUTTON_RIGHT location:[sender locationInView:sender.view]];
        pencilForceRightClickOnce = true;
    }
}

I opened PR 297 about this.


Topic/task energy

Hi all !
Here are the developments that I made for the RA-L paper "Passive Inverse Dynamics Control using a Global Energy Tank for Torque-Controlled Humanoid Robots in Multi-Contact".
I implemented a new task called energyTask in TSID and made quite some changes. I don't know where to propose this PR as it also modifies the formulation of the QP (inverse-dynamics-formulation-acc-force) to take the energy into account.
If perhaps you can tell me where to propose it @andreadelprete, @nim65s ? Perhaps in a new branch ? Thanks !
The energy task is used to transform the classical whole-body controller using inverse dynamics of TSID into a passive scheme. The passivity is a stability criterion based on the power flow exchanged by the components of the system. A storage function H(x) is chosen (often as the energy of the system) and to have a passive system, the system internal power (d_H: derivative of the energy in the system) must be lesser or equal to the power transferred to the system through its port. For a system controller+robot (controlled in torque) it is the velocity and the torque.
The energy task adds an energy tank to the controller to monitor the energy flow of the system. This tank regulates the task gains using coefficients (alpha, beta and gamma in [0, 1]) to respect the passivity of the system. These coefficients are multiplied to the task vectors in the QP formulation.
Thus, if one of the coefficient is lowered to zero (when there is no more energy in the tank), the tasks are penalized because have a decreased desired acceleration or even a null one. Moreover, as the tank is computed without taking into account the constraints of the QP, a passivity constraint is added in the QP formulation in addition to the regulating coefficient.
For more information, see the paper (soon to be published).

Hi @NoelieRamuzat , thanks for your contribution, it looks really interesting. At a first sight, I am not against having this PR directly on the devel branch. It will probably take me a while to review, as it's a lot of changes, but I think we can leave it here. Unless of course @nim65s has a better idea.

Hi,
No, this looks really clean to me, I also think we should put that on devel.
The only issue I see is the API changes.
@NoelieRamuzat : could you document (and maybe motivate) the modifications you made ? I'm not talking about anything you added, just the cases where you changed a return type, or removed some const. This will bu useful in the next version release notes, and if this break anyone's code, this will help them to upgrade.
Also, maybe, a test for this new feature would be nice ;)

Hi @NoelieRamuzat , just for your information, I am reading your paper to understand the theory in details before reviewing this PR. I'll probably send you an email to ask a few questions about the theory.

Hi @nim65s, @andreadelprete,
Thanks for your comments, I am currently working on the API changes.
No problem for the theory details @andreadelprete, the early access of the paper is at the following link:
https://ieeexplore.ieee.org/document/9691905

Hi !
Here are the explanations for the changes in the API:

I created the TaskLevelMotion structure in the formulation because I needed the vector of motion tasks in the QP (m_taskMotions) to be of class TaskMotion and not simply TaskBase (to have access to the specific methods of motions).

I added in the class TaskMotion the virtual methods

Hi ! Sorry I made a miss-click on the PR.
Here are the explanations for the changes in the API:

I created the TaskLevelMotion structure in the formulation because I needed the vector of motion tasks in the QP (m_taskMotions) to be of class TaskMotion and not simply TaskBase (to have access to the specific methods of TaskMotion).

I added in the class TaskMotion the virtual setter and getter Kp, Kd and the methods getJacobian and acceleration_ref as I need them for the computation of the energy.
As these functions are now in the parent class, the inherited classes have to have the same return types.
This is why, in the CoM and angular-momentum tasks, I changed the return types of the Kp and Kd getters form Vector3 to VectorXd.
In particular, for the angular-momentum task, I added the methods velocity_ref, velocity_err, acceleration_ref, acceleration_err to have the generic methods of the TaskMotion class defined and use them in the computation of the energy. They return the momentum_ref and momentum_error of the AM class.
However, as the return types of the methods of the TaskMotion class were VectorXd I had to change the return types of the momentum methods (and also the ones of the private members).
Moreover, in the SE3_equality task, I had to remove the const of the getter Kp, Kd as they are not const in the parent class.
And then, because the contact classes implement the getter Kp, Kd for their m_motionTask, I also had to remove the const there.

Finally, in the contact classes I had to remove the const of the getMotionTask method.
I call this method in the energy task :

TaskSE3Equality& contact_motion = cl->contact.getMotionTask();
auto tl = std::make_shared<TaskLevelMotion>(contact_motion, 1);

And if it is const it does not work because the TaskLevelMotion takes a reference.
I implemented it the same way as the other TaskLevel formulations.
I did not found conflicting use of contact.getMotionTask which needed this const, thus I removed it.