[BUG]: the nasName parameter in the powerflex secret is now mandatory

Bug Description
Despite what is written here  the nasName.
The driver loops on the log below when that value is undefined and then crashes.
This impacts existing customers who upgraded from the previous version where we didn't have NAS support.
Logs
time="2024-01-15T14:43:16Z" level=info msg="Probing all arrays. Number of arrays: 1"
time="2024-01-15T14:43:16Z" level=info msg="default array is set to array ID: ca27126f4274560f"
time="2024-01-15T14:43:16Z" level=info msg="ca27126f4274560f is the default array, skipping VolumePrefixToSystems map update. \n"
time="2024-01-15T14:43:16Z" level=info msg="array ca27126f4274560f probed successfully"
time="2024-01-15T14:43:16Z" level=info msg="configured ca27126f4274560f" allSystemNames= endpoint="https://knl3013.krj.gie" isDefault=true nasName=0xc0007fa630 password="********" skipCertificateValidation=true systemID=ca27126f4274560f user=admin
time="2024-01-15T14:43:16Z" level=info msg="/csi.v1.Node/NodeGetInfo: REP 0002: nasName value not found in secret, it is mandatory parameter for NFS volume operations, if not specified, provide the default value as 'none'"
time="2024-01-15T14:43:17Z" level=info msg="/csi.v1.Identity/GetPluginInfo: REQ 0003: XXX_NoUnkeyedLiteral={}, XXX_sizecache=0"
time="2024-01-15T14:43:17Z" level=info msg="/csi.v1.Identity/GetPluginInfo: REP 0003: Name=csi-vxflexos.dellemc.com, VendorVersion=2.8.0+dirty, Manifest=map[commit:4a8a0ab90c4d56ca0ed00a8dd0aabdd7b526423c formed:Wed, 20 Sep 2023 06:15:43 UTC semver:2.8.0+dirty url:http://github.com/dell/csi-vxflexos], XXX_NoUnkeyedLiteral={}, XXX_sizecache=0"
time="2024-01-15T14:43:18Z" level=info msg="/csi.v1.Node/NodeGetInfo: REQ 0004: XXX_NoUnkeyedLiteral={}, XXX_sizecache=0"
Screenshots
No response
Additional Environment Information
No response
Steps to Reproduce
Install the driver and don't set a nasName (just like the second example from the sample secret).
Expected Behavior
If no value is set by the user in the secret, default to none without crashing
CSM Driver(s)
CSI Driver for PowerFlex v2.8
Installation Type
CSM Operator 1.8
Container Storage Modules Enabled
No response
Container Orchestrator
OCP 4.13
Operating System
CoreOS

link:20340

Hi @coulof , I believe array configured in the secret.yaml are >=v4.0 and as per the code I can see that this is how it was designed from day 1, to decide and add the required nfs topology on csi-node for the array that support NFS i.e. >=4.0.
If nasName will not be present then do you want us to add nfs topology or not?
If not then I can go ahead and can change this logic but my understanding is that NFS should be enabled by default and this label/topology should get added over all the csi-nodes and adding them without having a nasName in the secret doesn't make sense. I would love to hear and understand your approach and use case how you wanted it to work and then we can discuss and finalize the new approach if needed.
Currently we will add the topology on the basis of nasName: https://github.com/dell/csi-powerflex/blob/d50d49eb865444fbb2b639511f6dde1b1ab49ac2/service/node.go#L753
https://github.com/dell/csi-powerflex/blob/d50d49eb865444fbb2b639511f6dde1b1ab49ac2/service/service.go#L510

@coulof : Thoughts on above suggestion please

@adarsh-dell, I don't want to change the topology logic.
The request is to make nasName not mandatory in the configuration and, if not defined, fall back to none.
The reasons are :

NAS is not available for older PowerFlex versions we support (3.6)
In case of a driver upgrade, former configuration did not have nasName and after upgrade it will crash because this parameter is missing (cf. logs above)
Our own sample (2nd one) is missing that tag

Please tell me if I'm wrong and if that parameter isn't mandatory.

Hi @coulof , Let me work on this and get back to you ASAP with some data and conclusion.
Thanks

@coulof So customer was using 4.0 array with v2.7.0 of driver?

Hello @coulof ,
We've updated the check logic, and you can find this in CSM 1.10.
Closing this issue. Feel free to reopen if you have any further questions.
Best regards,
Adarsh

Docs need to be updated as it still states this is optional or required:false:
https://dell.github.io/csm-docs/docs/deployment/helm/drivers/installation/powerflex/

Hi @mlitka-cs , Can you please explain that what is confusing here?
As part of this github issue, we have made this field as an optional field so this is not a mandatory one any more.
User can install the driver even without configuring this value in secret.yaml, doesn't matter what is the version of backend storage array i.e. version that support NFS >=4.x.


fix: unmarshal number leads to int overflow

Use int64 type for disk size.
Resolves https://github.com/maas/terraform-provider-maas/issues/116
When compiled on a 32-bit platform int will be int32 and will lead to an overflow and JSON unmarshal error:
type Foo struct {
	Size int32
}

func main() {
	data := []byte(`{"Size":<PHONE_NUMBER>76}`)
	foo := Foo{}
	err := json.Unmarshal(data, &foo)
	if err != nil {
		fmt.Println(err)
	}
	fmt.Println(foo.Size)
}

Changes look good. Since you opened this one, what about memory (int) and storage, which is float64?!?
Same for VMHostResource

Well, my intent was to fix one particular issue and not all the type issues in the codebase, but if we want to address them all at once, I am fine with it 🙂

Thank you very much for taking care of all the potential overflows. LGTM :beers:


Create Using_Git_Credentials_from_Codebase_Connector_in_CI_Pipelines_…

…Run_Step.md
KB for Using Git Credentials from Codebase Connector in CI Pipeline's Run Step

[ x] Tested Locally

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


Traceable user actions for Space/ Area /WI's

Scenario:

When user deletes a Space / Area / WI .
The information should be traceable . In terms of Who deleted what or Who moved what / Edit/ Updates .

It would be easy for End user to find out who changed what .
In order to track an incident by which space got removed from the openshift.io

@catrobson @michaelvirgil @nimishamukherjee  any suggestions !

Completely agree, but we haven't built in audit logging yet and history which would track this.  Will be a feature we'll want to add!

@catrobson sure !


Upgrades

https://hibernate.atlassian.net/browse/HHH-10948
https://hibernate.atlassian.net/browse/HHH-10949

Applied upstream.


SAM-1074 Adding Delete test submission attempt feature for samigo, we…

… used this feature at Texas State Univ  from 2006 till now for sakai10.4
Tested over sakai's trunk, works well. For history of this feature merge request and also related feature demo video link, please see SAM-1074.

Can you amend the last commit to prefix it with SAM-1074 please?

Code comments provided in-line

This feature should have a property to control whether it can be turned on, and should be off by default.

This jira has merge conflict and without it, the feature on SAM-2587 doesn't work and in turn https://jira.sakaiproject.org/browse/SAM-2712 results.
Are @yuanhuaqu able to resolve the conflicts here so this can be merged? The property is probably a good idea but would need to involve both this workflow and another and I think should be a separate issue.

This looks good, can you run a "git rebase master" to clean up all the commits on this?

I did a merge with master on Mar 22 and resolved the conflicts.  I tried to do "git rebase master" , it somehow didn't pull all the commit on this branch and allow me to squash.  I guess, having a merge in the middle of the process won't allow me to rebase? Any guide I can follow for this case?

Hi @yuanhuaqu
Having a merge in there does complicate things a little..
Basically you need to get rid of the merge, you can do this a few ways perform a rebase and drop the commit with the merge.You can also squash your commits in the same rebase.
So you need to figure out how many commits to include in the rebase, in the example below I use 5 but you should adjust according to the number of commits you have on this branch. (Remember the one of those commits is the merge)
git rebase HEAD~5
Select which commits to squash and select the merge commit to drop.
Once this is complete you will then just have 1 commit and the merge will be gone.

At this point you should have just 1 commit being the last one, now just need to update this PR by force pushing your changes.
Hope this helps!
BTW there are others to do this like performing a SOFT reset on your branch but the way I described above would be the most direct.

It took me a while figuring out the complexity caused by using merge instead of rebase for updating  my feature branch with master, resolve conflicts and eventually squash all the commits (8) into a cleaner one.
@ern
Thanks  for the guide.  It helped me a great deal!!!!    May I suggest you to put this guide in somewhere like Git+Setup ?  And surely, case like mine with this branch which almost stretch out about a year,   to keep feature branch updated before it finally get into the master base , doing a   git rebase master will be much simpler than git merge master (which I learned it the hard way :=))

I have some internal documentation explaining most if not all of this, which I plan to move into the Sakai Confluence page you mentioned in the near future.

Thanks all for following up on this, I'll merge and test this after Travis passes.

Thanks.


ASP.NET Core Example does not work.

The ASP.NET core example will throw an exception in ASP.NET Core 2.1 with EF Core 2.1. Which will throw the System.InvalidOperationException.
With the message:
'No database provider has been configured for this DbContext. A provider can be configured by overriding the DbContext.OnConfiguring method or by using AddDbContext on the application service provider. If AddDbContext is used, then also ensure that your DbContext type accepts a DbContextOptions<TContext> object in its constructor and passes it to the base constructor for DbContext.'

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

ID: de9db02d-7310-1141-6aeb-539c02326a36
Version Independent ID: 90062036-aa01-3f73-dac9-b4a092245721
Content: Connection Strings - EF Core
Content Source: entity-framework/core/miscellaneous/connection-strings.md
Product: entity-framework
GitHub Login: @rowanmiller
Microsoft Alias: divega

It looks like I was just missing the constructor within a controller.
If you are going to migrate the default generated connection string don't forget to add to each controller
public class SomeController : Controller
{
   // This is needed
    private readonly YourContext _context;

    public SomeController(YourContext context)
    {
         _context = context;
     }
    // Routing and Controller logic...
}

Why isn't this code included in the example if it is needed?


Introduce end to end overlay integration test

This PR introduces end to end overlay integration tests. To make it work the following commits were
made:

Add necessary bats testing code and functions

Add sandbox ID to the service ls output so that it can be used to setup container

The test found an important /etc/hosts bug which was fixed
Signed-off-by: Jana Radhakrishnan<EMAIL_ADDRESS>

:+1: LGTM


Testing, please ignore. (uztwiq)

This is a bug bounty test.. Please DO NOT APPROVE THIS! (uztwiq)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.uztwiq wteue seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


ETag and dynamic response headers

Is there any way to dynamically set response headers? E.g. generating ETag based on response body for cache control.

Yep. You can use callback(null, body, headers) to set dynamic headers. They'll overwrite http: headers in function.json as well.


