text:
Do not block config updates if we cannot not set up the status subsystem

What this PR does / why we need it:
Moves the status subsystem setup (provisioning clients and retrieving publish service addresses) inside the channel receiver that handles updates from the proxy and add readiness flags to indicate if setup has completed successfully. If setup is marked not ready, attempt setup and mark the result. If setup is still unready, the status update handler does nothing. If setup is ready, process status updates.
This avoids an issue where config updates deadlocked after the first loop. The update loop attempts to send updates through the ConfigDone channel that the status loop (should) receive. Prior to this change, failure to initialize the status subsystem meant it would never receive, and the update loop would block indefinitely.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #2001
Special notes for your reviewer:

RunningAddresses() was public but had no apparent reason to be. It now returns a private type, so I made it private.
Integration tests for this would require testing in an environment that cannot provision LBs. I think KTF can do this, but it does require a separate test step (I think--something separate anyway, it's mutually exclusive with our current environment).
Unit tests are maybe doable, but I think you'd need to refactor the status subsystem to define an interface for at least newStatusConfig() and runningAddresses(), mock those to always fail, and then do something convoluted with the channel--I suppose you could run PullConfigUpdate() with mocked always fail versions, have the test send to the channel with a short timeout, and fail if it exceeds the timeout?
While writing this I also confirmed how we were handling changes to the publish service in the status subsystem outside the controller reconcilers (where we will, in the future, handle updates to the GWAPI equivalent of publish services). It turns out that we don't handle this at all: we retrieve the publish services during init, save them, and then never update them again as far as I can tell (though we do have logic to update Ingress-likes if the addresses change!). This PR does not seek to address that, though it's presumably something we want to handle properly. Handling it here seems like it'd require just getting the publish service each time, which seems inefficient. I'm curious if it'd make sense to both move that into a watch somewhere and/or have a controller that handles those updates for both GWAPI and Ingress.

PR Readiness Checklist:
Complete these before marking the PR as ready to review:

[x] the CHANGELOG.md release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR

RunningAddresses() was public but had no apparent reason to be. It now returns a private type, so I made it private.

:+1:

Integration tests for this would require testing in an environment that cannot provision LBs. I think KTF can do this, but it does require a separate test step (I think--something separate anyway, it's mutually exclusive with our current environment).

I think we would need to add some functionality to our metallb addon that would cause it to ignore certain services, I'm not aware off the top of my head the configuration for that but if it did not exist for some reason it would be reasonably straightforward to add upstream.
In the short term, we could add an E2E style test (or expand an existing E2E test) where turning off metallb is more practical because each test case gets its own cluster.

Unit tests are maybe doable, but I think you'd need to refactor the status subsystem to define an interface for at least newStatusConfig() and runningAddresses(), mock those to always fail, and then do something convoluted with the channel--I suppose you could run PullConfigUpdate() with mocked always fail versions, have the test send to the channel with a short timeout, and fail if it exceeds the timeout?

While you're thinking about refactors I just wanted to point out https://github.com/Kong/kubernetes-ingress-controller/issues/1492 for your considerations. I have thought for some time that we would need to rewrite the entire status condition handling code in time. I would argue rather than refactoring heavily we should be reimplementing the status conditions as an aspect of controllers themselves.

While writing this I also confirmed how we were handling changes to the publish service in the status subsystem outside the controller reconcilers (where we will, in the future, handle updates to the GWAPI equivalent of publish services). It turns out that we don't handle this at all: we retrieve the publish services during init, save them, and then never update them again as far as I can tell (though we do have logic to update Ingress-likes if the addresses change!). This PR does not seek to address that, though it's presumably something we want to handle properly. Handling it here seems like it'd require just getting the publish service each time, which seems inefficient. I'm curious if it'd make sense to both move that into a watch somewhere and/or have a controller that handles those updates for both GWAPI and Ingress.

Good catch I would like to see a follow up issue for this so we tackle it separately.

I think we would need to add some functionality to our metallb addon that would cause it to ignore certain services ...  In the short term, we could add an E2E style test (or expand an existing E2E test) where turning off metallb is more practical because each test case gets its own cluster.

Ignoring specific services doesn't really help since this test is only relevant to the proxy service. May as well just turn it off entirely. I'm loathe to have something that slow for what's essentially a single regression test, but :shrug: refactoring to allow for a convoluted test would be painful, especially for something we intend to rework.
1cf9bbaaa0468786e86f799842b037605d7e66f1 attempts this but rapidly runs into two problems:

E2E tests against manifests and by extension existing images. Is there an existing way to trial them against a branch? I'm guessing you would need to build an image, load it into KIND, and then patch the manifests to use the temporary image?
The tests rely on the LB IP to test behavior, and this removes that. Does KTF have a way to expose the node IP for NodePorts instead? https://github.com/gianarb/kube-port-forward exists as an alternative, but I'd prefer to avoid using a one-off PoC.

E2E tests against manifests and by extension existing images. Is there an existing way to trial them against a branch? I'm guessing you would need to build an image, load it into KIND, and then patch the manifests to use the temporary image?

Yes that would be the workflow. It would seem to call for the following

the kind.Builder should have a WithContainerImageFiles(files ...string) option to identify image archives and load them prior to loading addons.
the E2E tests for this should deploy using the kustomize manifests instead of the all in one, to allow image specification

The tests rely on the LB IP to test behavior, and this removes that. Does KTF have a way to expose the node IP for NodePorts instead? https://github.com/gianarb/kube-port-forward exists as an alternative, but I'd prefer to avoid using a one-off PoC.

Not yet, but I believe that would be a trivial WithProxyServiceNodePort() to add the to KTF and wire that up to the helm values underneath.

Back to draft pending https://github.com/Kong/kubernetes-testing-framework/pull/149
The changes in 0e5d6f0f5500423e861ad83427597ab05c5908ec allow for E2E tests with custom images and using NodePorts in the event that a LoadBalancer has no IPs (or if the Service is explicitly a NodePort). It does not support automatically building the image from the current branch and loading that; you must build/tag the image yourself and specify it manually. IMO good enough to demonstrate the change viability for now--image build automation would be necessary for CI, but would require a bunch of CI work to make work. Manual local run results:
17:06:19-0800 esenin $ TEST_KONG_CONTROLLER_IMAGE_OVERRIDE="kictest:2.0.5-test" GOFLAGS="-tags=e2e_tests" go test -v \
        -race \
        -parallel 8 \
        -timeout 30m \
        ./test/e2e/... -test.run TestDeployAllInOneDBLESSNoLoadBalancer
17:06:43-0800 esenin $ TEST_KONG_CONTROLLER_IMAGE_OVERRIDE="kictest:2.0.5-test" GOFLAGS="-tags=e2e_tests" go test -v \
        -race \
        -parallel 8 \
        -timeout 30m \
        ./test/e2e/... -test.run TestDeployAllInOneDBLESSNoLoadBalancer
=== RUN   TestDeployAllInOneDBLESSNoLoadBalancer
    all_in_one_test.go:106: configuring all-in-one-dbless.yaml manifest test
=== PAUSE TestDeployAllInOneDBLESSNoLoadBalancer
=== CONT  TestDeployAllInOneDBLESSNoLoadBalancer
    all_in_one_test.go:111: building test cluster and environment
    all_in_one_test.go:125: deploying kong components
    all_in_one_test.go:556: using modified ../../deploy/single/all-in-one-dbless.yaml manifest at /tmp/kictest.909394191
    all_in_one_test.go:269: creating a tempfile for kubeconfig
    all_in_one_test.go:277: dumping kubeconfig to tempfile
    all_in_one_test.go:282: waiting for testing environment to be ready
    all_in_one_test.go:285: creating the kong namespace
    all_in_one_test.go:293: deploying any supplemental secrets (found: 0)
    all_in_one_test.go:299: deploying the /tmp/kictest.909394191 manifest to the cluster
    all_in_one_test.go:306: waiting for kong to be ready
    all_in_one_test.go:128: running ingress tests to verify all-in-one deployed ingress controller and proxy are functional
    all_in_one_test.go:315: deploying an HTTP service to test the ingress controller and proxy
    all_in_one_test.go:321: exposing deployment httpbin via service
    all_in_one_test.go:326: creating an ingress for service httpbin with ingress.class kong
    all_in_one_test.go:335: finding the kong proxy service ip
    all_in_one_test.go:359: waiting for route from Ingress to be operational at http://172.18.0.2:30620/httpbin
--- PASS: TestDeployAllInOneDBLESSNoLoadBalancer (182.86s)

Updated with the actual KTF release and rebased onto main with the previous smaller changes squashed. Now just the commit that fixes status handling and the new E2E test.
The E2E tests normally only run on tags, with the expectation that the manifests in that tag will use an image built for that tag. That's true if you're doing a release (and it's what we want for releases, to test the actual artifacts), but not otherwise. To handle this, the test updates add a shim to see if you've specified an override via the environment, rewrites the stock manifest to use that image, loads the image, and deploys the modified manifest.
Creating the image remains up to the user: this does not add CI logic for building a test image from the current branch and overriding to that. You need to manually build images before you manually run E2E tests with an override. CI will eventually test the changes whenever they're tagged. test.txt is the manual test I ran for this branch. Though not shown, TestDeployAllInOneDBLESSNoLoadBalancer will fail when run with any current released image.

Re-run following changes. Istio result is garbage since I don't run an SSH agent. Ignoring it tests.txt. Re-running that separately, but don't expect it to have issues since it's a separate codebase than the all in one tests--still in e2e but it doesn't use the deployKong() helper.

The integration tests have failed twice now. The test introduced in https://github.com/Kong/kubernetes-ingress-controller/commit/12099e8cc86c704bfa89abd89c2413e35e1686b2#diff-23f82f96580f3a9696df4886f9539c8b88cf3a3b2297b71c197e417f9d24e7b3 appears to be flaky and unrelated to this change:

The test is new.
The tested component (the admission server) behaves identically for both Postgres and DB-less systems. It failed once on DB-less (which prevented Postgres from running) and succeeded once on DB-less, but then failed in Postgres on that run.
The failure is due to a missing resource in the Kubernetes API store. I suspect we just need to wait, it's possible there's some lag between the credential create succeeding and it being actually available.

Investigating, but I think it should be ignored here.

authors: rainest shaneutt


text:
[Issue-3752] Extension - Update address for TON testnet in the token detail screen on All accounts mode

Related issue(s)

#3752

Is your feature request related to a problem(s)? Please describe.

Update logic show address on balance detail modal

Describe the solution you'd like

Update logic show address on balance detail modal

Describe alternatives you've considered

No

Additional context

No

🚀 Deployed on https://pr-3763--sw-web-runner.netlify.app

source: gharchive/pull-request

repo: Koniverse/SubWallet-Extension

license_type: permissive

license_source: github-api


text:
Clarification on config usage

from help string, mmt states:
      --config string   config file (default is $HOME/.mmt.yaml)

yet it's not entirely clear what the structure of config should be. Are there any guidelines for this?

https://github.com/KonradIT/mmt/pull/29
parameter: value
ie
camera: gopro
output: /home/user/Videos
input: 10.5.5.9
connection: connect

True, now the config file is supported.

source: gharchive/issue

authors: KonradIT daktak psukys

repo: KonradIT/mmt


text:
Solved issue #5 sound effects

Used Three.js Audio section for adding audio :

[x] Sound after clicking the tile
[x] background music

@sanket95droid  hey, please remove changes to package-lock.json and yarn.lock I will update them manually in the next commit

@sanket95droid  yes I fixed the issue you mentioned earlier about node-gyp etc.

@KonradLinkowski please compare and merge my PR!!

@sanket95droid  I can't merge it because you didn't resolve the conflicts.
But I added hacktoberfest-accepted it should appear as being accepted for hacktoberfest

Ohk i'll try to resolve those conflits and make a commit @KonradLinkowski

Ohk i'll try to resolve those conflits and make a commit @KonradLinkowski

@KonradLinkowski  Done ✅

repo: KonradLinkowski/Stack

license: MIT


text:
async not running if btn is disabled

    btnSignin.setOnClickListener{
            async() {
                var toastText : String = applicationContext.resources.getString(R.string.hint_signin_failed)
                try {
                    btnSignin.enabled = false
                    Log.d(LOG_TAG, "haha")
                    val authorization = Authorization()
                    val accessToken = authorization.authenticate(
                            editUsername.text.toString(),
                            editPassword.text.toString())
                    toastText = "access_token: $accessToken"
                }
                catch(e : Exception) {
                    Log.d(LOG_TAG, e.toString())
                }
                uiThread {
                    btnSignin.enabled = true
                    toast(toastText)
                }
            }
        }

haha will not output, and following code will not be run

my fault, must access controls from uiThread

repo: Kotlin/anko

license_source: bigquery


text:
Not able to set lparams on cardView

I'm new to anko, but so far I've not been able to find a way to set layout parameters on a cardView.
i.e.
cardView {

}.lparams { // lparams does not exist on cardView
    margin = dip(5)
}

@kiangtengl
lparams should be wrap under layout. You can apply lparams method to whatever view you want.
For example:
textView {
xxx
}.lparams {
xxx
}

This won't work.
While try to wrap this textView under linearLayout:
linearLayout {
   lparams {
      width = wrapContent
      height = wrapContent
    }
    textView {
    xxxx
    }.lparams {
    width = matchParent
    height = wrapContent
    }
}

This should work.

authors: Anthonyeef kiangtengl


text:
Minor edit of previous proposed change in trimming text - trim from start NOT end

Change in AbstractNode.java getSubstringFromStartToFit intead of getSubstringFromEndToFit

OK, I see the problem with this - the text get cropped correctly but it will get cropped from the left...to me it make more sense when it would be cropped from right - see the attached image ("MIDI device" is the label and "ble Synth" is the value text cropped from left). So really there should be "getSubstringFromStartToFit" NOT the "getSubstringFromEndToFit" :-/ sorry :-D
Also I have hinted on that you can use text(string,x,y,width,height) to crop text using processing built in function - maybe be it would be more efficient?

The problem with text(str, x,y,w,h) is that your text can completely disappear if it doesn't fit the height exactly, I think it's better to only crop it from the sides.
I agree with your idea to trim the right text from the other side so the start of the right text is visible as long as possible. I'll take a look at it later today.

Thanks a lot!

I applied your proposed change in this commit but I'm not going to merge this since you're a few commits behind.

repo: KrabCode/LazyGui


text:
Help for instalation

How can i open it :/ i can't open it

What are you trying to run? If you can not run the installation version, try a portable.
Minimum system requirements: Windows 7 and .NET Framework 4.5

i try its no openig sir

i use win10

İts done thx

authors: Benamas KriBetko

repo: KriBetko/KryBot


text:
merge from arlac77/npm-package-template

package.json

chore(package): rollup@^1.23.0
chore(scripts): cover@#overwrite c8 -x 'tests/**/*.mjs' --temp-directory build/tmp ava && c8 report -r lcov -o build/coverage --temp-directory build/tmp
docs(package): remove keyword null
chore(package): set $.ava.require='esm' as in template
chore(package): set $.ava.files='tests/*-test.mjs' as in template
chore(package): set $.ava.extensions='mjs' as in template

:tada: This PR is included in version 5.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: Kronos-Integration/kronos-service


text:
merge from arlac77/npm-package-template-esm-only

LICENSE

chore(license): add year 2020

:tada: This PR is included in version 2.0.13 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: Kronos-Integration/service-logger-gelf


text:
merge from arlac77/npm-package-template-esm-only

package.json

chore(package): add ^16.0.1 remove ^16.0.0 (devDependencies.semantic-release)

:tada: This PR is included in version 2.0.14 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


text:
Am I missing something here? (Dead Space)

So I followed the PcGaming wiki here to fix the controller deadzones. The instructions say to open Durazno.exe but it's not in any of the folders that was in the download. I didn't get any Durazno.ini or DLL either.

Binaries are not hosted on Github, you can download them from the following link that can be found on the project Readme: http://tiny.cc/magicaltools

Oh shit ok thank you much

authors: InformalMoose KrossX

repo: KrossX/Durazno

license: mit


text:
ERROR: Invalid File

I'm trying to use you tool, but I get errors when processing.  I've downloaded the audiobook several times to ensure that the file is good, but I consistently get the same results.  Mediainfo decodes the metadata just fine.  Any ideas?
./AAXtoMP3 -e:mp3 --level 4 -c -A ******** -l 1 ./ab.aax
ERROR: Invalid File: ./ab.aax
Source: ./ab.aax
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x7fffef4a6160] [aax] mismatch in checksums!
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x7fffef4a6160] error reading header
./ab.aax: Invalid data found when processing input

ok this can be closed.  i read issue #98 that prompted me to look into the activation bytes i was using.  i found that audible-activator was giving me the wrong value.  i used tables to crack the activation bytes and got the correct value.  after that aaxtomp3 worked great.

license: WTFPL


text:
Some small fixes for the Install Kuadrant and Sail via OLM guide.

Small tweaks to the kustomize install:

Add a sample AWS env-vars config
Fixed an old/outdated path in a comment in one of the kustomize files

cc: @maleck13

repo: Kuadrant/kuadrant-operator


text:
mantela.json にリダイレクトがあると壊れる

訪問済みノードの管理にURLを使っているせいで、リダイレクト元とリダイレクト先とを別のものと判断してノードがたくさん生えるっぽい

そもそも、同じ内容を複数の場所で配っても壊れないようにIDを指定していたはずなのに、これを訪問判定に使わないのは愚の骨頂

repo: KusaReMKN/mantela


text:
Init menu does not have an EXIT option, only CTRL+C exit

Enhancement
The menu of kusion init does not have an EXIT option, only CTRL+C exit
screenshot:

I don't think we need an exit button here from a long time view. Now we have only have 2 templates on list, "exit" button can be touched quickly, but if we have 10+ templates, users have to move the arrow from top to the bottom, this will be a very annoying operation.

authors: elliotxx howieyuen

repo: KusionStack/kusion


text:
Save unchanged but lived resource

fix: https://github.com/KusionStack/kusion/issues/102
Resource is living in Runtime, but not applied by kusion, next time user use kusion to apply the same Resource but no changes, kusion should save it in State

Coverage increased (+0.1%) to 74.66% when pulling 049d08dcdb75a7cea265fabdbf5a70f2252db8c9 on howieyuen:save-unchanged-but-lived-resource into 3299afd63943519c0a5e6944723fe1e63ecf3922 on KusionStack:main.

authors: coveralls howieyuen


text:
fix: add a kusion-control label in svc labels

What type of PR is this?
/kind bug

What this PR does / why we need it:
add a kusion-control label in svc labels
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Additional documentation e.g., design docs, usage docs, etc.:

lgtm


text:
docs: add kusion environment management proposal

What type of PR is this?
/kind documentation
What this PR does / why we need it:
add doc "kusion environment management proposal".
Which issue(s) this PR fixes:

Fixes #589

Pull Request Test Coverage Report for Build 6952270555
Warning: This coverage report may be inaccurate.
We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
To ensure accuracy in future PRs, please see these guidelines.
A quick fix for this PR: rebase it; your next report should be accurate.

0 of 0   changed or added relevant lines in 0 files are covered.
190 unchanged lines in 14 files lost coverage.
Overall coverage increased (+0.4%) to 75.853%

Files with Coverage Reduction
New Missed Lines
%

pkg/cmd/preview/options.go
2
83.12%

pkg/engine/operation/preview.go
3
79.31%

pkg/generator/appconfiguration/generator/ordered_resources_generator.go
3
90.57%

pkg/projectstack/types.go
4
94.37%

pkg/engine/operation/apply.go
5
75.59%

pkg/generator/appconfiguration/generator/accessories/database/database_generator.go
7
83.72%

pkg/generator/appconfiguration/generator/accessories/database/aws_rds.go
8
84.21%

pkg/engine/operation/models/operation_context.go
12
0.0%

pkg/generator/appconfiguration/generator/monitoring/monitoring_generator.go
13
75.27%

pkg/generator/appconfiguration/util.go
14
70.29%

Totals

Change from base Build 6719444720:
0.4%

Covered Lines:
7027

Relevant Lines:
9264

💛  - Coveralls

There is new pull request https://github.com/KusionStack/kusion/pull/621, please track there, close this pull request.

authors: coveralls healthjyk


text:
New Earn UI

Description
This PR sets up the new Earn UI for Kwenta.
Related issue
#1387
Motivation and Context
This PR is one of many geared towards the KWENTA token launch.
How Has This Been Tested?
N/A
Screenshots (if appropriate):

Maybe we can remove the distribution eligibility box on this PR from the repository; so when we merge it into dev it's gone, noticed it shows up on this draft deploy on the earn page, too

authors: koredefashokun platschi

repo: Kwenta/kwenta


text:
"Redis downlod or install failed."

I don't know why but every time I try and download Redis I get this error message

I have tried uninstalling and reinstalling NadekoBot completley, with the installer. But it doesnt seem to work still. Only install that works was FFMPEG. I also searched through most of the posted issues but I didn't find any that worked. Example "Crash upon start up" but the only answer is install redis but I can't install redis.

any help is apriciated.

Get latest redis 3.0.504 from here.

@Purpleness2 you can close the issue. Were going to solve it in this issue: #2128 .

i have the same problem for youtube dl

Download the batch in this zip and use option 8 and then 9 for youtube-dl.

I've pushed a fix. Restart your updater (Your updater will update) and then install redis. It will work now.

authors: Kwoth Lynxiris Macley-Kun Purpleness2 samdivaio

repo: Kwoth/NadekoBot


text:
Addressing issue: Heron's Area Explanation #9

Added a readme file with an explanation of Heron's formula.

Great! Thanks for tackling this. Ideally, the name of the README would be named something like HeronExplanation so it would be listed right next to the program, but this is fine for now.
Thanks again for your work!

Thanks, @kira0992! Hope you'll be able to continually contribute to this project. Your work is very nice.
Just out of curiosity, how were you able to find our repo?

I just searched by the tag "good first issue" and yours was the first one. :)

