How to calculate the total number of the all FP64 instructions executed in the kernel?

Hello!
I analyzing the performance of a several scientific libraries. And, I'd like to understand an actual arithmetic complexity of each. Which metrics of rocproof  I should use for this goal?
I guess SQ_INSTS_VALU, then the total number will be equal:
CU_NUM * SIMD_NUM * SQ_INSTS_VALU.  Where, for AI100: CU_NUM is 120 CU, SIMD_NUM is 4. It's correct?
Thanks!

First, isn't SIMD_NUM 16, not 4 even on your CDNA MI100?
Then I would be surprised if SQ_INSTS_VALU was only FP64 instructions!

Hi @vasslavich
Thanks for reaching out.
Let me assign to one of the developers to help you. Thank you.

Hi,
A note, actually I'd like to know the total number FP64 for to calculate/comparision FLOPS of these specific kernels. It can be very interesting.

Hi @vasslavich, we have a metric for this on MI200 but not MI100. Is this still needed?
rocprofiler/src/core/counters/metrics/derived_counters.xml
The metric is called TOTAL_64_OPS

Hi @vasslavich, do you still need help from AMD on this ticket?  If not, please close the ticket.  Thanks.

Closing this ticket as there is no response from @vasslavich.  Please re-open if you are still looking for total number of all FP64 instructions executed in the kernel.


Add configurable features for camera view panel

Description
Add option to modify far clip and vertical FOV of camera view, which are useful when viewing in FPS mode (e.g. frame aligned mode).

camera view panel before changing:

after change:

Fixed formatting issues
We found the default values in https://github.com/OGRECave/ogre/blob/master/OgreMain/src/OgreCamera.cpp#L60-L63:mFOVy = Radian(Math::PI/4.0f);
mNearDist = 100.0f;
mFarDist = 100000.0f;

However, we are not sure whether the upper limit for mFOVy (90 degree) is proper.
Question: could you please explain what does "it breaks ABI." mean in a little more detail?

We found the default values in https://github.com/OGRECave/ogre/blob/master/OgreMain/src/OgreCamera.cpp#L60-L63

These are different values than you used: far clipping distance 100 vs. 100000
What about reading the initial value from the created OGRE camera? Then you are sure to be always in sync with OGRE defaults.
I'm still hesitating to merge such a ABI change to a base class.

To avoid ABI breakage in the base class: What about adding those additional properties only in the FPSViewController?

Closing due to inactivity.


make a DegradationModelBlackbox

remove explicit split of resistance, scale, and shift.
They will be reintroduced later.

remove the Q -> V model.
remove scale, resistance, shift altogether
simplify the dependencies


Update build.proj

Fix https://github.com/castleproject/Core/issues/97

Fixed already in https://github.com/Moq/moq4/commit/adf6b6ad4e2aeae011bbd733646f953ec119b848 as soon as I noticed :).

Thanks! When will it be released to nuget?

Pushed!


CSHARP-2276: IMongoIndexManager CreateOne or CreateOneAsync methods can throw NullReferenceException

Rebased and master and pushed to master.


Users should be anonymous, yet still uniquely identifiable

User Story
As a User, I would like to chat anonymously but identifiably so that other people know I am the same person chatting, but without revealing my true identity.
Detailed Description
Users should be associated with an anonymous username, this way people know they are conversing with the same person. For example we could do something like Verb + Noun, like Dancing Kangaroo.  This could be the same for a user across all places, or each place can be a new identifier for a user.
Acceptance Criteria

[ ] Given a user, then an anonymous identifier is associated with that user

@stovsky What are your thoughts on simply assigning a user a random animal name when they sign up? Could get a large amount of animal names (>100?) to make enough for many identifiable users, and permanently assign someone this when signing  up

@ldalton02 I think this would work, but obviously will encounter issues when we reach a lot of users.  Also it may be important for a user to have unique anonymity across places, so they can have a different persona at different locations. However, I think it ultimately depends on the experience we want, since it also could be equally as valid for users to want to build their reputation in the area with the same anonymous name.

@stovsky Discussed offline, users will be able to change their "avatar" once per 24 hours


Create object for SecureSet in code_schools.yaml

Feature
Why is this feature being added?
SecureSet is an amazing partner, and also a Cyber Security Bootcamp. They've requested to be listed on our /code_schools page.
What should your feature do?
Add SecureSet to ./config/code_schools.yaml in observation of rules set out in the top of that file.
VA-Approved
Notes: Not a traditional coding bootcamp. SecureSet focuses on security training relevant to the IT industry.
Locations:

Colorado Springs, CO
Denver, CO
Website: https://secureset.com/

Doing this,  do you have the logo in front_end yet?

Completed in https://github.com/OperationCode/operationcode_backend/pull/198


Parallel Program Request

I have the Parallel Program emblem and I would like to get added to the Parallel Program Report site.

[x] I understand that this website is not affiliated with Bungie, Inc. in any way.

Bungie Name: My Derpy Turtle#6665
My contribution: Small css changes to Guardian Theater way back in the day

Added as per 4bef485. Let me know if you wanna change your name, role, or the link provided in the site.

Looks good to me :) Thanks!


added http OPTIONS and an event grid validation example

Signed-off-by: Jiaxiao Zhou<EMAIL_ADDRESS>The SpinHttpExecutor misses a OPTIONS http method implementation. This PR adds that. In addition, it adds an example to validate a http request from Event Grid subscription webhook authentication.

rust

interesting... not sure how that went through but I will delete it.

Thanks a lot for catching the missing HTTP method!
Would it make sense to split the two contributions, as they are separate?
Perhaps the cloud events example would make more sense in the kitchensink examples repo?
https://github.com/fermyon/spin-kitchensink

Thanks a lot for catching the missing HTTP method!
Would it make sense to split the two contributions, as they are separate? Perhaps the cloud events example would make more sense in the kitchensink examples repo? https://github.com/fermyon/spin-kitchensink

@radu-matei I moved the example out of this PR. Now it only fixes the http options.


browse subdir shows index.php from root dir

Hello,
another problem i discovered shortly after https://github.com/mholt/caddy/issues/297
If i request each file directly, each file is correctly handled. So if i request http://localhost:81/ i get the index.php (phpinfo()) rendered. But if i request http://localhost:81/test/ for dir indexing i get the index.php from root dir rendered.
I'm at Windows 7 x64 with newest PHP 5.6.14 x64
<IP_ADDRESS>:81 {
  root www/
  browse /
  fastcgi / <IP_ADDRESS>:9123 php
}

Root Dir Content:

/index.php
/test.html
/folder/
/folder/test.html

This looks a bug and should not be the case. Trying to find a fix.

This should be fixed now. Feel free to close this issue when you confirm it.

Fix confirmed.


TrelloHttpClient for the modern version of the Async Http Client.

I'm open to suggestions for the name of the class... the current one is pretty ugly but I couldn't think of anything better.
Also, bump jackson version to the current version, and give Label
accessors for its id attribute.
The implementation is almost identical to the one for the old ning AHC client. It uses final ObjectReader and ObjectWriter fields as those are preferable to the mutable ObjectMapper type.

can you also update the README file? it has a section about http clients

Can do.


Add opt-in c++11 stream insertable check.

It adds opt-in define CATCH_CONFIG_CPP_11_STREAM_INSERTABLE_CHECK for enabling C++11 stream insertable check which should be better in some cases as suggested by @philsquared in #872.
All current tests seem to pass fine with it on my system.
Should I also add it to documentation somewhere?
PR should resolve #872 and #757 for those who opt-in.