Python index update

Docs Build status updates of commit 6e7db93:
:clock10: Full build: the average full build time is 130 min(s) 33 sec(s), this is based on the last 258 build(s) for this repository.

Docs Build status updates of commit 6e7db93:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-services/storage-blob-readme.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/storage-file-share-readme.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/storage-index.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/storage-queue-readme.md
:warning:Warning
View (azure-python)
Details

docs-ref-autogen/azure-storage-file/azure.storage.file.sharedaccesssignature.FileSharedAccessSignature.yml
:warning:Warning
View (azure-python)
Details

docs-ref-services/storage-blob-readme.md

[Warning] Both ms.prod and ms.service can't be specified. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Invalid value for ms.technology: 'azure' is not valid with ms.prod value 'azure'.
Line 60: [Warning] Invalid file link:(~/docs-ref-services/configure-local-development-environment.md).

docs-ref-services/storage-file-share-readme.md

[Warning] Both ms.prod and ms.service can't be specified. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Invalid value for ms.technology: 'azure' is not valid with ms.prod value 'azure'.
Line 57: [Warning] Invalid file link:(~/docs-ref-services/configure-local-development-environment.md).
Line 191: [Warning] Link 'http://aka.ms/azsdk-python-storage-fileshare-sharefileclient' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

docs-ref-services/storage-index.md

[Warning] Both ms.prod and ms.service can't be specified. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Invalid value for ms.technology: 'azure' is not valid with ms.prod value 'azure'.
Line 24: [Warning] Invalid file link:(~/docs-ref-services/storage-blob-readme).
Line 25: [Warning] Invalid file link:(~/docs-ref-services/storage-queue-readme).
Line 26: [Warning] Invalid file link:(~/docs-ref-services/storage-file-share-readme).
Line 27: [Warning] Invalid file link:(~/docs-ref-services/storage-file-datalake-readme).
Line 33: [Warning] Invalid file link:(~/docs-ref-services/azure-storage-blob/?view=azure-python-previous&preserve-view=true).
Line 34: [Warning] Invalid file link:(~/docs-ref-services/azure-storage-queue/?view=azure-python-previous&preserve-view=true).
Line 35: [Warning] Invalid file link:(~/docs-ref-services/azure-storage-file/?view=azure-python-previous&preserve-view=true).
Line 41: [Warning] Invalid file link:(~/docs-ref-services/storage/management).

docs-ref-services/storage-queue-readme.md

[Warning] Both ms.prod and ms.service can't be specified. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Invalid value for ms.technology: 'azure' is not valid with ms.prod value 'azure'.

docs-ref-autogen/azure-storage-file/azure.storage.file.sharedaccesssignature.FileSharedAccessSignature.yml

[Warning] 1 invalid cross reference(s) "<xref:azure.storage.common.models.Protocol>".

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 86feabb:
:clock10: Full build: the average full build time is 130 min(s) 35 sec(s), this is based on the last 260 build(s) for this repository.

Docs Build status updates of commit 86feabb:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-services/storage-blob-readme.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/storage-file-share-readme.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/storage-index.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/storage-queue-readme.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/storage-blob-readme.md

[Warning] Both ms.prod and ms.service can't be specified. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Invalid value for ms.technology: 'azure' is not valid with ms.prod value 'azure'.
Line 60: [Warning] Link 'https://docs.microsoft.com/en-us/azure/storage/common/storage-auth?toc=/azure/storage/blobs/toc.json' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

docs-ref-services/storage-file-share-readme.md

[Warning] Both ms.prod and ms.service can't be specified. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Invalid value for ms.technology: 'azure' is not valid with ms.prod value 'azure'.
Line 57: [Warning] Link 'https://docs.microsoft.com/en-us/azure/storage/common/storage-auth' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 191: [Warning] Link 'http://aka.ms/azsdk-python-storage-fileshare-sharefileclient' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

docs-ref-services/storage-index.md

[Warning] Both ms.prod and ms.service can't be specified. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Invalid value for ms.technology: 'azure' is not valid with ms.prod value 'azure'.
Line 24: [Warning] Invalid file link:(~/docs-ref-services/storage-blob-readme).
Line 25: [Warning] Invalid file link:(~/docs-ref-services/storage-queue-readme).
Line 26: [Warning] Invalid file link:(~/docs-ref-services/storage-file-share-readme).
Line 27: [Warning] Invalid file link:(~/docs-ref-services/storage-file-datalake-readme).
Line 41: [Warning] Invalid file link:(~/docs-ref-services/storage/management).

docs-ref-services/storage-queue-readme.md

[Warning] Both ms.prod and ms.service can't be specified. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Invalid value for ms.technology: 'azure' is not valid with ms.prod value 'azure'.
Line 58: [Warning] Link 'https://docs.microsoft.com/en-us/azure/storage/common/storage-auth?toc=/azure/storage/queues/toc.json' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


FB11020478 - Xcode 14 incremental builds are all serial

FB11020478 - Xcode 14 incremental builds are all serial(expecting parallel wherever applicable)
We have enclosed the Xcode project("SerialReproducer.zip") and a video("Xcode14-repro.mov") demonstrating the issue in this ticket. (Repro1 as well as Repro 2).
Attachments:

Xcode14-repro.mov
SerialReproducer.zip

Setup:
The Xcode project was created from the latest Xcode Version 14.0.
In the reproducer, there are 5 libraries - LibA, LibB, LibC, LibD, LibE.
Scenario:

LibA, LibB, LibC, LibD → all depend on LibE.
This means if there are changes in LibE, it should trigger a recompilation of files in LibA, LibB, LibC, LibD targets.
Since LibA, LibB, LibC, LibD targets are disjoint from each other, they should compile in parallel.

Repro1: Repro to get all serial incremental builds:

Select the scheme: "All".
Do a clean build. Notice LibA-LibD targets are compiled in parallel.
Now, make any changes in "LibE.swift". It can be adding a new class or struct, any meaningful change inside Xcode.
Build the Scheme "All".
Notice that targets: LibA, LibB, LibC, LibD follow a serial compilation sequence. Ideally, LibA-LibD should compile in parallel in the same way as they were compiled in the Clean Build case.
Make any change in LibE.swift and you will always see serial incremental builds for all successive changes/invocations.

But this is not always the case. The new build system in Xcode 14 does give parallel builds under a very special edge-case.
Repro2: Repro to get parallel builds:

Follow the steps in "Repro1" to setup the initial state.
Now make a change in LibA.swift, LibB.swift, LibC.swift, LibD.swift, LibE.swift.(it can be commenting out code, adding a new class etc) Notice: we have made changes to all the files that are a part of the compilation sequence.
Now build the scheme: "All".
Notice that the parallel incremental builds are back. We can see from the Xcode's assistant build timeline that LibA, LibB, LibC, LibD are being compiled in parallel.
Now, make any change just in "LibE.swift". It can be adding a new class, anything.
Build the scheme and notice that LibA-LibD are compiled in parallel.
We now get parallel builds for all the successive changes in LibE.swift.
This initially in Repro 1 was only giving serial builds for the exact same change. Maybe there is a state that is missing in the initial incremental build and that's why it's all serial.

For any medium to large projects, not getting parallel incremental builds brings a significant regression that will be affecting the developer experience. Can the fix be prioritized and are there any workarounds that we can explore till the fix lands in an Xcode 14 release?

cc: @aciidb0mb3r

