Create alternative way to use testcontainers in MUnit using fixtures

🚀 What is included in this PR?
This PR includes an alternative way (more idiomatic) of using TestContainers with MUnit using fixtures.
Some examples:
class MysqlSpec extends FunSuite with TestContainersFixtures {

  val mysql = ForEachContainerFixture(MySQLContainer())

  // You need to override `munitFixtures` and pass in your container fixture
  override def munitFixtures = List(mysql)

  test("test case name") {
    // Inside your test body you can do with your container whatever you want to
    assert(mysql.container.jdbcUrl.nonEmpty)
  }
}

class MysqlSpec extends FunSuite with TestContainersFixtures {

  val mysql = ForAllContainerFixture(MySQLContainer())

  // You need to override `munitFixtures` and pass in your container fixture
  override def munitFixtures = List(mysql)

  test("test case name") {
    // Inside your test body you can do with your container whatever you want to
    assert(mysql.container.jdbcUrl.nonEmpty)
  }
}

class MysqlSpec extends FunSuite with TestContainersFixtures {

  val mysql = ContainerFunFixture(MySQLContainer())

  mysql.test("test case name") { container =>
    // Inside your test body you can do with your container whatever you want to
    assert(container.jdbcUrl.nonEmpty)
  }
}

@alejandrohdezma thank you so much! This looks great!
Would you mind adding a few examples to the readme?


Try to query the Domain objects first in middleware. Then fall back to Header & DNS.

It looks like we're actually using fully qualified URL's (http, https, paths) in the Domain modeling, which was there to support subprojects & translations. However, I think we need to just be storing the actual Domain as unique, and using subproject & translation modeling to create appropriate domains for those projects.
This adds that, and switches to using proper Domain objects on CNAME resolution as the first choice. This makes it so people can use CDN's and other things that break CNAME's currently.

LGTM, though I noted a change to the html template that wasn't part of the PR here. It's just a small change though

What change in the template?


GetOrCreateAsync's factory should use ConfigureAwait

GetOrCreateAsync's factory should use with ConfigureAwait false, as some UI applications might block on the UI thread.

Added ConfigureAwait(false) in GetOrCreateAsync
Added a test to cover the issue.
Added two helper classes for the tests. Helper classes comments' indicated their original source.

Not sure if tests falls into the 'too hard' category, because of the helper classes.
Addresses #2252

@anurse and @Tratcher please review thid PR.

@Pilchie please suggest reviewers

@rynowak had some thoughts about ConfigureAwait in these libraries, specifically that its not worth trying to test all of the code paths and instead use an analyzer to make sure all the places have ConfigureAwait(false).
cc @JamesNK

@davidfowl , I am happy to with the analyzer instead of tests, could you suggest one?

I have setup Microsoft.CodeAnalysis.FxCopAnalyzers in https://github.com/grpc/grpc-dotnet
It comes with a lot of analyzers. I have disabled most of them but ConfigureAwait false is still enabled: https://github.com/grpc/grpc-dotnet/blob/master/Grpc.DotNet.ruleset

I suppose I need to run GenerateReferenceSource or GenerateReferenceAssemblies to resolve build issues.

