Allow invitations to use public DID

Currently the framework only supports invitations that directly include the serviceEndpoint, recipientKeys and routingKeys. However the connection protocol RFC states that an invitation can use use a publicly resolvable DID. With the new ledger service from #82 we can now resolve public Indy / Sov DIDs.
Indy doesn't support DID docs yet, but we can retrieve the service information using an ATTRIB request I think? This information can be used to respond to the invitation.
Checklist

[x] Check if received invitation contains DID. Retrieve required data from ledger if present and then use that going forward.
[x] Allow to create an invitation with a DID instead of the separate attributes.
[x] Only use the public did for the invitation, for the other messages a peer did should still be used
[x] We need to store somewhere a public DID was used for the invitation. ACA-Py has a key in the record, should we also use this approach?

Questions

When creating an invitation with DID, should it just be a string parameter, or should we only allow to create invitation with the current agent public DID?
Are there other places in the framework where public DIDs can be used per the RFCs?

Not implemented yet, but Out-Of-Band Protocol can use public DIDs

Is there any plans to implement did exchange invitations with public DIDs? I see in issue #992 that there was work started on it as one point with no closure.

Yes i think documentation is the most important, and maybe adding some utils to make dids DIDComm-ready
One thing that is missing (i think?) is whether a did is rotated? I'm not 100%. Like if you want to use a did:web for invitation and then keep using that for the connection instead of a did:peer

Thanks for the clarifications here. So I went ahead and implemented invitations with public dids in my credo agent, however I always get an error stating Unable to resolve did document for did.  Here is what I'm doing,
When the agent is instructed to use a public did we do a oob.createInvitation.
In there we get the public did of the agent with this,
    const publicDidInfoRecord = await this.agent.genericRecords.findById('PUBLIC_DID_INFO')
    const content = publicDidInfoRecord.content as { didInfo: { did: string } }
    return content.didInfo.did