Hey @erikolofsson, I see that you have a PR that talks about Parallel Incremental Builds (https://github.com/apple/swift-llbuild/pull/832). Can you confirm if it's related to the above issue?

Yes, I believe that it is related to the above.

Above PR was merged.

Should this be reopened @dmbryson since the PR was reverted and this issue continues in Xcode 14.3.1?

@dmbryson any updates/workarounds related to this issue?


#118 Quiz App

I propose changes to https://zerooctave.github.io/ZeroOctave-Javascript-Projects/Public/Quiz_app.html
It's UI, The result generated seems quite to be inappropriate, I would like to contribute for the same!

Go Ahead

I've commited...one pr gave me the following error:" resource-not-accessible-by-integration"...so i closed and reopened...kindly check!


⚠ ukray.serverssh.net has degraded performance

In c511bd3, ukray.serverssh.net (http://ukray.serverssh.net/) experienced degraded performance:

HTTP code: 200
Response time: 16027 ms

Resolved: ukray.serverssh.net performance has improved in 0e095b8.


Narrower asserts in NGInlineNode::ShapeTextIncludingFirstLine

For #RUN-1261 (https://linear.app/replay/issue/RUN-1261/add-counter-to-nginlinenode-and-assert-in-shapetextincludingfirstline)

Fixed up the assertions here to get at the control flow path that leads into the Shape call.

Fixed up the assertions here to get at the control flow path that leads into the Shape call.

We've added asserts in the control flow leading up to this, so that should already be the case, but I'll be explicit and add this too.


Integrate Spotless to keep code clean

integrate https://github.com/diffplug/spotless in the same manner as google:
See https://github.com/google/android-fhir/blob/openmrs/buildSrc/src/main/kotlin/SpotlessConfig.kt
The license used by the project:
https://github.com/icrc/openmrs-android-fhir/blob/main/license-header.txt

sure :)


DCAL_Land_Change analysis for Simiyu (Tanzania) times out

DCAL_Land_Change analysis for Simiyu (Tanzania) times out see notebook here https://gist.github.com/mubea/b4d7016b7e7cf25b1b4921dc144c5b36 and screenshot
This could use dask
Please review @caitlinadams @andrewdhicks @jcrattz

All of the DCAL notebooks will not run an analysis for Simiyu (Tanzania) whose extents are latitude = (- 2.18297, -4.08798) and
longitude = (33.36163, 35.20679)


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 2648 ms

Resolved: Bofrost.at performance has improved in 1608814 after 20 minutes.


Implemented SA1513 (incl. codefix and tests)

Implementation for #114

I made a few changes during the merge commit:

Renamed GetTransformedDocument → GetTransformedDocumentAsync
Added the <remarks> section to the code fix provider documentation
Made some whitespace alterations (in particular, I don't indent case labels relative to the switch statement)

I'll file a bug for the remaining big issue I noticed.


Add mammoth submodule to dev tools

I created this fork of mammoth.js which I will add some instructions on how to use as a future tool to convert our tutorials to html.

The repo is now up to date with the latest and documentation has been added on how to convert documents:
https://github.com/ProteoWizard/DocumentConverter


Installing this package in ios react native having issue

Hi @TuyaRonbin ,
I hope you're doing good,
right now we are facing issue while building the ios App in react native that app build failed,
the issue occurs after installing tuya integration,
the issue is showing in xcode,

Linker command failed with exit code 1 (use -v to see invocation)
can you please help me, I shall be thankful.
Best Regards

[!] Unable to read the license file LICENSE for the spec TYMbedtls (2.25.2)
[!] Unable to read the license file LICENSE for the spec TuyaDefaultPanelUIKit (0.1.3)
[!] Unable to read the license file LICENSE for the spec TuyaSmartDefaultPanelKit (2.0.4)
[!] Unable to read the license file LICENSE for the spec TuyaSmartMbedTLS (3.33.3)
[!] Unable to read the license file LICENSE for the spec TuyaSmartNetworkKit (3.34.5)
[!] Unable to read the license file LICENSE for the spec TuyaSmartShareKit (1.3.2)
[!] Unable to read the license file LICENSE for the spec TYMbedtls (2.25.2)
[!] Unable to read the license file LICENSE for the spec TuyaDefaultPanelUIKit (0.1.3)
[!] Unable to read the license file LICENSE for the spec TuyaSmartDefaultPanelKit (2.0.4)
[!] Unable to read the license file LICENSE for the spec TuyaSmartMbedTLS (3.33.3)
[!] Unable to read the license file LICENSE for the spec TuyaSmartNetworkKit (3.34.5)
[!] Unable to read the license file LICENSE for the spec TuyaSmartShareKit (1.3.2)
getting these warning while installing a pods

I have facing same issue

same issue occurred when run on IOS
please help

Any updates?


⚠ Bofrost.si has degraded performance

In ee8da93, Bofrost.si (https://www.bofrost.si) experienced degraded performance:

HTTP code: 200
Response time: 2752 ms

Resolved: Bofrost.si performance has improved in c7bbb22 after 7 minutes.


Update front facing videos

Proposed changes
Precisely what the title says. This patch updates both the repository README and the documentation index page to show a slightly more enticing video of Beluga in action.
Type of change

[ ] 🐛 Bugfix (change which fixes an issue)
[ ] 🚀 Feature (change which adds functionality)
[x] 📚 Documentation (change which fixes or extends documentation)

Checklist

[ ] Lint and unit tests (if any) pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)
[x] All commits have been signed for DCO

Skipping CI as this does not affect code.


[Bug] automaticLayout doesnt shrink to container within flex layout

Reproducible in vscode.dev or in VS Code Desktop?

[X] Not reproducible in vscode.dev or VS Code Desktop

Reproducible in the monaco editor playground?

[ ] Not reproducible in the monaco editor playground

Monaco Editor Playground Code
monaco.editor.create(document.getElementById('container'), {
  value: "function hello() {\n\talert('Hello world!');\n}",
  language: 'javascript',
  automaticLayout: true,
});

.root {
    display: flex;
    align-items: stretch;
    height: 100%;
}
.sidebar {
    width: 150px;
}
#container {
    flex: 1;
}

some sidebar

Reproduction Steps
expand the width of your viewport and see the editor grow as expected.
now shrink the viewport width
Actual (Problematic) Behavior
The editor is not shrinking to fit the width of the container even though it is properly expanding.
Expected Behavior
It should shrink as the container shrinks
Additional Context
I have only seen this problem when the editor is a part of a flex or grid layout.  This is not a problem if the width is specified as a percent of its parent rather than using flex, but there are cases where flex or grid would be the best way of laying this out.

monaco-editor just uses ResizeObserver, so there is nothing monaco-editor can do...
But I found a solution in CSS Grid.
minmax(0px, auto) is the magic, only auto does not solve the problem.
monaco.editor.create(document.getElementById('container'), {
  value: "function hello() {\n\talert('Hello world!');\n}",
  language: 'javascript',
  automaticLayout: true,
});

.root {
    display: grid;
    grid-template-columns: 150px minmax(0px, auto);
    height: 100%;
}

some sidebar

Oh excellent, thanks for taking the time to show me @tamayika! 🙏

I think another option you could try is (with flexbox):
#container {
    flex: 1;
    min-width: 0;
}

Nice, indeed that does the trick as well, thanks!


Remove Configuration system

Because you should be able to achieve everything you want by pretransforming the expression.

@Pangoraw that should be the last breaking change for 1.0!


Add example with molecule on hover

Something like: https://github.com/wjm41/molplotly
We need to generate a scatter plot containing some smiles as properties that could be rendered on the fly by openchemlib.
Ideally a prediction model. Like comparing boiling predicted versus experimental.

can i work on this?


[Don't merge] Test ESLint and Flow errors

cc @bestander

So seems the bots work @bestander !

@satya164, indeed, it took a couple of hours after the commit.
Could be because of the queue in Travis builds.
I'll close the PR unless you have any more concerns

@bestander would be awesome for this to take a couple of minutes instead of hours. What could we do to achieve that? I'm curious about how much resources Travis provides for OSS projects. Looks like it's free, but does the number of workers scale as the project becomes more popular?

@martinbigio this is being discussed internally https://www.facebook.com/groups/osssupport/permalink/1013475482034400/
A few notes that are not a secret afaik.

FB uses Travis at capacity, and FB pays for them. There will be some more negotiation about that.

Travis limits their capacity per company travis-ci.org/facebook, the more projects we have on https://github.com/facebook using travis the more they will interfere with each other

Some projects abuse the number of concurrent builds. Flow uses 6 VMs for every PR and branch build, React - 4, RN used 5 and I reduced it to 3. We could reduce the number of VMs on all projects (considering that build/test time takes less than VM startup and environment setup) and could reduce the queue size for some time but not in a long term perspective

CircleCI is a good alternative, we could convince more projects to switch from Travis. I suppose the longer Travis queues are the more will switch. Though switching all projects to Circle will probably make Circle slow :) And also Circle does not provide IOS environment openly.

Considering that Circle is faster starting up we could move the eslint-bot command to Circle and execute it first. I'll keep an eye on that option in the next few weeks depending how the Travis thing gets resolved


绘制的line弧度弯到了负值区域

请确保使用了最新的代码版本

已使用了最新的代码版本，确认还存在

@fhqrnr  贴一下你的配置 主要是数据

var cacheData = {"hour":["00:00","01:00","02:00","03:00","04:00","05:00","06:00","07:00","08:00","09:00","10:00","11:00","12:00","13:00","14:00","15:00","16:00","17:00","18:00","19:00","20:00","21:00"],"finished":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,88,151,134,159,50,0,0,0],"finishedTotal":582,"receive":[131,3,1,0,0,0,0,3,7,28,46,58,36,48,43,53,60,51,15,0,0,0],"receivedTotal":583}
lineChart = new wxCharts({
canvasId: 'lineCanvas',
type: 'line',
categories: cacheData.hour,
animation: true,
background: '#f5f5f5',
series: [{
name: '接收量',
data: cacheData.receive,
}, {
name: '完成量',
data: cacheData.finished,
}],
xAxis: {
disableGrid: true,
gridColor:'#E9E9E9',
},
yAxis: {
gridColor:'#E9E9E9',
min: 0
},
width: windowWidth,
height: 300,
dataLabel: false,
dataPointShape: true,
extra: {lineStyle: 'curve'}
})

同问，一样出现了这个问题


The API operation 'Batch' requires the property 'body' to be of type 'String' but is of type 'Object'.'

I followed the tutorial step by step and got the following error:
The API operation 'Batch' requires the property 'body' to be of type 'String' but is of type 'Object'.'
I tried this in 2 tenants and got the same result. I am using Global Admin account on both tenants.

Hi @EValliarampath I'm sorry you're having trouble. We only just recently updated this tutorial, but the changes haven't been published yet to docs.microsoft.com. Can you tell me if you were following the steps at https://docs.microsoft.com/en-us/graph/tutorials/flow or the steps in the Markdown files in this repository?
The swagger file defines body as an object so I suspect that's where the problem lies. If you edit your custom connect, on the Definition tab there's a toggle for Swagger Editor. If you turn that on, can you cut and paste the Swagger definition and share here?


Friday Night Funkin' EYY's, but GF cheers too

Title.
https://user-images.githubusercontent.com/44783518/113492493-13a91300-94ae-11eb-8b82-a3264bef7dae.mp4
Also, won't stop GF from looking like a diva when the trains passes too.
 Seriously, I can get why this isn't merged into the main game.

What is there for me to clean up? The code works like it should and is commented too.
Switch over elseif statements, more comments..? I need something to work with.

thats better ig


Add pre-built binaries to releases

Hey there,
it would be great if we had pre-baked binaries e.g. for use on CoreOS in the releases. This greatly facilitates deployment as you don't have to build the project yourself.

On coreos? You'll prolly want to use docker there?
Right now, releasing is setting a tag in git, not looking forward to do more than that.

Yeah - missed that. I wanted to use skyDNS outside the Kubernetes context. You're right, Docker kinda acts as the 'missing package manager' for CoreOS apart from some non-containerized stuff like (most of the time) the kubelet or e.g. Calico networking plugins. Guess that's where my confusion came from, as I wanted to run skyDNS 'outside' the Kubernetes cluster i.e. in a non-containerized way while I just could have used a simple Docker container not managed by Kubernetes - instead being invoked by systemd - as well.
PS: seems like the latest-tagged image mentioned in the readme is missing on Docker Hub


Error: [invokeFunction] unknown service 'explorerService'

Hello,
I'm getting an error when triggering the redo action using the following line of code:
editor.trigger('keyboard', 'redo', {});

The error message is the following:

Below my packages versions:

monaco-editor: 0.37.1
monaco-vscode-api: 1.78.8
monaco-languageclient: 6.0.3

After some investigation, it seems like the error is coming from the following piece of code:

I thought to override the ExplorerService to bypass the error still i didn't succeed, it seems like there is no override/implementation yet for that service, am i right?
Any help is welcome, thank you!

Can you try with the last version of this lib/monaco-editor?