When Directory.Build.target defines the build Reference to FxCopAnalyzer and as well as CodeAnalysisRuleset, I get a build error because ref/*.csproj-s are not updated.

eng/targets/ResolveReferences.targets(200,5): error MSB3245: Could not resolve this reference. Could not locate the package or project for "Microsoft.CodeAnalysis.FxCopAnalyzers". Did you update baselines and dependencies lists? See docs/ReferenceResolution.md for more details.

When I  move
  <ItemGroup>
    <Reference Include="Microsoft.CodeAnalysis.FxCopAnalyzers" />
  </ItemGroup>

to Directory.Build.props, and run the script that updates the ref/ projects, then build.cmd, I get the following error:

C:\Users...\source\repos\Extensions.dotnet\sdk\5.0.100-alpha1-015536\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.DefaultItems.targets(256,5): error NETSDK1023: A PackageReference for 'Microsoft.CodeAnalysis.FxCopAnalyzers' was included in your project. This package is implicitly referenced by the .NET SDK and you do not typically need to reference it from your project. For more information, see https://aka.ms/sdkimplicitrefs [C:\Users...\source\repos\Extensions\src\Caching\Abstractions\ref\Microsoft.Extensions.Caching.Abstractions.csproj]

What would be the suggested way to resolve this issue?

Looks like we probably have to add this to the references list: https://github.com/aspnet/Extensions/blob/master/docs/ReferenceResolution.md#example-adding-a-new-dependency
@anurse @JamesNK - can you help with that?

Step 1 and 2 there should be all that's needed, I believe. Adding the <Reference> element to the project and then the <LatestPackageReference> element to the eng/Dependencies.props file. While this package does comes from "another dotnet team", it's dotnet/roslyn-analyzers which is not part of our dependency flow process, so there's no need to go through step 3.
@ladeak let me know if you have any issues making those updates!

@anurse , I have added the Dependency to the "External dependencies":
https://github.com/aspnet/Extensions/pull/2767/files#diff-8c508e8b957801ef7a859521e59d58b9 but still returns a build error:
eng/targets/ResolveReferences.targets(200,5): error MSB3245: Could not resolve this reference. Could not locate the package or project for "Microsoft.CodeAnalysis.FxCopAnalyzers". Did you update baselines and dependencies lists? See docs/ReferenceResolution.md for more details.

@anurse Could you suggest, I did those two steps as suggested, but I still get errors.


Async improvements

Check: https://developers.home-assistant.io/docs/asyncio_working_with_async/
E.g. need to add some await when pulling states for price and energy.

no need


[Storage] Use Eslint plugin

We are planning on removing .eslintrc.old.json file and this PR removes its use in storage packages. See https://github.com/Azure/azure-sdk-for-js/issues/11256.

With this merged, do we have to fix all the linting errors if any?

With this merged, do we have to fix all the linting errors if any?

The output from the linter will continue to be published to the html file as listed in the lint script in the package.json file.
#10782 is tracking the work required to fix the linting errors.
Once all errors are fixed, we will remove the output to html file so that any future linting errors will break the build in the PR


However the issue with the above svg is that the gradient does not cover the shape and is padded.
You will find in the source code a note saying:
{
SpreadMethod is not implemented
Assumed to be repeat for LinearGradient and pad for RadialGradient
}
The reason it is not implemented is that is kind of hard to do with GDI+
However if the gradient area is equal or larger than the filled are it should work.  In most svgs  probably including yours, when this is not the case it is by accident and not by design.  For example the following svg now renders fine:
<svg
  xmlns:xlink="http://www.w3.org/1999/xlink"
  viewBox="200 230 100 60">

<linearGradient
   y2="245"
   x2="260"
   y1="220"
   x1="200"
   gradientTransform="translate(20,20)"
   gradientUnits="userSpaceOnUse"
   id="linearGradient2833"
   xlink:href="#linearGradient4944" />
<linearGradient
   id="linearGradient4944">
  <stop
     id="stop3448"
     offset="0" />
  <stop
     id="stop3450"
     stop-color="#f5f5f5"
     stop-opacity=".9608"
     offset="1" />
</linearGradient>

<rect
   style="fill:#053cac;stroke:url(#linearGradient2833);stroke-width:10"
   id="rect2829"
   height="25"
   width="60"
   y="240"
   x="220" />
</svg>

It is easier to use the default gradientUnits and use percentages to fill the area:
<svg
  xmlns:xlink="http://www.w3.org/1999/xlink"
  viewBox="200 230 100 60">

<linearGradient
   y1="0"
   x1="0"
   y2="1"
   x2="1"
   id="linearGradient2833"
   xlink:href="#linearGradient4944" />
<linearGradient
   id="linearGradient4944">
  <stop
     id="stop3448"
     offset="0" />
  <stop
     id="stop3450"
     stop-color="#f5f5f5"
     stop-opacity=".9608"
     offset="1" />
</linearGradient>

<rect
   style="fill:#053cac;stroke:url(#linearGradient2833);stroke-width:10"
   id="rect2829"
   height="25"
   width="60"
   y="240"
   x="220" />
</svg>


onLongPress

Hi there,
I was wondering if it is possible to use the package without having to longpress a button?
I want to have the focused_menu pop up after just one click but not sure how to do this or if this is possible?
Sorry for creating an issue for this but wasn't sure how to ask this question otherwise!
Thanks in advance

Already done on #8

Merged!


(wip) feat (AMBER-534) Added remaining Sidebar data (private artworks)

The type of this PR is: feat

This PR solves AMBER-534
Description
Adding remaining data to sidebar ("Exclusive Access" section with link to gallery page)

skipping the second test for a sec while I fix the link! the test isn't picking it up the link or text for some reason. brb.


documents: fix Flask-Login import

As discussed on Hangouts/Gitter, running nosetests invenio/modules/documents/testsuite/test_api.py is currently broken due to a broken import in invenio/modules/documents/documentext/fields/base.cfg, similar to https://github.com/inveniosoftware/invenio/commit/0875c0570b99f77af5a715ed35857c506b6e8bbf.

Uh, I was under the impression that 1/2 spaces before the bullet point were mandatory. Sorry for the emails.


Max depth should always be read from the configuration

Reading the DocumentDB.MAX_DEPTH should be discouraged, and all components should read the value from the DocsApiConfiguration.getMaxDepth(). This would allow dynamic depth for different collections in the future. Also it would make current unit testing more efficient.

This is fixed by #1270. @EricBorczuk fyi


[Quais] - Support building mined transactions

User needs to be able to submit a mined transaction.  Quais needs to comport to GoQuai.
When you make a transaction, you must get the previous header, and then put the transaction in the header and submit it.
After that - we will need to be able to mine it.
It is not clear on what the additional fields are for the mined transactions - is this the same or different from work objects?  @kiltsonfire

Is this a duplicate of #29?

Update from #25:
This allows users to specify the amount of work they want to have on a transaction being pushed through so that it can be included in the block in the correct order.
Question: Do we also need to have a field for time, so that if the work done is not done in a certain time, the transaction is canceled?

From #29 👍
Requirements:
-add optional field at the end that specifies work threshold.
-If a work threshold is not specified we will return a transaction that has been hashed one time


[feature-request] Add webp polyfill

What
It would be cool if you could include a webp polyfill in your service (maybe webp-hero).
Details
I regularly use WebP to reduce my file size, but I also have to support IE11 which does not support this format. And because I really like your service and use it for other polyfills too it would be great if you could integrate one for WebP.
Additional information

WebP is an image format employing both lossy and lossless compression. It is currently developed by Google, based on technology acquired with the purchase of On2 Technologies.

Browser polyfill for the webp image format.

webp images come alive, even in safari and ie11! (firefox and edge now support webp)
webp-hero actually runs google's libwebp decoder in the browser — it converts webp images to png's on-the-fly
webp-hero's polyfill functionality renders decoded image data to a hidden canvas, and converts that to a png data url which is then displayed to the user

https://github.com/chase-moskal/webp-hero

Hi, I don't think we will add a polyfill for webp, it is a very large polyfill and only works in some scenarios (does not work for webp images used in CSS). I would recommend using the srcset attribute on an IMG tag and serving PNG or jpeg to browsers which don't have webp support


How can tabnine be globally disabled?

Sometimes it uses too much CPU. I'd like to know how I could disable it for all editors. Thanks

Hi.
We've made several fixes lately that improve TabNine's cpu and memory consumption.
TabNine should now require less resources, especially when idle in the background, so I suspect this request might be less relevant for the latest version.
Can you try out the latest (2.5.1), and let us know if you think it might still be relevant?

Ok, will check. In the meantime, can it be disabled globally? For my knowledge :)

No way to disable it globally currently, I'm afraid. You have to do it one by one


Thread support

Current implementation adds support for slack threading.
Currently, slack supports thread notification using "chat.postMessage".
In order to use threads a bot user with the support of "chat.postMessage"
need to be used.
Slack hooks currently don't have a thread support.

@steven-foster I will take a look this weekend. In the meantime, would you be able to do a review?

I've managed to modify my slack bot commands and jenkins jobs to use thread support and we are extremely happy with the result.
I would be happy to help merging this in master :)

Sorry I didn't see your message @kmadel. I'm not a Java developer really, nor very familiar with the codebase of this plugin so I'm not totally sure about the implementation of this feature. It seems fine, and it works.
I noticed that the description for bot user and the slack docs seem like they contradict each other.

Pass true to post the message as the authed user, instead of as a bot.

but it seems to work anyway?
Also, a big improvement to this feature would be a full-flow example of posting a message and adding thread replies to it. Currently I have trouble with finding the correct thread_ts.

Hello @steven-foster, us use Hubot robot.
I would need some help from you to write the correct documentation. Probably I will miss some steps...
Steps:

Each Slack message that is received in hubot app has a special object (msg)
When a new message is received from a channel a timestamp is set on msg.message.rawMessage.ts (Slack message timestamp).
To make hubot respond in a thread you should set msg.message.thread_ts = msg.message.rawMessage.ts.
From this moment all messages that will be written using msg object will be written under msg.message.rawMessage.ts
Obs: if you communicate with your hubot in a thread msg.message.thread_ts will already be set on
msg.message.rawMessage.ts

Jenkins side

I've added a new param to all of my buildflows (named slack_room). This parameter is filled by hubot with a slack room and a thread_ts (msg.message.room + ":" + msg.message.thread_ts)
I've created a new secret key to be used ( jenkins-key from slack app, it's a new hubot app token created in slack) (👎 jenkins-slack token will not work)
Then, in my buildflows I've checked botUser, I've used my created jenkins-key and fill up the room with $slack_room (room:thread_ts)

I will help you merge this feature as fast as you wish.

Hi @iulianstana, thanks for the explanation. I was doing something similar but not with hubot. I got some feedback from people who just wanted to add threads to the messages they sent with the slack plugin, so that's why I was curious about your workflow.
I made a PR for your repo (this PR) which returns a response object from the pipeline step with all the info needed to send a thread. My java isn't too strong, so let me know if it's a good approach.

@kmadel Resolved conflict with master. Would you like from me to add some additional documentation?

@kmadel Can I help you with this PR?


Source/Github dependency on a plugin gives me an obscure NPE, while file dependency of the same code works fine.

https://groups.google.com/d/topic/simple-build-tool/z5-YUQEuoqE/discussion

sorry, this is a duplicate of #352 ...


Update concepts page

Please update the "package" definition in AWS CodeArtifact concepts page to include NuGet as a package manager supported.

Created a pull request with fix. See https://github.com/awsdocs/aws-codeartifact-user-guide/pull/11

@tjohn123456 issue created

Closing this as the PR is merged, thanks again @tjohn123456 !

Closing this as the PR is merged, thanks again @tjohn123456 !


Overwrite implicitly defined mirrored associations with self by default

Thank you all for your work on this project. It's been simply amazing to work with!
Problem this feature will solve
Let's say I have two models with a one-to-one association between them. I want to have factories for each of them, and, by default, fill in these associations as well. Creating either factory should create one instance of both models.
Desired solution
I would love to be able to do that in the following manner:
factory :user do
  comment
end

factory :comment do
  user
end

In this case, when calling FactoryBot.create(:user), I expect one user and one comment associated with each other to be created. When FactoryBot calls the comment factory from the user factory, it should fill in the user field with the user that is already being built. Then:
FactoryBot.create(:user) # Should create one user and one associated comment
# Instead, each factory keeps calling the other in an infinite loop of association building.

Alternatives considered
This can be achieved in the current version by doing:
factory :user do
  comment { association :comment, user: instance }
end

factory :comment do
  user { association :user, comment: instance }
end

but that is quite verbose and a little less readable (in my opinion).

Additional context
I am not the most proficient with FactoryBot or Rails in general, so please let me know if there are any alternative solutions!
Feedback & your other thoughts are also very welcome.
Thanks again for all of your work!

Thanks for the kind words @rjclaasen in the name of everyone that has contributed to factory bot. From a rough read of the associations creation process(lib/factory_bot/declaration/association.rb) in order to address this issue, I would say we could check if the invoking factory has an association to the current factory and then access the instance before creating a new value. But in order to do that we couldn't stop at one "level" deep of the declaration, it could go a few layers deep easily. This sounds like a graph traversal to find a cycle to me and seems like overkill to run it every-time an association is created. The example you provided is a similar to the one expressed here but take a look at the warning:
Note that this approach works with build, build_stubbed, and create,
but the associations will return nil when using attributes_for.

Also, note that if you assign any attributes inside a custom initialize_with
(e.g. initialize_with { new(**attributes) }), those attributes should not refer
to instance, since it will be nil.

To decide which value to pick by default might get hairy because the invoking factory would be dictating what value to use here, and overrides once the nesting(one factory calls another ...) gets going I don't really know if there's a clear way to get there.
There are other strategies using transient attributes that will give you better control on the lifecycle of the attributes that are added. You can find examples on how to use transients here and also a more intricate example with associations on this post I hope this gives you an idea of some alternatives. If you can illustrate other use cases for a change of behavior on how we create associations, please use the repro script on the repo, and if you are so kind please elaborate on how the change on API would impact other associations. Thanks.

@rjclaasen have you tried any of the alternatives? Would you say that any of them addresses your concern?

I have chosen to use the verbose alternative as specified in the original post.
Thanks for all the help!


Add post method support to OneLogin_Saml2_Auth.process_slo

AE-2147
changed signature of auth.process_slo to include method_data='get_data'
changed signature of logout_response.is_valid
added method_data to auth_test

Coverage decreased (-0.7%) to 95.645% when pulling 739a32c2d5e82f5f9cb2d7c3d8130423b32be6ea on mmargetts:AE-2147 into 3da33a7248013fc8e9a0d1aa576cad05ccca6266 on onelogin:master.

Is not that simply. HTTP-POST binding is more complex that simply be able to read the POST parameter,  for example the signature is embedded instead of be part of a GET parameter


Autocompletion in shell adapter

I think many users of hubot would like to achieve ability to autocomplete commands in their day to day activities. Not all chats allows to autocomplete for bots, but shell certainly has this ability
( https://preview.npmjs.com/package/cline ) , which means it could be added as an optional integration feature to adapters API and implemented in Shell adapter so that in future it could be supported by any adapter.
Use case:

Developer introduce respond entry:

  robot.respond /run (job|script|car|source_build)/i, (res) ->
      # run something

User runs bin/hubot --name hubot
User types "hu" and press Tab
Shell attaches "bot" to line
User types space then "r" and then press Tab
Shell attaches "un" to line
User types space then "sc" and then press Tab
Shell attaches "ript" to line
User erases "script", types "s" and press Tab
Shell prints variants to choose: "script source_build"
User prints "o", press Tab
Shell attaches "urce_build" to line
User erases "source_build" and press Tab
Shell prints variants to choose: "job script car source_build"

Replaced shell with readline implementation. Let's try that.


Very good, does it currently support the deployment of the Baichuan model?

Thanks

Since the model structure of baichuan is the same as that of LLaMa, TurboMind also supports baichuan-7B.
Check this documentation to infer it. https://github.com/InternLM/lmdeploy/blob/main/docs/zh_cn/serving.md
Note that we haven't tested it yet, so you'll have to update some configurations like bos and eos.  @hljjjmssyh

@tpoisonooo  thanks.

deploy.py needs some fix for baichuan packed attention qkv weight QaQ

@hljjjmssyh  I have tried baichuan-13B-chat,  baichuan using it's tokenization here https://huggingface.co/baichuan-inc/Baichuan-13B-Chat/blob/main/tokenization_baichuan.py,   lmdeploy preprocess (tokenization) not compatible with baichuan now.
Unless you only need turbomind doing inference.

Do you mean that if I use turbomind for baichuan, I need to rewrite the tokenizer ?

Yes.

Do you mean that if I use turbomind for baichuan, I need to rewrite the tokenizer ?

Yes.

Hi, Can you give me some guidance on how to use Baichuan tokenizer and what possible changes I may need to make?

What is the status of this issue now? Any updates?

7B can be supported. But 13B cannot yet

可以支持7B。但13B还不能

The difference between baichuan-13B and 7B is mainly that the rotary encoding is removed and the alibi encoding is added. The original FasterTransformer framework has a linear_bias_slopes parameter that can implement alibi encoding, and the alibi encoding is calculated as follows:
if (true) {    invokeBuildAlibiSlopes(linear_bias_slopes_, head_num_, stream_); }
Then add linear_bias_slopes to the input tensor of decoder and contextDecoder,
if (true) {    decoder_input_tensors.insert({"linear_bias_slopes",                                    Tensor(MEMORY_GPU,                                           data_type,                                           {local_head_num_},                                           linear_bias_slopes_ + local_head_num_ * tensor_para_.rank_)}); }
I used the original FT framework to test this method of deploying baichuan-13B, and the output is correct. Can lmdeploy also consider reusing similar functions to adapt to baichuan-13B?

We are now focusing on supporting Qwen now (PR #230 ). Baichuan-13B is arranged after that

We are now focusing on supporting Qwen now (PR #230 ). Baichuan-13B is arranged after that

Thank you very much, the update has been very fast

@lvhan028 Hi, do you have plans to support Baichuan-13B?

7B can be supported. But 13B cannot yet

@lvhan028 The difference between baichuan-13B and 7B is mainly that the rotary encoding is removed and the alibi encoding is added. The original FasterTransformer framework has a linear_bias_slopes parameter that can implement alibi encoding, and the alibi encoding is calculated as follows: if (true) { invokeBuildAlibiSlopes(linear_bias_slopes_, head_num_, stream_); } Then add linear_bias_slopes to the input tensor of decoder and contextDecoder, if (true) { decoder_input_tensors.insert({"linear_bias_slopes", Tensor(MEMORY_GPU, data_type, {local_head_num_}, linear_bias_slopes_ + local_head_num_ * tensor_para_.rank_)}); } I used the original FT framework to test this method of deploying baichuan-13B, and the output is correct. Can lmdeploy also consider reusing similar functions to adapt to baichuan-13B?

@Dimensionzw Hi, could you tell me how to support Baichuan-13B in original FT framework? Thank you very much.

Hi, @Hap-Zhang
Sorry, we have no time to support Baichuan-13B now. We are busy with refactoring work, debugging the performance of W4 + int8 KV, and kernel optimization.
Requests for model support have been added to our backlog. We plan to incrementally address them in September.

OK, @lvhan028 Thank you very much!


2.6.6: Backend entry filtering is broken

In Symphony 2.6.6, the filtering of entries in the backend is broken completely.
This line breaks it. :-(
Why? Using General::intval is no good idea, because it will return -1 for empty values. The backend filtering doesn't set $_GET['limit'], so $limit will be -1. This results in an invalid SQL query containing LIMIT -1.
I suggest to push a fix and release a new Symphony version ASAP.

Damn. This fix was there to prevent SQL injection... sorry about that.
General::intval is way safer then intval tho since it checks for validity. We had problems with intval that parses string like '1.1' and '1test' as a valid int (when it's not).

@michael-e Could you test 291d1f3 before I release 2.6.7 ?
Thanks. And sourry again.

Confirmed that https://github.com/symphonycms/symphony-2/commit/291d1f3cedac74899af8af1bdfbdf8a11815e25c fixes this issue.

BTW, when have you posted this? I received your email some minutes ago, but Github states that you posted two hours ago. Do they have an email issue?

Do they have an email issue?

Maybe! I did posted it this morning. I'll release 2.6.7 shortly. Thanks!

Do they have an email issue?

Yes they do, I experienced the same thing.

There you go: https://github.com/symphonycms/symphony-2/releases/tag/2.6.7

Big thanks! Will update all the systems out there now.

Done. All systems are on Sym 2.6.7! :-))

:D


Parsing error when loading VSCode .code-snippets files

I'm using require("luasnip.loaders.from_vscode").load_standalone({ path = path }) to load snippets from a VSCode project and seeing the following errors:
ERROR | vscode-loader: Could not parse file .../.vscode/personal.code-snippets: ...local/share/nvim/lazy/LuaSnip/lua/luasnip/util/jsonc.lua:429: ERROR: expected ']' or ',' at line 68 col 5
ERROR | vscode-loader: Reading json from file `.../.vscode/personal.code-snippets` failed, skipping it.

Relevant lines from the personal.code-snippets file:
	"jest / test file for storybook": {
		"scope": "typescriptreact",
		"prefix": "new-jest-storybook",
		"body": [
			"import * as React from 'react';",
			"import { composeStories } from '@storybook/testing-react';",
			"import { render } from '...';",
			"import * as stories from '../stories/${TM_FILENAME/\\..*$//}.stories';",
			"",
			"const { ${TM_FILENAME/\\..*$//} } = composeStories(stories);"
LINE 68 >		"",
			"describe('${TM_FILENAME/\\..*$//}', () => {",
			"  test('renders', () => {",
			"    const component = render(<${TM_FILENAME/\\..*$//} />);",
			"    expect(component.getByTestId('$1')).toBeVisible();",
			"  });",
			"});",
		]
	},

Hey :)
There's really just a comma missing, check line 67

oddly enough i think it works in vscode... anyways, apologies for wasting your time


Set and adjust difficulty ratings before launch

With exercise number 20 just added, we can prepare for launch. Please add your votes for exercise difficulties, so we can adjust the difficulties and sort the config.json file accordingly.

Exercise
Current difficulty
Votes for Easy
Votes for  Medium
Votes for  Hard

Hello World
1

Raindrops
1

Leap
1

Bob
5

Gigasecond
1

Isogram
1

Collatz Conjecture
5

Allergies
3

Meetup
5

Two-Fer
2

Yacht
1

Nucleotide Count
1

Resistor Color
1

High Scores
3

Darts
2

Grains
1

Luhn
4

Eliud's Eggs
3

Armstrong Numbers
3

Difference of Squares
1

Please edit this post, so I can see it all in one place to update the config. @BNAndras, @glennj , @IsaacG

» wc --total=never -l */.meta/example.sql | sort -n
    1 hello-world/.meta/example.sql
    2 gigasecond/.meta/example.sql
    2 leap/.meta/example.sql
    5 raindrops/.meta/example.sql
    6 grains/.meta/example.sql
    7 two-fer/.meta/example.sql
   11 difference-of-squares/.meta/example.sql
   14 eliuds-eggs/.meta/example.sql
   15 darts/.meta/example.sql
   21 collatz-conjecture/.meta/example.sql
   22 meetup/.meta/example.sql
   27 bob/.meta/example.sql
   27 resistor-color/.meta/example.sql
   28 resistor-color-duo/.meta/example.sql
   29 allergies/.meta/example.sql
   30 armstrong-numbers/.meta/example.sql
   31 nucleotide-count/.meta/example.sql
   38 isogram/.meta/example.sql
   42 luhn/.meta/example.sql
   54 yacht/.meta/example.sql
   69 high-scores/.meta/example.sql