I put that did in the invitation options as invitationDid and try to create the invitation.
This is the full error I get.
error: {
    name: 'CredoError',
    message: "Unable to resolve did document for did '8yLAa5ZTNTxC4rkkgLMpq6': invalidDid undefined",
    status: 500,
    errors: [],
    stack: "CredoError: Unable to resolve did document for did '8yLAa5ZTNTxC4rkkgLMpq6': invalidDid undefined\n" +
      '    at DidResolverService.resolveDidDocument (/aries-backchannels/credo-ts/server/node_modules/@credo-ts/core/src/modules/dids/services/DidResolverService.ts:159:13)\n' +
      '    at async DidCommDocumentService.resolveServicesFromDid (/aries-backchannels/credo-ts/server/node_modules/@credo-ts/core/src/modules/didcomm/services/DidCommDocumentService.ts:21:25)\n' +
      '    at async OutOfBandApi.resolveInvitationRecipientKeyFingerprints (/aries-backchannels/credo-ts/server/node_modules/@credo-ts/core/src/modules/oob/OutOfBandApi.ts:951:41)\n' +
      '    at async OutOfBandApi.createInvitation (/aries-backchannels/credo-ts/server/node_modules/@credo-ts/core/src/modules/oob/OutOfBandApi.ts:233:38)'

Any idea what I'm doing wrong here? As I'm writing this I'm wondering if it should be a qualified did...

I don’t know the details, but we shouldn’t be creating anything new with unqualified DIDs.  I think your are trying to create a DIDComm connection, and if so, you should probably be using a did:peer:4 DID.

Actually I would expect the credo call for the publicDidInfoRecord to be returning a qualified did to me.

We don't have a 'Public DID' built-in configuration in Credo, so I guess you are following the strategy in AATH to save and retrieve the DID we want to use from a generic record.
in [AATH code] I see that it is saving public DID using unqualified Indy format (since it calls indyDidFromPublicKeyBase58), so @swcurran comment is relevant here, as the agent will not be able to resolve it. However, there is nothing wrong in creating an invitation using a non-peer DID, so I think it should work if you pass it to createInvitation in the format did:indy:{namespace}:{identifier}


Update dependencies

Update dependencies
Update CHANGELOG
Bump espflash and cargo-espflash version

I forget which library it is, but cc: @bjoernQ for the windows terminal issue just in case.

The problematic crate on Windows is crossterm - since this leaves it on 0.25.0 it should be fine.
We could update it with a workaround like described in https://github.com/esp-rs/espflash/pull/418#issuecomment-1717302410 .... but that workaround probably needs to be tested on other OSs or only get applied for Windows builds
But maybe leave it out of this PR and have a separate one for that


[PE-D][Tester C] Typo at the "Quick Start" section of User Guide

In the Quick Start section, it mentions "A GUI similar to the below should appear in a few seconds. The application will starts will an empty MediMate." in the "Quick Start" section of the User Guide.
There seems to be a typo in this line, perhaps it could be changed to "The application will starts with an empty MediMate."

Labels: type.DocumentationBug severity.Low
original: JavonTeo/ped#1

Fix


Add integration tests for KubernetesScriptServiceV1Alpha

Are you a customer of Octopus Deploy? Please contact our support team so we can triage your PR, so that we can make sure it's handled appropriately.
Background

Results

Fixes https://github.com/OctopusDeploy/Issues/issues/... (optional public issue)
Fixes https://github.com/OctopusDeploy/ResearchAndDevelopment/issues/... (optional private issue)
See How we use GitHub Issues (including this flowchart
Before

After

How to review this PR

Quality :heavy_check_mark:

Pre-requisites

[ ] I have read How we use GitHub Issues for help deciding when and where it's appropriate to make an issue.
[ ] I have considered informing or consulting the right people, according to the ownership map.
[ ] I have considered appropriate testing for my change.

Closing as this has been superseded by #887 and #888


Add VP support to example.

Adding VP support to futher expand the example.
Using did:key for VC and did:web for VP to add variety.
Print out logging as we go.
Print readable first stack trace if there are verify errors.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 90.44%. Comparing base (e02e347) to head (40f66d1).

Additional details and impacted files
@@                  Coverage Diff                  @@
##           example-usage-script     #184   +/-   ##
=====================================================
  Coverage                 90.44%   90.44%
=====================================================
  Files                         5        5
  Lines                      1057     1057
=====================================================
  Hits                        956      956
  Misses                      101      101

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e02e347...40f66d1. Read the comment docs.


"Modifying Preferences from Developer Toolbar" was supposed to appear, but doesn't

Request type

[ ] Please close this issue, I accidentally submitted it without adding any details
[x] New documentation
[ ] Correction or update

Details

Editing "Developer Toolbar" section in Mozillazine was supposed to be here, but the link doesn't go anywhere

@JJJoseph -- It would be helpful if you could tell me the page that includes the link so I can fix or remove the reference.


Add a system property to configure the daemon log level

Related to https://github.com/gradle/gradle/issues/2688
Currently, the daemon always logs with DEBUG log level in the daemon log. This was fine up to now (mostly), since not much happened between builds.
When file watching is enabled, a lot happens between builds - file changes are collected. In order to prevent the daemon log to overflow, it should be possible to set the log level differently - e.g. to INFO.
This PR introduces a system property org.gradle.daemon.loglevel which the daemon tries to pick up from the current build context and then changes the logging level after the build accordingly.

No, org.gradle.daemon.disable-output only disables the output to the console while the build is running, not to the daemon log.

In that case I think we should re-initialize the log level before we check that switch.

If we re-initialize logging before checking org.gradle.daemon.disable-output, then setting the logging doesn't work anymore, since stopping the logging router will reset the logging to the previous state, which is whatever the daemon had at the beginning.

Switching to info doesn't seem feasible, since then we lose the timestamps in the daemon logs, which seem to be important for users. It seems hard to produce timestamps with info logging in the daemon logs, since the logs are emitted by StyledTextOutputBackedRenderer for all consumers, and those either contain the timestamps (debug log), or they don't. All the meta-data is lost for the downstream consumers of the log messages.
Closing this PR.


Replace code style checker w/auto formatter

Please see individual commits.
This PR replaces the pycodestyle code style checking tool with the black tool which can also auto-format Python code according to PEP8 standards, and there is a commit to update to the auto-formatted code generated by black.

Thanks. Just pushed a commit which will hopefully fix this and allow for all Python versions to work.


Frontend With Framework - What and Why React.js

NEED TO CONTAIN

What is React.js
Why React.js
Advantage of React.js
Dis Advantages of React.js

Also make sure -
Avoid copy/paste, We will be checking.
Changes should be made inside the Frontend_Web_Development_React_Angular_Vue/ React inside Frontend_Web_Development_React_Angular_Vue branch.
Task will be assigned on first come first serve
Check out Contribution Guidelines
and Code Of Conduct

can i work on this ?

Can I be assigned the above task?

@Ravinayak07 you can only work at a single task at a time
do you want to do this or other one

@trip0le wait for some time,we are following first come first service,If he is doing another one we will assign this to you

@trip0le you can do it

Can I work on this

@Ravinayak07 you can only work at a single task at a time
do you want to do this or other one

I want to work on this

@Ravinayak07 you can only work at a single task at a time
do you want to do this or other one

ok i will work on other one.

@trip0le you can do it
Thank you Sir

Can I work on this sir?

I am interested to do it. Please consider me if it is reassigned.

I can work on this

I wish to contribute in the form of documentation. Assign me this work.

@trip0le any updates

I can work on this. Please consider me if it is reassigned

I can work on this

@trip0le  any updates please inform us

@trip0le any updates please inform us

Sir, I am working on the above issue.
Is there a deadline by which I have to complete my work?

@trip0le take your time.One week is max time.Please try to finish before it.Because things are planned according to week

@trip0le take your time.One week is max time.Please try to finish before it.Because things are planned according to week

Sure Sir

@anandhu720 Sir, I was thinking of making a power point presentation with audio on the above issue. In that case,  if I push a readme file having the google drive link of the presentation in my forked repository and then send a pull request to the Frontend_Web_Development_React_Angular_Vue branch from the same, will it be acceptable?

@anandhu720 Sir, I have finished working on the above issue. Would you please check if whether its alright?


feat: Expose getActiveEditor and getActiveEditorState

Partially implements feature request #5333
Submit a pull request and waiting for the team's opinion.
 Need this one to access parent editor during importJSON for my own purpose.

If we do expose them, I'd like to add typedoc doc blocks to them so they show up in the API docs and people have a sense of how they work (e.g., what is the concept of "active" editor)

@acywatson I've added two $-prefixed functions. Do you have any comments on the naming/doc?


API capitalization typos

Change 'Api' to 'API' on line 20?
https://github.com/CartoDB/cartodb/blob/6324fcf5e0def3f136eb7870741eb15d75b882c6/app/views/admin/client_applications/api_key.html.erb#L20

There has been no activity on this issue for more several months. We are closing it. If you think this still needs to be addressed please open a new issue.


Update instructor notes

@csmagnano and @cmilica can you please briefly outline instructor notes from the episodes you led on January 25?  These don't need to be detailed, but it will be very helpful to capture the interactive exercises you led and the figures you drew on the board (e.g. bias/variance plots, logistic regression plots).
Other notes we can include:

Write the workshop website URL on the board in the beginning
Show participants what screen they should see if the ml4bio software is correctly installed
Participants want to know what is happening behind the scenes of the ml4bio software
Express that the ml4bio software is only for conceptual teaching, applied ML research in biology requires batch processing and sometimes high-throughput computing
I used DNA binding as the biological example at the end of the first lesson, what is the biological motivation, why is it useful to have a trained model that can extrapolate to new samples

We should also update the instructor notes based on the February 25, 2021 workshop.


remove jest from project

What does this change?
Remove jest from project

This still does not deal with:

@types/jest
ts-jest

Addressed in #31


Use chttpd provided functions

couch_mrview_show's usage of couch_chttp:send_external_response
brakes CORS support. Since couch_httpd's version of send_external_response
doesn't have support for CORS compared to chttpd's version.
Other couch_http's functions are switched to corresponding chttpd's
versions as well.
COUCHDB-2656

Wouldn't it break now CORs for backdoor interface? Also, wouldn't CORs implemented for chttpd solve this problem https://github.com/apache/couchdb-chttpd/pull/8 ?

Wouldn't it break now CORs for backdoor interface?

I'll add test case for it. However I'm not sure where to put it. On one hand we have all CORs related tests in couch/test/couchdb_cors_tests on the other hand it would introduce one more PR.

Also, wouldn't CORs implemented for chttpd solve this problem apache/couchdb-chttpd#8

apache/couchdb-chttpd#8 wouldn't solve the problem with couch_mrview_show. The changes in apache/couchdb-chttpd#8 are compatible with this PR though.

Wouldn't it break now CORs for backdoor interface?

I'll add test case for it. However I'm not sure where to put it. On one hand we have all CORs related tests in couch/test/couchdb_cors_tests on the other hand it would introduce one more PR.

I think we should move all the tests which are requires full server set up to the couchdb repository while in subprojects repos maintain only the tests which are tests related project modules without interactions with the other projects. In other simpler words: couchdb for integrational/functional tests, couchdb-X - for unit tests.

@kxepal: You are right this change would brake backdoor interface.
Here we need to call chttpd_external version of the json_req_obj for clustered and couch_httpd_external one for backdoor. The difference between the two versions is in set of properties returned and in couch_db:get_db_info -> fabric:get_db_info However I really don't like introducing the knowledge about type of a call to couch_mrview_show. I'm looking for alternative approaches.

@iilyak I have only one thought here: make one httpd for all the couch (: Suddenly, this is epic task for a week or two may be, but definitely will solve a lot of compatibility issues between cluster/backdoor interface. I hardly can find a time for even more trivial things, not for such massive refactoring, but if you could lobby this problem and fix it - that would be awesome and helpful for the whole project.
However, all this problem as I see is about to add one more argument to each httpd_handler that defined the interface and shuffle and unite the code of chttpd and httpd. Plus think about how to start this server twice with different config sections.

The problem is fixed by following commit
Test case is added in PR


Feature Request : Multiple Profiles

Feature Request : Multiple Profiles
This feature could seperate your extentions & Themes to Focus On ONE thing at a time like for example i am working on An HTML project but the python snippets/extensions are interfering or Increasing VS Code Launch Time

/duplicate
See https://github.com/microsoft/vscode/issues/116740#issuecomment-1124498799

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


FPU L/S instructions data sections.

Hi,
Where are the FP load/stores  targeted to? What are the data patterns for them?
Are these valid FP numbers or just any random patterns? Are these data sections shared with fixed L/S instructions?
When random program is executed the FP regs have tendency to saturation - to become NaNs or 0 etc.
Does riscv-dv "refresh" FPU regs periodically with valid FP numbers?
Thanks in advance
Alex

We currently have a routine to initialize the floating GPR to some interesting values
https://github.com/google/riscv-dv/blob/master/src/riscv_asm_program_gen.sv#L641
This doesn't apply to data sections. It's done at the beginning of the program. We can make it randomly injected in the program to "refresh FPU"

We currently have a routine to initialize the floating GPR to some interesting values
https://github.com/google/riscv-dv/blob/master/src/riscv_asm_program_gen.sv#L641
This doesn't apply to data sections. It's done at the beginning of the program. We can make it randomly injected in the program to "refresh FPU"

there is one more problem - fflags are also saturate with time, reducing their testing efficiency.
Also can the RM in fcsr be selected/updated randomly multiple times in the test, including a small percentage of illegal values?

there is one more problem - fflags are also saturate with time, reducing their testing efficiency.
Also can the RM in fcsr be selected/updated randomly multiple times in the test, including a small percentage of illegal values?


Issue with a complex data structure

Hi, could you tell any problem with this data? It doesn't work however I try. The exported file Skills.json is always empty.
https://github.com/laicasaane/BakingSheet/commit/330e426e01594451bb16818520faa779f57e03be

Seems like your xlsx contains empty row - which BakingSheet consider as end of the file. (I have not found a better way to detect yet.)

I've implemented something called empty row streak threshold to allow bypassing a number of empty rows before considering it's the end of file. Using this implementation for a while makes me forget that the original BakingSheet doesn't have that mechanism.
https://github.com/Zitga-Tech/ZBase.Foundation.Data/blob/e79ff18bad5e3892a38f2155acfdd9ce788b46a8/Packages/ZBase.Foundation.Data/Data.Authoring/Converters/DatabaseRawSheetImporter.cs#L27C42-L27C42

I might adopt something like that in future.


Catalina 10.15.7 Support?

Hey I was trying to troubleshoot your method to run the game for Mac OS and was having trouble getting the game to run. I saw that you had only posted a successful go with Catalina 10.15.5 and was wondering if that was the issue I was having to get the game to run. I merged the files like you said and moved the game file from the steam common apps to my desktop and renamed it but to no avail. Any help would be appreciated- thanks

As stated in the ReadMe, the Steam version is not supported. Moving it out of the Steam directory won't help in this case.
The reason I added the part about renaming/moving is because macOS may remember/cache some info about an app, such as the fact that it's 32bit and doesn't run. In these cases, renaming or moving an app will make macOS forget about those details and try to start the app again.
Here's the problem with the Steam version:
Upon starting the game, no matter where you put it, the app's included SteamWorks logic sees that it's not authenticated with Steam, so then it will launch Steam for authentication and file consistency. If it can authenticate, it will attempt to start the game, but not before it has made sure you have the original (32bit) Steam files.
Simply put, the reason that the Steam version isn't supported is because it would require disabling/removing the Steam authentication from the game app.
I will give it try on 10.15.7 and get back to you when I got that up and running, soon-ish.

Just tested HuniePop (non-Steam version) on macOS Catalina 10.15.7 and it's working without issues.

The only additional fix someone might need to apply, is making the HuniePop binary executable using the terminal:
chmod u+x HuniePop.app/Contents/MacOS/HuniePop

I will add this to the ReadMe.


Attempt to put canned bucket ACL of "public-read" results in "Invalid Request"

Describe the bug
Direct communication with AWS (after enabling ACLs and public access to the bucket) results in the expected behavior, but attempting to put the ACL via versity results in the following being returned:
An error occurred (InvalidRequest) when calling the PutBucketAcl operation: Invalid Request

To Reproduce

Create a bucket in the Amazon S3 console.
Select the bucket and select the Permissions tab.
Check the Block public access section and select Edit and set Block all public access to off if not already off.
Go to the Object Ownership section, select Edit, and select ACLs Enabled and set Object Ownership to Object Writer if this hasn't already been done.
Set the AWS_ENDPOINT_URL value to point to the versity gateway, and send the following command: aws --no-verify-ssl s3api put-bucket-acl --bucket <name> --acl public-read

Expected behavior
The request succeeds, and the get-bucket-acl command returns a Grants element similar to the following:
{
     "Grantee": {
         "Type": "Group",
         "URI": "http://acs.amazonaws.com/groups/global/AllUsers"
     },
     "Permission": "READ"
 }

Server Version
Version  : v0.21
Build    : 10ed210
BuildTime: 2024-05-02_11:46:50PM
Darwin Lukes-MacBook-Pro.local 23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:12:25 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T6030 arm64

More debugging info:  in s3cmd, as with aws, the setacl command works, but with communication via versitygw, the following error is returned:
Problem: <class 'AttributeError: 'ConfigParser' object has no attribute 'readfp'
   S3cmd:   2.4.0
   python:   3.12.2 (main, Feb  6 2024, 20:19:44) [Clang 15.0.0 (clang-15<IP_ADDRESS>.5)]
   environment LANG=NOTSET

Thanks for the bug report, I'll take a look. For your information our implementation of Bucket ACLs differ from traditional AWS ACLs. Some features aren't supported in our end. I'll double check this part.


FS improvements for unit tests

Towards fixing #114024

many teardown methods of our unit tests are using rimraf with the MOVE option.
this causes that the first error which occurs during moving is swallowed i.e. see the error being ignored here https://github.com/microsoft/vscode/blob/6d2e0aa21d386fbc4096c6a801b9248b866a0c6d/src/vs/base/node/pfs.ts#L96
this most likely hides the fact that some tests continue writing to the fixture directory even after the test has signaled completion (this is the root problem here)
not waiting for unlinking and not using graceful-fs in our unit tests causes some tests which are unlucky and are not first in the mocha runner schedule to fail in their teardown hook
mocha does not recover from a failure in a teardown hook even if retry is used (i.e. even if the test is decorated with flakyTest)

This PR aims to expose the tests which write to the fixture directory even after the test has signaled completion. By using rimraf with the UNLINK option, any error will immediately become visible. I have already seen a ENOTEMPTY being thrown from the BackupTracker test. The best fix would be for the tests to be analyzed and repaired to stop writing to the fixture directory after they signal completion. The bandaid approach that I have started is to leave a TODO in the test and to use rimrafWithRetries especially in these tests where this ENOTEMPTY is observed.

Actually there is more to it. It looks like an EPERM can also be thrown when deleting a file which is still being written to:
https://github.com/microsoft/vscode/pull/114026/checks?check_run_id=1668335479#step:11:7692
  6406 passing (1m)
  38 pending
  1 failing

  1) BackupTracker
       "after each" hook for "should hot exit (reason: QUIT, windows: single, workspace)":
     Error: EPERM: operation not permitted, lstat 'C:\Users\RUNNER~1\AppData\Local\Temp\vsctests\backuprestorer\f1517443-8841-46bc-8cde-5c81baa87dca\Backups\2746e85e3aa3db1143f8b6945d3619a5\file\3852fac775a9ca8e1002a47d2dc725cf'

Again it is the BackupTracker. This is definite proof that these tests continue writing to their fixture directories after signaling completion.

Actually there is more to it. It looks like an EPERM can also be thrown when deleting a file which is still being written to:
https://github.com/microsoft/vscode/pull/114026/checks?check_run_id=1668335479#step:11:7692
  6406 passing (1m)
  38 pending
  1 failing

  1) BackupTracker
       "after each" hook for "should hot exit (reason: QUIT, windows: single, workspace)":
     Error: EPERM: operation not permitted, lstat 'C:\Users\RUNNER~1\AppData\Local\Temp\vsctests\backuprestorer\f1517443-8841-46bc-8cde-5c81baa87dca\Backups\2746e85e3aa3db1143f8b6945d3619a5\file\3852fac775a9ca8e1002a47d2dc725cf'

Again it is the BackupTracker. This is definite proof that these tests continue writing to their fixture directories after signaling completion.

OK. This test is just really really annoying.
Even retrying 5 times to delete the fixture directory fails sometimes -- https://dev.azure.com/monacotools/Monaco/_build/results?buildId=99749&view=logs&j=672276a2-8d3a-5fab-615d-090c51352f92&t=6ad30dce-518e-54c1-94da-00d19cce9354&l=7718:
2021-01-08T12:25:53.8249062Z     Hot Exit
2021-01-08T12:25:53.8251719Z       "onExit" setting
2021-01-08T12:25:53.8735822Z         âˆš should hot exit on non-Mac (reason: CLOSE, windows: single, workspace) (38ms)
2021-01-08T12:25:53.8905155Z [1772:0108/122553.889:INFO:CONSOLE(56)] "Ignoring error in retry 1 of 5:  Error: ENOTEMPTY: directory not empty, rmdir 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\7d13d710-7fdf-42fb-98c6-46b2bafaa13a\Backups\2746e85e3aa3db1143f8b6945d3619a5\file'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:53.8920053Z [1772:0108/122553.890:INFO:CONSOLE(56)] "Ignoring error in retry 2 of 5:  Error: EPERM: operation not permitted, lstat 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\7d13d710-7fdf-42fb-98c6-46b2bafaa13a\Backups\2746e85e3aa3db1143f8b6945d3619a5\file\dda638bb65409922442ccdd71cf1edb6'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:53.9465342Z         âˆš should hot exit on non-Mac (reason: CLOSE, windows: single, empty workspace) (39ms)
2021-01-08T12:25:53.9643588Z [1772:0108/122553.963:INFO:CONSOLE(56)] "Ignoring error in retry 1 of 5:  Error: ENOTEMPTY: directory not empty, rmdir 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\0f247949-a849-4c66-acfe-5063b1c01aed\Backups\2746e85e3aa3db1143f8b6945d3619a5\file'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:53.9657238Z [1772:0108/122553.964:INFO:CONSOLE(56)] "Ignoring error in retry 2 of 5:  Error: EPERM: operation not permitted, lstat 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\0f247949-a849-4c66-acfe-5063b1c01aed\Backups\2746e85e3aa3db1143f8b6945d3619a5\file\3a7efecfe644728728903fa292f0b5b2'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:53.9672344Z [1772:0108/122553.966:INFO:CONSOLE(56)] "Ignoring error in retry 3 of 5:  Error: EPERM: operation not permitted, lstat 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\0f247949-a849-4c66-acfe-5063b1c01aed\Backups\2746e85e3aa3db1143f8b6945d3619a5\file\3a7efecfe644728728903fa292f0b5b2'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:53.9986223Z         âˆš should NOT hot exit (reason: CLOSE, windows: multiple, workspace)
2021-01-08T12:25:54.0210109Z         âˆš should NOT hot exit (reason: CLOSE, windows: multiple, empty workspace)
2021-01-08T12:25:54.0927763Z         âˆš should hot exit (reason: QUIT, windows: single, workspace) (46ms)
2021-01-08T12:25:54.1102831Z [1772:0108/122554.109:INFO:CONSOLE(56)] "Ignoring error in retry 1 of 5:  Error: ENOTEMPTY: directory not empty, rmdir 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\728c6b3c-0705-49dc-9f82-c0d917c37550\Backups\2746e85e3aa3db1143f8b6945d3619a5\file'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:54.1114752Z [1772:0108/122554.110:INFO:CONSOLE(56)] "Ignoring error in retry 2 of 5:  Error: EPERM: operation not permitted, lstat 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\728c6b3c-0705-49dc-9f82-c0d917c37550\Backups\2746e85e3aa3db1143f8b6945d3619a5\file\3852fac775a9ca8e1002a47d2dc725cf'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:54.1128861Z [1772:0108/122554.111:INFO:CONSOLE(56)] "Ignoring error in retry 3 of 5:  Error: EPERM: operation not permitted, lstat 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\728c6b3c-0705-49dc-9f82-c0d917c37550\Backups\2746e85e3aa3db1143f8b6945d3619a5\file\3852fac775a9ca8e1002a47d2dc725cf'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:54.1144999Z [1772:0108/122554.113:INFO:CONSOLE(56)] "Ignoring error in retry 4 of 5:  Error: EPERM: operation not permitted, lstat 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\728c6b3c-0705-49dc-9f82-c0d917c37550\Backups\2746e85e3aa3db1143f8b6945d3619a5\file\3852fac775a9ca8e1002a47d2dc725cf'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:54.1755928Z         âˆš should hot exit (reason: QUIT, windows: single, empty workspace)
2021-01-08T12:25:54.1932182Z [1772:0108/122554.192:INFO:CONSOLE(56)] "Ignoring error in retry 1 of 5:  Error: ENOTEMPTY: directory not empty, rmdir 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\cb3e2d0f-52ec-4276-a19d-7f521f74e565\Backups\2746e85e3aa3db1143f8b6945d3619a5\file'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:54.2456466Z         âˆš should hot exit (reason: QUIT, windows: multiple, workspace) (39ms)
2021-01-08T12:25:54.2643971Z [1772:0108/122554.263:INFO:CONSOLE(56)] "Ignoring error in retry 1 of 5:  Error: ENOTEMPTY: directory not empty, rmdir 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\19911ac7-5b01-4de2-95ca-c3d5aa51dec3\Backups\2746e85e3aa3db1143f8b6945d3619a5\file'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:54.2663334Z [1772:0108/122554.265:INFO:CONSOLE(56)] "Ignoring error in retry 2 of 5:  Error: EPERM: operation not permitted, lstat 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\19911ac7-5b01-4de2-95ca-c3d5aa51dec3\Backups\2746e85e3aa3db1143f8b6945d3619a5\file\45f70f99ede8991195b760b6b84bbd67'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:54.3195077Z         âˆš should hot exit (reason: QUIT, windows: multiple, empty workspace)
2021-01-08T12:25:54.3355907Z [1772:0108/122554.334:INFO:CONSOLE(56)] "Ignoring error in retry 1 of 5:  Error: ENOTEMPTY: directory not empty, rmdir 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\65a65541-bb98-4208-a7f1-5c5d51fe7353\Backups\2746e85e3aa3db1143f8b6945d3619a5\file'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:54.3369864Z [1772:0108/122554.336:INFO:CONSOLE(56)] "Ignoring error in retry 2 of 5:  Error: EPERM: operation not permitted, lstat 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\65a65541-bb98-4208-a7f1-5c5d51fe7353\Backups\2746e85e3aa3db1143f8b6945d3619a5\file\1b7340a36de1e1c3636b8291f12cf492'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:54.3382834Z [1772:0108/122554.337:INFO:CONSOLE(56)] "Ignoring error in retry 3 of 5:  Error: EPERM: operation not permitted, lstat 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\65a65541-bb98-4208-a7f1-5c5d51fe7353\Backups\2746e85e3aa3db1143f8b6945d3619a5\file\1b7340a36de1e1c3636b8291f12cf492'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:54.3395365Z [1772:0108/122554.338:INFO:CONSOLE(56)] "Ignoring error in retry 4 of 5:  Error: EPERM: operation not permitted, lstat 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\65a65541-bb98-4208-a7f1-5c5d51fe7353\Backups\2746e85e3aa3db1143f8b6945d3619a5\file\1b7340a36de1e1c3636b8291f12cf492'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)

OK. This test is just really really annoying.
Even retrying 5 times to delete the fixture directory fails sometimes -- https://dev.azure.com/monacotools/Monaco/_build/results?buildId=99749&view=logs&j=672276a2-8d3a-5fab-615d-090c51352f92&t=6ad30dce-518e-54c1-94da-00d19cce9354&l=7718:
2021-01-08T12:25:53.8249062Z     Hot Exit
2021-01-08T12:25:53.8251719Z       "onExit" setting
2021-01-08T12:25:53.8735822Z         âˆš should hot exit on non-Mac (reason: CLOSE, windows: single, workspace) (38ms)
2021-01-08T12:25:53.8905155Z [1772:0108/122553.889:INFO:CONSOLE(56)] "Ignoring error in retry 1 of 5:  Error: ENOTEMPTY: directory not empty, rmdir 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\7d13d710-7fdf-42fb-98c6-46b2bafaa13a\Backups\2746e85e3aa3db1143f8b6945d3619a5\file'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:53.8920053Z [1772:0108/122553.890:INFO:CONSOLE(56)] "Ignoring error in retry 2 of 5:  Error: EPERM: operation not permitted, lstat 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\7d13d710-7fdf-42fb-98c6-46b2bafaa13a\Backups\2746e85e3aa3db1143f8b6945d3619a5\file\dda638bb65409922442ccdd71cf1edb6'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:53.9465342Z         âˆš should hot exit on non-Mac (reason: CLOSE, windows: single, empty workspace) (39ms)
2021-01-08T12:25:53.9643588Z [1772:0108/122553.963:INFO:CONSOLE(56)] "Ignoring error in retry 1 of 5:  Error: ENOTEMPTY: directory not empty, rmdir 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\0f247949-a849-4c66-acfe-5063b1c01aed\Backups\2746e85e3aa3db1143f8b6945d3619a5\file'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:53.9657238Z [1772:0108/122553.964:INFO:CONSOLE(56)] "Ignoring error in retry 2 of 5:  Error: EPERM: operation not permitted, lstat 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\0f247949-a849-4c66-acfe-5063b1c01aed\Backups\2746e85e3aa3db1143f8b6945d3619a5\file\3a7efecfe644728728903fa292f0b5b2'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:53.9672344Z [1772:0108/122553.966:INFO:CONSOLE(56)] "Ignoring error in retry 3 of 5:  Error: EPERM: operation not permitted, lstat 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\0f247949-a849-4c66-acfe-5063b1c01aed\Backups\2746e85e3aa3db1143f8b6945d3619a5\file\3a7efecfe644728728903fa292f0b5b2'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:53.9986223Z         âˆš should NOT hot exit (reason: CLOSE, windows: multiple, workspace)
2021-01-08T12:25:54.0210109Z         âˆš should NOT hot exit (reason: CLOSE, windows: multiple, empty workspace)
2021-01-08T12:25:54.0927763Z         âˆš should hot exit (reason: QUIT, windows: single, workspace) (46ms)
2021-01-08T12:25:54.1102831Z [1772:0108/122554.109:INFO:CONSOLE(56)] "Ignoring error in retry 1 of 5:  Error: ENOTEMPTY: directory not empty, rmdir 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\728c6b3c-0705-49dc-9f82-c0d917c37550\Backups\2746e85e3aa3db1143f8b6945d3619a5\file'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:54.1114752Z [1772:0108/122554.110:INFO:CONSOLE(56)] "Ignoring error in retry 2 of 5:  Error: EPERM: operation not permitted, lstat 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\728c6b3c-0705-49dc-9f82-c0d917c37550\Backups\2746e85e3aa3db1143f8b6945d3619a5\file\3852fac775a9ca8e1002a47d2dc725cf'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:54.1128861Z [1772:0108/122554.111:INFO:CONSOLE(56)] "Ignoring error in retry 3 of 5:  Error: EPERM: operation not permitted, lstat 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\728c6b3c-0705-49dc-9f82-c0d917c37550\Backups\2746e85e3aa3db1143f8b6945d3619a5\file\3852fac775a9ca8e1002a47d2dc725cf'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:54.1144999Z [1772:0108/122554.113:INFO:CONSOLE(56)] "Ignoring error in retry 4 of 5:  Error: EPERM: operation not permitted, lstat 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\728c6b3c-0705-49dc-9f82-c0d917c37550\Backups\2746e85e3aa3db1143f8b6945d3619a5\file\3852fac775a9ca8e1002a47d2dc725cf'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:54.1755928Z         âˆš should hot exit (reason: QUIT, windows: single, empty workspace)
2021-01-08T12:25:54.1932182Z [1772:0108/122554.192:INFO:CONSOLE(56)] "Ignoring error in retry 1 of 5:  Error: ENOTEMPTY: directory not empty, rmdir 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\cb3e2d0f-52ec-4276-a19d-7f521f74e565\Backups\2746e85e3aa3db1143f8b6945d3619a5\file'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:54.2456466Z         âˆš should hot exit (reason: QUIT, windows: multiple, workspace) (39ms)
2021-01-08T12:25:54.2643971Z [1772:0108/122554.263:INFO:CONSOLE(56)] "Ignoring error in retry 1 of 5:  Error: ENOTEMPTY: directory not empty, rmdir 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\19911ac7-5b01-4de2-95ca-c3d5aa51dec3\Backups\2746e85e3aa3db1143f8b6945d3619a5\file'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:54.2663334Z [1772:0108/122554.265:INFO:CONSOLE(56)] "Ignoring error in retry 2 of 5:  Error: EPERM: operation not permitted, lstat 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\19911ac7-5b01-4de2-95ca-c3d5aa51dec3\Backups\2746e85e3aa3db1143f8b6945d3619a5\file\45f70f99ede8991195b760b6b84bbd67'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:54.3195077Z         âˆš should hot exit (reason: QUIT, windows: multiple, empty workspace)
2021-01-08T12:25:54.3355907Z [1772:0108/122554.334:INFO:CONSOLE(56)] "Ignoring error in retry 1 of 5:  Error: ENOTEMPTY: directory not empty, rmdir 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\65a65541-bb98-4208-a7f1-5c5d51fe7353\Backups\2746e85e3aa3db1143f8b6945d3619a5\file'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:54.3369864Z [1772:0108/122554.336:INFO:CONSOLE(56)] "Ignoring error in retry 2 of 5:  Error: EPERM: operation not permitted, lstat 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\65a65541-bb98-4208-a7f1-5c5d51fe7353\Backups\2746e85e3aa3db1143f8b6945d3619a5\file\1b7340a36de1e1c3636b8291f12cf492'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:54.3382834Z [1772:0108/122554.337:INFO:CONSOLE(56)] "Ignoring error in retry 3 of 5:  Error: EPERM: operation not permitted, lstat 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\65a65541-bb98-4208-a7f1-5c5d51fe7353\Backups\2746e85e3aa3db1143f8b6945d3619a5\file\1b7340a36de1e1c3636b8291f12cf492'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)
2021-01-08T12:25:54.3395365Z [1772:0108/122554.338:INFO:CONSOLE(56)] "Ignoring error in retry 4 of 5:  Error: EPERM: operation not permitted, lstat 'C:\Users\VSSADM~1\AppData\Local\Temp\vsctests\backuprestorer\65a65541-bb98-4208-a7f1-5c5d51fe7353\Backups\2746e85e3aa3db1143f8b6945d3619a5\file\1b7340a36de1e1c3636b8291f12cf492'", source: file:///D:/a/1/s/out-build/vs/base/node/pfs.js (56)