Hi @AXeL-dev there is a next version is available (https://github.com/TypeFox/monaco-languageclient/issues/512):
https://www.npmjs.com/package/monaco-languageclient/v/6.3.0-next.1
that uses monaco-vscode-api 1.80.1-next.0 and monaco-editor 0.40.0

@CGNonofr and @AXeL-dev There now is a Draft PR: https://github.com/TypeFox/monaco-languageclient/pull/513
I need to update documentation, but then it is ready for review.

@kaisalmen Actually, it was due to a missing dependency, i fixed it by installing it:
npm i @vscode/vscode-languagedetection

@CGNonofr @kaisalmen All good now! the redo works correctly with version 6.3.0-next.1.
Thank you so much for the help!


CMP: Fix total_timeout behavior; small doc and diagnostic improvements

Also fix up CSR test cases for 81-test_cmp_cli.t
Checklist

[x] documentation is added or updated
[x] tests are added or updated

Rebased to fix trivial merge conflict (due to renamed files changed here).

Rebased again to fix a merge conflict.

This pull request is ready to merge

Merged - thanks @t8m


[sqllab] some frontend tests

stoked to see tests for SQL Lab! i think we could make these test even more useful if we added some tests for component methods (wrapper.instance().someMethod()) and tested that the correct children are rendered as well for each component.

Thank you for the review @ascott! I learned a lot through this PR and ended up refactoring things beyond tests, mostly around reducing the number of points of redux state injection.
I think I addressed all the comments.

Coverage for the whole repo:
Before
=============================== Coverage summary ===============================
Statements   : 12.7% ( 295/2322 )
Branches     : 2.23% ( 14/628 )
Functions    : 7.55% ( 40/530 )
Lines        : 12.75% ( 285/2236 )
================================================================================

After
=============================== Coverage summary ===============================
Statements   : 31.26% ( 703/2249 )
Branches     : 22.31% ( 139/623 )
Functions    : 21.87% ( 110/503 )
Lines        : 31.46% ( 683/2171 )
================================================================================

Details:

@ascott I think I've ironed out all of your comments, your feedback was super valuable, thanks again!

Generally looking good. Big diff! @mistercrunch, thanks for all the code coverage! 🚢


OCPBUGSM-20067 Add View Cluster Events to Day 2

Isn't the role suppose to be always "Worker"? Do we think users will add masters on day 2?

Eagle eye, @nirfarkas  :-) Right, it is recently Worker only but I was told that we might want to add Master in the future. Anyway, this is what API recently allows and especially returns. Rewording Automaitc to Worker or even automatically changing it by UI would not be a good idea.


Fix markdown formatting

Broken in 28899d6ec6 by @janetkuo  according to blame.

This change is

I signed it!


Remote API

vmdkops can only provide limited information.
vmdkops_admin provides detailed information but can only access on ESX node.
We need a remote api ~

@Revolution1 Thank you for your feedback. Can you add some more details for the information you would like to see surfaced? And what is the operational model that you have in mind?

For example，I want to monitor the status of vmdk volumes vmdkops_admin.py ls provides these information but can only access on the ESX node.
what we need is a remote api, restful or socket(vmci). Adding more columns like I/O rates, load etc. could be better.
Volume  Datastore   Created By VM  Created                   Attached To VM  Policy  Capacity  Used
------  ----------  -------------  ------------------------  --------------  ------  --------  -------
myv     datastore1  esx-docker     Tue Aug 23 09:06:55 2016  esx-docker      N/A     100.00MB  14.00MB
myo     datastore1  esx-docker     Tue Aug 23 13:14:39 2016  detached        N/A     100.00MB  14.00MB

And list datastore.
VMCI (the Vmware way):
Currently some of the information is calculated by the vmdkops_admin.py:
def generate_ls_rows():
    """ Gather all volume metadata into rows that can be used to format a table """
    rows = []
    for v in vmdk_utils.get_volumes():
        path = os.path.join(v['path'], v['filename'])
        name = vmdk_utils.strip_vmdk_extension(v['filename'])
        metadata = get_metadata(path)
        attached_to = get_attached_to(metadata)
        policy = get_policy(metadata, path)
        size_info = get_vmdk_size_info(path)
        created, created_by = get_creation_info(metadata)
        rows.append([name, v['datastore'], created_by, created, attached_to,
                     policy, size_info['capacity'], size_info['used']])
    return rows

Just move these codes to vmdk_ops.py.
RestAPI (the Docker way):
The entire Docker ecosystem is based on RestAPI, so may be VMDK plugin should do so.
Thank you.

update:
docker volume inspect api actually left a empty "Status" column:
https://docs.docker.com/engine/reference/api/docker_remote_api_v1.24/#inspect-a-volume
we can put additional information in "Status"
just like what raxray do:
volume inspect aaa
{
    "Name": "aaa",
    "Driver": "rexray",
    "Mountpoint": "",
    "Status": {
        "availabilityZone": "default",
        "fields": null,
        "iops": 0,
        "name": "aaa",
        "server": "scaleio",
        "service": "scaleio",
        "size": 8,
        "type": "defaultSP"
    },
    "Labels": { },
    "Scope": "global"
}

@Revolution1 Please download latest release and check 'docker volume inspect'.
Do not hesitate to give master a try and you will see more features!

Nice！
2016-08-31 23:37 GMT+08:00 Prashant Dhamdhere<EMAIL_ADDRESS>
@Revolution1 https://github.com/Revolution1 Please download latest
release and check 'docker volume inspect'.
Do not hesitate to give master a try and you will see more features!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/vmware/docker-volume-vsphere/issues/586#issuecomment-243804575,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADF13lg4NgwRI2CQpDU2hzWnXapJLIVfks5qlZ-xgaJpZM4Jq9It
.

I compile and install the code from the latest master on both ESX and vm.
And I creted two vmdk volume
I can't mount it ....
ESX:
[root@dce:/usr/lib/vmware/vmdkops/bin] tail /var/log/vmware/vmdk_ops.log
09/01/16 05:45:07 3309244 [esx-docker] [INFO   ] executeRequest 'get' completed with ret=None
09/01/16 05:45:07 3309244 [esx-docker] [INFO   ] *** attachVMDK: /vmfs/volumes/datastore1/dockvols/myv.vmdk to esx-docker VM uuid = 42359e64-15c1-dd2a-647f-d24a69501d22
09/01/16 05:45:12 3309244 [esx-docker] [INFO   ] Disk /vmfs/volumes/datastore1/dockvols/myv.vmdk successfully attached. bus_number=1, disk_slot=0
09/01/16 05:45:12 3309244 [esx-docker] [INFO   ] executeRequest 'attach' completed with ret={'Bus': '1', 'Unit': '0'}
09/01/16 05:45:12 3309244 [esx-docker] [INFO   ] *** detachVMDK: /vmfs/volumes/datastore1/dockvols/myv.vmdk from esx-docker VM uuid = 42359e64-15c1-dd2a-647f-d24a69501d22
09/01/16 05:45:14 3309244 [esx-docker] [INFO   ] Disk detached /vmfs/volumes/datastore1/dockvols/myv.vmdk
09/01/16 05:45:14 3309244 [esx-docker] [INFO   ] executeRequest 'detach' completed with ret=None
09/01/16 05:45:14 3309244 [esx-docker] [INFO   ] executeRequest 'list' completed with ret=[{u'Attributes': {}, u'Name': 'myo'}, {u'Attributes': {}, u'Name': 'myv'}]
09/01/16 05:45:14 3309244 [esx-docker] [INFO   ] executeRequest 'list' completed with ret=[{u'Attributes': {}, u'Name': 'myo'}, {u'Attributes': {}, u'Name': 'myv'}]
09/01/16 05:45:20 3309244 [esx-docker] [INFO   ] executeRequest 'list' completed with ret=[{u'Attributes': {}, u'Name': 'myo'}, {u'Attributes': {}, u'Name': 'myv'}]
[root@dce:/usr/lib/vmware/vmdkops/bin] ./vmdkops_admin.py ls
Volume  Datastore   Created By VM  Created                   Attached To VM  Policy  Capacity  Used
------  ----------  -------------  ------------------------  --------------  ------  --------  -------
myo     datastore1  esx-docker     Thu Sep  1 05:36:49 2016  detached        N/A     100.00MB  14.00MB
myv     datastore1  esx-docker     Thu Sep  1 05:40:40 2016  detached        N/A     100.00MB  14.00MB

vm:
root@ubuntu:~# docker volume ls
DRIVER              VOLUME NAME
local               86161800f044ad216d950f7230f23328d4d42ff0d0533a2f5084a58e8d40a90e
local               a1f648b8ce4edb489bfb6b2be3114136fdf0af5a3f7316283085cbfbae96346c
vmdk                myo
vmdk                myv
root@ubuntu:~# docker run --rm -it -v myv:/v daocloud.io/ubuntu bash
docker: Error response from daemon: VolumeDriver.Mount: Device not found.

root@ubuntu:~# docker volume inspect myv
[
    {
        "Name": "myv",
        "Driver": "vmdk",
        "Mountpoint": "/mnt/vmdk/myv",
        "Labels": {},
        "Scope": "global"
    }
]

When I socat the sock file it did have a "Status" field but the value is "null".
socat TCP-LISTEN:1234,reuseaddr,fork UNIX-CLIENT:/run/docker/plugins/vmdk.sock

root@ubuntu:~# curl -X GET -d '{"Name":"myv"}' localhost:1234/VolumeDriver.Get
{"Mountpoint":"","Err":"","Volumes":null,"Volume":{"Name":"myv","Mountpoint":"/mnt/vmdk/myv","Status":null},"Capabilities":{"Scope":""}}

Maybe I did something wrong with it?
Thank you for your help!

docker volume create --driver=vmdk --name=myv@datastore1 -o size=100mb

Hi,
Most likely you have an older version of the volume plugin. On a volume
attach request, the plugin doesn't return the bus and unit number any more.
Can you pull the current master and test with that.
On Thu, Sep 1, 2016 at 11:30 AM, Renjie Cai<EMAIL_ADDRESS>wrote:

I compile and install the code from the latest master on both ESX and vm.
And I creted two vmdk volume
I can't mount it ....
ESX:
[root@dce:/usr/lib/vmware/vmdkops/bin] tail /var/log/vmware/vmdk_ops.log
09/01/16 05:45:07 3309244 [esx-docker] [INFO   ] executeRequest 'get' completed with ret=None
09/01/16 05:45:07 3309244 [esx-docker] [INFO   ] *** attachVMDK: /vmfs/volumes/datastore1/dockvols/myv.vmdk to esx-docker VM uuid = 42359e64-15c1-dd2a-647f-d24a69501d22
09/01/16 05:45:12 3309244 [esx-docker] [INFO   ] Disk /vmfs/volumes/datastore1/dockvols/myv.vmdk successfully attached. bus_number=1, disk_slot=0
09/01/16 05:45:12 3309244 [esx-docker] [INFO   ] executeRequest 'attach' completed with ret={'Bus': '1', 'Unit': '0'}
09/01/16 05:45:12 3309244 [esx-docker] [INFO   ] *** detachVMDK: /vmfs/volumes/datastore1/dockvols/myv.vmdk from esx-docker VM uuid = 42359e64-15c1-dd2a-647f-d24a69501d22
09/01/16 05:45:14 3309244 [esx-docker] [INFO   ] Disk detached /vmfs/volumes/datastore1/dockvols/myv.vmdk
09/01/16 05:45:14 3309244 [esx-docker] [INFO   ] executeRequest 'detach' completed with ret=None
09/01/16 05:45:14 3309244 [esx-docker] [INFO   ] executeRequest 'list' completed with ret=[{u'Attributes': {}, u'Name': 'myo'}, {u'Attributes': {}, u'Name': 'myv'}]
09/01/16 05:45:14 3309244 [esx-docker] [INFO   ] executeRequest 'list' completed with ret=[{u'Attributes': {}, u'Name': 'myo'}, {u'Attributes': {}, u'Name': 'myv'}]
09/01/16 05:45:20 3309244 [esx-docker] [INFO   ] executeRequest 'list' completed with ret=[{u'Attributes': {}, u'Name': 'myo'}, {u'Attributes': {}, u'Name': 'myv'}]
[root@dce:/usr/lib/vmware/vmdkops/bin] ./vmdkops_admin.py ls
Volume  Datastore   Created By VM  Created                   Attached To VM  Policy  Capacity  Used