If there exercises were one task each, I'd say line count is a good measure ;) But the multi-tasks throws that off.

I added my votes to the table.

My votes are added as well.

Glenn said we should continue without him for a moment.
I took our votes and made a PR: #56


Requesting Lock Button/Toggle for Items/Feats in character sheet

Trying to highlight text within feats (specifically) often times leads me to "grabbing" the feat and "throwing" it off of my character sheet. CTRL+Z does not undo this action. The best way that I can find to fix is to reopen the compendium the drag the feat back onto the sheet.
Highlighting text really helps me as I'm reading across all platforms. Having the option to lock "item" boxes that I definitely don't want to remove would be immensely helpful.

It might be nicer to do what we do with spells and restrict the dragzone to only the header, rather than doing a a lock button.


ValidatingClientStore to throw on error

Is your feature request related to a problem? Please describe.
I was getting a null client, even though the client id was registered in the client store.
The problem was that the client did not have a secret.
I found it only by looking closely in the Output logs.
Describe the solution you'd like
Configure to throw error exception when any error like that happens.
Describe alternatives you've considered
Documentation

The error in the log was: IdentityServer4.Stores.ValidatingClientStore: Error: Invalid client configuration for client xxx: Client secret is required for client_credentials, but no client secret is configured.

That works exactly as designed.

Yup, that is why this is a feature request.


Implement traits for TypeMap

There are a few common std traits that are useful to implement on types when applicable. For TypeMap, those could be

Default -- implemented in https://github.com/bdashore3/typemap_rev/commit/be6e56e48d87495bcdacbdf8a8832af3a34dd3e4.
PartialEq
Eq
Debug
Clone

Would there be a separate Type for each of those traits (similar to the old typemap implementation) or would the typemap have multiple functions to insert types matching different traits to be able to store the trait information? The latter would mean that operations of traits can only be performed on the saved types that implement said trait.