You should explain the toggle in docs/configuration.md, but generally looks it looks good.
I'll fix-up whitespace and fmt later.

I added explanation and removed weird underscore between CPP and 11

It's in and I have to say, I honestly can't wait till Catch Classic is put into legacy mode, there is way too many C++11 toggles to test properly.


Alternate location for the "default User Folder"

Before you start...

[X] Have you refreshed the page? You might be using an old version of the website.
[X] Have you checked if someone already requested this feature? If they have, post a comment with your use case instead.

Description
Currently using store version of the App.
my Start setting location for the default folders (Documents, Downloads, Music, Pictures, Videos) are not located on C:\ ( C: drive ), and nor I want to store it on OneDrive (as Files App is defaulted to currently)
normal File exe. (W11) works as planned, and is able to change location if i so choose.
Alternative solutions
No response
Relevant Assets
No response

This is the repo for the website, not the app. Please open the issue again in https://github.com/files-community/files.


add the --include-implicit-teams flag to list-memberships

r? @mlsteele
Using the extra column from https://github.com/keybase/keybase/pull/1697, filter out implicit teams from the team list results by default, and add a flag (that maybe no one will ever use) to bring them back. Also clean up the formatting a little bit in the non-all case, where printing the username is redundant.

Made it devel only.


[feature] Custom request method

Hi,
Great job always, thanks.
Is it possible to add custom request method ?
To make request of a non-existing implementation.
Like this :
const functionName = 'LISTING_STATUS'
const params = {
    date: '2013-08-03'
}
const response = await av.customRequest(functionName, params)

Hi, it is, but the essential purpose of this package is to have the types of what the API returns, so if this feature is implemented it has to ensure that all the possible results of the API are typed, which will be accomplished eventually by implementing the functions one by one.


Set photo did not save to system file

After #110, I know how to get the thumbnail from your api, clap for your quick response !!!
but when i create contact, add photo using setPhoto api like the instruction, I could not see the photo be added to the system.
I tested the add photo function on system dialer app, I successfully got the photo on my dialer app, so It must be the issue on the setPhoto part.
Here is the code I get photo uri. I am using jetpack compose.
val launcher = rememberLauncherForActivityResult(contract =
    ActivityResultContracts.GetContent()) { uri: Uri? ->
        imageUri = uri
    }

Using content provider to get photo byte data (bitmap)
fun uriToBitmap(context: Context, uri: Uri?) : Bitmap? {
        if (uri == null) return null

        return if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.P) {
            ImageDecoder.decodeBitmap(
                ImageDecoder.createSource(
                    context.contentResolver,
                    uri
                )
            )
        } else {
            MediaStore.Images.Media.getBitmap(context.contentResolver, uri)
        }
    }

Then save the bitmap using setPhoto with extra contact data
Contacts(context)
            .insert()
            .rawContact {
                setName {
                    this.displayName = contact.name
                }
                if (!contact.email.isNullOrEmpty()) {
                    addEmail {
                        this.address = contact.email
                    }
                }
                if (!contact.location.isNullOrEmpty()) {
                    addAddress {
                        this.formattedAddress = contact.location
                    }
                }

                if (!contact.number.isNullOrEmpty()) {
                    addPhone {
                        this.number = contact.number
                    }
                }

                val photoBitmap = contact.getPhotoBitmap()
                if (photoBitmap != null) {
                    setPhoto(context, photoBitmap)
                }
            }
            .allowBlanks(true)
            .commit()

I check the bitmap object, it's not empty, so the problem is in the third code.
Did I do something wrong on this code ?

@lau1944, it was not clear enough so I made more updates to the documentation https://github.com/vestrel00/contacts-android/commit/8ea871ca89ef27292c77d6fb89c73bd1e8882ae0
What you are seeing is expected behavior because you are calling the setPhoto extension function on a RawContact that has not yet been inserted into the Contacts Provider database. You have to insert (commit) the RawContact first and then you can set the photo.
In any case, I 100% agree that this is the fault of the library. Sorry 😁  It should not allow you to call setPhoto (and other extension functions) if the entity has not yet been inserted. I will be fixing this issue in #117 🔥
For now, I added a section in this howto page to make things clear; https://github.com/vestrel00/contacts-android/blob/main/howto/howto-get-set-remove-contact-raw-contact-photo.md#inserting-contacts-with-photo
I'll copy-paste it here too.
Inserting contacts with photo
You cannot get/set/remove photos for Contacts/RawContacts that have not yet been inserted in the
Contacts Provider database. In other words, only Contacts/RawContacts retrieved via query or result
APIs can use the extension functions in contacts.core.util.ContactPhoto.kt and
contacts.core.util.RawContactPhoto.kt.
To insert a new contact "with photo", you should insert the contact first. Then, if the insert
succeeds, proceed to set the photo.
Do,
val insertResult = Contacts(context)
    .insert()
    .rawContact {
        ...
    }
    .commit()

val contact = insertResult.contacts(contactsApi).firstOrNull()
contact?.setPhoto(...)

Don't,
val insertResult = Contacts(context)
    .insert()
    .rawContact {
        setPhoto(...)
    }
    .commit()

For more info about insert, read How do I create/insert contacts?

It is true that the API should not allow you to call setPhoto on a Contact/RawContact that has not
yet been inserted. It is currently misleading. This will be fixed in issue #117. As of right now,
the following documentation is included in contacts.core.util.ContactPhoto.kt and
contacts.core.util.RawContactPhoto.kt functions.
/*
 * ## For existing (inserted) entities only
 *
 * This function will only work for entities that have already been inserted into the Contacts
 * Provider database. This means that this is only for entities that have been retrieved using
 * query or result APIs.
 */

Note for contributors; It is possible to include photo thumbnail data as part of the insertion
of a new RawContact using ContactsContract.CommonDataKinds.Photo.PHOTO. The Contacts Provider
will use the thumbnail as the full-sized photo as well. However, this is not good practice as the
full-sized photo will have a really low resolution. Showing the full-sized photo in a big view
will not look good. Therefore, this library does not allow this. Consumers must first insert their
new RawContact so that they can set the full-sized photo.

@lau1944, one more thing. I noticed in the code snippet you provided that you check if !isNullOrEmpty(). You actually don't need to perform that check because the API internally does not insert data that is null, empty, or blank (only spaces). You also don't need to use this.
So, combined with my previous comment, your code should look something like...
val contactsApi = Contacts(context)
val insertResult = contactsApi
            .insert()
            .rawContact {
                setName {
                    displayName = contact.name
                }
                addEmail {
                    address = contact.email
                }
                if (!contact.location.isNullOrEmpty()) {
                    addAddress {
                        formattedAddress = contact.location
                    }
                }

                if (!contact.number.isNullOrEmpty()) {
                    addPhone {
                        number = contact.number
                    }
                }
            }
            .allowBlanks(true)
            .commit()

val photoBitmap = contact.getPhotoBitmap()
if (photoBitmap != null) {
    insertResult.contacts(contactsApi).firstOrNull()?.setPhoto(context, photoBitmap)
}