myo     datastore1  esx-docker     Thu Sep  1 05:36:49 2016  detached        N/A     100.00MB  14.00MB
myv     datastore1  esx-docker     Thu Sep  1 05:40:40 2016  detached        N/A     100.00MB  14.00MB
vm:
root@ubuntu:~# docker volume ls
DRIVER              VOLUME NAME
local               86161800f044ad216d950f7230f23328d4d42ff0d0533a2f5084a58e8d40a90e
local               a1f648b8ce4edb489bfb6b2be3114136fdf0af5a3f7316283085cbfbae96346c
vmdk                myo
vmdk                myv
root@ubuntu:~# docker run --rm -it -v myv:/v daocloud.io/ubuntu bash
docker: Error response from daemon: VolumeDriver.Mount: Device not found.
root@ubuntu:~# docker volume inspect myv
[
{
"Name": "myv",
"Driver": "vmdk",
"Mountpoint": "/mnt/vmdk/myv",
"Labels": {},
"Scope": "global"
}
]
When I socat the sock file it did have a "Status" field but the value is
"null".
socat TCP-LISTEN:1234,reuseaddr,fork UNIX-CLIENT:/run/docker/plugins/vmdk.sock
root@ubuntu:~# curl -X GET -d '{"Name":"myv"}' localhost:1234/VolumeDriver.Get
{"Mountpoint":"","Err":"","Volumes":null,"Volume":{"Name":"myv","Mountpoint":"/mnt/vmdk/myv","Status":null},"Capabilities":{"Scope":""}}
Maybe I did something wrong with it?
Thank you for your help!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/vmware/docker-volume-vsphere/issues/586#issuecomment-243983925,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APHseOXQKd4l1cWPLB20uL0XIgmq5e1qks5qlmoAgaJpZM4Jq9It
.

With the current master should see something like this (in the
vmdk_ops.log) on a mount request:
executeRequest 'attach' completed with ret={'ControllerPciSlotNumber':
'224', 'Unit': '3'}
Of course the slot number and unit may be different in your set up.
On Thu, Sep 1, 2016 at 12:00 PM, Govindan T<EMAIL_ADDRESS>wrote:

Hi,
Most likely you have an older version of the volume plugin. On a
volume attach request, the plugin doesn't return the bus and unit number
any more. Can you pull the current master and test with that.
On Thu, Sep 1, 2016 at 11:30 AM, Renjie Cai<EMAIL_ADDRESS>wrote:

I compile and install the code from the latest master on both ESX and vm.
And I creted two vmdk volume
I can't mount it ....
ESX:
[root@dce:/usr/lib/vmware/vmdkops/bin] tail /var/log/vmware/vmdk_ops.log
09/01/16 05:45:07 3309244 [esx-docker] [INFO   ] executeRequest 'get' completed with ret=None
09/01/16 05:45:07 3309244 [esx-docker] [INFO   ] *** attachVMDK: /vmfs/volumes/datastore1/dockvols/myv.vmdk to esx-docker VM uuid = 42359e64-15c1-dd2a-647f-d24a69501d22
09/01/16 05:45:12 3309244 [esx-docker] [INFO   ] Disk /vmfs/volumes/datastore1/dockvols/myv.vmdk successfully attached. bus_number=1, disk_slot=0
09/01/16 05:45:12 3309244 [esx-docker] [INFO   ] executeRequest 'attach' completed with ret={'Bus': '1', 'Unit': '0'}
09/01/16 05:45:12 3309244 [esx-docker] [INFO   ] *** detachVMDK: /vmfs/volumes/datastore1/dockvols/myv.vmdk from esx-docker VM uuid = 42359e64-15c1-dd2a-647f-d24a69501d22
09/01/16 05:45:14 3309244 [esx-docker] [INFO   ] Disk detached /vmfs/volumes/datastore1/dockvols/myv.vmdk
09/01/16 05:45:14 3309244 [esx-docker] [INFO   ] executeRequest 'detach' completed with ret=None
09/01/16 05:45:14 3309244 [esx-docker] [INFO   ] executeRequest 'list' completed with ret=[{u'Attributes': {}, u'Name': 'myo'}, {u'Attributes': {}, u'Name': 'myv'}]
09/01/16 05:45:14 3309244 [esx-docker] [INFO   ] executeRequest 'list' completed with ret=[{u'Attributes': {}, u'Name': 'myo'}, {u'Attributes': {}, u'Name': 'myv'}]
09/01/16 05:45:20 3309244 [esx-docker] [INFO   ] executeRequest 'list' completed with ret=[{u'Attributes': {}, u'Name': 'myo'}, {u'Attributes': {}, u'Name': 'myv'}]
[root@dce:/usr/lib/vmware/vmdkops/bin] ./vmdkops_admin.py ls
Volume  Datastore   Created By VM  Created                   Attached To VM  Policy  Capacity  Used

myo     datastore1  esx-docker     Thu Sep  1 05:36:49 2016  detached        N/A     100.00MB  14.00MB
myv     datastore1  esx-docker     Thu Sep  1 05:40:40 2016  detached        N/A     100.00MB  14.00MB
vm:
root@ubuntu:~# docker volume ls
DRIVER              VOLUME NAME
local               86161800f044ad216d950f7230f23328d4d42ff0d0533a2f5084a58e8d40a90e
local               a1f648b8ce4edb489bfb6b2be3114136fdf0af5a3f7316283085cbfbae96346c
vmdk                myo
vmdk                myv
root@ubuntu:~# docker run --rm -it -v myv:/v daocloud.io/ubuntu bash
docker: Error response from daemon: VolumeDriver.Mount: Device not found.
root@ubuntu:~# docker volume inspect myv
[
{
"Name": "myv",
"Driver": "vmdk",
"Mountpoint": "/mnt/vmdk/myv",
"Labels": {},
"Scope": "global"
}
]
When I socat the sock file it did have a "Status" field but the value is
"null".
socat TCP-LISTEN:1234,reuseaddr,fork UNIX-CLIENT:/run/docker/plugins/vmdk.sock
root@ubuntu:~# curl -X GET -d '{"Name":"myv"}' localhost:1234/VolumeDriver.Get
{"Mountpoint":"","Err":"","Volumes":null,"Volume":{"Name":"myv","Mountpoint":"/mnt/vmdk/myv","Status":null},"Capabilities":{"Scope":""}}
Maybe I did something wrong with it?
Thank you for your help!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/vmware/docker-volume-vsphere/issues/586#issuecomment-243983925,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APHseOXQKd4l1cWPLB20uL0XIgmq5e1qks5qlmoAgaJpZM4Jq9It
.

I was directly install the newly compiled vib without remove the old version.
Now I get it run correctly.
Great thanks!


Fix for handling of version ranges

don't include first prerelease in the allowed max for an exclusive range.
Fixes https://github.com/python-poetry/poetry/issues/8475, https://github.com/python-poetry/poetry/issues/8405, https://github.com/python-poetry/poetry/issues/8202
(actually 8202 seems to have been resolved by changes in the available dependencies on pypi and so I can't reproduce it now: but I'm pretty sure these will all be the same)
Absurdly I can't find a simple testcase that takes two versions or version ranges and compares or intersects them or something to demonstrate the point.  So I confess that I don't fully understand what was going wrong before this fix.
However I do understand that those issues are

something to do with wildcard constraints (eg =2.*) which poetry interprets as having a lower bound that is the first dev-release (eg 2.dev0)
and something to do with how they interact with regular but adjacent constraints like <2

so I've made this fix somewhat on gut: <2 certainly shouldn't allow 2.dev0 and so it's weird that allowed_max would return that value.
What can I say?  I'm confused, but this looks like a good fix and it does resolve those issues...

I now think that the real problem - or anyway among the real problems - is ambiguity in poetry-core's treatment of the max in a strict inequality range.

when dealing with a parsed value such as <2 the max is 2 but the allowed_max should be 2.dev0, because pre-releases are excluded by <
however when dealing with a value calculated by operations between other versions or ranges, the max should be considered to be correct as it is, not to be revised by allowed_max

eg consider (>1,<3).difference(2).  This should come out as >1,<2 || >2,<3: except that in the first part of that prereleases should be allowed and so subsequent calculations that treat this as though it were >1,<2.dev0 are wrong

A possible approach is to handle this at parsing and abandon allowed_max altogether.  ie parse_single_constraint("<2") should construct the object with max=2.dev0 all along.  Then never use allowed_max at all.
This also solves those issues reported in poetry - but causes carnage in the test scripts: the main (but probably not only) problem being that parsing and then printing <2 then gives <2.dev0 - which should indeed be equivalent, but is not so pretty...

A possible approach is to handle this at parsing and abandon allowed_max altogether. ie parse_single_constraint("<2") should construct the object with max=2.dev0 all along. Then never use allowed_max at all.
This also solves those issues reported in poetry - but causes carnage in the test scripts: the main (but probably not only) problem being that parsing and then printing <2 gives <2.dev0 - which should indeed be equivalent, but is not so pretty...

If we went down this path, maybe we should also change __str__ so that <2 and <2.dev0 would always be printed as <2? I suppose explicit constraints like <2.dev0 are rare so that complaints that <2.dev0 gives <2 are neglectable.

that seems plausible and I have a branch in which I tried it.  Among the chaos in the unit tests I see at least these wrinkles

lots of failures where the unit tests compare a parsed value to an explicitly constructed Version and now get a different answer: to be expected, but will be tedious to work through
there's a distinction between version ranges as used in version requirements, and versions as used in markers / python versions.  So as not to break the world it's probably unwise to make changes for the latter two
the good news is that printing <2.dev0 as just <2 is I think fine in the PEP440 context; because the rules about prereleases give these strings the same meaning
this approach both fixes and introduces bugs when dealing with != specifiers

eg !=2 is represented internally as <2 || >2.  Today, the allowed_max business re-interprets that as <2.dev0 || >2 ie it wrongly disallows the prereleases
eg after the change, (>1).union(!=2) for some reason becomes >1,<2 || >2.  Without allowed_max that's correct as an internal representation, but becomes wrong once re-parsed - it really does want to be written eg in lockfiles as >1,!=2

