Target netstandard1.6 and net45

Hit a couple snags, of course.

MS Test SDK downgrades packages with a warning: https://github.com/Microsoft/vstest/issues/1764
F# SDK so helpfully substitutes it's own random version of FSharp.Core package.

Targeting F# core package 4.2.3, since 4.2.* is the lowest version supporting netstandard.
I also resurrected generation of XML doc files, they were in the 0.3.1 package.
Tests out good:
c:\projects\FParsec-Pipes>dotnet test FParsec-Pipes-Test -f netcoreapp2.0
Microsoft (R) Build Engine version 15.8.169+g1ccb72aefa for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

  Restoring packages for c:\projects\FParsec-Pipes\FParsec-Pipes\FParsec-Pipes.fsproj...
  Restoring packages for c:\projects\FParsec-Pipes\FParsec-Pipes-Test\FParsec-Pipes-Test.fsproj...
  Generating MSBuild file c:\projects\FParsec-Pipes\FParsec-Pipes\obj\FParsec-Pipes.fsproj.nuget.g.props.
  Generating MSBuild file c:\projects\FParsec-Pipes\FParsec-Pipes\obj\FParsec-Pipes.fsproj.nuget.g.targets.
  Restore completed in 637.35 ms for c:\projects\FParsec-Pipes\FParsec-Pipes\FParsec-Pipes.fsproj.
  Generating MSBuild file c:\projects\FParsec-Pipes\FParsec-Pipes-Test\obj\FParsec-Pipes-Test.fsproj.nuget.g.props.
  Generating MSBuild file c:\projects\FParsec-Pipes\FParsec-Pipes-Test\obj\FParsec-Pipes-Test.fsproj.nuget.g.targets.
  Restore completed in 866.43 ms for c:\projects\FParsec-Pipes\FParsec-Pipes-Test\FParsec-Pipes-Test.fsproj.
Build started, please wait...
Build completed.

Test run for c:\projects\FParsec-Pipes\FParsec-Pipes-Test\bin\Debug\netcoreapp2.0\FParsec-Pipes-Test.dll(.NETCoreApp,Version=v2.0)
Microsoft (R) Test Execution Command Line Tool Version 15.8.0
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...

Total tests: 47. Passed: 47. Failed: 0. Skipped: 0.
Test Run Successful.
Test execution time: 0.9635 Seconds

c:\projects\FParsec-Pipes>dotnet test FParsec-Pipes-Test -f net45
Microsoft (R) Build Engine version 15.8.169+g1ccb72aefa for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

  Restore completed in 33.81 ms for c:\projects\FParsec-Pipes\FParsec-Pipes\FParsec-Pipes.fsproj.
  Restore completed in 31.35 ms for c:\projects\FParsec-Pipes\FParsec-Pipes-Test\FParsec-Pipes-Test.fsproj.
Build started, please wait...
Build completed.

Test run for c:\projects\FParsec-Pipes\FParsec-Pipes-Test\bin\Debug\net45\FParsec-Pipes-Test.exe(.NETFramework,Version=v4.5)
Microsoft (R) Test Execution Command Line Tool Version 15.8.0
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...

Total tests: 47. Passed: 47. Failed: 0. Skipped: 0.
Test Run Successful.
Test execution time: 1.2194 Seconds

c:\projects\FParsec-Pipes>dotnet test Examples.SQLite
Build started, please wait...
Build completed.

Test run for c:\projects\FParsec-Pipes\Examples.SQLite\bin\Debug\netcoreapp2.0\Examples.SQLite.dll(.NETCoreApp,Version=v2.0)
Microsoft (R) Test Execution Command Line Tool Version 15.8.0
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...
Skipped  TestSqlFiles

Total tests: 11. Passed: 10. Failed: 0. Skipped: 1.
Test Run Successful.
Test execution time: 1.6925 Seconds

Release packaging (requires the SNK file)
c:\projects\FParsec-Pipes>sn -k ..\robert.peele.snk

Microsoft (R) .NET Framework Strong Name Utility  Version 4.0.30319.0
Copyright (c) Microsoft Corporation.  All rights reserved.

Key pair written to ..\robert.peele.snk

c:\projects\FParsec-Pipes>dotnet pack FParsec-Pipes -c Release
Microsoft (R) Build Engine version 15.8.169+g1ccb72aefa for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

  Restore completed in 29.78 ms for c:\projects\FParsec-Pipes\FParsec-Pipes\FParsec-Pipes.fsproj.
  FParsec-Pipes -> c:\projects\FParsec-Pipes\FParsec-Pipes\bin\Release\net45\FParsec-Pipes.dll
  FParsec-Pipes -> c:\projects\FParsec-Pipes\FParsec-Pipes\bin\Release\netstandard1.6\FParsec-Pipes.dll
  Successfully created package 'c:\projects\FParsec-Pipes\FParsec-Pipes\bin\Release\FParsec-Pipes.1.1.0.nupkg'.

Make sure the right FSharp.Core version 4.2.3 is really used.
c:\projects\FParsec-Pipes>dotnet build FParsec-Pipes-Test -c Release -bl:build.binlog -v:n | grep 'FSharp.Core'
         -r:C:\Users\kkm\.nuget\packages\fsharp.core\4.2.3\lib\net45\FSharp.Core.dll
         -r:C:\Users\kkm\.nuget\packages\fsharp.core\4.2.3\lib\netstandard1.6\FSharp.Core.dll
         -r:C:\Users\kkm\.nuget\packages\fsharp.core\4.2.3\lib\net45\FSharp.Core.dll
         -r:C:\Users\kkm\.nuget\packages\fsharp.core\4.2.3\lib\netstandard1.6\FSharp.Core.dll

Package contents and dependencies look reasonable, too.
c:\projects\FParsec-Pipes>unzip -l FParsec-Pipes\bin\Release\FParsec-Pipes.1.1.0.nupkg
Archive:  FParsec-Pipes\bin\Release\FParsec-Pipes.1.1.0.nupkg
  Length      Date    Time    Name
---------  ---------- -----   ----
      507  2018-10-16 20:13   _rels/.rels
     1578  2018-10-16 20:13   FParsec-Pipes.nuspec
   200704  2018-10-17 03:13   lib/net45/FParsec-Pipes.dll
    12028  2018-10-17 03:13   lib/net45/FParsec-Pipes.xml
   201216  2018-10-17 03:13   lib/netstandard1.6/FParsec-Pipes.dll
    12028  2018-10-17 03:13   lib/netstandard1.6/FParsec-Pipes.xml
      528  2018-10-16 20:13   [Content_Types].xml
      683  2018-10-16 20:13   package/services/metadata/core-properties/a079646db21a4b81837eb9bd62131c5f.psmdcp
---------                     -------
   429272                     8 files

c:\projects\FParsec-Pipes>unzip -p FParsec-Pipes\bin\Release\FParsec-Pipes.1.1.0.nupkg FParsec-Pipes.nuspec
<?xml version="1.0" encoding="utf-8"?>
<package xmlns="http://schemas.microsoft.com/packaging/2013/05/nuspec.xsd">
  <metadata>
    <id>FParsec-Pipes</id>
    <version>1.1.0</version>
    <authors>Robert Peele</authors>
    <owners>Robert Peele</owners>
    <requireLicenseAcceptance>false</requireLicenseAcceptance>
    <licenseUrl>https://opensource.org/licenses/MIT</licenseUrl>
    <projectUrl>https://github.com/rspeele/FParsec-Pipes</projectUrl>
    <description>Package Description</description>
    <releaseNotes>Target netstandard1.6 and net45</releaseNotes>
    <copyright>Copyright 2016 Robert Peele</copyright>
    <tags>parser combinator f# fsharp c# csharp parsec fparsec pipe pipes</tags>
    <repository url="https://github.com/rspeele/FParsec-Pipes" />
    <dependencies>
      <group targetFramework=".NETFramework4.5">
        <dependency id="FParsec" version="1.0.3" exclude="Build,Analyzers" />
        <dependency id="FSharp.Core" version="4.2.3" exclude="Build,Analyzers" />
        <dependency id="System.ValueTuple" version="4.4.0" exclude="Build,Analyzers" />
      </group>
      <group targetFramework=".NETStandard1.6">
        <dependency id="FParsec" version="1.0.3" exclude="Build,Analyzers" />
        <dependency id="FSharp.Core" version="4.2.3" exclude="Build,Analyzers" />
        <dependency id="NETStandard.Library" version="1.6.1" exclude="Build,Analyzers" />
        <dependency id="System.ValueTuple" version="4.4.0" exclude="Build,Analyzers" />
      </group>
    </dependencies>
  </metadata>
</package>

Closes #9

You are the man. Thank you so much for doing this and especially for including all the dotnet commands you used to test on both Framework and Core and to package. That made it so much easier for me to confirm on my own machine vs. wandering around in the dark not sure if what I'm doing matches current doctrine.
Also, this made me realize that I never backed up my own .snk and in fact had changed hard drives since the last time I did any open source work. The only drive with my .snk on it was sitting on my desk getting beverages spilled on it. So thanks for reminding me to pull that off of there!

My pleasure! I learned something in the process, too, namely how to pin the FSharp.Core package version.
The current doctrine regarding the SNK is just create one per open-source project and check it in. The signature is no longer relied upon for security, but allows the DLL to have a strong name.:

[!WARNING]
Do not rely on strong names for security. They provide a unique identity only.

If you are an open-source developer and you want the identity benefits of a strong-named assembly, consider checking in the private key associated with an assembly into your source control system.

There are interesting effects of changing the key, but if it's gone, it's gone. Basically, new key means new "full name", which means the build cannot create a binding redirect to consolidate references to one single version of the assembly (it is considered an entirely different assembly), but the two fight for the same file name in the bin/ output. I do not think many people are using this particular library to experience major unification problems; compare this and that. And all this can happen only if A.EXE refers to both B.DLL and your library nuget e. g. ver. 0.3.1, and B.DLL is in turn built against ver. 42.0 with a different key, for some value of 42. We (meaning the users of it) will survive. :)
There is also this new PublicSign aka "fake sign" mechanism which, I believe, requires an SNK with a public key only. But I do not know much else except that it exists.
By the way, AssemblyInfo.{cs,vb,fs} is no longer necessary too (you still have version 0.4.0 there). If you do not set the version attributes, the build will generate one in a temp directory and compile it in, setting all 3 version fields to the package version from the <Version> property in .*proj. This is the right thing to do for simple cases like this library. Also sets author, description, copyright, all this stuff.
Love the compiler-abuse tag ob the repo, by the way. Very apt! :)


Introduced Vector2 and Vector3 Square Lenght.

I would like to add this two functions.
It's simple, but having a length function that doesn't use sqrt() (for comparative purposes) would be nice when you need to calculate lots of distances each frame.