repo: Kyle-P/Mathematics


text:
Add orThrow and orDefault methods to Index

Adds orThrow and orDefault methods to Index. It was kind of annoying how Index#key and Index#value were marked as Nullable when in certain situations you know that they won't return nullable. Like NamedTextColor.NAMES.key(NamedTextColor.RED). These orThrow methods are just helpers to avoid wrapping calls in requireNonNulls or ignoring warnings.
Also added orDefault methods since that's a common map need.

addressed those requested changes and the check style errors

repo: KyoriPowered/adventure


text:
Only 30 repos are shown

I looked at a profile with over 30 repos (my own) and only 30 repos are used. The language data is also looks skewed, presumably because not all repos are accounted for.
Glancing at the code, it looks like the cause is that you're not paginating the GitHub API results.

BTW, it's a cool extension :-)

Glad you like it! I am looking into the pagination for the repository count, and with further research have found that the API serves up 30 repositories at a time, so I am working on a fix to display all of your repositories. This is also skewing the language data because it only pulls languages from the 30 repositories that it grabs from the API.
Thank you for bringing this issue to my attention. I will try and get a fix out by the weekend :)

I fixed this problem, however I am not ready to re-upload the extension to the chrome store. (I ran into another problem while fixing this one :) (see issue #3 )) I will probably get v.1.5.0 up on the extension store tomorrow sometime.
Thank you for bringing this problem to my attention.
If you would like to use the updated version you can load the contents of the repository as an unpacked extension in chrome
-Kyle

authors: KyroChi stephenmcd

repo: KyroChi/GitHub-Profile-Fluency


text:
Integrate CICD solutions

Integrate Travis CI

Travis
Github Actions
Circle CI
Jenkins


text:
Bug: Warnings since updating to HA 2023.2

Since updating to HA 2023.2, I have been getting some warnings in the logs about some of the HASS.Agent sensors. I get the following warning:
Sensor sensor.office_pc_satellite_gpuload has device class None, state class None and unit % thus indicating it has a numeric value; however, it has the non-numeric value: (<class 'str'>);
There was one other one, but I deleting the log without capturing the entry. If it pops up again, I will add to this post.
Thanks,
Scott

Same issue here.
It appears that when the gpuload sensor is "0%", it actually has no value.

I can also confirm this issue, and the conclusion @barneyonline made. I've been receiving the following warning from it:
Logger: homeassistant.components.sensor
Source: components/sensor/init.py:608
Integration: Sensor (documentation, issues)
First occurred: February 28, 2023 at 11:35:52 PM (1 occurrences)
Last logged: February 28, 2023 at 11:35:52 PM
Sensor sensor.XXXX_gpuload has device class None, state class None and unit % thus indicating it has a numeric value; however, it has the non-numeric value: (<class 'str'>); Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A"integration%3A+mqtt"

authors: DeniedExistence UPEngineer barneyonline


text:
Bug: Typing of '@' character is not possible on whole system when agent is running

Describe the bug
When HASS.Agent is running on my Windows 10 machine, I am no longer able to type '@' chars. I am using a german keyboard, and the Agent is somehow blocking the typing. On a german keyboard the shortcut for '@' is 'Alt Gr + Q'. For example typing of a '€' is pretty similar: 'Alt Gr + E' and is working fine. When I quit the Agent by clicking on the tray icon, it will immediately work again. I have no quickactions configured, I only have a single dummy sensor.
To Reproduce
Steps to reproduce the behavior:

Boot machine with Agent on autostart.
Wait when Agent is started
Try to type '@' char -> not working

Expected behavior
When no shortcuts are configured, it should not affect typing of any characters on a keyboard.
Screenshots
If applicable, add screenshots to help explain your problem.
Misc info (please complete the following information):

Windows build (ideally screenshot/info of winver.exe output): 22H2 19045.3208
Windows' UI language: German
HASS.Agent version: 2022.14.0

Please check what's applicable (multiple answers possible):

[x] Installed via installer
[ ] Installed manually
[x] Problem occurs in HASS.Agent
[ ] Problem occurs in Satellite Service

Possible duplicate of https://github.com/LAB02-Research/HASS.Agent/issues/292 & https://github.com/LAB02-Research/HASS.Agent/issues/225 & https://github.com/LAB02-Research/HASS.Agent/issues/122
Could you please try and configure different HotKey as https://github.com/LAB02-Research/HASS.Agent/issues/225#issuecomment-1387646483 suggested?
At some point this will be probably addressed by having a warning notification for German keyboard layouts.

Thank you very much, that solved my problem.

argl.... I was wondering for months whats wrong with my Gaming Keyboard or its driver that off all things the @ sign is not working sometimes....
then I look around in search of something different and find this thread.... yeah well, that explains it and also why @ works in the RDP connection to my laptop, but not on my PC, which my brain stored as "sometimes its working".
Thanks!
one problem less.


text:
在复制实验时遇到的问题

当我执行python train.py --dataset CROHME的时候，train.py执行到第72行代码的时候开始报错，但是这个错误很奇怪，我不是很明白，不知道你们有遇到过吗？

'x'是在字典中的，可能是你字典路径没有指定正确，检查一下words_dict。

我检查了字典路径没有错误，但是仍然有这个报错。

你好，可以请问你的邮箱吗？在拜读论文时有一些不懂的地方想要请教。联系了文中给出的邮件，但是没有被回复。

我也收到相同的错误 KeyError: 'x'

@LBH1024 任何人请帮我解决这个错误 KeyError: 'x'

我也收到相同的错误 KeyError: 'x'

你把数据集换成作者提供的数据集试试看

@SuperHHzy 非常感谢你的答复。请分享相同的数据集。我无法下载它。网站不接受我的手机号码下载。再次非常感谢 SuperHHzy。我的邮箱：pinkal21300@iiitnr.edu.in

可能是你的x和字典的x，不是同一个，虽然看上去都差不多，你用python写一个if 判断是否相等就知道了


text:
Retrieve all un-nested related Resource RTs in Sinopia Editor search

Since un-nesting the admin metadata RT, it is harder to retrieve all related Resource RTs (Work, Instance, AdminMetadata, Item) in the Sinopia Editor for additional editing.  Searching on cataloger initials will only retrieve admin metadata, while searching for a title will not retrieve admin metadata.  It would be more efficient if a cataloger could search one resource and in the search results also get all of the resources that are related to it.
For example, search a Work and in the search results also get related Instances, related Works, and related AdminMetadata.
It might entail allowing Sinopia search to refine by the main resource Classes, e.g., Work, Instance, Item, Admin Metadata.  It might also be visually useful to group the related resources indented under the main result resource.  If the main result is a Work, then indent and group under it the related Instances, AdminMetadata, Items found.

Thanks for surfacing this requirement @NancyJean! This aligns well with some of the planning work that we've been doing that involves more awareness of the relationship between Works and Instances.

Great!  Another way to do this might be with drill downs based on the relationships, e.g., if you searched for a Work, under each Work result you's get a +hasInstance, +AdminMetadata, +relatedWork, etc. and you could choose to open or not.  That would make for a more elegant and less cluttered display.

see also #2187

Couple options:

Placing the instance/admin metadata/related works as sub-sections to the work.

Having Instance/Admin metadata/related works as columns (this becomes unwieldy quickly)

Agree with you that 2 gets unwieldy.

I agree - I like the first option better.
Question -- would the other options still be easily accessible after you choose one of them?  So, if I choose to edit a Work, would the Admin metadata remain easily accessible for updating as well or would I have to search for it?  I'm thinking that it would make cataloging easier if all options were easily accessible after choosing one of them, e.g., having the Admin metadata (esp.) or the other options available to open with a click from the same Web page that's being edited.  I do understand that this is different from the page you're showing above and perhaps a separate issue :)

Agree that option 2 is not viable.
Question about option 1 though. This is for a general search, correct? If we did, say, an instance search, would we still see the links to works and admin metadata?
Also, I am hoping that once we have machine-generated data in admin metadata, that we can attach those templates to the work and instance templates rather than have them separate...

This is for any Sinopia search. If you did an instance search, you would still see the links to works and admin metadata.

authors: NancyJean NancyL astridu justinlittman michelleif


text:
Adds Stanford, Cornell, and UCSD ShareVDE authority sources

Adds QA authority lookup sources for Stanford, Cornell, and UCSD Works and Instances. NOTE currently QA is returning an URI instead of a text literal in the label field. This will be fixed soon.

Coverage remained the same at 77.256% when pulling 16cf12c20d681c8ae6bf5e25c99ad05103317b71 on add-qa-sharevde into 949781d0078ed1e27979ef44d791e9fdda12797f on master.

Do we really want to keep adding stuff to the spoof?  When will we be close enough to real to stop fussing with the spoof?

@ndushay when https://github.com/LD4P/qa_server/issues/51 gets resolved...

authors: coveralls jermnelson jgreben ndushay


text:
False positive detected on virus total and ESET NOD32, etc

Virus detected. Novice users are unable to determine if it is safe. Also you seem to have an imposter, bitcore.io

Can you give more infos? Thank you.

This also includes Sparta based Bowsers and Sophos

Maybe you can upload to virustotal and provide a link.

authors: DJPlaya DocSnyd3r2 WageSlave limxdev

repo: LIMXTEC/BitCore


text:
Version 0.7.2 does not work with examples/k8s/deploy/linstor-csi-1.16.yaml

Hi, I changed the version numbers in linstor-csi-1.16.yaml in order to use v0.7.2 instead of v0.7.0 and it did not work out. I could not attach a volume to a pod. Kubernetes gave me an error 404. When I switched back to v0.7.0 the problem disappeared.
I think the current linstor-csi-1.16.yaml are not compatible with v0.7.2
I use k8s 1.16.3
One more question, the master node in my cluster is a satellite as other two nodes (workers) are. Do I need to have linstor-csi-node running on the master node too?

I am sorry, that was my bad. The problem was with the way I named Nodes in linstor. They should be named the same way they were named in kubernetes.

repo: LINBIT/linstor-csi


text:
Hwi宏定义在readme.md中与代码不一致

OS_INCLUDE_HWI and OS_INCLUDE_HWI mentioned in Readme.md both have changed, which are defined accordingly as LOSCFG_PLATFORM_HWI and LOSCFG_PLATFORM_HWI_LIMIT now. Please update um in line with source code.

OS_INCLUDE_HWI and OS_INCLUDE_HWI mentioned in Readme.md？I can't find it.

sorry for mistake, they exist in HuaweiLiteOSKernelDevGuide.md

编程示例
前提条件：
在los_config.h中，将OS_INCLUDE_HWI定义为YES。
在los_config.h中，设置最大硬中断个数OS_HWI_MAX_USED_NUM。
说明 目前的中断测试代码提供了基本框架，中断硬件初始化代码请用户根据开发板硬件情况在Example_Exti0_Init()函数中自行实现。

But in los_config.h, I just could find#if defined (RAM_SIZE_LEVEL_0)
#define LOSCFG_PLATFORM_HWI                             NO
#elif defined(RAM_SIZE_LEVEL_1)
#define LOSCFG_PLATFORM_HWI                             YES
#elif defined(RAM_SIZE_LEVEL_2)
#define LOSCFG_PLATFORM_HWI                             YES
#else
#define LOSCFG_PLATFORM_HWI                             YES
#endif

/**
 * @ingroup los_config
 * Maximum number of used hardware interrupts, including Tick timer interrupts.
 */
#define LOSCFG_PLATFORM_HWI_LIMIT                       96

I'm sorry for that,we did some code optimization，so in source code we deleted the macro OS_HWI_MAX_USED_NUM and OS_INCLUDE_HWI, but forgot update HuaweiLiteOSKernelDevGuide.md.
we will fix this later

already fix. Thanks for you report.


text:
使用主题服务器产生内部错误500

目前使用的 Sakura 版本？
2.14.1
目前使用的 halo 版本？
所有版本
建议/问题

建议提供一下后台日志。

日志.log

建议提供一下后台日志。

全部最近7天最近30天
2024-07-13T23:39:29.753+08:00  WARN 7 --- [yReconciler-t-1] io.r2dbc.h2.H2Connection  : Option{name='readOnly', sensitive=false} + isn't supported in H2 at the transaction level. You must set it on conenction URL. See http://www.h2database.com/html/features.html#read_only
2024-07-13T23:39:34.383+08:00  INFO 7 --- [undedElastic-16] run.halo.live2d.Live2dInitProcessor  : live2d config {
"isAiChat" : false,
"aiChatBaseSetting" : {
"timeout" : 10,
"chunkTimeout" : 10,
"showChatMessageTimeout" : 10
},
"modelTexturesId" : 53,
"isForceUseDefaultConfig" : false,
"modelId" : 1,
"tools" : [ "hitokoto", "asteroids", "switch-model", "switch-texture", "photo", "info", "quit" ],
"isTools" : true,
"copyContent" : true,
"backSite" : true,
"backSiteTip" : "哇，你终于回来了～",
"selectorTips" : [ ],
"openConsole" : true,
"copyContentTip" : "你都复制了些什么呀，转载要记得加上出处哦！",
"openConsoleTip" : "你是想要看看我的小秘密吗？",
"firstOpenSite" : true,
"loadTime" : "defer",
"consoleShowStatu" : false,
"live2dLocation" : "left",
"photoName" : "live2d",
"apiPath" : "https://api.zsq.im/live2d/",
"hitokotoApi" : "https://v1.hitokoto.cn",
"showHitokoto" : true,
"tips" : "/themes/theme-sakura/assets/live2d/tips.json"
}
2024-07-13T23:39:34.391+08:00 ERROR 7 --- [undedElastic-16] org.thymeleaf.TemplateEngine  : [THYMELEAF][boundedElastic-16] Exception processing template "index": An error happened during template rendering
org.thymeleaf.exceptions.TemplateOutputException: An error happened during template rendering
at org.thymeleaf.engine.OutputTemplateHandler.handleText(OutputTemplateHandler.java:75) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.ProcessorTemplateHandler.handleText(ProcessorTemplateHandler.java:587) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Text.beHandled(Text.java:97) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Model.process(Model.java:282) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.ProcessorTemplateHandler.handleStandaloneElement(ProcessorTemplateHandler.java:1204) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.StandaloneElementTag.beHandled(StandaloneElementTag.java:228) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Model.process(Model.java:282) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Model.process(Model.java:290) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.GatheringModelProcessable.process(GatheringModelProcessable.java:78) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.ProcessorTemplateHandler.handleCloseElement(ProcessorTemplateHandler.java:1640) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.CloseElementTag.beHandled(CloseElementTag.java:139) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Model.process(Model.java:282) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.ProcessorTemplateHandler.handleOpenElement(ProcessorTemplateHandler.java:1587) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.OpenElementTag.beHandled(OpenElementTag.java:205) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Model.process(Model.java:282) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Model.process(Model.java:290) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.GatheringModelProcessable.process(GatheringModelProcessable.java:78) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.ProcessorTemplateHandler.handleCloseElement(ProcessorTemplateHandler.java:1640) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.CloseElementTag.beHandled(CloseElementTag.java:139) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Model.process(Model.java:282) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.ProcessorTemplateHandler.handleOpenElement(ProcessorTemplateHandler.java:1587) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.OpenElementTag.beHandled(OpenElementTag.java:205) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.TemplateModel.process(TemplateModel.java:136) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.TemplateManager.parseAndProcess(TemplateManager.java:592) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.TemplateEngine.process(TemplateEngine.java:1103) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.TemplateEngine.process(TemplateEngine.java:1077) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.spring6.SpringWebFluxTemplateEngine.lambda$createFullStream$0(SpringWebFluxTemplateEngine.java:198) ~[thymeleaf-spring6-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at reactor.core.publisher.MonoCreate.subscribe(MonoCreate.java:61) ~[reactor-core-3.6.4.jar:3.6.4]
at reactor.core.publisher.Mono.subscribe(Mono.java:4568) ~[reactor-core-3.6.4.jar:3.6.4]
at reactor.core.publisher.MonoSubscribeOn$SubscribeOnSubscriber.run(MonoSubscribeOn.java:126) ~[reactor-core-3.6.4.jar:3.6.4]
at reactor.core.scheduler.WorkerTask.call(WorkerTask.java:84) ~[reactor-core-3.6.4.jar:3.6.4]
at reactor.core.scheduler.WorkerTask.call(WorkerTask.java:37) ~[reactor-core-3.6.4.jar:3.6.4]
at java.base/java.util.concurrent.FutureTask.run(Unknown Source) ~[na:na]
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) ~[na:na]
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[na:na]
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[na:na]
at java.base/java.lang.Thread.run(Unknown Source) ~[na:na]
Caused by: org.thymeleaf.exceptions.TemplateProcessingException: Exception evaluating SpringEL expression: "pluginFinder.available('PluginSearchWidget', '>=1.5.0')" (template: "module/head/index" - line 37, col 28)
at org.thymeleaf.spring6.expression.SPELVariableExpressionEvaluator.evaluate(SPELVariableExpressionEvaluator.java:292) ~[thymeleaf-spring6-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at run.halo.app.theme.ReactiveSpelVariableExpressionEvaluator.evaluate(ReactiveSpelVariableExpressionEvaluator.java:29) ~[classes/:2.14.1]
at org.thymeleaf.standard.expression.VariableExpression.executeVariableExpression(VariableExpression.java:166) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.standard.expression.SimpleExpression.executeSimple(SimpleExpression.java:66) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.standard.expression.Expression.execute(Expression.java:109) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.standard.expression.Expression.execute(Expression.java:138) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.standard.processor.StandardUtextTagProcessor.doProcess(StandardUtextTagProcessor.java:87) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.processor.element.AbstractAttributeTagProcessor.doProcess(AbstractAttributeTagProcessor.java:74) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.processor.element.AbstractElementTagProcessor.process(AbstractElementTagProcessor.java:95) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.util.ProcessorConfigurationUtils$ElementTagProcessorWrapper.process(ProcessorConfigurationUtils.java:633) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.ProcessorTemplateHandler.handleOpenElement(ProcessorTemplateHandler.java:1314) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.OpenElementTag.beHandled(OpenElementTag.java:205) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.TemplateModel.process(TemplateModel.java:136) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.TemplateManager.process(TemplateManager.java:519) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.util.LazyProcessingCharSequence.writeUnresolved(LazyProcessingCharSequence.java:85) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.util.AbstractLazyCharSequence.write(AbstractLazyCharSequence.java:103) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.AbstractTextualTemplateEvent.writeContent(AbstractTextualTemplateEvent.java:224) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Text.write(Text.java:78) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.OutputTemplateHandler.handleText(OutputTemplateHandler.java:71) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
... 36 common frames omitted
Caused by: org.springframework.expression.spel.SpelEvaluationException: EL1004E: Method call: Method available(java.lang.String,java.lang.String) cannot be found on type run.halo.app.theme.finders.impl.PluginFinderImpl
at org.springframework.expression.spel.ast.MethodReference.findAccessorForMethod(MethodReference.java:237) ~[spring-expression-6.1.5.jar:6.1.5]
at org.springframework.expression.spel.ast.MethodReference.getValueInternal(MethodReference.java:147) ~[spring-expression-6.1.5.jar:6.1.5]
at org.springframework.expression.spel.ast.MethodReference$MethodValueRef.getValue(MethodReference.java:400) ~[spring-expression-6.1.5.jar:6.1.5]
at org.springframework.expression.spel.ast.CompoundExpression.getValueInternal(CompoundExpression.java:98) ~[spring-expression-6.1.5.jar:6.1.5]
at org.springframework.expression.spel.ast.SpelNodeImpl.getValue(SpelNodeImpl.java:114) ~[spring-expression-6.1.5.jar:6.1.5]
at org.springframework.expression.spel.standard.SpelExpression.getValue(SpelExpression.java:338) ~[spring-expression-6.1.5.jar:6.1.5]
at org.thymeleaf.spring6.expression.SPELVariableExpressionEvaluator.evaluate(SPELVariableExpressionEvaluator.java:265) ~[thymeleaf-spring6-3.1.2.RELEASE.jar:3.1.2.RELEASE]
... 54 common frames omitted
2024-07-13T23:39:34.395+08:00 ERROR 7 --- [undedElastic-16] o.t.spring6.SpringWebFluxTemplateEngine  : [THYMELEAF][boundedElastic-16] Exception processing template "index": An error happened during template rendering
org.thymeleaf.exceptions.TemplateOutputException: An error happened during template rendering
at org.thymeleaf.engine.OutputTemplateHandler.handleText(OutputTemplateHandler.java:75) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.ProcessorTemplateHandler.handleText(ProcessorTemplateHandler.java:587) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Text.beHandled(Text.java:97) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Model.process(Model.java:282) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.ProcessorTemplateHandler.handleStandaloneElement(ProcessorTemplateHandler.java:1204) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.StandaloneElementTag.beHandled(StandaloneElementTag.java:228) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Model.process(Model.java:282) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Model.process(Model.java:290) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.GatheringModelProcessable.process(GatheringModelProcessable.java:78) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.ProcessorTemplateHandler.handleCloseElement(ProcessorTemplateHandler.java:1640) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.CloseElementTag.beHandled(CloseElementTag.java:139) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Model.process(Model.java:282) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.ProcessorTemplateHandler.handleOpenElement(ProcessorTemplateHandler.java:1587) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.OpenElementTag.beHandled(OpenElementTag.java:205) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Model.process(Model.java:282) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Model.process(Model.java:290) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.GatheringModelProcessable.process(GatheringModelProcessable.java:78) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.ProcessorTemplateHandler.handleCloseElement(ProcessorTemplateHandler.java:1640) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.CloseElementTag.beHandled(CloseElementTag.java:139) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Model.process(Model.java:282) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.ProcessorTemplateHandler.handleOpenElement(ProcessorTemplateHandler.java:1587) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.OpenElementTag.beHandled(OpenElementTag.java:205) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.TemplateModel.process(TemplateModel.java:136) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.TemplateManager.parseAndProcess(TemplateManager.java:592) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.TemplateEngine.process(TemplateEngine.java:1103) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.TemplateEngine.process(TemplateEngine.java:1077) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.spring6.SpringWebFluxTemplateEngine.lambda$createFullStream$0(SpringWebFluxTemplateEngine.java:198) ~[thymeleaf-spring6-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at reactor.core.publisher.MonoCreate.subscribe(MonoCreate.java:61) ~[reactor-core-3.6.4.jar:3.6.4]
at reactor.core.publisher.Mono.subscribe(Mono.java:4568) ~[reactor-core-3.6.4.jar:3.6.4]
at reactor.core.publisher.MonoSubscribeOn$SubscribeOnSubscriber.run(MonoSubscribeOn.java:126) ~[reactor-core-3.6.4.jar:3.6.4]
at reactor.core.scheduler.WorkerTask.call(WorkerTask.java:84) ~[reactor-core-3.6.4.jar:3.6.4]
at reactor.core.scheduler.WorkerTask.call(WorkerTask.java:37) ~[reactor-core-3.6.4.jar:3.6.4]
at java.base/java.util.concurrent.FutureTask.run(Unknown Source) ~[na:na]
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) ~[na:na]
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[na:na]
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[na:na]
at java.base/java.lang.Thread.run(Unknown Source) ~[na:na]
Caused by: org.thymeleaf.exceptions.TemplateProcessingException: Exception evaluating SpringEL expression: "pluginFinder.available('PluginSearchWidget', '>=1.5.0')" (template: "module/head/index" - line 37, col 28)
at org.thymeleaf.spring6.expression.SPELVariableExpressionEvaluator.evaluate(SPELVariableExpressionEvaluator.java:292) ~[thymeleaf-spring6-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at run.halo.app.theme.ReactiveSpelVariableExpressionEvaluator.evaluate(ReactiveSpelVariableExpressionEvaluator.java:29) ~[classes/:2.14.1]
at org.thymeleaf.standard.expression.VariableExpression.executeVariableExpression(VariableExpression.java:166) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.standard.expression.SimpleExpression.executeSimple(SimpleExpression.java:66) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.standard.expression.Expression.execute(Expression.java:109) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.standard.expression.Expression.execute(Expression.java:138) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.standard.processor.StandardUtextTagProcessor.doProcess(StandardUtextTagProcessor.java:87) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.processor.element.AbstractAttributeTagProcessor.doProcess(AbstractAttributeTagProcessor.java:74) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.processor.element.AbstractElementTagProcessor.process(AbstractElementTagProcessor.java:95) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.util.ProcessorConfigurationUtils$ElementTagProcessorWrapper.process(ProcessorConfigurationUtils.java:633) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.ProcessorTemplateHandler.handleOpenElement(ProcessorTemplateHandler.java:1314) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.OpenElementTag.beHandled(OpenElementTag.java:205) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.TemplateModel.process(TemplateModel.java:136) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.TemplateManager.process(TemplateManager.java:519) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.util.LazyProcessingCharSequence.writeUnresolved(LazyProcessingCharSequence.java:85) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.util.AbstractLazyCharSequence.write(AbstractLazyCharSequence.java:103) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.AbstractTextualTemplateEvent.writeContent(AbstractTextualTemplateEvent.java:224) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Text.write(Text.java:78) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.OutputTemplateHandler.handleText(OutputTemplateHandler.java:71) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
... 36 common frames omitted
Caused by: org.springframework.expression.spel.SpelEvaluationException: EL1004E: Method call: Method available(java.lang.String,java.lang.String) cannot be found on type run.halo.app.theme.finders.impl.PluginFinderImpl
at org.springframework.expression.spel.ast.MethodReference.findAccessorForMethod(MethodReference.java:237) ~[spring-expression-6.1.5.jar:6.1.5]
at org.springframework.expression.spel.ast.MethodReference.getValueInternal(MethodReference.java:147) ~[spring-expression-6.1.5.jar:6.1.5]
at org.springframework.expression.spel.ast.MethodReference$MethodValueRef.getValue(MethodReference.java:400) ~[spring-expression-6.1.5.jar:6.1.5]
at org.springframework.expression.spel.ast.CompoundExpression.getValueInternal(CompoundExpression.java:98) ~[spring-expression-6.1.5.jar:6.1.5]
at org.springframework.expression.spel.ast.SpelNodeImpl.getValue(SpelNodeImpl.java:114) ~[spring-expression-6.1.5.jar:6.1.5]
at org.springframework.expression.spel.standard.SpelExpression.getValue(SpelExpression.java:338) ~[spring-expression-6.1.5.jar:6.1.5]
at org.thymeleaf.spring6.expression.SPELVariableExpressionEvaluator.evaluate(SPELVariableExpressionEvaluator.java:265) ~[thymeleaf-spring6-3.1.2.RELEASE.jar:3.1.2.RELEASE]
... 54 common frames omitted
2024-07-13T23:39:34.403+08:00 ERROR 7 --- [undedElastic-16] a.w.r.e.AbstractErrorWebExceptionHandler : [76a371c9-694] 500 Server Error for HTTP GET "/"
org.thymeleaf.exceptions.TemplateOutputException: An error happened during template rendering
at org.thymeleaf.engine.OutputTemplateHandler.handleText(OutputTemplateHandler.java:75) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
Suppressed: reactor.core.publisher.FluxOnAssembly$OnAssemblyException:
Error has been observed at the following site(s):
*__checkpoint ⇢ Handler run.halo.app.theme.router.factories.IndexRouteFactory$$Lambda/0x000000005b6aa010@2b11e7b0 [DispatcherHandler]
*__checkpoint ⇢ run.halo.app.security.InitializeRedirectionWebFilter [DefaultWebFilterChain]
*__checkpoint ⇢ AuthorizationWebFilter [DefaultWebFilterChain]
*__checkpoint ⇢ ExceptionTranslationWebFilter [DefaultWebFilterChain]
*__checkpoint ⇢ LogoutWebFilter [DefaultWebFilterChain]
*__checkpoint ⇢ ServerRequestCacheWebFilter [DefaultWebFilterChain]
*__checkpoint ⇢ SecurityContextServerWebExchangeWebFilter [DefaultWebFilterChain]
*__checkpoint ⇢ HaloAnonymousAuthenticationWebFilter [DefaultWebFilterChain]
*__checkpoint ⇢ ReactorContextWebFilter [DefaultWebFilterChain]
*__checkpoint ⇢ CsrfWebFilter [DefaultWebFilterChain]
*__checkpoint ⇢ HttpHeaderWriterWebFilter [DefaultWebFilterChain]
*__checkpoint ⇢ ServerWebExchangeReactorContextWebFilter [DefaultWebFilterChain]
*__checkpoint ⇢ org.springframework.security.web.server.WebFilterChainProxy [DefaultWebFilterChain]
*__checkpoint ⇢ run.halo.app.webfilter.AdditionalWebFilterChainProxy [DefaultWebFilterChain]
*__checkpoint ⇢ HTTP GET "/" [ExceptionHandlingWebHandler]
Original Stack Trace:
at org.thymeleaf.engine.OutputTemplateHandler.handleText(OutputTemplateHandler.java:75) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.ProcessorTemplateHandler.handleText(ProcessorTemplateHandler.java:587) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Text.beHandled(Text.java:97) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Model.process(Model.java:282) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.ProcessorTemplateHandler.handleStandaloneElement(ProcessorTemplateHandler.java:1204) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.StandaloneElementTag.beHandled(StandaloneElementTag.java:228) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Model.process(Model.java:282) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Model.process(Model.java:290) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.GatheringModelProcessable.process(GatheringModelProcessable.java:78) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.ProcessorTemplateHandler.handleCloseElement(ProcessorTemplateHandler.java:1640) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.CloseElementTag.beHandled(CloseElementTag.java:139) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Model.process(Model.java:282) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.ProcessorTemplateHandler.handleOpenElement(ProcessorTemplateHandler.java:1587) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.OpenElementTag.beHandled(OpenElementTag.java:205) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Model.process(Model.java:282) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Model.process(Model.java:290) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.GatheringModelProcessable.process(GatheringModelProcessable.java:78) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.ProcessorTemplateHandler.handleCloseElement(ProcessorTemplateHandler.java:1640) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.CloseElementTag.beHandled(CloseElementTag.java:139) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Model.process(Model.java:282) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.ProcessorTemplateHandler.handleOpenElement(ProcessorTemplateHandler.java:1587) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.OpenElementTag.beHandled(OpenElementTag.java:205) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.TemplateModel.process(TemplateModel.java:136) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.TemplateManager.parseAndProcess(TemplateManager.java:592) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.TemplateEngine.process(TemplateEngine.java:1103) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.TemplateEngine.process(TemplateEngine.java:1077) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.spring6.SpringWebFluxTemplateEngine.lambda$createFullStream$0(SpringWebFluxTemplateEngine.java:198) ~[thymeleaf-spring6-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at reactor.core.publisher.MonoCreate.subscribe(MonoCreate.java:61) ~[reactor-core-3.6.4.jar:3.6.4]
at reactor.core.publisher.Mono.subscribe(Mono.java:4568) ~[reactor-core-3.6.4.jar:3.6.4]
at reactor.core.publisher.MonoSubscribeOn$SubscribeOnSubscriber.run(MonoSubscribeOn.java:126) ~[reactor-core-3.6.4.jar:3.6.4]
at reactor.core.scheduler.WorkerTask.call(WorkerTask.java:84) ~[reactor-core-3.6.4.jar:3.6.4]
at reactor.core.scheduler.WorkerTask.call(WorkerTask.java:37) ~[reactor-core-3.6.4.jar:3.6.4]
at java.base/java.util.concurrent.FutureTask.run(Unknown Source) ~[na:na]
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) ~[na:na]
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[na:na]
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[na:na]
at java.base/java.lang.Thread.run(Unknown Source) ~[na:na]
Caused by: org.thymeleaf.exceptions.TemplateProcessingException: Exception evaluating SpringEL expression: "pluginFinder.available('PluginSearchWidget', '>=1.5.0')" (template: "module/head/index" - line 37, col 28)
at org.thymeleaf.spring6.expression.SPELVariableExpressionEvaluator.evaluate(SPELVariableExpressionEvaluator.java:292) ~[thymeleaf-spring6-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at run.halo.app.theme.ReactiveSpelVariableExpressionEvaluator.evaluate(ReactiveSpelVariableExpressionEvaluator.java:29) ~[classes/:2.14.1]
at org.thymeleaf.standard.expression.VariableExpression.executeVariableExpression(VariableExpression.java:166) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.standard.expression.SimpleExpression.executeSimple(SimpleExpression.java:66) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.standard.expression.Expression.execute(Expression.java:109) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.standard.expression.Expression.execute(Expression.java:138) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.standard.processor.StandardUtextTagProcessor.doProcess(StandardUtextTagProcessor.java:87) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.processor.element.AbstractAttributeTagProcessor.doProcess(AbstractAttributeTagProcessor.java:74) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.processor.element.AbstractElementTagProcessor.process(AbstractElementTagProcessor.java:95) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.util.ProcessorConfigurationUtils$ElementTagProcessorWrapper.process(ProcessorConfigurationUtils.java:633) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.ProcessorTemplateHandler.handleOpenElement(ProcessorTemplateHandler.java:1314) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.OpenElementTag.beHandled(OpenElementTag.java:205) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.TemplateModel.process(TemplateModel.java:136) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.TemplateManager.process(TemplateManager.java:519) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.util.LazyProcessingCharSequence.writeUnresolved(LazyProcessingCharSequence.java:85) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.util.AbstractLazyCharSequence.write(AbstractLazyCharSequence.java:103) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.AbstractTextualTemplateEvent.writeContent(AbstractTextualTemplateEvent.java:224) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Text.write(Text.java:78) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.OutputTemplateHandler.handleText(OutputTemplateHandler.java:71) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.ProcessorTemplateHandler.handleText(ProcessorTemplateHandler.java:587) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Text.beHandled(Text.java:97) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Model.process(Model.java:282) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.ProcessorTemplateHandler.handleStandaloneElement(ProcessorTemplateHandler.java:1204) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.StandaloneElementTag.beHandled(StandaloneElementTag.java:228) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Model.process(Model.java:282) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Model.process(Model.java:290) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.GatheringModelProcessable.process(GatheringModelProcessable.java:78) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.ProcessorTemplateHandler.handleCloseElement(ProcessorTemplateHandler.java:1640) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.CloseElementTag.beHandled(CloseElementTag.java:139) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Model.process(Model.java:282) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.ProcessorTemplateHandler.handleOpenElement(ProcessorTemplateHandler.java:1587) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.OpenElementTag.beHandled(OpenElementTag.java:205) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Model.process(Model.java:282) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Model.process(Model.java:290) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.GatheringModelProcessable.process(GatheringModelProcessable.java:78) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.ProcessorTemplateHandler.handleCloseElement(ProcessorTemplateHandler.java:1640) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.CloseElementTag.beHandled(CloseElementTag.java:139) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.Model.process(Model.java:282) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.ProcessorTemplateHandler.handleOpenElement(ProcessorTemplateHandler.java:1587) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.OpenElementTag.beHandled(OpenElementTag.java:205) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.TemplateModel.process(TemplateModel.java:136) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.engine.TemplateManager.parseAndProcess(TemplateManager.java:592) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.TemplateEngine.process(TemplateEngine.java:1103) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.TemplateEngine.process(TemplateEngine.java:1077) ~[thymeleaf-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at org.thymeleaf.spring6.SpringWebFluxTemplateEngine.lambda$createFullStream$0(SpringWebFluxTemplateEngine.java:198) ~[thymeleaf-spring6-3.1.2.RELEASE.jar:3.1.2.RELEASE]
at reactor.core.publisher.MonoCreate.subscribe(MonoCreate.java:61) ~[reactor-core-3.6.4.jar:3.6.4]
at reactor.core.publisher.Mono.subscribe(Mono.java:4568) ~[reactor-core-3.6.4.jar:3.6.4]
at reactor.core.publisher.MonoSubscribeOn$SubscribeOnSubscriber.run(MonoSubscribeOn.java:126) ~[reactor-core-3.6.4.jar:3.6.4]
at reactor.core.scheduler.WorkerTask.call(WorkerTask.java:84) ~[reactor-core-3.6.4.jar:3.6.4]
at reactor.core.scheduler.WorkerTask.call(WorkerTask.java:37) ~[reactor-core-3.6.4.jar:3.6.4]
at java.base/java.util.concurrent.FutureTask.run(Unknown Source) ~[na:na]
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) ~[na:na]
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[na:na]
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[na:na]
at java.base/java.lang.Thread.run(Unknown Source) ~[na:na]
Caused by: org.springframework.expression.spel.SpelEvaluationException: EL1004E: Method call: Method available(java.lang.String,java.lang.String) cannot be found on type run.halo.app.theme.finders.impl.PluginFinderImpl
at org.springframework.expression.spel.ast.MethodReference.findAccessorForMethod(MethodReference.java:237) ~[spring-expression-6.1.5.jar:6.1.5]
at org.springframework.expression.spel.ast.MethodReference.getValueInternal(MethodReference.java:147) ~[spring-expression-6.1.5.jar:6.1.5]
at org.springframework.expression.spel.ast.MethodReference$MethodValueRef.getValue(MethodReference.java:400) ~[spring-expression-6.1.5.jar:6.1.5]
at org.springframework.expression.spel.ast.CompoundExpression.getValueInternal(CompoundExpression.java:98) ~[spring-expression-6.1.5.jar:6.1.5]
at org.springframework.expression.spel.ast.SpelNodeImpl.getValue(SpelNodeImpl.java:114) ~[spring-expression-6.1.5.jar:6.1.5]
at org.springframework.expression.spel.standard.SpelExpression.getValue(SpelExpression.java:338) ~[spring-expression-6.1.5.jar:6.1.5]
at org.thymeleaf.spring6.expression.SPELVariableExpressionEvaluator.evaluate(SPELVariableExpressionEvaluator.java:265) ~[thymeleaf-spring6-3.1.2.RELEASE.jar:3.1.2.RELEASE]
... 54 common frames omitted

我的halo版本是[2.14.1]，主题版本任何一个都发生错误。
刚开始填错了

尝试将 Halo 升级至 1.7.0 版本试试。
或者理论上使用上一个版本的主题并不会报错。
看日志似乎有个 stream 流数据的插件，可以再提供一下你的系统详情么。在概览页面复制即可。

尝试将 Halo 升级至 1.7.0 版本试试。
或者理论上使用上一个版本的主题并不会报错。
看日志似乎有个 stream 流数据的插件，可以再提供一下你的系统详情么。在概览页面复制即可。

使用halo版本2.15.0更新主题至2.4.0版本后会导致服务器产生内部错误500
但升级halo版本至最新2.17.2后问题解决

使用halo版本2.15.0更新主题至2.4.0版本后会导致服务器产生内部错误500 但升级halo版本至最新2.17.2后问题解决

确实会有这样的问题，这是我的问题，2.4.0 使用了 2.17 最新的 API，所以导致不兼容低级版本。我应该将最低版本设置为 2.17.0。

close https://github.com/LIlGG/halo-theme-sakura/commit/8b3d47b2cbab76673c8b95360cdaf84e26674ac3

authors: 9216tudou LIlGG Yaklo

repo: LIlGG/halo-theme-sakura


text:
Update ScratchJr website

add print buttons to activity pages
replace Family Days twitter widget
fix Conversation and Meet-and-Greet Japanese activity print format

All of the changes are available to test on
http://staging.scratchjr.org/

Printing "Run a Race" results in step 4 not appearing entirely on the screen.  It stays as only one page, so not all information is available.

@BryceLTaylor Anne at Tufts thought it would be better to get these changes out rather than waiting for the run-a-race activity to be fixed, so I opened an issue for that one, and I'm merging these changes to master.

authors: BryceLTaylor chrisgarrity

repo: LLK/scratchjr-website


text:
Improving commit encodings collection support

This is an alternative to #178 as a more systematic commit encoding refactoring addressing several issues and providing test coverage

Rebased on a master tip which now has a fixed CI

This is an alternative to #178 as a more systematic commit encoding refactoring addressing several issues and providing test coverage

Sorry, but I do not see how this could be an alternative for PR #178 when the issue that it was trying to address had to do with implementation of CommitEncode for vectors (Vec<T>) and not collections in general.
To illustrate what I am saying, if you take the collections() test function that is included in this PR and replace the statement that declares the collection variable so that the collection is now a vector instead of a binary tree map (as shown below),
        /*let collection: BTreeMap<usize, Item> = bmap! {
            0 => Item(s!("My first case")),
            1 => Item(s!("My second case with a very long string")),
            3 => Item(s!("My third case to make the Merkle tree two layered"))
        };*/
        let collection = vec![
            Item(s!("My first case")),
            Item(s!("My second case with a very long string")),
            Item(s!("My third case to make the Merkle tree two layered")),
        ];

and try to (compile and) execute that test function,
cargo test -p client_side_validation collections

you will get the following error:
error[E0599]: no method named `commit_serialize` found for struct `Vec<Item>` in the current scope
   --> client_side_validation/src/commit_encode.rs:395:35
    |
395 |         println!("{}", collection.commit_serialize().to_hex());
    |                                   ^^^^^^^^^^^^^^^^ method not found in `Vec<Item>`
    |
   ::: /Users/claudio/.cargo/registry/src/github.com-1ecc6299db9ec823/amplify-3.0.0/src/strategy.rs:86:1
    |
86  | pub struct Holder<T, S>(T, PhantomData<S>);
    | ------------------------------------------- doesn't satisfy `Holder<[Item], _>: commit_encode::CommitEncode`
    |
   ::: /Users/claudio/.rustup/toolchains/stable-x86_64-apple-darwin/lib/rustlib/src/rust/library/alloc/src/vec.rs:300:1
    |
300 | pub struct Vec<T> {
    | -----------------
    | |
    | doesn't satisfy `Vec<Item>: commit_encode::CommitEncodeWithStrategy`
    | doesn't satisfy `Vec<Item>: commit_encode::CommitEncode`
    |
    = note: the method `commit_serialize` exists but the following trait bounds were not satisfied:
            `Vec<Item>: commit_encode::CommitEncodeWithStrategy`
            which is required by `Vec<Item>: commit_encode::CommitEncode`
            `[Item]: Sized`
            which is required by `[Item]: commit_encode::CommitEncode`
            `[Item]: commit_encode::CommitEncodeWithStrategy`
            which is required by `[Item]: commit_encode::CommitEncode`
            `[Item]: Clone`
            which is required by `[Item]: commit_encode::CommitEncode`
            `Holder<[Item], _>: commit_encode::CommitEncode`
            which is required by `[Item]: commit_encode::CommitEncode`

Showing that the CommitEncode trait is not automatically implemented for Vec<T> as it is for BTreeMap<K,V> and BTreeSet<T>.

Showing that the CommitEncode trait is not automatically implemented for Vec as it is for BTreeMap<K,V> and BTreeSet.

Correct, and that is done deliberately, as I commented in #178, otherwise we will have an unpredictable behavior. Each time you need CommitEncode on a specific vector type, you need to do impl CommitEncodeWithStrategy for Vec<ConcreteType> { type Strategy = Merklization } explicitly - no new trait is needed.
Even if you'd like to support arbitrary Vec, you need not a new trait but instead implementing generic patter like it's done in the original commit_encode code for BTreeMap/BTreeSet:
    impl<T> CommitEncodeWithStrategy for Vec<T> {
        type Strategy = Merklization;
    }

However I think this is quite risky and instead considering removing this auto implementations for BTreeMap/BTreeSet and having manual implementations on each concrete type.

Each time you need CommitEncode on a specific vector type, you need to do impl CommitEncodeWithStrategy for Vec<ConcreteType> { type Strategy = Merklization } explicitly - no new trait is needed.

Yes, that is what I initially thought and tried. However, this is not possible. For instance, if you try to do the following implementation in the contract::assignments module of the rgb-core crate (see code below),
impl CommitEncodeWithStrategy for Vec<OwnedState<PedersenStrategy>> {
    type Strategy = commit_strategy::Merklization;
}

you will get the following error when you try to compile the code:
error[E0117]: only traits defined in the current crate can be implemented for arbitrary types
  --> src/contract/assignments.rs:51:1
   |
51 | impl CommitEncodeWithStrategy for Vec<OwnedState<PedersenStrategy>> {
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^---------------------------------
   | |                                 |
   | |                                 `Vec` is not defined in the current crate
   | impl doesn't use only types from inside the current crate
   |
   = note: define and implement a trait or new type instead

Even if you'd like to support arbitrary Vecs, you need not a new trait but instead implementing generic pattern like it's currently done in the original commit_encode code for BTreeMap/BTreeSet https://github.com/LNP-BP/rust-lnpbp/blob/master/client_side_validation/src/client_side_validation.rs#L190-L195:
    impl<T> CommitEncodeWithStrategy for Vec<T> {
        type Strategy = Merklization;
    }

Unfortunately, this is also not possible because this generic implementation would conflict with the specific implementations for Vec<u8>, Vec<u16>, Vec<u32>, and Vec<u64> that already exist. I have also tried it.

Right, you can't implement foreign traits on the foreign types (like Vec or HashMap). Thus we will need a generic implementation inside client_side_verify. It can be done by removing the existing implementations on different integers (since they are not needed anyway and will be covered by the generic implementation). I do not like such generalization, but afraid no other choice here... Will add a commit in a moment.

@claudiosdc done with 6b29111188d55a456a85d7f76121cf77756fd432

@claudiosdc done with 6b29111

Yes, I guess this will do the trick. Thanks.
I believe we can close PR #178 in favor of this one.

Thank you for catching that. I do not remember the reason behind that, but I assume I had it when I was doing all that custom implementations (instead of deriving Vec the same way I derived BTreeSet/BTreeMap, especially with this specific exclusion). Will do the investigation tomorrow.

authors: claudiosdc dr-orlovsky

repo: LNP-BP/rust-lnpbp


text:
Prevent weird text boxes to appear in the chapter

Steps to reproduce

inject this js: https://cdn.discordapp.com/attachments/1055525753325883403/1141673728732827801/aaa.js
Go to AllNovelFull, The Incubus System, Glossary (Chapter 0).
open Chapter 0 (Glossary)

Expected behavior
Weird text box never appears
Actual behavior
https://github.com/LNReader/lnreader/assets/75091899/fb5389ff-e65b-4a00-876d-1cec09aca151
LNReader version
1.1.17
Android version
Android 8 miui 8
Device
Huawei p8 lite 2017
Other details
These text boxes appear rarely, but when they do they are a pain.
Maybe directly deleting them before before the JS is applied.
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with a source, I should be opening an issue in the sources repository.
[X] I have updated the app to version 1.1.17.
[X] I will fill out all of the requested information in this form.

There is no input present in the chapter's HTML and neither is the text box present in the chapter without applying any custom JS.
If this only happens after applying your custom JS then it's not an app issue.

authors: Palloxin rajarsheechatterjee

repo: LNReader/lnreader


text:
Angpow C(l) at a given l depends on l_max

Hi there, I've been looking at the ccl C_l predictions for the DES Y1 redmagic n(z)s. I was trying to compare the angpow and Limber clustering predictions, but then noticed some significant sensitivity (up to a few percent) in the angpow prediction to the l_max used, which made that comparison tricky. The plot attached shows the fractional difference in the the angpow C_l prediction for exactly the same l values (0<l<300), but in one case the calculation was done with l_max=600 (see the angpow_lmax_test function in the script used to generate the plot).
I am guessing this is either coming from
i) me screwing up/misunderstanding the usage, apologies if that is the case.
ii) l_max is used to set some accuracy settings, which changes the result at a given l.
I've also attached the n(z)s (rm_y1_nz.txt) in case anyone wants to run this script.

Hi @NiallMac. The setting of l_max for angpow set the value for k_max in the P(k) integral with the relation k_max = \pi * l_max / chi_min, where chi_min is the comoving distance of the closest edge of the closest bin. Then depending on the bin distance, the l_max should be set appropriately. I see that your first bin starts at z=0.1, then you should wonder if the corresponding k_max makes sense considering your data. My recipe would be to start with a high l_max, decrease it and see where it starts diverging beyond your requirements, at least for the first bin (the blue curve which is the worst).
BTW this is the first time I hear Angpow is used for science, if you need help for the parameter tuning please don't hesitate to ask.

Hi @jeremyneveu . So then using a higher l_max should increase the accuracy at all ell? That is not what I'm seeing...
For example here is the comparison I mentioned to the Limber calculation for l_max=300 and l_max=600. The agreement at high l for l_max=600 is quite a bit worse.

BTW this is the first time I hear Angpow is used for science, if you need help for the parameter tuning please don't hesitate to ask.
P.S. Thanks! :)

Ok thank for the plots. Using a higher l_max may not increase the accurcay of the integrals if the integrand does not decrease rapidly enough. Also as l_max and k_max are linked, numerically you will see this l_max dependence problem using other methods. I think then that what should drive the choice of the l_max is your data. In particular for the first shell, k_max should be very high. For z_min=0.1, chi_min=436 Mpc then k_max = 2.16 Mpc^-1 for l_max = 300. Is this k_max pertinent concerning the non-linearities of the P(k) or even the bining of your data in this bin ? Then you can take the reverse problem and regarding the k_max relevant for your case set the l_max.

That k_max is reasonable for my application, yes. I think I understand your point that the integrand may not converge rapidly enough for a given k_max. But in that case shouldn't the result at a given l get more accurate as I increase l_max, since that correspondingly increases k_max? But here the opposite happens, so I guess I'm not understanding your suggestion.

Hi, this is the same problem with the Class Lmax/cl_kmax. You certainly guess that there is need of P(k) regularisation above a k_max if you want to get the linear P(k) working.

Thanks @jecampagne, what is your suggestion exactly? To apply some filter to P(k) - if so how would this be chosen?

Thanks Jean-Eric. Is there some set of accuracy settings in angpow that I would need to increase to get an arbitrarily (numerically) accurate prediction? I'd like to know this so I have something to do convergence testing against.

@NiallMac The main problem is that the angpow version in CCL is the very first one that we have used for the paper. Afterwards I have made several changes that are not yet included in Angow via CCL as we do not want to make troubles in the CCL paper review. So, the original quadrature to perform z-integrations in the CCL/angpow version is not the optimal one but it may suffice. As an advise do not use the "cuts"  (Weights and Radial) as this was a  "no-good idea" and sorry for this (in the new release these has been removed), so in practice one
total_weight_cut = 0   (the default is may be 10^-6)
has_deltaR_cut = 0   (this is certainly the default)
JE

Thanks @jecampagne. It seems to me pretty essential to have a version of angpow in ccl that works reasonably for common applications such as this, regardless of troubles for the CCL paper review, or it shouldn't be included at all. How easy would it be to update to the optimal one?

Hi @NiallMac. The Angpow in CCL was benchmarked on CLASS and on the other non-limber computation provided bu CCL (method=native). In PR#283 you can see that for close redshift bins even for l_max = 200 the mean relative difference between the two methods with respect to the cosmic variance is below 2 order of magnitudes : https://github.com/LSSTDESC/CCL/pull/283 So Angpow is working as we would expect in these cases. You can try to set the two parameters proposed by @jecampagne going into the CCL/build/Angow directory and change the default parameter values in angpow_parameters.cc. I have just tried and did not see differences using your plot script, maybe try you also (I am currently travelling, not easy to work).
The inclusion of the last version of Angpow is not hard I believe, for the coding part at least, but the rebenchmarking operation can be long.

Thanks @jeremyneveu , those are useful plots. Just to make sure I understand the colorscale, do you mind describing for me exactly the quantity you calculate for that?

@jeremyneveu I'm afraid that's still not completely clear to me - what exactly is "cosmic variance" in your equation? Do you take the mean of the ratio, or do you take the mean of the numerator, with the denominator representing the error on that mean? Would your formula account for the possibility of all the C_ells being different by a small amount compared to the cosmic variance on any single C_l, but coherently so that the net effect is significant (e.g. if 100 ells are offset in the same direction by 0.1sigma)?

@NiallMac I have to correct my formula, I used :
< abs( (C_ell^Angpow - C_ell^CCL_native_non_Limber)/C_ell^CCL_native_non_Limber )/ cosmic variance >_ell
with cosmic variance = sqrt(2/(2l+1))
In other words, I checked that the relative difference between the two codes is below by at least an order of magnitude (two orders in general) with respect to the cosmic variance. The things I would like to point is that the ell_max variation you showed with Angpow will appear also with the other algorithm, because intrinsically chosing ell_max is chosing k_max.
To answer the second part of your question, yes the relative difference between the 2 algorithms is smooth with ell with in general a small shift at many ells.

@jeremyneveu ok that seems problematic for a benchmark test - in an analysis we combine information from a wide range of ell, so any inaccuracies that are coherent across a range of ell are additive, while the noise is beaten down by combining many ell modes. Comparing the inaccuracies ell-by-ell to the cosmic variance does not capture this at all.

@NiallMac This algorithm comparaison points out a systematic error between the two implementations of the non-Limber C_ell in CCL. Indeed this is "coherent across a range of ell" but we showed that this is well below the minimum statistical error you expect from a data analysis, e.g. the cosmic variance.

A more suitable formula would be:
< (C_ell^Angpow - C_ell^CCL_native_non_Limber) >_ell / \sqrt( \Sum_ell V(elll) / N_ell )
Where V(ell) is the cosmic variance for C(ell), and N_ell is the total number of ells. Now the denominator is actually the error on the mean taken in the numerator.
Probably an even better option would be to inverse variance weight the mean.

@NiallMac Looking over this thread, I agree the current error bars might not be sufficient for LSST. The goal for the paper was to present CCL and a method for numerical validation, but we expect that eventually we will have forecasts to determine whether the numerical precision achieved is good enough (i.e., doesn't induce any bias in the cosmological parameters). For this, we need a proper forecasting pipeline which is not yet in place, but it should be the next step. There will also be a trade-off between speed and accuracy that we will need to explore. For your particular application, though, indeed you could do as you say, explore the l_max value (or any other precision parameters in CCL) that allow you to reach the criterion you established above.

As described above, it doesn't seem to be the case that accuracy increases with l_max, and it's not clear that any of the parameters the ccl user has access to will help either. I completely understand if LSST precision is beyond requirements right now, but we're talking about percent-level effects here, which is some way from LSST precision presumably, and it would be good to provide some useful quantification of the accuracy of the current implementation to users.

We can certainly explore this further. I would say perhaps first extending our checks in the case of angpow vs. the native nonlimber implementation (have you looked at that comparison?), and then reproducing the test you did for the limber case. This should probe a realistic range of redshifts and ell values. It shouldn't be hard to set that up within CCL itself. Beyond l_max, I can imagine other parameters playing a role as well. Let's add this to the to-do list.

I think this issue may be obsolete due to the fact that we no longer support angpow currently. @elisachisari?

I agree. Closing

authors: NiallMac c-d-leonard damonge elisachisari jecampagne jeremyneveu

repo: LSSTDESC/CCL


text:
start package

Here I just setup the python package using a pyproject.toml file. I decided to use this type of file since it is more modern and suggested over the older setup.py + requirements.txt.
For installing the package + dependencies (locally or pypi), I decided to use flit which seems very lightweight and simple to use, although I'm open to suggestions.
Specifically
flit install -s --deps all

will install all dependencies (specified in pyproject.toml, see dependencies and project.optional-dependencies) and the package locally (in editable mode). I added how to install the package in the README also.
Any suggestions or does this look ok @EiffL @mdschneider ? After this PR I will start adding the galaxy drawing code we discussed (the code will live in the bpp folder)

Hi @EiffL and @mdschneider - I'm merging this now to start adding the other code. Please feel free to still let me know if you have suggestions and I'm happy to open a separate PR to address them.

repo: LSSTDESC/bayesian-pipelines-pixels


text:
关于训练过程生成异常

你好，感谢开源。
我把高曝光的图片从数据集中筛选了出来，除了路径和数据集没有改过其他代码了。
可以正常训练，但是在run-out中得到的train-output图片显示异常，不知道是什么原因，您可以看看不，感谢。
贴图为train-output1和train-output4

如果是在训练过程中如此，那是正常现象(此时模型还没有收敛)；如果在训练最终时还是如此，那你可以通过先运行多亮度的图，看看你的环境配置有无问题，以及检查数据匹配情况，也不排除本身该作者的模型不太适合只有过曝光的图像调整任务。

感谢您的回复。
图片是是训练最终时得到的结果，那我来试试多亮度的图，而且只用过曝光的图像训练过程损失也非常非常高，好奇怪


text:
The NodeDef mentions attr dilations not in Op

Could you give the version of tensorflow, I got an error about the "NodeDef mentions attr "dilations" not in Op".

tensorflow 1.10.0
keras 2.2.2

authors: LZQthePlane xiaoxiaoSummer


text:
update needed.

latest update have added "frames when empty" and a ton more settings both for host and game settings.
don't know how either but the discord webhook stopped working, just now. was working earlier today when the game got an update.
an option for message when the server status is online and joinable. could be when the serverlog sends this message "Shutting down Asynchronous Streaming" i havn't see it anywere els. could be wrong. but you know what i mean :D
PS. Nice work, keep it up :D

Thank you!
I am about 75% done with a semi-big update, I'll have a look at all this as well. The webhook issue sounds strange but I might have an idea.
Should hopefully be done with the update this week.

oh. found out they get SUPER delayed. shut down server around 01:51 and a message came up around 04:50.
started the server this morning around 09:21 and havn't still got anything on the Discord.
before i got message almost instant, but after the update and update in 5 min message, it got super delayed. they came 1/6-23 11:50, don't know if it's because they both got send at the same time?

If you are still running a server, could you see if the latest release has this issue? Thanks. 😊

after a day or two the issue stopped, and messages came through as soon i pressed the button. so may have been a discord server issue.
testing new release now :D

Thank you.
I tried making it as easy as possible to use. If you have the time, please let me know what you think in comparison to the old version. If you are migrating your server to the new version, don't forget to create backups.
The remove server is currently bugged but I'll release a new version tomorrow fixing it.

when i try to update a server with any other name in folder it sends
Failed to load script file 'C:\V-Rising' (real server path--> 'C:\V-Rising Server') might not be able to read (space) might just need som "serverpath" quotes in code.
when failing updating server due to space in server path, it comes with error code, and is just stuck on updating. people with no logic to look in steamcmd window, is lost and will just wait for update, maybe even uninstall again.
could remove the server tab without issue. no idéa what is bugged?
no webhook edit messages, i need those to give the messages alittle spice. also to remove the ip.
should load game and host settings in server folder save. C:*\SaveData\Settings
so maybe option to save elswere, or just press save and it saves in that location.
bigger "hitbox" for settings button, where you have to hit is very small :D
RCON console is not available. it's activated in settings.
maybe add the "Add server" button up right at the server fan list. together with VSM settings makes more sense up there.
option for different webhook messages for each server. would be very handy.
thats everything my eye hit right away :D
look awesome with new overlay. maybe add an darkmode (love that)

Big thanks!
I will have a look at all this tomorrow. RCON is temporarily disabled but should be back soon. I'll re-add the discord messages again, it's already planned, and per server is a good idea. The "Add Server" thing is hard to implement, I've been thinking about it but haven't found a way to do it "elegantly".
Only thing I'm wondering about is the Settings button, do you mean VSM Settings? The hitbox should act normal so it sounds a bit weird.
Thank you again!

no the hitboxes in host settings and game settings files.
and elegant maybe like this, and the +moves with server fans :D

Ah, I understand!
If you mean the ones with digits specifically (with up and down arrows on the side) they are meant to be replaced in the future, I did notice myself that they were frustrating to click on. I haven't gotten that far yet.
I'll see what I can do with the main UI in regards to your image. Thank you again for taking the time, I appreciate the feedback. 😊

no problem 😄  it's nice to have a little "touch" on the work 😄  especially when i use it my self 😄 not much of a coder my self tho, only basic understanding 😅

I've fixed almost everything above now.

Path can now contains spaces
Dark mode works
Game and Save Settings Editors now asks if you wanna save to a server and will automatically create it at the right place
All webhook messages are now customizable
RCON has been added again (a bit ugly, will improve over time)
Hitboxes fixed, all number boxes now use another control which looks and "acts" better

To do:

Add "New Server" button on the tabcontrol (might push the release before I can add this, haven't found a good method)

Need a bit more time then I should be able to push the release. Sorry for the wait.

I pushed the new release now, you can download it here or use the auto-updater. Let me know if it's like you wanted. Still trying to figure out where to put "Settings" and the "New" button for servers.

awesome work :D love the result :D could you add auto load of host and game settings? and maybe make it depend on what server fan you are on? if not on the fan it's fine with the current dropdown menu when you save :D but at least so i don't have to look after the files them self.

Of course. I'll make it a setting that you toggle, if enabled it will autoload the selected server when you open the editor (if it exists). I'll have a look at it this weekend. Let me know if you have any other suggestions or find any bugs.

Auto loading has been added in the latest release today.

so nice to see :D hard to see now how it would be any better :D maybe option for modinstall and auto update on that part.
only thingis, only dev builds of mods is available atm, cause the gloomrot update smashed the mods.
maybe if you are up for it, create a mod that will pull the player count, maybe even playerlist. so you can see if the server is empty or have players onlne :D
somthing completly diffrent, but hey if you have the time and want to explore i would say go you it :D

I've made some progress and should be able to release a new version with mod management being included. Hopefully it'll be done by this weekend. 👍

looks awesome. but just encounted a bug. when the server auto updates it closes the server but the auto restart starts the server while updating the server, making the application come to either alot of booting messages and fail, somtimes even crash.
the auto restart server needs to have a 5-10 sec delay, check if steamCMD is running and still updating, then wait.

Hmm, I've thoroughly tested that and it shouldn't happen. I'll have a look at it.

my server does somthing els XD

the one from 16:08 is manuel reboot

I found the error, I will add it to the next release.

The new version is getting flagged by anti viruses again, haven't had this happen since last year. I'll have to revert the latest version and try to fix it...

Should be uploaded now, let me know if it works. I think the mod manager is triggering some false detections.

Looks good. If you could implement the tags from the store, that would be really helpful, cause many plugins is outdated, and some is only for clients and some for only servers. Newst plugins is tagged with gloomrot update tag, but i have seen some updated without the tag. Not easy to go around.

woop :D new feedback :D leave an check off for webhook message per server. having a test server running, don't need messages to be sent, and have custom messages set and ready for when i need them. so deleting them would be a hassel :D

Sure, I'll add that. :)

I'm gonna close this issue because of its length, if you find any bugs or new feature requests please let me know in a new one. And thank you again for all the support.

repo: Lacyway/V-Rising-Server-Manager