Problem with NERDTree

Hey, nice job with vim-crystal, i figured out about crystal-lang yesterday and the first think that i looked for was the plugin for vim.
So, my NERDTree became weird after the vim-crystal. The problem is, when I open the vim for the first time its normal, then I open a .cr file and the colours of the NERDTree still normal. The problem begins when I close the .cr file and open another .cr, the NERDTree loses all the colours and became green.
When I open the for the first time

When i close the file and open another

Hi, @basmoura .
Thank you for your report.
I actually don't use nerdtree.  So I tried it in minimum environment.
$ mkdir tmp && cd tmp
$ git clone https://github.com/scrooloose/nerdtree.git
$ git clone https://github.com/rhysd/vim-crystal.git

And I wrote very small vimrc as tmp.vimrc.
set nocompatible
set rtp+=./nerdtree
set rtp+=./vim-crystal

syntax enable
colorscheme desert

Then I started vim.
$ vim -u tmp.vimrc

After that, I executed :NERDTreeToggle and opened crystal code, closed it and opened second crystal code.
Then I could reproduce the collapsed syntax highlight :tada:

@basmoura
The reason is that the filetype of NERDTree buffer is set to crystal.
I think this is an issue of NERDTree on opening a file without an empty buffer because vim-crystal is a very simple filetype plugin.
Could you report this bug to NERDTree issues with this page's URL?  I think NERDTree developer can solve the problem.

@basmoura
I found a bug on filetype detection in vim-crystal.  I fixed it in 6d69504.  At least the bug was fixed in my test environment.
Could you update vim-crystal and test it?  If test is OK, I'll close this issue.

@rhysd works perfectly :tada:
thank you, nice job man!

@basmoura
Thanks for your confirmation!


Update readme details for Kubeflow 1.3

For Kubeflow 1.3, the minimum k8s version is 1.17 and the default nodeport are exposed to 30380.

/lgtm
/approve


skippy-gradle-android plugin does not always write test-impact-analysis.json

The skippy-gradle-android plugin does not always write the test-impact-analysis.json file.
How to re-produce: Use the attached project and execute the following commands:
Command 1
./gradlew clean skippyClean && ls app/.skippy

BUILD SUCCESSFUL in 670ms
2 actionable tasks: 1 executed, 1 up-to-date

config.json

Command 2
./gradlew check && ls -l app/.skippy

BUILD SUCCESSFUL in 6s
60 actionable tasks: 2 executed, 58 up-to-date

com.example.testskippy.MyJavaSkippyTest.exec
com.example.testskippy.MyTestOne.exec
config.json
predictions.log

The above output is not as expected.
Command 3
The expected output is generated if check is executed again:
./gradlew check && ls -l app/.skippy

BUILD SUCCESSFUL in 6s
60 actionable tasks: 2 executed, 58 up-to-date

LATEST
config.json
test-impact-analysis.json

TestSkippy.zip

Relates to https://github.com/skippy-io/skippy/issues/162

How to re-produce:
git clone git@github.com:skippy-io/skippy-android-sandbox.git

Next, import the project into IntelliJ and execute :app:check:

For some reason, classesDirs is empty when afterEvaluate for :app is executed:

This causes ProjectSettings to not invoke the action that calls Skippy's build api:

My current assumption: The Android plugin collects the classes directories too early:
https://github.com/skippy-io/skippy/blob/7e8ebcfa8bfe0b33fb84a9de7735800122bf937d/skippy-gradle-android/src/main/java/io/skippy/gradle/android/ProjectSettings.java#L43-L51
For some reason, that's not a problem with the Java plugin that retrieves the classes directories from the SourceSetContainer:
https://github.com/skippy-io/skippy/blob/7e8ebcfa8bfe0b33fb84a9de7735800122bf937d/skippy-gradle/src/main/java/io/skippy/gradle/ProjectSettings.java#L60-L72

I think we have to get rid of the File::exists check:
https://github.com/skippy-io/skippy/blob/7e8ebcfa8bfe0b33fb84a9de7735800122bf937d/skippy-gradle-android/src/main/java/io/skippy/gradle/android/AndroidDestinationDirectoryCollector.java#L43

https://github.com/skippy-io/skippy/pull/198
https://github.com/skippy-io/skippy-regression-suite/pull/13


Custom-made profiles for other games not working after alt-tabbing out and back in

Expected behavior:
Aurora switches from desktop profile to profile for respective game after tabbing out and back in.
Actual behavior:
Aurora stays on desktop profile as if the game isn't active anymore.
How often does this problem occur?
This problem occurs every time you alt-tab out and back in after launching it.
Please describe the steps to reproduce this issue:
The issue can be reproduced by doing following steps:

Install game (in my case it was osu!)
Create profile for game in Aurora (My profile was just static colors for certain keys)
Launch game
Alt-tab out of the game
Alt-tab back into the game.

What is the version of Aurora you are experiencing this issue with?
My version is v0.6.2b
Does the previous version of Aurora have this issue?
The previous version, v0.6.1-dev4, doesn't support my keyboard so I probably wouldn't be able to test it.
Please include any logs, screenshots, or files that are related to this issue:
Profile: https://i.imgur.com/iCZ0SHU.png
Profile showing on keyboard: https://i.imgur.com/oV3jQK0.jpg
Game showing profile: https://i.imgur.com/30vWDl7.jpg
Game after tabbing out and back in: https://i.imgur.com/NJlmPHG.jpg

Try going into aurora settings and switching the detection method from Windows events to the other one. I had that problem at first but foreground app scan seems to be more reliable.

Thanks! It works perfectly now.


Darwin: "Error: Is a directory (os error 21)" on "fossilizer import ~/Downloads/hachyderm-20240411.tar"

System is Safari, MacOS Ventura 13.6.6. My Mastodon instance is hachyderm.io (one of them at least).
Download an archive, but helpfully (?) Safari untars the file, so I have to re-tar it for fossilizer.
% fossilizer import ~/Downloads/hachyderm-20240411.tar
[2024-04-11T23:43:19Z INFO  fossilizer::cli::import] Importing "/Users/emv/Downloads/hachyderm-20240411.tar"
[2024-04-11T23:43:21Z INFO  fossilizer::mastodon] Found 1125 items
[2024-04-11T23:43:21Z INFO  fossilizer::db::activities] Imported 500 items
[2024-04-11T23:43:21Z INFO  fossilizer::db::activities] Imported 1000 items
Error: Is a directory (os error 21)

> ~/src/github.com/lmorchard/fossilizer/target/debug/fossilizer -V
fossilizer 0.2.0

Same result when I build from source and when I use the provided binary.

Hmm, that's an unexpected error... guessing something tried to write a file where there was already a directory, but that's weird
You might want to try deleting any existing build or data directory (rm -rf ./build ./data) and try a fossilizer init and then another import from scratch?
I'm going to scratch my head a bit at where that error might have come from and see if I can add some better error reporting.

ok, problem avoided, and a possible diagnosis:
first, Safari helpfully (?) expands out zip files when you download them, but you can avoid that with ctrl-click and then "Download linked file"
second, the linked file is a .zip file which works just fine I guess (no errors on import); the error that I got above happened after I tried to import a tar file that had been created from the expanded out zip file.
The workaround is easy enough and I blame my browser not your code.


Enhancement: Reference phpunit.xsd as installed with composer

This PR

[x] references phpunit.xsd as installed with composer

❗ Blocked by #53.
💁♂ Helps with auto-completion!

@localheinz Thank you, this will help developers better complete their phpunit.xml

Thank you, @johnkary!


Add a Gitter chat badge to README.md

jdhom/flippers now has a Chat Room on Gitter
@jdhom has just created a chat room. You can visit it here: https://gitter.im/jdhom/flippers.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

had already added gitter to readme.md


Test: server Update book summaries

Test Plan: Update Book Report Summaries API Endpoint
Test Scenarios

Valid Update Request

Description: Sending a valid request to update the book report summary for a specific chapter.
Steps:

Prepare a request with valid parameters including book ID, chapter number, and updated summary.
Send the request to the API endpoint for updating book report summaries.
Verify the response status code and message.
Check the database or storage to ensure that the book report summary for the specified chapter is updated as expected.

Expected Result: The API endpoint updates the book report summary for the specified chapter, and the response indicates successful completion.

Invalid Parameters

Description: Testing the API endpoint with invalid or missing parameters.
Steps:

Prepare a request with missing or invalid parameters (e.g., missing book ID, invalid chapter number).
Send the request to the API endpoint for updating book report summaries.
Verify the response status code and message.
Ensure that the book report summary is not updated and no changes are made to the database.

Expected Result: The API endpoint rejects the request due to invalid parameters and returns an appropriate error response.

Unauthorized Access

Description: Attempting to access the API endpoint without proper authentication.
Steps:

Send a request to the API endpoint without including authentication credentials.
Verify the response status code and message.
Check whether the request is denied and no changes are made to the book report summaries.

Expected Result: The API endpoint rejects the unauthorized request and returns a 401 Unauthorized response.

Error Handling

Description: Testing error handling and edge cases.
Steps:

Introduce errors such as database connectivity issues or unexpected server errors.
Send requests to the API endpoint under these conditions.
Verify the response status code and message.

Expected Result: The API endpoint gracefully handles errors and returns appropriate error responses without compromising data integrity.

Notes

Execute the test scenarios sequentially, ensuring thorough coverage of all functionalities.
Record and report any issues encountered during testing for further investigation and resolution.
Collaborate with backend developers to address any identified issues and ensure the stability and reliability of the API endpoint.

did this


Application reorder

What this PR does / Why we need it
Reordered the application so gender isn't first. Added in the description that we offer the data to our sponsors.
Some questions

[ ] I have read the contributing guidelines
[ ] I abide by this repository Code of Conduct
[ ] I understand that my PR won't be merged until Travis gives a "green light"

Additional Notes (optional)
Do you want to add anything else? We :heart: to hear your opinions!

Can't accept this Moving changes to #199 as submitted by @qaisjp


MobileNetV3 keras models have bug with GlobalAveragePooling2D

System information
TensorFlow version:
print(tf.version.GIT_VERSION, tf.version.VERSION)
v2.4.0-rc4-71-g582c8d236cb 2.4.0

Describe the current behavior
According to MobileNetV3Small documentation

The weights for all 6 models are obtained and translated from the Tensorflow checkpoints from TensorFlow checkpoints found here.

But keras models cannot reproduce performance on ImageNet #48066.
Tensorflow pb model contains GlobalAvgPool before Conv2D with filter <1x1x576x1024>:

But MobileNetV3Small from keras.application contains GlobalAvgPool after Conv2D with filter <1x1x576x1024>:

https://github.com/tensorflow/tensorflow/blob/6a278b9cf2fbed781661079b13d88b4106622a09/tensorflow/python/keras/applications/mobilenet_v3.py#L295-L308
Such version of MobileNetV3Small achieves top1: 56.79% instead of 68.1%.
Describe the expected behavior
To achieve reported accuracy, change model code to:
  x = activation(x)

  x = layers.GlobalAveragePooling2D()(x)
  if channel_axis == 1:
    x = layers.Reshape((last_conv_ch, 1, 1))(x)
  else:
    x = layers.Reshape((1, 1, last_conv_ch))(x)

  x = layers.Conv2D(
      last_point_ch,
      kernel_size=1,
      padding='same',
      use_bias=True,
      name='Conv_2')(x)
  x = activation(x)

  if include_top:
    if dropout_rate > 0:
      x = layers.Dropout(dropout_rate)(x)
    x = layers.Conv2D(classes, kernel_size=1, padding='same', name='Logits')(x)
    x = layers.Flatten()(x)
    imagenet_utils.validate_activation(classifier_activation, weights)
    x = layers.Activation(activation=classifier_activation,
                          name='Predictions')(x)

Thanks for the report. Please open a PR with the fix.

Thanks for reporting the issue. Please https://github.com/tensorflow/tensorflow/pull/48542#issuecomment-824258134 for more updates. #48542 should fix the issue.