@ThePituLegend thanks for the improvement! :)


Fix code example in Quick Start docs

@bahmutov/cypress-esbuild-preprocessor doesn't have a default export:
module.exports = createBundler

The old imports produced a type error when loading Cypress:
TypeError: (0 , cypress_esbuild_preprocessor_1.default) is not a function
    at cypress.config.ts:17:22
    at step (cypress.config.ts:33:23)
    at Object.next (cypress.config.ts:14:53)
    at fulfilled (cypress.config.ts:5:58)

The docs reflect the examples, which work (tested in ci). Have you perhaps hit the same thing described in https://github.com/badeball/cypress-cucumber-preprocessor/issues/790?

Ah, that could be it. Never mind!


Release 1.1.10

Summary | Résumé
List of tags
1.1.4 -> 1.1.10:

refactor WAF
tweak scanfiles timeout alarm
security group for Quicksight

#665 Remove hosts restrictions and consolidate all invalid paths under one rule (to ring them all) (Jimmy)
#675 no news is good news (Steve A)
#670 add security group for quicksight (Steve A)
#673 fix: update scanfiles timeout alarm description (Andrew)
#676 Added WAF rules for documentation website (Jimmy)
#678 add regex for static assets (Steve A)

Note that there's an open PR (#674) that will make the bulk_send key inactive in terraform.


write simple e2e test for draft init and up

I know @adamreese managed to get https://github.com/Mirantis/kubeadm-dind-cluster working on Circle. We might be able to take advantage of that work to test and run these e2e tests.
See https://github.com/kubernetes/helm/pull/3636


Non-interactive version?

Is there a non-interactive version of this available? I'd like to run this on the command line with parameters passed and get the derived addresses back.

There's not a command line version of this tool specifically, but there are some bip39 command line tools you can look into.
Have a look at https://github.com/trezor/python-mnemonic if you use python. Unfortunately there's no example usage documented with it.
You could try using bitcoind but I'm not familiar enough with the bip39 parts of that interface to give any more info.
Also have a look at https://github.com/bitcoinjs/bip39 if you use nodejs.
And finally check out https://github.com/tyler-smith/go-bip39 for golang.
I like your idea and it may be worth making a simple binary that does the same as this tool but in command-line form.

Thanks for your answer!
I'm using python, but would be willing to drop down to js for a decent, complete implementation. ;-)
What is missing from the tools/libraries that you listed is the encoding from public key to an address in the format specific to a coin. Do you happen to have any pointers for that or did you implement that from scratch yourself?


[Idea] Get GPU info

First question, where to get the information from?
I found in the pciutils repository the following:

In runs on the following systems:
Linux		(via /sys/bus/pci, /proc/bus/pci or i386 ports)
FreeBSD		(via /dev/pci)
NetBSD		(via libpci)
OpenBSD		(via /dev/pci)
GNU/kFreeBSD	(via /dev/pci)
Solaris/i386	(direct port access)
Aix		(via /dev/pci and odmget)
GNU Hurd	(direct port access)
Windows		(direct port access, see README.Windows for caveats)
CYGWIN		(direct port access)
BeOS		(via syscalls)
Haiku		(via /dev/misc/poke)
Darwin		(via IOKit)
DOS/DJGPP	(via i386 ports)
SylixOS		(via /proc/pci)

There are many possible places to search, depending on the kernel (or operating system). But in some cases it's a matter of reading a plain text file. In order not to make the issue too long, I recommend the first part of this article. As you can see in the article, it is possible to read the vendor identifier, device identifier and class identifier.
Step two: mapping identifiers to GPUs
I quote again the previous repository, the following:

The database of PCI IDs (the pci.ids file) gets out of date much faster
than I release new versions of this package, so it is maintained separately.
It lives at https://pci-ids.ucw.cz/, where you can browse the database,
download the most recent pci.ids file (e.g., by running the update-ids utility)
and also submit new entries.

If we go through that website, we can corroborate that the GPU information (in addition to other devices that are not relevant) can be obtained from these ID's.
At first I thought that the pci.ids file should be downloaded regularly to keep it updated but, at least in Arch Linux, I found it in /usr/share/hwdata/pci.ids.
I'm not sure this is the best way to solve it, but I think it can work, without relying on system commands or external crates.

I'm afraid the future won't be shipped until I can sort out the performance issues within aparato.

sneak peek
Uploading image.png…

What's the current status on this? I'd love to help, as I have some Rust experience.

Hi @PowerBall253,
Thanks for taking interest!
aparato was originally supposed to help us determine this information, but it's been unmaintained for a very long now. If you'd like to contribute, I suggest looking at other pci.ids parsers and hooking them with libmacchina, then we can add support for that readout in macchina.

