Add Deployment badge to README

Add this cod to the README.md to show the status of the production deployment
Image URL
https://dev.azure.com/E4W/Elliotforwater/_apis/build/status/ElliotForWater.efw-webapp?branchName=main

Can't do but hope I'll get to learn if someone does.

I've done this a couple of times. I had to grant read access to the repositories first though as the image was being blocked. @Andreae4w I don't have organization-level access to change this. Are you able to? I've attached a screenshot of the setting we need to change.

@gsambrotta @ConradParker @adityaraute I managed to update the settings from Azure. Thanks a lot for letting me know!

Yeah, no. Sorry. I am still not sure if I know enough to solve this issue. Would request someone else to take it up.

Hi @adityaraute if you need any help, we can guide you on working on this issue.
If you instead prefer to not work on it, no problem, just let us know.
Is mostlyabout changing our README file adding the above image URL

Yes do not wish to work on it, I will observe from the sidelines. 😄

Isn't this as simple as adding the following line to the README.md file?
![Efw-Webapp-Azure-Production-Development](https://dev.azure.com/E4W/Elliotforwater/_apis/build/status/ElliotForWater.efw-webapp?branchName=main)

Is it? I tried, didn't work.

Maybe I am misunderstanding the requirement here, but as @ConradParker pointed out the image is blocked and we need some access to see the actual status in the forked repository so that it would show the status.
But after that access if granted isn't this the code change that this issue will need to resolve it?

This is what I see when I paste the line you have mentioned in the comment. The badge doesn't render.
Hence, would request whoever can solve the issue to take it up.

@sachinh19 you understood the requirement perfectly and yes, it should work adding just that line to the readme file.
To be honest I never add such badges before so I'm not so sure how it works.
We should figured out this together :)
@Andreae4w can you confirm that now the settings in Azure are done in a way that the badge can be shown publicly?
@ConradParker you said you already have done this, do we need to do anything else?

@gsambrotta Yes, I can confirm that. :)

This is what I see when I paste the line you have mentioned in the comment. The badge doesn't render.
Hence, would request whoever can solve the issue to take it up.

This is because you do not have access to the repository.

@sachinh19 you understood the requirement perfectly and yes, it should work adding just that line to the readme file.
To be honest I never add such badges before so I'm not so sure how it works.
We should figured out this together :)
@Andreae4w can you confirm that now the settings in Azure are done in a way that the badge can be shown publicly?
@ConradParker you said you already have done this, do we need to do anything else?

Now that the settings in azure are done, just adding that line to the README file should do the trick.
I would suggest one of the owners of the repository to take this change up since there is a good chance that you folks will not see the error that we can see in @adityaraute's screenshot
I would recommend on of the owners of the repositories add it so that they can render it before

I can confirm the badge is still not showing. Sorry guys, we were hoping this was an easy one for starting out. I'll take a look at the permissions again. Leave it with me.

@ConradParker @sachinh19 @adityaraute sorry guys, I have just noticed it did not take my change of settings on Azure. I have just corrected it and should be fine now.

@ConradParker @sachinh19 @adityaraute sorry guys, I have just noticed it did not take my change of settings on Azure. I have just corrected it and should be fine now.

Thanks @Andreae4w , It's still not working for me so I'll keep investigating.

thank you @ConradParker  and everybody that helped! :tada:

Wait, it's done? I don't see a linked PR.


Add option to stop pomodoro manually

Current implementation stops pomodoro automatically when the time is off. Could you add an option to stop it manually, e.g. via button in the notification. Also it would be great to have possibility to run break manually. Thanks a lot! Toggl is the best timer ever :heart:

This is a major problem for me as well. I love Toggle and I try to track all meaningful activities. However, only some of them need to be pomodoro-ed. For example, if I track a meeting at work, I don't want time tracking stop after 25 minutes. I want to stop it manually when the meeting is over. I completely agree with Ihor that there should be 1) notification when the pomodoro is finished (I often miss this event because I don't always have sound on my computer on or I listen to a music and don't notice the "ding!" of pomodoro), 2) option to stop pomodoro manually. Alternative solutions could be 1) a possibility to start tracking with or without a pomodoro (two Play buttons instead of one?), 2) a button on the main screen to turn on/off pomodoro functionality.
Overall, Toggle is a great tool but pomodoro functionality as it is right now a bit useless for me. Since most of the entries I track don't need to be pomodoro-ed, the current implementation allows for a bad user experience. I need to manually update each entry which surpassed pomodoro limit . . .

Manual pomodoro stop is must have! Will be really glad to see this feature.

+1


Upgrade to webpack v5

Purpose
I need to support a custom build artifact in a legacy Ember application.  This project was very helpful but I needed to make a few upgrades.  I am creating this PR in case it helps someone else stuck in the same place as I was.
Changes

Targets node 12 and above
Adds package-lock.json file
Adds dependabot support (this can be removed if not helpful)
Removes rsvp dependency (supported natively in node 12)
Upgrades all other packages

Warning: The new node and webpack versions are breaking changes.

Woah, that escaped me completely back then! Sorry. If you're interested in picking this package up, I can transfer it to you.


ci(lint): enable errorlint linter

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

4 of 4 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 72.279%

Totals

Change from base Build<PHONE_NUMBER>:
0.03%

Covered Lines:
1494

Relevant Lines:
2067

💛  - Coveralls


IsNumber doesn't account for the sign

Currently, IsNumber() only expects 0-9. However, it should account for negative sign as well (and maybe positive too)
Fix will be as below.
// IsNumber updated
func IsNumber(s string) bool {
	if len(s) == 0 {
		return false
	}
	for i, v := range s {
		// Number should consist of -, +, and 0-9
		// And only first character can be - or +.
		// Otherwise, it should be between 0-9.
		if i == 0 && (v == '-' || v == '+') {
			continue
		}
		if v < '0' || v > '9' {
			return false
		}
	}
	return true
}

Fixed in 0.5


Blank Resource Type with Facet Count

When I use the links for types of content on the About page, I receive a blank resource type with an actual facet count. I also get one when I do a manual search for "all" from the home page.

There are blank resource types in production as well.  This seems to be a data issue from a migration possibly?

From what I can tell resource type was not required as late as Sufia 6 based on this commit from Hector in Sufia: https://github.com/samvera/sufia/commit/ee2e6b0820e9e4043da05a68d695518d80049b06
A report that I ran on May 19, 2017 shows some files with Resource Types and some files without resource Types. https://psu.box.com/s/7xl0pp7xwyotrkm2ldhi1jbrp8trmgeg
I believe the final solution to make this work would either be have the facet translated to show a link that would show any resources with a blank facet value:
for example: https://scholarsphere.psu.edu/solr/collection1/select?fq=has_model_ssim:GenericWork&q=-resource_type_tesim:*&sort=date_uploaded_dtsi desc

I18n unspecified for the default value in the resource type.  We may insert it in the document, but it might be nicer to facet on the missing field instead of updating .
The above query is not quite right, since the number of documents does not match the facet in the application.

This may be relevant https://github.com/projectblacklight/blacklight/issues/1130


[FLINK-21008][coordination] Register ClusterEntrypoint#closeAsync as shutdown hook for the cleanup

What is the purpose of the change
In ClusterEntrypoint#shutDownAsync, we first call the closeClusterComponent, which also includes deregistering the Flink application from cluster management(e.g. Yarn, K8s). Then we call the stopClusterServices and cleanupDirectories. Imagine that the cluster management do the deregister very fast, the JobManager process receives SIGTERM before or is being executing the stopClusterServices and cleanupDirectories. The JVM process will directly exit then. So the concurrent shutDownAsync may not be fully executed. This will cause Kubernetes ConfigMaps or ZooKeeper nodes leak.
This PR first fixes the behavior of closeAsync and then register it as shutdown for the clean up.
Brief change log

Register ClusterEntrypoint#closeAsync as shutdown hook for the cleanup

Verifying this change

Add two unit tests to guard the closeAsync behavior
Start a standalone cluster and send SIGTERM to JobManager process, we will have following logs to verify that the closeAsync is executed in the shutdown hook.