During the load testing thousands of HTTP requests were generated by the golang HTTP client. The server couldn't keep up with the load and requests started timeouting.
What did you see happen?
We added a simple atomic counter to see the progress of processed requests and realized, that when the load is too high, some client goroutines never finish even though a context with a deadline is used. A dump from the client showed the following stuck stack traces:
#	0x7379b8	net/http.(*persistConn).roundTrip+0x978								/usr/local/go/src/net/http/transport.go:2675
#	0x72b859	net/http.(*Transport).roundTrip+0x799								/usr/local/go/src/net/http/transport.go:608
#	0x70f6b2	net/http.(*Transport).RoundTrip+0x12								/usr/local/go/src/net/http/roundtrip.go:17
#	0x1fafeb3	github.com/opentracing-contrib/go-stdlib/nethttp.(*Transport).RoundTrip+0x253

What did you expect to see?
As we went deeper we saw a possible place in the net/http/transport.go that could cause the issue. When the readLoop is waiting when reading the body of the response and the pc.roundTrip waits until pgClosed/cancelChan/ctxDoneChan, it might happen, that the select in readLoop processes the rc.req.Cancel or rc.req.Context().Done(), calls and removes the cancelKeyFn from the transport.reqCanceler and the pc.roundTrip.pcClosed case will never have canceled=true or even pc.t.replaceReqCanceler()=true because the transport.reqCanceler won't contain the cancelKey anymore.
The prerequisites for this to happen are:

the processing timeouted or is canceled
the rc.reqCancel or rc.req.Context().Done() is processed by readLoop

CC @neild

This issue may have something to do with 212d385 and 854a2f8.

As we went deeper we saw a possible place in the net/http/transport.go that could cause the issue. When the readLoop is waiting when reading the body of the response and the pc.roundTrip waits until pgClosed/cancelChan/ctxDoneChan, it might happen, that the select in readLoop processes the rc.req.Cancel or rc.req.Context().Done(), calls and removes the cancelKeyFn from the transport.reqCanceler and the pc.roundTrip.pcClosed case will never have canceled=true or even pc.t.replaceReqCanceler()=true because the transport.reqCanceler won't contain the cancelKey anymore.
The prerequisites for this to happen are:

the processing timeouted or is canceled
the rc.reqCancel or rc.req.Context().Done() is processed by readLoop

Nonetheless, I'm not so convinced by this analysis because if the client has made its way to here:
https://github.com/golang/go/blob/065c5d220e802e85d410a5e6adba0819ab71aeda/src/net/http/transport.go#L2272-L2277
, a response should have been sent out, which would set free the roundtrip method from blocking in select{...}:
https://github.com/golang/go/blob/065c5d220e802e85d410a5e6adba0819ab71aeda/src/net/http/transport.go#L2708-L2718
Any chance you can write a test that can reproduce this issue? Thanks!
@rschone