I owe you a 🍺 for this one.

I owe you a 🍺 for this one.


Some translation changes relates to Ukrainian language.

- Add Ukrainian translation into templates/home.tmpl
- Fix Ukrainian language name in conf/app.ini
      because on Ukrainian 'language' is female.
- Add me as translator into conf/locale/TRANSLATORS

Thank you! I used Google Translator... good to have something to blame :trollface:


National Security Group

[Enter feedback here]
My guess tells me that this was intended to be "Network Security Group" and not National.

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

ID: 013a2c17-bda2-11bd-2a61-d9f8c8efe728
Version Independent ID: 013a2c17-bda2-11bd-2a61-d9f8c8efe728
Content: Virtual Network support for Power Platform overview (preview) - Power Platform
Content Source: power-platform/admin/vnet-support-overview.md
Service: power-platform
Sub-service: admin
GitHub Login: @ritesp
Microsoft Alias: ritesp

Thanks for your comment, @cwanja. This issue has been assigned to the doc author for review.


Make calendar period to get configurable & enable multiple sensors

Since I've got the component working and all is looking  good, I would like to do some feature requests:

Component only looks 24Hrs ahead, possibility to change this in the configuration.yaml
Maybe do something with start/end date/time?

Possibility to create multiple sensors, each for a (shared) calendar