2021-04-02 13:55:40,200 INFO  org.apache.flink.runtime.entrypoint.ClusterEntrypoint        [] - RECEIVED SIGNAL 15: SIGTERM. Shutting down as requested.
2021-04-02 13:55:40,202 INFO  org.apache.flink.runtime.entrypoint.ClusterEntrypoint        [] - Shutting StandaloneSessionClusterEntrypoint down with application status UNKNOWN. Diagnostics Cluster entrypoint has been closed externally..
2021-04-02 13:55:40,203 INFO  org.apache.flink.runtime.dispatcher.DispatcherRestEndpoint   [] - Shutting down rest endpoint.
2021-04-02 13:55:40,209 INFO  org.apache.flink.runtime.blob.BlobServer                     [] - Stopped BLOB server at <IP_ADDRESS>:50424
2021-04-02 13:55:40,221 INFO  org.apache.flink.runtime.dispatcher.DispatcherRestEndpoint   [] - Removing cache directory /var/folders/8v/gjbsrg5n2c35bx10yky3_fv00000gn/T/flink-web-903e94a9-8990-4ca9-9711-b180f9f12eb2/flink-web-ui
2021-04-02 13:55:40,223 INFO  org.apache.flink.runtime.dispatcher.DispatcherRestEndpoint   [] - http://localhost:8081 lost leadership
2021-04-02 13:55:40,223 INFO  org.apache.flink.runtime.dispatcher.DispatcherRestEndpoint   [] - Shut down complete.
2021-04-02 13:55:40,223 INFO  org.apache.flink.runtime.entrypoint.component.DispatcherResourceManagerComponent [] - Closing components.
2021-04-02 13:55:40,224 INFO  org.apache.flink.runtime.dispatcher.runner.SessionDispatcherLeaderProcess [] - Stopping SessionDispatcherLeaderProcess.
2021-04-02 13:55:40,224 INFO  org.apache.flink.runtime.dispatcher.StandaloneDispatcher     [] - Stopping dispatcher akka.tcp://flink@localhost:6123/user/rpc/dispatcher_1.
2021-04-02 13:55:40,224 INFO  org.apache.flink.runtime.dispatcher.StandaloneDispatcher     [] - Stopping all currently running jobs of dispatcher akka.tcp://flink@localhost:6123/user/rpc/dispatcher_1.
2021-04-02 13:55:40,225 INFO  org.apache.flink.runtime.resourcemanager.slotmanager.DeclarativeSlotManager [] - Closing the slot manager.
2021-04-02 13:55:40,225 INFO  org.apache.flink.runtime.resourcemanager.slotmanager.DeclarativeSlotManager [] - Suspending the slot manager.
2021-04-02 13:55:40,225 INFO  org.apache.flink.runtime.dispatcher.StandaloneDispatcher     [] - Stopped dispatcher akka.tcp://flink@localhost:6123/user/rpc/dispatcher_1.
2021-04-02 13:55:40,232 INFO  org.apache.flink.runtime.rpc.akka.AkkaRpcService             [] - Stopping Akka RPC service.
2021-04-02 13:55:40,235 INFO  org.apache.flink.runtime.rpc.akka.AkkaRpcService             [] - Stopping Akka RPC service.
2021-04-02 13:55:40,243 INFO  akka.remote.RemoteActorRefProvider$RemotingTerminator        [] - Shutting down remote daemon.
2021-04-02 13:55:40,243 INFO  akka.remote.RemoteActorRefProvider$RemotingTerminator        [] - Shutting down remote daemon.
2021-04-02 13:55:40,245 INFO  akka.remote.RemoteActorRefProvider$RemotingTerminator        [] - Remote daemon shut down; proceeding with flushing remote transports.
2021-04-02 13:55:40,245 INFO  akka.remote.RemoteActorRefProvider$RemotingTerminator        [] - Remote daemon shut down; proceeding with flushing remote transports.
2021-04-02 13:55:40,265 INFO  akka.remote.RemoteActorRefProvider$RemotingTerminator        [] - Remoting shut down.
2021-04-02 13:55:40,265 INFO  akka.remote.RemoteActorRefProvider$RemotingTerminator        [] - Remoting shut down.
2021-04-02 13:55:40,282 INFO  org.apache.flink.runtime.rpc.akka.AkkaRpcService             [] - Stopped Akka RPC service.
2021-04-02 13:55:40,285 INFO  org.apache.flink.runtime.rpc.akka.AkkaRpcService             [] - Stopped Akka RPC service.
2021-04-02 13:55:40,286 INFO  org.apache.flink.runtime.entrypoint.ClusterEntrypoint        [] - Terminating cluster entrypoint process StandaloneSessionClusterEntrypoint with exit code 1445.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

cc @tillrohrmann This PR is now ready for review. Please have a look.

cc @tillrohrmann I have updated this PR and added two unit tests to guard the closeAsync behavior.

I will have a look at the failed Yarn tests.

cc @tillrohrmann, comments addressed. Please have a look.

I have pushed a fixup commit to address the comments and will open corresponding PRs to 1.12 and 1.11.

I am merging this PR now.


Add CLI option for selecting a named config from a multi-config

What kind of change does this PR introduce?
feature

Did you add tests for your changes?
yes

If relevant, link to documentation update:

Summary
Adds an option to specify a named configuration to use with multiple configs.
Implements #2821

Does this PR introduce a breaking change?
no

Other information
This option has no effect on single configurations.
All configurations with a matching name in a multi-config will be compiled.

Thanks

Seems like name is not described in docs

In the docs, I think the example with multiple configurations needs just a small example snippet which would make it instantly more clear. Under the image of code is a --config-name flag snippet, ---> could be --config-name amd to represent the example. Just a thought!

@ezetreezy Send a PR


Update issue 1.0.2 -> 2.0.1

The following message
fatal: No names found, cannot describe anything.
is added to the output when you build, it does not stop the build itself and the version number seems correct, I think this might be looking for a tag and failing if there are none.
the issue goes away if you restore the old version.

Unfortunately, I don't know of a way to suppress that message on my end without cutting the feature that causes it. It is, indeed, due to a missing tag. You should be able to add the following to your project file to suppress it though:
<ItemGroup>
    <AssemblyMetadataCommand Remove="GitDescription"/>
</ItemGroup>

This corrects the issue


[Java][FlightSQL] Arrow Flight SQL JDBC Driver makes ActionCreatePreparedStatementRequest even for Statement.executeQuery() and Statement.exeute().

Describe the bug, including details regarding any error messages, version, and platform.
We (Deephaven Data Labs) have a simple FlightSQL implementation that doesn't support PreparedStatement with the understanding that executing ad hoc queries should be possible with JDBC's Statement.execute()/executeQuery(). However,  the following test case failed with an exception that indicates the driver chooses to use PreparedStatement anyways. Note that the ADBC driver for FlightSQL (Python) uses CommandStatementQuery for the same use case.
   @Test
    public void testJDBCExecuteQuery() throws SQLException {
        try (Connection connection =  DriverManager.getConnection("jdbc:arrow-flight-sql://localhost:" + localPort +
                "/?Authorization=Anonymous&useEncryption=false")) {
            Statement statement = connection.createStatement();
            ResultSet rs = statement.executeQuery("SELECT * FROM crypto where Instrument='BTC/USD' AND Price > 50000 and Exchange = 'binance'");
            ResultSetMetaData rsmd = rs.getMetaData();
            int columnsNumber = rsmd.getColumnCount();
            while (rs.next()) {
                for (int i = 1; i <= columnsNumber; i++) {
                    if (i > 1) System.out.print(",  ");
                    String columnValue = rs.getString(i);
                    System.out.print(columnValue + " " + rsmd.getColumnName(i));
                }
                System.out.println("");
            }
        }
    }

Method arrow.flight.protocol.FlightService/DoAction is unimplemented
cfjd.org.apache.arrow.flight.FlightRuntimeException: UNIMPLEMENTED: Method arrow.flight.protocol.FlightService/DoAction is unimplemented
	at app//cfjd.org.apache.arrow.flight.CallStatus.toRuntimeException(CallStatus.java:131)
	at app//cfjd.org.apache.arrow.flight.grpc.StatusUtils.fromGrpcRuntimeException(StatusUtils.java:164)
	at app//cfjd.org.apache.arrow.flight.grpc.StatusUtils$1.next(StatusUtils.java:250)
	at app//cfjd.org.apache.arrow.flight.sql.FlightSqlClient$PreparedStatement.<init>(FlightSqlClient.java:941)
	at app//cfjd.org.apache.arrow.flight.sql.FlightSqlClient.prepare(FlightSqlClient.java:728)
	at app//cfjd.org.apache.arrow.flight.sql.FlightSqlClient.prepare(FlightSqlClient.java:708)
	at app//org.apache.arrow.driver.jdbc.client.ArrowFlightSqlClientHandler.prepare(ArrowFlightSqlClientHandler.java:170)
	at app//org.apache.arrow.driver.jdbc.ArrowFlightMetaImpl.prepareAndExecute(ArrowFlightMetaImpl.java:161)
	at app//cfjd.org.apache.calcite.avatica.AvaticaConnection.prepareAndExecuteInternal(AvaticaConnection.java:675)
	at app//cfjd.org.apache.calcite.avatica.AvaticaStatement.executeInternal(AvaticaStatement.java:156)
	at app//cfjd.org.apache.calcite.avatica.AvaticaStatement.executeQuery(AvaticaStatement.java:227)
	at app//io.deephaven.flightsql.test.FlightSqlTest.testJDBCExecuteQuery(FlightSqlTest.java:673)
	at java.base@11.0.21/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base@11.0.21/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base@11.0.21/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base@11.0.21/java.lang.reflect.Method.invoke(Method.java:566)
	at app//org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:688)
	at app//org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
	at app//org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
	at app//org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:149)
	at app//org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:140)
	at app//org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestMethod(TimeoutExtension.java:84)
	at app//org.junit.jupiter.engine.execution.ExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$

This Python script runs OK against the same server.
with adbc_driver_flightsql.dbapi.connect("grpc://localhost:10000",
    conn_kwargs={ "adbc.flight.sql.rpc.call_header.authorization": "Anonymous"}) as conn:
    with conn.cursor() as cursor:
        cursor.execute("SELECT * from crypto")
        pa_table = cursor.fetch_arrow_table()

version: Arrow 13.0.0
platform: MacOS 14.5
Component(s)
Java

It looks like adbc_driver_flightsql first tries doAction / CreatePreparedStatement / ActionCreatePreparedStatement "select * from crypto", but then falls back to getFlightInfo / CommandStatementQuery "select * from crypto".
It does seem a bit strange that the default behavior is to go the prepared statement route even when the query is ad-hoc? For reference, the sequence diagrams here show the ad-hoc vs prepared statement: https://arrow.apache.org/docs/format/FlightSql.html#sequence-diagrams

Currently, both JDBC and ADBC driver bindings execute ALL queries (prepared or not) through the AFS PreparedStatement endpoints. See https://github.com/apache/arrow-adbc/issues/2040#issuecomment-2305242075


bug: plonk: Compile() corrupts the circuit object

Description
When frontend.Compile(..., &circuit) is called on a circuit := myCircuitDefinition{ ... } object, subsequent call to frontend.NewWitness(&circuit, ...) panics with can't set fr.Element from type expr.Term. I prepared a test case illustrating the problem. The test fails for every curve. I believe it shouldn't fail regardless the order in which Compile() and NewWitness() are called.
Here's the code snippet in case the link above stops working one day:
func TestCompileDoesntCorruptCircuit(t *testing.T) {
	assert := assert.New(t)
	for _, curve := range getCurves() {
		// This is deliberately instantiated inside the loop so each iteration gets a fresh object
		circuit := commitmentCircuit{X: 3}

		t.Run(
			curve.String(), func(t *testing.T) {
				ccs, err := frontend.Compile(curve.ScalarField(), scs.NewBuilder, &circuit)
				assert.NoError(err)
				assert.NotNil(ccs)

				// NewWitness fails if Compile is called on &circuit first.
				// It works ok if Compile is called after NewWitness.
				w, err := frontend.NewWitness(&circuit, curve.ScalarField())
				if err != nil {
					t.Fatalf(
						"frontend.Compile() corrupted circuit for curve %v; err: %v",
						curve.String(), err
					)
				}
				assert.NotNil(w)
			},
		)
	}
}