Also keep in mind that all of that code is being done in the caller thread and requires permissions so you might want to use the coroutine extensions provided in the library. I haven't written the howto pages for them yet but it's something like...
launch {
    val contactsApi = Contacts(context)
    val insertResult = contactsApi
            .insertWithPermission()
            .rawContact {
                ...
            }
            .allowBlanks(true)
            .commitWithContext()

    val photoBitmap = contact.getPhotoBitmap()
    if (photoBitmap != null) {
        insertResult
            .contacts(contactsApi)
            .firstOrNull()
            ?.setPhotoWithContext(context, photoBitmap)
    }
}

If you are already handling threading and permissions then you can ignore this suggestion.
Good luck! Let me know how it goes 😁

Thank you for your help ! I can't believe how much effort you put in this. Clap for you 👏👏
A small suggestion for the rawContact api, to make the set method more intuitive,
Instead of disabling the set photo method in the rawContact scope function, you can add photo after the contact has been successfully committed to the library.
The developer doesn't have to worry much about two insertResult states, the first is contact insert result, second is photo add result, you handle that in your library, and it looks much cleaner in our view.

Thanks for that suggestion @lau1944 !!! ❤ 🔥
I thought about this a lot. At first, I was thinking of all the reasons why I should not take your suggestion. Things like, API complexity, maintenance costs, supporting multiple ways of doing the same thing, all came to my mind. I thought to myself, "no".
However, when I look at it from a consumer perspective (your perspective) I 100% agree with you. At the end of the day, this library is about making it easier for consumers to interface with the Contacts Provider. It is not about how beautifully architected the library is (though I will keep it beautiful as much as I can 😁).
So, I created issues #119 and #120.
Thanks again for your valuable feedback!!! And of course, thanks for trying out this library. I'm having a lot of fun working on this haha!

Looking forward to your work 😊


Dropdown menu in a collapsed navbar bug

Dropdown menu don't appear correctly in a collapsed navbar and links with icons (font awesome or material icons) don't stay aligned with the others links.

Code:

 aaaa

		bbbb

cccc

dddd

Same Problem here

Hi! I made a few changes to fix the issue with dropdowns. I will update the partial _responsive.scss and you must overwrite this with the old file in assets/sass/ct-paper/_responsive.scss, after you do that please compile your assets/sass/ct-paper.scss with Koala. Make sure the output path is assets/sass/ct-paper.css. Hope that will be ok for you!
Best,
Dragos
_responsive.scss.zip


Deallocate eviction policy auto start

After VM's state is turned to deallocated, will it automatically start once there is an availability?
Or do I have to try and start it manually?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a1bd5076-fe52-cfca-4173-dec861167812
Version Independent ID: 0122fff1-79e0-446c-00a4-85248a21b6dc
Content: Create an Azure scale set that uses low-priority VMs (Preview)
Content Source: articles/virtual-machine-scale-sets/virtual-machine-scale-sets-use-low-priority.md
Service: virtual-machine-scale-sets
GitHub Login: @mmccrory
Microsoft Alias: memccror

@assaf-grth
Thanks for the question! We are investigating and will update you shortly.

@assaf-grth VMSS wont start the deallocated VM automatically.

So just to make sure, unless I try to start it manually, it will remain deallocated?

Yes you are right

Refer to this faq on this doc https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-use-low-priority#does-autoscale-work-with-both-eviction-policies-deallocate-and-delete
Its better to go for delete eviction policy and setup autoscaling. If your scale set capacity is 3, Then if 3 deallocated vms are there, Then VMSS wont scale after that.
If the eviction policy is delete, Then it deletes the vms when evicted and will create new ones when capacity is there

@assaf-grth  I will close this out for now. If you need additional help please let me know and we can reopen and continue.


Please open source the teacher logits

Dear Authors,
Very impressive work. For reproducibility purposes could you please share the teacher logits files for all the teachers shown in this paper?

Thanks for your attention to our work!
Sorry for the late reply.
We have uploaded the teacher logits files, which were generated by CLIP-ViT-Large/14-22k on ImageNet-22k (Ref. the tutorial).
You can download them by azcopy.
azcopy cp "https://tracking2019.blob.core.windows.net/tinyvit-teacher-logits/clip_224_22k_top100_logits_bs128/?sv=2020-04-08&st=2022-10-07T06%3A14%3A52Z&se=2022-10-21T06%3A14%3A00Z&sr=c&sp=rl&sig=RPycNtS5qTk77Z2nmyQeUHObEzVHrRCxtc41%2BalTN9A%3D" ./ --recursive

There are 1440 files (90 epochs * 8 ranks * (key + value files)) about 499 GB (18GB for keys, 481GB for values).
You can download the logits in the specific epoch.
For example, download the logits in the epoch 0:
azcopy cp "https://tracking2019.blob.core.windows.net/tinyvit-teacher-logits/clip_224_22k_top100_logits_bs128/logits_top100_epoch0/?sv=2020-04-08&st=2022-10-07T06%3A14%3A52Z&se=2022-10-21T06%3A14%3A00Z&sr=c&sp=rl&sig=RPycNtS5qTk77Z2nmyQeUHObEzVHrRCxtc41%2BalTN9A%3D" ./ --recursive

The expiration time is Oct. 21, 2022. We can extend the date if necessary : ).

Close it. Feel free to re-open it if necessary for extending the date : )

Could you please extend the date？ Thanks a lot !

Could you please extend the date？ Thanks a lot !

Hi @HaoWuSR , the date has been extended.

Hello Sir could you also share the logits of teacher based on datasets such as imagenet-1K and any other dataset?

Hi @sanyalsunny111 , sorry that I did not prepare the teacher logits on ImageNet-1k for this codebase.
You can follow the tutorial to save the sparse logits.

Thank you for responding @wkcn Could you please provide a running script that could be used to save sparse logits of CLIP-ViT-Large/14-22k with imagenet-1k? I am asking cause I see save_logits.py can use both imagenet-22k and imagenet-1k. Any feedback on this?

Hi @sanyalsunny111, the following command is used to save sparse logits of CLIP-ViT-Large/14-22k on ImageNet-1k.
python -m torch.distributed.launch --nproc_per_node 8 save_logits.py --cfg configs/teacher/clip_vit_large_patch14_22k.yaml --data-path ./ImageNet --batch-size 128 --eval --resume checkpoints/clip_vit_large_patch14_22k.pth --opts DISTILL.TEACHER_LOGITS_PATH ./teacher_logits_1k AUG.MIXUP 0.8 AUG.CUTMIX 1.0 DATA.DATASET imagenet TRAIN.EPOCHS 300 DISTILL.LOGITS_TOPK 10

It needs the extra config options AUG.MIXUP 0.8 AUG.CUTMIX 1.0 DATA.DATASET imagenet TRAIN.EPOCHS 300 DISTILL.LOGITS_TOPK 10 to save the 1k logits.
However, I recommend Swin-base/large 22kto1k or BEiT-base/large 22kto1k as the 1k teacher model, since CLIP-ViT-Large/14-22k is not finetuned on ImageNet-1k.

Hi @wkcn Thank you very much for earlier responses. I have saved the teacher logits on teacher CLIP-ViT-Large/14-22k using ImageNet-1k. Could you please provide a pre-training script (with distillation) with saved teacher logits on ImageNet.

Hi @sanyalsunny111, you can try this script:
python -m torch.distributed.launch --nproc_per_node 8 main.py --cfg configs/1k/tiny_vit_21m.yaml --data-path ./ImageNet --batch-size 128  --opts DISTILL.TEACHER_LOGITS_PATH ./teacher_logits_1k AUG.MIXUP 0.8 AUG.CUTMIX 1.0 DATA.DATASET imagenet TRAIN.EPOCHS 300 DISTILL.LOGITS_TOPK 10