That is certainly possible. I have put it on the to-do list

Notes to self for implementing this
The following changes will as a minimum be needed to enable multiple sensors

Setting the name of the sensor in the configuration.yaml.
Setting the name of the calendar to use and if not set use default calendar as now.

Regarding making the period configurable, this should be as easy as just changing the code from getting todays events to getting the next x hours events and then making the number of hours configurable via the configuration.yaml with a default value of 24.
It might also be nice to give the option of setting a number of hours back in time to include. I can see a couple of potential automation use cases using earlier events.

Is a datetime from and datetime to parameter more convenient ?
Say if I want to make a wake-me-up event, then I want to look only if there is an event in the morning, the next day...

Then you would have to change your configuration.yaml every day with a new date wouldn't you?
There is actually already a service you can call at office365calendar.get_calendar_events here you can specify at start and end datetime, this creates a new sensor with the events for this period.
You can also specify the calendar name in this service call and you should be able to access shared calendars this way. But that part is completely untested on my end for now

True.
I'll test the service call, see what this does.
Before this custom component I used Google Calendar, as embedded in HA.
For each calendar I had an entity defined.

Hello i have added these features in the latest version https://github.com/PTST/O365Calendar-HomeAssistant/releases/tag/v1.1


Improve test isolation

Perform setup/teardown in beforeEach/afterEach rather than in the describe callback
Use stubs rather than mutating shared values like config
Use fake timers rather than relying on timeouts to work around async delays
Style fixes