Expected Behavior
The proposed test case doesn't fail. It doesn't matter if NewWitness() is called before or after Compile().
Actual Behavior
The proposed test case fails. NewWitness() must be called before Compile() to avoid gnark panicking.
Possible Fix

Steps to Reproduce

Fork my branch or paste the test above to backend/plonk/plonk_test.go
Run the test, it fails
Change the order in which Compile() and NewWitness() are called
Run the test again, it passes

Context
I was writing a simple application proving and verifying a trivial circuit using Plonk and KZG. I was getting panic() in NewWitness so I played around and I noticed that the problem goes away if I generate private witness before I compile the circuit.
To be frank I'm not 100% sure this is a bug. Another way to avoid the problem is to call Compile() on one instance of the circuit  (e.g. on an empty one, like &myCircuitDefinition{}) and NewWitness() on another. On the other hand I don't see a reason Compile() would mutate the object so I guess this may be a bug.
Your Environment

gnark version used: today's master, d11824fa
gnark-crypto version used: v0.12.2-0.20231221171913-5d5eded6bb15
go version: 1.21.5 darwin/arm64
Operating System and version: macOS Sonoma 14.1 (23B2073)

Hi,
Yes, Compile() can mutate the circuit - this happens for example when we use field emulation where we compute the overflows. You should by default instantiate different Circuit instances for compilation and witness assignment.
There is another issue if you use already assigned Circuit for compile and witness assignment. When you have set X=3 by doing circuit := commitmentCircuit{X: 3}, then the compiler can deduce that in this circuit X is a constant and perform different logic (for R1CS we encode the value as a constant and in PLONK we use another selector). Now, if you try to assign witness to the same variable, then witness assignment doesn't work as the variable is optimized out.
If you want to be able to always assign X as a witness, then you should not compile with X set to non-nil value.
For example, see KZG recursion examples:

https://github.com/Consensys/gnark/blob/master/std/commitments/kzg/verifier_test.go#L924-L931 we fix the verification key for recursion. This performs the precomputation ahead of time, reducing the size of the circuit significantly.
https://github.com/Consensys/gnark/blob/master/std/commitments/kzg/verifier_test.go#L351-L358 here we don't, the recursion verification key is not provided at compile time and needs to be provided through witness assignment.


Assist gc and remove transactions.

After syncing memory will grow without timely gc, removing this reference (tip.__transactions) helped with performance issues, as well as increasing the max old space size:
node --max-old-space-size=8192 example.js

ACK


sc-10109 Warning text color is too hard to read

Scope of changes
sc-10109 Warning text color is too hard to read
Type of change

[x] bug fix
[ ] new feature
[ ] documentation
[ ] other (describe)

Acceptance criteria
https://app.shortcut.com/rotational/story/10109/warning-text-color-is-too-hard-to-read
Author checklist

[ ] I have manually tested the change and/or added automation in the form of unit tests or integration tests
[ ]  I have updated the dependencies list
[ ]  I have recompiled and included new protocol buffers to reflect changes I made
[ ]  I have added new test fixtures as needed to support added tests
[ ]   Check this box if a reviewer can merge this pull request after approval (leave it unchecked if you want to do it yourself)
[ ]  I have moved the associated Shortcut story to "Ready for Review"

Reviewer(s) checklist

[ ] Any new user-facing content that has been added for this PR has been QA'ed to ensure correct grammar, spelling, and understandability.

Codecov Report
Base: 44.11% // Head: 44.66% // Increases project coverage by +0.55% :tada:

Coverage data is based on head (b5d36c3) compared to base (62a421d).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #847      +/-   ##
==========================================
+ Coverage   44.11%   44.66%   +0.55%
==========================================
  Files         619      460     -159
  Lines       23074    20571    -2503
  Branches     1409      765     -644
==========================================
- Hits        10178     9188     -990
+ Misses      11568    10235    -1333
+ Partials     1328     1148     -180

Flag
Coverage Δ

unittests
44.66% <ø> (+0.55%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...-admin-ui/src/pages/app/details/contact/Contact.js

...eb/gds-admin-ui/src/components/BusinessCategory.js

web/gds-admin-ui/src/helpers/api/utils.js

.../src/pages/app/details/contact/EditContactModal.js

...eb/gds-admin-ui/src/redux/autocomplete/reducers.js

web/gds-admin-ui/src/components/Oval.js

web/gds-admin-ui/src/components/PageTitle.js

...dmin-ui/src/pages/app/details/ReviewNotes/index.js

web/gds-admin-ui/src/contexts/auth/constants.js

web/gds-admin-ui/src/redux/vasp-details/actions.js

... and 149 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Add quick suggestions for include/exclude patterns

Related to #44
Add quick suggestions feature to easily amend include/exclude parameters.

In src/gitingest/ingest_from_query.py:

Add generate_suggestions function to analyze repository and identify common file patterns.
Implement check_relevance function to check the relevance of each suggestion.
Add sort_suggestions function to sort suggestions based on the number of files or total lines affected.

In src/gitingest/cli.py:

Add new --suggestions option to display quick suggestions for include/exclude patterns.
Update main function to include suggestions in the output.

In src/gitingest/parse_query.py:

Add normalize_user_added_patterns function to normalize user-added patterns.
Add check_user_added_matches_suggestions function to check if user-added patterns match any suggestions.

In src/gitingest/tests/test_ingest.py:

Add tests for generate_suggestions, check_relevance, and sort_suggestions functions.

In src/static/js/utils.js:

Add toggleSuggestion function to handle adding/removing suggestions by clicking.
Add displaySuggestions function to display suggestions in the web interface.

For more details, open the Copilot Workspace session.

@cyclotruc Thank you for reviewing!
I was just testing out workspaces on mobile as I'm OOO for the holidays and don't have a machine to run a dev environment. It seems useful at first glance, but not nearly ready for implementing full features.
I'm afraid I won't be able to make a good PR for #44, I'm happy to close this and just keep the feature request open. Let me know in case you'd like me to reopen this PR.
All the best!
Scott

It's all good, the issue will help us frame the discussion and so this helps already


GridMap with a NavigationMeshInstance will crash the game.

Operating system or device - Godot version:
Windows 10 64bit - Godot 2.1 alpha
Issue description (what happened, and what was expected):
Having a GridMap with a NavigationMeshInstance will crash the game when run. There is no error in the debugger.
Steps to reproduce:
Create a mesh library, with one mesh having a NavigationMeshInstance. Then create a simple GridMap using that mesh library.
Link to minimal example project (optional but very welcome):
https://github.com/CowThing/godot-gridmap-crash

i cant reproduce it.
project example given in previous post runs ok for me, no crashes.

I also currently heavily use gridmap populated with many meshes with navigation and it works ok.
Godot 2.1 alpha, Windows 7
@CowThing maybe something with your graphic drivers ?

I tried running it again. It appears that sometimes it crashes, but sometimes it doesn't.
However if I delete the NavigationMesh from the mesh library the project has never crashed. So I'm certain it happens only when the NavigationMesh is present.

Godot 2.1 alpha
Windows 7
I done fiew tests and thats what i found.

GridMap with NavigationMeshes might create crashes in game, in editor or in both.
Godot does not capture these crashes (no error is shown by godot) just windows 0xC0000005
While in editor, rotating tile (KEY S) can make editor crash.
while in game, game will crash perhaps at moment when tile should be shown
adding WorldEnvironment to scene with default environment created - prevents from these crashes.

Hm, on the screenshot looks like this has strange address, maybe the method navmesh_create() is called from uninitialized pointer, so accessing to member last_id crashes the application? I guess that GridMap class doesn't initialize the navigation pointer in constructor, so it sometimes has random number different than NULL, so sometimes it crashes :)

Please try #5139 (not tested by me).


How to remove header and footer from first page  of DOCX (html to docx) ?

Hello,
We are generating DOCX report into our application for that we used html to docx , html-docx-js node packages and it gives us expected result.
Now, we need to add cover page into first page docx so automatically header/footer will be started from second page but we are not getting any way any attribute which help us to do same.
Please provide some suggestion to fulfill requirement.
Thanks,
Jyoti

@jyotisonghare At present concept of cover page or skipping headers and footers for the first page isn't something that I have explored.
Which attributes have you checked so far? And I sincerely hope, the attributes you were checking out were in OOXML context and not the options of html-to-docx. If not, I would suggest checking out headers and footers in OOXML standards, this PDF is for the first edition of that and you could create a PR with a branch from develop for that purpose.

@jyotisonghare At present concept of cover page or skipping headers and footers for the first page isn't something that I have explored.
Which attributes have you checked so far? And I sincerely hope, the attributes you were checking out were in OOXML context and not the options of html-to-docx. If not, I would suggest checking out headers and footers in OOXML standards, this PDF is for the first edition of that and you could create a PR with a branch from develop for that purpose.

@privateOmega , thanks for your response.
We are creating docx using HTML content. We have to only  remove header and footer from first page i.e. our cover page,  for that I have used - headerType attribute however 'even' and 'first' values are not working only default value work's.
Adding the below code for your reference:
const fileBuffer = await HTMLtoDOCX(htmlData, headerString, {
table: { row: { cantSplit: true } },
header: true,
footer: true,
pageNumber: true,
font: 'Nunito',
headerType:'even'
}, footerString);
Also can you please suggest how can we add the custom CSS for header & footer, where header consist of ( PROJECT NAME + LOGO).

@privateOmega , thanks for your response.
We are creating docx using HTML content. We have to only  remove header and footer from first page i.e. our cover page,  for that I have used - headerType attribute however 'even' and 'first' values are not working only default value work's.
Adding the below code for your reference:
const fileBuffer = await HTMLtoDOCX(htmlData, headerString, {
table: { row: { cantSplit: true } },
header: true,
footer: true,
pageNumber: true,
font: 'Nunito',
headerType:'even'
}, footerString);
Also can you please suggest how can we add the custom CSS for header & footer, where header consist of ( PROJECT NAME + LOGO).

@jyotisonghare I have added a PR for this.
Well custom CSS for header and footer is written in the same way as the document only, inline styles. You could use package like juice in case you want to inline the styles from a css file in your application.

@jyotisonghare I have added a PR for this.
Well custom CSS for header and footer is written in the same way as the document only, inline styles. You could use package like juice in case you want to inline the styles from a css file in your application.

@privateOmega , I have added your PR code into existing package and pass parameter. However it is not working for me would you please correct me where I am doing wrong or please let me know how do I pull your current code
const fileBuffer = await HTMLtoDOCX(htmlString, 'Header Text Goes Here ', {
title: 'Cover page issue',
headerType: 'default',
header: true,
footerType: 'default',
footer: true,
font: 'Nunito',
fontSize: 22,
complexScriptFontSize: 22,
table: {
row: {
cantSplit: true,
},
},
pageNumber: true,
skipFirstHeaderFooter: true,
} , ' Footer Text Goes Here');

@privateOmega , I have added your PR code into existing package and pass parameter. However it is not working for me would you please correct me where I am doing wrong or please let me know how do I pull your current code
const fileBuffer = await HTMLtoDOCX(htmlString, 'Header Text Goes Here ', {
title: 'Cover page issue',
headerType: 'default',
header: true,
footerType: 'default',
footer: true,
font: 'Nunito',
fontSize: 22,
complexScriptFontSize: 22,
table: {
row: {
cantSplit: true,
},
},
pageNumber: true,
skipFirstHeaderFooter: true,
} , ' Footer Text Goes Here');

@privateOmega , we are waiting for your response.
Thanks,
Jyoti

@privateOmega , we are waiting for your response.
Thanks,
Jyoti

@jyotisonghare Could you please post the html-to-docx entry in dependencies of your package.json?
I am assuming you are still using the version from npm, which doesn't have this change yet because it hasn't been merged, so inorder to access it, you should be doing npm i git://github.com/privateOmega/html-to-docx#feature/skip-first-header for now, when I release a new version, you would be getting it from npm i html-to-docx

@jyotisonghare Could you please post the html-to-docx entry in dependencies of your package.json?
I am assuming you are still using the version from npm, which doesn't have this change yet because it hasn't been merged, so inorder to access it, you should be doing npm i git://github.com/privateOmega/html-to-docx#feature/skip-first-header for now, when I release a new version, you would be getting it from npm i html-to-docx

PR is merged for now, will release a new version by tomorrow after testing.

PR is merged for now, will release a new version by tomorrow after testing.

Thanks @privateOmega
We are excited about the release of the new version.

Thanks @privateOmega
We are excited about the release of the new version.

Hi @privateOmega
Any Updates for the new version release with this fix?
I also tried npm i git://github.com/privateOmega/html-to-docx#feature/skip-first-header, but no dist/code folder present after install.

Hi @privateOmega
Any Updates for the new version release with this fix?
I also tried npm i git://github.com/privateOmega/html-to-docx#feature/skip-first-header, but no dist/code folder present after install.

@jyotisonghare @mahendra119 Released v1.1.33 now. Closing this issue.

@jyotisonghare @mahendra119 Released v1.1.33 now. Closing this issue.

Thank you very much @privateOmega. You have saved us a lot of time.

Thank you very much @privateOmega. You have saved us a lot of time.

@privateOmega  Thank you very much.

@privateOmega  Thank you very much.


Correct LC_ALL.  Resolves #26227

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


0.94.0b3 Home Assistant won't start

Version of HACS
0.4.1
Describe the bug
Home Assistant fails to start up, populates the below errors in the logs. Error doesn't seem to be related to HACS, but my only change on this beta was updating from 0.2.1 and confirmed Home Assistant starts up okay after disabling HACS in configuration.yaml.
To update I initially tried copying 0.4.1 files over 0.2.1, when that didn't work I deleted it all and copied fresh from the repo and had the same thing.
Debug log

2019-06-01 23:26:33 ERROR (Thread-6) [concurrent.futures] exception calling callback for <Future at 0x7f1f35a3c828 state=finished raised RuntimeError>
Traceback (most recent call last):
  File "/usr/lib/python3.5/concurrent/futures/thread.py", line 55, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/xiaomi_aqara/__init__.py", line 144, in setup
    discovery.load_platform(hass, component, DOMAIN, {}, config)
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/helpers/discovery.py", line 130, in load_platform
    hass_config))
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/core.py", line 255, in add_job
    self.loop.call_soon_threadsafe(self.async_add_job, target, *args)
  File "/usr/lib/python3.5/asyncio/base_events.py", line 618, in call_soon_threadsafe
    self._check_closed()
  File "/usr/lib/python3.5/asyncio/base_events.py", line 357, in _check_closed
    raise RuntimeError('Event loop is closed')
