Error running analyses in Habitus v1.9.6 from UCloud - permission denied

From my Home-Folder in UCloud, @vincentvanhees and myself tried to run several test-analyses in Habitus v.1.9.6. I'm getting an error "Permission denied" when running my test accelerometer and GPS data in UCloud. No results are processed in the UCloud Jobs folder.
Jasper tested the exact same data in the same Habitus version and it worked fine for him, so he asked us to repeat the analyses in Habitus with the excact same job-parameters in a .json file. Still, we are experiencing the same errors as before ("permission denied").
@emolinaro, can you help us with this problem? If it helps for you we can also share our data within UCloud... please let us know if you want us to also share this with you.
stdout.txt
stdout-2.txt
Testdata 01042022.zip
TestJasper.zip

@TeunRemmers this error happens when the input files are owned by root.
You should change the files ownership by launching another app, for example Terminal Ubuntu. You have to mount the data folder within this app instance and run the following command from the corresponding terminal interface:
sudo chown -R ucloud:ucloud /work/my_input_data_folder
Notice that sudo doesn't work within the HABITUS app. That's why you should use the app mentioned above.

When I tested it, I did not use the 'Select folders to use' section.
I think you only need this if you plan to work with data that is spread out over locations within UCloud. So, I think you can skip this for now.

This indicates that you cannot use sudo, try again without sudo: chown -R ucloud:ucloud /work/TestJasper

The "chown" command seems to work...

... but I'm still experiencing the same error in PalmsPy interface

This is not an error, but a warning. Please wait for the analyses to finish.

Thanks for the help Vincent, shortly (1-2 minutes) after the warning the server disconnects (see screenshot above). When I try to examine the results in the specified folder, no results exist. I also attached the config .json file and the log of Palmspy analyses.
PALMSpy.log
config.json.zip

@TeunRemmers does the PALMSpy log file in /work report some information?

@emolinaro what do you mean with the PALMSpy log in /work? I only have the folders beneath. Where can I find /work?

If you refer to the Jobs-folder, this does not include any PALMSpy log file (see beneath).

The HABITUS app should produce a log file in /work when the run is completed. It seems that the analysis was not completed when you closed the job.

Teun: /work is the folder you mounted when you started the app. From within the app this is called /work but from your own perspective it is probably something else. For example last week you shared this screen shot:

which would mean that your work for that run was /Home/TestJasper/Test01042022/data

@emolinaro thank you for you answer, I never changed the permissions of the folders. Now I tried to run the same analyses in the project "Skilfull Start" workspace. However from this workspace, I do not have access to Habitus v2.0-def but only Shiny v4.2.0. When I try to open the terminal in Shiny for subsequent PALMSpy analyses, I see the following screen (not the familiair terminal window) where you can specify PALMSpy / GGIR, etc.

Hi, you should not use the Shiny app anymore.  The script used to launch HABITUS in this app changes the folder permissions. You should use instead the app HABITUS v2.0-dev. Please, do the tests using the project "HABITUS development and testing". @vincentvanhees  can you add him to the project and then to the group "test_plamsplusr"? .

@TeunRemmers let me know when you have accepted the invitation for the project, because I then als need to add you to a group "test_palmsplusr". I cannot do that before you have accepted the first invitation.

@vincentvanhees I accepted the invitation.

Thanks, I have now also added you to the specific group. This is the group Emiliano and I used to test the app.

I've tested the data again in the new Shared data folder and I've made a little screen recording following all my steps so that you can maybe see what I'm doing wrong. You can also use the data in the Folder "Test01042022" to test if you can run my data successfully.
https://user-images.githubusercontent.com/102030034/178713516-cfa627d4-0fa5-457e-9c9c-7fc90f57e7f9.mp4

Thanks @TeunRemmers for recording the video.
In the log file I see:
Caused by: java.io.FileNotFoundException: /work/Test01042022/data/acc/1221_Fontys_80.csv (Permission denied)
java.io.FileNotFoundException: /work/Test01042022/data/acc/1221_Fontys_80.csv (Permission denied)
So, I then use the Ubuntu Terminal app and cd to the data folder I see:

this indicates that the folders are owned by user ucloud, but not the files which are still owned by root.
When I then try to chown everything in the data folder without sudo, it does not allow me:

but when I use sudo it allows me to do this:

the ownership has now changed from root to ucloud.
When I then re-run the Habitus 2.0-dev app, I see in the log file (via the terminal) that the problem is again with the Window sizes as we previously discussed with Jasper:

This looks like a problem with either the data, the config file or PALMSpy itself. To understand whether the Habitus 2.0-dev app plays a role in it,  you may want to process the file again with Habitus 1.9-6.
For some reason the Habitus 2.0-dev app crashes, which I think is a separate issue.


Three digit css shorthand for hex-values for color coding.

Three digit css shorthand hex-values for color coding.
Some browsers have this worng, and renders my colors wrong.
#963; becomes #936000

Just did some checks across modern browsers, then tried going all the way back to IE6 and it was able to render the color #963 correctly. Can you specify in which browser/circumstance you saw it be rendered wrong? Could it be another tool converting it incorrectly before applying it?

Closing for now, will re-open if a browser is proven to fail support here.

Samsung internet android v 11.22.3

https://codepen.io/Fyrd/pen/VweMdXJ looks the same in Samsung internet 11.2 as in other browsers


Unable to connect to existing RabbitMQ queue (creates a queue with destination.group naming scheme)

High-level issue definition:
Incorrect queue binding while connecting with existing RabbitMQ infrastructure.

Details:
I have a scenario where I would like to use existing infrastructure (queues, exchanges and bindings), from a spring cloud stream application with rabbitmq binding.
Spring Cloud dependency:
Release version: Greenwich.RELEASE
Artifact: spring-cloud-starter-stream-rabbit
Spring boot release version: 2.1.0