Hi, I have no experience with this but I would like to work on as I would like to have that output. I would appreciate some guidance if you can point me in the right direction.
So, first I find a library which can parse psi.ids, maybe like (this one)[https://crates.io/crates/pci-ids]? Do I then use some other method to get the currently connected pci vga device or how do I go about this?

Ok thanks for the guidance, I'll have a look at it when I have some free time for sure and come back here if I get stuck

I have something working. Does this issue need to be moved to libmacchina first or shall I just open a PR over there? I also have some code ready for macchina to actually display the GPU.

Since that pr has been merged to libmacchina, is there a version update that needs to happen before I can make a pr here to utilise the new functionality? I have code ready just not sure if the crate needs an update first.

Ok cool, thank you

this issue was created in may 2021, and I just needed this today, exactly when it is very close to being merged... feeling lucky!
thank you very much for the project Macchina team, and the gpu part too @Rolv-Apneseth

The newest commit related to this issue seems to be broken for me
thread 'main' panicked at 'Could not find opening square bracket for sub device: Reference RX 5700 XT', /home/user/.local/share/cargo/registry/src/index.crates.io-6f17d22bba15001f/libmacchina-6.4.0/src/linux/pci_devices.rs:86:22

It was working before and only the latest commit broke it? That's weird, but I'll have a look as it's just a matter of how the strings are being processed I think

He's using device 731f 1002 0b36 which doesn't have a subdevice name. We should return the device string when an opening brace can't be located.

Alright will do

Is it not implemented for windows ?

No sorry not yet, I only implemented it for Linux. I believe it would also require internet access to get pci.ids.

@JacobTravers Can you git pull and try again?

Works fine now 👍🏽

Thanks for reporting that issue @JacobTravers


Failed install on Debian

I was trying to test this module, but had some issues installing.
I enclose the following:

Console output
2.npm-debug.log

--

Console output
npm WARN engine<EMAIL_ADDRESS>wanted: {"node":"0.6 || 0.8 || 0.10"} (current: {"node":"0.12.0","npm":"2.5.1"})

<EMAIL_ADDRESS>install /home/debian/sandbox/node_modules/ife
node-gyp rebuild

gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gyp/0.12.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/home/debian/sandbox/node_modules/ife/.node-gyp"
child_process: customFds option is deprecated, use stdio instead.
make: Entering directory /home/debian/sandbox/node_modules/ife/build'   CXX(target) Release/obj.target/IFEBinding/IFE.o In file included from ../IFE.cc:12:0: ../IFEheader.h:29:44: error: ‘Arguments’ in namespace ‘v8’ does not name a type ../IFEheader.h:29:59: error: ISO C++ forbids declaration of ‘args’ with no type [-fpermissive] ../IFEheader.h:30:45: error: ‘Arguments’ in namespace ‘v8’ does not name a type ../IFEheader.h:30:60: error: ISO C++ forbids declaration of ‘args’ with no type [-fpermissive] ../IFEheader.h:31:43: error: ‘Arguments’ in namespace ‘v8’ does not name a type ../IFEheader.h:31:58: error: ISO C++ forbids declaration of ‘args’ with no type [-fpermissive] ../IFEheader.h:32:45: error: ‘Arguments’ in namespace ‘v8’ does not name a type ../IFEheader.h:32:60: error: ISO C++ forbids declaration of ‘args’ with no type [-fpermissive] ../IFEheader.h:33:48: error: ‘Arguments’ in namespace ‘v8’ does not name a type ../IFEheader.h:33:63: error: ISO C++ forbids declaration of ‘args’ with no type [-fpermissive] ../IFEheader.h:34:49: error: ‘Arguments’ in namespace ‘v8’ does not name a type ../IFEheader.h:34:64: error: ISO C++ forbids declaration of ‘args’ with no type [-fpermissive] /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/src/node_object_wrap.h: In member function ‘void node::IFE::emit(v8::Local<v8::Value>*, int)’: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/src/node_object_wrap.h:132:30: error: ‘v8::Persistent<v8::Object> node::ObjectWrap::handle_’ is private ../IFE.cc:27:29: error: within this context ../IFE.cc:27:36: error: base operand of ‘->’ has non-pointer type ‘v8::Persistent<v8::Object>’ /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/src/node_object_wrap.h:132:30: error: ‘v8::Persistent<v8::Object> node::ObjectWrap::handle_’ is private ../IFE.cc:31:20: error: within this context ../IFE.cc:31:40: error: no matching function for call to ‘v8::Function::Call(v8::Persistent<v8::Object>&, int&, v8::Local<v8::Value>*&)’ ../IFE.cc:31:40: note: candidate is: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:2557:16: note: v8::Local<v8::Value> v8::Function::Call(v8::Handle<v8::Value>, int, v8::Handle<v8::Value>*) /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:2557:16: note:   no known conversion for argument 1 from ‘v8::Persistent<v8::Object>’ to ‘v8::Handle<v8::Value>’ /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h: In static member function ‘static void node::IFE::Initialize(v8::Handle<v8::Object>)’: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:816:13: error: ‘v8::HandleScope::HandleScope()’ is protected ../IFE.cc:40:17: error: within this context ../IFE.cc:42:63: error: no matching function for call to ‘v8::FunctionTemplate::New(v8::Handle<v8::Value> (&)(const int&))’ ../IFE.cc:42:63: note: candidate is: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:3455:34: note: static v8::Local<v8::FunctionTemplate> v8::FunctionTemplate::New(v8::Isolate*, v8::FunctionCallback, v8::Handle<v8::Value>, v8::Handle<v8::Signature>, int) /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:3455:34: note:   no known conversion for argument 1 from ‘v8::Handle<v8::Value>(const int&)’ to ‘v8::Isolate*’ ../IFE.cc:43:63: error: no matching function for call to ‘v8::Persistent<v8::FunctionTemplate>::New(v8::Local<v8::FunctionTemplate>&)’ ../IFE.cc:43:63: note: candidate is: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:5809:4: note: static T* v8::PersistentBase<T>::New(v8::Isolate*, T*) [with T = v8::FunctionTemplate] /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:5809:4: note:   candidate expects 2 arguments, 1 provided ../IFE.cc:44:25: error: base operand of ‘->’ has non-pointer type ‘v8::Persistent<v8::FunctionTemplate>’ ../IFE.cc:45:25: error: base operand of ‘->’ has non-pointer type ‘v8::Persistent<v8::FunctionTemplate>’ ../IFE.cc:45:40: error: ‘NewSymbol’ is not a member of ‘v8::String’ ../IFE.cc:47:70: error: could not convert ‘node::IFE::constructor_template’ from ‘v8::Persistent<v8::FunctionTemplate>’ to ‘v8::Handle<v8::FunctionTemplate>’ ../IFE.cc:48:66: error: could not convert ‘node::IFE::constructor_template’ from ‘v8::Persistent<v8::FunctionTemplate>’ to ‘v8::Handle<v8::FunctionTemplate>’ ../IFE.cc:49:70: error: could not convert ‘node::IFE::constructor_template’ from ‘v8::Persistent<v8::FunctionTemplate>’ to ‘v8::Handle<v8::FunctionTemplate>’ ../IFE.cc:50:76: error: could not convert ‘node::IFE::constructor_template’ from ‘v8::Persistent<v8::FunctionTemplate>’ to ‘v8::Handle<v8::FunctionTemplate>’ ../IFE.cc:51:78: error: could not convert ‘node::IFE::constructor_template’ from ‘v8::Persistent<v8::FunctionTemplate>’ to ‘v8::Handle<v8::FunctionTemplate>’ ../IFE.cc:53:38: error: ‘NODE_PSYMBOL’ was not declared in this scope ../IFE.cc:54:17: error: ‘NewSymbol’ is not a member of ‘v8::String’ ../IFE.cc:54:63: error: base operand of ‘->’ has non-pointer type ‘v8::Persistent<v8::FunctionTemplate>’ ../IFE.cc: At global scope: ../IFE.cc:57:32: error: ‘Arguments’ does not name a type ../IFE.cc:57:43: error: ISO C++ forbids declaration of ‘args’ with no type [-fpermissive] /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h: In static member function ‘static v8::Handle<v8::Value> node::IFE::New(const int&)’: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:816:13: error: ‘v8::HandleScope::HandleScope()’ is protected ../IFE.cc:58:17: error: within this context ../IFE.cc:61:18: error: request for member ‘This’ in ‘args’, which is of non-class type ‘const int’ ../IFE.cc:62:38: error: ‘class v8::HandleScope’ has no member named ‘Close’ ../IFE.cc:62:54: error: too few arguments to function ‘v8::Handle<v8::Primitive> v8::Undefined(v8::Isolate*)’ /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:305:28: note: declared here ../IFE.cc:64:14: error: request for member ‘Length’ in ‘args’, which is of non-class type ‘const int’ ../IFE.cc:65:46: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:66:35: error: ‘ThrowException’ was not declared in this scope ../IFE.cc:69:17: error: request for member ‘This’ in ‘args’, which is of non-class type ‘const int’ ../IFE.cc: At global scope: ../IFE.cc:72:37: error: ‘Arguments’ does not name a type ../IFE.cc:72:48: error: ISO C++ forbids declaration of ‘args’ with no type [-fpermissive] /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h: In static member function ‘static v8::Handle<v8::Value> node::IFE::arpcache(const int&)’: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:816:13: error: ‘v8::HandleScope::HandleScope()’ is protected ../IFE.cc:73:17: error: within this context ../IFE.cc:79:20: error: ‘class v8::HandleScope’ has no member named ‘Close’ ../IFE.cc:79:36: error: too few arguments to function ‘v8::Handle<v8::Primitive> v8::Undefined(v8::Isolate*)’ /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:305:28: note: declared here ../IFE.cc:80:38: error: no matching function for call to ‘v8::Object::New()’ ../IFE.cc:80:38: note: candidate is: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:2388:24: note: static v8::Local<v8::Object> v8::Object::New(v8::Isolate*) /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:2388:24: note:   candidate expects 1 argument, 0 provided ../IFE.cc:84:69: error: ‘inet_ntop’ was not declared in this scope ../IFE.cc:88:18: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:88:38: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:91:18: error: ‘class v8::HandleScope’ has no member named ‘Close’ ../IFE.cc: At global scope: ../IFE.cc:94:33: error: ‘Arguments’ does not name a type ../IFE.cc:94:44: error: ISO C++ forbids declaration of ‘args’ with no type [-fpermissive] /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h: In static member function ‘static v8::Handle<v8::Value> node::IFE::list(const int&)’: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:816:13: error: ‘v8::HandleScope::HandleScope()’ is protected ../IFE.cc:97:17: error: within this context ../IFE.cc:101:39: error: invalid conversion from ‘int’ to ‘v8::Isolate*’ [-fpermissive] /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:2417:23: error:   initializing argument 1 of ‘static v8::Local<v8::Array> v8::Array::New(v8::Isolate*, int)’ [-fpermissive] ../IFE.cc:104:42: error: no matching function for call to ‘v8::Object::New()’ ../IFE.cc:104:42: note: candidate is: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:2388:24: note: static v8::Local<v8::Object> v8::Object::New(v8::Isolate*) /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:2388:24: note:   candidate expects 1 argument, 0 provided ../IFE.cc:105:18: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:105:39: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:116:9: error: ‘inet_ntop’ was not declared in this scope ../IFE.cc:116:9: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:116:9: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:118:20: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:118:62: error: no matching function for call to ‘v8::Integer::New(int&)’ ../IFE.cc:118:62: note: candidate is: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:2012:25: note: static v8::Local<v8::Integer> v8::Integer::New(v8::Isolate*, int32_t) /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:2012:25: note:   candidate expects 2 arguments, 1 provided ../IFE.cc:120:9: error: ‘inet_ntop’ was not declared in this scope ../IFE.cc:120:9: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:120:9: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:121:9: error: ‘inet_ntop’ was not declared in this scope ../IFE.cc:121:9: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:121:9: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:122:9: error: ‘inet_ntop’ was not declared in this scope ../IFE.cc:122:9: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:122:9: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:127:18: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:127:38: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:128:29: error: no matching function for call to ‘v8::Number::New(int&)’ ../IFE.cc:128:29: note: candidate is: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:1999:24: note: static v8::Local<v8::Number> v8::Number::New(v8::Isolate*, double) /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:1999:24: note:   candidate expects 2 arguments, 1 provided ../IFE.cc:131:18: error: ‘class v8::HandleScope’ has no member named ‘Close’ ../IFE.cc: At global scope: ../IFE.cc:134:31: error: ‘Arguments’ does not name a type ../IFE.cc:134:42: error: ISO C++ forbids declaration of ‘args’ with no type [-fpermissive] /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h: In static member function ‘static v8::Handle<v8::Value> node::IFE::up(const int&)’: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:816:13: error: ‘v8::HandleScope::HandleScope()’ is protected ../IFE.cc:135:17: error: within this context ../IFE.cc:138:31: error: request for member ‘Holder’ in ‘args’, which is of non-class type ‘const int’ ../IFE.cc:142:29: error: invalid types ‘const int[int]’ for array subscript ../IFE.cc:143:33: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:145:43: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:145:74: error: ‘ThrowException’ was not declared in this scope ../IFE.cc:146:36: error: no matching function for call to ‘v8::Boolean::New(bool)’ ../IFE.cc:146:36: note: candidate is: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note: static v8::Handle<v8::Boolean> v8::Boolean::New(v8::Isolate*, bool) /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note:   candidate expects 2 arguments, 1 provided ../IFE.cc:166:31: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:168:43: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:168:72: error: ‘ThrowException’ was not declared in this scope ../IFE.cc:169:36: error: no matching function for call to ‘v8::Boolean::New(bool)’ ../IFE.cc:169:36: note: candidate is: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note: static v8::Handle<v8::Boolean> v8::Boolean::New(v8::Isolate*, bool) /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note:   candidate expects 2 arguments, 1 provided ../IFE.cc:173:50: error: ‘inet_pton’ was not declared in this scope ../IFE.cc:174:7: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:174:7: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:174:7: error: ‘ThrowException’ was not declared in this scope ../IFE.cc:174:7: error: no matching function for call to ‘v8::Boolean::New(bool)’ ../IFE.cc:174:7: note: candidate is: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note: static v8::Handle<v8::Boolean> v8::Boolean::New(v8::Isolate*, bool) /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note:   candidate expects 2 arguments, 1 provided ../IFE.cc:174:7: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:174:7: error: ‘ThrowException’ was not declared in this scope ../IFE.cc:174:7: error: no matching function for call to ‘v8::Boolean::New(bool)’ ../IFE.cc:174:7: note: candidate is: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note: static v8::Handle<v8::Boolean> v8::Boolean::New(v8::Isolate*, bool) /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note:   candidate expects 2 arguments, 1 provided ../IFE.cc:175:7: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:175:7: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:175:7: error: ‘ThrowException’ was not declared in this scope ../IFE.cc:175:7: error: no matching function for call to ‘v8::Boolean::New(bool)’ ../IFE.cc:175:7: note: candidate is: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note: static v8::Handle<v8::Boolean> v8::Boolean::New(v8::Isolate*, bool) /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note:   candidate expects 2 arguments, 1 provided ../IFE.cc:175:7: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:175:7: error: ‘ThrowException’ was not declared in this scope ../IFE.cc:175:7: error: no matching function for call to ‘v8::Boolean::New(bool)’ ../IFE.cc:175:7: note: candidate is: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note: static v8::Handle<v8::Boolean> v8::Boolean::New(v8::Isolate*, bool) /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note:   candidate expects 2 arguments, 1 provided ../IFE.cc:176:7: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:176:7: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:176:7: error: ‘ThrowException’ was not declared in this scope ../IFE.cc:176:7: error: no matching function for call to ‘v8::Boolean::New(bool)’ ../IFE.cc:176:7: note: candidate is: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note: static v8::Handle<v8::Boolean> v8::Boolean::New(v8::Isolate*, bool) /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note:   candidate expects 2 arguments, 1 provided ../IFE.cc:176:7: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:176:7: error: ‘ThrowException’ was not declared in this scope ../IFE.cc:176:7: error: no matching function for call to ‘v8::Boolean::New(bool)’ ../IFE.cc:176:7: note: candidate is: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note: static v8::Handle<v8::Boolean> v8::Boolean::New(v8::Isolate*, bool) /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note:   candidate expects 2 arguments, 1 provided ../IFE.cc:180:35: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:186:43: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:186:63: error: ‘ThrowException’ was not declared in this scope ../IFE.cc:187:36: error: no matching function for call to ‘v8::Boolean::New(bool)’ ../IFE.cc:187:36: note: candidate is: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note: static v8::Handle<v8::Boolean> v8::Boolean::New(v8::Isolate*, bool) /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note:   candidate expects 2 arguments, 1 provided ../IFE.cc:191:17: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:192:17: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:194:36: error: no matching function for call to ‘v8::Boolean::New(bool)’ ../IFE.cc:194:36: note: candidate is: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note: static v8::Handle<v8::Boolean> v8::Boolean::New(v8::Isolate*, bool) /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note:   candidate expects 2 arguments, 1 provided ../IFE.cc:196:33: error: no matching function for call to ‘v8::Boolean::New(bool)’ ../IFE.cc:196:33: note: candidate is: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note: static v8::Handle<v8::Boolean> v8::Boolean::New(v8::Isolate*, bool) /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note:   candidate expects 2 arguments, 1 provided ../IFE.cc: At global scope: ../IFE.cc:199:33: error: ‘Arguments’ does not name a type ../IFE.cc:199:44: error: ISO C++ forbids declaration of ‘args’ with no type [-fpermissive] /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h: In static member function ‘static v8::Handle<v8::Value> node::IFE::down(const int&)’: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:816:13: error: ‘v8::HandleScope::HandleScope()’ is protected ../IFE.cc:200:17: error: within this context ../IFE.cc:203:31: error: request for member ‘Holder’ in ‘args’, which is of non-class type ‘const int’ ../IFE.cc:207:14: error: invalid types ‘const int[int]’ for array subscript ../IFE.cc:208:43: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:208:77: error: ‘ThrowException’ was not declared in this scope ../IFE.cc:209:20: error: ‘class v8::HandleScope’ has no member named ‘Close’ ../IFE.cc:209:36: error: too few arguments to function ‘v8::Handle<v8::Primitive> v8::Undefined(v8::Isolate*)’ /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:305:28: note: declared here ../IFE.cc:211:30: error: invalid types ‘const int[int]’ for array subscript ../IFE.cc:213:48: error: ‘inet_pton’ was not declared in this scope ../IFE.cc:220:43: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:220:61: error: ‘ThrowException’ was not declared in this scope ../IFE.cc:221:20: error: ‘class v8::HandleScope’ has no member named ‘Close’ ../IFE.cc:221:36: error: too few arguments to function ‘v8::Handle<v8::Primitive> v8::Undefined(v8::Isolate*)’ /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:305:28: note: declared here ../IFE.cc:223:13: error: request for member ‘Length’ in ‘args’, which is of non-class type ‘const int’ ../IFE.cc:224:7: error: ‘AsciiValue’ is not a member of ‘v8::String’ ../IFE.cc:224:30: error: expected ‘;’ before ‘val’ ../IFE.cc:233:17: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:234:17: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:236:36: error: no matching function for call to ‘v8::Boolean::New(bool)’ ../IFE.cc:236:36: note: candidate is: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note: static v8::Handle<v8::Boolean> v8::Boolean::New(v8::Isolate*, bool) /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note:   candidate expects 2 arguments, 1 provided ../IFE.cc:238:33: error: no matching function for call to ‘v8::Boolean::New(bool)’ ../IFE.cc:238:33: note: candidate is: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note: static v8::Handle<v8::Boolean> v8::Boolean::New(v8::Isolate*, bool) /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note:   candidate expects 2 arguments, 1 provided ../IFE.cc: At global scope: ../IFE.cc:241:36: error: ‘Arguments’ does not name a type ../IFE.cc:241:47: error: ISO C++ forbids declaration of ‘args’ with no type [-fpermissive] /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h: In static member function ‘static v8::Handle<v8::Value> node::IFE::gratarp(const int&)’: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:816:13: error: ‘v8::HandleScope::HandleScope()’ is protected ../IFE.cc:247:17: error: within this context ../IFE.cc:249:29: error: invalid types ‘const int[int]’ for array subscript ../IFE.cc:250:33: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:252:43: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:252:74: error: ‘ThrowException’ was not declared in this scope ../IFE.cc:253:36: error: no matching function for call to ‘v8::Boolean::New(bool)’ ../IFE.cc:253:36: note: candidate is: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note: static v8::Handle<v8::Boolean> v8::Boolean::New(v8::Isolate*, bool) /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note:   candidate expects 2 arguments, 1 provided ../IFE.cc:259:33: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:261:43: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:261:78: error: ‘ThrowException’ was not declared in this scope ../IFE.cc:262:36: error: no matching function for call to ‘v8::Boolean::New(bool)’ ../IFE.cc:262:36: note: candidate is: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note: static v8::Handle<v8::Boolean> v8::Boolean::New(v8::Isolate*, bool) /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note:   candidate expects 2 arguments, 1 provided ../IFE.cc:266:46: error: ‘inet_pton’ was not declared in this scope ../IFE.cc:267:43: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:267:66: error: ‘ThrowException’ was not declared in this scope ../IFE.cc:268:36: error: no matching function for call to ‘v8::Boolean::New(bool)’ ../IFE.cc:268:36: note: candidate is: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note: static v8::Handle<v8::Boolean> v8::Boolean::New(v8::Isolate*, bool) /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note:   candidate expects 2 arguments, 1 provided ../IFE.cc:271:32: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:273:43: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:273:79: error: ‘ThrowException’ was not declared in this scope ../IFE.cc:274:36: error: no matching function for call to ‘v8::Boolean::New(bool)’ ../IFE.cc:274:36: note: candidate is: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note: static v8::Handle<v8::Boolean> v8::Boolean::New(v8::Isolate*, bool) /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note:   candidate expects 2 arguments, 1 provided ../IFE.cc:278:44: error: ‘inet_pton’ was not declared in this scope ../IFE.cc:279:39: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:279:61: error: ‘ThrowException’ was not declared in this scope ../IFE.cc:280:36: error: no matching function for call to ‘v8::Boolean::New(bool)’ ../IFE.cc:280:36: note: candidate is: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note: static v8::Handle<v8::Boolean> v8::Boolean::New(v8::Isolate*, bool) /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:6194:17: note:   candidate expects 2 arguments, 1 provided ../IFE.cc:283:33: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:301:41: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:301:72: error: ‘ThrowException’ was not declared in this scope ../IFE.cc:302:22: error: ‘class v8::HandleScope’ has no member named ‘Close’ ../IFE.cc:302:38: error: too few arguments to function ‘v8::Handle<v8::Primitive> v8::Undefined(v8::Isolate*)’ /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:305:28: note: declared here ../IFE.cc:306:13: error: request for member ‘Length’ in ‘args’, which is of non-class type ‘const int’ ../IFE.cc:307:17: error: invalid types ‘const int[int]’ for array subscript ../IFE.cc:308:45: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:308:93: error: ‘ThrowException’ was not declared in this scope ../IFE.cc:309:22: error: ‘class v8::HandleScope’ has no member named ‘Close’ ../IFE.cc:309:38: error: too few arguments to function ‘v8::Handle<v8::Primitive> v8::Undefined(v8::Isolate*)’ /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:305:28: note: declared here ../IFE.cc:311:21: error: invalid types ‘const int[int]’ for array subscript ../IFE.cc:314:13: error: request for member ‘Length’ in ‘args’, which is of non-class type ‘const int’ ../IFE.cc:315:17: error: invalid types ‘const int[int]’ for array subscript ../IFE.cc:316:45: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:316:93: error: ‘ThrowException’ was not declared in this scope ../IFE.cc:317:22: error: ‘class v8::HandleScope’ has no member named ‘Close’ ../IFE.cc:317:38: error: too few arguments to function ‘v8::Handle<v8::Primitive> v8::Undefined(v8::Isolate*)’ /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:305:28: note: declared here ../IFE.cc:319:23: error: invalid types ‘const int[int]’ for array subscript ../IFE.cc:321:41: error: ‘New’ is not a member of ‘v8::String’ ../IFE.cc:321:89: error: ‘ThrowException’ was not declared in this scope ../IFE.cc:322:22: error: ‘class v8::HandleScope’ has no member named ‘Close’ ../IFE.cc:322:38: error: too few arguments to function ‘v8::Handle<v8::Primitive> v8::Undefined(v8::Isolate*)’ /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:305:28: note: declared here ../IFE.cc:327:18: error: ‘class v8::HandleScope’ has no member named ‘Close’ ../IFE.cc:327:42: error: no matching function for call to ‘v8::Integer::New(int&)’ ../IFE.cc:327:42: note: candidate is: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:2012:25: note: static v8::Local<v8::Integer> v8::Integer::New(v8::Isolate*, int32_t) /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/deps/v8/include/v8.h:2012:25: note:   candidate expects 2 arguments, 1 provided In file included from ../IFEheader.h:4:0,                  from ../IFE.cc:12: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/src/node_object_wrap.h: In static member function ‘static T* node::ObjectWrap::Unwrap(v8::Handle<v8::Object>) [with T = node::IFE]’: ../IFE.cc:139:43:   instantiated from here /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/src/node_object_wrap.h:55:32: error: ‘node::ObjectWrap’ is an inaccessible base of ‘node::IFE’ ../IFE.cc: In static member function ‘static v8::Handle<v8::Value> node::IFE::gratarp(const int&)’: ../IFE.cc:328:3: warning: control reaches end of non-void function [-Wreturn-type] ../IFE.cc: In static member function ‘static v8::Handle<v8::Value> node::IFE::down(const int&)’: ../IFE.cc:239:3: warning: control reaches end of non-void function [-Wreturn-type] /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/src/node_object_wrap.h: In static member function ‘static T* node::ObjectWrap::Unwrap(v8::Handle<v8::Object>) [with T = node::IFE]’: /home/debian/sandbox/node_modules/ife/.node-gyp/0.12.0/src/node_object_wrap.h:56:3: warning: control reaches end of non-void function [-Wreturn-type] ../IFE.cc: In static member function ‘static v8::Handle<v8::Value> node::IFE::up(const int&)’: ../IFE.cc:197:3: warning: control reaches end of non-void function [-Wreturn-type] ../IFE.cc: In static member function ‘static v8::Handle<v8::Value> node::IFE::list(const int&)’: ../IFE.cc:132:3: warning: control reaches end of non-void function [-Wreturn-type] ../IFE.cc: In static member function ‘static v8::Handle<v8::Value> node::IFE::arpcache(const int&)’: ../IFE.cc:92:3: warning: control reaches end of non-void function [-Wreturn-type] ../IFE.cc: In static member function ‘static v8::Handle<v8::Value> node::IFE::New(const int&)’: ../IFE.cc:70:3: warning: control reaches end of non-void function [-Wreturn-type] make: *** [Release/obj.target/IFEBinding/IFE.o] Error 1 make: Leaving directory /home/debian/sandbox/node_modules/ife/build'
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:267:23)
gyp ERR! stack     at ChildProcess.emit (events.js:110:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:1067:12)
gyp ERR! System Linux 3.14.1_006-trio2000
gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/debian/sandbox/node_modules/ife
gyp ERR! node -v v0.12.0
gyp ERR! node-gyp -v v1.0.2
gyp ERR! not ok
npm ERR! Linux 3.14.1_006-trio2000
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "ife"
npm ERR! node v0.12.0
npm ERR! npm  v2.5.1
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the ife package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls ife
npm ERR! There is likely additional logging output above.
npm ERR!