Especially Clone trait will alow for clonable, extensible metadata


Fix missing node neigh metric for counting arping requests

The metric was never enabled due to the missing subsystem from the
switch case.
Fixes: 42eb1edafda ("node-neigh: add metric to count arping requests")
Signed-off-by: Chris Tarazi<EMAIL_ADDRESS>
Fixes: https://github.com/cilium/cilium/pull/14816
Related: https://github.com/cilium/cilium/pull/22888

/test


Unable to create new properties or qnodes

Sending a request to the /api/create_node endpoint to create new properties or qnodes results in this error:
save_entry() missing 1 required positional argument: 'property'
I looked into what is going on in t2wml api and this is probably related to how the new entries are saved in either t2wml backend or the t2wml api. Is it possibly related to the two not being in sync together on the feature/wikifier_endpoints branch? This is what I found in the process:
The save_entry function signature requires these params: def save_entry(self, property, data_type=None, *args, **kwargs)
This is what is sent from the api: t2wml_settings.wikidata_provider.save_entry(**entity_dict)

should be fixed with latest t2wml-api from development and latest t2wml development

thanks!

I'm still getting this error, this is after updating both t2wml backend and api development branches:
save_entry() missing 1 required positional argument: 'property'

this is also fixed now thanks to @devowit, closing the issue


Link broken

when I go here it takes me to a 404 page.

I fixed the link so it should work now!
Here is the link in case you need it: https://raw.githubusercontent.com/LuminesenceProject/LumiOS/main/LumiOS.v6.5.html.

thank you I appreciate it


Tuya RGBW have white sent as colour