Fix remaining ESLint warnings in affected files
Continue to move towards async/await
Allow Chai assertion statements

Worth noting a couple side benefits:

Much faster full test runs! Especially in CI.
Much less logging noise because the stubs for those methods are actually working again.


Fix directory path in the README

Slight correction about paths is made so could you check it out?
On another note, this package depends on ocp-indent when testing. Don't you need to add it to depends or depopts list in opam file or somewhere?

Now checking Travis CI and the Python version of its image. 3.5+ is preferable if you choose one.

On another note, this package depends on ocp-indent when testing. Don't you need to add it to depends or depopts list in opam file or somewhere?

No. ocp-indent code-formats .ml and .mli files in this package. opam doesn't need to re-check the code format because the files have been already checked by CI.

Thank you @akabe for cheking and marging the PR!
About ocp-indent, when I first followed your Contribution instruction and commited my diff, consequently the hook activated and raised an error since I hadn't installed ocp-indent. It was mostly because I was an OCaml beginner and I wondered if the package should be required explicitly in somewhere like opam but if you don't think so, it's completely no problem! Thanks

Sorry, I should explain installation of ocp-indent in the contribution section. I will add it to the next patch. Thanks.


Importers for all resources provided

Currently there is now way to import resources already created in FireHydrant into Terraform state, but there should be! There's commonly already severities created as well as runbooks in an account that should be able to be mapped to a resource in Terraform.

does import now work?


update snapcast media player

Description:
Update the snapcast media player to support the latest version of Snapcast, 0.11.1, which contained a breaking API change. This component will no longer support versions lower than 0.11.1.
Other changes:

Asynchronous (faster!)
Fixes naming issue
Two classes of Snapcast media_players: Groups and Clients. Clients control individual client volume, groups control input source (stream). This is a breaking change to configurations that rely on entity ids, in some cases.
Adds two services, snapcast_snapshot and snapcast_restore, to save and restore state of client(s) and group(s). Useful for interrupting playing music with TTS.

I'd prefer some folks test this and confirm it works before merge.
Related issue (if applicable): https://github.com/home-assistant/home-assistant/issues/7054, https://github.com/home-assistant/home-assistant/issues/4533
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Example entry for configuration.yaml (if applicable):
media_player:
  - platform: snapcast
    host: 'localhost'

Checklist:
If the code communicates with devices, web services, or third-party tools:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.

I don't know why it's failed an import in travis.

There is no option to control sound by group, are you planning support for his in the future?

@FilipLigaarden I suppose it is possible. Group volume control is just setting the volume on the individual group members though. There isn't a Snapcast command to set a group volume.
@pvizeli Thanks for the feedback, will update. This is my first really async component.

Addressed review comments.

Had another person test this. Free to merge if review passes.
Still don't know why travis ci fails.

Nice work, however, here are two bugs.
#1: The play/pause button does nothing.
#2: When you change the clients names, they will not respond to changes in volume until you restart hass, however mute does work like normal.
Request: If possible, to list all clients within the group, with volume sliders when you open the group entity, like illustrated in pic 1.
I understand this second request might be a little overboard, but here it comes:

Nice work, here are some bugs and feedback.
1: The play/pause button does nothing, see request 2 for possible solution.
2: When you change the clients names from the Android app, they will not respond to changes in volume until you restart hass, however mute works like normal.
Future requests:
1: If possible, to list all clients within the group, with volume sliders when you open the group entity, like illustrated in the picture.
2: Integration of MPD as an option, i don't know if this is even possible, but would look very nice. Forgot to include the source button.
3: Discovery?
Paint design, but should illustrate what i have in mind.

The android app is a perfect example of how it should look like.

@FilipLigaarden Keep in mind that this PR is only for device support - how it looks in the front end is not covered. That would be a separate change. The play/pause button should not show, but it's a front end bug with the media player card, not with the snapcast component.
The name/volume change issue is a bug within the scope of this PR, and I will fix that one. Thanks for the report!

I still don't see any reason why the CI fails with bad imports.

The pypi package definitely includes those packages
python-snapcast has the right version in file and requirements
python-snapcast is not listed more than once in requirements
People have tried this PR and it works for them

I just tried it and I get a different entity_name for my group with every snapserver restart. Is there a possibility to make this stable to use the device in automations and groups?

@pvizeli is there a "Part 2" to your review?

I will do it :+1:

Will this fix be included in next release?

@pvizeli , but isn't the snapshot/restore function in this code very hass specific? It just saves the current state internal to hass and then set it from that. All the get/set state already comes from the lib. Just the handling of the stored data is in this component - which is hass specific.
I don't see how thee could be much functionality put into the lib without making the lib hass-specific (which is not the intent I think, as its a general api implementation for snapcast).

What is the status on this?

Hi All,
Many thanks for your efforts in making this work (I wish I could help, but unfortunately I am not any good at this). Do we have any idea when this will be implemented into HASS? Will it be part of the upcoming release(s) - i.e. is it worth waiting or shall we downgrade to a previous snapcast version?
Best,
Dimitris

Hello @happyleavesaoc,
When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).
The commits that are missing a linked GitHub account are the following:

ba5c46ff790b861259b0ce16f7561a6b2e9b762e - This commit has something that looks like an email address (happyleavesaoc@gmail.com). Maybe try linking that to GitHub?.

Unfortunately, we are unable to accept this pull request until this situation is corrected.
Here are your options:

If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.

If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.

If you only made a single commit you should be able to rungit commit --amend --author="Author Name<EMAIL_ADDRESS>
(substituting Author Name and<EMAIL_ADDRESS>for your actual information) to set the authorship information.
If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:

You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.

Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.

We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.
Thanks, I look forward to checking this PR again soon! :heart:

@pvizeli addressed your comments.
Still don't know why import is failing. Those modules are present.

I manually installed this, it works perfectly. Thanks @happyleavesaoc !
@balloob i would really love this to be part of the next release (and i'm sure i'm not alone), would you maybe help about that Travis CI issue ?

@happyleavesaoc it's a bug in pylint. Python 3 added support for empty folders but Python 2 doesn't support that. Fix it by adding an empty __init__.py file to the snapcast folder inside the package.

@balloob Thanks. Actually I had a __init__.py, but I didn't list that top-level directory in setup.py's packages. Well, good to know.
Anyway, checks pass no.w

We can merg it after travis is ok


Typo in "Available job-wide settings" section

When attempting to create a new dedup schedule, I used the command lifted directly from here.
New-DedupSchedule -Name "NightlyOptimization" -Type Optimization -DurationHours 11 -Memory 100 -Cores 100 -Priority High -Days @(1,2,3,4,5) -Start (Get-Date "2016-08-08 19:00:00")
This was rejected on Server 2022, with error
New-DedupSchedule : Cannot process argument transformation on parameter 'Priority'. Cannot convert value "Medium" to type "Microsoft.PowerShell.Cmdletization.GeneratedTypes.DedupSchedule.Priority". Error: "Unable to match the identifier name Medium to a valid enumerator name. Specify one of the following enumerator names and try again: Low, Normal, High"
So, the correct syntax for 'Priority' is Low, Normal, High. Whereas in this document, it shows Low, Medium, High. Please correct the typo.

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

ID: afbeabe4-15fa-65dd-9fe2-126ceadc96a1
Version Independent ID: 7a8534d6-56b3-ae36-463c-158ebb5e86bc
Content: Advanced Data Deduplication settings
Content Source: WindowsServerDocs/storage/data-deduplication/advanced-settings.md
Product: windows-server
Technology: storage
GitHub Login: @wmgries
Microsoft Alias: wgries

#assign:christking246

Thanks again for contacting Microsoft, we value your feedback.
A documentation change has been made updating the priority listing for Dedup and will be live after the next business day. We will now be closing this thread.
Thank you and have a most pleasant day.


CB-20442: Fixed SDX status checker job status update issues.

Jira: https://jira.cloudera.com/browse/CB-20442
Simply modified the logic within the status checker job to use the SDX cluster's account ID for the status updates.
Note that this is not an issue our team introduced especially not in any period in the last few months. Seems to me like either something in CB changed or we modified how we track these exceptions making them more present. Note also that the basic functionality of the status checker job is still correct even with this issue. This is just ensuring that we do not throw an exception every time the updates are called.
Testing:

Verify that issue exists without this fix by stopping a DL's nodes on the cloud provider so as to make the status checker job set it to unreachable
Verify that the issue no longer exists with this fix by doing the same as above and ensuring no exceptions are present

The change looks good.
How was this issue introduced? Depending on "ThreadBasedUserCrnProvider.getUserCrn()" to get user CRN is not new. Why are we observing this issue now?
Any thoughts?

Good question, so I do see that around 7 months ago this change was made. This would have introduced the issue for the status checker job.
As for why we did not see it until now, I believe it's because we weren't looking for it and everything was working correctly despite the errors thrown. I looked in DataDog as well and do not see an active monitor for it.
@sodre90 may have some other input on how this was discovered and whether it was occurring for the last 7 months or not.

AccountId can be acquired from the SdxClusterCrn.

I have addressed your first comment. As for this, the account ID is being sourced from the sdx cluster directly, do you think it'd be better to instead parse it from the CRN? I figured just using the field in the cluster object would suffice.

@lnardai I have updated the code to fit closer with what you've mentioned. Thank you for your comments.


[Helm Charts] Connectors MVP - without keycloak

Same as https://github.com/camunda/camunda-platform-helm/pull/501, but minimal version without security.
The following k8s configs work without helm charts:
apiVersion: apps/v1
kind: Deployment
metadata:
  name: connectors