Also unable to install on Ubuntu 16.04
here's where it failed
60 verbose lifecycle<EMAIL_ADDRESS>CWD: /home/dash/node_modules/ife 61 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'node-gyp rebuild' ] 62 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null 63 info lifecycle<EMAIL_ADDRESS>Failed to exec install script 64 verbose unlock done using /home/dash/.npm/_locks/staging-4cd1093b6e015bea.lock for /home/dash/node_modules/.staging 65 warn enoent ENOENT: no such file or directory, open '/home/dash/package.json' 66 verbose enoent This is related to npm not being able to find a file. 67 warn dash No description 68 warn dash No repository field. 69 warn dash No README data 70 warn dash No license field. 71 verbose stack Error<EMAIL_ADDRESS>install: node-gyp rebuild71 verbose stack Exit status 1 71 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:280:16) 71 verbose stack     at emitTwo (events.js:126:13) 71 verbose stack     at EventEmitter.emit (events.js:214:7) 71 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) 71 verbose stack     at emitTwo (events.js:126:13) 71 verbose stack     at ChildProcess.emit (events.js:214:7) 71 verbose stack     at maybeClose (internal/child_process.js:925:16) 71 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5) 72 verbose pkgid<EMAIL_ADDRESS>73 verbose cwd /home/dash 74 verbose Linux 4.13.0-32-generic 75 verbose argv "/usr/bin/node" "/usr/bin/npm" "install" "ife" 76 verbose node v8.9.2 77 verbose npm  v5.5.1 78 error code ELIFECYCLE 79 error errno 1 80 error<EMAIL_ADDRESS>install:node-gyp rebuild80 error Exit status 1 81 error Failed at the<EMAIL_ADDRESS>install script. 81 error This is probably not a problem with npm. There is likely additional logging output above. 82 verbose exit [ 1, true ]