[TuyaAccessory] Sending Living room back bulb {"2":"colour","5":"8c8c8c0000008c"} [TuyaAccessory] Sending Living room front bulb {"2":"colour","5":"ffffff000000ff"}
this happens when i say "siri set living room light to white" :(
tested with both HEXHSB and HSB - works only on HEXHSB - but still issue is with understanding white command :(
when used manually from the app and clicked:
[TuyaAccessory] setColorTemperature: 73 [TuyaAccessory] Sending Living room front bulb {"2":"white","4":219}

I also have a bulb that is requiring the "English" spelling of color (colour). Could we get an option to specify US or EU spelling?


this.contentTypes.find is not a function

I get this error, when i am setting allowed file types and then select file from file browser:
ERROR TypeError: this.contentTypes.find is not a function
    at NgUploaderService.push../node_modules/ngx-uploader/fesm5/ngx-uploader.js.NgUploaderService.allContentTypesAllowed (ngx-uploader.js:365)
    at NgUploaderService.push../node_modules/ngx-uploader/fesm5/ngx-uploader.js.NgUploaderService.isContentTypeAllowed (ngx-uploader.js:376)
    at ngx-uploader.js:73
    at FileList.reduce (<anonymous>)
    at NgUploaderService.push../node_modules/ngx-uploader/fesm5/ngx-uploader.js.NgUploaderService.handleFiles (ngx-uploader.js:70)
    at HTMLInputElement.NgFileSelectDirective.fileListener (ngx-uploader.js:568)

On Angular 9 this issue dissapeared.


Added censor and fixed requirements

i dont know anything else to add to pr

Same question

Same question

as? who

Same question

as? who

As mine about the deleted .env file

i added it back


feat: add azure keyvault support

I have added a simple command line flag to specify (and implicitly enable) the azure key vault. I don't think this approach will scale as more external service integrations are added (hashicorp vault etc).

Thanks. Would be cool if you can update the README as well.

I squashed my commits when I rebased, so this has messed up the review snippets. All fixes are in there though.

LGTM! @rollulus can you approve the changes?

:+1:


Unable to connect, no error details given

What happened?
error appears when tring to connect to environment, and connection is not made. Expected connection to be made and icon to go green
What version of the tool are you using?
v2.2.1
What version of Visual Studio Code are you running?
No response
Any relevant session id from VSCode?
ff8ebe37-336d-45dd-b4c3-479885543d281731926828184
Relevant log output
VSCode version: 1.95.3.
Extension version: 2.2.1.
Error occured in connectDataverse command.
Error code: undefined.
Error message: undefined.
Error stack: undefined.

I wasnt able to capture lot of details from the error produced. Can you please share the following:

What type of login did you use?
Does your environment has MFA enabled?
Have you tried using any other login method?

This will help me isolate the issue. Thanks.

After removing the connection and reading the issue resolved


Contextmenu visible on long-press on iPad

When longpressing on an iPad, the native contextmenu appears next to the jstree contextmenu.
Originally reported here: https://github.com/athombv/homey/issues/1000#issuecomment-301699364

Please check again using the code from the master branch. If the issue is still there let me know and I will reopen. Sorry I am asking for this, but I do not currently have an iPad to test on.


Action node UI improvements for scalability

Discussed in https://github.com/microsoft/BotFramework-Composer/discussions/7333

Originally posted by mewa1024 April 23, 2021
Issues:

it's long and hard to find things
some items in appear in multiple categories (e.g., OAuth)
there is no distinction between native actions and actions added by packages

Suggestions:
1 - add a search field above at the top of the menu (TJ actually built this as part of the Jan 2021 hackathon)
2 - have some convention for actions added by packages, such as font style, meta-text, separate menu, dotted path (Tom's  suggestion in #6282)

@mareekuh FYI for design backlog.


Quick question about intents and utterances

I got it all working perfectly up until the point where I have to go to my ipaddress/remote nothing loads after that and the server does say its listening on port 443.
Is it possible for you to send me the intents and utterances for me to add to my app?
Thanks for everything you've done with this, it's greatly appreciated.

You can get a list of intents/utterances by pointing to the server and loading the page "https://<IP_ADDRESS>/remote" on any web browser.
The intent/utterances are going to be specific to your remote based on what is programmed there and how the code ties into it.
It would be best to use the CLI to see a list of available commands on your remote (https://github.com/sushilks/harmonyHubCLI)
then you can modify the code to use those commands.

Using the CLI is there a way to set a specific volume? I had the harmony hub control working from the command line but that only gives me option for up and down on volume not setting a specific volume which is what brought me to this skill in the first place. I'm assuming that IP mentioned is your own on your machine and not a standard one for the skill.
Thanks

How the volume is changed is a function of the equipment that you are using. i.e if the equipment supports setting a specific volume then CLI should be able to execute it.
I haven't see this as an option on TV or on my amplifier.
Yes the IP is an example you will need to change it to point to your server.

Ok thank you very much for your help.


Doesn't work with "Indexed-color mode" images

Describe the bug
Good afternoon, today I noticed such an error. You can check on these images: https://imgur.com/a/QngvJ6n
Images in "Indexed-color mode" are not converted, they are simply skipped.
Reproduction
npm run build && https://laravel.com/docs/9.x/vite#blade-processing-static-assets
System Info
System:
    OS: Linux 4.15 Ubuntu 18.04.6 LTS (Bionic Beaver)
    CPU: (2) x64 AMD EPYC Processor
    Memory: 899.51 MB / 1.90 GB
    Container: Yes
    Shell: 4.4.20 - /bin/bash
Binaries:
    Node: 16.17.0 - /usr/bin/node
    npm: 8.19.1 - /usr/bin/npm
npmPackages:
    vite: ^3.0.0 => 3.1.0

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

@sapphi-red What else is needed?

@AndriiTereshchuk Please read https://stackoverflow.com/help/minimal-reproducible-example.

You could use GitHub repositories.

https://github.com/AndriiTereshchuk/laravel so?

Vite does not treat images differently depending on image format. I guess it's just inlined.
https://vitejs.dev/config/build-options.html#build-assetsinlinelimit
Closing as it seems it's not a bug in Vite.


[QUESTION] Volume attaching and detaching in a loop

Question
Why does this volume attach and detach in a looping manner?

Environment

Longhorn version: 1.2.2
Kubernetes version: 1.21
Node config

OS type and version CentOS7
CPU per node: 6
Memory per node: 32G
Disk type SSD

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): HyperV

Additional context
We upgraded to 1.2.2. The automatic upgrade worked. All volumes' engine image is on 1.2.2. Some volumes keep attaching and detaching.
Logs from longhorn manager:
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:28:35Z\" level=info msg=\"Adding backend: tcp://<IP_ADDRESS>:10330\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: 2021/12/07 08:28:35 cannot create an available backend for the engine from the addresses [tcp://<IP_ADDRESS>:10330]"
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:29:49Z\" level=info msg=\"Starting with replicas [\\\"tcp://<IP_ADDRESS>:10240\\\"]\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:29:49Z\" level=info msg=\"Connecting to remote: <IP_ADDRESS>:10240\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:30:09Z\" level=warning msg=\"failed to create backend with address tcp://<IP_ADDRESS>:10240: failed to get replica <IP_ADDRESS>:10240 info from remote: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = \\\"transport: Error while dialing dial tcp <IP_ADDRESS>:10240: i/o timeout\\\"\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:30:09Z\" level=info msg=\"Adding backend: tcp://<IP_ADDRESS>:10240\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: 2021/12/07 08:30:09 cannot create an available backend for the engine from the addresses [tcp://<IP_ADDRESS>:10240]"
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:30:28Z\" level=info msg=\"Starting with replicas [\\\"tcp://<IP_ADDRESS>:10330\\\"]\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:30:28Z\" level=info msg=\"Connecting to remote: <IP_ADDRESS>:10330\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:30:48Z\" level=warning msg=\"failed to create backend with address tcp://<IP_ADDRESS>:10330: failed to get replica <IP_ADDRESS>:10330 info from remote: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = \\\"transport: Error while dialing dial tcp <IP_ADDRESS>:10330: i/o timeout\\\"\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:30:48Z\" level=info msg=\"Adding backend: tcp://<IP_ADDRESS>:10330\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: 2021/12/07 08:30:48 cannot create an available backend for the engine from the addresses [tcp://<IP_ADDRESS>:10330]"
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:31:05Z\" level=info msg=\"Starting with replicas [\\\"tcp://<IP_ADDRESS>:10330\\\"]\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:31:05Z\" level=info msg=\"Connecting to remote: <IP_ADDRESS>:10330\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:31:25Z\" level=warning msg=\"failed to create backend with address tcp://<IP_ADDRESS>:10330: failed to get replica <IP_ADDRESS>:10330 info from remote: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = \\\"transport: Error while dialing dial tcp <IP_ADDRESS>:10330: i/o timeout\\\"\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:31:25Z\" level=info msg=\"Adding backend: tcp://<IP_ADDRESS>:10330\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: 2021/12/07 08:31:25 cannot create an available backend for the engine from the addresses [tcp://<IP_ADDRESS>:10330]"
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:31:45Z\" level=info msg=\"Starting with replicas [\\\"tcp://<IP_ADDRESS>:10285\\\"]\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:31:45Z\" level=info msg=\"Connecting to remote: <IP_ADDRESS>:10285\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:32:05Z\" level=warning msg=\"failed to create backend with address tcp://<IP_ADDRESS>:10285: failed to get replica <IP_ADDRESS>:10285 info from remote: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = \\\"transport: Error while dialing dial tcp <IP_ADDRESS>:10285: i/o timeout\\\"\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:32:05Z\" level=info msg=\"Adding backend: tcp://<IP_ADDRESS>:10285\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: 2021/12/07 08:32:05 cannot create an available backend for the engine from the addresses [tcp://<IP_ADDRESS>:10285]"
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:32:11Z\" level=info msg=\"Starting with replicas [\\\"tcp://<IP_ADDRESS>:10240\\\"]\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:32:11Z\" level=info msg=\"Connecting to remote: <IP_ADDRESS>:10240\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:32:31Z\" level=warning msg=\"failed to create backend with address tcp://<IP_ADDRESS>:10240: failed to get replica <IP_ADDRESS>:10240 info from remote: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = \\\"transport: Error while dialing dial tcp <IP_ADDRESS>:10240: i/o timeout\\\"\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:32:31Z\" level=info msg=\"Adding backend: tcp://<IP_ADDRESS>:10240\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: 2021/12/07 08:32:31 cannot create an available backend for the engine from the addresses [tcp://<IP_ADDRESS>:10240]"
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:32:40Z\" level=info msg=\"Starting with replicas [\\\"tcp://<IP_ADDRESS>:10240\\\"]\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:32:40Z\" level=info msg=\"Connecting to remote: <IP_ADDRESS>:10240\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:33:00Z\" level=warning msg=\"failed to create backend with address tcp://<IP_ADDRESS>:10240: failed to get replica <IP_ADDRESS>:10240 info from remote: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = \\\"transport: Error while dialing dial tcp <IP_ADDRESS>:10240: i/o timeout\\\"\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:33:00Z\" level=info msg=\"Adding backend: tcp://<IP_ADDRESS>:10240\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: 2021/12/07 08:33:00 cannot create an available backend for the engine from the addresses [tcp://<IP_ADDRESS>:10240]"
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:33:03Z\" level=info msg=\"Starting with replicas [\\\"tcp://<IP_ADDRESS>:10240\\\"]\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:33:03Z\" level=info msg=\"Connecting to remote: <IP_ADDRESS>:10240\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:33:23Z\" level=warning msg=\"failed to create backend with address tcp://<IP_ADDRESS>:10240: failed to get replica <IP_ADDRESS>:10240 info from remote: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = \\\"transport: Error while dialing dial tcp <IP_ADDRESS>:10240: i/o timeout\\\"\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:33:23Z\" level=info msg=\"Adding backend: tcp://<IP_ADDRESS>:10240\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: 2021/12/07 08:33:23 cannot create an available backend for the engine from the addresses [tcp://<IP_ADDRESS>:10240]"
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:33:35Z\" level=info msg=\"Starting with replicas [\\\"tcp://<IP_ADDRESS>:10240\\\"]\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:33:35Z\" level=info msg=\"Connecting to remote: <IP_ADDRESS>:10240\""
longhorn-manager-42l7k time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-e-9e9e94c2: time=\"2021-12-07T08:33:55Z\" level=warning msg=\"failed to create backend with address tcp://<IP_ADDRESS>:10240: failed to get replica <IP_ADDRESS>:10240 info from remote: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = \\\"transport: Error while dialing dial tcp <IP_ADDRESS>:10240: i/o timeout\\\"\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:24:19Z\" level=info msg=\"Listening on gRPC Replica server <IP_ADDRESS>:10285\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:24:19Z\" level=info msg=\"Listening on sync agent server <IP_ADDRESS>:10287\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:24:19Z\" level=info msg=\"Listening on data server <IP_ADDRESS>:10286\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:24:19Z\" level=info msg=\"Listening on sync <IP_ADDRESS>:10287\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:24:52Z\" level=warning msg=\"Received signal interrupt to shutdown\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:24:52Z\" level=warning msg=\"Starting to execute registered shutdown func github.com/longhorn/longhorn-engine/app/cmd.startReplica.func4\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:25:04Z\" level=info msg=\"Listening on data server <IP_ADDRESS>:10286\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:25:04Z\" level=info msg=\"Listening on sync agent server <IP_ADDRESS>:10287\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:25:04Z\" level=info msg=\"Listening on gRPC Replica server <IP_ADDRESS>:10285\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:25:04Z\" level=info msg=\"Listening on sync <IP_ADDRESS>:10287\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:25:32Z\" level=warning msg=\"Received signal interrupt to shutdown\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:25:32Z\" level=warning msg=\"Starting to execute registered shutdown func github.com/longhorn/longhorn-engine/app/cmd.startReplica.func4\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:25:46Z\" level=info msg=\"Listening on sync agent server <IP_ADDRESS>:10287\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:25:46Z\" level=info msg=\"Listening on data server <IP_ADDRESS>:10286\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:25:46Z\" level=info msg=\"Listening on gRPC Replica server <IP_ADDRESS>:10285\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:25:46Z\" level=info msg=\"Listening on sync <IP_ADDRESS>:10287\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:26:10Z\" level=warning msg=\"Received signal interrupt to shutdown\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:26:10Z\" level=warning msg=\"Starting to execute registered shutdown func github.com/longhorn/longhorn-engine/app/cmd.startReplica.func4\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:26:27Z\" level=info msg=\"Listening on sync agent server <IP_ADDRESS>:10287\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:26:27Z\" level=info msg=\"Listening on data server <IP_ADDRESS>:10286\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:26:27Z\" level=info msg=\"Listening on gRPC Replica server <IP_ADDRESS>:10285\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:26:27Z\" level=info msg=\"Listening on sync <IP_ADDRESS>:10287\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:26:52Z\" level=warning msg=\"Received signal interrupt to shutdown\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:26:52Z\" level=warning msg=\"Starting to execute registered shutdown func github.com/longhorn/longhorn-engine/app/cmd.startReplica.func4\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:26:55Z\" level=info msg=\"Listening on data server <IP_ADDRESS>:10286\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:26:55Z\" level=info msg=\"Listening on gRPC Replica server <IP_ADDRESS>:10285\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:26:55Z\" level=info msg=\"Listening on sync agent server <IP_ADDRESS>:10287\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:26:55Z\" level=info msg=\"Listening on sync <IP_ADDRESS>:10287\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:27:20Z\" level=warning msg=\"Received signal interrupt to shutdown\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:27:20Z\" level=warning msg=\"Starting to execute registered shutdown func github.com/longhorn/longhorn-engine/app/cmd.startReplica.func4\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:27:38Z\" level=info msg=\"Listening on sync agent server <IP_ADDRESS>:10332\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:27:38Z\" level=info msg=\"Listening on gRPC Replica server <IP_ADDRESS>:10330\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:27:38Z\" level=info msg=\"Listening on data server <IP_ADDRESS>:10331\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:27:38Z\" level=info msg=\"Listening on sync <IP_ADDRESS>:10332\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:28:04Z\" level=warning msg=\"Received signal interrupt to shutdown\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:28:04Z\" level=warning msg=\"Starting to execute registered shutdown func github.com/longhorn/longhorn-engine/app/cmd.startReplica.func4\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:28:14Z\" level=info msg=\"Listening on gRPC Replica server <IP_ADDRESS>:10330\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:28:14Z\" level=info msg=\"Listening on sync agent server <IP_ADDRESS>:10332\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:28:14Z\" level=info msg=\"Listening on data server <IP_ADDRESS>:10331\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:28:14Z\" level=info msg=\"Listening on sync <IP_ADDRESS>:10332\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:29:27Z\" level=warning msg=\"Received signal interrupt to shutdown\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:29:27Z\" level=warning msg=\"Starting to execute registered shutdown func github.com/longhorn/longhorn-engine/app/cmd.startReplica.func4\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:29:46Z\" level=info msg=\"Listening on data server <IP_ADDRESS>:10241\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:29:46Z\" level=info msg=\"Listening on sync agent server <IP_ADDRESS>:10242\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:29:46Z\" level=info msg=\"Listening on gRPC Replica server <IP_ADDRESS>:10240\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:29:46Z\" level=info msg=\"Listening on sync <IP_ADDRESS>:10242\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:30:14Z\" level=warning msg=\"Received signal interrupt to shutdown\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:30:14Z\" level=warning msg=\"Starting to execute registered shutdown func github.com/longhorn/longhorn-engine/app/cmd.startReplica.func4\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:30:25Z\" level=info msg=\"Listening on data server <IP_ADDRESS>:10331\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:30:25Z\" level=info msg=\"Listening on sync agent server <IP_ADDRESS>:10332\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:30:25Z\" level=info msg=\"Listening on gRPC Replica server <IP_ADDRESS>:10330\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:30:25Z\" level=info msg=\"Listening on sync <IP_ADDRESS>:10332\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:30:56Z\" level=warning msg=\"Received signal interrupt to shutdown\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:30:56Z\" level=warning msg=\"Starting to execute registered shutdown func github.com/longhorn/longhorn-engine/app/cmd.startReplica.func4\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:31:03Z\" level=info msg=\"Listening on data server <IP_ADDRESS>:10331\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:31:03Z\" level=info msg=\"Listening on sync agent server <IP_ADDRESS>:10332\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:31:03Z\" level=info msg=\"Listening on gRPC Replica server <IP_ADDRESS>:10330\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:31:03Z\" level=info msg=\"Listening on sync <IP_ADDRESS>:10332\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:31:28Z\" level=warning msg=\"Received signal interrupt to shutdown\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:31:28Z\" level=warning msg=\"Starting to execute registered shutdown func github.com/longhorn/longhorn-engine/app/cmd.startReplica.func4\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:31:44Z\" level=info msg=\"Listening on data server <IP_ADDRESS>:10286\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:31:44Z\" level=info msg=\"Listening on sync agent server <IP_ADDRESS>:10287\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:31:44Z\" level=info msg=\"Listening on gRPC Replica server <IP_ADDRESS>:10285\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:31:44Z\" level=info msg=\"Listening on sync <IP_ADDRESS>:10287\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:32:09Z\" level=warning msg=\"Received signal interrupt to shutdown\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:32:09Z\" level=warning msg=\"Starting to execute registered shutdown func github.com/longhorn/longhorn-engine/app/cmd.startReplica.func4\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:32:10Z\" level=info msg=\"Listening on data server <IP_ADDRESS>:10241\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:32:10Z\" level=info msg=\"Listening on sync agent server <IP_ADDRESS>:10242\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:32:10Z\" level=info msg=\"Listening on gRPC Replica server <IP_ADDRESS>:10240\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:32:10Z\" level=info msg=\"Listening on sync <IP_ADDRESS>:10242\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:32:33Z\" level=warning msg=\"Received signal interrupt to shutdown\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:32:33Z\" level=warning msg=\"Starting to execute registered shutdown func github.com/longhorn/longhorn-engine/app/cmd.startReplica.func4\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:32:38Z\" level=info msg=\"Listening on sync agent server <IP_ADDRESS>:10242\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:32:38Z\" level=info msg=\"Listening on data server <IP_ADDRESS>:10241\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:32:38Z\" level=info msg=\"Listening on gRPC Replica server <IP_ADDRESS>:10240\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:32:38Z\" level=info msg=\"Listening on sync <IP_ADDRESS>:10242\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:33:01Z\" level=warning msg=\"Received signal interrupt to shutdown\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:33:01Z\" level=warning msg=\"Starting to execute registered shutdown func github.com/longhorn/longhorn-engine/app/cmd.startReplica.func4\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:33:02Z\" level=info msg=\"Listening on data server <IP_ADDRESS>:10241\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:33:02Z\" level=info msg=\"Listening on sync agent server <IP_ADDRESS>:10242\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:33:02Z\" level=info msg=\"Listening on gRPC Replica server <IP_ADDRESS>:10240\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:33:02Z\" level=info msg=\"Listening on sync <IP_ADDRESS>:10242\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:33:29Z\" level=warning msg=\"Received signal interrupt to shutdown\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:33:29Z\" level=warning msg=\"Starting to execute registered shutdown func github.com/longhorn/longhorn-engine/app/cmd.startReplica.func4\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:33:34Z\" level=info msg=\"Listening on data server <IP_ADDRESS>:10241\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:33:34Z\" level=info msg=\"Listening on sync agent server <IP_ADDRESS>:10242\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:33:34Z\" level=info msg=\"Listening on gRPC Replica server <IP_ADDRESS>:10240\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:33:34Z\" level=info msg=\"Listening on sync <IP_ADDRESS>:10242\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:33:56Z\" level=warning msg=\"Received signal interrupt to shutdown\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:33:56Z\" level=warning msg=\"Starting to execute registered shutdown func github.com/longhorn/longhorn-engine/app/cmd.startReplica.func4\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:33:58Z\" level=info msg=\"Listening on gRPC Replica server <IP_ADDRESS>:10240\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:33:58Z\" level=info msg=\"Listening on data server <IP_ADDRESS>:10241\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:33:58Z\" level=info msg=\"Listening on sync agent server <IP_ADDRESS>:10242\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:33:58Z\" level=info msg=\"Listening on sync <IP_ADDRESS>:10242\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:34:21Z\" level=warning msg=\"Received signal interrupt to shutdown\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:34:21Z\" level=warning msg=\"Starting to execute registered shutdown func github.com/longhorn/longhorn-engine/app/cmd.startReplica.func4\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:34:36Z\" level=info msg=\"Listening on sync agent server <IP_ADDRESS>:10242\""
longhorn-manager-5szq6 time="2021-12-07T08:34:58Z" level=warning msg="pvc-bba665d4-3208-40b5-b2af-9cea046a2fa7-r-5290248d: time=\"2021-12-07T08:34:36Z\" level=info msg=\"Listening on gRPC Replica server <IP_ADDRESS>:10240\""

Can you check if there are any error messages in the replica instance manager pod?
You can find the name of pod instance-manager-r-xxxxxxxx by checking the volume detail page.

After installing updates on the OS, the issue appears to be fixed. All PVC's are attached. However this is a little bit frustrating since we do not know the actual cause.
I am starting to think that the hypervisor might be causing this, since after the update all went well.
The logs from instance-manager-r:
time="2021-12-07T09:59:07Z" level=info msg="Currently snapshot volume-snap-2a42925d-ed6c-48d0-95d8-5b4fc08b452c.img doesn't meet criteria to be removed, skip it for now"
[pvc-98b3b15d-f37f-492a-bd21-fe99e0401ec8-r-651efd92[] time="2021-12-07T09:59:07Z" level=info msg="Prepare removing disk: c4f45290-b3f8-4c7c-8239-e43e527e74ab"
time="2021-12-07T09:59:07Z" level=info msg="Coalescing volume-snap-2a42925d-ed6c-48d0-95d8-5b4fc08b452c.img to volume-snap-c4f45290-b3f8-4c7c-8239-e43e527e74ab.img"
time="2021-12-07T09:59:07Z" level=info msg="Replace volume-snap-2a42925d-ed6c-48d0-95d8-5b4fc08b452c.img with volume-snap-c4f45290-b3f8-4c7c-8239-e43e527e74ab.img"
time="2021-12-07T09:59:07Z" level=info msg="Replacing disk volume-snap-c4f45290-b3f8-4c7c-8239-e43e527e74ab.img with volume-snap-2a42925d-ed6c-48d0-95d8-5b4fc08b452c.img"
time="2021-12-07T09:59:07Z" level=info msg="Old file volume-snap-2a42925d-ed6c-48d0-95d8-5b4fc08b452c.img exists, deleting"
[pvc-98b3b15d-f37f-492a-bd21-fe99e0401ec8-r-651efd92[] time="2021-12-07T09:59:07Z" level=info msg="Done replacing volume-snap-2a42925d-ed6c-48d0-95d8-5b4fc08b452c.img with volume-snap-c4f45290-b3f8-4c7c-8239-e43e527e74ab.img"
[pvc-5c12ea82-e5e9-4119-a573-90ae9c3a2a2e-r-417d0ee7[] time="2021-12-07T09:59:08Z" level=info msg="Replica server starts to snapshot [0daa87a9-2bce-49d4-b776-ed2803c898f8[] volume, user created false, created time 2021-12-07T09:54:50Z, labels map[]"
time="2021-12-07T09:59:08Z" level=info msg="Starting to create disk" disk=0daa87a9-2bce-49d4-b776-ed2803c898f8
time="2021-12-07T09:59:08Z" level=info msg="Finished creating disk" disk=0daa87a9-2bce-49d4-b776-ed2803c898f8
[pvc-5c12ea82-e5e9-4119-a573-90ae9c3a2a2e-r-417d0ee7[] time="2021-12-07T09:59:08Z" level=info msg="Sending file volume-head-002.img.meta to <IP_ADDRESS>:10393"
time="2021-12-07T09:59:08Z" level=info msg="source file size: 178, setting up directIO: false"
[pvc-5c12ea82-e5e9-4119-a573-90ae9c3a2a2e-r-417d0ee7[] time="2021-12-07T09:59:08Z" level=info msg="Done sending file volume-head-002.img.meta to <IP_ADDRESS>:10393"
[pvc-5c12ea82-e5e9-4119-a573-90ae9c3a2a2e-r-417d0ee7[] time="2021-12-07T09:59:08Z" level=info msg="Reloading the revision counter before processing the first write, the current revision cache is 3277021, the latest revision counter in file is 3277021"
[pvc-5c12ea82-e5e9-4119-a573-90ae9c3a2a2e-r-417d0ee7[] time="2021-12-07T09:59:08Z" level=info msg="Replace volume-snap-6c02a029-0623-4d9e-9e21-f98b2cb0243e.img with volume-snap-025a02e6-403c-44b4-b814-9a373657930b.img"
[pvc-5c12ea82-e5e9-4119-a573-90ae9c3a2a2e-r-417d0ee7[] time="2021-12-07T09:59:08Z" level=info msg="Replacing disk volume-snap-025a02e6-403c-44b4-b814-9a373657930b.img with volume-snap-6c02a029-0623-4d9e-9e21-f98b2cb0243e.img"
time="2021-12-07T09:59:08Z" level=info msg="Old file volume-snap-6c02a029-0623-4d9e-9e21-f98b2cb0243e.img exists, deleting"
time="2021-12-07T09:59:08Z" level=info msg="Done replacing volume-snap-6c02a029-0623-4d9e-9e21-f98b2cb0243e.img with volume-snap-025a02e6-403c-44b4-b814-9a373657930b.img"
[pvc-98b3b15d-f37f-492a-bd21-fe99e0401ec8-r-651efd92[] time="2021-12-07T09:59:10Z" level=info msg="Reloading the revision counter before processing the first write, the current revision cache is 903748, the latest revision counter in file is 903748"
[pvc-5c12ea82-e5e9-4119-a573-90ae9c3a2a2e-r-417d0ee7[] time="2021-12-07T09:59:24Z" level=info msg="Replica server starts to snapshot [1f349da4-1101-4f15-b847-dcf3ea346669[] volume, user created false, created time 2021-12-07T09:55:07Z, labels map[]"
time="2021-12-07T09:59:24Z" level=info msg="Starting to create disk" disk=1f349da4-1101-4f15-b847-dcf3ea346669
time="2021-12-07T09:59:24Z" level=info msg="Finished creating disk" disk=1f349da4-1101-4f15-b847-dcf3ea346669
[pvc-5c12ea82-e5e9-4119-a573-90ae9c3a2a2e-r-417d0ee7[] time="2021-12-07T09:59:24Z" level=info msg="Sending file volume-head-003.img.meta to <IP_ADDRESS>:10483"
time="2021-12-07T09:59:24Z" level=info msg="source file size: 178, setting up directIO: false"
[pvc-5c12ea82-e5e9-4119-a573-90ae9c3a2a2e-r-417d0ee7[] time="2021-12-07T09:59:24Z" level=info msg="Done sending file volume-head-003.img.meta to <IP_ADDRESS>:10483"
[pvc-5c12ea82-e5e9-4119-a573-90ae9c3a2a2e-r-417d0ee7[] time="2021-12-07T09:59:31Z" level=info msg="Marking disk 0daa87a9-2bce-49d4-b776-ed2803c898f8 as removed"
[pvc-5c12ea82-e5e9-4119-a573-90ae9c3a2a2e-r-417d0ee7[] time="2021-12-07T09:59:31Z" level=info msg="Marking disk 1f349da4-1101-4f15-b847-dcf3ea346669 as removed"
time="2021-12-07T09:59:31Z" level=info msg="Prepare removing disk: 1f349da4-1101-4f15-b847-dcf3ea346669"
time="2021-12-07T09:59:31Z" level=info msg="Currently snapshot volume-snap-1f349da4-1101-4f15-b847-dcf3ea346669.img doesn't meet criteria to be removed, skip it for now"
[pvc-5c12ea82-e5e9-4119-a573-90ae9c3a2a2e-r-417d0ee7[] time="2021-12-07T09:59:31Z" level=info msg="Prepare removing disk: 0daa87a9-2bce-49d4-b776-ed2803c898f8"
time="2021-12-07T09:59:31Z" level=info msg="Coalescing volume-snap-1f349da4-1101-4f15-b847-dcf3ea346669.img to volume-snap-0daa87a9-2bce-49d4-b776-ed2803c898f8.img"
[pvc-5c12ea82-e5e9-4119-a573-90ae9c3a2a2e-r-417d0ee7[] time="2021-12-07T09:59:31Z" level=info msg="Replace volume-snap-1f349da4-1101-4f15-b847-dcf3ea346669.img with volume-snap-0daa87a9-2bce-49d4-b776-ed2803c898f8.img"
time="2021-12-07T09:59:31Z" level=info msg="Replacing disk volume-snap-0daa87a9-2bce-49d4-b776-ed2803c898f8.img with volume-snap-1f349da4-1101-4f15-b847-dcf3ea346669.img"
time="2021-12-07T09:59:31Z" level=info msg="Old file volume-snap-1f349da4-1101-4f15-b847-dcf3ea346669.img exists, deleting"
[pvc-5c12ea82-e5e9-4119-a573-90ae9c3a2a2e-r-417d0ee7[] time="2021-12-07T09:59:31Z" level=info msg="Done replacing volume-snap-1f349da4-1101-4f15-b847-dcf3ea346669.img with volume-snap-0daa87a9-2bce-49d4-b776-ed2803c898f8.img"
time="2021-12-07T09:59:31Z" level=info msg="Prepare removing disk: 6c02a029-0623-4d9e-9e21-f98b2cb0243e"
time="2021-12-07T09:59:31Z" level=info msg="Coalescing volume-snap-1f349da4-1101-4f15-b847-dcf3ea346669.img to volume-snap-6c02a029-0623-4d9e-9e21-f98b2cb0243e.img"
[pvc-5c12ea82-e5e9-4119-a573-90ae9c3a2a2e-r-417d0ee7[] time="2021-12-07T09:59:31Z" level=info msg="Replace volume-snap-1f349da4-1101-4f15-b847-dcf3ea346669.img with volume-snap-6c02a029-0623-4d9e-9e21-f98b2cb0243e.img"
[pvc-5c12ea82-e5e9-4119-a573-90ae9c3a2a2e-r-417d0ee7[] time="2021-12-07T09:59:31Z" level=info msg="Replacing disk volume-snap-6c02a029-0623-4d9e-9e21-f98b2cb0243e.img with volume-snap-1f349da4-1101-4f15-b847-dcf3ea346669.img"
time="2021-12-07T09:59:31Z" level=info msg="Old file volume-snap-1f349da4-1101-4f15-b847-dcf3ea346669.img exists, deleting"
time="2021-12-07T09:59:31Z" level=info msg="Done replacing volume-snap-1f349da4-1101-4f15-b847-dcf3ea346669.img with volume-snap-6c02a029-0623-4d9e-9e21-f98b2cb0243e.img"
[longhorn-instance-manager[] time="2021-12-07T09:59:41Z" level=info msg="Process Manager: prepare to create process pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de"
[longhorn-instance-manager[] time="2021-12-07T09:59:41Z" level=info msg="Process Manager: created process pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:41Z" level=info msg="Creating volume /host/var/lib/longhorn/replicas/pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-d6aecbc4, size<PHONE_NUMBER>/512"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:41Z" level=info msg="Starting to create disk" disk=000
time="2021-12-07T09:59:41Z" level=info msg="Finished creating disk" disk=000
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:41Z" level=info msg="Listening on sync agent server <IP_ADDRESS>:10167"
time="2021-12-07T09:59:41Z" level=info msg="Listening on data server <IP_ADDRESS>:10166"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:41Z" level=info msg="Listening on gRPC Replica server <IP_ADDRESS>:10165"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:41Z" level=info msg="Listening on sync <IP_ADDRESS>:10167"
[longhorn-instance-manager[] time="2021-12-07T09:59:41Z" level=info msg="Process pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de has started at localhost:10165"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:41Z" level=info msg="New connection from: <IP_ADDRESS>:35884"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:41Z" level=info msg="Opening volume /host/var/lib/longhorn/replicas/pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-d6aecbc4, size<PHONE_NUMBER>/512"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:41Z" level=info msg="Replica server starts to snapshot [0b84086e-0589-4472-9812-531fc462af1a[] volume, user created false, created time 2021-12-07T09:59:41Z, labels map[]"
time="2021-12-07T09:59:41Z" level=info msg="Starting to create disk" disk=0b84086e-0589-4472-9812-531fc462af1a
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:41Z" level=info msg="Finished creating disk" disk=0b84086e-0589-4472-9812-531fc462af1a
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:41Z" level=info msg="Launching receiver for file volume-head-001.img.meta"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:41Z" level=info msg="Running ssync server for file volume-head-001.img.meta at port 10168"
time="2021-12-07T09:59:41Z" level=info msg="Creating Ssync service"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:41Z" level=info msg="open: receiving fileSize: 178, setting up directIO: false"
time="2021-12-07T09:59:41Z" level=info msg="Ssync server opened and ready"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:41Z" level=info msg="Closing ssync server"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:41Z" level=info msg="Done running ssync server for file volume-head-001.img.meta at port 10168"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:41Z" level=info msg="Running ssync server for file volume-snap-dd8ec395-2d34-4e37-8110-5a1bcec40e0d.img at port 10169"
time="2021-12-07T09:59:41Z" level=info msg="Creating Ssync service"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:41Z" level=info msg="open: receiving fileSize:<PHONE_NUMBER>, setting up directIO: true"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:41Z" level=info msg="Ssync server opened and ready"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:43Z" level=info msg="Reloading the revision counter before processing the first write, the current revision cache is 0, the latest revision counter in file is 0"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:44Z" level=info msg="Closing ssync server"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:44Z" level=info msg="Done running ssync server for file volume-snap-dd8ec395-2d34-4e37-8110-5a1bcec40e0d.img at port 10169"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:44Z" level=info msg="Running ssync server for file volume-snap-dd8ec395-2d34-4e37-8110-5a1bcec40e0d.img.meta at port 10170"
time="2021-12-07T09:59:44Z" level=info msg="Creating Ssync service"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:44Z" level=info msg="open: receiving fileSize: 158, setting up directIO: false"
time="2021-12-07T09:59:44Z" level=info msg="Ssync server opened and ready"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:44Z" level=info msg="Closing ssync server"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:44Z" level=info msg="Done running ssync server for file volume-snap-dd8ec395-2d34-4e37-8110-5a1bcec40e0d.img.meta at port 10170"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:44Z" level=info msg="Running ssync server for file volume-snap-0b84086e-0589-4472-9812-531fc462af1a.img at port 10171"
time="2021-12-07T09:59:44Z" level=info msg="Creating Ssync service"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:44Z" level=info msg="open: receiving fileSize:<PHONE_NUMBER>, setting up directIO: true"
time="2021-12-07T09:59:44Z" level=info msg="Ssync server opened and ready"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:44Z" level=info msg="Closing ssync server"
time="2021-12-07T09:59:44Z" level=info msg="Done running ssync server for file volume-snap-0b84086e-0589-4472-9812-531fc462af1a.img at port 10171"
time="2021-12-07T09:59:44Z" level=info msg="Running ssync server for file volume-snap-0b84086e-0589-4472-9812-531fc462af1a.img.meta at port 10172"
time="2021-12-07T09:59:44Z" level=info msg="Creating Ssync service"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:44Z" level=info msg="open: receiving fileSize: 178, setting up directIO: false"
time="2021-12-07T09:59:44Z" level=info msg="Ssync server opened and ready"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:44Z" level=info msg="Closing ssync server"
time="2021-12-07T09:59:44Z" level=info msg="Done running ssync server for file volume-snap-0b84086e-0589-4472-9812-531fc462af1a.img.meta at port 10172"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:44Z" level=info msg="Sync agent gRPC server finished rebuilding replica/sync files for replica <IP_ADDRESS>"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:44Z" level=info msg="Reloading volume"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:44Z" level=info msg="Marking disk 0b84086e-0589-4472-9812-531fc462af1a as removed"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:44Z" level=info msg="Prepare removing disk: 0b84086e-0589-4472-9812-531fc462af1a"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:44Z" level=info msg="Currently snapshot volume-snap-0b84086e-0589-4472-9812-531fc462af1a.img doesn't meet criteria to be removed, skip it for now"
time="2021-12-07T09:59:44Z" level=info msg="Prepare removing disk: dd8ec395-2d34-4e37-8110-5a1bcec40e0d"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:44Z" level=info msg="Coalescing volume-snap-0b84086e-0589-4472-9812-531fc462af1a.img to volume-snap-dd8ec395-2d34-4e37-8110-5a1bcec40e0d.img"
time="2021-12-07T09:59:44Z" level=info msg="Replace volume-snap-0b84086e-0589-4472-9812-531fc462af1a.img with volume-snap-dd8ec395-2d34-4e37-8110-5a1bcec40e0d.img"
time="2021-12-07T09:59:44Z" level=info msg="Replacing disk volume-snap-dd8ec395-2d34-4e37-8110-5a1bcec40e0d.img with volume-snap-0b84086e-0589-4472-9812-531fc462af1a.img"
time="2021-12-07T09:59:44Z" level=info msg="Old file volume-snap-0b84086e-0589-4472-9812-531fc462af1a.img exists, deleting"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:44Z" level=info msg="Done replacing volume-snap-0b84086e-0589-4472-9812-531fc462af1a.img with volume-snap-dd8ec395-2d34-4e37-8110-5a1bcec40e0d.img"
[pvc-3f6c3def-06ce-4fcc-81c5-aa30dc56d389-r-f61f13de[] time="2021-12-07T09:59:45Z" level=info msg="Reloading the revision counter before processing the first write, the current revision cache is 5499780, the latest revision counter in file is 5499780"

Also I have pinged the instance-manager-r-xxxxxxxx from longhorn-manager. It's responsive.

Also I have pinged the instance-manager-r-xxxxxxxx from longhorn-manager.

Pinable before installing updates on the OS?

I'll consider closing this issue now.
Feel free to reopen it once the symptom is reproducible.


file input support request.

Please kindly support for file input save as and open file input. tia

It is possible to achieve with something like this:
    <label for="files" class="button file-label">Upload
    </label>
    <input
      onchange="yourUploadHandler(e)"
      accept=".csv, .doc, image/*"
      class="hidden"
      id="files"
      type="file" />

.file-label {
  width: 15rem;
}
input[type=file].hidden {
  visibility: hidden;
  width: 15rem;
  margin-left: -15rem;
}

Heads up; do not wrap the label around the input, this will make IE (at least Edge) to go bonkers.

@marcusasplund it's very impressive! Okay for you if I add this feature in the next version?

Yes, of course!

@faststare Inspire by @marcusasplund, I add this feature #249
Now I will close this issue.


PUT/POST/DELETE on /redfish/v1/Systems/<system_id>/Storage/ArrayControllers-0 should return 405

Resolved it with PR https://github.com/ODIM-Project/ODIM/pull/62


the following code should show normal error

// Type unions are a way of declaring that an object
// could be more than one type.

type StringOrNumber = string | number;
type ProcessStates = "open" | "closed";
type OddNumbersUnderTen = 1 | 3 | 5 | 7 | 9;
type AMessyUnion = "hello" | 156 | { error: true };

// If the use of "open" and "closed" vs string is
// new to you, check out: example:literals

// We can mix different types into a union, and
// what we're saying is that the value is one of those types.

// TypeScript will then leave you to figure out how to
// determine which value it could be at runtime.

// Unions can sometimes be undermined by type widening,
// for example:

type WindowStates = "open" | "closed" | "minimized" | string;

// If you hover above, you can see that WindowStates
// becomes a string - not the union. This is covered in
// example:type-widening-and-narrowing

// If a union is an OR, then an intersection is an AND.
// Intersection types are when two types intersect to create
// a new type. This allows for type composition.

interface ErrorHandling {
  success: boolean;
  error?: { message: string };
}

interface ArtworksData {
  artworks: { title: string }[];
}

interface ArtistsData {
  artists: { name: string }[];
}

// These interfaces can be composed in responses which have
// both consistent error handling, and their own data.

type ArtworksResponse = ArtworksData & ErrorHandling;
type ArtistsResponse = ArtistsData & ErrorHandling;

// For example:

const handleArtistsResponse = (response: ArtistsResponse) => {
  if (response.error) {
    console.error(response.error.message);
    return;
  }

  console.log(response.artists);
};

// A mix of Intersection and Union types becomes really
// useful when you have cases where an object has to
// include one of two values:

interface CreateArtistBioBase {
  artistID: string;
  thirdParty?: boolean;
}

type CreateArtistBioRequest = CreateArtistBioBase & ({ html: string } | { markdown: string });

// Now you can only create a request when you include
// artistID and either html or markdown

const workingRequest: CreateArtistBioRequest = {
  artistID: "banksy",
  markdown: "Banksy is an anonymous England-based graffiti artist...",
};

const badRequest: CreateArtistBioRequest = {
  artistID: "banksy",
};

function main() {
    print("done.");
}

yes, it does


Fill background...

Hi! I've just moved over to Immich from GooglePhotos and was overjoyed to see that there is a module for Immich as well! :) Thank you!
I have a question/request, when a picture is displayed and you are using backgroundSize: 'contain', is there a way to "fill" the rest of the screen with black (or as in the MMM-GooglePhotos module with a dimmed zoomed in part of current picture)?
Why? My mirror is used as a Digital-Photo-Frame when no one is standing in front of it, so the module is shown "in front of" all the other modules then. But when someone comes in proximity to the mirror, the "picture-module" is hidden and all the other modules are shown...
Again thank you for this module! :)

I'll see what can be done here.  should not be too difficult hopefully to put a black background.

Thank you for fixing this! :)


[1.0.8] Funtions don't read output of commands.

If functions don't read properly output of commands.
Sample output of debug
++ [[ '' =~ -(FCronDaemon)$ ]]

Line where is "if" from above:
59   if [[ $($CRON_SEARCH) =~ \-(FCronDaemon)$ ]]

Repaired this quirk in 1.0.8-dev


Fix canonical_gauge(::PSOModel)

canonical_gauge was not always behaving as advertised. It appears this is related to differing implementations of QR factorization for dense v. sparse matrices. I have not looked into why this happens so if it is obvious to someone I'd appreciate a comment being left here.
There was a test for this function, but apparently it was not strong enough, so I added a test that covers a case where the function was misbehaving. I don't expect my fix to impact performance much, since I think canonical_gauge already densified PSO models before this PR.

I'd believe that dense QR and sparse QR might give literally different factorizations (especially since P is rectangular—right?), but I can't imagine why the rest of the code would care.
It'd be worth sanity-checking that sparse QR is at least giving a correct factorization, so that the problem is for sure somewhere in our code and not in Julia linear algebra.

I'll approve this change, since it's important to have correct code in master—but conditional on you filing an issue for someone to investigate further and figure out how to get sparsity back.

Just a note: this function generically produces dense models anyway (see the comment on line 82 of admittance_model.jl) so I don't think one should worry about getting sparsity back.

nice

Is this a uniqueness issue? Can QR with pivoting help?

Well according to Wikipedia QR decomposition is unique (under basic assumptions) so I don't think there's anything one can do. Circuits generically have sparse high dimensional PSO models but dense low dimensional transfer functions.

For those interested I just took another look, there are different types returned depending on whether you attempt QR factorization on a sparse or dense matrix. The SuiteSparse.SPQR.QRSparse type includes some row and column permutations we were ignoring. Something to keep in mind for the future but probably expected behavior.

That’s what I thought. I was using rank revealing QR in Matlab quite a while ago. That was returning a sorted QR with a permutation matrix so that you can compress a dense matrix with not too much effort.