probably there's more that I haven't yet spotted
This feels like the right direction conceptually but I've no idea when or whether I'm likely to find the time or energy to do anything about it

I now think that the real problem - or anyway among the real problems - is ambiguity in poetry-core's treatment of the max in a strict inequality range.

when dealing with a parsed value such as <2 the max is 2 but the allowed_max should be 2.dev0, because pre-releases are excluded by <

Pre-releases must be excluded by < unless the specified version is itself a pre-release, yes. But development releases are pre-releases for any release, including pre-/post-releases.
The versions 2aN.devN, 2aN, 2bN.devN, 2bN, 2rcN.devN, 2rcN are all less than 2.dev0.
If you wanted a pre-release allowed exclusive upper bound for the latest version starting with 1 or less then the exclusive ordered comparison equivalent syntax should be <2a0.dev0.

You are mistaken, but thanks anyway
https://peps.python.org/pep-0440/#summary-of-permitted-suffixes-and-relative-ordering


Remove all references to the Maven Wrapper

Remove all references to the Maven Wrapper

Story ID
Story Name

#172483248
Remove all references to the Maven Wrapper in the projects listed in the story

Summary of Changes:
Remove mvn.cmd and .mvn/wrapper

Review readiness
This pull request is considered a Work In Progress unless all of the following boxes are checked.
Items not required for this PR should be removed from the below list.

[x] A secret scan was run:

[ ] on every commit
[ ] on every push

[x] Existing tests of the following types were run:

[ ] unit tests
[ ] integration tests

[ ] Application was run to ensure it is still working as expected
[ ] Examples given to customers still work as expected
[ ] Code quality gates have been meet:

[ ] Code Coverage
[ ] Sonar Quality Gate

[x] Ensured no breaking changes to the public interface

PR Reviewer's Checklist
Be sure to give yourself enough time to review the PR.  We are looking for good approvals, not rubber stamped approvals.

[x] Pull down the branch
[x] Review the code
[x] Build the code
[x] Run tests, application and/or examples locally
[x] Review code's coverage
[x] Review code's Sonar quality gate

Reviewers for this PR:

[ ] @autonomic-tmc/sdk-team
[ ] @autonomic-tmc/fe-pr-reviewers

The repository's README.md contains references to the Maven wrapper. Please remove them.
./mvnw clean install
./mvnw -Pintegration-tests clean verify
(export TMC_CLIENT_ID=your-client-id && export TMC_CLIENT_SECRET=your-client-secret && ./mvnw -Pintegration-tests clean verify)

Maybe they should just be updated. We could just do mvn clean install and etc.

Oops!  I meant update them, not remove then.  Sorry for the confusion.

As discussed with team, leaving the maven wrappers in for now. Updated documentation to use ./mvnw instead of mvn.
Story to investigate usage of maven and gradle wrappers: https://www.pivotaltracker.com/story/show/172596720


cant for the life of me make this work in lazyvim

see title, plus with telescope. get error on load. i think i have several ways of configuring it mixed up.
`Error  21:35:29 notify.error lazy.nvim Failed to run config for telescope.nvim
...m/lazy/telescope.nvim/lua/telescope/_extensions/init.lua:10: 'project' extension doesn't exist or isn't installed: module 'telescope._extensions.project' not found:
no field package.preload['telescope._extensions.project']
cache_loader: module telescope._extensions.project not found
cache_loader_lib: module telescope._extensions.project not found
no file '/nix/store/rcn887ckva37g82v34kki2h8r0l15qyk-luajit-2.1.1713773202-env/share/lua/5.1/telescope/_extensions/project.lua'
no file '/nix/store/rcn887ckva37g82v34kki2h8r0l15qyk-luajit-2.1.1713773202-env/share/lua/5.1/telescope/_extensions/project/init.lua'
no file '/Users/nils/.local/share/nvim/lazy-rocks/telescope.nvim/share/lua/5.1/telescope/_extensions/project.lua'
no file '/Users/nils/.local/share/nvim/lazy-rocks/telescope.nvim/share/lua/5.1/telescope/_extensions/project/init.lua'
no file '/nix/store/rcn887ckva37g82v34kki2h8r0l15qyk-luajit-2.1.1713773202-env/lib/lua/5.1/telescope/_extensions/project.so'
no file '/Users/nils/.local/share/nvim/lazy-rocks/telescope.nvim/lib/lua/5.1/telescope/_extensions/project.so'
no file '/nix/store/rcn887ckva37g82v34kki2h8r0l15qyk-luajit-2.1.1713773202-env/lib/lua/5.1/telescope.so'
no file '/Users/nils/.local/share/nvim/lazy-rocks/telescope.nvim/lib/lua/5.1/telescope.so'
stacktrace:

/telescope.nvim/lua/telescope/_extensions/init.lua:10 in load_extension
/telescope.nvim/lua/telescope/_extensions/init.lua:62 in load_extension
~/.config/nvim/lua/plugins/telescope.lua:101 in config
/LazyVim/lua/lazyvim/plugins/extras/editor/telescope.lua:44 in open
/LazyVim/lua/lazyvim/util/pick.lua:75 in open
/LazyVim/lua/lazyvim/util/pick.lua:83
lua:1
vim/_editor.lua:0 in cmd
/dashboard-nvim/lua/dashboard/theme/doom.lua:24`

can you paste you configuration? it should be something like this
{
  'ahmedkhalf/project.nvim',
  config = function()
      require('telescope').load_extension('projects')
  end
}


Issue and Pull Request linking

As we discussed;

Every pull request must be linked with an issue.

I found Linking a pull request to an issue article. As I read, using keyword is working only default branch. However we will link every pull request and issues.
@onurmenal do you have any opinion?

I think default approach is clear. We didn't discuss code review standarts yet. May be we can check all of this details on code review stage.


Doubt or request to have availability to select time range in week/day view

Version
"tui-calendar": "^1.7.0"
Development Environment
Debian 4.9.110-3+deb9u6 (2018-10-08) x86_64 GNU/Linux
Current Behavior
I don't need full 24h in the week view
Expected Behavior
// Write example code
// Option to select time range:
 ...
    week: {
      startTime: 11, // [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23] default: 0
      endTime:  23, // [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23] default:23
    }
...

To have the week view narrowed to the interested time range, otherwise I have all the relevant information at the bottom and half view empty.

We have the options that you expect: hourStart, hourEnd. But it's not released.
See this commit.

Thanks for the quick feedback.
When is it expected to be released?
I found full calendar with that option, so now I am not using tui calendar
but it is a great work anyways. Keep on it.
Saludos,
•_-
El lun., 5 nov. 2018 3:34, 유동식<EMAIL_ADDRESS>escribió:

We have the options that you expect: hourStart, hourEnd. But it's not
released.
See this commit
https://github.com/nhnent/tui.calendar/commit/a98b35d077869a6e9984b373016c2a29be65f706
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nhnent/tui.calendar/issues/235#issuecomment-435737675,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACS6R7oS1ySThsNd1gMKmYrcyJowKfqeks5ur6OhgaJpZM4YMG1o
.

@jmvelasco Check the new version v1.8.0.


CRN-1178 add working groups card component

new PR here: https://github.com/yldio/asap-hub/pull/2409


how  to use labels or text as conditions

Hi, great work!
I'm also trying to reproduce sCM and testing with your code.
"""
train_consistency.py  line 90~98
v_x = torch.cos(t) * torch.sin(t) * dxt_dt / sigma_data
v_t = torch.cos(t) * torch.sin(t)
F_theta, F_theta_grad, logvar = torch.func.jvp(
model_wrapper,
(x_t / sigma_data, t),
(v_x, v_t),
has_aux=True
)
"""
I have a question: if I want to use labels or text as conditions, what should v_y look like?
I'm looking forward to your answer.