Fix presser audit typos

Fixes https://github.com/EmbarkStudios/rust-ecosystem/pull/91/files#r1038109294

oh @fu5ha you didn't remove the wrong puffin audit in here!

third time the charm?

Oops hahaha. I guess because I fixed it on my exisitng branch rather than making a new patch on main. Thanks!

ah that's why I missed it also because I searched through the file in your PR, but didn't spot it


Improve SYCL kernels in CSR table

Description
Please include a summary of the change. For large or complex changes please include enough information to introduce your change and explain motivation for it.
Changes proposed in this pull request:

/intelci: run

/intelci: run

/intelci: run


[ BUG ] Latest CLI Cant install components

Describe the bug
Installing components using:  npx @react-native-reusables/cli@latest add radio-group. No longer works since the release of<EMAIL_ADDRESS>
Using the newest version I get the error above, however if I use<EMAIL_ADDRESS>all works fine, I'm not sure if its something I have missed or need to change for the latest version. Or if it is indeed a bug
Expected behavior
Install component, which works on the previous version of cli within my project
Platform (please complete the following information):

VS Code

Getting the same over here:
{
  "platforms": "universal",
  "aliases": {
    "components": "~/components",
    "lib": "~/lib"
  }
}

Looks like a result of https://github.com/mrzachnugent/react-native-reusables/commit/743f58d7a0cf19b94da3afad4d2b742210334381. Is there a changelog anywhere? Love all the improvements but having trouble finding anything documenting them + any breaking changes.

Just published the fix.
@mattmatters There isn't a changelog yet. Haven't gotten around to it. If that's something you'd like to add, PRs are welcomed.

Just published the fix.
@mattmatters There isn't a changelog yet. Haven't gotten around to it. If that's something you'd like to add, PRs are welcomed.

Thanks for being so prompt. Let me see if I can get something going. Definitely would like to give back to this project in some way.

Thanks for being so quick @mrzachnugent ! loving the project also :)


CU19 has gone, CU20 details here!

Linky: https://download.microsoft.com/download/6/e/7/6e72dddf-dfa4-4889-bc3d-e5d3a0fd11ce/SQLServer2019-KB5024276-x64.exe
Version: 15.0.4312.2
Cheers!

@westy Fixed with https://github.com/tfenster/mssql-image/commit/8b55cc9c95ad19b7717bc6ae0bb8d2b2b5bb8953, thanks!


feat(type-designer) Display Type References

Display Type References
As a User
I want to see references to types from the next column
So that I can understand the relationships between elements.
Acceptance Criteria:

[ ] In the edit drawer of a type, an option make it possible to create the link between two types, to create a type ref.
In 'IED 1 Type' config, there is a 'link to' option specifying Bays types: Choosing one creates a new type reference card underneath it.
[x] Each card might display type references cards underneath, only from types from the next column (on the right).
[ ] The types references should update dynamically as elements are added or removed.
[ ] A specific UI icon makes it clear that the card is a type reference

A 180-degree turn in logic is planned in another PR, with the team agreeing on a different way of handling the parent-child relationship in SCD integration.


tests: add data file consistency test for concoctions

Tests as discussed in #2331.

I will put together a test for this, I thought we already had one.

Probably not but...
There is a generic datafile structure test that does not include concoctions.txt because it it "too complex".  I have a feeling someone wrote a similar concoctions specific test but I could not find it quickly.  I suspect what I am remembering was never committed.
The gCLI command "checkconcoctions" iterates over concoctions to confirm that Concoction.compareTo() meets its contract for all concoction data.  Sometimes running that turns up inconsistencies in concoctions.txt.  The check was deliberately made a command, and not a test, because it takes time and made running the tests longer than people liked.  I just ran it and there are some things to be fixed but none of them seem to be Mayam.


Migration from dbt-vertica 1.6.0 to 1.7.x

What are you changing in this pull request and why?

Checklist

[ ] Review the Content style guide so my content adheres to these guidelines.
[ ] For docs versioning, review how to version a whole page and version a block of content.
[ ] Add a checklist item for anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."

Adding new pages (delete if not applicable):

[ ] Add page to website/sidebars.js
[ ] Provide a unique filename for the new page

Removing or renaming existing pages (delete if not applicable):

[ ] Remove page from website/sidebars.js
[ ] Add an entry website/static/_redirects
[ ] Run link testing locally with npm run build to update the links that point to the deleted page

hey @Sachin-Thakur thanks for opening this up. looks great and i tweaked it a little and removed the 'v1.7.0 and newer' since te reusable partial already includes it and it was repeating. going to merge this and thank you again ✨


fix bug where _children might be null when handling a terminated message

In the included test, _children is null, so the _children.Remove call threw an exception. This PR just checks for null first.

👍


Update mrclay/minify version ?

Hello,
Could be great to benefit from last fixes of mrclay/minify 3.0.x !

@Nuranto I just updated dependencies to mrclay/minify  ^3.0 in the develop branch. Please try it and let me know if you have any issues:
composer require stolz/assets:dev-develop

Hello @Stolz
There's a fatal error in Manager class. \JSMin have to become \JSMin\JSMin
When that's fixed, it seems OK.


Can't install Bosch-Thermostat

Hi, I can't install the Plugin.
My Setup:
Hass with docker on Arabian 23.11.
Installed Repository over HACS.
If I want to install the integration I get a:
Error
Config flow could not be loaded: {"message":"Invalid handler specified"}.
So the integration cannot be installed.
I get the following logs in HASS:
`Logger: homeassistant.loader
Source: loader.py:847
First occurred: 8:46:30 AM (2 occurrences)
Last logged: 8:53:28 AM
Unexpected exception importing platform custom_components.bosch.config_flow
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/loader.py", line 847, in get_platform
cache[full_name] = self._import_platform(platform_name)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/loader.py", line 864, in _import_platform
return importlib.import_module(f"{self.pkg_path}.{platform_name}")
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/importlib/init.py", line 90, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "", line 1387, in _gcd_import
File "", line 1360, in _find_and_load
File "", line 1310, in _find_and_load_unlocked
File "", line 488, in _call_with_frames_removed
File "", line 1387, in _gcd_import
File "", line 1360, in _find_and_load
File "", line 1331, in _find_and_load_unlocked
File "", line 935, in _load_unlocked
File "", line 994, in exec_module
File "", line 488, in _call_with_frames_removed
File "/config/custom_components/bosch/init.py", line 12, in
from bosch_thermostat_client.const import (
File "/usr/local/lib/python3.12/site-packages/bosch_thermostat_client/init.py", line 10, in
from .gateway import gateway_chooser
File "/usr/local/lib/python3.12/site-packages/bosch_thermostat_client/gateway/init.py", line 1, in
from .ivt import IVTGateway, IVTMBLanGateway
File "/usr/local/lib/python3.12/site-packages/bosch_thermostat_client/gateway/ivt.py", line 6, in
from bosch_thermostat_client.connectors import connector_ivt_chooser
File "/usr/local/lib/python3.12/site-packages/bosch_thermostat_client/connectors/init.py", line 2, in
from .ivt import IVTXMPPConnector
File "/usr/local/lib/python3.12/site-packages/bosch_thermostat_client/connectors/ivt.py", line 2, in
import aioxmpp
File "/usr/local/lib/python3.12/site-packages/aioxmpp/init.py", line 101, in
from .errors import (  # NOQA
File "/usr/local/lib/python3.12/site-packages/aioxmpp/errors.py", line 538, in
class UserError(Exception):
File "/usr/local/lib/python3.12/site-packages/aioxmpp/errors.py", line 559, in UserError
DEFAULT_FORMATTER = i18n.LocalizingFormatter()
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/aioxmpp/i18n.py", line 108, in init
self.tzinfo = tzinfo if tzinfo is not None else tzlocal.get_localzone()
^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/tzlocal/unix.py", line 219, in get_localzone
_cache_tz = _get_localzone()
^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/tzlocal/unix.py", line 176, in _get_localzone
tzenv = utils._tz_from_env()
^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/tzlocal/utils.py", line 109, in _tz_from_env
raise zoneinfo.ZoneInfoNotFoundError(
zoneinfo._common.ZoneInfoNotFoundError: 'tzlocal() does not support non-zoneinfo timezones like MY_TIME_ZONE. \nPlease use a timezone in the form of Continent/City'
`
and:
`Logger: homeassistant.config_entries
Source: config_entries.py:2275
First occurred: 8:46:30 AM (2 occurrences)
Last logged: 8:53:28 AM
Error occurred loading flow for integration bosch: Exception importing custom_components.bosch.config_flow`
HASS Version is:
Core
2024.2.4
Frontend
20240207.1
Python 3.12.1 (main, Jan  4 2024, 12:00:29) [GCC 13.2.1 20231014] on linux
Is there anything I can do?
Regards
Christian