RuntimeError: Event loop is closed

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.5/concurrent/futures/_base.py", line 297, in _invoke_callbacks
    callback(self)
  File "/usr/lib/python3.5/asyncio/futures.py", line 463, in _call_set_state
    dest_loop.call_soon_threadsafe(_set_state, destination, source)
  File "/usr/lib/python3.5/asyncio/base_events.py", line 618, in call_soon_threadsafe
    self._check_closed()
  File "/usr/lib/python3.5/asyncio/base_events.py", line 357, in _check_closed
    raise RuntimeError('Event loop is closed')
RuntimeError: Event loop is closed

If you try 0.2.1 it works?
Can you use hastebin to share the entire HA log after startup?

0.2.1 appears to work (HA starts fine), but gives this error:
2019-06-02 00:19:47 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-06-02 00:19:49 ERROR (MainThread) [homeassistant.setup] Error during setup of component hacs
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/setup.py", line 153, in _async_setup_component
    hass, processed_config)
  File "/home/homeassistant/.homeassistant/custom_components/hacs/__init__.py", line 103, in async_setup
    require_admin=IFRAME["require_admin"],
TypeError: object NoneType can't be used in 'await' expression

The original post has my entire HA log after startup (apart from the usual custom component warning prior to those errors).

Still, post the entire log file.

Here's the full debug logging with 0.4.1 and HA failing to start:
https://pastebin.com/pn706bGh

That is wierd, it does not even load it..
If you comment out xaomi do you get further?