spec:
  selector:
    matchLabels:
      app: connectors
  template:
    metadata:
      labels:
        app: connectors
    spec:
      containers:
      - name: connectors
        image: camunda/connectors-bundle:0.16.0
        imagePullPolicy: IfNotPresent
        resources:
          limits:
            memory: "1024Mi"
            cpu: "500m"
        ports:
        - containerPort: 8080
        env:
          - name: ZEEBE_CLIENT_BROKER_GATEWAY-ADDRESS
            value: <IP_ADDRESS>:26500
          - name: ZEEBE_CLIENT_SECURITY_PLAINTEXT
            value: "true"
          - name: CAMUNDA_CONNECTOR_POLLING_ENABLED
            value: "false"
          - name: CAMUNDA_CONNECTOR_WEBHOOK_ENABLED
            value: "false"
          - name: SPRING_MAIN_WEB-APPLICATION-TYPE
            value: none

apiVersion: v1
kind: Service
metadata:
  name: connectors-service
spec:
  type: ClusterIP
  selector:
    app: connectors
  ports:
  - port: 8088
    targetPort: 8080

Could you please check the failed pipelines?

Yep. At first, they were not looking like related but now I was able to confirm that all are related to my changes. Looking into it.

Thanks for your effort @igpetrov :100:

Hello team !
I have one question : Shouldn't the connectors be a subchart instead of being integrated in the templates ?

@vctrmn we are moving away from the sub-charts model because of its limitations.


Document local development best practices

We are lacking an easy quickstart for new devs to get the various pieces of the site up and running for local development iteration.  We should add detail to the README making it easy for new devs to join the effort.

I would like to pick this up


Does this theme style support Markdown TOC？

Hi, @Mivinci
Does this theme style support Markdown TOC ? Just like Yuque.
I do not see a post with  TOC support in example site.

@islongshiyu  Not yet. Cuz I wanted this theme to be simple. But I'll consider adding ToC on the top of each article 😊

Hi, @islongshiyu
ToC is now supported. Add a toc: true in the front-matter to optionally render a ToC for a post.


Solution does not build inside Visual Studio for Mac

Seems like transitive restore doesn't work with VS for Mac... the iOS/Android/macOS projects can't find Xamarin.Forms nuget package and won't build.
WORKAROUND: build from command line on macOS:
msbuild /t:restore
msbuild

Once built you can then open VS for Mac and run samples under debugger.  If you make changes just rebuild from command line.

Seems like full PackageReference support is coming in VS for Mac


Add version attribute

I chose to emit the version string into _version.d because those extensions are currently gitignore'd. I don't think this would cause any problem with the build, etc. but let me know if that's not the case.


Refactor names

inspired by #668

@Liubov-crypto please ensure that default name switching and initial names fetching works fine


Charge Voltage Limitation linear switch back on SOC

Is your feature request related to a problem? Please describe.
My 18 Cells are perfectly balanced that the voltage difference stays always under 0.01 V. (most often 0.001-0.007)
I use the linear CVL and the charging voltage is correctly changed to float voltage after they reached max voltage.
They stay in float voltage and dont switch back to max voltage as CELL_VOLTAGE_DIFF_TO_RESET_VOLTAGE_LIMIT is never reached.
Describe the solution you'd like
I would like to have the solution that in linear mode the switch back to max voltage also happens when the SOC_LEVEL_TO_RESET_VOLTAGE_LIMIT is reached
Describe alternatives you've considered
No response
Additional context
I use the Version 1.0.0-jkbms_ble (20230505)

Makes sense. It will be included in the next pre-release and release.


Explain why componentDidMount is a better place to make an ajax request

In the docs, in componentWillMount section section it says:

Avoid introducing any side-effects or subscriptions in this method

And in the componentDidMount section:

If you need to load data from a remote endpoint, this is a good place to instantiate the network request

Which for me is confusing because I won't like to wait for the component to be mounted to dispatch an ajax call to fulfill the component data dependencies. I would like to do it as soon as possible, like in the constructor, not even in componentWillMount.
Clearly you may have a reason why you say this in the docs, I might be not seeing the bigger picture. So it will be nice if you can explain a bit more in detail or point me in the direction of where I can find the reason.

I won't like to wait for the component to be mounted to dispatch an ajax call to fulfill the component data dependencies. I would like to do it as soon as possible, like in the constructor, not even in componentWillMount.

If it's an async request, it won't be fulfilled by the time the component mounts anyway, regardless of where you fire it. This is because JS is single threaded, and the network request can't "come back" and be handled while we are still rendering. So the difference between firing it earlier and later is often negligible.
You're right that it matters in some rare cases though and for those cases it might make sense to break the recommendation. But you should be extra cautious as state can update before mounting, and if your data depends on state, you might have to refetch in that case. In other words: when in doubt, do it in componentDidMount.
The specific recommendation to avoid side effects in the constructor and Will* lifecycles is related to the changes we are making to allow rendering to be asynchronous and interruptible (in part to support use cases like this better). We are still figuring out the exact semantics of how it should work, so at the moment our recommendations are more conservative. As we use async rendering more in production we will provide a more specific guidance as to where to fire the requests without sacrificing either efficiency or correctness. But for now providing a clear migration path to async rendering (and thus being more conservative in our recommendations) is more important.