Just a quick question where the best checkpoints and training logs will be saved?

Hi @sanyalsunny111 ,
The checkpoint and log will be saved in the folder ./output by default. You can change it by adding the command   --output xxxx when running the script.

Hey @wkcn could you please share your code for the Linear probe with various datasets as shown in Table 5 of the paper?

Hi @sanyalsunny111 , please refer to torchvision and Cross-Domain Few-Shot Learning (CD-FSL) Benchmark.

Hi @wkcn, I have used Linear Probe and a few shot codes from moco-v3 and CD-FSL, but it's not matching your results on Table 5. Is it possible for you to share your codes for the Linear probing and Few shot?

Could you please extend the date？ Thanks a lot !

Hi @HaoWuSR , the date has been extended.

Hi @wkcn can you please extend the date?

Hi @BrendanCReidy, thanks for your attention to our work!
The new link:
azcopy cp "https://tracking2019.blob.core.windows.net/tinyvit-teacher-logits?sv=2020-04-08&st=2023-01-26T03%3A00%3A21Z&se=2023-02-09T03%3A00%3A00Z&sr=c&sp=rl&sig=lVTekKcg9SAvzF6AmyGJTIv%2FXNx42XLLqSYSfpxmWLY%3D" ./ --recursive

Hi @wkcn can you please extend the date?