That was our best guess :( Hmm, you're right that the case re := <-resc has to free the roundtrip method when the readLoop reaches its last select, there must be something else.
The problem is that the situation with stuck goroutines is reproducible only in production. A gateway service (Golang, HTTP client) communicates with a Java service (HTTP server here) using PUT call. Both HA, initially 2->2 pods before scaling. When the gateway is bombed by requests generated by dozens of pods (simulated DDoS - hundreds of requests per second on each of them), the Java service starts to become slow and latencies rise, the number of concurrently processed requests in the gateway goes from ~tens to ~thousands. We let the load test go in such frequency for ~15-30 seconds and then turn it off (to reproduce the issue but being under k8s memory limits - not kill the pods and before the services scale up and spread the load handling). After this load test a metric watching the number of currently processed requests shows values around ~lower hundreds (and never returns to the normal level of ~tens). The same number of stuck goroutines is visible in pprof dump.
So the only information we have is the pprof dump pointing us to the roundtrip method. Still far from writing a test, searching for the exact reason :(
We set ResponseHeaderTimeout, there is deadline on context, we tried it without trace round tripper, disabled keep alive, with different golang versions - 1.21, 1.22 but nothing from this helped to stop the goroutines stuck.
Any ideas how to proceed further or what else to try? Thank you!

That was our best guess :( Hmm, you're right that the case re := <-resc has to free the roundtrip method when the readLoop reaches its last select, there must be something else.
The problem is that the situation with stuck goroutines is reproducible only in production. A gateway service (Golang, HTTP client) communicates with a Java service (HTTP server here) using PUT call. Both HA, initially 2->2 pods before scaling. When the gateway is bombed by requests generated by dozens of pods (simulated DDoS - hundreds of requests per second on each of them), the Java service starts to become slow and latencies rise, the number of concurrently processed requests in the gateway goes from ~tens to ~thousands. We let the load test go in such frequency for ~15-30 seconds and then turn it off (to reproduce the issue but being under k8s memory limits - not kill the pods and before the services scale up and spread the load handling). After this load test a metric watching the number of currently processed requests shows values around ~lower hundreds (and never returns to the normal level of ~tens). The same number of stuck goroutines is visible in pprof dump.
So the only information we have is the pprof dump pointing us to the roundtrip method. Still far from writing a test, searching for the exact reason :(
We set ResponseHeaderTimeout, there is deadline on context, we tried it without trace round tripper, disabled keep alive, with different golang versions - 1.21, 1.22 but nothing from this helped to stop the goroutines stuck.
Any ideas on how to proceed further to localize the bug? Thank you!

I'll keep investigating this. In the meantime, please inform us by updating this issue thread if any helpful info pops into your head, thanks!


[aws-crt-cpp/aws-sdk-cpp] Disable parallel configure

Fixes https://github.com/microsoft/vcpkg/issues/20167
aws-crt-cpp/aws-sdk-cpp configure Config.h to source directory, it cause the failures in parellel configure, so disable the parellel configure.
See https://github.com/awslabs/aws-crt-cpp/blob/main/CMakeLists.txt#L87
CMake Error at CMakeLists.txt:87 (configure_file):
configure_file attempted to configure a file:
C:/Users/xanat/Documents/Files/Projects/system_monitor/third-party/vcpkg/buildtrees/aws-crt-cpp/src/c763da6810-ba58d2be12.clean/include/aws/crt/Config.h
into a source directory.

cc @camarois

Thanks for the fix!


custom data column name support in text_classification train script

this PR adds support for custom data column name support in the sparseml.transformers.text_classification train script.
input_column_names allows for one or two column names in the input csv/json file to be specified as inputs to the model/tokenizer
label_column_name gives the user the ability to override the default label name for model targets
existing behavior should not be modified based on these changes

thanks @mgoin @KSGulin responded


Create ascaz

@0xNinjaCoder lib/domains/ng/edu/ascaz: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@0xNinjaCoder I have to close this request without merging, because you requested to add a non-existent domain to this repository: Host ascaz.edu.ng not found: 3(NXDOMAIN) Please ensure that you are familiar with this repository rules located at the bottom of this page and submit a new request with the correct information. Thank you for understanding!


Element keeps dragging after mouse up.

Hi .
Not sure if it happened to you too but must be pretty common. I'm using resize validator. The element stops when validator returns false but it keeps moving after I release the mouse button (when I pass over it again).
Thank you,
Mani
Update: I guess passing over an iframe causes this
Update: OK putting an overlay on the iframe solved the problem, its has nothing to do with this package. Thanks again

Glad you got it sorted 😄


The additionalProperties field in OpenAPI schema makes build fail

What are the steps to reproduce this issue?
Example OpenAPI definition:
"MyObject": {
  "type": "object",
  "properties": {
    "empty": {
      "type": "boolean"
    }
  },
  "additionalProperties": {
    "type": "object"
  }
}

What happens?
Orval generates the following code:
export interface MyObject {
  empty?: boolean;
  [key: string]: { [key: string]: any }
}

What were you expecting to happen?
No types clash.
Any logs, error output, etc?
Typescript throws build error:
Property 'empty' of type "boolean | undefined" is not assignable to 'string' index type '{ [key: string]: any }'. ts(2411)
What versions are you using?
Operating System: Windows 10
Package Version: 6.29.1

Have you tried 6.31.0?

With 6.31.0 the output is a bit different: unknown instead of any, but tcs compilation still fails with same error.
export interface MyObject {
  empty?: boolean;
  [key: string]: { [key: string]: unknown }
}

I think this is relatively a duplicate of https://github.com/anymaniax/orval/issues/419
???

up?


ImportError: cannot import name 'soft_unicode' from 'markupsafe'

2022-02-18T13:55:12.9961209Z           from jinja2 import Environment, FileSystemLoader
2022-02-18T13:55:12.9962165Z         File ".../python3.9/site-packages/jinja2/__init__.py", line 33, in <module>
2022-02-18T13:55:12.9962690Z           from jinja2.environment import Environment, Template
2022-02-18T13:55:13.0123423Z         File ".../python3.9/site-packages/jinja2/environment.py", line 15, in <module>
2022-02-18T13:55:13.0124029Z           from jinja2 import nodes
2022-02-18T13:55:13.0124565Z         File ".../python3.9/site-packages/jinja2/nodes.py", line 19, in <module>
2022-02-18T13:55:13.0124932Z           from jinja2.utils import Markup
2022-02-18T13:55:13.0125450Z         File ".../jinja2/utils.py", line 642, in <module>
2022-02-18T13:55:13.0125825Z           from markupsafe import Markup, escape, soft_unicode
2022-02-18T13:55:13.0126431Z       ImportError: cannot import name 'soft_unicode' from 'markupsafe' .../python3.9/site-packages/markupsafe/__init__.py)

From: https://github.com/astropy/astrowidgets/runs/5248500732?check_suite_focus=true
Might be caused by problem mentioned in https://github.com/aws/aws-sam-cli/issues/3661#issuecomment-1044307257

Environment:

Python version: 3.9
Jinja version: Log didn't say, probably your latest stable release

p.s. I saw pallets/markupsafe#286 but the resolution is unclear to me.

How is pip pulling in unsupported version from PyPI? jinja2 isn't a direct dependency. Can you please clarify? Thanks!


[paperless_ngx] Unable to find zbar shared library

Which addon?

Addon name : paperless_ngx
Addon version : latest

Describe the bug
When uploading, an error comes up: Unable to find zbar shared library. When checking here: https://github.com/paperless-ngx/paperless-ngx/blob/main/docs/setup.rst#bare-metal-route it looks like some dependencies are missing
To Reproduce

Upload a document from the home page
See error

Full addon log
[2022-04-30 22:09:54 +0000] [1069] [WARNING] Worker with pid 1102 was terminated due to signal 9
22:11:02 [Q] INFO Enqueued 1
22:11:02 [Q] INFO Process-1:8 processing [***.pdf]
Process Process-1:8:
Traceback (most recent call last):
  File "/usr/lib/python3.8/pydoc.py", line 347, in safeimport
    module = __import__(path)
  File "/app/paperless/src/documents/tasks.py", line 25, in <module>
    from pyzbar import pyzbar
  File "/usr/local/lib/python3.8/dist-packages/pyzbar/pyzbar.py", line 7, in <module>
    from .wrapper import (
  File "/usr/local/lib/python3.8/dist-packages/pyzbar/wrapper.py", line 151, in <module>
    zbar_version = zbar_function(
  File "/usr/local/lib/python3.8/dist-packages/pyzbar/wrapper.py", line 148, in zbar_function
    return prototype((fname, load_libzbar()))
  File "/usr/local/lib/python3.8/dist-packages/pyzbar/wrapper.py", line 127, in load_libzbar
    libzbar, dependencies = zbar_library.load()
  File "/usr/local/lib/python3.8/dist-packages/pyzbar/zbar_library.py", line 65, in load
    raise ImportError('Unable to find zbar shared library')
ImportError: Unable to find zbar shared library
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/lib/python3.8/multiprocessing/process.py", line 315, in _bootstrap
    self.run()
  File "/usr/lib/python3.8/multiprocessing/process.py", line 108, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/local/lib/python3.8/dist-packages/django_q/cluster.py", line 424, in worker
    f = pydoc.locate(f)
  File "/usr/lib/python3.8/pydoc.py", line 1632, in locate
    nextmodule = safeimport('.'.join(parts[:n+1]), forceload)
  File "/usr/lib/python3.8/pydoc.py", line 362, in safeimport
    raise ErrorDuringImport(path, sys.exc_info())
pydoc.ErrorDuringImport: problem in documents.tasks - ImportError: Unable to find zbar shared library
22:11:03 [Q] ERROR reincarnated worker Process-1:8 after death
22:11:03 [Q] INFO Process-1:10 ready for work at 1263

Full addon config
Default config nothing changed
System

Supervisor version: supervisor-2022.04.0
Host system version: Home Assistant OS 7.6

Hi thanks for the report. This issue is identified in the upstream image and the change will be merged here as soon as it is done : https://github.com/linuxserver/docker-paperless-ngx/issues/10

Awesome thanks

They have merged the PR but no release yet we need to wait a bit more


Offer stable access to stacktrace call stack

StackTraces are used by various logging packages to print the class name and/or method name from which a log originates. This is currently solved by ad hoc parsing of StackTrace toString() results, e.g.,
https://github.com/magillus/flutter-fimber/blob/master/fimber/lib/fimber_base.dart#L242
I suggest that StrackTrace introduce a first-class, structured representation of the stack trace instead of an implied protocol in toString().
Relying on toString() introduces the following issues:

every developer needs to re-implement the parsing logic (which also requires a complete understanding of the variety of stack traces that might be produced)
toString() does not imply stable return values, it could conceivably change at any time

It's definitely an SDK question, we don't want to specify the stack trace format in the language specification (for all the reasons Matan has mentioned, mainly that we want to just use native stack traces when compiling to JavaScript and other potential future native platforms).
Parsing the stack trace to figure out who called you is a kind of reflection, so I'm OK with that costing extra for the code doing so, and not adding the cost to other code which just propagates a stack trace and eventually prints it.
It's quite possible for the VM to add extra functionality to native stack traces, like iterating them, but that's also going to be a reflection and/or debugging-like operation, and definitely not something that is available cross-platform. I'd personally rather spend their developer resources on something which benefits all Dart users :smile:.

Thanks for the replies. I've filed the following issue in the SDK repo:
https://github.com/dart-lang/sdk/issues/42927
I'm going to close this issue because it sounds like there is nothing more to do on the language front. If there is any internal tracking reason to leave this open then please feel free to re-open.


Add figures/plots to expected output.

Update Expected output with Figures for next release.

started contributing to this, but needs more work


Runtime error Godot with Firebase-UI 4.3.0

Godot version:
3.0.6 Stable
Issue description:
Hi all, I am little desperate and looking for any advice right now. I am working on my Godot 3.0.6 based android mobile game. As I created some Android modules I am compiling Godot myself. So far I was able to handle all the issues and application worked fine on test mobile device. However when I tried to add module that is using Firebase-UI 4.3.0 application is failing when I try to use functions connected to this library.
In application I have custom android three modules:

GPS handling - simple Java
Firebase DB - working with firebase database/firestore
FirebaseAuth - working with mentioned Firebase-UI 4.3.0

Both first two modules are working nicely without any problems. Firebase auth module is however not working correctly. I want to support Google, Facebook and simple Email sign options. Google and Facebook login methods are working but simple email one is not. When I click on "Login with email" option in generated UI of Firebase-UI module app just dumps with following errors.
java.lang.RuntimeException: Unable to start activity ComponentInfo{org.godotengine.bacterio/com.firebase.ui.auth.ui.email.EmailActivity}: android.view.InflateException: Binary XML file line #34: Binary XML file line #34: Error inflating class android.support.design.widget.TextInputLayout
Caused by: android.view.InflateException: Binary XML file line #34: Binary XML file line #34: Error inflating class android.support.design.widget.TextInputLayout
Caused by: android.view.InflateException: Binary XML file line #34: Error inflating class android.support.design.widget.TextInputLayout
Caused by: android.content.res.Resources$NotFoundException: Drawable org.godotengine.godot:drawable/design_password_eye with resource ID #0x7f07008f
Caused by: android.content.res.Resources$NotFoundException: File res/drawable-v21/design_password_eye.xml from drawable resource ID #0x7f07008f
I am not able to understand what is causing this. Small test app that I have created in Androd Studio (simple activity - no godot parts) is working correctly with all three login options. All dependencies in gradle.build file are same and also is the coding.
I have searched whole google already. I have tried different versions of com.android.support.* libreries like 27.1.1, I have tried different complie SDK versions, I have tried different Gradle versions etc.
Following are the gradle build file and manifest file of application
build.gradle.txt
AndroidManifest.xml.txt
I though the resources were not added to apk correctly when multiDex was used togather with Godot but after checking generated APK resources.arsc file and folder i can see ones mentioned in error. So I am not sure if resources are real problem here or not

My only tought is that it could be connected how Godot handles resources or well I dont know. Is here anyone that used Firebase-UI successfully with Godot. Or any tips would be deeply appricieted as in Godot and mobile development I am newbee.
Thank you guys in advance.

For anyone having this issue I was able to solve it. You can find how here adn what was the root cause full issue topic .
Quick info how I did it:
In my  java module I have created res/layout folder. I have created copies of 4 layouts that FirebaseUI 4.3.1 uses when working with email signin (this is version dependent so they can differ for you). In my case these were:
fui_forgot_password_layout.xml, fui_check_email_layout.xml, fui_register_email_layout.xml, fui_register_email_layout.xml
In each of these files wherever there was <android.support.design.widget.TextInputLayout> used I have added this property app:passwordToggleDrawable="@null" and for password fields I have also removed app:passwordToggleEnabled="true". This is example of TextInputLayout after changes:
                android:id="@+id/password_layout"
<EMAIL_ADDRESS>                android:layout_width="match_parent"
                android:layout_height="wrap_content"
                android:layout_marginTop="@dimen/fui_field_padding_vert"
                app:layout_constraintTop_toBottomOf="@+id/welcome_back_password_body"
				app:passwordToggleDrawable="@null">

                <android.support.design.widget.TextInputEditText
                    android:id="@+id/password"
<EMAIL_ADDRESS>/>

            </android.support.design.widget.TextInputLayout>


expose consolidateBy to finders

consolidateBy has been added as a node property.

wow! very nice! so now in fetch_multi we can just look at this node property. nice job AJ!


Data generation code

Is the data generation code available anywhere? I couldn't find it in the repository.

The data generation code is not released, but you can find a MATLAB version of the forward modeling code at this link. Our code exactly follows this MATLAB code and translates it to Python. The parameters of the MATLAB code should be used.
nz=70; nx=70;
dx=10; nbc=120; nt=1001; dt=0.001;
freq=15; s=ricker(freq,dt); isFS=false;
coord.sx = 1dx; coord.sz = 1dx;
coord.gx=(1:nx)*dx; coord.gz=ones(size(coord.gx))*dx;

I see, I was actually more interested in the code that creates the velocity models. A shame it wasn't released. But knowing the forward modeling is helpful nonetheless. Thanks for the info.


Proptypes issues with new RN 48

After i upgraded react native to last version, react-native-keyboard-spacer started to crash application because after react changes Proptypes is now can not be imported from react directly. You need install another package as described here https://facebook.github.io/react/blog/2017/04/07/react-v15.5.0.html. I was able to fix it by changing package files directly, but it is bad idea for a lot of reasons

fixed this issue by editing KeyboardSpacer.js
import React, { Component } from 'react'; import PropTypes from 'prop-types';

@hackerhgl  PR?

 Luckily it's just one file, i took it out and added it to my own components folder. Alternatively we could fork it, merge all PR

@Andr3wHur5t please merge PRs and make new release. If you don't want to maintance this repo, just give rights to someone else.

I apologize if my response time is slow.
Every PR is tested with multiple versions of react native to see what minimal supported version is to consider all the apps which use this that haven’t upgraded; breaking existing apps rather than upgraded ones (which haven’t released) would be bad also.
I would love to have automated tests to streamline this process but it has proven difficult with the feature support (such as hardware keyboards). As such I do manual testing which takes time.
As for adding another maintainer I’m open to this assuming they consider down stream consequences (requests welcome); but as of yet no one has offered.
I’ve recently pushed a out which works on the most recent version of RN. If you are still seeing this issue please post a repro so I can verify.


[Package Issue]: x86 URL in Wondershare.PDFelement.8 and Wondershare.PDFelement.9 returns 404 code

Please confirm these before moving forward

[X] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
[X] I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue
Installation issue.
Brief description of your issue
@coolplaylinbot 's recently automatic scanning there has found that these versions of Wondershare.PDFelement.8 returns 404 code in x86. But the x64 is still available now.

For this package you can simply replace the unavailable one by another as the installers of the two arches are actually the same.

I current do not have much more time to do this.
CC @stephengillie @Trenly

I current do not have much more time to do this.
CC @stephengillie @Trenly

"Do what you can, with what you have, where you are." - Theodore Roosevelt


Gt Ore support

Add GT Shard Ores to the the Ore Destruction Curcible recipes
fix https://github.com/GTNewHorizons/GT-New-Horizons-Modpack/issues/9789


Install ROS on a VirtualBox

https://www.youtube.com/watch?v=PvjwhBqZkVM

Using Vagrant is enough


fix TensorMask ->PILBase create

add TensroMask case for PILBase.create method

Careful, you're missing an if at the beginning of your statement ;)

Je suis désolé !

Thanks!

there was a typo


Added new service(s) to cancel sales order item.

Implemented: Added a new service cancel#SalesOrderItem to cancel an order item in OFBiz and other related in-line services.
Implementation Document link: https://github.com/saastechacademy/foundation/blob/main/project-ideas/order-ledger/cancelSalesOrder.md

Closing this MR as it is created using a different account.


Fallback to BSD md5(1)

Fixes #289

@aespinosa I'm worried about cross-shell compatibility here.  I think we may be safer if we check the return code from the first run of md5sum in ruby, and try "md5" if it's nonzero.

Hi @jkeiser
Ok, I'll make the shell check after reading the transport api a bit.

@jkeiser How does this look now?
According to my tests on FreeBSD, exitstatus is 1 for csh and 127 for sh

ping @jkeiser . let's hack on this tomorrow.

Grar, I didn't get back to this as soon as I'd have liked :(  This looks good now, merging!

Merged as 8b0e3a2


🐛 Bug Report: Cannot host catalog on S3, nor get Techdocs on S3

📜 Description
We are currently struggling with Backstage Software Catalog on S3
we have both configurations pointing to S3, for techdocs and for catalog:
On the S3 root, we have a catalog-info.yaml file and a /docs folder with htlm rendered mkdocs
techdocs:
  builder: external # Alternatives - 'local'
  generator:
    runIn: 'local' # Alternatives - 'local'
  publisher:
    type: awsS3 # Alternatives - 'googleGcs' or 'local'. Read documentation for using alternatives.
    awsS3:
      bucketName: xx
      region: xx
      endpoint: xx
      s3ForcePathStyle: true
      credentials:
        accessKeyId: ${S3_ACCESS_KEY_ID}
        secretAccessKey: ${S3_SECRET_ACCESS_KEY}
catalog:
  providers:
    awsS3:
      bucketName: xx
      region: xx
      endpoint: xx
      s3ForcePathStyle: true
      credentials:
        accessKeyId: ${S3_ACCESS_KEY_ID}
        secretAccessKey: ${S3_SECRET_ACCESS_KEY}
      schedule: # optional; same options as in TaskScheduleDefinition
        # supports cron, ISO duration, "human duration" as used in code
        frequency: { minutes: 30 }
        # supports ISO duration, "human duration" as used in code
        timeout: { minutes: 3 }

catalog-info.yaml is at the root of the S3 bucket
apiVersion: backstage.io/v1alpha1
kind: Component
metadata:
  name: component-name
  description: |
    Build and run your Apps
  links:
    - title: Website
      url: https://www.site.com
    - title: Documentation
      url: https://documentation.com/
  annotations:
    backstage.io/techdocs-ref: dir:./docs
spec:
  type: tool
  owner: owner
  lifecycle: production

👍 Expected behavior
The software catalog should appear on our backstage webApp, with the corresponding techdoc
👎 Actual Behavior with Screenshots
Connection to the S3 bucket is OK:
│ {"level":"info","message":"Successfully connected to the AWS S3 bucket xxxxxx.","plugin":"techdocs","service":"backstage","type":"plugin"}
and actually there's no component in our catalog
All components (0)
👟 Reproduction steps
Install backstage from the default helm template, and configure access to an S3 bucket as described above.
📃 Provide the context for the Bug.
We failed to find a complete doc for S3 based Software catalog, or missed it. Did we miss something?
🖥 Your Environment
Browser: Firefox, is it relevant in that context?
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
No, but I'm happy to collaborate on a PR with someone else

Hi @Vinzz, I have a few questions for you that will help me out get you some answers. First you say "Install backstage from the default helm template" in your steps to reproduce, can you confirm that you also ran npx @backstage/create-app@latest to create your Backstage instance and then built a docker image from that? If you did did you also add the code changes mentioned here that you would make to your catalog.ts file? https://backstage.io/docs/integrations/aws-s3/discovery/#:~:text=backend/src/plugins/-,catalog.ts,-%3A
One part of this that I can answer right now is that this is not how TechDocs is intended to work with S3. To make that work you should be generating and publishing the content using the TechDocs CLI - https://backstage.io/docs/features/techdocs/cli.
Once I hear back from you I'll be able to help more 👍

Hi @awanlin, thanks for your answer,
We used this helm chart, following this documentation
Not sure about the npx @backstage/create-app@latest command, shall we run it from inside the backstage container?
As for the doc publication, if i'm now corrected, we'll have to make a call to techdocs-cli publish --publisher-type awsS3 at the end of our gitlab CI job, once the doc is constructed, right?
thanks!

@awanlin Good news, with techdocs-cli publish we managed to publish our doc on S3, thanks for the hint
Do you have a tip on how to store the catalog definition on S3?

Hi @Vinzz, thanks for the follow up. I think to start it's important to mention that Backstage is a code first framework for creating an Internal Developer Portal which means you need to run npx @backstage/create-app@latest to create your Backstage instance and then build it as a docker image to run. I highly recommend you read through the Getting Started guide as it will help you with this context: https://backstage.io/docs/getting-started/
As for getting S3 to work you will need to make some minor code changes to your created Backstage instance to get it working for you. The documentation is pretty clear on the changes that you need to make: https://backstage.io/docs/integrations/aws-s3/discovery

thanks @awanlin , so your advice is to install with nox(m) rather than using helm charts and docker images?

 My advice is to use the output from npx @backstage/create-app@latest to use as the base for your docker image and then use the helm chart to deploy that. Does that make sense?

ok, it's no clear, thanks @awanlin !

Awesome! Do you think we can close this issue then?

yes indeed


Fix monitoring-plugin on podman

What type of PR is this?
bug
What this PR does / Why we need it?
This fixes a bug where if ce.putFileToMount encountered an error, it wouldn't be passed through. This resulted in a situation where the monitoring plugin wouldn't start, but no error would be passed (even with debug).
It also fixes the root bug that was causing ce.putFileToMount to fail. The podman machine ssh command requires the name of the machine you are SSH'ing into to be specified if you are putting an in-line command command.
Which Jira/Github issue(s) does this PR fix?
Resolves #
Special notes for your reviewer
Pre-checks (if applicable)

[x] Ran unit tests locally
[x] Validated the changes in a cluster
[x] Included documentation changes with PR

Codecov Report
Attention: Patch coverage is 33.33333% with 2 lines in your changes are missing coverage. Please review.

Project coverage is 44.19%. Comparing base (7340d42) to head (4224117).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #357      +/-   ##
==========================================
+ Coverage   44.18%   44.19%   +0.01%
==========================================
  Files          54       54
  Lines        4117     4116       -1
==========================================
  Hits         1819     1819
+ Misses       2033     2032       -1
  Partials      265      265

Files
Coverage Δ

cmd/ocm-backplane/console/console.go
23.31% <33.33%> (+0.03%)
:arrow_up:

/lgtm


[mistake-fix][ui]fix the letter case mistake

#3722
Last time, I made a letter case error that prevented the UI from triggering the change password request.

I wrote it as 'userinfo'
It should be 'userInfo'

I'm sorry for my mistake
上次提交的pr,我犯了一个字母大小写的错误,导致前端无法正常提交修改密码请求
本应该是'userInfo',我在提交时写成了'userinfo'
为我的过失表示抱歉

Please change title to [Fix][ui]fix the letter case mistake.


Sequence feature vs gene

I know we discussed this, but it seems that the molecules are split between these two classes.  If they are redundant, then we should only have one.

I think that the materialization of the asserted sequence feature subClassOf axioms is an artifact of how I'm generating the neuron-development file since all those classes also have an asserted subClassOf gene axiom as well. Thus the sequence feature is redundant since gene's are subClassOf sequence feature. I didn't prioritize fixing this because the inferred hierarchy places them all under gene.


(IAC-383) Fixed Logging and monitoring in a K8s 1.22 deployment

Fixed Logging and monitoring in a K8s 1.22 deployment.:

Updated the annotations required for logging and monitoring to work with K8s v1.22

Test coverage:

Verified the changes on Azure with

K8s v1.22.4 and INGRESS_NGINX_CHART_VERSION: 4.0.13
K8s v1.19.13 and INGRESS_NGINX_CHART_VERSION: 3.20.1

Verified the changes on GCP with

K8s 1.22.3-gke.700 with INGRESS_NGINX_CHART_VERSION: 4.0.13

Do these changes work with both ingress-ngnix v0.4.3 and v1.1.0? Checking because if these are merged into main it will break folks using the older version. If they are breaking changes. We'll have to set aside some time to do the release and sync things.

Yes this changes work for both k8s v1.19 (the default) with INGRESS_NGINX_CHART_VERSION: 3.20.1
and k8s v1.22 with INGRESS_NGINX_CHART_VERSION: 4.0.13

Did you do a squash and merge or just a merge? When you do the final merge into main the process was to squash and merge items to keep the push history clean. If needed you can alter based on your processes.

Also be sure to delete the working branches when the final merge takes place.

Did you do a squash and merge or just a merge? When you do the final merge into main the process was to squash and merge items to keep the push history clean. If needed you can alter based on your processes.

I think I just used merge. Will squash and merge here after.


Needs to remove sso-idp-config.xml which was previously used for dashboard related cluster configurations

Environment
IS 5.10.0 beta 2 node cluster deployment
DB Mysql 5.7
While setting up a 2 node cluster deployment observed that the following file which we use to do previous dashboard configurations is still available in the IS 5.10.0 beta pack.
IS_HOME>/repository/conf/identity/sso-idp-config.xml
According to new user portal implementation when setting up a cluster we do not need to do any configuration in the above file. Therefore it would be better to remove this file if we are no longer using this file.

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


task generate:struct2interface is broken because of examples/infra/redis/kod_gen_interface.go

$ task generate:struct2interface
task: Task "install:mockgen" is up to date
task: [generate:struct2interface] go run ./cmd/kod struct2interface .
2024/06/08 08:30:42 Loading input failed: examples/infra/redis/kod_gen_interface.go:11:8: failed parsing returns: examples/infra/redis/kod_gen_interface.go:11:12: unknown package "redis"
panic: mockgen error: exit status 1

goroutine 1 [running]:
github.com/samber/lo.must({0x7b1d80, 0xc000417610}, {0x0, 0x0, 0x0})
	/home/whatever/go/pkg/mod/github.com/samber/lo@v1.39.0/errors.go:53 +0x1df
github.com/samber/lo.Must0(...)
	/home/whatever/go/pkg/mod/github.com/samber/lo@v1.39.0/errors.go:72
github.com/go-kod/kod/cmd/kod/internal.init.func4(0xb8a660, {0xc000032420?, 0x4?, 0x81a17c?})
	/home/whatever/Documents/dev/perso/kod/cmd/kod/internal/struct2interface.go:379 +0xa9
github.com/spf13/cobra.(*Command).execute(0xb8a660, {0xc0000323e0, 0x1, 0x1})
	/home/whatever/go/pkg/mod/github.com/spf13/cobra@v1.8.0/command.go:987 +0xab1
github.com/spf13/cobra.(*Command).ExecuteC(0xb8a380)
	/home/whatever/go/pkg/mod/github.com/spf13/cobra@v1.8.0/command.go:1115 +0x3ff
github.com/spf13/cobra.(*Command).Execute(...)
	/home/whatever/go/pkg/mod/github.com/spf13/cobra@v1.8.0/command.go:1039
github.com/go-kod/kod/cmd/kod/internal.Execute()
	/home/whatever/Documents/dev/perso/kod/cmd/kod/internal/root.go:33 +0x1a
main.main()
	/home/whatever/Documents/dev/perso/kod/cmd/kod/main.go:6 +0xf
exit status 2
task: Failed to run task "generate:struct2interface": exit status 1

infra/redis package imports "github.com/redis/go-redis/v9"
but Go reports the file as missing, calling task mod doesn't solve issue

I think "github.com/redis/go-redis/v9" usually imported as redis conflicts somehow with the infra/redis package

maybe this kind of conflict should be detected by kod ?


Update to tree-sitter-cli 0.19.1

((program . (comment) @include)
 (#match? @include "^;\ +inherits\ *:"))

makes problems with 0.19.1

Is the new rust stuff needed for the update?


Issues on the 26th?

I just wanted to check in if there were any issues on the 26th of February (yesterday), that could have caused photos not to show up? Just making sure if it was an issue from my end or if something  actually happened on your end.
Thanks!

I do see some spikes and flip-flops towards AMS-IX on the 26th and the 27th. Our provider mentions upgrades on some of the core routers in AMS-IX on these dates. While the traffic was re-routed, I do see that the link to Cloudflare's POP in AMS behaved somewhat strange (reconnected a few times), links to other Cloudflare POP's were unaffected.
But there has been no change in load, traffic or errors, and response times were stable.

Thank you so much for taking the time to check it out and the detailed answer, very much appreciated! Based on this, it looks more like an issue from my end.
Thanks again!


Read value object from transform context as org.apache.avro.generic.GenericRecord only

Addressed feedback for the preview (#4):

Remove the code that maps the object value from the transform context as GenericAvroRecord
Avoid using optional class members on the FlattenStep
Add unit tests for thrown exception

Did minor suggestions.
LGTM 👍


Create github.md

Useful github commands.

Description

Resolves #issue

Verification

[ ]

Resources

@MoizLokh Ready for review!


Specify the minimum required Node version in the package.json files

https://docs.npmjs.com/files/package.json#engines

Ideally, we test our quickstarts in Travis with specific Node versions.

Fixed with 3a498917275dc9d27a6e6464367441e8f0393539.


[SymbolGraph] [5.3] Pick best synthesized member when possible

A type can have multiple overloads available from different protocols from
which it inherits. Ask the type checker to pick the best one where possible.
rdar://60193198

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test

Build failed
Swift Test OS X Platform
Git Sha - d77b76f168b7ca74df4e3a78cdfaa8d6f39e68db


[Doc] Fix the Themes section

Following the change of API for more stateless component.

@subjectix Could you review? Feel free to merge.

@oliviertassinari All seems good :+1: :+1:


Report only shows data for TPC since 2023-10-14

The reporting system only includes data for the TPC-H related tests since 2023-10-14. We stopped showing (persisting/recording?) data for all other tests.

There are 2 different plots no, one before renaming the directory and one after

There are 2 different plots no, one before renaming the directory and one after

That's #1098.

Closed as completed by #1101


[On-boarding]: dashboards-flow-framework plugin

What is the name of your plugin?
dashboards-flow-framework
What is the link to your GitHub repo?
https://github.com/opensearch-project/dashboards-flow-framework
Targeted release version
2.17
Does the plugin require documentation?
Yes
What type of the plugin are we on-boarding?
OpenSearch-dashboards plugin
Did you read the on-boarding document?
yes
Does this plugin has all the necessary automated tests?
Not yet
Have you completed the required reviews including Security reviews, UX reviews?
In progress
Have you on-boarded automated security scanning for the GitHub repo associated with this plugin?
yes
Additional context
CC: Tyler Ohlsen @ohltyler

Todo:
Add release notes in the plugin
Add tests in opensearch-dashboards-functional-test
Add documentation. Need to contact the documentation team

Also the plugin id should be flowFrameworkDashboards.
Thanks.

Hi @saimedhi
Looks like security review for this plugin was in progress. Is there any update on this?
Thanks!

Hello @gaiksaya, Starting 26th Aug (Monday) and throughout the week, @ohltyler and I will add Add tests in opensearch-dashboards-functional-test
We will also add release notes and essential documentation.
Does this timeline work @gaiksaya ?   And also did we miss something. Please let us know. Thank you.

cc: @ohltyler

Hi @ohltyler @saimedhi,
Can you update the status of the plugin here? Are we still targeting 2.17?

Hi @ohltyler @saimedhi, Can you update the status of the plugin here? Are we still targeting 2.17?

@gaiksaya, we are targeting 2.18. Thank you. Let me know if anything needs to be done by me.


Add vertex post-processing function

Sometimes it's necessary to, for example, draw lines on a flat surface and then project those into three dimensions after line vertex computation. It seems necessary to add a post-processing pragma for the vertex shader. This is easy to implement but just want to think it over before adding.

Added as postproject, together with render-time viewportSize which allows rendering to the correct corresponding viewport size.

Published in v2.1.0


Deploy as (distroless) image

Add trivy scanner as well into pipeline:

Added Dockerfile (using chainguard distroless node image) and docs, container image scan using trivy: https://github.com/secureIO-GmbH/VulnerabilityHeatmap/actions/runs/7384910144/job/20088662720
Closing.

Scan results will be uploaded as json: https://github.com/secureIO-GmbH/VulnerabilityHeatmap/actions/runs/7387131430


[virtual tour] after finish the tour, wrong z-index

Current status
After end of virtual tour we have z-index issue

System GA

Update virtual-tour to v1.1.4 and indigo-layout to v1.7.6

testing: if the element not exists, the tour should be on the center.


Add ThirtyInch to values

I want to add ThirtyInch to AboutLibraries.
To be honest.  I have really no clue how your lib work and if everything is correct. I don't really understand the wiki...
Whatever.
The only thing I want to reach is:
If ThirtyInch is "autodetected" (via classPath I guess) it should be available in the "libraries section"...
I hope everything is set up correctly for that 👍

@StefMa well the main idea was that the developer includes the string in his library, and the aboutlibraries will find that automatically. As this did not happen to frequently most definition files got included in this lib.
These contain the classPath which allows me to check if a class exists or not, if it is there the lib is included ---> proguard will preven this.
In the worst case you can still define the libs you want to see during creation of the LibsBuilder

OK. Thank you for the information.
Does aboutLibraries works, if I add the strings to our ThirtyInch project? Then I would include it in our library instead in this one. I think it will be easier to maintain...
Another question
Is the library_thirtyinch_strings.xml correct? If I would copy it in our lib, would AboutLibrary recognize our lib?
What is define_int_ThirtyInch?
We don't include ThirtyInch or AboutLibraries in Ti. So we don't have to define define_ThirtyInch but define_int_ThirtyInch, right? 🤔

@StefMa exactly the only difference you have to make ist to remove the int
I do the same for example herE: https://github.com/mikepenz/FastAdapter/blob/develop/library-core/src/main/res/values/library_fastadapter_strings.xml
Yes it looks correct as of how it looks.
well the define_int or define_ string is used by the AboutLibraries library to check if the resource is coming from the  AboutLibraries itself, so it is not yet allowed to show it, only if the classPath results in a result.
if the define_ is found without the int it know that the resource is coming from a library and directly shows it without further checks

I have tested it, but it don't work.
See this PR https://github.com/StefMa/ThirtyInch/pull/1/files
The list is just empty :(
What I'm doing wrong?

I will have to look at it, but can't do this right now.
Do you have anything in the build which might remove the resource file?

Ahh thank you!
Yes, in the test sample we use proGuard. It have removed the unused resources. Of course...
I've fixed it now 👍 It works if I disabling the removing with -keep public class **.R$string

@StefMa can you please try if:
-keepclasseswithmembers class **.R$* {
    public static final int define_*;
}

would be enough too?

Yep, that is enough.
Thank you for your help 👍

You are welcome :)
Thanks for integrating it ;)


[libffi] x64-windows/msys build failure Win 10

libffi build failure on Windows (x64-windows) using vcpkg: Unexpected token in configure script
Operating system
Windows 10
Compiler
x64-windows/msys
Steps to reproduce the behavior

Run vcpkg install libffi:x64-windows
Observe the build failure during the configuration stage

Error Output
From config-x64-windows-dbg-err.log:
/C/Users/[user]: line 1: syntax error near unexpected token `('
/C/Users/[user]: line 1: `[42DC:4AA4][2023-11-14T14:20:58]i001: Burn v<IP_ADDRESS>18, Windows v10.0 (Build 19045: Service Pack 0), path: C:\Windows\Temp\{33307A31-6BB0-47F8-9FBC-B9000BF55454}\.cr\VC_redist.x64.exe'

From config-x64-windows-dbg-out.log:
configure: loading site script /C/Users/[user]

Full Logs

config-x64-windows-dbg-config.log

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by libffi configure 3.4.6, which was
generated by GNU Autoconf 2.71.  Invocation command line was
$ ./../src/libffi-3-5867c437e9.clean/configure --build=x86_64-pc-mingw32 --enable-portable-binary --disable-docs --disable-multi-os-directory 'CFLAGS=-Xcompiler -nologo -Xcompiler -utf-8 -Xcompiler -MP -Xcompiler -MDd -Xcompiler -Z7 -Xcompiler -Ob0 -Xcompiler -Od -Xcompiler -RTC1 -DFFI_BUILDING_DLL' 'CCAS=msvcc.sh -m64' ac_cv_prog_ac_ct_STRIP=: gl_cv_double_slash_root=yes ac_cv_func_memmove=yes --disable-silent-rules --verbose --enable-shared --disable-static '--prefix=/C/Users/[user]/vcpkg/installed/x64-windows/debug' '--bindir=${prefix}/../tools/libffi/debug/bin' '--sbindir=${prefix}/../tools/libffi/debug/sbin' '--libdir=${prefix}/lib' '--includedir=${prefix}/../include' '--datarootdir=${prefix}/share/libffi'
---------
Platform.
---------
hostname = B332P13_DESKTOP
uname -m = x86_64
uname -r = 3.5.3.x86_64
uname -s = MSYS_NT-10.0-19045
uname -v = 2024-05-20 12:06 UTC
/usr/bin/uname -p = unknown
/bin/uname -X     = unknown
/bin/arch              = x86_64
/usr/bin/arch -k       = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo      = unknown
/bin/machine           = unknown
/usr/bin/oslevel       = unknown
/bin/universe          = unknown
PATH: /c/Program Files (x86)/Windows Kits/10/bin/10.0.22621.0/x64/
PATH: /c/Program Files (x86)/Microsoft Visual Studio/2022/BuildTools/VC/Tools/MSVC/14.38.33130/bin/Hostx64/x64/
PATH: /c/Program Files (x86)/Microsoft Visual Studio/2022/BuildTools/VC/Tools/MSVC/14.38.33130/bin/Hostx64/x64/
PATH: /c/Program Files (x86)/Microsoft Visual Studio/2022/BuildTools/VC/Tools/MSVC/14.38.33130/bin/HostX64/x64/
PATH: /c/Program Files (x86)/Microsoft Visual Studio/2022/BuildTools/Common7/IDE/VC/VCPackages/
PATH: /c/Program Files (x86)/Microsoft Visual Studio/2022/BuildTools/Common7/IDE/CommonExtensions/Microsoft/TestWindow/
PATH: /c/Program Files (x86)/Microsoft Visual Studio/2022/BuildTools/MSBuild/Current/bin/Roslyn/
PATH: /c/Program Files (x86)/Microsoft SDKs/Windows/v10.0A/bin/NETFX 4.8 Tools/x64/
PATH: /c/Program Files (x86)/Windows Kits/10/bin/10.0.22621.0/x64/
PATH: /c/Program Files (x86)/Windows Kits/10/bin/x64/
PATH: /c/Program Files (x86)/Microsoft Visual Studio/2022/BuildTools/MSBuild/Current/Bin/amd64/
PATH: /c/Windows/Microsoft.NET/Framework64/v4.0.30319/
PATH: /c/Program Files (x86)/Microsoft Visual Studio/2022/BuildTools/Common7/IDE/
PATH: /c/Program Files (x86)/Microsoft Visual Studio/2022/BuildTools/Common7/Tools/
PATH: /c/Users/[user]/vcpkg/downloads/tools/powershell-core-7.2.21-windows/
PATH: /c/Users/[user]/vcpkg/scripts/buildsystems/make_wrapper/
PATH: /usr/share/automake-1.16/
PATH: /usr/bin/
PATH: /c/Windows/system32/
PATH: /c/Windows/
PATH: /c/Windows/system32/Wbem/
PATH: /c/Windows/system32/WindowsPowerShell/v1.0/
PATH: /c/Program Files (x86)/Microsoft Visual Studio/2022/BuildTools/Common7/IDE/CommonExtensions/Microsoft/CMake/CMake/bin/
PATH: /c/Program Files (x86)/Microsoft Visual Studio/2022/BuildTools/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/
PATH: /c/Program Files (x86)/Microsoft Visual Studio/2022/BuildTools/Common7/IDE/VC/Linux/bin/ConnectionManagerExe/
PATH: /c/Program Files (x86)/Microsoft Visual Studio/2022/BuildTools/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/
PATH: /c/Users/[user]/vcpkg/buildtrees/libffi/src/libffi-3-5867c437e9.clean/
PATH: /c/Program Files (x86)/Microsoft Visual Studio/2022/BuildTools/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/
PATH: /c/Users/[user]/vcpkg/downloads/tools/msys2/1e74ca60daa10104/mingw64/bin/
-----------
Core tests.
-----------
configure:2440: loading site script /C/Users/[user]
| [42DC:4AA4][2023-11-14T14:20:58]i001: Burn v<IP_ADDRESS>18, Windows v10.0 (Build 19045: Service Pack 0), path: C:\Windows\Temp{33307A31-6BB0-47F8-9FBC-B9000BF55454}.cr\VC_redist.x64.exe
| [42DC:4AA4][2023-11-14T14:20:58]i009: Command Line: '-burn.clean.room=C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.VisualCpp.Redist.14,version=14.38.33130,chip=x64\VC_redist.x64.exe -burn.filehandle.attached=688 -burn.filehandle.self=604 /q /norestart /log C:\Users[user]\AppData\Local\Temp\dd_setup_20231114141940_039_Microsoft.VisualCpp.Redist.14.log'
| [42DC:4AA4][2023-11-14T14:20:58]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.VisualCpp.Redist.14,version=14.38.33130,chip=x64\VC_redist.x64.exe'
| [42DC:4AA4][2023-11-14T14:20:58]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.VisualCpp.Redist.14,version=14.38.33130,chip=x64'
| [42DC:4AA4][2023-11-14T14:20:58]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\G'
| [42DC:4AA4][2023-11-14T14:20:58]i000: Setting string variable 'WixBundleName' to value 'Microsoft Visual C++ 2015-2022 Redistributable (x64) - 14.38.33130'
| [42DC:4AA4][2023-11-14T14:20:58]i000: Setting string variable 'WixBundleManufacturer' to value 'Microsoft Corporation'
| [42DC:46EC][2023-11-14T14:20:58]i000: Setting version variable 'WixBundleFileVersion' to value '14.38.33130.0'
| [42DC:4AA4][2023-11-14T14:20:58]i100: Detect begin, 11 packages
| [42DC:4AA4][2023-11-14T14:20:58]i000: Setting string variable 'Arm64_Check' to value 'AMD64'
| [42DC:4AA4][2023-11-14T14:20:58]i000: Setting version variable 'windows_uCRT_DetectKey' to value '10.0.19041.3570'
| [42DC:4AA4][2023-11-14T14:20:58]i000: Setting numeric variable 'windows_uCRT_DetectKeyExists' to value 1
| [42DC:4AA4][2023-11-14T14:20:58]i102: Detected related bundle: {8bdfe669-9705-4184-9368-db9ce581e0e7}, type: Upgrade, scope: PerMachine, version: 14.36.32532.0, operation: MajorUpgrade
| [42DC:4AA4][2023-11-14T14:20:58]i052: Condition '(VersionNT = v6.3 AND NOT VersionNT64) AND (windows_uCRT_DetectKeyExists AND windows_uCRT_DetectKey >= v10.0.10240.0)' evaluates to false.
| [42DC:4AA4][2023-11-14T14:20:58]i052: Condition '(VersionNT = v6.3 AND VersionNT64) AND (windows_uCRT_DetectKeyExists AND windows_uCRT_DetectKey >= v10.0.10240.0)' evaluates to false.
| [42DC:4AA4][2023-11-14T14:20:58]i052: Condition '(VersionNT = v6.2 AND NOT VersionNT64) AND (windows_uCRT_DetectKeyExists AND windows_uCRT_DetectKey >= v10.0.10240.0)' evaluates to false.
| [42DC:4AA4][2023-11-14T14:20:58]i052: Condition '(VersionNT = v6.2 AND VersionNT64) AND (windows_uCRT_DetectKeyExists AND windows_uCRT_DetectKey >= v10.0.10240.0)' evaluates to false.
| [42DC:4AA4][2023-11-14T14:20:58]i052: Condition '(VersionNT = v6.1 AND NOT VersionNT64) AND (windows_uCRT_DetectKeyExists AND windows_uCRT_DetectKey >= v10.0.10240.0)' evaluates to false.
| [42DC:4AA4][2023-11-14T14:20:58]i052: Condition '(VersionNT = v6.1 AND VersionNT64) AND (windows_uCRT_DetectKeyExists AND windows_uCRT_DetectKey >= v10.0.10240.0)' evaluates to false.
| [42DC:4AA4][2023-11-14T14:20:58]i052: Condition '(VersionNT = v6.0 AND NOT VersionNT64) AND (windows_uCRT_DetectKeyExists AND windows_uCRT_DetectKey >= v10.0.10240.0)' evaluates to false.
| [42DC:4AA4][2023-11-14T14:20:58]i052: Condition '(VersionNT = v6.0 AND VersionNT64) AND (windows_uCRT_DetectKeyExists AND windows_uCRT_DetectKey >= v10.0.10240.0)' evaluates to false.
| [42DC:4AA4][2023-11-14T14:20:58]i103: Detected related package: {D5D19E2F-7189-42FE-8103-92CD1FA457C2}, scope: PerMachine, version: 14.36.32532.0, language: 0 operation: MajorUpgrade
| [42DC:4AA4][2023-11-14T14:20:58]i103: Detected related package: {0025DD72-A959-45B5-A0A3-7EFEB15A8050}, scope: PerMachine, version: 14.36.32532.0, language: 0 operation: MajorUpgrade
| [42DC:4AA4][2023-11-14T14:20:58]i103: Detected related package: {D5D19E2F-7189-42FE-8103-92CD1FA457C2}, scope: PerMachine, version: 14.36.32532.0, language: 0 operation: MajorUpgrade
| [42DC:4AA4][2023-11-14T14:20:58]i103: Detected related package: {0025DD72-A959-45B5-A0A3-7EFEB15A8050}, scope: PerMachine, version: 14.36.32532.0, language: 0 operation: MajorUpgrade
| [42DC:4AA4][2023-11-14T14:20:58]i101: Detected package: Windows81_x86, state: Absent, cached: None
| [42DC:4AA4][2023-11-14T14:20:58]i101: Detected package: Windows81_x64, state: Absent, cached: None
| [42DC:4AA4][2023-11-14T14:20:58]i101: Detected package: Windows8_x86, state: Absent, cached: None
| [42DC:4AA4][2023-11-14T14:20:58]i101: Detected package: Windows8_x64, state: Absent, cached: None
| [42DC:4AA4][2023-11-14T14:20:58]i101: Detected package: Windows7_MSU_x86, state: Absent, cached: None
| [42DC:4AA4][2023-11-14T14:20:58]i101: Detected package: Windows7_MSU_x64, state: Absent, cached: None
| [42DC:4AA4][2023-11-14T14:20:58]i101: Detected package: WindowsVista_MSU_x86, state: Absent, cached: None
| [42DC:4AA4][2023-11-14T14:20:58]i101: Detected package: WindowsVista_MSU_x64, state: Absent, cached: None
| [42DC:4AA4][2023-11-14T14:20:58]i101: Detected package: vcRuntimeMinimum_x64, state: Absent, cached: None
| [42DC:4AA4][2023-11-14T14:20:58]i101: Detected package: vcRuntimeAdditional_x64, state: Absent, cached: None
| [42DC:4AA4][2023-11-14T14:20:58]i101: Detected package: vcRuntime_arm64, state: Absent, cached: None
| [42DC:4AA4][2023-11-14T14:20:58]i052: Condition 'VersionNT >= v6.1' evaluates to true.
| [42DC:4AA4][2023-11-14T14:20:58]i199: Detect complete, result: 0x0
| [42DC:4AA4][2023-11-14T14:20:58]i200: Plan begin, 11 packages, action: Install
| [42DC:4AA4][2023-11-14T14:20:58]i052: Condition 'VersionNT = v6.3 AND NOT VersionNT64' evaluates to false.
| [42DC:4AA4][2023-11-14T14:20:58]w321: Skipping dependency registration on package with no dependency providers: Windows81_x86
| [42DC:4AA4][2023-11-14T14:20:58]i052: Condition 'VersionNT = v6.3 AND VersionNT64' evaluates to false.
| [42DC:4AA4][2023-11-14T14:20:58]w321: Skipping dependency registration on package with no dependency providers: Windows81_x64
| [42DC:4AA4][2023-11-14T14:20:58]i052: Condition 'VersionNT = v6.2 AND NOT VersionNT64' evaluates to false.
| [42DC:4AA4][2023-11-14T14:20:58]w321: Skipping dependency registration on package with no dependency providers: Windows8_x86
| [42DC:4AA4][2023-11-14T14:20:58]i052: Condition 'VersionNT = v6.2 AND VersionNT64' evaluates to false.
| [42DC:4AA4][2023-11-14T14:20:58]w321: Skipping dependency registration on package with no dependency providers: Windows8_x64
| [42DC:4AA4][2023-11-14T14:20:58]i052: Condition 'VersionNT = v6.1 AND NOT VersionNT64' evaluates to false.
| [42DC:4AA4][2023-11-14T14:20:58]w321: Skipping dependency registration on package with no dependency providers: Windows7_MSU_x86
| [42DC:4AA4][2023-11-14T14:20:58]i052: Condition 'VersionNT = v6.1 AND VersionNT64' evaluates to false.
| [42DC:4AA4][2023-11-14T14:20:58]w321: Skipping dependency registration on package with no dependency providers: Windows7_MSU_x64
| [42DC:4AA4][2023-11-14T14:20:58]i052: Condition 'VersionNT = v6.0 AND NOT VersionNT64' evaluates to false.
| [42DC:4AA4][2023-11-14T14:20:58]w321: Skipping dependency registration on package with no dependency providers: WindowsVista_MSU_x86
| [42DC:4AA4][2023-11-14T14:20:58]i052: Condition 'VersionNT = v6.0 AND VersionNT64' evaluates to false.
| [42DC:4AA4][2023-11-14T14:20:58]w321: Skipping dependency registration on package with no dependency providers: WindowsVista_MSU_x64
| [42DC:4AA4][2023-11-14T14:20:58]i052: Condition '(VersionNT64) AND NOT (Arm64_Check = "ARM64")' evaluates to true.
| [42DC:4AA4][2023-11-14T14:20:58]i000: Setting string variable 'WixBundleRollbackLog_vcRuntimeMinimum_x64' to value 'C:\Users\G_000_vcRuntimeMinimum_x64_rollback.log'
| [42DC:4AA4][2023-11-14T14:20:58]i000: Setting string variable 'WixBundleLog_vcRuntimeMinimum_x64' to value 'C:\Users\G_000_vcRuntimeMinimum_x64.log'
| [42DC:4AA4][2023-11-14T14:20:58]i052: Condition '(VersionNT64) AND NOT (Arm64_Check = "ARM64")' evaluates to true.
| [42DC:4AA4][2023-11-14T14:20:58]i000: Setting string variable 'WixBundleRollbackLog_vcRuntimeAdditional_x64' to value 'C:\Users\G_001_vcRuntimeAdditional_x64_rollback.log'
| [42DC:4AA4][2023-11-14T14:20:58]i000: Setting string variable 'WixBundleLog_vcRuntimeAdditional_x64' to value 'C:\Users\G_001_vcRuntimeAdditional_x64.log'
| [42DC:4AA4][2023-11-14T14:20:58]i052: Condition 'Arm64_Check = "ARM64"' evaluates to false.
| [42DC:4AA4][2023-11-14T14:20:58]i201: Planned package: Windows81_x86, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None
| [42DC:4AA4][2023-11-14T14:20:58]i201: Planned package: Windows81_x64, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None
| [42DC:4AA4][2023-11-14T14:20:58]i201: Planned package: Windows8_x86, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None
| [42DC:4AA4][2023-11-14T14:20:58]i201: Planned package: Windows8_x64, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None
| [42DC:4AA4][2023-11-14T14:20:58]i201: Planned package: Windows7_MSU_x86, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None
| [42DC:4AA4][2023-11-14T14:20:58]i201: Planned package: Windows7_MSU_x64, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None
| [42DC:4AA4][2023-11-14T14:20:58]i201: Planned package: WindowsVista_MSU_x86, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None
| [42DC:4AA4][2023-11-14T14:20:58]i201: Planned package: WindowsVista_MSU_x64, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None
| [42DC:4AA4][2023-11-14T14:20:58]i201: Planned package: vcRuntimeMinimum_x64, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
| [42DC:4AA4][2023-11-14T14:20:58]i201: Planned package: vcRuntimeAdditional_x64, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
| [42DC:4AA4][2023-11-14T14:20:58]i201: Planned package: vcRuntime_arm64, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None
| [42DC:4AA4][2023-11-14T14:20:58]i207: Planned related bundle: {8bdfe669-9705-4184-9368-db9ce581e0e7}, type: Upgrade, default requested: Absent, ba requested: Absent, execute: Uninstall, rollback: Install, dependency: None
| [42DC:4AA4][2023-11-14T14:20:58]i299: Plan complete, result: 0x0
| [42DC:4AA4][2023-11-14T14:20:58]i300: Apply begin
| [42DC:4AA4][2023-11-14T14:20:58]i010: Launching elevated engine process.
| [42DC:4AA4][2023-11-14T14:20:59]i011: Launched elevated engine process.
| [42DC:4AA4][2023-11-14T14:20:59]i012: Connected to elevated engine.
| [46A0:0408][2023-11-14T14:20:59]i358: Pausing automatic updates.
| [46A0:0408][2023-11-14T14:20:59]i359: Paused automatic updates.
| [46A0:0408][2023-11-14T14:20:59]i360: Creating a system restore point.
| [46A0:0408][2023-11-14T14:20:59]w363: Could not create system restore point, error: 0x80070422. Continuing...
| [46A0:0408][2023-11-14T14:20:59]i370: Session begin, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{1de5e707-82da-4db6-b810-5d140cc4cbb3}, options: 0x7, disable resume: No
| [46A0:0408][2023-11-14T14:20:59]i000: Caching bundle from: 'C:\Windows\Temp{AEF1E815-E581-43FB-8199-F577A64C1358}.be\VC_redist.x64.exe' to: 'C:\ProgramData\Package Cache{1de5e707-82da-4db6-b810-5d140cc4cbb3}\VC_redist.x64.exe'
| [46A0:0408][2023-11-14T14:20:59]i320: Registering bundle dependency provider: VC,redist.x64,amd64,14.38,bundle, version: 14.38.33130.0
| [46A0:0408][2023-11-14T14:20:59]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{1de5e707-82da-4db6-b810-5d140cc4cbb3}, resume: Active, restart initiated: No, disable resume: No
| [46A0:46B0][2023-11-14T14:21:00]i305: Verified acquired payload: vcRuntimeMinimum_x64 at path: C:\ProgramData\Package Cache.unverified\vcRuntimeMinimum_x64, moving to: C:\ProgramData\Package Cache{1CA7421F-A225-4A9C-B320-A36981A2B789}v14.38.33130\packages\vcRuntimeMinimum_amd64\vc_runtimeMinimum_x64.msi.
| [46A0:46B0][2023-11-14T14:21:00]i305: Verified acquired payload: cab5046A8AB272BF37297BB7928664C9503 at path: C:\ProgramData\Package Cache.unverified\cab5046A8AB272BF37297BB7928664C9503, moving to: C:\ProgramData\Package Cache{1CA7421F-A225-4A9C-B320-A36981A2B789}v14.38.33130\packages\vcRuntimeMinimum_amd64\cab1.cab.
| [46A0:46B0][2023-11-14T14:21:00]i305: Verified acquired payload: vcRuntimeAdditional_x64 at path: C:\ProgramData\Package Cache.unverified\vcRuntimeAdditional_x64, moving to: C:\ProgramData\Package Cache{C31777DB-51C1-4B19-9F80-38EF5C1D7C89}v14.38.33130\packages\vcRuntimeAdditional_amd64\vc_runtimeAdditional_x64.msi.
| [46A0:46B0][2023-11-14T14:21:00]i305: Verified acquired payload: cab2C04DDC374BD96EB5C8EB8208F2C7C92 at path: C:\ProgramData\Package Cache.unverified\cab2C04DDC374BD96EB5C8EB8208F2C7C92, moving to: C:\ProgramData\Package Cache{C31777DB-51C1-4B19-9F80-38EF5C1D7C89}v14.38.33130\packages\vcRuntimeAdditional_amd64\cab1.cab.
| [46A0:0408][2023-11-14T14:21:00]i301: Applying execute package: vcRuntimeMinimum_x64, action: Install, path: C:\ProgramData\Package Cache{1CA7421F-A225-4A9C-B320-A36981A2B789}v14.38.33130\packages\vcRuntimeMinimum_amd64\vc_runtimeMinimum_x64.msi, arguments: ' MSIFASTINSTALL="7" NOVSUI="1"'
| [42DC:4AA4][2023-11-14T14:21:53]i319: Applied execute package: vcRuntimeMinimum_x64, result: 0x0, restart: Required
| [46A0:0408][2023-11-14T14:21:53]i325: Registering dependency: {1de5e707-82da-4db6-b810-5d140cc4cbb3} on package provider: Microsoft.VS.VC_RuntimeMinimumVSU_amd64,v14, package: vcRuntimeMinimum_x64
| [46A0:0408][2023-11-14T14:21:53]i301: Applying execute package: vcRuntimeAdditional_x64, action: Install, path: C:\ProgramData\Package Cache{C31777DB-51C1-4B19-9F80-38EF5C1D7C89}v14.38.33130\packages\vcRuntimeAdditional_amd64\vc_runtimeAdditional_x64.msi, arguments: ' MSIFASTINSTALL="7" NOVSUI="1"'
| [42DC:4AA4][2023-11-14T14:21:54]i319: Applied execute package: vcRuntimeAdditional_x64, result: 0x0, restart: None
| [46A0:0408][2023-11-14T14:21:54]i325: Registering dependency: {1de5e707-82da-4db6-b810-5d140cc4cbb3} on package provider: Microsoft.VS.VC_RuntimeAdditionalVSU_amd64,v14, package: vcRuntimeAdditional_x64
| [46A0:0408][2023-11-14T14:21:55]i301: Applying execute package: {8bdfe669-9705-4184-9368-db9ce581e0e7}, action: Uninstall, path: C:\ProgramData\Package Cache{8bdfe669-9705-4184-9368-db9ce581e0e7}\VC_redist.x64.exe, arguments: '"C:\ProgramData\Package Cache{8bdfe669-9705-4184-9368-db9ce581e0e7}\VC_redist.x64.exe" -uninstall -quiet -burn.related.upgrade -burn.ancestors={1de5e707-82da-4db6-b810-5d140cc4cbb3} -burn.filehandle.self=1180'
| [42DC:4AA4][2023-11-14T14:21:56]i319: Applied execute package: {8bdfe669-9705-4184-9368-db9ce581e0e7}, result: 0x0, restart: None
| [46A0:0408][2023-11-14T14:21:56]i372: Session end, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{1de5e707-82da-4db6-b810-5d140cc4cbb3}, resume: ARP, restart: Required, disable resume: No
| [46A0:0408][2023-11-14T14:21:56]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{1de5e707-82da-4db6-b810-5d140cc4cbb3}, resume: ARP, restart initiated: No, disable resume: No
| [42DC:4AA4][2023-11-14T14:21:56]i399: Apply complete, result: 0x0, restart: Required, ba requested restart:  No
| [42DC:4AA4][2023-11-14T14:21:56]i500: Shutting down, exit code: 0xbc2
| [42DC:4AA4][2023-11-14T14:21:56]i410: Variable: Arm64_Check = AMD64
| [42DC:4AA4][2023-11-14T14:21:56]i410: Variable: SystemFolder = C:\Windows\system32
| [42DC:4AA4][2023-11-14T14:21:56]i410: Variable: VersionNT = <IP_ADDRESS>
| [42DC:4AA4][2023-11-14T14:21:56]i410: Variable: VersionNT64 = <IP_ADDRESS>
| [42DC:4AA4][2023-11-14T14:21:56]i410: Variable: windows_uCRT_DetectKey = 10.0.19041.3570
| [42DC:4AA4][2023-11-14T14:21:56]i410: Variable: windows_uCRT_DetectKeyExists = 1
| [42DC:4AA4][2023-11-14T14:21:56]i410: Variable: WixBundleAction = 5
| [42DC:4AA4][2023-11-14T14:21:56]i410: Variable: WixBundleElevated = 1
| [42DC:4AA4][2023-11-14T14:21:56]i410: Variable: WixBundleFileVersion = 14.38.33130.0
| [42DC:4AA4][2023-11-14T14:21:56]i410: Variable: WixBundleInstalled = 0
| [42DC:4AA4][2023-11-14T14:21:56]i410: Variable: WixBundleLog = C:\Users\G
| [42DC:4AA4][2023-11-14T14:21:56]i410: Variable: WixBundleLog_vcRuntimeAdditional_x64 = C:\Users\G_001_vcRuntimeAdditional_x64.log
| [42DC:4AA4][2023-11-14T14:21:56]i410: Variable: WixBundleLog_vcRuntimeMinimum_x64 = C:\Users\G_000_vcRuntimeMinimum_x64.log
| [42DC:4AA4][2023-11-14T14:21:56]i410: Variable: WixBundleManufacturer = Microsoft Corporation
| [42DC:4AA4][2023-11-14T14:21:56]i410: Variable: WixBundleName = Microsoft Visual C++ 2015-2022 Redistributable (x64) - 14.38.33130
| [42DC:4AA4][2023-11-14T14:21:56]i410: Variable: WixBundleOriginalSource = C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.VisualCpp.Redist.14,version=14.38.33130,chip=x64\VC_redist.x64.exe
| [42DC:4AA4][2023-11-14T14:21:56]i410: Variable: WixBundleOriginalSourceFolder = C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.VisualCpp.Redist.14,version=14.38.33130,chip=x64
| [42DC:4AA4][2023-11-14T14:21:56]i410: Variable: WixBundleProviderKey = VC,redist.x64,amd64,14.38,bundle
| [42DC:4AA4][2023-11-14T14:21:56]i410: Variable: WixBundleRollbackLog_vcRuntimeAdditional_x64 = C:\Users\G_001_vcRuntimeAdditional_x64_rollback.log
| [42DC:4AA4][2023-11-14T14:21:56]i410: Variable: WixBundleRollbackLog_vcRuntimeMinimum_x64 = C:\Users\G_000_vcRuntimeMinimum_x64_rollback.log
| [42DC:4AA4][2023-11-14T14:21:56]i410: Variable: WixBundleSourceProcessFolder = C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.VisualCpp.Redist.14,version=14.38.33130,chip=x64
| [42DC:4AA4][2023-11-14T14:21:56]i410: Variable: WixBundleSourceProcessPath = C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.VisualCpp.Redist.14,version=14.38.33130,chip=x64\VC_redist.x64.exe
| [42DC:4AA4][2023-11-14T14:21:56]i410: Variable: WixBundleTag =
| [42DC:4AA4][2023-11-14T14:21:56]i410: Variable: WixBundleVersion = 14.38.33130.0
| [42DC:4AA4][2023-11-14T14:21:56]i007: Exit code: 0xbc2, restarting: No
----------------
Cache variables.
----------------
ac_cv_env_CCASFLAGS_set=
ac_cv_env_CCASFLAGS_value=
ac_cv_env_CCAS_set=set
ac_cv_env_CCAS_value='msvcc.sh -m64'
ac_cv_env_CPPFLAGS_set=set
ac_cv_env_CPPFLAGS_value='-DWIN32 -D_WINDOWS -D_DEBUG'
ac_cv_env_CXXCPP_set=
ac_cv_env_CXXCPP_value=
ac_cv_env_LT_SYS_LIBRARY_PATH_set=
ac_cv_env_LT_SYS_LIBRARY_PATH_value=
ac_cv_env_build_alias_set=set
ac_cv_env_build_alias_value=x86_64-pc-mingw32
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_func_memmove=yes
ac_cv_prog_ac_ct_STRIP=:
gl_cv_double_slash_root=yes
-----------------
Output variables.
 This issue appears to be related to vcpkg_configure_make rather than the libffi port itself.
Attempted Solutions

Installing required MSYS2 packages:
    pacman -S base-devel mingw-w64-x86_64-toolchain pkg-config

Setting MAKE environment variable in portfile.cmake:
    set(ENV{MAKE} gmake)

Using CONFIGURE_ENVIRONMENT_VARIABLES in vcpkg_configure_make:
    vcpkg_configure_make(
    SOURCE_PATH "${SOURCE_PATH}"
    ${configure_triplets}
    USE_WRAPPERS
    OPTIONS
        --enable-portable-binary
        --disable-docs
        --disable-multi-os-directory
        ${options}
    CONFIGURE_ENVIRONMENT_VARIABLES
        "CC=gcc"
        "CXX=g++"
        "MAKE=gmake"
)

Setting MAKE environment variable system-wide:
    setx MAKE gmake
    Verified with:
    gmake --version
GNU Make 4.2.1
Built for x86_64-w64-mingw32
Copyright (C) 1988-2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

None of these solutions resolved the issue.
Additional Context

The error occurs when loading a site script from /C/Users/[user]
The path mentioned in the error (C:\Windows\Temp\{33307A31-6BB0-47F8-9FBC-B9000BF55454}\.cr\VC_redist.x64.exe) suggests involvement of Visual C++ Redistributable installation
The build is using MSYS2 to provide a Unix-like environment on Windows

Possible Causes

Conflict between Windows and Unix-style path handling in the configure script
Unexpected interaction between vcpkg, MSYS2, and Visual Studio build tools
Corruption or misconfiguration in the MSYS2 environment
Issues with the vcpkg_configure_make function in handling Windows-specific scenarios

Request
Any assistance in resolving this build failure would be greatly appreciated. Specifically:

Guidance on debugging the vcpkg_configure_make function execution in this environment
Suggestions for isolating whether this is a vcpkg, libffi, or environment-specific issue
Potential workarounds or patches for the vcpkg_configure_make function to handle this scenario

Thank you for your time and assistance in resolving this issue.

Try using the x64-mingw-dynamic triplet from the MSYS2 x64 terminal window if you want to build/compile/link with gcc/g++ within the vcpkg-root directory.
The x64-windows triplet is used to build windows dynamic libraries using its own environment, some ports use MSVC/msbuild and other ports vcpkg downloads its own MSYS2/mingw environment.
But most importantly, they both load their respective toolchain with a clean initialized environment.

This is what I wrote a while ago:
https://learn.microsoft.com/vcpkg/users/platforms/mingw
Some points to mention here:

Set the host triplet to avoid x64-windows being used for tools and scripts.
Note the problems with mixing different msys2/cygwin runtime. My current usage pattern uses a non-default PATH construction: mingw path (.../mingw64, ../ucrt64) at the begin of PATH, msys2 (.../usr/bin) at the end of PATH.

NOTE: My installation of libffi x64-windows/msys was using an [almost] completely vanilla set of environment variables, as well as using defaults. Why should that installation have gone wrong?
With the following configuration, I was unable to get boost working, but I was able to get libffi installed [a dependency of boost.]
[created] x64-mingw-dynamic.cmake
set(VCPKG_TARGET_ARCHITECTURE x64)
set(VCPKG_CRT_LINKAGE dynamic)
set(VCPKG_LIBRARY_LINKAGE dynamic)

# Correct Compiler Paths
set(VCPKG_CMAKE_SYSTEM_NAME MinGW)
set(VCPKG_CHAINLOAD_TOOLCHAIN_FILE "${VCPKG_ROOT}/scripts/toolchains/mingw.cmake")

# Define the compiler
set(VCPKG_CMAKE_C_COMPILER "/mingw64/bin/gcc.exe")
set(VCPKG_CMAKE_CXX_COMPILER "/mingw64/bin/g++.exe")

# Set additional flags
set(VCPKG_CXX_FLAGS "-std=c++17")
set(VCPKG_C_FLAGS_DEBUG "-g")
set(VCPKG_C_FLAGS_RELEASE "-O3") # Fixed typo from "-03" to "-O3"
set(VCPKG_CXX_FLAGS_DEBUG "-g")
set(VCPKG_CXX_FLAGS_RELEASE "-O3") # Fixed typo from "-03" to "-O3"
set(VCPKG_LINKER_FLAGS "-static-libgcc -static-libstdc++")

# Add additional environment variables if necessary
set(ENV{MAKE} "gmake")
set(ENV{CC} "/mingw64/bin/gcc.exe")
set(ENV{CXX} "/mingw64/bin/g++.exe")

# Fixing path issues by setting MinGW paths
list(INSERT ENV{PATH} 0 "/mingw64/bin")
list(APPEND ENV{PATH} "/usr/bin")

# Config specific to my setup
set(VCPKG_CONFIGURE_OPTIONS "--enable-portable-binary --disable-docs --disable-multi-os-directory")

# Use custom toolchain file if it exists
if(EXISTS "${VCPKG_ROOT}/scripts/toolchain/custom-mingw.cmake")
    set(VCPKG_CHAINLOAD_TOOLCHAIN_FILE "${VCPKG_ROOT}/scripts/toolchains/custom-mingw.cmake")
endif

In cmd;
vcpkg install libffi:x64-mingw-dynamic --vcpkg-root C:\vcpkg

Does the build work with the stock x64-mingw-dynamic triplet? It might be easier to start with something which is known to work and then to add changes incrementally.
Forcing gmake is not needed in msys. It doesn't have BSD make.
Your custom triplet uses POSIX paths (/mingw64) where we normally use mixed-Windows paths (C:/msys64/mingw64).
Be careful which CMake, ninja, make, mingw32-make you install. MSYS programs (/usr) handle only POSIX paths (starting with /), but most of the time you need tools which can handle windows paths (C:/..., C:\...).
And remember setting the host triplet.

It appears I've found the failure in the x64 windows build.
The commands issued in building libffi do not account for what I identified as [user] in the path to have any spaces in them.
vcpkg does not always support spaces existing within the given installation path.
Thus, I installed vcpkg from github into a system linked folder which has no spaces, and it worked.
mklink /D C:\Users\Your_User_Name\ C:\Users\Your User Name\

git clone https://github.com/microsoft/vcpkg.git C:\Users\Your_User_Name\

mklink /D C:\vcpkg C:\Users\Your_User_Name\vcpkg

When attempting to install boost (with libffi) through mingw (with cobalt) the community builds failed.

The commands issued in building libffi do not account for what I identified as [user] in the path to have any spaces in them.

In fact this was my initial guess. I didn't add it to my answers because there was too much clutter with unrelated complications. No information, no benefit.

This is in fact a bug, just not a fundamental bug that applies to all platforms.

The commands issued in building libffi do not account for what I identified as [user] in the path to have any spaces in them.

In fact this was my initial guess. I didn't add it to my answers because there was too much clutter with unrelated complications. No information, no benefit.

You're right. It was a little cluttered.

It is a bug in those build systems, and it can easily be avoided by choosing different directories.
Or maybe by using super-ugly 8.3 DOS paths.
Don't expect much energy going into that problem.


Helm charts missing README.md

Describe the bug
Helm charts (charts/vela-core & charts/oam-runtime) missing README.md file, however, the released package seems to include github repo's README.md, there is an underlying problem that repo's README.md is using local referenced contents (check below) which caused display problem when showing chart's README
![](docs/resources/what-is-kubevela.png)
 [CONTRIBUTING](./CONTRIBUTING.md)

fixed by https://github.com/oam-dev/kubevela/pull/3331


Fix filtering for continuous

Seems to be broken and causing performance issues.

I see filtering in b2ContinuousQueryCallback.


Issue #1144 Clustered store bulk operations

This is a bloody hack of the store's bulk compute methods tailored to work with only cache's get, put and remove methods ONLY. The stats are not wired in. There is no test coverage except for an integration test that I wrote to check if things would work with this hack. Raising this PR just to validate my approach. Don't wanna waste time doing this if this isn't what's expected.

I'll be adding one more commit to this PR that fixes exception contract of all the store methods wrapping all RuntimeExceptions to StoreAccessExceptions. I have the changes ready. But not pushing it now as that'd screw up the whole formatting of ClusteredStore class.

test this please

Fixed the stats bug in bulk ops and added tests to verify the same.


Removed C# 6.0 features

Fixes continuation of #159

Did not realize that @KrzysztofCwalina had a PR for the same thing up already.


bug(stepper): aria-disabled not properly updated for step header buttons in linear steppers

Reproduction
Example of a linear stepper with this issue: https://stackblitz.com/angular/vbkvxdpeoml?file=src%2Fapp%2Fstepper-overview-example.ts
Steps to reproduce:

Enable linear mode
Fill out first step
Go back to step header using keyboard navigation
Move focus to next step

Expected Behavior
The screen reader should read aloud the content of the button but not mention anything about being disabled since clicking the button will work.
Actual Behavior
The screen reader says the button is disabled.
This is because aria-disabled attribute is still set on the button, but shouldn't be anymore since the step is now complete.
Environment

Angular: 12.2.4
CDK/Material: 12.2.4
Tested on Chrome with NVDA, ChromeVox, and VoiceOver.

Hi @amysorto ,
Thank you for reporting this issue. I an unable to repro on the provided stackblitz: https://stackblitz.com/angular/vbkvxdpeoml?file=src%2Fapp%2Fstepper-overview-example.ts. Below is a video capture of me trying to repro. Could you please let me know if I'm doing the correct reproduction steps? That way we can know if there is a bug that we need to fix.
https://user-images.githubusercontent.com/7720245/213253311-503c2744-ace9-449e-b714-13b2680779d5.mov
-Zach

Okay, I can reproduce now. I forgot to enable linear mode 🤦 . Bug can be reproduced without using a screenreader:

navigate to Stepper Overview example on https://material.angular.io/components/stepper/overview
(Fill out your address has gray disabled appearance and cannot be clicked on)
Type asdf into name field
(Fill out your address has gray disabled appearance but can be clicked on. It has aria-disabled="true" in the DOM.)

Seems like an invalid state for something to have disabled appearance and aria-disabled="true", but that the user is still able to interact with it.


Update Moq

Part of the fix for aspnet/Coherence-Signed#583.

@ryanbrandenburg,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot


KAFKA-3786: Let ConfigDef filter property key value pairs

@ijuma This is just one proposal for tackling the problem I mentioned in JIRA. Another related issue resolved here is that Kafka Streams may prefer a different default value for some of the underlying configs.
Let me know what do you think, and if there is a better approach, I'd be OK to go with that as well.

@guozhangwang I think the general idea is fine, but not sure about some of the details. Will comment on the PR.

One more thing: have you considered adding a logUnused to the KafkaStreams constructor? It seems like it would do the right thing if placed after KafkaConsumer and KafkaProducer are instantiated.

I think we still cannot call logUnused at the end because the configs may be used later when tasks / state managers are created, and users may want to pass extra config values that will only be used in ProcessorContext, plus we construct the produce / consumer configs by copying the property value.

OK, fair enough.

@ijuma Mind taking another look?

@ijuma Addressed comments.

Left a few minor comment, the rest LGTM. Feel free to merge after fixing them.

Thanks @ijuma , addressed comments and merged to trunk.


Feature/json schema form tests

Description
Jest tests for form rendering from custom schema.
Related issues
Closes #54
Type of change

[x] New feature (non-breaking change which adds functionality)

Changes Made

Created custom schema with different field types
Test form rendering
Test field rendering

Testing

[x] Integration Tests

I'm not sure if we have covered all the cases in forms yet but at least I have seen most of them.

There can be some underlying special cases but I think we can add those later if found.

I don't see the test case for enum in jest test for example, or is it already covered in cypress test (?)

Good call, missed that one entirely. Introduced test for enum field just now.

And I think it's good also to have some comments (in jest test) about which case/form as an example to be easier to catch up later.

Very good point. Added some comments to latest commit.


Fix Lidar lag spike from RaycastLiDARSensor.cs

Fixed a performance bug when using lidar by changing the minimum raycast calculation per job.
As we see in the unity editor's profiling tool, there's a lag spike every time lidar run, and a single job seems to perform all the calculations.

After changing the minCommandsPerJob parameter from RaycastCommand.ScheduleBatch inside RaycastLiDARSensor.cs with a constant value of 256 (arbitrary value), we can see an improvement: there are no more lag peaks, the frame rate is now stable and tasks are better distributed between jobs.

@alexandrefch
Sorry for late reply.
But, I am checking your nice PR.
Thus, I am wondering why you closed this PR.
If it is because the delay, we would like to have more time.

@alexandrefch
I see.
Thank you for your reply.
And I am looking forward to your new PR.
FYI, We also have a big PR on https://github.com/Field-Robotics-Japan/UnitySensors/pull/163.
This may also includes the Camera problem.

I just checked your linked commit and the camera issue still, in fact here, image publisher is based on compressed image, but image serializer is using EncodeToJPG method from Unity that was intended for screenshot purpose, not realtime encoding.
To allow a fast and high quality image topic (1920x1080 at 30fps), like in ZeroSimROSUnity the publisher need to send raw image by simply use the rendertexture data without encoding anything.

I see.
Thank you for your comment.
I did not know ZeroSimROSUnity. I will check details.
And also looking forward to hear your PR.


URL: https://nibs.ac.ke course url page: https://www.nibs.ac.ke/schoo…

College URL: https://nibs.ac.ke
Related Course page URL: https://www.nibs.ac.ke/school-of-computer-sciences/

@emchegep First stage of verification passed, official domain is nibs.ac.ke as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@emchegep Thank you for your patience while waiting for a review and processing your request. Pull request merged.

@philipto Thank you.


type: [fix], message: Fix isSetNewVersion function logic.

What?
[Here goes your feature/bug-fix proposal](type: [fix], message: Fix isSetNewVersion function logic.)
Type of change?

[ ] [breaking change(s)]: Changes that will require other changes in dependant applications.
[ ] [build]: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
[ ] [ci]: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
[ ] [docs]: Documentation only changes
[ ] [feat]: A new feature
[x] [fix]: A bug fix
[ ] [perf]: A code change that improves performance
[ ] [refactor]: A code change that neither fixes a bug nor adds a feature
[ ] [style]: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
[ ] [test]: Adding missing tests or correcting existing tests

Note: Remove the non-checked options
Why?
The isSetNewVersion function behavior was wrong. It was returning "" while it should return the tag version as a string.
How?
By returning fmt.Sprintf("%d.%d.%d", latest.Major, latest.Minor, latest.Patch).
How has this been tested?

[x] Unit tests
[x] Integration tests
[ ] Benchmark tests

Before submitting a PR please make sure to check if:

[x] The code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented on my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] The changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and/or existing unit tests pass locally with my changes
[x] New and/or existing integration tests pass locally with my changes

LGTM!