RabbitMQ infrastructure:
exchange: appExchange (direct)
queue: appQueue (durable)
binding: appExchange -> appQueue (routingKey: #)

Application Configuration:
spring:
  cloud:
    stream:
      bindings:
        appSink:
          destination: appExchange
          group: appQueue
          consumer:
            concurrency: 2
            bind-queue: false
            declare-exchange: false
            queue-name-group-only: true

This creates a new queue with the destination.group naming scheme resulting in appExchange.appQueue instead of connecting to the existing appQueue.
Alternatives that I've tried:

Destination and group with the same name:

        appSink:
          destination: appQueue
          group: appQueue

This creates a queue appQueue.appQueue

Blank destination

        appSink:
          group: appQueue

This creates a queue appSink.appQueue
Seems to me that queue-name-group-only: true is not being applied as I expect it. What am I missing or mis-configuring? Or is this a known limitation.
PS: I have been referring these source:

https://docs.spring.io/spring-cloud-stream/docs/current/reference/htmlsingle/#_rabbitmq_consumer_properties
https://stackoverflow.com/a/50351798/6886283

Works just fine now! Thanks for helping out, I should have been more careful.


Client RequestLogger does not work with some client implementations

http4s version: 0.20-M4
The RequestLogger middleware does not seem to work with the AsyncHttpClient or the OkHttpClient. It does work with BlazeClient.
When trying to view headers and a body of a request nothing seems to log (not even an empty log line). The ResponseLogger does work with all of the above clients.
See gitter discussion: https://gitter.im/http4s/http4s?at=5c3622f06370df0b91b56732
Have tried setting <logger name="org.http4s.client.middleware" level="INFO"/> in logback and my root logger to display DEBUG

This looks like a manifestation of #2348.


[1.3] chef-rvc-mode-delegate.cpp:115:115: error: ‘kOnOff’ is not a member of ‘chip::app::Clusters::RvcRunMode::Feature’

Reproduction steps
Hello,
I am facing error building Chef RVC Linux app from v1.3-branch branch :
cd connectedhomeip/
source scripts/activate.sh
cd examples/chef
./chef.py -t linux -d rootnode_roboticvacuumcleaner_1807ff0c49 -b

Regards
Bug prevalence
always
GitHub hash of the SDK that was being used
d83caf7fefeaa91ebc549863552050311abe46ae
Platform
other
Platform Version(s)
Linux
Type
Platform Issue
Anything else?
rootnode_roboticvacuumcleaner_1807ff0c49.log
user@Matter:~/connectedhomeip/examples/chef$ ./chef.py -t linux -d rootnode_roboticvacuumcleaner_1807ff0c49 -b

  ______  __    __   _______  _______
 /      ||  |  |  | |   ____||   ____|
|  ,----'|  |__|  | |  |__   |  |__
|  |     |   __   | |   __|  |   __|
|  `----.|  |  |  | |  |____ |  |
 \______||__|  |__| |_______||__|

Target is set to rootnode_roboticvacuumcleaner_1807ff0c49
Setting up environment...
/home/user/connectedhomeip/examples/chef/../..//scripts/activate.sh: line 116: scripts/setup/gen_pigweed_cipd_json.py: No such file or directory

  WELCOME TO...

         █
         █
     ▄   █   ▄                                █     █
     ▀▀█████▀▀      ▄▀▀▀▄ ▄▀▀▀▄    ▄▀▀▀▀▄█  ▀▀█▀▀▀▀▀█▀▀   ▄▀▀▀▀▄    ▄▀▀
   ▀█▄       ▄█▀   █     █     █  █      █    █     █    █▄▄▄▄▄▄█  █
     ▀█▄   ▄█▀     █     █     █  █      █    █     █    █         █
  ▄██▀▀█   █▀▀██▄  █     █     █   ▀▄▄▄▄▀█    ▀▄▄   ▀▄▄   ▀▄▄▄▄▀   █
 ▀▀    █   █    ▀▀

  ACTIVATOR! This sets your shell environment variables.

Activating environment (setting environment variables):

  Setting environment variables for CIPD package manager...done
  Setting environment variables for Project actions........skipped
  Setting environment variables for Python environment.....done
  Setting environment variables for pw packages............skipped
  Setting environment variables for Host tools.............done

Checking the environment:

20240617 22:06:51 INF Environment passes all checks!

Environment looks good, you are ready to go!

RPC PW disabled
Software Version String: ""
Product ID 0x8000 / Vendor ID 0xFFF1
Building...
x86_64
Done. Made 3640 targets from 290 files in 298ms
ninja: Entering directory `out'
[2/8] c++ obj/ABS_PATH/home/user/connectedhomeip/examples/chef/common/rootnode_roboticvacuumcleaner_1807ff0c49.chef-rvc-mode-delegate.cpp.o
FAILED: obj/ABS_PATH/home/user/connectedhomeip/examples/chef/common/rootnode_roboticvacuumcleaner_1807ff0c49.chef-rvc-mode-delegate.cpp.o
g++ -MMD -MF obj/ABS_PATH/home/user/connectedhomeip/examples/chef/common/rootnode_roboticvacuumcleaner_1807ff0c49.chef-rvc-mode-delegate.cpp.o.d -Wconversion -O0 -g2 -fno-common -ffunction-sections -fdata-sections -fno-exceptions -fno-unwind-tables -fno-asynchronous-unwind-tables -fPIC -Wall -Werror -Wextra -Wshadow -Wunreachable-code -Wvla -Wformat -Wformat-nonliteral -Wformat-security -Wundef -Wno-deprecated-declarations -Wno-missing-field-initializers -Wno-unknown-warning-option -Wno-unused-parameter -Wno-cast-function-type -Wno-psabi -Wno-maybe-uninitialized -fdiagnostics-color -fno-strict-aliasing -fmacro-prefix-map=../third_party/connectedhomeip/= -I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -std=gnu++17 -fno-rtti -Wnon-virtual-dtor -DCHIP_DEVICE_CONFIG_DEVICE_VENDOR_ID=65521 -DCHIP_DEVICE_CONFIG_DEVICE_PRODUCT_ID=32768 -DCONFIG_ENABLE_PW_RPC=0 -DCHIP_DEVICE_CONFIG_DEVICE_PRODUCT_NAME=\"TEST_PRODUCT\" -DCHIP_HAVE_CONFIG_H=1 -DCHIP_ADDRESS_RESOLVE_IMPL_INCLUDE_HEADER=\<lib/address_resolve/AddressResolve_DefaultImpl.h\> -DCHIP_MINMDNS_USE_EPHEMERAL_UNICAST_PORT=1 -DCHIP_MINMDNS_HIGH_VERBOSITY=0 -DCHIP_MINMDNS_DEFAULT_POLICY=1 -DENABLE_CHIP_SHELL -DOPENTHREAD_CONFIG_CLI_TRANSPORT=OT_CLI_TRANSPORT_CONSOLE -DCHIP_SHELL_ENABLE_CMD_SERVER=false -I../include -I/home/user/connectedhomeip/examples/chef/common -I/home/user/connectedhomeip/examples/chef/common/clusters -Igen -Igen/zapgen -I../third_party/connectedhomeip/src/include -I../third_party/connectedhomeip/src -Igen/include -I../third_party/connectedhomeip/examples/chef/linux/include -I../third_party/connectedhomeip/config/standalone -I../third_party/connectedhomeip/zzz_generated/app-common -I../third_party/connectedhomeip/third_party/nlassert/repo/include -I../third_party/connectedhomeip/third_party/nlio/repo/include -I../third_party/connectedhomeip/third_party/inipp/repo/inipp -I../third_party/connectedhomeip/examples/platform/linux -I/home/user/connectedhomeip/examples/chef/shell_common -I/home/user/connectedhomeip/examples/chef/shell_common/include -I../third_party/connectedhomeip/src/lib/shell -c /home/user/connectedhomeip/examples/chef/common/chef-rvc-mode-delegate.cpp -o obj/ABS_PATH/home/user/connectedhomeip/examples/chef/common/rootnode_roboticvacuumcleaner_1807ff0c49.chef-rvc-mode-delegate.cpp.o
/home/user/connectedhomeip/examples/chef/common/chef-rvc-mode-delegate.cpp: In function ‘void emberAfRvcRunModeClusterInitCallback(chip::EndpointId)’:
/home/user/connectedhomeip/examples/chef/common/chef-rvc-mode-delegate.cpp:115:115: error: ‘kOnOff’ is not a member of ‘chip::app::Clusters::RvcRunMode::Feature’
  115 |         new ModeBase::Instance(gRvcRunModeDelegate, 0x1, RvcRunMode::Id, chip::to_underlying(RvcRunMode::Feature::kOnOff));
      |                                                                                ^~~~~~
/home/user/connectedhomeip/examples/chef/common/chef-rvc-mode-delegate.cpp: In function ‘void emberAfRvcCleanModeClusterInitCallback(chip::EndpointId)’:
/home/user/connectedhomeip/examples/chef/common/chef-rvc-mode-delegate.cpp:206:121: error: ‘kOnOff’ is not a member of ‘chip::app::Clusters::RvcCleanMode::Feature’
  206 |         new ModeBase::Instance(gRvcCleanModeDelegate, 0x1, RvcCleanMode::Id, chip::to_underlying(RvcCleanMode::Feature::kOnOff));
      |                                                                                ^~~~~~
At global scope:
cc1plus: note: unrecognized command-line option ‘-Wno-unknown-warning-option’ may have been intended to silence earlier diagnostics
[3/8] c++ obj/ABS_PATH/home/user/connectedhomeip/examples/chef/common/rootnode_roboticvacuumcleaner_1807ff0c49.chef-rvc-operational-state-delegate.cpp.o
FAILED: obj/ABS_PATH/home/user/connectedhomeip/examples/chef/common/rootnode_roboticvacuumcleaner_1807ff0c49.chef-rvc-operational-state-delegate.cpp.o
g++ -MMD -MF obj/ABS_PATH/home/user/connectedhomeip/examples/chef/common/rootnode_roboticvacuumcleaner_1807ff0c49.chef-rvc-operational-state-delegate.cpp.o.d -Wconversion -O0 -g2 -fno-common -ffunction-sections -fdata-sections -fno-exceptions -fno-unwind-tables -fno-asynchronous-unwind-tables -fPIC -Wall -Werror -Wextra -Wshadow -Wunreachable-code -Wvla -Wformat -Wformat-nonliteral -Wformat-security -Wundef -Wno-deprecated-declarations -Wno-missing-field-initializers -Wno-unknown-warning-option -Wno-unused-parameter -Wno-cast-function-type -Wno-psabi -Wno-maybe-uninitialized -fdiagnostics-color -fno-strict-aliasing -fmacro-prefix-map=../third_party/connectedhomeip/= -I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -std=gnu++17 -fno-rtti -Wnon-virtual-dtor -DCHIP_DEVICE_CONFIG_DEVICE_VENDOR_ID=65521 -DCHIP_DEVICE_CONFIG_DEVICE_PRODUCT_ID=32768 -DCONFIG_ENABLE_PW_RPC=0 -DCHIP_DEVICE_CONFIG_DEVICE_PRODUCT_NAME=\"TEST_PRODUCT\" -DCHIP_HAVE_CONFIG_H=1 -DCHIP_ADDRESS_RESOLVE_IMPL_INCLUDE_HEADER=\<lib/address_resolve/AddressResolve_DefaultImpl.h\> -DCHIP_MINMDNS_USE_EPHEMERAL_UNICAST_PORT=1 -DCHIP_MINMDNS_HIGH_VERBOSITY=0 -DCHIP_MINMDNS_DEFAULT_POLICY=1 -DENABLE_CHIP_SHELL -DOPENTHREAD_CONFIG_CLI_TRANSPORT=OT_CLI_TRANSPORT_CONSOLE -DCHIP_SHELL_ENABLE_CMD_SERVER=false -I../include -I/home/user/connectedhomeip/examples/chef/common -I/home/user/connectedhomeip/examples/chef/common/clusters -Igen -Igen/zapgen -I../third_party/connectedhomeip/src/include -I../third_party/connectedhomeip/src -Igen/include -I../third_party/connectedhomeip/examples/chef/linux/include -I../third_party/connectedhomeip/config/standalone -I../third_party/connectedhomeip/zzz_generated/app-common -I../third_party/connectedhomeip/third_party/nlassert/repo/include -I../third_party/connectedhomeip/third_party/nlio/repo/include -I../third_party/connectedhomeip/third_party/inipp/repo/inipp -I../third_party/connectedhomeip/examples/platform/linux -I/home/user/connectedhomeip/examples/chef/shell_common -I/home/user/connectedhomeip/examples/chef/shell_common/include -I../third_party/connectedhomeip/src/lib/shell -c /home/user/connectedhomeip/examples/chef/common/chef-rvc-operational-state-delegate.cpp -o obj/ABS_PATH/home/user/connectedhomeip/examples/chef/common/rootnode_roboticvacuumcleaner_1807ff0c49.chef-rvc-operational-state-delegate.cpp.o
/home/user/connectedhomeip/examples/chef/common/chef-rvc-operational-state-delegate.cpp: In function ‘void emberAfRvcOperationalStateClusterInitCallback(chip::EndpointId)’:
/home/user/connectedhomeip/examples/chef/common/chef-rvc-operational-state-delegate.cpp:164:131: error: no matching function for call to ‘chip::app::Clusters::RvcOperationalState::Instance::Instance(chip::app::Clusters::RvcOperationalState::RvcOperationalStateDelegate*&, chip::EndpointId&)’
  164 |     gRvcOperationalStateInstance        = new RvcOperationalState::Instance(gRvcOperationalStateDelegate, operationalStateEndpoint);
      |                                                                                ^
In file included from /home/user/connectedhomeip/examples/chef/common/chef-rvc-operational-state-delegate.h:22,
                 from /home/user/connectedhomeip/examples/chef/common/chef-rvc-operational-state-delegate.cpp:22:
../third_party/connectedhomeip/src/app/clusters/operational-state-server/operational-state-server.h:384:5: note: candidate: ‘chip::app::Clusters::RvcOperationalState::Instance::Instance(chip::app::Clusters::RvcOperationalState::Delegate*, chip::EndpointId)’
  384 |     Instance(Delegate * aDelegate, EndpointId aEndpointId) :
      |     ^~~~~~~~
../third_party/connectedhomeip/src/app/clusters/operational-state-server/operational-state-server.h:384:25: note:   no known conversion for argument 1 from ‘chip::app::Clusters::RvcOperationalState::RvcOperationalStateDelegate*’ to ‘chip::app::Clusters::RvcOperationalState::Delegate*’
  384 |     Instance(Delegate * aDelegate, EndpointId aEndpointId) :
      |              ~~~~~~~~~~~^~~~~~~~~
At global scope:
cc1plus: note: unrecognized command-line option ‘-Wno-unknown-warning-option’ may have been intended to silence earlier diagnostics
[5/8] c++ obj/rootnode_roboticvacuumcleaner_1807ff0c49.main.cpp.o
ninja: build stopped: subcommand failed.
Traceback (most recent call last):
  File "/home/user/connectedhomeip/examples/chef/./chef.py", line 1011, in <module>
    sys.exit(main())
  File "/home/user/connectedhomeip/examples/chef/./chef.py", line 872, in main
    shell.run_cmd("ninja -C out")
  File "/home/user/connectedhomeip/examples/chef/stateful_shell.py", line 139, in run_cmd
    raise RuntimeError(
RuntimeError: Error. Nonzero return code.
Returncode: 1
Cmd: ninja -C out

This feature value was removed from the spec.

@bzbarsky-apple Shouldn't the code be changed accordingly when the specialisation evolves?
Moreover, why were there any changes in the v1.3 branch when the specifications are now public?

Shouldn't the code be changed accordingly when the specialisation evolves?

Yes.  But it wasn't in this case, which is why you are hitting this problem.

Moreover, why were there any changes in the v1.3 branch when the specifications are now public?

That's a question for the RVC people and @robszewczyk

This now works with the latest commit:
$ ./examples/chef/chef.py -t linux -d rootnode_roboticvacuumcleaner_1807ff0c49 -b

  ______  __    __   _______  _______
 /      ||  |  |  | |   ____||   ____|
|  ,----'|  |__|  | |  |__   |  |__
|  |     |   __   | |   __|  |   __|
|  `----.|  |  |  | |  |____ |  |
 \______||__|  |__| |_______||__|

Target is set to rootnode_roboticvacuumcleaner_1807ff0c49
Setting up environment...

  WELCOME TO...

         █
         █
     ▄   █   ▄                                █     █
     ▀▀█████▀▀      ▄▀▀▀▄ ▄▀▀▀▄    ▄▀▀▀▀▄█  ▀▀█▀▀▀▀▀█▀▀   ▄▀▀▀▀▄    ▄▀▀
   ▀█▄       ▄█▀   █     █     █  █      █    █     █    █▄▄▄▄▄▄█  █
     ▀█▄   ▄█▀     █     █     █  █      █    █     █    █         █
  ▄██▀▀█   █▀▀██▄  █     █     █   ▀▄▄▄▄▀█    ▀▄▄   ▀▄▄   ▀▄▄▄▄▀   █
 ▀▀    █   █    ▀▀

  ACTIVATOR! This sets your shell environment variables.

Activating environment (setting environment variables):

  Setting environment variables for CIPD package manager...done
  Setting environment variables for Project actions........skipped
  Setting environment variables for Python environment.....done
  Setting environment variables for pw packages............skipped
  Setting environment variables for Host tools.............done

Checking the environment:

20240828 07:47:18 INF Environment passes all checks!

Environment looks good, you are ready to go!

RPC PW disabled
Software Version String: ""
Product ID 0x8000 / Vendor ID 0xFFF1
Building...
x86_64
Generating compile_commands took 41ms
Done. Made 3665 targets from 295 files in 1313ms
ninja: Entering directory `out'
[70/70] stamp obj/default.stamp
Done


Staging for v0.2.0 release

Update CI and CD workflows
Synchronize on-premise model (currently the metric of source computing infra analysis), but no models have changed.
Test with CM-Honeybee, CB-Spider, and CB-Tumblebug
Update the execution guide separately  (see https://github.com/cloud-barista/cm-beetle/discussions/73)

/approve


[Question] Why does nuget state that the packages have been witdrawn ?

Note: Version downloads are still active:

I just saw this. No idea what triggered this.
I assume, since I am only co-authoring the package, and since it was originally started by the Coapp org, that some (automated CVE) scanning detected a vulnerability and (automatically) flagged the package accordingly. As I say, just an assumption. I really don't know.
Today I got the notification that Lua 5.4.5 popped up on the official Lua FTP site: https://www.lua.org/ftp/
But it seems to be not fully released, yet: https://www.lua.org/work/
I will now start preparing the repo for the next build and release with:

#4
#2

I plan to fix those within the next week, next two weeks tops, and then I will have a new nuget packet version to release. I will then remove the warning flags.
I will keep this issue open until the new package is online.

Apparently the Coapp org unindexed all their packages: https://www.nuget.org/profiles/coapp
No idea what happened there. ... I plan to continue to maintain the Lua NuGet package on my own.

I did not find any very recent CVEs for Lua. Well, I found a couple, they are either addressed in recent versions, or will be addressed in version 5.4.5 and all in all seem ok-ish (your typical CVEs, nothing world-ending).
This and the fact that all Coapp org packages got unlisted makes me believe that the Coapp org did a final deprecation and house cleaning and (automatically) indiscriminated unlisted and flagged all their packets.
For that reason, I decided to remove the flags for all 5.4.x versions of the nuget package.

https://www.nuget.org/packages/lua/5.4.5


The dependency NUnit3TestAdapter 3.0.10 in project  does not support framework DNXCore,Version=v5.0

Very sorry if this has been addressed previously.
I've seen this post https://github.com/nunit/nunit-vs-adapter/issues/102 which does not appear to resolve this issue.
I am getting this error after installing NUnit3TestAdapter
The dependency NUnit3TestAdapter 3.0.10 in project Blog.IntegrationTests does not support framework DNXCore,Version=v5.0
Project.json :
{
"version": "1.0.0-",
"description": "Blog.IntegrationTests Class Library",
"authors": [ "Sam" ],
"tags": [ "" ],
"projectUrl": "",
"licenseUrl": "",
"frameworks": {
"net451": {
"dependencies": {
}
},
"dnxcore50": {
"dependencies": {
"Microsoft.CSharp": "4.0.1-beta-23516",
"System.Collections": "4.0.11-beta-23516",
"System.Linq": "4.0.1-beta-23516",
"System.Runtime": "4.0.21-beta-23516",
"System.Threading": "4.0.11-beta-23516"
}
}
},
"dependencies": {
"Autofac": "4.0.0-rc1-177",
"Blog.Core": "1.0.0-",
"Blog.Domain": "1.0.0-",
"Blog.Model": "1.0.0-",
"Blog.Services": "1.0.0-*",
"NUnit": "3.2.1",
"NUnit3TestAdapter":
"3.0.10"
}
}

The adapter does not yet support dnxcore. :-(
Issue #102 deals with a different issue - using the 2.0 adapter to run 3.x tests.

I am going to close this issue as a duplicate. Microsoft has a new adapter interface for .NET Core. It is being implemented in a separate repository. https://github.com/nunit/dotnet-test-nunit


how to handle chunks with missing postage stamp

viktor's suggestion - all chunks must have postage stamps

https://github.com/ethersphere/bee/issues/1440 has all research notes and architecture proposals. If you find your answer there, could you close this with the conclusion?


Worse than particles.js

Problem
According to README

tsParticles library is fully compatible with the particles.js configuration

However, today I migrated old project from particles.js to tsParticles and results are very disappointing:

Animation is not smooth anymore.
Particles are moving much faster.

I tried playing with configuration but it seems to be generic tsParticles issue.
Reproduction
I prepared CodePen examples, please open them side by side to see difference in results:

particles.js - nice and smooth!
tsParticles - kind of laggy :cry:

Version
1.39.0
Which library are you using?
Vanilla (tsparticles)
Code of Conduct

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

I tested both CodePen samples you provided and both are running 60 fps on my PC.
Anyway, the speed on pjs had a mistake in the formula since particles moving up/down/left/right were faster than other particles moving to other directions.
The fix needed a choice, I have chosen the easier to fix for everyone, just half the movement speed and it should looks the same (or at least really similar).
Now compare these codepens:
particles.js broken 🙄
tsParticles working
One is broken, one isn't. And I just changed move: true to move: false. There are a lot of unsolved bugs in the original library, lot of them here were solved.
I've released in the library files also a slim version, without some features (every feature can worsen the performance)
tsParticles slim
Let me know if this is better for your needs.
I'm working on the version 2 with more modularity so everyone can choose only the feature they need.

I've checked the mouse interaction, I think it's something related to FPS limiter. This is useful to avoid higher frame rates to change the general speed, pjs in higher frame rates is faster than in slower ones. I'll do some tests about it changing the factor used to adjust these values.

Finally I found the lag issue, and it’s solved in the new 1.39.3 version, released few minutes ago

After upgrading tsParticles from 1.39.0 to 1.39.3 animation is smooth :+1:
Btw. window resize is handled better by particles.js, because nothing gets scaled.


module std.array import 'indexOf' not found

DIni tries to import unexistent symbol indexOf:

../../home/maaaks/.dub/packages/dini-1.0.0/src/dini.d(12): Error: module std.array import 'indexOf' not found, did you mean 'alias IndexOf'?

However, if I remove the indexOf from that line, everything compiles successfully. I think you should remove it from source (and maybe check for other old unused imports).

@robik, can you tag Master with v1.0.1 so that dub can pull this fix down?


"Fuzzy" toggle

There's another similar plugin that lets you toggle 'fuzzy' which is useful when for example you have the regular blowpipe and the new orn kit one from leagues, because currently when you attach the orn kit it removes it from the layout. Is there any way we can toggle fuzzy on an item, or is there an alternative way of doing what I'm doing without having to re-add the blowpipe to all my layouts?

If you mean inventory setups, that one probably doesn't recognize blazing blowpipe as fuzzy. It most likely uses runelite's variation items system, which has probably not been updated to include the blazing blowpipe as a blowpipe.

So another example is that I have a different slayer helm but my layouts that I made with my old one are greyed out like this:

So I basically want it so that no matter what I do to my slayer helm it will still show up in all the layouts

did you variation tag the slayer helmet? (shift-drag it on the tag tab)

I did not know that was a thing, that helps, is there any way to retroactively tag items like that or does it need to be done on the creation of the tab?

Just shift drag it onto the tab. it will add all the variations. you don't have to do it at creation. But it would be nice if e.g. autolayout automatically did it for some items. It just can't be done for all variation items, I would have to make a manual list of which items need to be handled like this.


fix(test): check aws-exports on sandbox pull

Update sandbox pull e2e test to validate aws-exports.js, models/index.js and models/schema.js files.

Codecov Report

Merging #9959 (5fc54e1) into master (2bd4172) will increase coverage by 0.10%.
The diff coverage is 89.28%.

@@            Coverage Diff             @@
##           master    #9959      +/-   ##
==========================================
+ Coverage   53.00%   53.11%   +0.10%
==========================================
  Files         830      830
  Lines       46012    46002      -10
  Branches     9826     9829       +3
==========================================
+ Hits        24390    24433      +43
+ Misses      19604    19557      -47
+ Partials     2018     2012       -6

Impacted Files
Coverage Δ

...-graphql-auth-transformer/src/utils/definitions.ts
100.00% <ø> (ø)

...amplify-graphql-index-transformer/src/resolvers.ts
99.59% <ø> (ø)

...earchable-transformer/src/generate-resolver-vtl.ts
90.47% <ø> (ø)

...plify-graphql-relational-transformer/src/schema.ts
94.35% <50.00%> (-0.57%)
:arrow_down:

...-auth-transformer/src/resolvers/mutation.update.ts
88.29% <88.88%> (+0.06%)
:arrow_up:

...ator/src/server/subscription/mqtt-server/server.ts
44.14% <100.00%> (ø)

...l-auth-transformer/src/graphql-auth-transformer.ts
93.33% <100.00%> (+3.70%)
:arrow_up:

...plify-graphql-auth-transformer/src/utils/schema.ts
86.56% <100.00%> (+11.91%)
:arrow_up:

...index-transformer/src/graphql-index-transformer.ts
100.00% <100.00%> (ø)

...transformer/src/graphql-primary-key-transformer.ts
98.61% <100.00%> (ø)

... and 5 more

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


Banner/Label/Watermark to denote Staging not Live site

Could we add something distinctive to staging so it's clear which version of the site we're on. It's getting confusing with the regression test to ensure we're using the correct version of the site - they're all but identical except the URL and unpublished pages.

We have added a label to show when you aren't viewing a production version of the site.

Do you know when this'll appear on Staging?

I think we'll be pushing to staging later today :-)


How to rollback a block placed ?

Hello, i'm on the v2.0.6 of Prism and i don't know if it's possible to rollback placed blocks ? Because, actually when i do something like: /pr rb p:ErkoZ r:we a:place , it does just nothing but in reality it replace placed blocks by the same blocks but i want to replace it with the previous block..

Can you provide a more specific example? Also, you may want to look at /pr rs


Various minor performance enhancements

Breaks app/etc/env.php creation into distinct recipe
Removes composer-prep recipe from pre-deploy
Adjusts NGINX notification (restart/delayed instead of reload/immediately)
Stops crond and kills bin/magento cron jobs before setting deploy mode and running compilation/upgrade commands
Simplifies overall structure of magento-install
-- Moves individual resources out of confusing "notifies" structure
-- Moves app/etc/env.php file check to head of recipe, saving time
-- Provides better scrollback for debugging
-- Speeds up overall installation process

Tested and verified in dependent project


.wsf Files Not Supported

Describe the bug
It would be awesome if this extension supported .wsf files - specifically .wsf files with embedded and linked VBScript.
Code
N/A
To Reproduce
Open a .wsf file -> observe lack of syntax highlighting in VSCode
Expected behavior
VSCode operates similarly to the way it does with .vbs files
Screenshots
Omitted
Desktop (please complete the following information):

OS: Win10 Enterprise 20H2 x64
VS Code Version: 1.52.1
VBS-VSCode Version 1.2.0

To implement vbs as an embedded language the following guide provides samples: https://code.visualstudio.com/api/language-extensions/embedded-languages.
To cite that guide

Generally, language features that work across language region boundaries are harder to implement.

and I couldn't agree more. It would require to set a wsf file as xml and hook/hack into the xml language server. I have no time to spend so much effort in such a complex task.
To be consistent, same thing must be done with html.
If someone can, feel free to do a pull request.
Some syntax highlighting and autocompletion will even work if you set the language to vbs and the Run command will work also. But I would expect some strange side effects.
If you really need it, you maybe could create a simple include function (first and unchecked google result https://blog.ctglobalservices.com/scripting-development/jgs/include-other-files-in-vbscript/) for a skeleton wsf file and outsource your code in a normal vbs file.


feat(js_executor): move js execution logic to dylib and load it conditionally if defined

Summary:
Move js execution logic from cargo feature to separate dylib that is built on its own.
This is initial implementation that requires heavy polishing but already shows how that could look.
In this implementation:

removed unsafe-js feature completely
moved the execution of js and mini-v8 dependency to separate workspace crate
add configuration for js plugin to schema
load the dylib for js execution with libloading if it is specified in schema
pass script from schema to dylib for execution

The main struggle I've faced so far it's how to reliable pass data with ffi between cli and dylib as there a lot of nuances how it works for different compilations. I've spent some time fighting with it. And while some issues could be resolved with not using extern 😔 and using the same memory allocator in cli and dylib I still face segfaults when using more generic version of the plugin that accepts blueprint and changes it (mostly with Arc internals). So, for now I decided to implement simper approach with just specific interface only for specific js plugin that accepts and returns string. That approach is at least work in simple tests.
what else should be done:

fix TODOs and remove debugging stuff
add CI build for dylib
polish code and remove unnecessary cloning and unwraps
rework resolving plugin relative to the config

Issue Reference(s):
Fixes #556
Build & Testing:

[ ] I ran cargo test successfully.
[ ] I have run ./lint.sh --mode=fix to fix all linting issues raised by ./lint.sh --mode=check.

Checklist:

[ ] I have added relevant unit & integration tests.
[ ] I have updated the documentation accordingly (if applicable).
[ ] I have performed a self-review of my own code.

added benchmarks for the expression to see how much time js executes in comparison with const value.
Also, added benchmarks to compare running the code from dylib built in release and debug mode, and in comparison with built-in mini-v8 without dylib involved

Constdylib releasebuiltin mini-v8dylib debug

literal/Literal(Number(56))
time:   [60.276 ns 62.662 ns 65.550 ns]
literal/Literal(String("literal"))
time:   [70.881 ns 72.136 ns 74.184 ns]

unsafe-js/Unsafe(JS { input: Literal(Null), script: "57" })
time:   [732.81 µs 746.34 µs 761.83 µs]
unsafe-js/Unsafe(JS { input: Literal(Null), script: "'unsafe_js'" })
time:   [724.22 µs 735.26 µs 749.06 µs]
unsafe-js/Unsafe(JS { input: Literal(Null), script: "Array(111).fill(0).reduce((acc, el, i) => acc +...
time:   [741.51 µs 753.38 µs 767.74 µs]
unsafe-js/Unsafe(JS { input: Literal(String("{a: 23, b: 58}")), script: "ctx.a + ctx.b" })
time:   [734.69 µs 751.62 µs 771.97 µs]

unsafe-js-old/Unsafe(JSOld { input: Literal(Null), script: "59" })
time:   [728.25 µs 741.14 µs 757.36 µs]
unsafe-js-old/Unsafe(JSOld { input: Literal(Null), script: "'js_old'" })
time:   [729.72 µs 737.26 µs 745.84 µs]
unsafe-js-old/Unsafe(JSOld { input: Literal(Null), script: "Array(111).fill(0).reduce((acc, el, i) =...
time:   [758.85 µs 778.91 µs 802.64 µs]
unsafe-js-old/Unsafe(JSOld { input: Literal(String("{a: 23, b: 58}")), script: "ctx.a + ctx.b" })
time:   [736.29 µs 752.34 µs 771.84 µs]

unsafe-js-debug/Unsafe(JS { input: Literal(Null), script: "58" })
time:   [771.57 µs 791.33 µs 815.32 µs]
unsafe-js-debug/Unsafe(JS { input: Literal(Null), script: "'js_debug'" })
time:   [761.23 µs 770.96 µs 782.26 µs]
unsafe-js-debug/Unsafe(JS { input: Literal(Null), script: "Array(111).fill(0).reduce((acc, el, i) =>...
time:   [780.38 µs 796.28 µs 816.64 µs]
unsafe-js-debug/Unsafe(JS { input: Literal(String("{a: 23, b: 58}")), script: "ctx.a + ctx.b" })
time:   [761.40 µs 770.32 µs 781.57 µs]

so the difference is huge, it's kind of expected. But I do see some ways that could be improved and thanks to benchmarks I'll see the difference

Also, benchmarks with wrk with comparison between using @const and @js. For js I just used simple string as the value of script to make comparison more fair.
const_value:
Running 30s test @ http://localhost:8000/graphql
 1 threads and 100 connections
 Thread Stats   Avg      Stdev     Max   +/- Stdev
   Latency     1.76ms    0.89ms  31.70ms   74.06%
   Req/Sec    56.17k     5.13k   66.21k    78.67%
 1681863 requests in 32.99s, 221.35MB read
 Socket errors: connect 0, read 0, write 0, timeout 100
Requests/sec:  50978.03
Transfer/sec:      6.71MB

js_value:
Running 30s test @ http://localhost:8000/graphql
 1 threads and 100 connections
 Thread Stats   Avg      Stdev     Max   +/- Stdev
   Latency    75.65ms   37.39ms 323.53ms   67.61%
   Req/Sec     1.33k   109.61     1.49k    84.72%
 39868 requests in 33.01s, 5.13MB read
 Socket errors: connect 0, read 0, write 0, timeout 100
Requests/sec:   1207.75
Transfer/sec:    159.22KB

Difference is also huge. For now I'm trying to optimize it by at least storing parsed function definition between calls and not evaluate it on every request. But I'm struggling with the v8 definition that can't be shared between threads and therefore used in async tokio runtime.

managed to improve performance significantly by saving evaled js-function on init for later call in resolver. But this involved pretty ugly code to bypass issues that v8 is !Send and !Sync.
Running 30s test @ http://localhost:8000/graphql
  1 threads and 100 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     2.16ms    0.85ms  29.84ms   76.02%
    Req/Sec    45.56k     3.89k   50.35k    84.67%
  1363286 requests in 32.98s, 175.52MB read
  Socket errors: connect 0, read 0, write 0, timeout 100
Requests/sec:  41335.31
Transfer/sec:      5.32MB

so, now working on the way to improve this and fix usage for criterion benchmarks to see more detailed comparison

criterion benchmarks results after preserving v8 parts between calls:
literal/Literal(Number(56))
                        time:   [65.874 ns 67.309 ns 69.078 ns]
                        change: [+7.4435% +10.605% +13.896%] (p = 0.00 < 0.05)
                        Performance has regressed.
Found 13 outliers among 100 measurements (13.00%)
  13 (13.00%) high severe

literal/Literal(String("literal"))
                        time:   [77.726 ns 80.866 ns 85.606 ns]
                        change: [+6.5555% +10.336% +14.358%] (p = 0.00 < 0.05)
                        Performance has regressed.
Found 16 outliers among 100 measurements (16.00%)
  2 (2.00%) high mild
  14 (14.00%) high severe

unsafe-js/Unsafe(JS { input: Literal(Null), script: "57" })
                        time:   [26.213 µs 26.399 µs 26.586 µs]
                        change: [-96.578% -96.491% -96.412%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 2 outliers among 100 measurements (2.00%)
  1 (1.00%) high mild
  1 (1.00%) high severe

unsafe-js/Unsafe(JS { input: Literal(Null), script: "'unsafe_js'" })
                        time:   [26.634 µs 26.864 µs 27.092 µs]
                        change: [-96.327% -96.268% -96.215%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 7 outliers among 100 measurements (7.00%)
  7 (7.00%) high mild

Benchmarking unsafe-js/Unsafe(JS { input: Literal(Null), script: "Array(111).fill(0).reduce((acc, el, i) => acc +...: Collecting 100 samples in e
unsafe-js/Unsafe(JS { input: Literal(Null), script: "Array(111).fill(0).reduce((acc, el, i) => acc +...
                        time:   [26.741 µs 26.936 µs 27.122 µs]
                        change: [-96.354% -96.317% -96.278%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 3 outliers among 100 measurements (3.00%)
  1 (1.00%) high mild
  2 (2.00%) high severe

Benchmarking unsafe-js/Unsafe(JS { input: Literal(String("{a: 23, b: 58}")), script: "ctx.a + ctx.b" }): Collecting 100 samples in estimated 5.05
unsafe-js/Unsafe(JS { input: Literal(String("{a: 23, b: 58}")), script: "ctx.a + ctx.b" })
                        time:   [26.506 µs 26.704 µs 26.886 µs]
                        change: [-96.406% -96.349% -96.299%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 2 outliers among 100 measurements (2.00%)
  2 (2.00%) high mild

20-30x times faster so far


[RFR] Custom menu

[x] Add a Menu model
[x] Add a compatibility layer between Entity.menuView() and  Menu
[x] Change all inner links to put the entity name first (e.f. '#/list/posts/' becomes '#/posts/list') (eases url recognition)
[x] Optimize perf
[x] write doc

Switching to RFR

@fzaninotto I'm certainly not the most qualified reviewer on es6 part, but for me everything is good. Especially as it is tested ... About that, all tests pass on local, but failed on travis. Is this a known issue ?

Yes it is a known problem. e2e tests fail for no apparent reason, and it's a pain to debug. That's also why I didn't add more e2e tests for this PR.
If you're satisfied with the code, I'll let you merge, and I'll push an update to the built files to master right after.


More tombstone keys in the memtable of rocksdb and the seek duration may increase

Feature Request
Is your feature request related to a problem? Please describe:
When there are more tombstone keys in the memtable of rocksdb, the seek duration may increase. Currently, there is no effective monitoring metrics in Grafana to locate this problem.
Describe the feature you'd like:

It is recommended to add some grafana metric to help us accurately locate this problem and detect this abnormality in TiKV, and actively flush to reduce the impact on rocksdb-kv seek duration.
Describe alternatives you've considered:

Manual compaction.

/label sig/engine

Duplicate with https://github.com/tikv/tikv/issues/8486


⚠ Bofrost.be has degraded performance

In 02e4a6c, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1122 ms

Resolved: Bofrost.be performance has improved in 440d4e4.


Autofocus password field in login flow

#1987
Password field autofocus is implemented.

Coverage: 94.288% (+0.01%) from 94.277% when pulling d8a5536c58d9ac626a3c9bb616559ebd3bc2c2cb on jobayer12:issue-1987 into a3466ee4abd6be8586682cd59ce52cc6eb65ed79 on medplum:main.


Fix #1119: virtualConsole.sendTo should send jsdomErrors to console.error by default

I also threw in a commit that classes up virtual-console.js.

Hmm. I am not able to reproduce the on-error.js Travis failure.
Worse, this PR has revealed an interesting bug that the w3c tests seem to trigger, where we try to fire events on window before it's created (i.e. before it has a _document property). These seem to originate from the resource-loading subsystem.
If anyone wants to help debug I'd appreciate it.

OK, if I comment out window.close() in w3ctest.js, it goes away. So we should stop trying to fire events after the window closes. But, even if we do stop such things, it's unclear why we're trying to fire events after window closes.

OK figured out the w3ctest.js. window.close() actually fires a load event, but the window is all destroyed-ey by that time. So it's expected, and the fix was easy.
Still not sure why the on-error failure isn't showing for me. Can someone with non-Windows test?

Oh it's io.js 3 vs. 2, good times.


Source creation issues: With or without Python version

Currently, the source of a fractal task can be created with a source of "pip_remote:fractal_tasks_core:0.10.1:fractal-tasks::create_ome-zarr_structure", as well as the classical "pip_remote:fractal_tasks_core:0.10.1:fractal-tasks:py3.9:create_ome-zarr_structure". If the user doesn't specify the Python version, then that Python entry is just left empty in the source (i.e. just :: instead of :py3.9:), leading to an ambiguous task source.
Should the Python version be required? Or should fractal server than figure out what Python version is used and put this into the source?

In principle there may be a use case for the "missing" python version in task source, namely when a task is supposed to be compatible with multiple python versions and the user who collects the package wants to keep the task more portable. If we force this part of the source to be always set to something, then we incur the same issue as in https://github.com/fractal-analytics-platform/fractal-web/issues/285 (that is, if a new instance installs tasks for a different python version, all current workflows need to be updated).

That said, this is still a minor usability issue. I'm OK with always filling the python-version part of the source, and I would simply use the python version that is anyway being used for tasks.

For the moment I'd refrain from making the python version required for task collection, give #659 and the other issues in #697. Once we take broader decisions on the future of task collection, it will be easier to decide whether python-version should be required (IMO it will have to be required, and we will have to be more strict, but at the moment we are simply looking for an existing pythonX.Y executable - which we know is not the most robust choice).

Loosely-related quotes from https://github.com/fractal-analytics-platform/fractal-server/issues/702#issue-1716803032:

Re: portability
As compared to previous versions, we are making the source syntax more rich. Using fractal-tasks-core as an example, this means that the cellpose_segmentation task of 0.9.4 on a given Fractal instance won't automatically correspond to the one on another instance, if some fields (e.g. the Python version) differ. This introduces some friction when importing a workflow into a different Fractal instance, because if the two instance admins installed fractal-tasks-core with different Python version there will need to be some manual editing of the to-be-imported workflow JSON file (updating all Python versions in the task sources).
This cost cannot be easily avoided, if we want to be able to control the Python version of tasks. And this is something we most likely will have to do, given that (e.g.) cellpose still comes with an official "We recommend python 3.8" advice.

Re: why a string and not many db columns?
Question: Why don't we split the source string into several attributes? Answer: That would be too strict, for instance if we want to add a single "common" task that doesn't correspond to a Python package (e.g. a bash task that calls the bioconvert CLI). By keeping everything in the source attribute, we keep the freedom of doing so, without breaking anything on the fractal-server side. The discussion on how to handle it will then happen client-side.
In other words: fractal-server should not rely on the actual source structure, but it should only write it correctly for automatically-collected Python tasks. The different clients will then consume these sources to offer additional features.

This is made obsolete by https://github.com/fractal-analytics-platform/fractal-server/issues/1575, since task collection will now always have a Python version attached to it (context: this is because we want to explicitly define which Python interpreter will be used for creating venvs).


Update vue-loader to 13.0.5.

js-beautify broke and vue-loader switched to prettier. #1194
See:
https://github.com/beautify-web/js-beautify/issues/1247
https://twitter.com/vuejs/status/909785891941617664

Did you try checking if this will break anything else? Going from v12 to v13 might break something thus I did not really want to bump the version earlier.

I have that concern myself too. But I've tested building my vue files on laravel with v13 and it went well. Replace laravel-mix in your package.json to "laravel-mix": "yansern/laravel-mix", and see if yours compile fine?

After updating to Laravel-Mix 1.4.4 I suddenly get this Vue error: vue.common.js:478 [Vue warn]: Failed to mount component: template or render function not defined. and none of my single-file components work anymore. I would assume it's caused by the vue-loader change. Reverting to 1.4.3 fixes my issue and Vue works fine. Any idea what's wrong?

@ThomHurks If you use require('foo.vue') you'll need to change it to require('foo.vue').default. See: https://github.com/vuejs/vue-loader/releases/tag/v13.0.0
I just realized I use import instead of require when loading vue files that's why I wasn't getting any errors.
@JeffreyWay I think I need to submit another pull request, adding esModule: false on the vue-loader options on the the webpack-rules.js file for backwards compatibility. See: https://github.com/vuejs/vue-loader/blob/master/docs/en/options.md#esmodule

Ah, I'm using import for Vue and Vue plugins, but I'm using require for my own components. I'll try switching to using import or require().default for those. Probably a good idea to put this in the release notes :)

Ah yeah this is a breaking change. Need to fix that. @yansern can you submit that second PR?

@JeffreyWay Done. Hope this works!


Update CONTRIBUTING.md

Document moved to community repository.
Pull request template

Type of changes

[ ] CI
[ ] Bugfix
[ ] Feature
[ ] Generic maintenance tasks
[x] Documentation content changes
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no URL changes)
[ ] Improving performance of the project (not introducing new features)
[ ] Other (please describe):

Issue Number: N/A
What is the current behavior?

What is the new behavior?

Does this introduce a breaking change?

[ ] Yes
[x] No

For this case, there is another plan made. Closing.


Update Typing.jsx

Related Issue
Fixed Issue #24.
Proposed Changes
Updated Typing.jsx to remove the bug.

there are some conflicts can you resolve it before I merge it @nishant-giri

Yeah, sure. I'm resolving that.

@alceil, I've resolved the conflicts.


Remove any_param field from FunctionSpec

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run mvn clean verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

retest this please

R: @kennknowles

LGTM if you get it green

retest this please

retest this please

+R: @robertwb
Also removed from python.

LGTM, pending green tests.

retest this please

retest this please

retest this please

retest this please

retest this please

Run Precommit pipeline

Run Precommit Pipeline All

Run Precommit Pipeline All

Run Precommit Pipeline All

Run Precommit Pipeline All

Retest this please

retest this please

retest this please

Coverage increased (+0.03%) to 69.572% when pulling f0284554e6ce0b95c3652c2f2e6f256eef0695f2 on tgroh:remove_any_param into cfbdb6115eca25fd3f512355aaf4e9be80f5ed94 on apache:master.


Fixed "endless" queries

Fixes https://github.com/loupe-php/loupe/issues/134.
I have accidentally pushed this already in https://github.com/loupe-php/loupe/pull/136/files#diff-60e811f23f79f3d9ec47e6aa6599834bd758f7063de8dd1be2b9ae821d2615ea but here's the finalized version.
Tested using php bin/bench/search.php -q="this is taking so long".
Previously: 31283.11
Now: 1235.46
Search results are still "relevant" but again. What does "relevant" even mean with such a query 😊

Does this limit the total number of considered results to 1000? Or is that per term?
How does this behave if I have a total of 1.500 documents in the index and all matches are kind of bad (stemmed, low-ranking attribute, etc.) but the perfect match is the 1200th document with a perfect title match?

Would need to be tested but I guess you just won't find that document then.

If that limitation is per term, I think that's a reasonable compromise to make.
If the limit is for the whole result set, that might lead to some rather suboptimal search results in the long term, given that multiple terms are conceptually joined by OR. If a query starts with multiple generic terms and ends with a very specific term (The Long Day of Rübenthaler), it would probably fetch 1000 documents for the generic terms first, and then ignore the one result for the specific term since it's over the limit already. Not sure I correctly understood the logic here, though 🤠

Found out that it's not a general bug with the LIMIT query but this PR in its current state indeed causes issues. I will add a test case.

However, I don't really know if there's a different way to fix this issue. The query matches too many documents = you cannot expect it to find the most relevant document because in order to do that, it would have to search all of them which is exactly what you want to prevent. I think the same happens in MeiliSearch: https://www.meilisearch.com/docs/learn/resources/known_limitations#maximum-number-of-results-per-search

Again, you cannot prevent that from happening. What is relevant and what's not is determined on the entire result set. If you strip parts of it, then it's always possible that the most relevant gets stripped. You can try to improve the probability on some wild guesses like "longer terms are probably more distinct" etc. or we could again count the term frequency and order somehow by that but that's just a whole different story. I think we should first have a security guard which prevents Loupe from easily getting crashed which is what this PR does. Then we can still try to come up with ways to optimize this "security guard".

See https://github.com/loupe-php/loupe/pull/140 for a test case if you want to give it a try somehow.

Sounds like a good strategy! Lock things down to avoid the security issue and optimize later. I'll see if I find a minute to look into the test draft :) But the optimization shouldn't be a blocker here.


Pagination Error: Detected invalid url

I am getting:

Pagination Error: Detected invalid url "/feeds" for "feeds.html"
Expected "/" or "/index.html"

build log:

    Pagination: Starting

    Pagination: Page: feeds.html
    Pagination: --------------------------------------------------------------------------------
    Pagination:   Active configuration
    Pagination:     Enabled             : true
    Pagination:     Items per page      : 10
    Pagination:     Permalink           : /:num/
    Pagination:     Title               : :title | :num of :max
    Pagination:     Limit               : 0
    Pagination:     Sort by             : date
    Pagination:     Sort reverse        : true
    Pagination:   Active Filters
    Pagination:     Collection          : posts
    Pagination:     Offset              : 0
    Pagination:     Category            : [Not set]
    Pagination:     Tag                 : [Not set]
    Pagination:     Locale              : [Not set]
    Pagination:   Filtering by Category :  17 => 17
    Pagination:   Filtering by Tag      :  17 => 17
    Pagination:   Filtering by Locale   :  17 => 17
    Pagination: Rolling through the date fields for all documents

Pagination Error: Detected invalid url "/feeds" for "feeds.html"
Expected "/" or "/index.html"

`---
layout: page
title: Feeds
style: notebook
date: 2018-07-23
pagination:
enabled: true

{{page.title}}
`

Is there a solution for this error? I ran into the same problem and dont know how to solve it.

Is there a solution for this error?

Downgrade to using v2.0.0
gem "jekyll-paginate-v2", "2.0.0"

Try removing the permalink line from your config.yml file, and see if it works

It seems this is now incapable of handling tags with . in the name.  e.g.  vb.net
  Pagination Error: Detected invalid url "blog/tag/vb.net/index.html" for "blog/tag/vb.net/index.html"                     Expected "blog/tag/vb.net/" or "blog/tag/vb.net/index.net"
It used to just work - the URL on my live site is https://damieng.com/blog/tag/vb.net/

I had a same issue in the following file:
layout: custom
title: News
permalink: /news
pagination:
enabled: true
(just for reference, the pagination section in my _comfig.yml is:
pagination:
  enabled: true
  title: ':title - page :num of :max'
  per_page: 12
  permalink: '/page/:num/'
  limit: 0
  sort_field: 'date'
  sort_reverse: true
  trail:
    before: 2
    after: 2

To fix the issue, I had to add trailing slash in permalink of markdown file
(permalink: /news => permalink: /news/), now it works!

Do note that this validation was introduced in the v2.1.0 of this plugin which has been yanked from the Rubygems database (this feature being the major reason for the removal).
Therefore, if one's site doesn't depend on the "fixes" included in v2.1.0, I recommend that they edit their Gemfile to just use the v2.0.0 version:
gem 'jekyll-paginate-v2', '2.0.0'

Could you please upgrade to https://rubygems.org/gems/jekyll-paginate-v2/versions/3.0.0 and test again for me?


net/tayga: bugfixes for TUN interface and Tayga IPv6 addresses

@mimugmail, I found and fixed some minor bugs.
It now works without any manual configuration on the console. And it keeps working after a reboot.
(I have not done any serious stability testing yet. It would be great if someone else could test this, too.)

Merged, thanks! ❤


Model and mapping for dml statements

We need to create model and mapping for statements

[ ] insert
[ ] delete
[ ] update

If you meet some difficult cases, you can omit them for a while.

https://github.com/dbeaver/pro/wiki/Plans-on-ANTLR-based-parser-and-editor-services

After discussion we're not satisfied of the mapping approach using java's xpath in the hand-written annotations. So, this particular task is delayed.


test(transfer): last chain in forwarding packet is ICS20 v1

Description
closes: #6557
Can also potentially close (accidentally) #6577 if we agree on what I did.
Sorry for the number of files touched. I just figured it was unnecessary to have the TransferChannelOptions as a method on the suite after it doesn't use it anymore. Can revert that part if you guys prefer to keep it.

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).
[ ] 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.
[ ] 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)
[ ] Re-reviewed Files changed in the GitHub PR explorer.
[ ] Review SonarCloud Report in the comment section below once CI passes.

Putting this in draft while waiting for #6629


RFC

Not necessarily v4 but this is what I think the NW.js "ecosystem" needs. Not sure if nw-builder should have all this functionality. If it makes for sense for another repo to focus on it, I'd be happy to remove it.
API
nwbuild install --version=0.67.0 --flavour=sdk

Install one or more NW.js binaries.
nwbuild uninstall --version=0.67.0 --flavour=normal

Uninstall one or more NW.js binaries.
nwbuild initialize --docker=ubuntu22 --template=vanilla

Build your NW.js application in a Docker container to prevent weird cross platform issues. Optionally define a starter template if you're starting your Node project from scratch. If --template flag is defined then this creates the nw.develop.json and nw.package.json files.
nwbuild develop --manifestFile=./nw.develop.json

nwbuild automatically looks for the nw.develop.json manifest which defines options which are more suited for development.
nwbuild package --manifestFile=./nw.package.json --zip=tar

nwbuild automatically looks for the nw.package.json manifest which defines options which are more suited for packaging.
nwbuild installer --extention=dmg

An installer for the packaged applications.

IMO, all of this would be nice but none of it should be part of nw-builder. Instead, start a project like the Vue CLI tools. nwcli or something, which has this functionality.

I agree with @sysrage, separating CLI and docker stuff makes sense to me. It lets their repo(s) be more scoped to the specific problem it is trying to solve. And it keeps the nw-builder more focused and allows it to evolve to handle more edge cases needed by the community.
nw-builder should be focused on running locally on the current platform. Then if you want to set up GitHub Actions to run against Win, Lin, and OSX, and do 1 native build on each, that can work. Or if you want to just run your code on a single box using docker for the native builds, you could do that instead. But inside the docker container it would still just be using nw-builder normally.
But in general I like the idea of having some tooling that simplifies the process of using Docker and building each platform in their native environment, with their correct Node versions. That solves a lot of problems.

I knew what I wanted to build but didn't know if I should add it to a pre-existing tool like nw-builder or build one from scratch.  This clears things up, thanks!

Working on it here:
https://github.com/ayushmxn/nwbuild

Working on it here: https://github.com/ayushmxn/nwbuild

Awesome! Might I suggest a name change, since many/most of the features aren't actually related to a "build" process? 😉

Sure! I made this a while ago and wasn't sure of it's purpose.

Motivation for this was due to https://github.com/electron-userland/electron-builder and https://github.com/electron-userland/electron-forge. Essentially an all in one build tool.


TypeScript: Remove property message from extended Error class (does not work with "noImplicitOverrides")

The message property should be removed from the extended Error class because it's already defined in the parent. When this property exists and the typescript compiler option noImplicitOverrides is set it causes a compilation error when used with TypeScript 4.3+. Since the property already exists on the parent the removal should not affect older TypeScript versions.
I can create a PR for this if you want.
https://github.com/RicoSuter/NSwag/blob/f28fe417ef917f2c2b6a55993b1154f36d359850/src/NSwag.CodeGeneration.TypeScript/Templates/File.liquid#L129
Another alternative would be to be able to set the Version to 4.3 and generate override message: string.

Hi @stefan-schweiger and @RicoSuter , do you perhaps have an update on this?


Mean absolute error?

I noticed there's an objective for root mean square error but not for mean absolute error? I'm happy to put together a PR for this if you think this would be useful.
Actually what I think would be even more useful is to generalize this to quantile loss – happy to include that too. My use case is I want to predict a 90% interval. This could be done by training two separate predictors, quantile loss for 0.05 and 0.95.
Let me know if you think this is a bad idea and I won't attempt it :)

This will definitely be useful. In [scikit-learn's implementation] (http://scikit-learn.org/stable/modules/generated/sklearn.ensemble.GradientBoostingRegressor.html), it has squared, absolute, huber and quantile loss for regression tasks. It would be nice if xgboost also support them.

I started adding this and it seems pretty straightforward. There is one problem though. xgboost computes the second derivative and for quantile loss it's a Dirac delta, i.e. zero everywhere except an infinite spike around x=0.
I'm not sure how the second derivative (Hessian) is used – it doesn't seem to be used in sklearn's implementation

Closing this issue for now – will try to put together a pull request with the implementation. But would love to hear if you have any thoughts about what to do with the hessian

I looked at this some more and I have implemented something.
The problem is again with the Hessian. From what I understand, xgboost uses Newton's method to find the optimum and that's why the Hessian is used.
I see several options

Instead of mean absolute error, use Huber loss
Instead of mean absolute error, use something like log(exp(-x) + exp(x) which is similar
Use mean absolute error and make xgboost work with first order methods

I can put together a PR for Huber loss for now, but I'm not super excited about it since it requires a parameter delta. But maybe let's start there?

closing for now, also note #736 refactor gives an plugin system https://github.com/dmlc/xgboost/tree/brick/plugin to add in new loss and metrics

@erikbern I was looking for this exactly. Is there a Hubert loss equivalent for the tilted absolute loss case (i.e. when you want other quantiles besides the median?).
Even if you did get a second derivative is there a batch processing method in XgBoost, otherwise taking the Hessian might be prohibitive.

I implemented Huber but it has the same problems with convergence since the derivative isn't continuous.
I think the only solution would be to support a first-order method that doesn't require the Hessian

The twice differentiable log-cosh loss seems to be a reasonably good option for the xgboost's 2nd order framework.

Hello @tqchen,
Are plugins still the recommended way to add custom loss functions?
Are plugins only usable through the C++ frontend?
If yes, I guess I won't be able to use my custom loss in R.
I assume I should be using the example of a custom objective for R instead.

The log-cosh objective still suffers from the gradient and hessian for very large off-target predictions being constant, therefore resulting in absence of splits. Here is a blog post on the topic, a possible solution and implementation in Python: http://www.bigdatarepublic.nl/regression-prediction-intervals-with-xgboost/


signin with uppercase letters

fixes https://github.com/hoodiehq/hoodie/issues/499

LGTM

LGTM 🚀
Great work @dsims00! :clap:


Docker build ends in CMake error

Hi
I ran the docker build command but ran into the following error:
CMake Error at CMakeLists.txt:22 (add_library):
0.379   Cannot find source file:
0.379
0.379     mav_trajectory_generation/mav_trajectory_generation/src/motion_defines.cpp

I saw that the most recent push to this repo (related to the docker build process) failed a test. Do you have plans to fix this?
Thanks

I personally don't use docker for this repo, but a PR would be very much welcome.


Can this use case of query cli to be add in document?(rescue schema)

Hello I found this use Case on twitter. I think it's very useful.
https://twitter.com/edgedatabase/status/1623787934964146176
If disaster strikes and your schema file gets mangled 🌪 but your database is still in good shape, you can build a new schema file from the current state of your database. 😃

Use this CLI command:
edgedb query "describe schema as sdl;" -F tab-separated > dbschema/default.esdl

I posted that to Twitter thinking it was more trivia than anything and would rarely be useful. That's what I get for thinking. 😆
I'll think about where the right place to put this might be in the documentation. Maybe a "Recipes" sub-section in the existing documentation for edgedb query? I can justify putting it there, but I'm not sure it would ever look there when they need it.
Do you have any ideas about where you would want to find this if you needed it, @AnsonHwang86? It almost feels like this goes in some kind of separate "Troubleshooting" page in the docs...

Thanks. I think sub-section in [the existing documentation for edgedb query](https://www.edgedb.com/docs/cli/edgedb_query) will be good.


[error] (run-main-0) java.lang.IllegalStateException: failed to create a child event loop

My startup's REST API services is based on Netty and use Elasticsearch's Java client API to connect to ES servers.
Es was 5.1.2 and now it is being upgraded to 5.2.0 so is the Java client API.
During upgrade testing, the REST API service can not be started. Error trace is as bellow.
The REST service is built with Scala 2.11.8, with SBT as the build tool. Help much appreciated as it is at beta testing and we have got some users already. And we also need to upgrade Elasticsearch to 5.2 as it provides range date types, which are important for our business case.
I am looking into it. In the meanwhile, any insight is much appreciated.
[error] (run-main-0) java.lang.IllegalStateException: failed to create a child event loop
java.lang.IllegalStateException: failed to create a child event loop
at io.netty.util.concurrent.MultithreadEventExecutorGroup.(MultithreadEventExecutorGroup.java:88)
at io.netty.util.concurrent.MultithreadEventExecutorGroup.(MultithreadEventExecutorGroup.java:58)
at io.netty.util.concurrent.MultithreadEventExecutorGroup.(MultithreadEventExecutorGroup.java:47)
at io.netty.channel.MultithreadEventLoopGroup.(MultithreadEventLoopGroup.java:58)
at io.netty.channel.epoll.EpollEventLoopGroup.(EpollEventLoopGroup.java:100)
at io.netty.channel.epoll.EpollEventLoopGroup.(EpollEventLoopGroup.java:87)
at io.netty.channel.epoll.EpollEventLoopGroup.(EpollEventLoopGroup.java:64)
at io.netty.channel.epoll.EpollEventLoopGroup.(EpollEventLoopGroup.java:48)
at io.netty.channel.epoll.EpollEventLoopGroup.(EpollEventLoopGroup.java:41)
at cn.shujubiji.bj.BjServiceServer$.main(BjServiceServer.scala:147)
at cn.shujubiji.bj.BjServiceServer.main(BjServiceServer.scala)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at sbt.Run.invokeMain(Run.scala:67)
at sbt.Run.run0(Run.scala:61)
at sbt.Run.sbt$Run$$execute$1(Run.scala:51)
at sbt.Run$$anonfun$run$1.apply$mcV$sp(Run.scala:55)
at sbt.Run$$anonfun$run$1.apply(Run.scala:55)
at sbt.Run$$anonfun$run$1.apply(Run.scala:55)
at sbt.Logger$$anon$4.apply(Logger.scala:84)
at sbt.TrapExit$App.run(TrapExit.scala:248)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalArgumentException
at sun.misc.Unsafe.allocateMemory(Native Method)
at io.netty.util.internal.PlatformDependent0.allocateMemory(PlatformDependent0.java:524)
at io.netty.util.internal.PlatformDependent.allocateMemory(PlatformDependent.java:260)
at io.netty.channel.epoll.IovArray.(IovArray.java:64)
at io.netty.channel.epoll.EpollEventLoop.(EpollEventLoop.java:62)
at io.netty.channel.epoll.EpollEventLoopGroup.newChild(EpollEventLoopGroup.java:130)
at io.netty.channel.epoll.EpollEventLoopGroup.newChild(EpollEventLoopGroup.java:35)
at io.netty.util.concurrent.MultithreadEventExecutorGroup.(MultithreadEventExecutorGroup.java:84)
at io.netty.util.concurrent.MultithreadEventExecutorGroup.(MultithreadEventExecutorGroup.java:58)
at io.netty.util.concurrent.MultithreadEventExecutorGroup.(MultithreadEventExecutorGroup.java:47)
at io.netty.channel.MultithreadEventLoopGroup.(MultithreadEventLoopGroup.java:58)
at io.netty.channel.epoll.EpollEventLoopGroup.(EpollEventLoopGroup.java:100)
at io.netty.channel.epoll.EpollEventLoopGroup.(EpollEventLoopGroup.java:87)
at io.netty.channel.epoll.EpollEventLoopGroup.(EpollEventLoopGroup.java:64)
at io.netty.channel.epoll.EpollEventLoopGroup.(EpollEventLoopGroup.java:48)
at io.netty.channel.epoll.EpollEventLoopGroup.(EpollEventLoopGroup.java:41)
at cn.shujubiji.bj.BjServiceServer$.main(BjServiceServer.scala:147)
at cn.shujubiji.bj.BjServiceServer.main(BjServiceServer.scala)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at sbt.Run.invokeMain(Run.scala:67)
at sbt.Run.run0(Run.scala:61)
at sbt.Run.sbt$Run$$execute$1(Run.scala:51)
at sbt.Run$$anonfun$run$1.apply$mcV$sp(Run.scala:55)
at sbt.Run$$anonfun$run$1.apply(Run.scala:55)
at sbt.Run$$anonfun$run$1.apply(Run.scala:55)
at sbt.Logger$$anon$4.apply(Logger.scala:84)
at sbt.TrapExit$App.run(TrapExit.scala:248)
at java.lang.Thread.run(Thread.java:745)
[debug] 	Thread run-main-0 exited.
[debug] Interrupting remaining threads (should be all daemons).
[debug] Interrupting thread MasterListener-shujubiji-[<IP_ADDRESS>:26380]
[debug] 	Interrupted MasterListener-shujubiji-[<IP_ADDRESS>:26380]
[debug] Interrupting thread elasticsearch[client][transport_client_boss][T#5]
[debug] 	Interrupted elasticsearch[client][transport_client_boss][T#5]
[debug] Interrupting thread elasticsearch[client][transport_client_boss][T#3]
[debug] 	Interrupted elasticsearch[client][transport_client_boss][T#3]
[debug] Interrupting thread elasticsearch[client][generic][T#4]
[debug] 	Interrupted elasticsearch[client][generic][T#4]
[debug] Interrupting thread AsyncAppender-Worker-ASYNC
[debug] 	Interrupted AsyncAppender-Worker-ASYNC
[debug] Interrupting thread elasticsearch[client][transport_client_boss][T#1]
[debug] 	Interrupted elasticsearch[client][transport_client_boss][T#1]
[debug] Interrupting thread threadDeathWatcher-2-1
[debug] 	Interrupted threadDeathWatcher-2-1
[debug] Interrupting thread elasticsearch[client][management][T#1]
[debug] 	Interrupted elasticsearch[client][management][T#1]
[debug] Interrupting thread elasticsearch[client][transport_client_boss][T#4]
[debug] 	Interrupted elasticsearch[client][transport_client_boss][T#4]
[debug] Interrupting thread Thread-2
[debug] 	Interrupted Thread-2
[debug] Interrupting thread MasterListener-shujubiji-[<IP_ADDRESS>:26381]
[debug] 	Interrupted MasterListener-shujubiji-[<IP_ADDRESS>:26381]
[debug] Interrupting thread elasticsearch[client][transport_client_boss][T#6]
[debug] 	Interrupted elasticsearch[client][transport_client_boss][T#6]
[debug] Interrupting thread commons-pool-EvictionTimer
[debug] 	Interrupted commons-pool-EvictionTimer
[debug] Interrupting thread elasticsearch[client][generic][T#1]
[debug] 	Interrupted elasticsearch[client][generic][T#1]
[debug] Interrupting thread elasticsearch[client][generic][T#2]
[debug] 	Interrupted elasticsearch[client][generic][T#2]
[debug] Interrupting thread idle_connection_reaper
[debug] 	Interrupted idle_connection_reaper
[debug] Interrupting thread elasticsearch[client][generic][T#3]
[debug] 	Interrupted elasticsearch[client][generic][T#3]
[debug] Interrupting thread elasticsearch[client][transport_client_boss][T#7]
[debug] 	Interrupted elasticsearch[client][transport_client_boss][T#7]
[debug] Interrupting thread elasticsearch[client][scheduler][T#1]
[debug] 	Interrupted elasticsearch[client][scheduler][T#1]
[debug] Interrupting thread elasticsearch[client][transport_client_boss][T#8]
[debug] 	Interrupted elasticsearch[client][transport_client_boss][T#8]
[debug] Interrupting thread elasticsearch[client][transport_client_boss][T#2]
[debug] 	Interrupted elasticsearch[client][transport_client_boss][T#2]
[debug] Interrupting thread elasticsearch[client][[timer]]
[debug] 	Interrupted elasticsearch[client][[timer]]
[debug] Interrupting thread MasterListener-shujubiji-[<IP_ADDRESS>:26382]
[debug] 	Interrupted MasterListener-shujubiji-[<IP_ADDRESS>:26382]
[debug] Interrupting thread MasterListener-shujubiji-[<IP_ADDRESS>:26379]
[debug] 	Interrupted MasterListener-shujubiji-[<IP_ADDRESS>:26379]
[debug] Sandboxed run complete..
java.lang.RuntimeException: Nonzero exit code: 1
at scala.sys.package$.error(package.scala:27)
at sbt.BuildCommon$$anonfun$toError$1.apply(Defaults.scala:2128)
at sbt.BuildCommon$$anonfun$toError$1.apply(Defaults.scala:2128)
at scala.Option.foreach(Option.scala:236)
at sbt.BuildCommon$class.toError(Defaults.scala:2128)
at sbt.Defaults$.toError(Defaults.scala:39)
at sbt.Defaults$$anonfun$runTask$1$$anonfun$apply$46$$anonfun$apply$47.apply(Defaults.scala:769)
at sbt.Defaults$$anonfun$runTask$1$$anonfun$apply$46$$anonfun$apply$47.apply(Defaults.scala:767)
at scala.Function1$$anonfun$compose$1.apply(Function1.scala:47)
at sbt.$tilde$greater$$anonfun$$u2219$1.apply(TypeFunctions.scala:40)
at sbt.std.Transform$$anon$4.work(System.scala:63)
at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:228)
at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:228)
at sbt.ErrorHandling$.wideConvert(ErrorHandling.scala:17)
at sbt.Execute.work(Execute.scala:237)
at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:228)
at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:228)
at sbt.ConcurrentRestrictions$$anon$4$$anonfun$1.apply(ConcurrentRestrictions.scala:159)
at sbt.CompletionService$$anon$2.call(CompletionService.scala:28)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
[error] (bj/compile:run) Nonzero exit code: 1
Full dependencies are as :
Expected behavior[debug] 	/home/fqye/projects/shujubiji/bj/target/scala-2.11/classes
[debug] 	/home/fqye/projects/shujubiji/util/target/scala-2.11/classes
[debug] 	/home/fqye/projects/shujubiji/common/target/scala-2.11/classes
[debug] 	/home/fqye/projects/shujubiji/bj/lib/netty-all-4.1.4.Final.jar
[debug] 	/home/fqye/projects/shujubiji/bj/lib/logback-classic-1.1.7.jar
[debug] 	/home/fqye/projects/shujubiji/bj/lib/logback-core-1.1.7.jar
[debug] 	/home/fqye/projects/shujubiji/util/lib/netty-all-4.1.4.Final.jar
[debug] 	/home/fqye/.ivy2/cache/org.scalactic/scalactic_2.11/bundles/scalactic_2.11-3.0.0.jar
[debug] 	/home/fqye/.ivy2/cache/org.scala-lang/scala-library/jars/scala-library-2.11.8.jar
[debug] 	/home/fqye/.ivy2/cache/org.scala-lang/scala-reflect/jars/scala-reflect-2.11.8.jar
[debug] 	/home/fqye/.ivy2/cache/org.asynchttpclient/async-http-client/jars/async-http-client-2.0.11.jar
[debug] 	/home/fqye/.ivy2/cache/io.netty/netty-transport-native-epoll/jars/netty-transport-native-epoll-4.0.39.Final-linux-x86_64.jar
[debug] 	/home/fqye/.ivy2/cache/org.asynchttpclient/netty-resolver-dns/jars/netty-resolver-dns-2.0.11.jar
[debug] 	/home/fqye/.ivy2/cache/org.asynchttpclient/netty-resolver/jars/netty-resolver-2.0.11.jar
[debug] 	/home/fqye/.ivy2/cache/org.slf4j/slf4j-api/jars/slf4j-api-1.7.21.jar
[debug] 	/home/fqye/.ivy2/cache/org.asynchttpclient/netty-codec-dns/jars/netty-codec-dns-2.0.11.jar
[debug] 	/home/fqye/.ivy2/cache/org.reactivestreams/reactive-streams/jars/reactive-streams-1.0.0.jar
[debug] 	/home/fqye/.ivy2/cache/com.typesafe.netty/netty-reactive-streams/jars/netty-reactive-streams-1.0.6.jar
[debug] 	/home/fqye/.ivy2/cache/org.javassist/javassist/bundles/javassist-3.20.0-GA.jar
[debug] 	/home/fqye/.ivy2/cache/com.typesafe/config/bundles/config-1.3.1.jar
[debug] 	/home/fqye/.ivy2/cache/io.argonaut/argonaut_2.11/jars/argonaut_2.11-6.1.jar
[debug] 	/home/fqye/.ivy2/cache/org.scalaz/scalaz-core_2.11/bundles/scalaz-core_2.11-7.1.1.jar
[debug] 	/home/fqye/.ivy2/cache/org.scala-lang.modules/scala-parser-combinators_2.11/bundles/scala-parser-combinators_2.11-1.0.2.jar
[debug] 	/home/fqye/.ivy2/cache/org.scala-lang.modules/scala-xml_2.11/bundles/scala-xml_2.11-1.0.2.jar
[debug] 	/home/fqye/.ivy2/cache/com.github.julien-truffaut/monocle-core_2.11/jars/monocle-core_2.11-1.1.0.jar
[debug] 	/home/fqye/.ivy2/cache/com.github.julien-truffaut/monocle-macro_2.11/jars/monocle-macro_2.11-1.1.0.jar
[debug] 	/home/fqye/.ivy2/cache/org.elasticsearch/elasticsearch/jars/elasticsearch-5.2.0.jar
[debug] 	/home/fqye/.ivy2/cache/org.apache.lucene/lucene-core/jars/lucene-core-6.4.0.jar
[debug] 	/home/fqye/.ivy2/cache/org.apache.lucene/lucene-analyzers-common/jars/lucene-analyzers-common-6.4.0.jar
[debug] 	/home/fqye/.ivy2/cache/org.apache.lucene/lucene-backward-codecs/jars/lucene-backward-codecs-6.4.0.jar
[debug] 	/home/fqye/.ivy2/cache/org.apache.lucene/lucene-grouping/jars/lucene-grouping-6.4.0.jar
[debug] 	/home/fqye/.ivy2/cache/org.apache.lucene/lucene-highlighter/jars/lucene-highlighter-6.4.0.jar
[debug] 	/home/fqye/.ivy2/cache/org.apache.lucene/lucene-join/jars/lucene-join-6.4.0.jar
[debug] 	/home/fqye/.ivy2/cache/org.apache.lucene/lucene-memory/jars/lucene-memory-6.4.0.jar
[debug] 	/home/fqye/.ivy2/cache/org.apache.lucene/lucene-misc/jars/lucene-misc-6.4.0.jar
[debug] 	/home/fqye/.ivy2/cache/org.apache.lucene/lucene-queries/jars/lucene-queries-6.4.0.jar
[debug] 	/home/fqye/.ivy2/cache/org.apache.lucene/lucene-queryparser/jars/lucene-queryparser-6.4.0.jar
[debug] 	/home/fqye/.ivy2/cache/org.apache.lucene/lucene-sandbox/jars/lucene-sandbox-6.4.0.jar
[debug] 	/home/fqye/.ivy2/cache/org.apache.lucene/lucene-spatial/jars/lucene-spatial-6.4.0.jar
[debug] 	/home/fqye/.ivy2/cache/org.apache.lucene/lucene-spatial-extras/jars/lucene-spatial-extras-6.4.0.jar
[debug] 	/home/fqye/.ivy2/cache/org.apache.lucene/lucene-spatial3d/jars/lucene-spatial3d-6.4.0.jar
[debug] 	/home/fqye/.ivy2/cache/org.apache.lucene/lucene-suggest/jars/lucene-suggest-6.4.0.jar
[debug] 	/home/fqye/.ivy2/cache/org.elasticsearch/securesm/jars/securesm-1.1.jar
[debug] 	/home/fqye/.ivy2/cache/net.sf.jopt-simple/jopt-simple/jars/jopt-simple-5.0.2.jar
[debug] 	/home/fqye/.ivy2/cache/com.carrotsearch/hppc/jars/hppc-0.7.1.jar
[debug] 	/home/fqye/.ivy2/cache/joda-time/joda-time/jars/joda-time-2.9.5.jar
[debug] 	/home/fqye/.ivy2/cache/org.yaml/snakeyaml/bundles/snakeyaml-1.15.jar
[debug] 	/home/fqye/.ivy2/cache/com.fasterxml.jackson.core/jackson-core/bundles/jackson-core-2.8.6.jar
[debug] 	/home/fqye/.ivy2/cache/com.fasterxml.jackson.dataformat/jackson-dataformat-smile/bundles/jackson-dataformat-smile-2.8.6.jar
[debug] 	/home/fqye/.ivy2/cache/com.fasterxml.jackson.dataformat/jackson-dataformat-yaml/bundles/jackson-dataformat-yaml-2.8.6.jar
[debug] 	/home/fqye/.ivy2/cache/com.fasterxml.jackson.dataformat/jackson-dataformat-cbor/bundles/jackson-dataformat-cbor-2.8.6.jar
[debug] 	/home/fqye/.ivy2/cache/com.tdunning/t-digest/jars/t-digest-3.0.jar
[debug] 	/home/fqye/.ivy2/cache/org.hdrhistogram/HdrHistogram/bundles/HdrHistogram-2.1.6.jar
[debug] 	/home/fqye/.ivy2/cache/net.java.dev.jna/jna/jars/jna-4.2.2.jar
[debug] 	/home/fqye/.ivy2/cache/org.elasticsearch.client/transport/jars/transport-5.2.0.jar
[debug] 	/home/fqye/.ivy2/cache/org.elasticsearch.plugin/transport-netty3-client/jars/transport-netty3-client-5.2.0.jar
[debug] 	/home/fqye/.ivy2/cache/io.netty/netty/bundles/netty-3.10.6.Final.jar
[debug] 	/home/fqye/.ivy2/cache/org.elasticsearch.plugin/transport-netty4-client/jars/transport-netty4-client-5.2.0.jar
[debug] 	/home/fqye/.ivy2/cache/io.netty/netty-buffer/jars/netty-buffer-4.1.7.Final.jar
[debug] 	/home/fqye/.ivy2/cache/io.netty/netty-common/jars/netty-common-4.1.7.Final.jar
[debug] 	/home/fqye/.ivy2/cache/io.netty/netty-codec/jars/netty-codec-4.1.7.Final.jar
[debug] 	/home/fqye/.ivy2/cache/io.netty/netty-transport/jars/netty-transport-4.1.7.Final.jar
[debug] 	/home/fqye/.ivy2/cache/io.netty/netty-resolver/jars/netty-resolver-4.1.7.Final.jar
[debug] 	/home/fqye/.ivy2/cache/io.netty/netty-codec-http/jars/netty-codec-http-4.1.7.Final.jar
[debug] 	/home/fqye/.ivy2/cache/io.netty/netty-handler/jars/netty-handler-4.1.7.Final.jar
[debug] 	/home/fqye/.ivy2/cache/org.elasticsearch.plugin/reindex-client/jars/reindex-client-5.2.0.jar
[debug] 	/home/fqye/.ivy2/cache/org.elasticsearch.client/rest/jars/rest-5.2.0.jar
[debug] 	/home/fqye/.ivy2/cache/org.apache.httpcomponents/httpclient/jars/httpclient-4.5.2.jar
[debug] 	/home/fqye/.ivy2/cache/org.apache.httpcomponents/httpcore/jars/httpcore-4.4.5.jar
[debug] 	/home/fqye/.ivy2/cache/commons-logging/commons-logging/jars/commons-logging-1.1.3.jar
[debug] 	/home/fqye/.ivy2/cache/commons-codec/commons-codec/jars/commons-codec-1.10.jar
[debug] 	/home/fqye/.ivy2/cache/org.apache.httpcomponents/httpasyncclient/jars/httpasyncclient-4.1.2.jar
[debug] 	/home/fqye/.ivy2/cache/org.apache.httpcomponents/httpcore-nio/jars/httpcore-nio-4.4.5.jar
[debug] 	/home/fqye/.ivy2/cache/org.elasticsearch.plugin/lang-mustache-client/jars/lang-mustache-client-5.2.0.jar
[debug] 	/home/fqye/.ivy2/cache/com.github.spullara.mustache.java/compiler/jars/compiler-0.9.3.jar
[debug] 	/home/fqye/.ivy2/cache/org.elasticsearch.plugin/percolator-client/jars/percolator-client-5.2.0.jar
[debug] 	/home/fqye/.ivy2/cache/io.netty/netty-all/jars/netty-all-4.1.7.Final.jar
[debug] 	/home/fqye/.ivy2/cache/org.apache.logging.log4j/log4j-to-slf4j/jars/log4j-to-slf4j-2.7.jar
[debug] 	/home/fqye/.ivy2/cache/org.apache.logging.log4j/log4j-api/jars/log4j-api-2.7.jar
[debug] 	/home/fqye/.ivy2/cache/ch.qos.logback/logback-classic/jars/logback-classic-1.1.7.jar
[debug] 	/home/fqye/.ivy2/cache/ch.qos.logback/logback-core/jars/logback-core-1.1.7.jar
[debug] 	/home/fqye/.ivy2/cache/redis.clients/jedis/jars/jedis-2.9.0.jar
[debug] 	/home/fqye/.ivy2/cache/org.apache.commons/commons-pool2/jars/commons-pool2-2.4.2.jar
[debug] 	/home/fqye/.ivy2/cache/com.aliyun.oss/aliyun-sdk-oss/jars/aliyun-sdk-oss-2.4.0.jar
[debug] 	/home/fqye/.ivy2/cache/org.jdom/jdom/jars/jdom-1.1.jar
[debug] 	/home/fqye/.ivy2/cache/net.sf.json-lib/json-lib/jars/json-lib-2.4-jdk15.jar
[debug] 	/home/fqye/.ivy2/cache/commons-beanutils/commons-beanutils/jars/commons-beanutils-1.8.0.jar
[debug] 	/home/fqye/.ivy2/cache/commons-collections/commons-collections/jars/commons-collections-3.2.1.jar
[debug] 	/home/fqye/.ivy2/cache/commons-lang/commons-lang/jars/commons-lang-2.5.jar
[debug] 	/home/fqye/.ivy2/cache/net.sf.ezmorph/ezmorph/jars/ezmorph-1.0.6.jar
[debug] 	/home/fqye/.ivy2/cache/org.apache.poi/poi/jars/poi-3.15.jar
[debug] 	/home/fqye/.ivy2/cache/org.apache.commons/commons-collections4/jars/commons-collections4-4.1.jar
[debug] 	/home/fqye/.ivy2/cache/org.apache.poi/poi-scratchpad/jars/poi-scratchpad-3.15.jar
[debug] 	/home/fqye/.ivy2/cache/org.apache.poi/poi-ooxml/jars/poi-ooxml-3.15.jar
[debug] 	/home/fqye/.ivy2/cache/org.apache.poi/poi-ooxml-schemas/jars/poi-ooxml-schemas-3.15.jar
[debug] 	/home/fqye/.ivy2/cache/org.apache.xmlbeans/xmlbeans/jars/xmlbeans-2.6.0.jar
[debug] 	/home/fqye/.ivy2/cache/stax/stax-api/jars/stax-api-1.0.1.jar
[debug] 	/home/fqye/.ivy2/cache/com.github.virtuald/curvesapi/jars/curvesapi-1.04.jar
Actual behavior
Steps to reproduce
Minimal yet complete reproducer code (or URL to code)
Netty version
4.17
JVM version (e.g. java -version)
openjdk version "1.8.0_121"
OpenJDK Runtime Environment (IcedTea 3.3.0) (suse-3.1-x86_64)
OpenJDK 64-Bit Server VM (build 25.121-b13, mixed mode)
OS version (e.g. uname -a)
Linux linux-68qh 4.9.11-1-default #1 SMP PREEMPT Sat Feb 18 17:59:27 UTC 2017 (cf9c670) x86_64 x86_64 x86_64 GNU/Linux

What cause trace (each getCause() until null) of this exception?

@Scottmitch yeah its because he tries to use the native transport while sun.misc.Unsafe is not accessible.
@fangqiao please use the NIO transport if you can not use sun.misc.Unsafe. In 4.1.8.Final we throw a more meaningful error.

That is what I figured. Update Netty :)

Thanks. It worked when I tried Nio.
But I am curious why I can use Epoll before I upgrade Elasticsearch Java client to 5.2.2? It worked with Epoll very well and was deployed to production with no problems at all.

@fangqiao from what I understand elastic search has a very tight securitymanager config these days. @jasontedor any idea ?


[BUG] xxx is not supported event type for OpenIMSDKRN

OpenIM Server Version
3.7.1
Operating System and CPU Architecture
macOS (ARM)
Deployment Method
Source Code Deployment
Bug Description and Steps to Reproduce

在测试聊天界面的时候发现没有实时收到消息
Screenshots Link
No response

we will fix next version


Comments from reviewers that are relevant for the thesis

Test their statistical approach compared to what can be inferred from other statistical analyses for at least one of their datasets

control data sets should be constructed in which the ‘correct’ outcomes are known

Can RGCCA explain more about the biology behind the datasets than its counterparts?

“Only the models in which all the blocks were part of a single connected network were analyzed”. Why this choice? Should not a disconnected block (or more) be interpreted as a complete lack of interaction between the block of variables with the other ones?

Use ASV with DADA2?

16S data for copy number variation and add what kind of repercussion it can have on the analysis.

Worth mentioning Correcting for 16S rRNA gene copy numbers in microbiome surveys remains an unsolved problem that I found after a quick google search

Cited and mentioned and discussed on the thesis


Can't fetch GLS trancactions anymore

Until today I was able to fetch transactions just fine with fints2ledger 0.6.0. Today I can't anymore:
❯ fints2ledger --csv-file /home/varac/.config/fints2ledger/transactions-giro.csv --ledger-file /home/varac/beancount/journals/fints2ledger-giro.beancount --date 2020/12/01
You should register your program with the ZKA and pass your own product_id as a parameter.
Dialog response: 9050 - Die Nachricht enthält Fehler.
Dialog response: 9800 - Dialog abgebrochen
Dialog response: 9340 - Auftrag abgelehnt.
Traceback (most recent call last):
  File "/home/varac/.local/pipx/venvs/fints2ledger/lib/python3.8/site-packages/fints/client.py", line 453, in get_sepa_accounts
    return self._send_with_possible_retry(dialog, seg, self._get_sepa_accounts)
  File "/home/varac/.local/pipx/venvs/fints2ledger/lib/python3.8/site-packages/fints/client.py", line 1234, in _send_with_possible_retry
    response = dialog.send(command_seg)
  File "/home/varac/.local/pipx/venvs/fints2ledger/lib/python3.8/site-packages/fints/dialog.py", line 156, in send
    self.client.process_response_message(self, response, internal_send=internal_send)
  File "/home/varac/.local/pipx/venvs/fints2ledger/lib/python3.8/site-packages/fints/client.py", line 230, in process_response_message
    self._process_response(dialog, None, response)
  File "/home/varac/.local/pipx/venvs/fints2ledger/lib/python3.8/site-packages/fints/client.py", line 1294, in _process_response
    raise FinTSClientPINError("Error during dialog initialization, PIN wrong?")
fints.exceptions.FinTSClientPINError: Error during dialog initialization, PIN wrong?

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/varac/.local/bin/fints2ledger", line 8, in <module>
    sys.exit(main())
  File "/home/varac/.local/pipx/venvs/fints2ledger/lib/python3.8/site-packages/fints2ledger/main.py", line 9, in main
    Fints2Csv(config).retrieveAndSave()
  File "/home/varac/.local/pipx/venvs/fints2ledger/lib/python3.8/site-packages/fints2ledger/fints2csv.py", line 24, in retrieveAndSave
    transaction), retriever.get_hbci_transactions(self.config["fints"]["start"], Date.today())))
  File "/home/varac/.local/pipx/venvs/fints2ledger/lib/python3.8/site-packages/fints2ledger/transaction_retriever.py", line 7, in get_hbci_transactions
    accounts = self.client.get_sepa_accounts()
  File "/home/varac/.local/pipx/venvs/fints2ledger/lib/python3.8/site-packages/fints/client.py", line 453, in get_sepa_accounts
    return self._send_with_possible_retry(dialog, seg, self._get_sepa_accounts)
  File "/home/varac/.local/pipx/venvs/fints2ledger/lib/python3.8/site-packages/fints/dialog.py", line 45, in __exit__
    self.end()
  File "/home/varac/.local/pipx/venvs/fints2ledger/lib/python3.8/site-packages/fints/dialog.py", line 112, in end
    response = self.send(HKEND1(self.dialog_id), internal_send=True)
  File "/home/varac/.local/pipx/venvs/fints2ledger/lib/python3.8/site-packages/fints/dialog.py", line 131, in send
    self.finish_message(message)
  File "/home/varac/.local/pipx/venvs/fints2ledger/lib/python3.8/site-packages/fints/dialog.py", line 178, in finish_message
    auth_mech.sign_commit(message)
  File "/home/varac/.local/pipx/venvs/fints2ledger/lib/python3.8/site-packages/fints/security.py", line 157, in sign_commit
    user_defined_signature=UserDefinedSignature(
  File "/home/varac/.local/pipx/venvs/fints2ledger/lib/python3.8/site-packages/fints/types.py", line 360, in __init__
    setattr(self, k, v)
  File "/home/varac/.local/pipx/venvs/fints2ledger/lib/python3.8/site-packages/fints/types.py", line 45, in __set__
    value_ = self._parse_value(value)
  File "/home/varac/.local/pipx/venvs/fints2ledger/lib/python3.8/site-packages/fints/fields.py", line 299, in _parse_value
    return Password(value)
  File "/home/varac/.local/pipx/venvs/fints2ledger/lib/python3.8/site-packages/fints/utils.py", line 260, in __str__
    raise Exception("Refusing to use PIN after block")
Exception: Refusing to use PIN after block

Right after this Exception, I get a useless PIN sent to my phone.
I upgraded to 0.6.1 but this didn't help neither. Any ideas what's wrong ?

Nevermind, after logging in to the bank using 2fa it worked again.


Addition of Tests for the PrettyPrinter Package

type:
Tests

description:
This PR focuses on enhancing the test coverage for the prettyprinter package. The following changes have been made:

Added tests for the clusterscan_test.go file. The tests cover the TestClusterScan_getNextSteps, TestNewClusterPrinter, TestPrintNextSteps, and TestGetWorkloadScanCommand functions.
Added tests for the frameworkscan_test.go file. The tests cover the TestNewSummaryPrinter and TestGetVerboseMode functions.
Added tests for the imagescan_test.go file. The tests cover the TestNewImagePrinter and TestPrintNextSteps_ImageScan functions.

main_files_walkthrough:
 files:

core/pkg/resultshandling/printer/v2/prettyprinter/clusterscan_test.go: Added tests for the TestClusterScan_getNextSteps, TestNewClusterPrinter, TestPrintNextSteps, and TestGetWorkloadScanCommand functions.
core/pkg/resultshandling/printer/v2/prettyprinter/frameworkscan_test.go: Added tests for the TestNewSummaryPrinter and TestGetVerboseMode functions.
core/pkg/resultshandling/printer/v2/prettyprinter/imagescan_test.go: Added tests for the TestNewImagePrinter and TestPrintNextSteps_ImageScan functions.

/descrive

@VaibhavMalik4187 I have issues with colors:
        	Error Trace:	/home/mbertschy/github.com/kubescape/kubescape/core/pkg/resultshandling/printer/v2/prettyprinter/clusterscan_test.go:87
        	Error:      	Not equal:
        	            	expected: "\n\x1b[97m\x1b[1mWhat now?\x1b[22m\x1b[39m\x1b[38;5;238m\x1b[1m\x1b[22m\x1b[39m\n\x1b[38;5;238m\x1b[1m─────────\x1b[22m\x1b[39m\n\x1b[38;5;238m\x1b[1m\x1b[22m\x1b[39m\n\x1b[38;5;238m\x1b[1m\x1b[22m\x1b[39m\x1b[38;5;238m\x1b[1m* \x1b[22m\x1b[39m\x1b[37mRun one of the suggested commands to learn more about a failed control failure\x1b[39m\n\x1b[37m\x1b[39m\x1b[38;5;238m\x1b[1m* \x1b[22m\x1b[39m\x1b[37mScan a workload with \x1b[97m\x1b[1m'$ kubescape scan workload'\x1b[22m\x1b[37m to see vulnerability information\x1b[39m\n\x1b[37m\x1b[39m\x1b[38;5;238m\x1b[1m* \x1b[22m\x1b[39m\x1b[37mInstall Kubescape in your cluster for continuous monitoring and a full vulnerability report: https://kubescape.io/docs/install-operator/\x1b[39m\n\x1b[37m\x1b[39m\x1b[37m\x1b[39m\n\x1b[37m\x1b[39m"
        	            	actual  : "\nWhat now?\n─────────\n\n* Run one of the suggested commands to learn more about a failed control failure\n* Scan a workload with '$ kubescape scan workload' to see vulnerability information\n* Install Kubescape in your cluster for continuous monitoring and a full vulnerability report: https://kubescape.io/docs/install-operator/\n\n"

@matthyx it's ready for a review.