HI @Andrewymd , thanks for your attention to our work!
Here is the new link. The storage size of the teacher logits (clip_22k) is 499 GB.
Please install azcopy (https://learn.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-v10) before downloading the teacher logits.
azcopy copy "https://hopengscus7387599778.blob.core.windows.net/tinyvit-teacher-logits/clip_224_22k_top100_logits_bs128/?sv=2021-08-06&se=2023-09-14T05%3A49%3A17Z&sr=c&sp=rl&sig=8HyBKYcLikVGtunLnTXgmtn8Ej0JiQsZt%2BCbexC6kfQ%3D" "./" --overwrite=prompt --check-md5 FailIfDifferent --from-to=BlobLocal --recursive --log-level=INFO

Hi @wkcn can you please extend the date? Thanks for your great work~

Hi @jotoy , here is the new download command.
azcopy copy  "https://hopengscus7387599778.blob.core.windows.net/tinyvit-teacher-logits/clip_224_22k_top100_logits_bs128/?sv=2021-08-06&st=2023-10-30T16%3A30%3A11Z&se=2023-11-29T16%3A30%3A00Z&sr=c&sp=rl&sig=MuAQWkYvVfD8q4YEKH2BdjdFoHR5ZkpKlMIOJlt2diM%3D" "./" --recursive

Thanks for your attention to our work!

Hi @wkcn can you please extend the date? Thank you very much.

Hi @wkcn, another question, since all of the 90epochs logits are too huge, whether can I train the TinyViT using only the logics of epoch 90? Thnaks!

@maybeliuchuan
Thanks for your attention to our work!
Sorry that I could not extend the date. The logits can be reproduced by the teacher model CLIP-ViT-Large/14-22k on ImageNet-21k.
An epoch may be not enough on ImageNet-21k. You can try to save the teacher logits on ImageNet-1k. Here is the related tutorial: https://github.com/microsoft/Cream/blob/main/TinyViT/docs/SAVE_TEACHER_LOGITS.md


Highlights don't line up with the text they are highlighting

When I highlight text in my code, the highlight doesn't line up with the code. The highlight gets more and more offset, as text goes further to the right in the row. This seems to just be a miscalculation of the displayed text's position in the row. The script that draws the highlights is getting understated values for some reason. I am guessing that something with the way the highlighter handles font width is wrong.
Version: 1.78.0
Commit: 252e5463d60e63238250799aef7375787f68b4ee
User Ag

ent: Mozilla/5.0 (X11; CrOS x86_64 14541.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Embedder: github.dev

Which font do you use? Does it reproduce with standard settings?


EOF occurred in violation of protocol (_ssl.c:600)

Hi,
Since few days I have this error "EOF occurred in violation of protocol (_ssl.c:600)". Google said me that is an issue with openssl. The workaround is to force TLS V1. But how can I do that with aiohttp?
Thanks,

Hi. Are you talking about client or server API?
For client you can specify sslcontext parameter in TCPConnector constructor.

Hi asvetlov,
It's a client request:
response = yield from aiohttp.request('GET', 'https://example.com')
If I do that:
conn = aiohttp.TCPConnector(verify_ssl=False)
response = yield from aiohttp.request('GET', 'https://example.com', connector = conn)
It's simple but this should works, no?

You code disables all SSL validation checks.
See https://github.com/KeepSafe/aiohttp/blob/master/aiohttp/connector.py#L259 for examples of SSLContext creation.

Thanks Asvetlov, it works well.

Sure!
On Wed, Jan 28, 2015 at 3:07 PM, matt75013<EMAIL_ADDRESS>wrote:

Closed #260 https://github.com/KeepSafe/aiohttp/issues/260.
—
Reply to this email directly or view it on GitHub
https://github.com/KeepSafe/aiohttp/issues/260#event-226054171.

--
Thanks,
Andrew Svetlov


How to reuse memory？

My logic now is that every call to the exported function will buf := make(p[]byte,4096) memory, although every call buf = nil, but I find that wazero keeps calling Grow() to expand the memory, causing my process memory to keep increasing.
I want to ask how to reuse memory?
wasm:
func payload(d []byte) ([]byte, error){       buf := make([]byte, 4096)       fmt.Println(buf)       buf  = nil }
Host:
wasm.instance.Invoke("payload")
wazero:
func (m *MemoryInstance) WriteString(offset uint32, val string) bool {
if !m.hasSize(offset, uint64(len(val))) {
return false
}
copy(m.Buffer[offset:], val)
return true
}

It seems that only the Grow interface is provided, and no interface for reducing memory is provided。

If you want better help, you need to give us more info into what you're doing, how you're doing it, etc. Like, what do you use to compile Wasm: TinyGo, Go…?
But still, yes, Wasm memory only grows, never shrinks. That's how it is.
Whatever is running inside the Wasm (TinyGo, Go…) should eventually free the memory you're allocating, and start reusing the freed memory. wazero's memory usage won't decrease, but should stabilize.
If you want to be sure you reuse the buffer, though, the easiest way is to keep it in a global variable.


Add description of lab meetings

This big document includes some expectations and processes for lab meetings.
I'd love to hear your thoughts!

@ajrcampbell - I'm going to merge this because I really want these guidelines in the main repo. But please fix forwards when you have time! Moving the content around to make it clearer would be great!


MQTT - multiple connections with same clientid (if configured)

Describe the bug
I've configured mqtt with a custom client id (config see below)
This leads to errors in my mosquitto log (see below).
It looks like evcc creates multiple connections with the same (configured) clientid (instead of using just 1 connection)?!
Steps to reproduce

Configure mqtt
Set a custom client id
Use mqtt plugin at multiple locations

Configuration details
mqtt:
  broker: <IP_ADDRESS>:1883
  topic: evcc
  clientid: evcc
  user: evcc
  password:<PHONE_NUMBER>

meters:
  - name: pv
    type: custom
    power: # power (W)
      source: mqtt
      topic: home/energy/electricity/photovoltaic/generator/power
    energy: # optional energy (kWh)
      source: mqtt
      topic: home/energy/electricity/photovoltaic/generator/energy
      scale: 0.001
    currents:
      - source: mqtt
        topic: home/energy/electricity/photovoltaic/current/l1
      - source: mqtt
        topic: home/energy/electricity/photovoltaic/current/l2
      - source: mqtt
        topic: home/energy/electricity/photovoltaic/current/l3
  - name: charge
    type: custom
    power: # power (W)
      source: mqtt
      topic: home/energy/electricity/wallbox/power
    energy: # optional energy (kWh)
      source: mqtt
      topic: home/energy/electricity/wallbox/energy
      scale: 0.001
    currents:
      - source: mqtt
        topic: home/energy/electricity/wallbox/current/l1
      - source: mqtt
        topic: home/energy/electricity/wallbox/current/l2
      - source: mqtt
        topic: home/energy/electricity/wallbox/current/l3
  - name: grid
    type: custom
    power: # power (W)
      source: mqtt
      topic: home/energy/electricity/meter/power
      scale: -1
    energy: # optional energy (kWh)
      source: mqtt
      topic: home/energy/electricity/photovoltaic/generator/energy
      scale: 0.001
    currents:
      - source: mqtt
        topic: home/energy/electricity/meter/current/l1
      - source: mqtt
        topic: home/energy/electricity/meter/current/l2
      - source: mqtt
        topic: home/energy/electricity/meter/current/l3

Log details
mqtt broker / mosquitto log:

1676896287: New client connected from <IP_ADDRESS>:33898 as evcc (p2, c1, k30, u'evcc').
1676896287: New connection from <IP_ADDRESS>:54988 on port 1883.
1676896287: Client evcc already connected, closing old connection.
1676896287: New client connected from <IP_ADDRESS>:54988 as evcc (p2, c1, k30, u'evcc').
1676896287: New connection from <IP_ADDRESS>:33899 on port 1883.
1676896287: Client evcc already connected, closing old connection.
1676896287: New client connected from <IP_ADDRESS>:33899 as evcc (p2, c1, k30, u'evcc').
1676896287: New connection from <IP_ADDRESS>:54994 on port 1883.
1676896287: Client evcc already connected, closing old connection.
1676896287: New client connected from <IP_ADDRESS>:54994 as evcc (p2, c1, k30, u'evcc').
1676896287: New connection from <IP_ADDRESS>:33900 on port 1883.
1676896287: Client evcc already connected, closing old connection.
1676896287: New client connected from <IP_ADDRESS>:33900 as evcc (p2, c1, k30, u'evcc').
1676896287: New connection from <IP_ADDRESS>:54996 on port 1883.
1676896287: Client evcc already connected, closing old connection.
1676896287: New client connected from <IP_ADDRESS>:54996 as evcc (p2, c1, k30, u'evcc').
1676896288: New connection from <IP_ADDRESS>:33901 on port 1883.
1676896288: Client evcc already connected, closing old connection.
1676896288: New client connected from <IP_ADDRESS>:33901 as evcc (p2, c1, k30, u'evcc').
1676896288: New connection from <IP_ADDRESS>:55012 on port 1883.
1676896288: Client evcc already connected, closing old connection.
1676896288: New client connected from <IP_ADDRESS>:55012 as evcc (p2, c1, k30, u'evcc').
....

What type of operating system are you running?
Linux
Version
0.112.5

Thats strange. It should reuse the connection. Closing since evcc logfile is missing.

[main  ] INFO 2023/02/20 13:19:45 evcc 0.112.5
[main  ] INFO 2023/02/20 13:19:45 using config file: /etc/evcc.yaml
[main  ] INFO 2023/02/20 13:19:45 starting ui and api at :7070
[db    ] INFO 2023/02/20 13:19:45 using sqlite database: /home/mkleine/.evcc/evcc.db
[mqtt  ] INFO 2023/02/20 13:19:45 connecting evcc at tcp://<IP_ADDRESS>:1883
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: read tcp <IP_ADDRESS>:55244-><IP_ADDRESS>:1883: read: connection reset by peer
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: not currently connected and ResumeSubs not set
[mqtt  ] ERROR 2023/02/20 13:19:45 error: not currently connected and ResumeSubs not set
[mqtt  ] ERROR 2023/02/20 13:19:45 error: not currently connected and ResumeSubs not set
[mqtt  ] ERROR 2023/02/20 13:19:45 error: not currently connected and ResumeSubs not set
[mqtt  ] ERROR 2023/02/20 13:19:45 error: not currently connected and ResumeSubs not set
[mqtt  ] ERROR 2023/02/20 13:19:45 error: not currently connected and ResumeSubs not set
[mqtt  ] ERROR 2023/02/20 13:19:45 error: not currently connected and ResumeSubs not set
[mqtt  ] ERROR 2023/02/20 13:19:45 error: not currently connected and ResumeSubs not set
[mqtt  ] ERROR 2023/02/20 13:19:45 error: not currently connected and ResumeSubs not set
[mqtt  ] ERROR 2023/02/20 13:19:45 error: not currently connected and ResumeSubs not set
[mqtt  ] ERROR 2023/02/20 13:19:45 error: not currently connected and ResumeSubs not set
[mqtt  ] ERROR 2023/02/20 13:19:45 error: not currently connected and ResumeSubs not set
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: read tcp <IP_ADDRESS>:55258-><IP_ADDRESS>:1883: read: connection reset by peer
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: read tcp <IP_ADDRESS>:55270-><IP_ADDRESS>:1883: read: connection reset by peer
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: read tcp <IP_ADDRESS>:55272-><IP_ADDRESS>:1883: read: connection reset by peer
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: read tcp <IP_ADDRESS>:55288-><IP_ADDRESS>:1883: read: connection reset by peer
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: EOF
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: read tcp <IP_ADDRESS>:55302-><IP_ADDRESS>:1883: read: connection reset by peer
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: EOF
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: read tcp <IP_ADDRESS>:55320-><IP_ADDRESS>:1883: read: connection reset by peer
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: read tcp <IP_ADDRESS>:55336-><IP_ADDRESS>:1883: read: connection reset by peer
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: EOF
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: read tcp <IP_ADDRESS>:55368-><IP_ADDRESS>:1883: read: connection reset by peer
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: read tcp <IP_ADDRESS>:55384-><IP_ADDRESS>:1883: read: connection reset by peer
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: read tcp <IP_ADDRESS>:55394-><IP_ADDRESS>:1883: read: connection reset by peer
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: read tcp <IP_ADDRESS>:55410-><IP_ADDRESS>:1883: read: connection reset by peer
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: read tcp <IP_ADDRESS>:55422-><IP_ADDRESS>:1883: read: connection reset by peer
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: read tcp <IP_ADDRESS>:55438-><IP_ADDRESS>:1883: read: connection reset by peer
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: EOF
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: read tcp <IP_ADDRESS>:55454-><IP_ADDRESS>:1883: read: connection reset by peer
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: read tcp <IP_ADDRESS>:55456-><IP_ADDRESS>:1883: read: connection reset by peer
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: EOF
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: read tcp <IP_ADDRESS>:55464-><IP_ADDRESS>:1883: read: connection reset by peer
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: read tcp <IP_ADDRESS>:55470-><IP_ADDRESS>:1883: read: connection reset by peer
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: read tcp <IP_ADDRESS>:55480-><IP_ADDRESS>:1883: read: connection reset by peer
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: read tcp <IP_ADDRESS>:55486-><IP_ADDRESS>:1883: read: connection reset by peer
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: EOF
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: read tcp <IP_ADDRESS>:55518-><IP_ADDRESS>:1883: read: connection reset by peer
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: read tcp <IP_ADDRESS>:55532-><IP_ADDRESS>:1883: read: connection reset by peer
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: read tcp <IP_ADDRESS>:55546-><IP_ADDRESS>:1883: read: connection reset by peer
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: read tcp <IP_ADDRESS>:55554-><IP_ADDRESS>:1883: read: connection reset by peer
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: read tcp <IP_ADDRESS>:55570-><IP_ADDRESS>:1883: read: connection reset by peer
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: read tcp <IP_ADDRESS>:55582-><IP_ADDRESS>:1883: read: connection reset by peer
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: read tcp <IP_ADDRESS>:55588-><IP_ADDRESS>:1883: read: connection reset by peer
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 tcp://<IP_ADDRESS>:1883 connection lost: read tcp <IP_ADDRESS>:55600-><IP_ADDRESS>:1883: read: connection reset by peer
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: not currently connected and ResumeSubs not set
[mqtt  ] ERROR 2023/02/20 13:19:45 error: not currently connected and ResumeSubs not set
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: connection lost before Subscribe completed
[mqtt  ] ERROR 2023/02/20 13:19:45 error: not currently connected and ResumeSubs not set
[mqtt  ] ERROR 2023/02/20 13:19:45 error: not currently connected and ResumeSubs not set
...

Nein, ohne die clientId ist alles gut

Sehr gut, dann hab ich ein Testszenario (und Du einen workaround ;).

Oh man - ich bin blind... Es lief ein Docker-Container zum Test (längst vergessen, dass es das System gibt) mit evcc. Wenn man das Log lesen würde, dann sieht man auch zwei unterschiedliche IPs, welche sich um die Client-ID streiten...

1676896287: New client connected from <IP_ADDRESS>:33898 as evcc (p2, c1, k30, u'evcc').
1676896287: New connection from <IP_ADDRESS>:54988 on port 1883.
1676896287: Client evcc already connected, closing old connection.
1676896287: New client connected from <IP_ADDRESS>:54988 as evcc (p2, c1, k30, u'evcc').
1676896287: New connection from <IP_ADDRESS>:33899 on port 1883.

Ich gehe dann mal lieber ins Bett 😞


Player UI freezes after ~5 seconds of playback

OS:
Windows 10
Issue Descriptions:
When I start a song the UI is responsive and okay for 5 seconds then it freezes. The song keeps playing, and the UI is fine again for the first 5 seconds on the next song that plays,
Steps to Reproduce:
This happens every single time I play a new track.

Google is having quite a few upgrade bugs at the moment.  I'm closing out all UI bugs until at least a few days have passed from their latest update.

Hi. Thanks for pretty nice app.
I also faced it. Tray program control menu also freezes sometimes.
And sometimes the interface freezes when changing the window focus.
I'm on Windows 10, Acer Laptop with Intel and Nvidia 860M.

@ViRGiL175 Disable desktop notifications 👍

It works... But why :)
Thank you anyway.


Upgrade to the latest version of Lombiq.Tests.UI (OCC-102)

Is your feature request related to a problem? Please describe
The version currently used runs the tested webapp as a separate process (harder to debug) whereas version 4.0.1 uses WebApplicationFactory to instantiate the webapp in the same process. This involves some breaking changes, so it's also necessary in case we will need additional features from the library in the future.
Describe the solution you'd like

Upgrade version
Make necessary changes according to migration docs here.
Review updated OC testing docs here.

Jira issue

@DAud-IcI What do you think about migrating to the new .NET 6.0 hosting model, in this issue? We already use this in other projects (example: https://github.com/Lombiq/Open-Source-Orchard-Core-Extensions/blob/dev/src/Lombiq.OSOCE.Web/Program.cs). I have to do things in Program.cs anyway, so this could be a good opportunity.

I'm in favor of it.


   WHY NOT BOLT?  MAYBE IN THE FUTURE! CANCELLED MY SUBSCRIPTION AFTER 2 HOURS.
I
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-6qkwza
Steps to reproduce
X
Expected behavior
Z
Screen Recording / Screenshot
No response
Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 130
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 58023017,
  "usedJSHeapSize": 54765217,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = LeonardSEO
Chat ID = 4e85cc1c08aa

Additional context
No response

@LeonardSEO I understand that you are frustrated and I can understand that, as I've been learning on how to use these tools like Bolt effectively. However, I believe you could choose better words to express yourself as a sign of respect to the bolt developers and the overall community. I hope you find the solution to your technical problem though. Cheers.

Apologies for the frustration during the beta! Tips for a better usage experience can be found in #678


[MonorepoBuilder] bump-interdependency command bug

The symbol ^ is lost when the command is called on Windows OS.

Actual for monorepo 8.x and 9.x versions.
Actual on PHP 7.4 and PHP 8.0
Only on Windows OS

Reproduce
Execute somethig like: vendor/bin/monorepo-builder.bat bump-interdependency "^2.9"
Expected
Output message:

[OK] Inter-dependencies of packages were updated to "^2.9"

All dependencies should be exposed to the version ^2.9
Actual
Output message:

[OK] Inter-dependencies of packages were updated to "2.9"

All dependencies are exposed to the version 2.9 instead of ^2.9

Hi,
thanks for reporting the issue. Unfortunatelly, there are no active Windows devs who can help out.
I can point you to direction, where this happens, but then we'll need your help to provide the fix.
It might happen due to your CLI escaping the `^. Then it we cut already here: https://github.com/symplify/symplify/blob/893fee82ec571ae840f235ebac1ebcbff3e340ba/packages/monorepo-builder/src/Command/BumpInterdependencyCommand.php#L66

Hmmm... Probably symfony bug?
Testing:
$version = $input->getArgument(self::VERSION_ARGUMENT);

var_dump($version);

Actual result:
$ vendor/bin/monorepo-builder.bat bump-interdependency "^2.9"
string(3) "2.9"

Lol, nope:
var_dump($_SERVER['argv']);

array:3 [
  0 => ...bin/../symplify/monorepo-builder/bin/monorepo-builder"
  1 => "bump-interdependency"
  2 => "2.9"
]

Perhaps the problem is something else. I think this is related to ansicon or the PhpStorm terminal.
In any case, this is not a monorepo bug.
Thanks!

P.S. Its ansicon bug. After completely removing this service, the error disappeared.

Cool, thanks for sharing!
How did you remove it? What it is actually?

How did you remove it?

ansicon -up
ansicon -U
Remove ansicon directory (in addition, you should stop all services associated with it, for example: winpty, env.exe etc)
And after restarting the terminal, the error was gone.

I see, thanks :+1:
Btw, I'm just curious. It seems you're quite skilled with CLI in Windows. Far beyond most Windows devs I meet. Why don't you use a *nix based OS?

Why don't you use a *nix based OS?

Because I have good PC and Steam :D

Because I have good PC and Steam :D

I see :laughing: . I solved this with dual boot ;)


Sharing of rendering results

Motivation and Context
Habitat-sim currently has the ability to draw RGB, Depth, and Semantic observations all on the same render pass, however, this isn't currently leveraged!  This PR adds the ability for sensor to "borrow" eachother's render results so that if you draw for an RGB sensor and have a Depth sensor that is configured identically, the Depth sensor won't invoke another draw but will instead just read the Depth Buffer from the RGB draw. For Replica scenes, we can share between RGB, Depth, and Semantic!
One question for reviewers:  I also tried an implementation that copies between RenderTargets instead of sharing them.  While this seems safer, that copy obviously has a cost and grows with resolution.  We currently don't make any assumptions that would be violated by this direct sharing so maybe it is fine?  If we do want this copy, my testing says that the cost of doing the copy in draw_observation is pretty high (performance with GPU2GPU drops to bellow without for 256x256 for instance).  Doing the copy in get_observation is less costly.
@mosra I left the code to copy between framebuffers in the PR to see if you knew if there was a way to do it faster.
How Has This Been Tested
New tests.
I re-ran the benchmark on the normal MP3D test scene and got
 ====== FPS (512 x 512, depth_only): 5624.3 =============
 ================ Performance (FPS) NPROC=1 ========
Resolution      rgb             rgbd            depth_only
128 x 128       3151.7          1510.4          2361.9
256 x 256       2750.8          1137.1          1893.8
512 x 512       1607.2          697.9           1315.9
 ====================================================
 ================ Performance (FPS) NPROC=3 =============
Resolution      rgb             rgbd            depth_only
128 x 128       7684.1          3423.9          5935.4
256 x 256       6339.5          2885.4          4878.6
512 x 512       3817.1          1929.5          3610.2
 ======================================================
 ================ Performance (FPS) NPROC=5 ===============
Resolution      rgb             rgbd            depth_only
128 x 128       10651.7         4819.9          9146.4
256 x 256       8940.7          4056.9          7848.4
512 x 512       6674.5          2939.8          5624.3
 =====================================================

Comparing to the existing results, this maybe matters for higher resolutions, but otherwise it surprisingly doesn't.  However, 17DRP5sb8fy is a reasonably lightweight scene.
1LXtFkjw3qL on the other-hand is much heavier and there it matters.  Before the PR:
 ================ Performance (FPS) NPROC=1 ==========
Resolution      rgb             rgbd            depth_only
128 x 128       1227.5          557.1           1129.8
256 x 256       1128.7          501.7           918.3
512 x 512       833.3           415.0           802.9
 =================================================

After:
 ================ Performance (FPS) NPROC=1 ========
Resolution      rgb             rgbd            depth_only
128 x 128       1289.9          868.7           1073.2
256 x 256       1270.8          855.0           1044.9
512 x 512       994.9           566.6           843.0
 ===============================================

Then with GPU2GPU transfer enabled we get close to zero-cost RGB-D
 ================ Performance (FPS) NPROC=1 ======
Resolution      rgb             rgbd            depth_only
128 x 128       1319.1          909.5           1219.3
256 x 256       1426.3          924.4           1207.0
512 x 512       1364.3          959.6           1125.2
 ==========================================

Types of changes
New feature (non-breaking change which adds functionality)

This looks like it will help speed up the habitat-challenge repos quite a bit! Well done.

@erikwijmans Any reason this still hasn't been merged? Are we blocked by something?

The speedups aren't high enough to justify the ugliness that is this solution IMO.  @mosra and I had a chat when I originally made this and the result of that (after some initial resistance from me) is that a better design would be to have a VisualSensor that inherently supports rendering multiple modalities (this would also reduce the ugliness that is making an agent with RGB-D + Sem agent currently), but that is a larger change that I haven't had time to make yet.


demo page won't show images

unsplash.it seems to be dead or heavy load.

Thanks for the heads-up but seems to be OK here

yes you are right.
must have been temporary.
Am 16.11.2016 um 22:23 schrieb Ashley White:

Thanks for the heads-up but seems to be OK here
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ashleydw/lightbox/issues/225#issuecomment-260973410,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMv1unJlRFwGzZsDP7LfYjvBJQJZBUopks5q-x_dgaJpZM4Kz8iB.

Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus


Decouple filesFirst option from sorting options in file explorer

I like files first as it is less confusing visually, but then I cannot have any sorting option.
I think it would be better to just make a different setting for this instead of adding all possible combinations.
Ideally, I would love a more advanced (multi) sorting:

Define common file types by extensions: { style: [css,sass,scss], script: [js], ... }
User define a custom order for file types: [ 'document', 'script', 'style', 'config', 'text' ]
Then order by extension, then by name...

Here's how I did it for a project I'm working on: codepen.io/ncodefun/pen/JwPgYO
The Javascript side of this is pretty straightforward, but I'm totally unfamiliar with VS code internals – maybe I could contribute if someone point me to the right direction!

I'm sorry but I just read the 87 related request's titles, nothing is even close to this request, please point me to the request you seem to think is a duplicate of this one, thanks.

Thank you. I fear the main point of this request is not addressed at all in these propositions (decoupling the filesFirst option) but I agree its all "related" feature requests, so I guess this one could be linked somehow to #27286. @bpasero ?

Ah sorry, just read to the bottom, thanks again, I'm out!


[Bug] Connecting to Rstudio workspace errors with "parameter not found"

Describe the bug
A clear and concise description of what the bug is.
Connecting to Rstudio workspace errors with "parameter not found"
To Reproduce
Steps to reproduce the behavior:

Go to '...' new created rstudio workspace
Click on 'connect
Scroll down to '....'
you will see something went wrong and further troubleshooting "parameter not found" erro

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Versions (please complete the following information):

Release Version installed [e.g. v1.0.3]
latest install of SWB and Studio templates.

Additional context
Add any other context about the problem here.

Set rstudio-user password
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (7) Failed to connect to localhost port 8787 after 17 ms: Connection refused
Note: AWS CLI version 2, the latest major version of the AWS CLI, is now stable and recommended for general use. For more information, see the AWS CLI version 2 installation instructions at: https:/
/docs.aws.amazon.com/cli/latest/userguide/install-cliv2.html
usage: aws [options]   [ ...] [parameters]
To see help text, you can run:
aws help
aws  help
aws   help
aws: error: argument --value: expected one argument
Stored rstudio public key in SSM


Replace URL, not domain

https://github.com/Fried-Chicken/ghost-static-site-generator/issues/3

@Stono


QDirStat

Describe the package
I'd like to request the package 'QDirStat' because it is helpful to be able to see a graphical representation of filetypes when trying to clear up space.
Image
Desktop

It is a very small tool (750 KiB), it's included in the Fedora package repos and wouldn't have a massive impact on the image size.


Fix for #375 - Added .Strict(bool) and .Verbatim(bool) methods on…

Description
Fix for #375 - Added .Strict(bool) and .Verbatim(bool) methods on QueryContainer that recursively apply the respective attribute to all subqueries. Also added a .Name(string) method on QueryContainer that names the (root) contained query.
Issues Resolved
#375
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Thanks @DumboJetEngine!


Jbaker/update build script

Alaska Airlines Pull Request
Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team
Summary by Sourcery
Build:

Update build script to include 'build:docs' in the build process.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[SPARK-18187][STREAMING] CompactibleFileStreamLog should not use "compactInterval" direcly with user setting.

What changes were proposed in this pull request?
CompactibleFileStreamLog relys on "compactInterval" to detect a compaction batch. If the "compactInterval" is reset by user, CompactibleFileStreamLog will return wrong answer, resulting data loss. This PR procides a way to check the validity of 'compactInterval', and calculate an appropriate value.
How was this patch tested?
When restart a stream, we change the 'spark.sql.streaming.fileSource.log.compactInterval' different with the former one.

Test build #68400 has started for PR 15827 at commit 4a7e28c.

Test build #68401 has started for PR 15827 at commit 23e1baf.

Test build #68400 has finished for PR 15827 at commit 4a7e28c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68400/
Test PASSed.

Test build #68401 has finished for PR 15827 at commit 23e1baf.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68401/
Test PASSed.

cc @zsxwing

Thanks for doing this. I just merged #15852. Could you close this PR, please?

@zsxwing OK，close it.


Update to support mmCIF

This PR includes updated backend support for reading mmCIF files. Code updated by @dhruvsatyapanthi007 and tested by @trprcll.

Was it intentional to commit all of the source files with a ~ on the end? I'm guessing these are side effects of whatever editor you are using?

Also the build currently fails without a preexisting obj directory... So maybe obj needs to be created when you type make ?


Fedora 35 Beta

I installed Howdy on Fedora 35 Beta, when authenticating via sudo I get the following messages:
libva info: VA-API version 1.13.0
libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so
libva info: va_openDriver() returns -1
libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
libva info: va_openDriver() returns -1
MFX: Can't initialize session
it works, but I don't like the messages, any advice how to get rid of them?

For what it's worth, I followed the trail to https://github.com/opencv/opencv/issues/17221, and a fix suggested there does get rid of the annoying warnings. Specifically, set OPENCV_VIDEOIO_PRIORITY_INTEL_MFX=0. (To make persistent, add export OPENCV_VIDEOIO_PRIORITY_INTEL_MFX=0 to ~/.profile or equivalent.)

@boltgolt, doesn't https://github.com/boltgolt/howdy/issues/595#issuecomment-964224376 demonstrate otherwise?

@boltgolt, I don't know. Apologies. I still can't discern what I was referencing.


Can't use Undo anymore

Godot version:
3.0.6
OS/device including version:
Windows 10
Issue description:
when i use tilemaps for my platforming game but i when undo ( Ctrl + Z ) a few times,
i get this error
core/undo_redo.cpp:337 - Condition ' action_level > 0 ' is true. returned: ""
core/undo_redo.cpp:316 - Condition ' action_level > 0 ' is true.
and then i can't undo anymore
is there any solution for my problem?
will their be a fix for this in a future update?
Open a new scene and place a few tiles then Undo the tile placements ( Alt + Z ) Until it gives the error above
https://github.com/godotengine/godot/issues
Minimal reproduction project:

We'll need detailed steps to reproduce the issue to be able to help you.

Sorry for the delay. I recorded the steps to recreate this error
https://youtu.be/BZh4iGWk568

sorry i misclicked with the close issue

@rayojarr The video died. Also I spam undo like mad, but no error appears. If you don't write the exact steps, I'll just close this issue. (also make sure to test it with 3.2 alpha)

Closing due to lack of update. Please comment if you can still reproduce this issue in the latest stable version of Godot.


Add experimental flag for ZSTD produce and fetch APIs

PR #873 delivers the last bit for ZSTD

Pre-release 1.14.0-beta.5 has the latest protocol version.


Evaluate adding Markdown Extensions

Markdown-It Syntax Extensions
Sub
H~2~0 → H2O
Sup
29^th^ → 29th
Inserted
++inserted++ → inserted
Mark
==marked== →  inserted
Footnote
Here is a footnote reference,[^1] and another.[^longnote]

[^1]: Here is the footnote.

Abbreviation
*[HTML]: Hyper Text Markup Language
*[W3C]:  World Wide Web Consortium

The HTML specification is maintained by the W3C.

Container
::: warning
*here be dragons*
:::

Output

here be dragons

Attributes
# header {.style-me}
paragraph {data-toggle=modal}

Output

header

paragraph

Possibly a charting option as well
https://medium.com/technical-writing-is-easy/diagrams-in-documentation-markdown-guide-4e78419e8d2f


fix: fixed the visibility of text in the docs

Description

Now whatever the theme would be, the text would be visible in the docs.

Related issue(s)

Resolves  #117

@ivangsa

/rtm


Fix issue where priority_brexit_taxon is nil

This prevents an error from being thrown when priority_brexit_taxon is nil because there isn't relevant taxon tagged to the content item

Could you add a changelog entry before you merge this please @theseanything


IRGen: Fix OpaqueStorageTypeInfo lowering

Can't call claimAll, rather need to call claimNext() according to the
number of expected explosions.
rdar://86069782

@swift-ci Please test


Product Pages: Fix Attire SVGs

E.g., https://main--caesars--hlxsites.hlx.page/caesars-palace/drafts/structured-content/restaurants/cafe-americano

Casual should have a t-shirt icon as seen in: https://www.caesars.com/caesars-palace/restaurants/cafe-americano
Similar issue seen for Formal & Business Casual attires.
Also, cuisine : American should be a burger instead of a fork and a knife.

I'm going to update the code to use the same text converted to lower-kebab-case as the icon name. As long as we have the icons in the code, we should then be all set.

@swetabar I've updated the code for cuisine to also be the same as attire. You need to find the missing icons and upload them with the right name of the svg as generated by the code (lower-kebab-case of the actual value from excel). Then it will work automatically


default value #to_hash error

Each time I try to set a default value to a class:
attribuite :some_class, Foo::SomeClass, default: proc { Foo::SomeClass }

I get this error:
Expected "Foo::SomeClass" to respond to #to_hash

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/26712803-default-value-to_hash-error?utm_campaign=plugin&utm_content=tracker%2F144935&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F144935&utm_medium=issues&utm_source=github).

I got this to work. Just need to initialize the default value.


convert regex_revalidate to cpp

This uses a std::shared_ptr of a std::vector for the rule set instead of a singly linked list with a manual atomic reference counter.  Performance is comparable, number of context switches is lower on this version, based on limited testing.

I've been more closely looking at regex_remap behavior for calls to traffic_ctl config reload.
Found a bug with the previous 'c' version where every time this is a called an extra config_continuation recurring task is started up, even if the plugin wasn't configured to run recurring configuration tasks.  That is actually fixable by examining the event which called the config_handler.
What I'm dealing with now is that remap plugins SHOULD reload their config files every time traffic_ctl config reload is called.  So the TSMgmtUpdateRegister(config_cont, "regex_revalidate"); call needs register a continuation that forces an immediate config reload for all plugin instances.

Another bad forehead slapper.  Any change to remap.config causes all remap plugins to be recreated from scratch, then replace the existing remap plugin, even if the rule itself did not change.  In order to not cause the regex_reval to reset (and start forcing assets stale all over again) I'll need to find some way to "pass the baton" from the existing instances to the new instances.

You can have plugin scope variables, so you might store a SHA of the configuration file there, and on reload block read the file and compute the SHA. If it's the same, reuse the existing parsed configuration.

At the moment I'm fixing the std::shared_ptr<> access as apparently it's not inherently thread safe itself.  Under what scenarios would the last modified time not be a sufficient check?

What I've done in the past is have an atomic boolean that's set when configuration update starts and cleared when it ends. The config update then does a CAS and if it doesn't set the bool, it just returns on the presumption another config update is already under way.

There is only one config continuation here that scans and sequentially updates all available configurations (this is for both the global and any remap plugins).  Since there's one continuation and it has a TSMutex assigned to it, there's no possible way for multiple simultaneous config updates to ever occur, correct??

This PR hasn't been updated for over 2 months.  If you would like to work on this please reopen.  Make sure it passes CI and doesn't have any merge conflicts.