I assume $y$ refers to the conditional input to the model. In that case, there is no $v_y$. The model only needs to be differentiated with respect to $x$ and $t$, while $y$ is just treated as a constant. With class labels, you can think of this like training a separate model for each class, but share most of the weights to improve performance.
model_wrapper exists so that only the necessary variables are differentiated: scaled_x_t and t. return_logvar is not (and can't be) differentiated, so it is not used as input to model_wrapper:
def model_wrapper(scaled_x_t, t):
        pred, logvar = model(scaled_x_t, t.flatten(), return_logvar=True)
        return pred, logvar

If you have a separate condition c to the model (class label, text, etc), you can modify model_wrapper to capture c and input it into the model:
for x0, class_label in dataset:
    x0 = x0.to(device)
    class_label = class_label.to(device)

    # Notice that c is captured as input to the model, but is not a parameter
    # in model_wrapper, so it will not be differentiated (i.e it is treated as a constant).
    def model_wrapper(scaled_x_t, t):
        pred, logvar = model(scaled_x_t, t.flatten(), return_logvar=True, c=class_label)
        return pred, logvar

Keep in mind that you have define model_wrapper after loading each batch of the dataset with this modification.
I added a commit efc165954f7997ad246d05b4f3eaf15c9020e7fb to make this clearer.

ok, understood, thank you very much.

closed issues

fixed #24


Fix mobile responsiveness based on tasks listed.

[x] The header of the Logo.gif and Github avatar arranged with flex-direction: column when the screen size is smaller than 640px.
[x] Adjust the text "An Open Source Project".
[x] The dummy images will not displayed in the background behind "An Open Source Project" when the screen size is smaller than 640px.
[x] Reformat contributors bid_image and avatar image
[x] The display text of the answer for "Before I Die" is arranged when the screen size is smaller than 640px.

Hi @lefty93,
Thank you for your time in assisting in this issue #14. I'm traveling and will review upon settling in at my destination. I appreciate you looking into this issue, Chu. Have a great day! And looking forward to seeing your work😀
Xander

Great job, Chu! Your updates have greatly improved the responsiveness of our project. Adjusting the screen window and viewing on mobile is now much smoother and cleaner. These small changes make the project more user-friendly and appealing.
I noticed that you added a state variable named "isMobile" and used the useEffect hook to add an event listener to the window object, which listens for the resize event. When triggered, the "handleSize" function updates the value of "isMobile" based on the width of the window. If the width is less than 768 pixels, "isMobile" is set to true, indicating that the application is being viewed on a mobile device. The useEffect hook also removes the event listener when the component unmounts.
You have done an excellent job using the value of "isMobile" to conditionally render the BrickLayout component. If "isMobile" is true, the BrickLayout component is rendered; otherwise, it is not.
Overall, your continual improvements to our UI interface are greatly appreciated. Keep up the great work, Chu! 👏🏻👏🏻Have a wonderful day!
And please feel free to add open issues of your own that you see fit for improving the Before I Die Code Project.


Selection of direct children of an HTML element

It seems that the possibility is missing to find direct childrens of an HTML element. According to http://stackoverflow.com/questions/3687637/how-to-get-only-direct-child-elements-by-jquery-function in jQuery there exist two possibilities to do this. In AngleSharp I would expect that the function QuerySelectorAll(">tr") used on an tbody element would only return the table rows which are the direct childs of this table body but not the ones in a nested table.

No the child selector should work (actually, jQuery has nothing to do with this - this is a standard CSS selector). Can you post a MWE to illustrate your problem?

            string source = @"
                <!DOCTYPE html>

                    <title></title>

                        data1
                        data2

                        data3

                                    subdata1
                                    subdata2

                ";
            HtmlParser parser = new HtmlParser();
            IHtmlDocument document = parser.Parse(source);

            IElement tableElement = document.QuerySelector("table");
            IHtmlCollection<IElement> tableRows = tableElement.QuerySelectorAll(">tr");
            Console.WriteLine(tableRows.Length);

Above is a simple example. I would have expected to see only the two child rows returned, but the tableRows collection contains three elements, including the one within the nested table.

The result is as expected. The selected you provided is converted to * > tr, which means all tr elements that are (direct) childs of any element.
BTW: Before you think there is something wrong with AngleSharp, please first check with any evergreen browser you got installed. Every browser will also return 3 in this case.
If you try the following you'll get the two rows you want:
var tableRows = document.QuerySelectorAll("body > table > tbody > tr");

Then you will get the expected result. Please note that I explicitly use body. If I would just omit this I would get 3:
var tableRows = document.QuerySelectorAll("table > tbody > tr");

For me your suggestion does not work, and that's why I quoted the jQuery solution: in my program I found already a specific element and want to select certain child nodes from it (e.g. the tr elements from above). In CsQuery I could have used element.Children("tr") for this (which is also supported by jQuery), but I cannot find a simple solution using AngleSharp.

Hm, this is strange as AngleSharp makes such things quite simple (imho). If you know LINQ and the DOM its easy.
var tableElement = document.QuerySelector("table");
var tableRows = tableElement.Children.Where(m => m.LocalName == "tr");

Please note that the example will result in 0 elements as tr are elements of tbody and not table, but this should be sufficient give you the right idea.

Thanks, this solves my problem!

For posterity:
document.QuerySelector("tbody").QuerySelectorAll(">tr")
document.QuerySelector("tbody").QuerySelectorAll(":scope>tr")

This isn't specific to AngleSharp, it's how all browsers work. However, it's unintuitive to need the :scope before >, so others probably made the same mistake.


FeignClient returns empty results when azure key vault dependency include in  build.gradle

Hello Everyone,
I am experiencing the weird issue with Azure keyvault dependency and OpenFeign(FeignClient)
I am using FeignClient to invoke  REST endpoint in springboot. It works fine. However, When I include below dependency for azure keyvault in build.gradle, endpoint returns empty results.
If I exclude the below dependency, I am able to see the results form endpoint.
Azure key vault dependency:
compile("com.azure.spring:azure-boot-starter-keyvault-secrets:3.6.0")
open feign dependencies:
compile("org.springframework.cloud:spring-cloud-starter-openfeign:2.1.3.RELEASE")
compile("io.github.openfeign:feign-okhttp")
SpringbootVersion :2.3.12
SpringCloudVersion: "Greenwich.M2"
Please let me know if anybody experienced the same issue.

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.


Bump digikam to 5.0

Digikam 5.0 got released. Packaging-wise that's not a simple version bump as digikam removed most of its KDE4 dependencies and ported to Qt5. For reference https://quickgit.kde.org/?p=digikam-software-compilation.git&a=blob&f=DEPENDENCIES
As 4.12 isn't really usable for me, I am offering 0.1 Bitcoin (~56$ ATM) as reward for the pull request that closes this issue, claimable till 2016/10/01. Please let me know if offers like these are inappropriate on the issue tracker.

/cc maintainers @cillianderoiste, @viric.

Please let me know if offers like these are inappropriate on the issue tracker.

On the contrary, I appreciate such bounties. Several months ago, I tried living on nix-related freelancing, but I stopped as it didn't seem very sustainable over long term.

@vcunat: Thanks for the clarification!
If I may update the bounty, digikam 5.1 just saw the light of day, see https://www.digikam.org/node/756. Packaging-wise, it should be the same as 5.0.

Got it working here with most optional features enabled. Just need some more time to get the geo-stuff (based on marble) working.
@clefru may I ask what use case made 4.12 unusable for you?

@the-kenny I struggled for some time to have digikam delete pictures for me because the kio-slave for trash:/ wouldn't launch. "nix-env -i kderuntime" into my user's nix-env eventually solved that problem as apparently it had nothing to do with digikam's own dependencies. I expect KDE5 to be much more of a hassle free experience, so I am committed to my bounty :)

Good news then! I'm not running any desktop environment either, and nix-env -i digikam5 just works™. The new non-kde trash also works flawlessly (it just stores trashed files in <dbdir>/.dtrash).
I'll ping you as soon as the PR gets merged.

One more thing: I noticed one bug that I couldn't solve yet: After the first start, I don't see any icons in the UI. This is solved by going into Digikam Settings -> Miscellaneous -> Icon Theme and selecting Breeze

What is <dbdir>/.dtrash exactly? Does that directory ever get cleaned up?

Digikam has the concept of collections - a directory tree with photos in it. The ~/.dtrash directory is in the root of that tree. It also provides an UI to show the trashed photos and to delete them permanently.

Thanks @the-kenny for your work! I've sent you your reward :).


Maya: Camera settings overrides are not working

Describe the bug
Project camera settings overrides for extract playblast in Maya are not working
To Reproduce
set the camera overrides in settings and publish review
Screenshots

Desktop :

OS: Windows
Host: Maya 2022.4
latest develop

[cuID:OP-3648]

Thank you Murphy, I'll fix this as I worked on this code earlier and it shouldn't take long.


Minor docs fixes

Proposed Changes
Minor rst formatting fixes.
Any background context you want to provide?
GSoD'19 applicant.

Could you give some more background for this? Did you have problems with getting the images to show up? The leading slash makes sphinx look in the docs root for the images (and they do show up in our generated docs, e.g. here).

Can you see any file on GitHub? How does the .png looks?

@tapaswenipathak I'm not sure I understand your question. The corresponding image (to the link I posted) is here in the repository.

Sorry for not replying earlier. I see now what you mean. I would really encourage users to read the generated documentation and not on GitHub. There are many other things that don't show up correctly at all when reading on GitHub. But this is a very small change so it definitely won't hurt to do this. There's one more of these that need to be changed in https://github.com/STEllAR-GROUP/hpx/blob/master/docs/sphinx/examples/1d_stencil.rst.

@msimberg do you think I can enhance anything else in this PR?


Error with Android SafetyNet AttestationFormat

Hi,
When using a Samsung mobile with Samsung Pass for biometric authentication, at registration JwtSecurityToken cause an exception.
AndroidSafetyNet.cs - AndroidSafetyNet.Verify()
IDX12729: Unable to decode the header
Header
{   "alg": "RS256",   "x5c": [ 2 certificates from google] }
Payload
{   "nonce": "69U9PFuBsL41fFrI7aJg8q3P+kTW77gJDVoOHvcrZqFG0pc=",   "timestampMs":<PHONE_NUMBER>858,   "apkPackageName": "com.google.android.gms",   "apkDigestSha256": "rTlKdfWU/r7xz"t5vjK6sH3C1Jfn5mRSC1HUStqJ4WX1vWFE=",   "ctsProfileMatch": true,   "apkCertificateDigestSha256": [     "8P1sW0E77PJcslw7UzRsiXL64w+O5041Ed+RBICtay1g24M="   ],   "basicIntegrity": true }
Parameters are

AuthenticatorAttachment=""
AttestationConveyancePreference="direct" // or indirect
UserVerificationRequirement="preferred"
Extensions="true"
UserVerificationIndex="true"
Location="true"
UserVerificationMethod="true"
RequireResidentKey="false"

Browser is Android Chrome version 78.0.3904.108
Android 9.0
Server FW 4.7.2 Windows 2019

Any Ideas ?
Regards

Solved ! for the momment...
The problem was Newtonsoft.json version 10.0.x which was required for System.IdentityModel.Tokens.Jwt (version 5.2.4 and Up)
I also Revert Base64UrlConverter to standard Type - Non generic: JsonConverter.
I don't think if your solution works at well with framework 4.7.2. and signed assemblies.
I'm working on an implementation for ADFS whitch require signed assemblies.
Best Regards

I am interested in helping you get this working the way you need it to. I really want to see an ADFS adapter for on prem that can authenticate users who have registered FIDO2 security keys with WHfB in Azure AD.

At this time, I am integrating your solution, and it is going pretty well.
You will see some screenshots below.
I will publish a new branch for a version 2.5 alpha before Christmas.
Because I still have a few things to put in place so that it is easily usable and testable.
Your expertise will be welcome.
The first tests are good, with FIDO keys, A Brio WebCam, or just the fingerprint readers present on PCs, tests with Android mobiles are also good.
This Alpha version will probably only work in memory with DemoStorage, SimpleMetadataService and StaticMetadataRepository.
Eventually, the Storage will be ADDS or SQLServer as supported today. SQLServer side no worries in sight, but For ADDS it's still in reflection.
Of course, I want to be able to manage several devices per user (up to 10 probably), PC, Tablet, Phone, professional or personal.
Regards

The storage is the thing I want to change, particularly for this application.  Windows Hello for Business uses msDS-KeyCredentialLink.  The feature that allows you to add FIDO2 security keys to an Azure AD user, when that data is replicated inbound to on prem domain controllers, that is the attribute it goes into.  Theoretically, you should be able to use the data in that attribute as the data store.  It should be pretty easy the way we built this to make it work, I just haven't found the time/motivation to actually make it a reality.  But that was basically one of my main goals when I was starting to get involved with this.

Hi,
Thank you for the tip ! I will use it.
On the other hand, people who are not in version 2016 for ADDS (v85), it will be necessary that I limit them to a single possibility, and that for those who wish to modify their ADDS Schema (which is rare, and often "complicated") it will eventually provide them the necessary scripts.
thanks again


Simplified Chinese translation recommendation of Settings UI

Key
Recommendation
Comment

Actions_DeleteConfirmationButton.Content
是，删除此快捷键
The current translation "密钥" means an encryption key, should use "快捷键" instead.

Actions_DeleteConfirmationMessage.Text
确定要删除此快捷键吗
Same as above.

Globals_DefaultProfile.HelpText
单击 '+' 图标或按下新建选项卡快捷键时打开的配置文件。
Same as above. And the "新的" is an adjective, should use "新建" instead. Using "按下" instead of "键入" is more typical.

I used the Feature template to open this issue, but maybe it should be categorized as a bug label.

I'm sorry for the long wait! This is now tracked at MSFT-44562310.


Different / Varied Failure Cases

Hi,
Really liking tinytuya - appreciate it! But I admit, seeing some odd results here. I think that's my specialty though ... 🤣.
 But ... relatively often (i.e. 10+ times a day), they cause my code to "yell", for a few different reasons. So attaching my code below, as well as some of the error messages. And a few thoughts,

I was going to add code to check for the recently added Error status ... but nothing is there in the case of passing results? Thinking there should always be a return status? Just to avoid try ... catch loops (they just seem nasty, LOL!)
I seem to be seeing different outcomes and failures, some of them not caught (reported) by the Error status. Or am I missing it?

My code, called inside the loop, with except to let me know what kinds of failure I am seeing,
        try:
            device = tinytuya.OutletDevice(currdevice['id'], currdevice['hostname'], currdevice['key'])
            device.set_version(currdevice['ver'])
            device.set_socketPersistent(True)
            device.updatedps()
            currData = device.status()
            if currdevice['ver'] == 3.1:
                time.sleep(0.5)
            dps = currData["dps"]
            # Check for power data - DP 19 on some 3.1/3.3 devices
            W = A = V = 0
            if "19" in dps.keys():
                W = float(dps['19']) / 10.0
                A = float(dps['18']) / 1000.0
                V = float(dps['20']) / 10.0
            # Check for power data - DP 5 for some 3.1 devices
            elif "5" in dps.keys():
                W = float(dps["5"]) / 10.0
                A = float(dps["4"]) / 1000.0
                V = float(dps["6"]) / 10.0
            # Return power measurement results
            return {'Current': A, 'Power': W, 'Voltage': V}
        except OSError:
            print("[OSError] Error reading Tuya power meter, ", currdevice['hostname'])
            return None
        except ValueError:
            print("[ValueError] Error reading Tuya power meter, ", currdevice['hostname'])
            return None
        except KeyError:
            print("[KeyError] Error reading Tuya power meter, ", currdevice['hostname'])
            print("[KeyError] Data, ", currData)
            return None
        except TypeError:
            print("[TypeError] Error reading Tuya power meter, ", currdevice['hostname'])
            print("[TypeError] Data, ", currData)
            return None

And, some of the exceptions (some normal / caught, others not,
[KeyError] Error reading Tuya power meter,  emFrontSwitch [KeyError] Data,  {'Error': 'Network Error: Unable to Connect', 'Err': '901', 'Payload': None}
[TypeError] Error reading Tuya power meter,  emRussell [TypeError] Data,  None
[KeyError] Error reading Tuya power meter,  emWinServer [KeyError] Data,  {'dps': {'18': 530, '19': 642}, 't':<PHONE_NUMBER>}
[KeyError] Error reading Tuya power meter,  emRussell [KeyError] Data,  {'Error': 'Network Error: Device Unreachable', 'Err': '905', 'Payload': None}

And this one, when using the data (somehow wrong data type?),
influxdb.exceptions.InfluxDBClientError: 400: {"error":"partial write: field type conflict: input field \"value\" on measurement \"Current\" is type integer, already exists as type float dropped=3"}

Thanks!

You can add a check for an error response from the status() call with something like this:
currData = device.status()
if currData is None or "Error" in currData:
    # something went wrong
    if "Error" in currData:
        Error = currData["Error"]
        print(Error)
    else:
        print("Null response")
    # return an error state or perhaps wait and retry?
    return {'Current': -1, 'Power': -1, 'Voltage': -1}

Some of the responses do not include all the keys (18, 19 and 20) which is probably an out of sync response from the device.updatedps() call which I have discovered only returns keys to values that actually changed since the last call.   You could update your check to:
            if "18" in dps and "19" in dps and "20" in dps:
                W = float(dps['19']) / 10.0
                A = float(dps['18']) / 1000.0
                V = float(dps['20']) / 10.0

call which I have discovered only returns keys to values that actually changed since the last call.

That makes sense, except ... and voltage may not change, even if current and power do - let me add a check for that. Good to know about this, thanks!
BTW, with my error checks, now I'm seeing this returned (entire return json) - make sense to you?
'Err',

Thanks again.

OK, updated my code to check individually for each returned value - let's see if that does it 😄.
Thanks again for the info!

Keep in mind that the status() command should always return all of the values.  The payloads you get that have only partial data can be ignored as they are likely out of sequence (delayed) responses from the updatedps() call.

FYI, I am using status(), after updatedps() ... still only partial parameters. Voltage, for example, is often not there. No biggie, I worked around it.
In case you're interested (or not ... LOL!), stats from the last day (or so),
hostname=emFrontSwitch       : Failure Rate = 0.5%, OK Count = 1240, Total Count = 1246
hostname=emMacOS             : Failure Rate = 0.1%, OK Count = 1245, Total Count = 1246
hostname=emLinuxServer       : Failure Rate = 0.0%, OK Count = 1246, Total Count = 1246
hostname=emPoolTuya          : Failure Rate = 2.0%, OK Count = 1221, Total Count = 1246
hostname=emRussell           : Failure Rate = 1.8%, OK Count = 1223, Total Count = 1245
hostname=emWinServer         : Failure Rate = 1.5%, OK Count = 1227, Total Count = 1246

And, from the highest failure rate,
name: Error
tags: errMessage=ERR_CONNECT
time count
---- -----
0    1

name: Error
tags: errMessage=ERR_OFFLINE
time count
---- -----
0    14

name: Error
tags: errMessage=tuyaTypeError
time count
---- -----
0    7

Wondering if perhaps adding more retries may help?
Thanks!

Thanks Russell.  Increasing the retry may help, or adding a retry specifically in your code when you don't get the response you want.  Keep in mind that the network ERROR responses you are getting occur only after tinytuya tries 5 times (you can increase the default with set_socketRetryLimit(integer)).
Do you have any other systems polling the devices at the same time?  That overlap may be causing some of the network errors.

you can increase the default with set_socketRetryLimit(integer)

Will give that a try, thanks!
FYI, getting very few error warnings now (as I trap most of them, log as needed). But did get this just today, figured I'd let you know.
Traceback (most recent call last):
  File "./eMeter.py", line 89, in <module>
    currData = meterTuya.emeter(currDevice)
  File "/mnt/ProgSSD/eMeter/tuyaMeter.py", line 30, in emeter
    device.updatedps()
  File "/mnt/ProgSSD/eMeter/venv/lib/python3.8/site-packages/tinytuya/__init__.py", line 880, in updatedps
    data = self._send_receive(payload,0)
  File "/mnt/ProgSSD/eMeter/venv/lib/python3.8/site-packages/tinytuya/__init__.py", line 574, in _send_receive
    msg = unpack_message(data)
  File "/mnt/ProgSSD/eMeter/venv/lib/python3.8/site-packages/tinytuya/__init__.py", line 301, in unpack_message
    _, seqno, cmd, _, retcode = struct.unpack(
struct.error: unpack requires a buffer of 20 bytes

Thanks!

Thanks!  Yes, I would love to figure out how that occured.   That's an odd one:

_, seqno, cmd, _, retcode = struct.unpack(
struct.error: unpack requires a buffer of 20 bytes

The confusing thing about that error is that unpack_message() should never be called if the payload is not at least 28 bytes and retry is not True.   Do you happen to have anything in your code that would do something like these:
d.retry = 5
d.retry = False

It could just be a weird GC issue in Python.  What python version are you using?

NP, let me know what I can do to help!

Do you happen to have anything in your code that would do something like these

I don't think so .. LOL! Here is my latest,
        try:
            device = tinytuya.OutletDevice(currdevice['id'], currdevice['hostname'], currdevice['key'])
            device.set_version(currdevice['ver'])
            device.set_socketPersistent(True)
            if 'socketTimeout' in currdevice:
                device.set_socketTimeout(currdevice['socketTimeout'])
            if 'socketRetryLimit' in currdevice:
                device.set_socketTimeout(currdevice['socketRetryLimit'])
            device.updatedps()
            currData = device.status()
            if currdevice['ver'] == 3.1:
                time.sleep(0.5)
            dps = currData["dps"]

What python version are you using?

Python 3.8.6

FYI, I see this issue hit every day or two. Not a biggie by any means, it's sort of a percolating (and interesting) item ... 😄

Thanks @arrmo - I appreciate the updates.  I added some additional error handling for unpack_message() calls to see if we can catch it.  It will be available in v1.2.4.

Hmmm ... nothing so far 😆. And with v1.2.4, my failure rates are down quite a bit? Did you change anything else?
hostname=emFrontSwitch       : Failure Rate = 0.7%, OK Count = 1428, Total Count = 1438
hostname=emHackintosh        : Failure Rate = 0.0%, OK Count = 1439, Total Count = 1439
hostname=emLinuxServer       : Failure Rate = 0.0%, OK Count = 1438, Total Count = 1438
hostname=emPoolTuya          : Failure Rate = 0.3%, OK Count = 1433, Total Count = 1438
hostname=emRussell           : Failure Rate = 0.0%, OK Count = 1438, Total Count = 1438
hostname=emWinServer         : Failure Rate = 0.3%, OK Count = 1434, Total Count = 1439

Thanks!

That's great!  There were a few other tweaks and bux fixes that went in, but it seems odd that it would have such a profound effect.  I'll take it.  Hopefully it holds. ;)  Thanks for the update.


Regenerated doc

Description
Regenerated doc
Type of change

Documentation update

Testing steps
N/A
Checklist

[ ] make before_commit passes
[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary
[ ] updated schemas and validators in insights-data-schemas in case of input/output change

Codecov Report

Merging #180 (62078e7) into master (53a59bc) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #180   +/-   ##
=======================================
  Coverage   25.64%   25.64%
=======================================
  Files           3        3
  Lines         468      468
=======================================
  Hits          120      120
  Misses        339      339
  Partials        9        9

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 53a59bc...62078e7. Read the comment docs.


[stable/jenkins] Bump appVersion

Jenkins LTS 2.107 has been released. Bump appVersion to reflect this.

/assign @unguiculus

/ok-to-test
/lgtm

Cheers.


Fix frame reloading from links instead a frame or a from a form

Closes #365

I am not a JavaScript expert but looking at https://github.com/hotwired/turbo/pull/360 it seems like it was supposed to already test for this. Is there an existing test producing a false positive?

FYI: The failed chrome test passed on firefox in the same build.  Also in my local environment the failed test passes.

I am not a JavaScript expert but looking at #360 it seems like it was supposed to already test for this. Is there an existing test producing a false positive?

#360 fixed the case where the link existed outside a frame, but Turbo uses different code when the link exists inside a frame.

@tleish could you please rebase from main? This should help with failing tests.