From the beginning if the readme:
It will only work with at least Home Assistant 2023.7 and maximum 2024.1 and Python >=3.11. It won't work with Home Assistant 2024.2 installed on HAOS which delivers Python 3.12.

May I ask, is there a timelime for support of HA 2024.2 ?

Don't know yet... https://github.com/bosch-thermostat/home-assistant-bosch-custom-component/issues/390#issuecomment-1965056042


higher order finite diff tests

Currently, we have no finite diff tests for second and third order derivatives, but we should have higher-order finite diff tests.

This issue was moved to stan-dev/math#66


Upgrade @actions/core dependency version

Issue #, if available:
Description of changes:
Upgrades @actions/core dependency version. Required to resolve warning against using set-output and save-state (Github is deprecating this and pipelines that use it will begin failing in June according to their docs)
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thanks for the notice, just set up dependabot and merged #23 . Closing this as it's now a duplicate.


Fix Yarn file system collisions

This pull request should fix Yarn file system collisions between Rugged and its test projects when testing itself.
Closes #35

Does the tmp/.mutex file have to exist first, or will Yarn create it if it doesn't exist?

Does the tmp/.mutex file have to exist first, or will Yarn create it if it doesn't exist?

The docs would make you think this was fine, but when I did this, our tests hang on the last project:

I'm not sure why that is, I'll try to investigate.

Okay, so I changed the approach entirely and used the network mutex option instead of file I think it has had a net effect of very slightly decreasing complexity in getConfig, and there don't seem to be any problems with the pipeline now that it's run through. It did seem to take longer than it did before, but that could be a coincidence or a byproduct of it avoiding conflicts.

Do we really need to specify the port manually? Or allow that to be configurable? Seems like something Yarn can/should figure out on its own.

Do we really need to specify the port manually? Or allow that to be configurable? Seems like something Yarn can/should figure out on its own.

The default port is the same one that yarn would use, however Yarn's docs don't specify what happens if that port is occupied, and I have some inclination to say it would just wait for the port to be open, I made it manually configurable in the case that for some reason someone using Rugged was continuously making use of Yarn's default port.


how to  save image returned from img = api.photo.random() function

from unsplash.api import Api
from unsplash.auth import Auth
client_id = ""
client_secret = ""
redirect_uri = ""
code = ""
auth = Auth(client_id, client_secret, redirect_uri, code=code)
api = Api(auth)
img = api.photo.random()
How to save the image which is returned as [Photo(id='Lg9uUduhSrc')]

did you get the solution?


feat(schema) add new config error array

Summary
A variant of https://github.com/Kong/kong/pull/9806. Whereas #9806 adds its additional error metadata as a new field inside the existing error objects, this variant adds a new fields.flattened section, containing an array of error objects (example). The new error objects store entity type and field names as values, rather than keys, allowing them to unmarshal into a Go struct.
Checklist

[ ] The Pull Request has tests
[ ] There's an entry in the CHANGELOG
[ ] There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Full changelog

Add an error accumulator table to schema validation and return it when POST /config encounters errors
Add a field to track whether errors have been processed and added to the error accumulator already. Strip this field before returning errors.

Issue reference
FTI-4366

At a high level, this approach shifts the complexity of dealing with the recursive nature of schema validation errors from their consumers (in our case, KIC) to the schema validation code. This PoC produces errors that can be easily unmarshaled in simpler cases, but fails on others:

Errors within complex objects, where fields have object values, does not successfully strip out the nested annotations. For example, setting an HTTP status code within upstream health probe configuration to a string results in garbage output.
Some unknown quality of controller-generated configuration causes a duplicate error entry in Kong's output. One of the duplicates lacks its errors. Unclear what causes this, since I encountered it at the end of the day and I couldn't reproduce it with manual testing.

The design is also very PoC-y and needs to be refined:

At a glance, it remains difficult to distinguish fields that contain other entities (e.g. a routes field under a services entry). These fields are treated effectively the same as any other: although they're handled via a dedicated case in the field validator, that information is not propagated back with errors. The additional nested field attempts to do this, but it's clunky, since in practice you need to look a few levels down into the object, and do some type guesswork, to find it.
The starting schema isn't obviously special. Schemas are hierarchical collections of more schemas, and there isn't a top-level schema type accessible throughout validation for storing the accumulated errors. The hack approach is to stuff it in ngx.ctx, but that's a poor solution. I don't know if there's some existing part of the parent/subschema relationship that would be appropriate for this, or where would be best to refactor the schema validator if not.

Superseded by https://github.com/Kong/kong/pull/10161


timeout waiting for app to be ready to install

clicking "Install Update"
times out waiting for "Ready to Install" button
UI Test Activity:
Assertion Failure: UpdateAppTest.swift:40: XCTAssertTrue failed - "Ready to Install" StaticText has not appeared

https://github.com/sparta-science/connect/blob/16222e88b603ebcd4e2e7d958264c44346c597f2/UITests/UpdateAppTest.swift#L38-L44

UI Test Activity:
Assertion Failure: UpdateAppTest.swift:41: XCTAssertTrue failed - "Ready to Install" StaticText has not appeared

timing out while downloading:


Inconsistency regarding modified date

I was following your sample code to update modified date and It was not working.
After going through source code of single page layout: https://github.com/mmistakes/minimal-mistakes/blob/master/_layouts/single.html, I came to realise the key for modified date has changed from modified to last_modified_at.

This is a really easy "first commit" if someone wants to help out and submit a pull request to change modified to last_modified_at in sample posts and docs.

I was confused, which one among doc and code was intended. Now it's clear, I can commit to update docs and send you pull request

Fixed in #929


feat(version): 0.4

Closes: #69
Signed-off-by: Jarkko Sakkinen<EMAIL_ADDRESS>

@haraldh this fails too, version bump does not help

@jarkkojs He probably meant a version bump of the MSRV.


Added Microsoft Edge Dev version 117.0.2007.0.

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/114357&drop=dogfoodAlpha

@wingetbot run


Removed delete of user config'd setup method

Using deep copy instead. Otherwise, subsequent tinymce inits do not have the user specified setup method.
Fixes issue angular-ui/ui-tinymce#122

This should now be fixed in master. Let me know if this is still an issue.


Add OpenTelemetry tracer

For the trace dropping, I've tried multiple things:

custom sampler: didn't work. we dropped the parent span, but couldn't access child spans.
don't call span.End() for dropped spans - this works but children spans still show up in the UI
filter spans in otel-collector.yml - same issue, only drops the parent span

For the trace dropping, I've tried multiple things:

I think the only thing we can do is to create an issue in the otel sdk?
https://github.com/open-telemetry/opentelemetry-go/issues

@ilya-hontarau I'll probably do but keep in mind that this is a fairly serious standard, so all SDKs would need to follow and implement it, so I don't have high hopes


Model named "Transaction" breaks SQLite

Describe the bug
If you name your model "Transaction", SQLite throws an error:
2021-05-14 15:21:03.801849-0700 bad-name[75507:11180230] [logging] near "Transaction": syntax error in "create table if not exists Transaction (
  "id" text primary key not null,
  "value" text
);"
2021-05-14 15:21:03.803693-0700 bad-name[75507:11180230] [AWSDataStorePlugin] The operation couldn’t be completed. (Amplify.DataStoreError error 8.)
2021-05-14 15:21:03.803790-0700 bad-name[75507:11180230] [logging] near "Transaction": syntax error in "select count(id) from Transaction where id = ?"
failure(DataStoreError: The operation couldn’t be completed. (SQLite.Result error 0.)
Recovery suggestion: The operation couldn’t be completed. (SQLite.Result error 0.)
Caused by:
near "Transaction": syntax error (code: 1))

To Reproduce
Steps to reproduce the behavior:

Create a model named "Transaction" (https://sandbox.amplifyapp.com/schema-design/4236af71-d0bb-47fa-9455-ddce75bcf525)
Generate code locally
Configure Amplify (only DataStore is needed)
Attempt to save instance of Transaction

Expected behavior
Models should be saved, regardless of name.
Environment(please complete the following information):

Amplify Framework Version: 1.9.2
Amplify Categories:

[ ] Analytics
[ ] API
[ ] Auth
[x] DataStore
[ ] Predictions
[ ] Storage

Dependency Manager: SPM
Swift Version: 5.4
CLI Version: 4.51.0
Xcode Version: 12.5 (12E262)

**Is this a regression (i.e. was this working before a version upgrade?)
I think this may have worked before, but can't be sure.
Device Information (please complete the following information):

Device: iPhone 11 Simulator
iOS Version: iOS 14.5
Specific to simulators: No, this error occurs on devices as well

xkcd -- Sorry, couldn't resist. 🤷🏻

suggestions for resolving the bug

Highlight the concept of reserved words to avoid in the documentation and the list of words NOT to use in table/field naming in the FAQ so that the user is aware of it
Incorporate reserved words check for table and field naming in the admin ui
Ideally, remove commonly used words like Transaction from the reserved words list

This should be fixed by the PR https://github.com/aws-amplify/amplify-ios/pull/1233 and will be available in the next release.

i believe this was released in https://github.com/aws-amplify/amplify-ios/releases/tag/v1.9.3 please let us know if you are still seeing issues

@lawmicha I just upgraded to v1.10.0 and I'm still experiencing this issue. My model is name Transaction and I keep getting this error [logging] near "Transaction": syntax error in "select   "root"."id" as "id", "root"."amount" as "amount", "root"."description" as "description" from Transaction as "root""  DataStoreError: The operation couldn’t be completed. (SQLite.Result error 0.) Recovery suggestion: The operation couldn’t be completed. (SQLite.Result error 0.) Caused by: near "Transaction": syntax error (code: 1)

@royjit This still has the pending release label, wondering if it has been released 'cause I still experience this?

@Kilo-Loco did you get this to work?

there's another PR that will fix this https://github.com/aws-amplify/amplify-ios/pull/1485 please track that PR, and should be released in the next amplify version 1.16.1 or greater


Adding entries in @PickList is only adding one entry

Issue Details
Type of Issue  (check one with "X")
[X] Bug Report => Please search GitHub for a similar issue or PR before submitting
[ ] Feature Request => Please ensure feature is not already in progress
[ ] Support Request => Please do not submit support requests here, instead see: https://discourse.oss.antheminc.com/

Current Behavior
When a @PickList is configured, adding entries from left to right is only adding one entry on the server side. e.g. if two two entries ["A", "B"] are in the left hand side, clicking add "A" and then add "B" will add the two entries in the picklist to the right side... but the network tab will show that "A" was added in both network requests.
Expected Behavior
The network tab should show both entries "A" and "B" added in each individual network request.
Environment Details

Nimbus Version:
1.3.1.M1

Browser:
Google Chrome

I took a look at the PrimeNG changes topicklist.component.ts from when we thought this was last working in 1.1.14.
From 1.1.14 to 1.3.1.M1, the PrimeNG version changed from 6.1.7 to 7.1.0.  Searching this Github diff for picklist.component.ts shows the difference... I don't think anything changed from PrimeNG's perspective that would have caused this issue.

There is one more issue with the picklists, the filter atop a picklist does not work.

There is one more issue with the picklists, the filter atop a picklist does not work.

@kumarraman, I'm not sure that these two issues would be related. Unless you think otherwise, can you please open a separate issue for this and outline how to reproduce the issue?

Added in 1.3.1.M4


Splitting up crate to reduce advisory blast radius?

As someone who wants to do what I think are reasonable and defensible uses of RSA (that is: RSASSA-PSS and RSASSA-PKCS1-v1_5) it would be great if there was a crate for that. But without bringing along the inevitable, infinite future security advisories for a crate that includes raw RSA, RSAES-PKCS1-v1_5, etc.
I think that could be done along protocol lines (eg, "rsa-signing" and "rsa-hazmat" crates?) or in an opinionated way (eg, "rsa-ok", "rsa-hazmat" crates?). The existing "rsa" crate could just reexport everything from these, perhaps?

FWIW, the Marvin Attack enables signature forgeries with RSASSA-PKCS#1v1.5 (i.e. BB'06-style)
The recent advisory affects all private key operations and allows a network attacker to recover either decryption or signing keys. Making modpow constant time (#394) will prevent key recovery but we still won't have fully mitigated the Marvin Attack which will still allow for both decryption and signature forgeries.
Constant-time modpow should enable safe use of OAEP or PSS, however.
We will continue to look into what can be done for PKCS#1v15 (e.g. moving to a pseudorandom rejection symbol for padding failures), however this is merely the latest in a long line of attacks which points to it being fundamentally flawed (see also The 9 Lives of Bleichenbacher's CAT).
(FWIW, this attack impacted many RSA libraries, many of which like the rsa crate are still vulnerable or have only partially mitigated it)

Yeah, due to #19 there's timing variability from signature operations which can leak the private key

Going to close this as splitting up the crate would not help for at least this specific incident


Parsing triples (nquads) with docker image ae095dab7896 significantly slower

REPOSITORY                                                    TAG                 IMAGE ID       CREATED        SIZE
adfreiburg/qlever                                             latest              ae095dab7896   16 hours ago   764MB
adfreiburg/qlever                                             previous            32a21873ce56   7 days ago     761MB

Speed with tag:latest
2024-10-17 20:15:07.644 - INFO: Triples parsed: 10,000,000 [average speed 0.3 M/s, last batch 0.3 M/s, fastest 0.3 M/s, slowest 0.3M/s]
Speed with tag:previous
2024-10-17 20:20:48.589 - INFO: Triples parsed: 10,000,000 [average speed 1.1 M/s, last batch 1.1 M/s, fastest 1.1 M/s, slowest 1.1 M/s]

@Stiksels Please set "parallel-parsing": true in your SETTINGS_JSON. The default has been changed to false. We had reasons for that, but it was still a bad idea, because most or all of the preconfigured Qleverfiles don't set parallel-parsing explicitly, and neither to most of Qleverfiles out there.

thanks @hannahbast that was the problem, with parallel-parsing set to true, the parsing speed is back up at 1.0M/s.
I see the following INFO and WARNING lines now:
2024-10-18 05:22:45.530 - INFO: You specified "parallel-parsing = true", which enables faster parsing for TTL files with a well-behaved use of newlines
2024-10-18 05:22:45.530 - WARN: Parallel parsing set to truein the.settings.json file; this is deprecated, please use the command-line  option --parse-parallel or -p instead
The issue from #1468 still remains, however: processing multiple large nquad files gets stuck on "merging partial vocabularies"


Remove oauth params from URL after authenticating

To avoid oauth and code getting duplicated and filling up the URL,
remove them after authenticating and redirecting back to TileBoard.
Use $location service to read and change query params. Allows to
remove crazy custom code for getting params and makes things much neater.
This PR also includes minor naming changes:

_request() => _tokenRequest()
url => data
New names better convey their actual purpose.

Resolves #279

Thank you!


Accept Uint8Array

Hi @pvorb ,
I want this library to accept Uint8Array.
It seems the library already accept Array,
and Uint8Array is also handled as well.
I don't have necessity for other typed arrays (Uint8ClampedArray, etc...),
so added Uint8Array only.

Thanks. Please fix the unit tests.

Thank you for your comment.
I've fixed the unit test,
putting polyfills directly in it for node.js 0.12.

Added note to README.


How to use context correctly?

This can be a dumb question due to I am new to context, my apologies first if I should not ask here.
For each operation with the client, it needs a context object. Should I create and save the only one context as the global variable then use it, or create it by context.Background()  every time when it is required then pass it to the function, or by other methods?
Thanks!

Hey @lynkas! That's not a dumb question at all, if you're new to Go's context, I'll recommend you to  read more about it here.
Sorry in advance that I'm keeping it short, I don't have too much time at the moment, and I prefer to "triage" issues as fast as I can. Also, some experts may explain it better than me.
There are many examples where Go context can be useful, here are some of our use cases:

Passing cancelations to database operations when a request is cancelled (it's mentioned in the link above)
Instrument the database operations (we use ocsql for this)
Add some statistics from our hooks
Inject {user, multi-tenancy, authorization} information to be used by the privacy later (and hooks)
Interact with other tools (e.g. gqlgen for supporting field collections)

And there are more - like I mentioned above, I'll recommended you to read about it before.

Should I create and save the only one context as the global variable then use it, or create it by context.Background() every time when it is required then pass it to the function, or by other methods?

For testing, you can context.Background(), for real code, I'll recommend you to use http.Reuqest.Context (if the operation is triggered by an HTTP request).
Closing, but feel free to continue the discussion if you still have questions.


SakHam

Hi  @SakHam, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added social share  to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.

hi Roshan Jossey,
I m a very beginner in git hub and general in open source community. Its my first time that a make a pull request, so i hope i did not anything wrong.
The tutorial is very good  and thank you very much. I hope i will help to solve some easy issues first.
Thanks again.
Από: Roshan Jossey<EMAIL_ADDRESS>Στάλθηκε: Δευτέρα, 26 Φεβρουαρίου 2018 5:17 μμ
Προς: Roshanjossey/first-contributions
Κοιν.: SakHam; Mention
Θέμα: Re: [Roshanjossey/first-contributions] SakHam (#3096)
Hi @SakHamhttps://github.com/sakham, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added social share to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Roshanjossey/first-contributions/pull/3096#issuecomment-368536560, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AjDhirAAw5UbmsFtTb00YisVh3nJ83jQks5tYssegaJpZM4STZtd.


Too many open files error on application server: LiquibaseEntityResolver opens too many file descriptors and never closes them

Environment

Java version: OpenJDK 11
Liquibase Version: newest (4.3.3)
Liquibase Integration & Version:  Java API (we're using new new Liquibase().listUnrunChangeSets manually). It's called from within a webapp with Jetty 9 / Tomcat 8 / Tomcat 9 / JSF 2.3 / Weld 3.1.7.
Database Vendor & Version: tested with MySQL 8 and PostgreSQL 12, but probably independent of DBMS
Operating System Type & Version: Ubuntu (tested on 18.04 and 20.10)

Description
Symptoms are the same as #1449, but not sure if it's the same cause (we're not using Spring). When running Liquibase, it opens many file decriptors and never closes them. They only get closed when the Garbabe  Collector runs, which may be a long in the future. This results in our application server crashing.
I first observed this on a test environment server with Tomcat 8 after upgrading vom liquibase 3 to liquibase 4. The webapp failed to start, and the log contained many too many open files messages. Checking via /proc/pid/fd indeed revealed that the number of file descriptors had reached the limit. At first I could not reproduce this locally on my machine, but now I can and I think I know why it happens:

The problematic part is in LiquibaseEntitiyResolve, which is called when Liquibase parses the database changelogs (we've got 11 XML changelog files) after we call `Liquibase#listUnrunChangeSets´.
When the LiquibaseEntityResolver is constructed, it also creates a fallbackResourceAccessor of type ClassLoaderResourceAccessor. The ClassLoaderResourceAccessor  loads all JARs of the application, but does so only lazily only when its #openStreams method is called.
Next the LiquibaseEntityResolver creates a CompositeResourceAccessor with the resource loader from the current scope and the fallback resource loader.  Now, and that's where the error starts happening, the composite resource accessor always calls openStreams on all accessors, regardless of whether an earlier found something or not.
This means that init method of the fallback ClassLoaderResourceAccessor is always called, loading all JARs.
In our case the LiquibaseEntityResolver is created about ~20 times, and each time it loads ~300 JARs. The fiel descriptor limit on the server is 4000, so it crashes before liquibase is done.
What I had been wondering is why I cannot observe this behavior locally, but now I've got an explanation for that. The same process I described above actually does happen  on my machine, but: the file descriptors are closed implicitly by the finalize  of the ZipFileSystem. When I debug into the application, I can observe the file descriptors growing on my machine as well. It's just that I seem to get lucky that the garbage collector kicks in early enough before even more file descriptors are opened. When
I increased the file descriptor limit on the test server, it finish running liquibase, but it only ran the finalizer and closed the file descriptor several minutes later (peak was ~6500 open file descriptors)

Is that enough information to reproduce? Not sure what the best solution here might be, but I guess some things that could be done are (i) closing the created file systems explicitly, (ii) not creating a new fallback accessor each time, (iii) not using the fallback accessor when the resource accessor from the current scope already returns a result.
┆Issue is synchronized with this Jira Bug by Unito

Hi @blutorange , what is the status of this issue?

@vesin Unless something has been done on this (looking at release 4.3.4 and 4.3.5 it seems not), this issue should still exist.
To summarize:

Use LiquiBase programmatically via new Liquibase(changelog, new ClassLoaderResourceAccessor(...), connection).update(...)
We have many changelogs, on the order of 15 changelog files with 50-200 changesets.
During the update process, as mentioned above, LiquibaseEntityResolver keeps creating new ClassLoaderResourceAccessors, which in turn keep creating more and more file handles to JAR files.
Our application has ~300 JAR files, so each time 300 file descriptors are created.
Currently Liquibase relies on the finalize method (of ZipFileSystem) to close the file descriptors. But depending on the garbage collector and the available RAM , this may not be called for several minutes.
This results in the system's limit being reached very quickly, so this is not usable in production.

As far as I can tell, this is not a random bug, but more like a conceptual issue with how  resource are handled, so I think somebody should definitely take a look at this.
So for the time being, we should be staying on 3.x until this gets fixed. Unfortunately, owasp-maven-plugin also reports critical security issues for 3.x, so we really need to update. We actually had to clone this project, make a quick and dirty fix to LiquibaseEntityResolver (just don't create a fallback resource accessor when there is a context resource accessor already) and compile that. But obiously that's not a good fix, a real fix would involve evaluating whether a fallback is needed, and if so, provide a single fallback that's not created everytime and close that at the end.
Also, we also had to subclass ClassLoaderResourceAccessor and add a #close method, since that class lazily opens file descriptors to JAR files, but provides not way of ever closing them, again relying on the finalize method.

For reference, this might be the problematic commit: https://github.com/liquibase/liquibase/pull/1621 There it creates a new ClassLoaderResourceAccessor within the resolve method. Since then, creating the accessor was moved into an instance field, but this is still problematic since liquibase creates more than one LiquibaseEntityResolver instance when run.

Also pretty similar to #1754 (probably the same cause), but that issue focuses on performance (doesn't seem to be slow for us), while this issue focuses on the application server process running out of resources

I updated the LiquibaseEntityResolver to be more efficient in how it creates ResourceAccessors and also made other code not construct as many instances of LiquibaseEntityResolver.
I was not able to replicate the original issue well to know for sure the fix solves the entire problem, though. Could you see if the fix in PR #1860 solves the problem for you, @blutorange ?

@nvoxland  That sounds great! I'll take a look as soon as I can during the next days and will let you know.

I can also try beta version as soon as you can make it public.

You can get a build with the changes off https://github.com/liquibase/liquibase/actions?query=branch%3ALB-1547
Can you try from that?

We have experienced similar performance issues as described in #1754 and the changes seem to have fixed it. I tested with the artifact linked by @nvoxland above.

Sorry it took a bit longer, but I can only really test this at work and I was away for a few days. So first of all, the changes from https://github.com/liquibase/liquibase/tree/LB-1547 definitely fix the issue.
There's one minor request I would like to make. We're using liquibase as follows:
var acc  = new ClassLoaderResourceAccessor(...);
try {
   var liqui = new Liquibase(file, acc, jdbcConnection);
   // ... do some work
}
finally {
   // not possible right now
   // acc.close();
}

What we'd like to do is close the resource accessor after use, so we can release the resources. Currently, ClassLoaderResourceAccessor has no close method -- could this be added? Otherwise it's never gets closed explicitly. It you let it implement AutoCloseable the implementation would look like this:
public class ClassLoaderResourceAccessor extends AbstractResourceAccessor implements AutoCloseable {
  // ...

  @Override
  public void close() throws Exception {
    if (rootPaths != null) {
      for (final FileSystem rootPath : rootPaths) {
        try {
          rootPath.close();
        }
        catch (final Exception e) {
          // ignore, if it can't be closed it might be cleaned up by the system / GC later
        }
      }
    }
  }
}

Thanks for testing the fix.
Yes, adding a close method to the ResourceAccessor interface is a good idea. This ticket will likely go out in a 4.4.1 release and we don't want to add interface changes in a patch release, so I created #1873 to get into a main release.

That sounds good, for now we can extend the class and add the close method ourselves. As for this ticket, I think we can close it then.

I tried solution with "AutoCloseable" and i still get same errors.
We have more then 300 change log files, and 40 tenants.

@vesin You did test with the fixed version (commit aeb34c9c91748926b207da18eeed14dca971b73a it's not in Maven yet I believe?) What I did to analyze the problem was to debug which JARs are opened when. At least for me, I don't see any JARs being opened more than once at a time. Do you see a JAR being opened more than once at the same time? When you create a ClassLoaderResourceAccessor, it should open the JARs once, and then reuse that accessor in LiquibaseENtityResolver without creating any new once. Once liquibase is done, your code should close the ClassLoaderResourceAccessor, which in turn should close the opened JAR files.
For debugging I set breakpoints in LiquibaseEntityResolver and in the constructors of jdk.nio.zipfs.JarFileSystem / jdk.nio.zipfs.ZipFileSystem. You can also check how many files are opened via ls /proc/<PID>/fd | wc -l and get a list of opened files via lsof -p 28537 (if you use Linux)

This is the code i use.
`@Service
public class LiquibaseService {
private static final Logger LOG = LoggerFactory.getLogger(LiquibaseService.class);
@Inject private MultiTenantConnectionProvider multiTenantConnectionProvider;

public boolean initLiquibase(String tenant) throws LiquibaseException, SQLException {
    LOG.debug("Initializing liquibase");

    final ClosableClassLoaderResourceAccessor resourceAccessor = new ClosableClassLoaderResourceAccessor();
    try (final Connection connection = multiTenantConnectionProvider.getConnection(tenant);
            ) {
        LOG.debug("Liquibase connection acquired for {}", tenant + "_core");
        final Database database = DatabaseFactory.getInstance().findCorrectDatabaseImplementation(new JdbcConnection(connection));
        database.setDefaultSchemaName(tenant + "_core");
        final Liquibase liquibase = new Liquibase("liquibase/db-changelog.xml", resourceAccessor, database);
        if (liquibase.listLocks().length > 0) {
            LOG.debug("Liquibase already locked.");
            return false;
        }
        LOG.debug("Liquibase update started");
        liquibase.update(new Contexts(), new LabelExpression());
        liquibase.close();
        return true;
    }finally{
        resourceAccessor.close();
    }
}

}
class ClosableClassLoaderResourceAccessor extends ClassLoaderResourceAccessor implements AutoCloseable {
private static final Logger LOG = LoggerFactory.getLogger(ClosableClassLoaderResourceAccessor.class);
@Override
public void close() {
if (rootPaths != null) {
for (final FileSystem rootPath : rootPaths) {
try {
LOG.info("Closing file" + rootPath.toString());
rootPath.close();
} catch (final Exception e) {
LOG.error("Unable to close resource", e);
// ignore, if it can't be closed it might be cleaned up by the system / GC later
}
}
}
}
}`

I still can't understand why does liquibase needs to load all jars to execute change logs...

@vesin : Liquibase looks through all the jars because we support having changelog files packaged in a jar file, and so we need to check if they are in there. The base ClassLoader interface does have the functionality we need, so we need to open them ourselves to check separately. The fix should make it so they don't keep being re-opened though. If you aren't using a build with the fix from #1873 in it, even your auto-closable logic will probably not help. The bug was buried a bit deeper.
For your use case, if you know better where your files will be you can use a different ResourceAccessor setup too. For example, if you use the ClassLoaderResourceAccessor(ClassLoader) constructor instead, it will look only in the locations specified in the passed classloader vs. all the jars in your entire application. There is also a FileSystemResourceAccessor that could work for you as well. A different classloader setup could avoid the bug enough to solve your problem until the actual fix goes out.

Great, thanks!

Thanks for testing the fix.
Yes, adding a close method to the ResourceAccessor interface is a good idea. This ticket will likely go out in a 4.4.1 release and we don't want to add interface changes in a patch release, so I created #1873 to get into a main release.

I see that #1873 is not resolved in the 4.4.0 release. Does this mean we cannot expect a fix before 4.5.0?

Hi all, when can we expect this fix to be released?


add a 10sec pause before we request instance termination

When the buildkite-agent exits cleanly (generally after an idle timeout), we ask the ASG to terminate the instance. The termination can happen very quickly, oftern within 2-3 seconds.
We use the legacy awslogs tool[1] to send logs to cloudwatch, and it buffers new logs for 5 seconds (or 32Kb, whichever comes first).
This results in a race condition - often the final logs from the agent as it shutdown may not make it to cloudwatch before the instance shuts down.
Long term we assume migrating from awslogs to the new cloudwatch agent might improve this situation. However, we don't plan to attempt that migration vor the v5 release and we'd like to improve the chances customers will have access to a full agent log in clouddwatch. Adding a 10 sec sleep before requesting termination is slightly-sad, but pragmatic option.
Note that this (sadly) won't resolve the race condition that prevents other useful logs from making it to cloudwatch, like the result of calling aws autoscaling terminate-instance-in-auto-scaling-group and systemd during shutdown

Hmmm, interesting.
That race condition can happen anyway, even without the new 10 second pause right? This might make it more likely to happen.
What's the impact? agent a could've been kept around to run the new job (potentially with warm caches), but agent b (with a cold cache) runs it instead?

There's one thing I forgot to consider in my hypothetical which is that the ASG will have its desired count decremented. This might incur the lag of waiting for another cycle of the agent scaler to reset the desired count. The impact is that it'll take longer to get an active agent in the pool.
This can be mitigated by adjusting the min-size and agent terminate-after-idle timeouts longer, so it really just comes down to performance tuning. Maybe it's not a big deal, it just popped into my head as a scenario that adding an extra delay will make slightly more likely.

It looks like the combination of this and #728 means that it can’t actually terminate the agent:
Oct 6 00:28:00 ip-10-0-x-xxx terminate-instance: requesting instance termination...
Oct 6 00:28:02 ip-10-0-x-xxx terminate-instance: An error occurred (ValidationError) when calling the TerminateInstanceInAutoScalingGroup operation: Currently, desiredSize equals minSize (2). Terminating instance without replacement will violate group's min size constraint. Either set shouldDecrementDesiredCapacity flag to false or lower group's min size.


chore: address linter findings in 07-tendermint

Description
Addresses all linting issues that would be found in 07-tendermint by upgrading golanci-lint version (see linked issue)

ref: #6086

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against the correct branch (see CONTRIBUTING.md).
[x] Linked to GitHub issue with discussion and accepted design, OR link to spec that describes this work.
[ ] Code follows the module structure standards and Go style guide.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/).
[ ] Added relevant godoc comments.
[x] Provide a conventional commit message to follow the repository standards.
[ ] Include a descriptive changelog entry when appropriate. This may be left to the discretion of the PR reviewers. (e.g. chores should be omitted from changelog)
[x] Re-reviewed Files changed in the GitHub PR explorer.
[ ] Review SonarCloud Report in the comment section below once CI passes.

Summary by CodeRabbit

Refactor

Enhanced error handling and type safety across various modules by introducing checks for successful type assertions before proceeding with operations.

Pretty admirable your persistence to fix all these linter errors, man. :)
We will have some merge conflicts, or linter screaming again depending on whether this PR mergers first or the ones for moving the 07-tendermint tests for client state to the light client module (this and this). Something just to keep in mind...

Thanks! I'll keep this PR open and solve merge conflicts when those two gets merged :)