I'll mark this issue as a "good first issue" in case anyone wants to take Dan's note about async and interruptions and add it to the docs.
Put another way, in the future (once the async API is stable and you're using it), it will be possible for lifecycle hooks like componentWillMount to be invoked more than once before a render- or to be invoked once and then never rendered- depending on whether higher priority work interrupts.
That's why it's important for side-effects (eg your network requests) to live in methods like componentDidMount, because they are guaranteed to only invoke once and only if the component has actually mounted. So you avoid firing network requests off needlessly, or perhaps logging events multiple times and corrupting your metrics, etc. Following these patterns now will make your eventual upgrade to async- (something we hope you'll want to do for performance reasons)- much easier.

It's important to not overload the docs with speculations about future behavior though. If explanation raises more questions than it answers I'd argue it would only make the docs more complex for the majority of readers.

I agree. But I also agree with OP that it's confusing and limiting for us to say "don't do this" without offering some hint at our rationale.
My elaboration above wasn't meant as a suggestion for what we should add to the docs, but rather to help whoever may work on adding the note to better understand why.

Thanks for the quick replies!
I agree with you of course. I only felt it was counter intuitive, and wanted to know the whys of the recommendation, that's all.
Perhaps in the future, when the API is stable, we can come up with a concise explanation for this recommendation.

Hello I'm a beginner to open source contributions. Have gone through the guidelines and was wondering if I should take up this issue?

This issue is all yours, @vishalvrv9! 😄
I've added an "in-progress" label so that others will know not to start work on the issue. If you change your mind about the issue, no worries! Just let me know so that I can remove the label and free it up for someone else to claim.
Cheers!

@gacosta89 @gaearon maybe I have misunderstood componentWillMount. Please correct me if I'm wrong.
The sole purpose of componentWillMount is for prefetching such as Ajax calls as long as the state is updated on componentWillReceiveProps. This is because React will queue state changes. On the other hand, setState should not be called on componentWillMount for the reasons mentioned above.

The sole purpose of componentWillMount is for prefetching such as Ajax calls

This is correct, @michaelgichia. Early prefetching is the canonical use for componentWillMount. It lets your app make a GET request a little bit earlier than waiting for mount.
It's best to stick with read-only (eg GET) requests though, for the reasons mentioned above regarding future async behavior. I like Dan's summary above: "When in doubt, do it in componentDidMount"

On the other hand, setState should not be called on componentWillMount

It is actually okay to set state from within componentWillMount. You initialize state in the constructor and this method is kind of an alternate constructor for components that were created via createClass. (See here for an explicit list of where it's okay to set state.)

@bvaughn thank you for taking your time to write a comprehensive explanation. I hope others will find this thread too for a better understanding of React Lifecycle and Setstate.

@vishalvrv9 hi vishal!  are you still working on this issue?
i don't see a in-progress label on this issue at the moment.
is this issue open again?  i would love to work on this!

Firstly, sorry for not keeping anyone posted.
@kevinkiklee Noticed there was no in-progress tag (as you mentioned) and hence didn't move forward with the work. I could happily finish this within the next 24hrs.

I've marked it in-progress then. 😄

** not clear. **
I get the things from the answers are :

constructor  ---- compentWillMount ---- [ Your request Data return] -----  render ---componentDidMount.
if this case your data will not be rendered.
I get the things from the answers are :

constructor  ---- compentWillMount -----  render  ---- [ Your request Data return] ---componentDidMount.
if this case your data will be rendered.

constructor  ---- compentWillMount -----  ren[ Your request Data return]der ---componentDidMount.
this case is impossible beacuse js is single threaded.

right? and why?


Azure VM Scale Set CustomScriptExtension Failing

I have followed the steps here and it did not create an initialized/formatted disc.  I opened an issue on stack overflow and no one else was able to get the instructions to work either: https://stackoverflow.com/questions/65005883/azure-vm-scale-set-customscriptextension-failing
Is it possible the document or API needs to be updated?
Thank you,
Brian

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

ID: 75079c9f-fff6-85f0-ede4-7f9c3e582c82
Version Independent ID: 4dba40e8-d5ea-4946-6123-2f22cc6326dc
Content: Azure Virtual Machine Scale Sets Attached Data Disks - Azure Virtual Machine Scale Sets
Content Source: articles/virtual-machine-scale-sets/virtual-machine-scale-sets-attached-disks.md
Service: virtual-machine-scale-sets
Sub-service: disks
GitHub Login: @ju-shim
Microsoft Alias: jushiman

Thanks for opening the bug, let me take a look.

The section of the doc with the command to execute is for a Service Fabric cluster.

"The rest of this article outlines specific use cases such as Service Fabric clusters that require data disks, or attaching existing data disks with content to a scale set."

Are you trying to attach an existing data disk with content to a scale set as looking at the stack overflow doc you provided it looks like your trying to attach a new, unformatted data disk without content which isn't supported for VMSS per this doc. Could you provide more information as to the nature of this doc bug?

Perhaps I confused myself.  I was trying to create a Service Fabric cluster
where the VMSS would create nodes with a formatted and attached data disk.
In experimenting, I moved away from a SF cluster deploy and moved to a pure
VMSS deploy to minimize the case of what I was trying to create.  It seems
in doing so I changed the scope of the problem and you are correct, it says
this will only work with Service Fabric.  Thank you for your time, back to
experimenting!
On Tue, Dec 1, 2020 at 4:49 PM Winston Howard<EMAIL_ADDRESS>wrote:

The section of the doc with the command to execute is for a Service Fabric
cluster.
"The rest of this article outlines specific use cases such as Service
Fabric clusters that require data disks, or attaching existing data disks
with content to a scale set."
Are you trying to attach an existing data disk with content to a scale set
as looking at the stack overflow doc you provided it looks like your trying
to attach a new, unformatted data disk without content which isn't
supported for VMSS per this doc. Could you provide more information as to
the nature of this doc bug?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/66961#issuecomment-736841997,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABOMGZXYW2UHUBI7FWSEYDDSSVQGHANCNFSM4UJLSXUQ
.

Sure, closing the issue then. Best of luck with your experimenting!


Want to implement react context api

Feature request:
Want to implement react context api @abdus

for what exactly?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Girl-Code-It/Opportunity-Calendar-Frontend/issues/188#issuecomment-813094347,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKG5GE24TEPCZFODR6HBQ53THDDHFANCNFSM42LOPHLA
.

@abhay27chauhan It would have been better if you would have given reference to the issue you are talking about. In fact, whenever you create an issue, give proper reasoning to what you wanna add and how will it benefit us.

I did not give a reason as you don't have either react context api or redux
in your app, and you are not going with redux as told by one of your team
mate so I thought that it is obvious that you would like to implement react
context api. So I opened the issue
On Thu, 8 Apr, 2021, 11:02 PM Vaishali, @.***> wrote:

@abhay27chauhan https://github.com/abhay27chauhan It would have been
better if you would have given reference to the issue you are talking
about. In fact, whenever you create an issue, give proper reasoning to what
you wanna add and how will it benefit us.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Girl-Code-It/Opportunity-Calendar-Frontend/issues/188#issuecomment-816008147,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKG5GEZEST26WYI5PYJEYCDTHXSC7ANCNFSM42LOPHLA
.

@vaishali614 is it ok ?

@vaishali614  ??


Credit the specific MIPS emulator linked to here

Really cool to find out my MIPS assembler & emulator are featured in your textbook. I thought a specific credit would be appropriate.

Hi Alan,
Thanks for your suggestion, I'm guessing somebody should be able to approve this soon. We are working on property crediting all the resources we use, and will also mention you on the page we have dedicated for that.
Your emulator has allowed many NZ high school students to actually play around with a low level language. For that we really thank you :D

Hi @alanhogan,
Thanks for your edit, we are very happy to credit you properly!
I should mention that in our long term plan is to use our own version of a MIPS emulator, as we can directly control it's reliability. The emulator you provide is great, however if the webpage disappears in a few years, there isn't much we can do (this happens constantly with the amount of links in our guide). So we are trying to create our own versions of all the 'interactives' in the CSFG. I did see you share the source code on your website, is this available under any open source license?

@Heidirose I’m gratified that something as simple as keeping my work online has been able to give so many students zero set-up, universally available way to play with MIPS!
@JackMorganNZ Thanks for bringing this up! I hate linkrot and will continue to do what I can, barring excessive obstacles, to keep my tools and really everything else I have shared, online. I’m sorry you have seen so many other resources disappear. And I totally, 100% support your effort to host your own “interactives” in order to ensure all the important linked resources you provide continue to be available.
To that end, I want to apply an open source license to my assembler & simulator.
How does CC BY-NC-SA 4.0 sound?

I threw the scripts up on GitHub an attached the aforementioned CC BY-NC-SA 4.0 license on them.
https://github.com/alanhogan/online-mips-assembler
https://github.com/alanhogan/miphps-mips-simulator
Think this will work for you? My understanding is that this is not a commercial endeavour and that you have no problem with attribution, so I think that license will work just fine.

Thanks @alanhogan, that's perfect! You're correct with saying this is a non-commercial endeavor, our project is under the same CC BY-NC-SA 4.0 license.
I've added the MIPS assembler to the guide on branch interactives/mips-assembler. Would you be able to check you're happy with how we have used it? I'm hosting the current version here for easier viewing.
We have added attribution within the footer of the interactive, and also in the README of the interactive folder and within the included-files document which is shown in the appendices online.

@JackMorganNZ Oops, somehow I didn’t see your comment until now. Email inbox fail :)
You moved fast! That’s great. Yeah, I’m very happy to see this. And your version looks a lot better than the awful styles I slapped on it so long ago, too.
You can always reach me at http://alanhogan.com/contact in the future.


doc: add document to explain how to run on GKE

Please answer these questions before submitting a pull request

Why submit this pull request?

[ ] Bugfix

[ ] New feature provided

[ ] Improve performance

[ ] Backport patches

Related issues

Bugfix

Description

How to fix?

New feature or improvement

Describe the details and related test reports.

Backport patches

Why need to backport?

Source branch

Related commits and pull requests

Target branch

@moonming @membphis @gxthrj Please take a look when you have time.

@moonming @membphis @gxthrj Please take a look when you have time.

Codecov Report

Merging #180 (afa649b) into master (f72d75d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #180   +/-   ##
=======================================
  Coverage   48.65%   48.65%
=======================================
  Files          30       30
  Lines        1482     1482
=======================================
  Hits          721      721
  Misses        675      675
  Partials       86       86

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f72d75d...afa649b. Read the comment docs.

Codecov Report

Merging #180 (afa649b) into master (f72d75d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #180   +/-   ##
=======================================
  Coverage   48.65%   48.65%
=======================================
  Files          30       30
  Lines        1482     1482
=======================================
  Hits          721      721
  Misses        675      675
  Partials       86       86

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f72d75d...afa649b. Read the comment docs.


Fishing Google Chrome extension

see the issue https://github.com/polkawallet-io/app/issues/98, reported by polkawallet user.

I lost 1 DOT that Polkadot forced me to leave on that fished account, is there a way to get it back somehow?

The same add-on is still in the Chrome Store and I fell into the same trap. I tried to enter polkadot js words and thought it was polkadot js plugin. There are some seed sales and vomit pre-sales that I participate in this wallet. These have not been credited to my account yet. If I open a new wallet, what will happen to the projects that are not transferred to my account? How come this extension is still in the Chrome Store?

Good question, and why polkadot-js is not replying ? I want my DOT back, but I also expect polkadot to take action not to let people like you get scam. 24 days and still no action as been taken

For those who want their 1 dot back after saving their found from this hacker : https://support.polkadot.network/support/solutions/articles/65000169248-error-balances-transferkeepalive-

There is absolutely nothing that "polkadot-js", aka me, can do here.
Don't expect miracles, I'm a single person - so what I did, hopefully alongside everybody else, was to report the extension, on Google. Apart from that, here we are dealing with a faceless store on the web, so reports is the only thing that can be done. At some point Google will take action.

After mailing support at polkadot.network, they were able to send me a fraction of dot so I got able to send my remaining DOT, now I got no lost, I recommend every person in my situation to do the same.
An action have been taken for the fishing extension and now polkadot is waiting for the removal of it.

This should be kept open for tracking until the extension is removed from chrome extension store.


Need this code with objective c support

Hello
I want this code with objective c if you possible else suggest me other library

You can use swift components from objective-c code, though this has not been tested for this project. See Apples Documentation on Mix and Match Interoperability.


V1.3b show upcoming friend events

Fixes #170

Codecov Report

Merging #185 (80b65c4) into master (e504244) will decrease coverage by 0.11%.
The diff coverage is 75.00%.

@@             Coverage Diff              @@
##             master     #185      +/-   ##
============================================
- Coverage     71.36%   71.24%   -0.12%
- Complexity      802      811       +9
============================================
  Files           117      120       +3
  Lines          2797     2838      +41
  Branches        424      424
============================================
+ Hits           1996     2022      +26
- Misses          623      634      +11
- Partials        178      182       +4

Impacted Files
Coverage Δ

...main/java/seedu/address/ui/ExpandedPersonCard.java
0.00% <0.00%> (ø)

...java/seedu/address/ui/ExpandedPersonListPanel.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/ui/MainWindow.java
0.00% <0.00%> (ø)

...address/model/event/EventDateIsAfterPredicate.java
63.63% <63.63%> (ø)

...ddress/model/event/EventDateIsBeforePredicate.java
63.63% <63.63%> (ø)

...ent/EventFriendNamesContainSubstringPredicate.java
63.63% <63.63%> (ø)

...eedu/address/logic/commands/ShowFriendCommand.java
78.78% <66.66%> (-1.22%)
:arrow_down:

...del/event/EventNameContainsSubstringPredicate.java
81.81% <81.81%> (ø)

...u/address/logic/parser/FindEventCommandParser.java
90.00% <90.90%> (-4.74%)
:arrow_down:

...seedu/address/logic/commands/FindEventCommand.java
93.33% <100.00%> (+3.33%)
:arrow_up:

... and 4 more

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


[hub] - Add forum model on the client side

It should be a singleton like user right now, and load whenever the user changes the forum he's on.

2 important files added:
/lib/forum-model/model.js: It's the client side model that is meant to be instantiated by any forum.

It has 2 methods that are important:

.fetch(): Returns a Promise, forcefully updates de model attributes with database data.
.load(): Returns a Promise, only makes a fetch() one time, unless .unloaded() is called

import Forum from '../forum-model/model'

let forum = new Forum('debate-zone')

forum.load()
  .then(() => {
    console.log('Correctly loaded from database!')
  })
  .catch(() => {
    console.log('There was a connection error, server error, or doesnt exists.')
  })

/lib/forum-model/user-forum.js: Extends model.js but always fetches the current loggedin user forum, and implements .exists() that returns a Boolean telling if the user has a forum.
import userForum from '../forum-model/user-forum'

if (userForum.exists()) console.log('User has a forum!')


Copy change: change word "Alarm" to Critical

Type of issue

[ ] Bug
[ ] New feature
[X] Improvement

Description
the red word below the number should say "Critical" instead of "Alarm". This is copy error on the mocks.

...

Duplicate issue: https://github.com/Azure/pcs-remote-monitoring-webui/issues/775


forced subtitle mkv flag are not preserved

Hi,
The Issue:
I want to preserve the mkv forced subtitle flags, but transcode-video removes them.
(I absolutely do not want to burn in subtitles, as all my mkvs have the forced subtitles flag properly set. Kodi automatically switches on the correct forced subtitles depending on the audio language at playback, exactly like a DVD/Bluray player. So burning them in is much less efficient as it doesn't support forced languages on the fly switching).
I primarily use transcode-video to only reencode the video and copy over all the audio and subtitles tracks.
How can I make it preserve all the mkv flags ? (fyi Megui correctly preserves the mkv forced subtitle flags when opening a source).
This is my command line:
transcode-video --crop detect --copy-audio all --add-subtitle all --no-auto-burn --quick "c:\movie.mkv
I have also tried to add --force-subtitle scan to this command line, but it doesn't change anything (the forced subtitle flag is still removed)
I see no --copy-subtitle all option in the --help. Would a --copy-subtitle all preserve the forced flags?
Question:
Does --force-subtitle scan do the same thing as makemkv?
As often the subtitles are not marked as forced inside the PGS, the optimal solution would be:

always preserved the original mkv forced flag (this is what --add-subtitle all should do) and
also scan the PGS subtitle for forced lines (so when running a batch we also automatically flag the subtitles in case the original had no forced flag but was containing a PGS with forced lines), this is what --force-subtitle scan does (?).

To summarize:

Could you please fix --copy-subtitle to preserve the original mkv forced flags
and if we add --force-subtitle scan do we have the best "catch all forced subtiles solution" ?

Many thanks.

And I forgot, when running an auto-batch, so that we don't find ourselves with 1 subtitles muxed several times in the mkv with the above "catch all forced subtiles solution":
3 - remove any double subtitle tracks (in case one subbtiltes apprears 2 times: once flagged as forced and once not flagged, this is what makemkv sometimes does)
Thanks a lot.

@Mangoes Thanks for the writing up this issue. I'll take a look at in a few days when I back at my Mac.

@Mangoes Sorry I took so long to look at your issue. I've been traveling a lot this summer and this is the first week I've been able to really focus on the project.
There is no -copy-subtitle option. It's --add-subtitle and I've been very clear in the past that its behavior is not to set attribute flags and that users must explicitly choose which subtitle to burn or force. That's why --burn-subtitle and --force-subtitle options exist. It's also why the scan argument is available for those latter two options.
So, I don't intend to change the semantics or behavior of --add-subtitle. Doing so might also cause problems for other users since there's no way to "un-force" a subtitle.
Anyway, using --force-subtitle scan with --add-subtitle all should get you the behavior you want. I just tried it myself and it found the subtitle with the forced flag in the input, added it to the output, and then correctly set the forced flag in the output. As a bonus, there's no need to use the no-auto-burn option when using that combination. Automatic subtitle burning is disabled in that case.
Regarding the scan implementation, that's internal to HandBrake itself. I don't know how it works or how similar it is to MakeMKV.  I then have to scan the output file looking for a subtitle with the default flag and set the forced flag in the "cleanup" portion of my code.
So, can you try --force-subtitle scan --add-subtitle all and see if that works for you? If it doesn't, I will consider adding something like a --auto-force option to do this.
Thanks.

@Mangoes Any update on trying --force-subtitle scan --add-subtitle all to see what happens?
Unless I hear from you soon I'll close this issue. Of course, you can still comment even if it's closed, and we can discuss re-opening it.
Thanks.

@Mangoes Since I haven't heard from you, I'm going to assume this is resolved and close the issue now. But, like I said, you can still comment and we can discuss re-opening it.


acsengine-features allows setting CUSTOM_HYPERKUBE_SPEC as a build param

cc: @dmitsh / @weinong
We need this for investigations and to setup jobs for pre-release builds of Kubernetes.
Please let me know thoughts, I know these are not right:
1. convention for naming build parameters?
2. does this need to be changed in other groovy scripts?

This change is

@colemickens,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

either update the existing jobs to add this parameter, or add a try-catch at the beginning of the pipeline to swallow exception.. If you want to do the former, let me know. wont block the PR. :)


Support for RDP links in Sunstone

Description
Windows VMs can benefit from RDP connections
Use case
Better UX than VNC for end users
Interface Changes
Current VNC button can be subsumed into a "Console" button that is really a "fancy" dropdown for:

VNC
RDP

(soon more to follow)
Additional Context
All Sunstone needs to do is opening a rdp:// link, pointing to the right NIC (more on this below). It is up to the browser and end user to have a correct configuration so a RDP client is launched.
Selecting the right IP can follow the next procedure:

if only one NIC, pick that
more than one NIC:

check for NIC with RDP=yes. This setting should be available on VM Template creation time (checkbox in the VM Template Network section that will add RDP=yes to the NIC). If more than one, pick the first one
if no NIC with RDP=yes, pick first one

Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

check -> https://github.com/citronneur/mstsc.js?files=1

PRs to merge:
• one: #4170
• docs: OpenNebula/docs/pull/927

It would be nice to implement SPICE as well https://github.com/OpenNebula/one/issues/1262


'Zero Deaths' Achievement is impossible after 500 IP purchase

The 'You start with 8th dimension and a Galaxy' 500 IP purchase makes it impossible to get the 'Zero Deaths' achievement.
While it is still possible to get it within a challenge, I don't believe the intent of this achievement is to get infinity with only dimensions 1-4.

That is the intent.


Calling PullImage before CreateContainer to pull images on pod VMs

The container runtime implementations such as containerd and cri-o do not call PullImage of kata CCv0 to pull images in pod VMs. So far, we need a custom version of containerd or kata shim to pull images in pod VMs.
With this patch, cloud-api-adaptor calls PullImage to pull an image in a pod VM, while processing a CreateContainer request.
I have tested this patch with both upstream and custom versions of containerd. In theory, this patch should also work with cri-o.
Fixes #88
A side effect of this patch is that pod definitions with imagePullPolicy: IfNotPresent now work with peer pod VMs.

#100

This is quite similar as what we did in MVP1 :-)


⚠ Bofrost.at has degraded performance

In 27a89e2, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1848 ms

Resolved: Bofrost.at performance has improved in 2182cb9 after 41 minutes.


Investigate public key diffs in System.Threading.Tasks.Extensions

Found in https://github.com/dotnet/source-build/pull/1144: Ref assembly versions we build of System.Threading.Tasks.Extensions public key does not match the official version.  This causes failures during the tarball build but not the production build.

cc @dseefeld


question

I would like to take the liberty of asking when your dataset will be released. I would like to conduct research based on this. Thank you for your help

Hi, the datasets are released now, sorry for the late response. Note that the weak-n-expert and half-expert datasets as well as the trifinger-cube-lift-sim-expert-* datasets contained some errors before May 15, 2023. So if you downloaded before that date, please delete the local files and download again.


Help to install

Hi
As stated in an other issue, I started with docker without much success and I moved to linux binary to test the home-gallery solution.
But when I try to start the server, it exists:
pascal@NewNas:~/Home-Gallery$ ./home-gallery-latest-linux-x64 Loaded gallery configuration from gallery.config.yml ✔ Gallery main menu · server Execute: DEBUG=server* /tmp/caxa/home-gallery/1.0.1/home-gallery/node/bin/node /tmp/caxa/home-gallery/1.0.1/home-gallery/cli.js server --storage /home/pascal/.cache/home-gallery/storage --database /home/pascal/.config/home-gallery/database.db --events /home/pascal/.config/home-gallery/events.db --port 1000 Have a good day...
Any hint?
Do I have to intsall any dependencies?
thanks

Seems it doesn't like 1000 as port, with 8080, it works better.

Port 1000 might not worked due the privilaged port (1-1024).
If you playing with docker, you can leave the port 3000 in the container and map the host port with -p parameter like -p 8080:3000.


Feat: IMDB scraping

Describe the feature
Hi @nikhil25803
I am a GSSoC '23 contributor, I would like to add an IMDB scraper which can search for a movie name and get a description, rating and actors.
Please assign me this issue.
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC 23 contributor
[X] I want to work on this issue

Go ahead @DyuthiVivek
Note

Create a separate module for this, as per the folder and project structure
Do not use the `selenium web driver as it is not compatible with all devices as well as cloud platforms.
Before making any changes, check if the module you want to add already exists or not. If yes, then add your functionality as a method only else make a separate module and class for it.

All the best 👨💻


Explicit behavior amount

Each consumer behavior as an amount.
Setting its value explicitly makes the code easier to understand.
Also updated dependencies to fix the Github warning.

When we're at it: is amount the correct term here?
Is a share? Is it a ratio? A percentage?

A better name for amount would be weight or share. But let's change that in another PR, the UI and maybe the benchmark script uses the current name.


On the fly texture packer

Hi, I'm wondering if there is some kind of "on the fly" texture packer that you can use inside the app itself.
For instance, imagine you have a game set up in medieval time, and you have knights of different kingdoms. You want to create, inside the app, armored knights that combine multiple kind of helmet,  armors, some kind of iron shoes and such (and add color to a few piece). The "armor mixes" would be random, and you'd then have to create textures of the knights in different positions, pack them together before using them. And this way have a unique look for random armies, but packed and efficient.
Is it possible with libgdx?

Whaou, and that's the PixmapPacker, http://libgdx.badlogicgames.com/nightlies/docs/api/com/badlogic/gdx/graphics/g2d/PixmapPacker.html