I tried updating to b4 with HACS disabled, worked the same, then tried enabling and got the same error.
I then disabled the Xiaomi Aqara platform and I no longer get the errors, but Home Assistant doesn't start up. Debug logs here (left sitting for 5 mins after the last log entry):
2019-06-02 07:55:12 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=logger, service=set_default_level>
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=logger, service=set_level>
2019-06-02 07:55:12 INFO (MainThread) [homeassistant.setup] Setup of domain logger took 0.0 seconds.
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=logger>
2019-06-02 07:55:12 INFO (MainThread) [homeassistant.setup] Setting up http
2019-06-02 07:55:12 INFO (MainThread) [homeassistant.setup] Setup of domain http took 0.0 seconds.
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=http>
2019-06-02 07:55:12 INFO (MainThread) [homeassistant.setup] Setting up system_log
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=system_log, service=clear>
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=system_log, service=write>
2019-06-02 07:55:12 INFO (MainThread) [homeassistant.setup] Setup of domain system_log took 0.0 seconds.
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=system_log>
2019-06-02 07:55:12 INFO (MainThread) [homeassistant.setup] Setting up recorder
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=recorder, service=purge>
2019-06-02 07:55:12 WARNING (Recorder) [homeassistant.components.recorder] Ended unfinished session (id=217 from 2019-06-01 22:23:22.895797)
2019-06-02 07:55:12 DEBUG (Recorder) [homeassistant.components.recorder] Connected to recorder database
2019-06-02 07:55:12 INFO (MainThread) [homeassistant.setup] Setup of domain recorder took 0.3 seconds.
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=recorder>
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.bootstrap] Setting up {'weather', 'ffmpeg', 'ifttt', 'light', 'vacuum', 'zeroconf', 'lifx', 'map', 'ios', 'influxdb', 'mobile_app', 'yeelight', 'notify', 'zone', 'frontend', 'device_tracker', 'auth', 'shopping_list', 'lovelace', 'hacs', 'google_assistant', 'switch', 'sensor', 'mqtt', 'cover', 'apple_tv', 'daikin', 'config', 'conversation', 'api', 'onboarding', 'fan', 'sun', 'climate', 'system_health', 'automation', 'input_number', 'history', 'media_player', 'websocket_api', 'homekit', 'media_extractor', 'discovery', 'plant', 'shell_command', 'logbook', 'sonos', 'configurator', 'cast', 'webhook', 'group', 'binary_sensor', 'alexa', 'http', 'input_select', 'speedtestdotnet', 'person', 'script', 'panel_iframe', 'timer', 'updater', 'input_boolean'}
2019-06-02 07:55:12 INFO (MainThread) [homeassistant.setup] Setting up input_number
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=input_number, service=set_value>
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=input_number, service=increment>
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=input_number, service=decrement>
2019-06-02 07:55:12 INFO (MainThread) [homeassistant.setup] Setting up zone
2019-06-02 07:55:12 INFO (MainThread) [homeassistant.setup] Setup of domain zone took 0.0 seconds.
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=zone>
2019-06-02 07:55:12 INFO (MainThread) [homeassistant.setup] Setting up timer
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=timer, service=start>
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=timer, service=pause>
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=timer, service=cancel>
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=timer, service=finish>
2019-06-02 07:55:12 INFO (MainThread) [homeassistant.setup] Setting up updater
2019-06-02 07:55:12 INFO (MainThread) [homeassistant.setup] Setting up input_boolean
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=input_boolean, service=turn_on>
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=input_boolean, service=turn_off>
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=input_boolean, service=toggle>
2019-06-02 07:55:12 INFO (MainThread) [homeassistant.setup] Setting up homekit
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.components.homekit] Begin setup HomeKit
2019-06-02 07:55:12 INFO (MainThread) [homeassistant.setup] Setting up lovelace
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event panels_updated[L]>
2019-06-02 07:55:12 INFO (MainThread) [homeassistant.setup] Setup of domain lovelace took 0.0 seconds.
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=lovelace>
2019-06-02 07:55:12 INFO (MainThread) [homeassistant.setup] Setting up discovery
2019-06-02 07:55:12 INFO (MainThread) [homeassistant.setup] Setup of domain discovery took 0.1 seconds.
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=discovery>
2019-06-02 07:55:12 INFO (MainThread) [homeassistant.setup] Setting up shell_command
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=shell_command, service=forked_daapd_volume_bedroom>
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=shell_command, service=forked_daapd_volume_living_room>
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=shell_command, service=forked_daapd_volume_shed>
2019-06-02 07:55:12 INFO (MainThread) [homeassistant.setup] Setup of domain shell_command took 0.0 seconds.
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=shell_command>
2019-06-02 07:55:12 INFO (MainThread) [homeassistant.setup] Setting up sonos
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=sonos, service=join>
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=sonos, service=unjoin>
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=sonos, service=snapshot>
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=sonos, service=restore>
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=sonos, service=set_sleep_timer>
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=sonos, service=clear_sleep_timer>
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=sonos, service=update_alarm>
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=sonos, service=set_option>
2019-06-02 07:55:12 INFO (MainThread) [homeassistant.setup] Setup of domain sonos took 0.0 seconds.
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=sonos>
2019-06-02 07:55:12 INFO (MainThread) [homeassistant.setup] Setting up ffmpeg
2019-06-02 07:55:12 DEBUG (MainThread) [haffmpeg.core] Start FFmpeg with ['/usr/bin/ffmpeg', '-version', '']
2019-06-02 07:55:12 INFO (MainThread) [homeassistant.setup] Setting up configurator
2019-06-02 07:55:12 INFO (MainThread) [homeassistant.setup] Setup of domain configurator took 0.0 seconds.
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=configurator>
2019-06-02 07:55:12 INFO (MainThread) [homeassistant.setup] Setting up cast
2019-06-02 07:55:12 INFO (MainThread) [homeassistant.setup] Setup of domain cast took 0.0 seconds.
2019-06-02 07:55:12 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=cast>
2019-06-02 07:55:12 INFO (MainThread) [homeassistant.setup] Setting up daikin
2019-06-02 07:55:12 INFO (MainThread) [homeassistant.setup] Setup of domain daikin took 0.0 seconds.
2019-06-02 07:55:13 DEBUG (MainThread) [pydaikin.appliance] Updating ['common/basic_info']
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setting up group
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setting up lifx
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setup of domain lifx took 0.0 seconds.
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=lifx>
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setting up input_select
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=input_select, service=select_option>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=input_select, service=select_next>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=input_select, service=select_previous>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=input_select, service=set_options>
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setting up influxdb
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setting up speedtestdotnet
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=speedtestdotnet, service=speedtest>
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setup of domain speedtestdotnet took 0.0 seconds.
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=speedtestdotnet>
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setting up sun
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.components.sun] sun phase_update@2019-06-01T22:25:13.245829+00:00: phase=small_day
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.components.sun] sun position_update@2019-06-01T22:25:13.245829+00:00: elevation=6.51 azimuth=57.24
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: new_state=<state sun.sun=above_horizon; next_setting=2019-06-02T07:43:03+00:00, next_noon=2019-06-02T02:43:12+00:00, azimuth=57.24, elevation=6.51, next_dawn=2019-06-02T21:16:14+00:00, next_midnight=2019-06-02T14:43:23+00:00, next_rising=2019-06-02T21:43:57+00:00, next_dusk=2019-06-02T08:10:44+00:00, rising=True, friendly_name=Sun @ 2019-06-02T07:55:13.284637+09:30>, entity_id=sun.sun, old_state=None>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.components.sun] next time: 2019-06-01T22:45:01+00:00
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setup of domain sun took 0.0 seconds.
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=sun>
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setting up person
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setting up yeelight
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: new_state=<state zone.home=zoning; latitude=-34.782027, radius=50.0, friendly_name=Home, longitude=138.669962, hidden=True @ 2019-06-02T07:55:13.371195+09:30>, entity_id=zone.home, old_state=None>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: new_state=<state zone.mawson_lakes=zoning; latitude=-34.809511, radius=500.0, friendly_name=Mawson Lakes, longitude=138.620297, hidden=True @ 2019-06-02T07:55:13.372572+09:30>, entity_id=zone.mawson_lakes, old_state=None>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: new_state=<state timer.sleep_bedroom=idle; remaining=None, duration=None @ 2019-06-02T07:55:13.373704+09:30>, entity_id=timer.sleep_bedroom, old_state=None>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: new_state=<state timer.sprinkler_zone_1=idle; remaining=None, duration=None @ 2019-06-02T07:55:13.381954+09:30>, entity_id=timer.sprinkler_zone_1, old_state=None>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: new_state=<state timer.sprinkler_zone_4=idle; remaining=None, duration=None @ 2019-06-02T07:55:13.382472+09:30>, entity_id=timer.sprinkler_zone_4, old_state=None>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: new_state=<state timer.sprinkler_zone_3=idle; remaining=None, duration=None @ 2019-06-02T07:55:13.382830+09:30>, entity_id=timer.sprinkler_zone_3, old_state=None>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: new_state=<state timer.sprinkler_zone_2=idle; remaining=None, duration=None @ 2019-06-02T07:55:13.385488+09:30>, entity_id=timer.sprinkler_zone_2, old_state=None>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event config_entry_discovered[L]>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: new_state=<state group.homekit_entities=unknown; order=0, friendly_name=HomeKit Entities, entity_id=('light.bedroom', 'light.wardrobe', 'light.ensuite', 'light.study', 'light.kitchen', 'light.living_room', 'light.lounge', 'light.front_door', 'light.laundry', 'light.back_door', 'light.pool_room', 'light.carport', 'light.outside_front', 'light.verandah', 'switch.sprinkler_control', 'input_boolean.homekit_location', 'media_player.living_room_tv', 'media_player.bedroom_tv', 'switch.vacuum', 'switch.triplej', 'switch.airplay_shed', 'switch.airplay_living_room', 'switch.airplay_bedroom', 'switch.lights', 'cover.roller_door', 'fan.verandah', 'climate.ac_bedroom', 'fan.ac_bedroom', 'climate.heater_living_room', 'cover.blind_bedroom') @ 2019-06-02T07:55:13.401381+09:30>, entity_id=group.homekit_entities, old_state=None>
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setup of domain updater took 0.8 seconds.
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=updater>
2019-06-02 07:55:13 INFO (Thread-2) [homeassistant.loader] Loaded darksky from homeassistant.components.darksky
2019-06-02 07:55:13 INFO (Thread-2) [homeassistant.loader] Loaded pi_hole from homeassistant.components.pi_hole
2019-06-02 07:55:13 DEBUG (Thread-5) [asyncio] Using selector: EpollSelector
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: service_data=title=New devices discovered, message=We have discovered new devices on your network. [Check it out](/config/integrations), notification_id=config_entry_discovery, domain=persistent_notification, service=create>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: service_data=notification_id=config_entry_discovery, domain=persistent_notification, service=dismiss>
2019-06-02 07:55:13 DEBUG (Thread-4) [homeassistant.components.yeelight] Adding configured Front West
2019-06-02 07:55:13 DEBUG (Thread-4) [homeassistant.components.yeelight] Adding configured Front East
2019-06-02 07:55:13 INFO (Thread-4) [homeassistant.loader] Loaded workday from homeassistant.components.workday
2019-06-02 07:55:13 INFO (Thread-4) [homeassistant.loader] Loaded generic_thermostat from homeassistant.components.generic_thermostat
2019-06-02 07:55:13 INFO (Thread-4) [homeassistant.loader] Loaded html5 from homeassistant.components.html5
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setup of domain timer took 0.9 seconds.
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=timer>
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setting up history
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event panels_updated[L]>
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setup of domain history took 0.0 seconds.
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=history>
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setting up websocket_api
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setup of domain websocket_api took 0.0 seconds.
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=websocket_api>
2019-06-02 07:55:13 DEBUG (Thread-5) [pyhap.characteristic] set_value: Name to Home Assistant Bridge
2019-06-02 07:55:13 DEBUG (Thread-5) [pyhap.characteristic] set_value: SerialNumber to default
2019-06-02 07:55:13 DEBUG (Thread-5) [pyhap.characteristic] set_value: FirmwareRevision to 0.94.0b4
2019-06-02 07:55:13 DEBUG (Thread-5) [pyhap.characteristic] set_value: Manufacturer to Home Assistant
2019-06-02 07:55:13 DEBUG (Thread-5) [pyhap.characteristic] set_value: Model to Bridge
2019-06-02 07:55:13 DEBUG (Thread-5) [pyhap.characteristic] set_value: SerialNumber to homekit.bridge
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setting up auth
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setup of domain auth took 0.0 seconds.
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=auth>
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setting up shopping_list
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setting up google_assistant
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=google_assistant, service=request_sync>
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setup of domain google_assistant took 0.0 seconds.
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=google_assistant>
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setting up mqtt
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setup of domain mqtt took 0.0 seconds.
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setting up apple_tv
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: new_state=<state persistent_notification.config_entry_discovery=notifying; title=New devices discovered, message=We have discovered new devices on your network. [Check it out](/config/integrations) @ 2019-06-02T07:55:13.738881+09:30>, entity_id=persistent_notification.config_entry_discovery, old_state=None>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event persistent_notifications_updated[L]>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: new_state=None, entity_id=persistent_notification.config_entry_discovery, old_state=<state persistent_notification.config_entry_discovery=notifying; title=New devices discovered, message=We have discovered new devices on your network. [Check it out](/config/integrations) @ 2019-06-02T07:55:13.738881+09:30>>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event persistent_notifications_updated[L]>
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setting up webhook
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setup of domain webhook took 0.0 seconds.
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=webhook>
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setting up config
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event panels_updated[L]>
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setting up conversation
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=conversation, service=process>
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setup of domain conversation took 0.0 seconds.
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=conversation>
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setting up api
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setting up alexa
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setup of domain alexa took 0.0 seconds.
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=alexa>
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setting up system_health
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setup of domain system_health took 0.0 seconds.
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=system_health>
2019-06-02 07:55:13 DEBUG (MainThread) [pyatv.airplay.srp] Authentication keys (Private=REDACTED, Public=REDACTED)
2019-06-02 07:55:13 DEBUG (MainThread) [pyatv.internal.apple_tv] Loaded AirPlay credentials: F15048A792E50510:REDACTED
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=ffmpeg, service=start>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=ffmpeg, service=stop>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=ffmpeg, service=restart>
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setup of domain ffmpeg took 1.0 seconds.
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=ffmpeg>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=config.entity_registry>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=config.automation>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=config.group>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=config.config_entries>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=config.script>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=config.area_registry>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=config.core>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=config.customize>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=config.auth>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=config.device_registry>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=config.auth_provider_homeassistant>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: new_state=<state group.irrigation=unknown; order=1, friendly_name=Irrigation, entity_id=('switch.sprinkler_zone_1', 'switch.sprinkler_zone_2', 'switch.sprinkler_zone_3', 'switch.sprinkler_zone_4') @ 2019-06-02T07:55:13.871336+09:30>, entity_id=group.irrigation, old_state=None>
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setup of domain yeelight took 0.5 seconds.
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=yeelight>
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setting up climate
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setting up notify
2019-06-02 07:55:13 INFO (Thread-2) [homeassistant.loader] Loaded mpd from homeassistant.components.mpd
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=homekit, service=start>
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setup of domain homekit took 1.3 seconds.
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=homekit>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=shopping_list, service=add_item>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=shopping_list, service=complete_item>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event panels_updated[L]>
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setup of domain shopping_list took 0.4 seconds.
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=shopping_list>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=mqtt, service=publish>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=mqtt>
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setup of domain influxdb took 0.7 seconds.
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=influxdb>
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setup of domain api took 0.1 seconds.
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=api>
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setting up onboarding
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=apple_tv, service=apple_tv_scan>
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=apple_tv, service=apple_tv_authenticate>
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setup of domain apple_tv took 0.2 seconds.
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=apple_tv>
2019-06-02 07:55:13 INFO (Thread-4) [homeassistant.loader] Loaded bom from homeassistant.components.bom
2019-06-02 07:55:13 INFO (Thread-4) [homeassistant.loader] Loaded plex from homeassistant.components.plex
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setting up ifttt
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=ifttt, service=trigger>
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setup of domain ifttt took 0.0 seconds.
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=ifttt>
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setting up mobile_app
2019-06-02 07:55:13 INFO (MainThread) [homeassistant.setup] Setup of domain config took 0.2 seconds.
2019-06-02 07:55:13 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=config>
2019-06-02 07:55:13 INFO (Thread-6) [homeassistant.loader] Loaded template from homeassistant.components.template
2019-06-02 07:55:14 DEBUG (MainThread) [homeassistant.helpers.restore_state] Created cache with [REDACTED]
2019-06-02 07:55:14 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: new_state=<state group.irrigation_control=unknown; order=2, friendly_name=Irrigation Control, entity_id=('input_number.sprinkler_timer_1', 'input_number.sprinkler_timer_2', 'input_number.sprinkler_timer_3', 'input_number.sprinkler_timer_4', 'input_number.sprinkler_temp', 'input_boolean.sprinkler_control') @ 2019-06-02T07:55:14.014196+09:30>, entity_id=group.irrigation_control, old_state=None>
2019-06-02 07:55:15 DEBUG (InfluxDB) [homeassistant.components.influxdb] Wrote 1 events

Interesting...
It then looks like that error comes from Xiaomi.
The last line here is (InfluxDB) [homeassistant.components.influxdb] Wrote 1 events did you try disabling that?
From what can tell HA has not even loaded HACS, so I find it hard to believe that is the issue here.
When it start you will see this INFO (MainThread) [homeassistant.setup] Setting up hacs
This is 3s worth of logs, how did you install HA?
If you try the latest stable, does that work?

https://github.com/custom-components/hacs/releases/tag/0.4.3 fixes your issue @mynameisdaniel32, you should also look into upgrading python :)


False positive in deprecation with mergMap

Describe the bug
When implementing the use of mergMap in Angular Ngrx effects, ESLint warns about the deprecated use of mergMap even if the operator is used correctly.
Expected behavior
The deprecation message should not appear when the operator is used correctly.
Reproduction code
export const deleteAddon = createEffect(
    (actions$ = inject(Actions), repository: AddonsRepository = inject(ADDONS_REPOSITORY)) => {
        return actions$.pipe(
            ofType(DeleteAddon),
            // This mergeMap alerts for deprecation!!
            mergeMap(({ id }) => deleteAddonUseCase(repository, id).pipe(
                map(() => DeleteAddonSuccess()),
            )),
        );
    },
    { functional: true },
);

Reproduction URL
No response
Version
7.8.1
Environment
No response
Additional context
No response

I can't confirm this in 7.x or 8.x.


Crana website + Documentation

Hello there,
I really loved the idea of Crana and i want to contribute as much as i can. I believe that the most funtumental thing about a project is how you present it to the public.
So what do you think about developing a simple website with documentation, maybe with docsify, docusaurous, docz or a similar framework-generator or even a custom made minimalistic site?
Comment your thoughts. I would love to help make this project bigger =)

Hi Panagiotis!
First of all thanks for your kind words and thanks for your willingness to be part of this project!
You are totally right, the presentation to the public is very very important, and there are many things to do regarding this aspect. I've recently set up a Kanban board under "projects" (https://github.com/scriptify/crana/projects/1), and there actually is excatly such a todo!
I am currently working on the next big change of Crana: Extensions (you can read more about them on the Kanban board). Therefore, I will not have so much time for documentation etc, so it would be awesome if you would like to start creating it! I can give you any help you need: Guiding you through the project, explaining stuff, answering questions, ... 🙂
Honestly I have no experience in creating documentation websites, until now I've always used SSG like GatsbyJS to create simple websites.
I also think that the README would need a lot of improvement, so that it's clearer what Crana is exactly about and what problems it tries to solve.
So which steps should we take next regarding the documentation/presentation to the public, what do you think?

I am gonna install Crana and test some stuff in the next couple of days, to get a better grip on the project and be able to improve the README.md and the documentation in general. And i will create a pull request with my suggestions.
In the meantime, check this out, https://docsify.js.org/#/?id=docsify . This kind of minimal site i am talking about. It's pretty straight forward and i think the minimal design which is implemented is absolutely smooth for open source projects.

I think docsify looks great, we could use it for the documentation of Crana.

Hello again,
I am in the verge of finishing a first prototype of crana's documentation site.
I think that maybe you should create an organization named Crana and trasfer the main repository there. Crana needs to be an organization in order to create multiple repositories like crana-core, crana-website, crana-express extension for example etc etc.
The reason i am suggesting this, is because i will have to upload Crana's documentation code somewhere and its very convient to create an organization.

You can see a prototype of the Docs here: http://crana-doc-test.surge.sh/#/. Of course it needs a lot of work, but this is the style it will be built upon.

That's a very good idea, I've just created an organization and sent you an invitation. I like how the documentation looks so far, good work!

@pankaryp I've just uploaded a new release of crana with the tag "next" to npm. You can try it by installing crana like this: "npm i -g crana@next" (what you probably already know ^^). It is the version you can find at this branch: https://github.com/CranaJS/crana/tree/feature/extensions
Here, I implemented crana extensions. You can already choose  between 3 offical extensions I've included (all of them under "official-extensions"): React, Typescript, Svelte. When you run "crana init ", you can choose which extensions to install. I think there's a lot left to explain, but I'm in a bit of a hurry right now, so I'll not explain everything in this comment. Please just drop your questions! (I'll come back here ASAP). PS: The implementation of the extension system also means that Crana is now totally independent of React, yei! 😄

So I'd suggest to publish the official docs page as soon as extensions have been shipped and documented.

Awesome, i will check it out as soon as i return home and i will finish the docs in the next 2-3 days. Didnt have much time to contribute this week unfortunately.

There are still a few things to stabilize and test before the next version can ship, so we have time. I also struggle to find more time, but that's a developer's life ^^

hehehe yea me too cause i have tones of university projects and right now i had an idea also for a CLI, that takes cares the project set up in different languages (javascript, nim, rust, elixir, python etc). So on top of all , i am working on this. Life is awesome! Lol

Btw if you need any help with the development of a plugin or maybe to extend crana's core, let me know. I am looking forward into getting more into crana's code.

Yea I also have a lot of projects going on, but this is the only OS project I can currently afford. But I would love to see it grow and become more mature from commit to commit.
Yea that would be awesome! I can guide you through the code if you want, we could have a video call with screen sharing, I think that would be the mose effective way.

yeap sure!! We can arrange that. Tell me if u have time inside this weekend !?

During the weekend I have no time unfortunately, not until Tuesday TBH. I'd have time from now until Friday night all the time basically.


difference of low , mid , high_extract.h5

Dear sir, I am a little confused of these models: mid_extract.h5, high_extract.h5, low_extract.h5，is the performance of low_extract.h5 worse than mid_extract.h5 and high_extract.h5, or high_extract.h5 is used to generate high cloakes, low_extract.h5 is used to generate low cloakes ? Is there any connection between the model's performance and the name of model like "low", "high"? thanks!

Dear sir, one more question, I have trained some models based on  tensorflow, how can I convert tensorflow model to h5 model based on keras that can be used directly in your code,  I have no idea about this , grateful to get advice from u,sir! Thank you .

The mid_ low_ and high_ has no real meaning, - just some names I gave arbitrarily when doing the experiments.
As for converting tf models to .h5 models, it is pretty complicated. I suggest you to change the source code of Fawkes to directly read your tf graph.


very bad book

I have never read a book in which the topics are explained in a worse way (no consistence, ,arguments explained inconsistently )...if anyone want learn really Rasa, go on RASa official site

HI nithikpackt !
Sorry for previous comment, sadly I was still very ignorant about Rasa and I superficially leafed through your excellent book;
very sorry!
Great book and great work...
thanks again


Standardise test structure and naming conventions

We've got a bit of a mismatch of conventions here between the original set of tests in Program.cs, the legacy tests I imported and new tests that have been written by later contributors. I don't really care which convention we go with, but I suggest standardising on file name (Program.cs seems a bit out of sync), test method name (we've got both Pascal case and underscores for word breaks), and test structure (there's a bunch of arrange / act / assert and more terse implementations).
I'm happy to leave the decision on how they're formatted to whoever wants to pick this up, main thing is to have conventions that others can come along and easily replicate.

With #29 merged, this should also have been addressed.

Hmmm... not really, still very different conventions and structures. I'm not overly precious about it other than the fact that those who come after us are still faced with some doing arrange / act / assert and others not, some pluralising "test -> tests", the MyAddressExtractorTest class sitting in the Program.cs file etc.


V3.6.0 and v3.6.1 not working on iPhone 6

Describe the bug
This version just doesn't work on iPhone 6 if it's supposed to on iPhone 6. Then a fix is needed for people that are having these issues.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Screenshots

Device (please complete the following information):

iOS Version: 12.4
iOS Device: iPhone 6
unc0ver Version: 3.6.0

Place an "x" between the brackets if true:

[x] this is a bug others will be able to reproduce
[x] this issue is present with all tweaks uninstalled(except for default packages) or disabled
[x] this issue is present after a rootfs restore
[x] this issue is present on the latest version of unc0ver

Logs
diagnostics.plist.txt

V3.6.2 is out and it works fine for  iphone 6..i got mine done with no problem.

Duplicate #1445
Also, it’s fixed in the latest version.
Sent with GitHawk

Duplicate #1444


Change mask on the fly

I need to change mask depending on country code
So if i have +44 the mask will be [99] [99] [9999] [9999]
And if i had +47 - [99] [99] [999] [999]
But when i trying to do that it doesn't work
  switch(countryCode) {
    case('44'):
      return this.setState({mask: '[99] [99] [9999] [9999]'})
    case('47'):
       return this.setState({mask: '[99] [99] [999] [999]'})
}

works for me, see my example:
renderHomePhone() {
	let { homePhone } = this.state;
	let mask = "[00]-[0000000]"; //default
	let placeholder = "02-000000" //default
	if (!homePhone) homePhone = ""; //handle undefined
	if (homePhone.substring(0, 2) == "07") {
		mask = "[000]-[0000000]"; //alternative mask
		placeholder = "070-000000" //alternative placeholder
	}
	return (<TextInputMask
		underlineColorAndroid="transparent"
		keyboardType="phone-pad"
		autoCapitalize="none"
		returnKeyType="done"
		onChangeText={this.onHomePhoneChanged()}
		value={homePhone}
		autoCorrect={false}
		placeholder={placeholder}
		mask={mask} />)
}

onHomePhoneChanged() {
	return (homePhone) => {
		this.setState({ homePhone });
	}
}

@yoavapi, what is your version of release, I use 0.5.2 as later crashes.

@alpamys-qanybet
I use 0.7.0

This should be working in the latest version


Container launcher collects CCEL data + CCEL ACPI table for TDX CS

It looks like Jiankun's previous PR has implemented the functionality to collect the CCEL. https://github.com/google/go-tpm-tools/pull/478/files

Jiankun's PR https://github.com/google/go-tpm-tools/pull/478/files already had such changes, reverting it now.


Layer not being scanned when parent is specified

This is similar to the issue #241, in the sense that I'm getting the same error.
I'll try to give all of the information that I can, please let me know if there's anything else I can give to help.  This is a scan using Klar, through to Clair.
First, the Klar debug messages I've added:
Analysing 8 layers
Layer 7:
 -- Name: sha256:03359f666646670c54cbb04583a0b2b8bd3cda11d2226c4261c6971c8839fb6b
 -- Path: https://****.amazonaws.com/v2/myrepository/blobs/sha256:03359f666646670c54cbb04583a0b2b8bd3cda11d2226c4261c6971c8839fb6b
 -- ParentName:
Layer 6:
 -- Name: sha256:188ea52cfdaa9f14ea50948b20301fd96aa8591ae5e83a1a83687ba3c5da86f3
 -- Path: https://****.amazonaws.com/v2/myrepository/blobs/sha256:188ea52cfdaa9f14ea50948b20301fd96aa8591ae5e83a1a83687ba3c5da86f3
 -- ParentName: sha256:03359f666646670c54cbb04583a0b2b8bd3cda11d2226c4261c6971c8839fb6b
Layer 5:
 -- Name: sha256:2705e2b0688be17e9554ce259abc84b938a4a1ee3a19e20f3f181e71bb8fb7c8
 -- Path: https://****.amazonaws.com/v2/myrepository/blobs/sha256:2705e2b0688be17e9554ce259abc84b938a4a1ee3a19e20f3f181e71bb8fb7c8
 -- ParentName: sha256:188ea52cfdaa9f14ea50948b20301fd96aa8591ae5e83a1a83687ba3c5da86f3
Layer 4:
 -- Name: sha256:7e7b4a891350f208368ef691e81cc88daa712a9dce5f2f1aa6ef9be62e39431c
 -- Path: https://****.amazonaws.com/v2/myrepository/blobs/sha256:7e7b4a891350f208368ef691e81cc88daa712a9dce5f2f1aa6ef9be62e39431c
 -- ParentName: sha256:2705e2b0688be17e9554ce259abc84b938a4a1ee3a19e20f3f181e71bb8fb7c8
Layer 3:
 -- Name: sha256:60d31e3372ffff97dae39e25c7a0420b5f04dd2370d72ef3db5dec37f336a2b5
 -- Path: https://****.amazonaws.com/v2/myrepository/blobs/sha256:60d31e3372ffff97dae39e25c7a0420b5f04dd2370d72ef3db5dec37f336a2b5
 -- ParentName: sha256:7e7b4a891350f208368ef691e81cc88daa712a9dce5f2f1aa6ef9be62e39431c
Layer 2:
 -- Name: sha256:27c50fcb0e3d7b6c1494d318706524f299d0ffecd286bca94f5573e24cd2be39
 -- Path: https://****.amazonaws.com/v2/myrepository/blobs/sha256:27c50fcb0e3d7b6c1494d318706524f299d0ffecd286bca94f5573e24cd2be39
 -- ParentName: sha256:60d31e3372ffff97dae39e25c7a0420b5f04dd2370d72ef3db5dec37f336a2b5
Layer 1:
 -- Name: sha256:26c9e012ae137d4815bd4191c0130b994e374cc74a371e0c7d9e3880afb78a7a
 -- Path: https://****.amazonaws.com/v2/myrepository/blobs/sha256:26c9e012ae137d4815bd4191c0130b994e374cc74a371e0c7d9e3880afb78a7a
 -- ParentName: sha256:27c50fcb0e3d7b6c1494d318706524f299d0ffecd286bca94f5573e24cd2be39
Push layer 1 failed: Push error 422: {"Error":{"Message":"worker: OS and/or package manager are not supported"}}

Layer 0:
 -- Name: sha256:d3aeceeb0289bf97c2474366cfcdaf66e29b409d45d6ed91be3335f16915f1b0
 -- Path: https://****.amazonaws.com/v2/myrepository/blobs/sha256:d3aeceeb0289bf97c2474366cfcdaf66e29b409d45d6ed91be3335f16915f1b0
 -- ParentName: sha256:26c9e012ae137d4815bd4191c0130b994e374cc74a371e0c7d9e3880afb78a7a
Push layer 0 failed: Push error 400: {"Error":{"Message":"worker: parent layer is unknown, it must be processed first"}}

Analyse image https://****.amazonaws.com/v2/myrepository:latest failed: Analyze error 404: {"Error":{"Message":"the resource cannot be found"}}

Then we have the Clair --log-level=debug messages:
2017-08-01 19:31:21.548461 I | v1: <IP_ADDRESS>:40646 "POST /v1/layers" 201 (4.304388ms)
2017-08-01 19:31:21.560767 I | v1: <IP_ADDRESS>:40646 "POST /v1/layers" 201 (4.655715ms)
2017-08-01 19:31:21.566606 I | v1: <IP_ADDRESS>:40646 "POST /v1/layers" 201 (3.411583ms)
2017-08-01 19:31:21.572435 I | v1: <IP_ADDRESS>:40646 "POST /v1/layers" 201 (3.221274ms)
2017-08-01 19:31:21.579362 I | v1: <IP_ADDRESS>:40646 "POST /v1/layers" 201 (4.209883ms)
2017-08-01 19:31:21.585636 I | v1: <IP_ADDRESS>:40646 "POST /v1/layers" 201 (3.682535ms)
2017-08-01 19:31:24.007154 W | clair: layer sha256:26c9e012ae137d4815bd4191c0130b994e374cc74a371e0c7d9e3880afb78a7a: Layer's namespace is unknown but non-namespaced features have been detected
2017-08-01 19:31:24.007801 I | v1: <IP_ADDRESS>:40646 "POST /v1/layers" 422 (2.419716605s)
2017-08-01 19:31:24.013049 W | clair: layer sha256:d3aeceeb0289bf97c2474366cfcdaf66e29b409d45d6ed91be3335f16915f1b0: the parent layer (sha256:26c9e012ae137d4815bd4191c0130b994e374cc74a371e0c7d9e3880afb78a7a) is unknown. it must be processed first
2017-08-01 19:31:24.013664 I | v1: <IP_ADDRESS>:40646 "POST /v1/layers" 400 (3.213397ms)
2017-08-01 19:31:24.017053 I | v1: <IP_ADDRESS>:40646 "GET /v1/layers/sha256:d3aeceeb0289bf97c2474366cfcdaf66e29b409d45d6ed91be3335f16915f1b0?vulnerabilities" 404 (1.564362ms)

Now, in the other issue threads that I've seen, I can see that this typically means that I need to specify what the parent is, otherwise the current layer being scanned's version isn't visible to Clair.  What's confusing, though, is that if you look in the Klar logs the Parent layer is being set.  Per the advice on #241 I did also go into the database and start poking around, and I found the layers table, which contained the following:
clairdb=> SELECT * FROM layer;                                                                                id |                                  name                                   | engineversion | parent_id | namespace_id |          created_at
----+-------------------------------------------------------------------------+---------------+-----------+--------------+-------------------------------
 10 | sha256:03359f666646670c54cbb04583a0b2b8bd3cda11d2226c4261c6971c8839fb6b |             3 |           |              | 2017-08-01 20:38:11.159211+00
 11 | sha256:188ea52cfdaa9f14ea50948b20301fd96aa8591ae5e83a1a83687ba3c5da86f3 |             3 |        10 |              | 2017-08-01 20:38:11.298273+00
 12 | sha256:2705e2b0688be17e9554ce259abc84b938a4a1ee3a19e20f3f181e71bb8fb7c8 |             3 |        11 |              | 2017-08-01 20:38:11.815988+00
 13 | sha256:7e7b4a891350f208368ef691e81cc88daa712a9dce5f2f1aa6ef9be62e39431c |             3 |        12 |              | 2017-08-01 20:38:11.935477+00
 14 | sha256:60d31e3372ffff97dae39e25c7a0420b5f04dd2370d72ef3db5dec37f336a2b5 |             3 |        13 |              | 2017-08-01 20:38:12.143668+00
 15 | sha256:27c50fcb0e3d7b6c1494d318706524f299d0ffecd286bca94f5573e24cd2be39 |             3 |        14 |              | 2017-08-01 20:38:15.763457+00
(6 rows)

So the "Parent" layer is scanned in the database.
At this point I'm out of ideas of anything that I'm specifically doing wrong, so I was wondering if there is something that you know that I don't :).
Thanks,
Kirk

I have run into this same problem and it is a major blocker to integrating Clair in our devops pipeline.  I've found that many recent and popular images from Docker Hub cannot be scanned without encountering a 422 error when POSTing layers to Clair such as tomcat:7-jre8, postgres:9.5.3 (versions prior to 9.5.3 work but later versions do not), python:3.5, nginx:1.12-alpine, redis:3, nginx:3.5, and openjdk:7.
I've noticed a few things in researching the issue that may be relevant and not mentioned in the original post.  All my testing has be done using Clair run from the docker image quay.io/coreos/clair:v2.0.1 and the klar-1.4.1-osx-amd64 downloaded from the klar releases page.
Clair will log a warning about a different feature name and version each time when the offending layer is POSTed in.  For example, running  klar tomcat:7-jre8
I will see the following line in the Clair logs
{"Event":"Namespace unknown","Level":"warning","Location":"worker.go:211","Time":"2017-08-28 20:13:36.031713","feature name":"init-system-helpers","feature version":"1.48","layer":"sha256:eb9b7457396558f37d230d8cb10dc083fb304895030d40ce8b54598e176546ec"}
{"Event":"Handled HTTP request","Level":"info","Location":"router.go:57","Time":"2017-08-28 20:13:36.031956","elapsed time":316097842,"method":"POST","remote addr":"<IP_ADDRESS>:23672","request uri":"/v1/layers","status":"422"}
After running that same command again however I see
{"Event":"Namespace unknown","Level":"warning","Location":"worker.go:211","Time":"2017-08-28 20:15:51.353136","feature name":"xz-utils","feature version":"5.2.2-1.2","layer":"sha256:eb9b7457396558f37d230d8cb10dc083fb304895030d40ce8b54598e176546ec"}
{"Event":"Handled HTTP request","Level":"info","Location":"router.go:57","Time":"2017-08-28 20:15:51.353383","elapsed time":340072038,"method":"POST","remote addr":"<IP_ADDRESS>:28774","request uri":"/v1/layers","status":"422"}
So the feature name and version before the 422 error is returned seem to be random.
Even more interesting, sometimes if I build the image on a different platform and different version of docker, it will scan successfully.  Using https://github.com/docker-library/tomcat/blob/master/7/jre8/Dockerfile I can build the tomcat:7-jre8 image in CircleCI which uses Docker version 1.9.1 and this image will scan successfully.  Docker inspect shows that the publicly available tomcat:7-jre8 image that does not scan was built with docker version 17.03.2-ce.
Most of the publicly available images I've found built with 1.9 or earlier will scan and most built with 1.10 or later fail.  For example postgres:9.5.2 which was built with 1.9.1 will scan, but postgres:9.5.3 which was built with 1.10.3 will fail.  But there are some exceptions to that rule such as nginx:1.12 (not the -alpine image) was built with <IP_ADDRESS>-ce and will scan.  This leads me to suspect this issue may be related to changes in 1.10.  Specifically the Content Addressable Storage and registry changes in 1.10 were recognized to have break compatibility with earlier versions https://docs.docker.com/registry/compatibility/.

In Clair v2, you cannot name layers by their content addressable SHA256. You must name them globally unique. This means that clients need to do something like concatenating the digest of the image manifest with the layer digest and use that as the layer name. Without it, you can accidentally merge histories together and get completely broken results.
I can see from your logs that Klar does not name the layers correctly from your logs. This is a bug in upstream Klar that needs to be fixed before we even begin to speculate other causes.
This requirement for naming is fixed in the upcoming Clair v3 API in order to prevent users from shooting themselves in the foot like this.

I can see from your logs that Klar does not name the layers globally unique. This is a bug in upstream Klar that needs to be fixed before we even begin to speculate other causes of failures.

Thanks for the reply, I have opened an issue about this with Klar .

This issue has been resolved by fixing the digest, as @jzelinskie had suggested.  Follow the link @owms provided to see the go implementation that solved this issue on our end.


Create about us page

What:

Create the about us and its components
Create a new sanity schema to manage the content from the about us page
Integrate the sanity API with the new page

Why:
Closes: https://app.asana.com/0/1168997577035609/1199626142937663/f
How:

Adding a new page in the pages folder that will contain the about-us page
Creating new components for the page following the design

Preview
https://602c5d0507e7980008d5ee53--tdc-home.netlify.app/about-us/
Media
https://www.loom.com/share/ee0345bbf6f14179af2f56215ac0da00

LGTM! Let's wait on the copy before deploying

@duranmla I just addressed your comment about the x-spacing. I will merge this


Ansible Terminal no longer has color for Ansible-Navigator

Summary
VSCode Ansible extension in version 2.8.108 has color in terminal when right-clicking in a playbook and doing Run Ansible Playbook via 'ansible-navigator run'. When upgrading to 2.9.118 all color is lost and text only shows as white.
If running directly from bash terminal, ansible-navigator does display color. Issue appears only when using extension version 2.9.118
Extension version
2.9.118
VS Code version
1.85.1
Ansible Version
ansible [core 2.15.8]
  config file = /home/adworjan/ansible/playbooks/AnsibleGit/ansible.cfg
  configured module search path = ['/home/adworjan/ansible/playbooks/AnsibleGit/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3.9/site-packages/ansible
  ansible collection location = /home/adworjan/ansible/playbooks/AnsibleGit/.ansible/collections:/usr/share/ansible/collections
  executable location = /usr/bin/ansible
  python version = 3.9.18 (main, Sep 22 2023, 17:58:34) [GCC 8.5.0 20210514 (Red Hat 8.5.0-20)] (/usr/bin/python3.9)
  jinja version = 3.1.2
  libyaml = True

OS / Environment
Red Hat Enterprise Linux 8.9 (Ootpa), ansible-lint 6.14.3
Relevant log output
No response

What is the result of running the comman below in the vscode terminal?
python3 -c "import sys; print(sys.stdout.isatty())"

If that is not True it might explain why is not colored.

It returns true on the VM itself, it returns false if I run it inside the EE. That's true with both versions of the extension, which still points to something changing within the extension itself


Install only agent with config file;  need more exemple / clear documentation ...

So ... installing K3S is : curl -sfL https://get.k3s.io | sh -
Installing K3S agent is more like : curl -sfL https://get.k3s.io | env K3S_SERVER=... K3S_TOKEN=... sh -
But i already have my /etc/rancher/k3s/config.yaml file created ( and populed ) ...
So how to install only the agent without re-specified all value in the commande ?
after reading the unclear documentation seem to be curl -sfL https://get.k3s.io | env INSTALL_K3S_EXEC=agent sh -
but that remove the k3s folder with my config.yaml  !

K3s does not ever write a config.yaml file. You may use a config file in place of any environment variable or CLI flag, with the caveat that installer variables that determine whether to install an agent or server will not be read from the config file, so you must specifically tell the installer to create an agent. The yaml keys are the same as CLI flag names.
Instead of doing
curl -sfL https://get.k3s.io | env K3S_SERVER=... K3S_TOKEN=... sh -`

You could instead do:
mkdir -p /etc/rancher/k3s
cat <<EOF >/etc/rancher/k3s/config.yaml
server: https://server:6443
token: my-token
EOF
curl -sfL https://get.k3s.io | INSTALL_K3S_EXEC=agent sh -
``

The uninstaller will remove /etc/rancher/k3s; is that perhaps what you're seeing?
Ho i run the uninstaller when i see the curl command didn't install the agent on my first try, so you right !

i already have a little scrip that generate the config.yam with good interface ip and good name for my nodes
also download a registries.yaml ^^
I think just adding curl -sfL https://get.k3s.io | env INSTALL_K3S_EXEC=agent sh - as another option to install only agents in the qwick-start guide is a good things ...

Closing as this isn't in our current plans