Support logging into AWS China (possibly a regression)

Describe the bug
I used to use this tool to authenticate against our AWS China account, but recently that stopped working.
Based on the debug logs, I suspect that we have to handle logic for the AWS China partition the way we handle the GovCloud partition.
To Reproduce
Steps to reproduce the behaviour:

Have an AWS China account
Create an Okta ADFS?/SSO? configuration for said account.
Set up an .okta-aws profile for that account (the app-link URL will be indistinguishable from the a non-China partition url, but any roles will look of the form arn:aws-cn:iam::<account_number>:role/<role_name>
Attempt to log in using okta-awscli

Expected behavior
I am able to log in successfully
Output
okta-awscli -dvf -o awscn -p awscn sts get-caller-identity
DEBUG - Setting AWS role to arn:aws-cn:iam::REDACTED:role/Okta-REDACTED
DEBUG - Setting AWS partition to AwsPartition.AWS <--- I suspect this is the issue
INFO - Force option selected,                 getting new credentials anyway.
INFO - App Link set as: https://tulip.okta.com/app/amazon_aws/REDACTED/sso/saml
INFO - Authenticating to: REDACTED.okta.com
INFO - Authenticating as<EMAIL_ADDRESS>Enter password:
INFO - Using predefined role: arn:aws-cn:iam::REDACTED:role/Okta-REDACTED
INFO - Authenticating to: REDACTED.okta.com
DEBUG - Requesting a duration of 14400 seconds
DEBUG - Getting STS token against ARN partition: AwsPartition.AWS
ERROR - Could not retrieve credentials: Specified provider doesn't exist (Service: AWSOpenIdDiscoveryService; Status Code: 400; Error Code: AuthSamlManifestNotFoundException; Request ID: 0c37721e-d8e5-4afb-a43d-fc9c1f5c618b; Proxy: null)

Environment (please complete the following information):

OS: MacOS
Version: 0.5.4

Additional context
None

Closing ... I have to explicitly set the region in my .aws/credentials


Added community demo to README

This change is

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Review status: 0 of 1 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 1 of 1 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Remove usage of DeviceAddressUpdateDelegate from python

Problem
DeviceAddressDelegate creates very strong coupling in flows and makes moving towards per-sessin tracking of address resolution much harder.
Change overview
Remove the DeviceAddressDelegate usage from python. Code/tests should not rely on this. As far as I could tell, C++ code was only ever using logging, do not expect python to be able to have needed more.
Testing
CI should validate.

I would note that originally this update could be used for 'commissioning complete', however currently we have a 'pairing delegate' that handles that and address resolution is generally just an intermediate step notification.

Fast tracking tooling updates


MRG: Better use of Nibabel

use .affine instead of .get_affine() etc.

LGTM, test fail might be fixed by merging #127

@bthirion please help me in #130 to fix version updates


ResourceName: ADServicePrincipalName After PSGallery installation of ActiveDirectoryDsc a simple use case of the configuration returns the "does not exist at the PowerShell module path nor is it registered as a WMI DSC" error

Problem description
See #120 for a similar error but same cause seemingly eliminated.
My Use case is 'PUSH' so I am running Powershell commands directly on the target to apply the configuration, in an elevated Powershell Prompt.
Following are similar checks requested from the linked prior issue:
PS F:\DSC> Get-DscResource -Module ActiveDirectoryDsc -Name ADServicePrincipalName | Format-List

ImplementationDetail : ScriptBased
ResourceType         : MSFT_ADServicePrincipalName
Name                 : ADServicePrincipalName
FriendlyName         : ADServicePrincipalName
Module               : ActiveDirectoryDsc
ModuleName           : ActiveDirectoryDsc
Version              : 6.2.0
Path                 : C:\Program Files\PowerShell\Modules\ActiveDirectoryDsc\6.2.0\DscResources\MSFT_ADServicePrincipalName\MSFT_ADServicePrincipalName.psm1
ParentPath           : C:\Program Files\PowerShell\Modules\ActiveDirectoryDsc\6.2.0\DscResources\MSFT_ADServicePrincipalName
ImplementedAs        : PowerShell
CompanyName          : DSC Community
Properties           : {ServicePrincipalName, Account, DependsOn, Ensure…}

Other checks:

that the module is installed for all users
the module exists in the PS Path
the pre-requisite Install-WindowsFeature -Name 'RSAT-AD-PowerShell'  was done

Verbose logs
PS F:\DSC> Start-DscConfiguration -Path 'F:\DSC\DoServiceAccountSPNs' -Wait -Verbose -Force
InvalidOperation: The PowerShell DSC resource MSFT_ADServicePrincipalName from module <ActiveDirectoryDsc,6.2.0> does not exist at the PowerShell module path nor is it registered as a WMI DSC resource.

DSC configuration
Configuration DoServiceAccountSPNs
{

    Import-DscResource -ModuleName 'PSDesiredStateConfiguration'
    Import-DscResource -ModuleName PSDscResources
    Import-DscResource -ModuleName ActiveDirectoryDsc

    Node localhost
    {
        ADServicePrincipalName 'BoServiceAccountSPNs'
        {
            ServicePrincipalName = 'MYSPNPREFIX/myserviceaccount.mydomain.com'
            Account = 'myserviceaccount'
        }
    }

}

DoServiceAccountSPNs -OutputPath:"./DoServiceAccountSPNs"

Suggested solution
I am pretty sure this is an issue with my configuration or versions as I'm new to this and it is a new level of dependency hell I haven't experienced before.
Operating system the target node is running
OsName               : Microsoft Windows Server 2022 Standard
OsOperatingSystemSKU : StandardServerEdition
OsArchitecture       : 64-bit
WindowsVersion       : 2009
WindowsBuildLabEx    : 20348.1.amd64fre.fe_release.210507-1500
OsLanguage           : en-US
OsMuiLanguages       : {en-US}

PowerShell version and build the target node is running
PS F:\DSC> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.2.11
PSEdition                      Core
GitCommitId                    7.2.11
OS                             Microsoft Windows 10.0.20348
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

ActiveDirectoryDsc version
Name               Version Path
----               ------- ----
ActiveDirectoryDsc 6.2.0   C:\Program Files\PowerShell\Modules\ActiveDirectoryDsc\6.2.0\ActiveDirectoryDsc.psd1

FWIW I believe the issue was in using Powershell 7 with our setup as reverting to the preinstalled PS seemed to enable DSC.

PowerShell 7 does not include support for DSC resources, must use Windows PowerShelll. In the future with DSCv3 it could be possible, see PS Team talk about it here:

Closing this as this is not something we can resolve in this repository.


Download process of the Ubuntu user-mode image will keep starting over after the download failed on slow connection

This is seriously not a big problem, because I could still bring my laptop to a place with a strong and reliable wifi, then download the image there..
My connection speed (during the cmd give me the download error) keeps fluctuating between 700kb/s and 1.5mb/s.. I know it's not fast, but it never stop all together.. usually with that connection speed and consistency, I manage to download a very large file (up to 16gb, etc. games ISO) if I leave my laptop overnight to do the download..
I wonder if there's an option where I could adjust the default setting for the request timeout before it gives me the "download failed  error"..
and one more thing, why it doesn't resume the download from where it stop previously..

Microsoft Windows [Version 10.0.15025]

Our install story is something we will be looking at closely in a future release.  For now this behavior is by-design.

The new mechanism is to install distributions via the Windows Store, closing this out.


add option to enable or disable k3s local-storage controller

@mnbro  Thank you for this. Please explain the reasoning behind this proposed change. It may seem obvious, but it's not for me, thanks! 🙏

@mnbro Thanks for adding context.
So when local storage is enabled, you won't need Longhorn to use it, correct?
But what will it use? I do not think Hetzner CSI support this. Or is it host path?
I would like to understand the exact use case, and what will be using that. Also you have to understand that our nodes use a specific partitioning scheme, with limit spaces for some directories and read only for others, so important to know where the data will be stored.
The only R-W directory that is not part of a snapshot is var/, important that it uses that. I do not see any config pointing to that in this PR, unless I missed it.

@kube-hetzner/core  FYI my above recommendation. Feedback welcome. Also more on the context explained here: https://chat.openai.com/share/2e9050f1-2a75-4293-86d5-bef232fa4132

Ok I see, thanks for the clarification, will merge tonight.

@mnbro Isn't openebs-local-pv with it's variety of types a better option to use?

openebs-local-pv hostpath seems identical to rancher local-path-provisioner. I'm fine with the option to enable the rancher's implementation.
openebs also offer zfs, lvm, rawfile and block local-pvs as well as using any pvc to maki it an RWX with nfs server, in case someone needs this info

@mnbro Thanks for your contribution and patience. This was just released in v2.10.0  🙏


Use the right flags when creating images (#328)

Test was querying for supported images with CL_MEM_WRITE_ONLY flag, but
always used CL_MEM_READ_ONLY to create images.
Fixes issue #328
Signed-off-by: Radek Szymanski<EMAIL_ADDRESS>Signed-off-by: James Morrissey<EMAIL_ADDRESS>

This PR now needs rebasing.


Disabled options in select form field

Summary
Hi,
as far as I can see (please correct me if I'm wrong), there is no way to disable options in the select form field (like they are displayed but cannot be selected) with Twill v2.5.2.
Describe the solution you'd like
Twill's select component VSelect uses vue select. Vue Select v3.3+ has the prop selectable that determines if an option is selectable or not. Please update vue select to the given version or provide another solution to disable options in the select form field.
Thank you!

Hi @hb-monah thanks for reporting this.
The work of updating to v3 has been started here: https://github.com/area17/twill/pull/674. I believe it will be picked up as part of the Twill 3.x effort.
If you feel comfortable with Vue.js and want to explore this on your end, you can have a look at VSelect.vue, which is Twill's wrapper component for vue-select.


unable to install docker ce on windows 10 pro

installed docker-ce by using choco , it is downloaded
PS C:\Windows\system32> choco install docker-for-windows -y
Chocolatey v0.10.11
Installing the following packages:
docker-for-windows
By installing you accept licenses for the packages.
Progress: Downloading docker-for-windows <IP_ADDRESS>07... 100%
docker-for-windows v<IP_ADDRESS>07 [Approved]
docker-for-windows package files install completed. Performing other installation steps.
Downloading docker-for-windows
from 'https://download.docker.com/win/stable/19507/Docker for Windows Installer.exe'
Progress: 100% - Completed download of C:\Users\shiva\AppData\Local\Temp\chocolatey\docker-for-windows\<IP_ADDRESS>07\Docker for Windows Installer.exe (521.01 MB).
Download of Docker for Windows Installer.exe (521.01 MB) completed.
Hashes match.
Installing docker-for-windows...
[23:13:22.443] [InstallWorkflow] Pre-requisite failed: Docker for Windows requires Windows 10 Pro or Enterprise version 14393, or Windows server 2016 RTM to run
docker-for-windows has been installed.
Only an exit code of non-zero will fail the package by default. Set
--failonstderr if you want error messages to also fail a script. See
choco -h for details.
The install of docker-for-windows was successful.
Software installed as 'EXE', install location is likely default.
Chocolatey installed 1/1 packages.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
but when i try to  run installer  it is giving following error
i frustrated , this is my third attempt , i tried all versions of docker ce editions
iam using windows 10 pro version
Docker for Windows requires Windows 10 Pro or Enterprise version 14393, or Windows server 2016 RTM to run

Hi Hari,
Reason No:1
To run Docker, your machine must have a 64-bit operating system running Windows 7 or higher.
Additionally, you must make sure that virtualization is enabled on your machine.
Reason No:2
Please install docker tool box
Docker Toolbox automatically creates a Linux VM on VirtualBox that hosts Docker on your Windows system
go to below link
https://docs.docker.com/toolbox/toolbox_install_windows/
click on download next == go for default steps
Thanks
Ravi

Resolution is uninstall VmWare/Virtual box before you use Docker


Image Generations v1 misinterprets POST requests as GET

Greetings.
In my NextJS project, the code from the tutorials and snippets in the documentation for Image Generations v1 will only respond with the following json data error:
{
  "error": {
    "code": null,
    "message": "Not allowed to GET on /v1/images/generations. (HINT: Perhaps you meant to use a different HTTP method?)",
    "param": null,
    "type": "invalid_request_error"
  }
}

This comes despite the fact that it was obtained using a POST request and not a GET request like is being suggested. This should be handled by the configured openAiApi object in the documentation's code. I've pasted it below so it can be reproduced:
const onSubmit = async (e) => {
   e.preventDefault();

   // instantiate openAI configuration
   const OPENAI_API_TOKEN = process.env.OPENAI_API_TOKEN;
   const configuration = new Configuration({
     apiKey: OPENAI_API_TOKEN,
   });
   const openai = new OpenAIApi(configuration);

   const response = await openai.createImage(
     "Adorable dog"
   );
}

But to really be sure before raising an issue on GH, I investigated by writing a plain fetch request and setting the POST http method manually:
    try {
      const response = await fetch(
        "https://api.openai.com/v1/images/generations",
        {
          method: "POST",
          headers: {
            "Content-Type": "application/json",
            Authorization: `Bearer ${OPENAI_API_TOKEN}`,
          },
          body: JSON.stringify({
            prompt: promptValue,
            n: 1,
            size: "1024x1024",
          }),
        }
      );
      console.log(response);
    } catch (err) {
      if (err.response) {
        console.log(err.response.status);
        console.log(err.response.data);
      } else {
        console.log(err.message);
      }
    }

This manually constructed POST request above fails to produce anything other than the same json error from before, complaining of some imaginary GET. I feel as though I am being gaslit by what is otherwise an awesome API to use. There is no GET request anywhere here, what is going wrong to cause this?
And yes, I am aware that OpenAI rejects rated-R generated content so rest assured that promptValue is as vanilla as it gets.

After hours of searching I have determined the cause of this issue to be an issue with the CORS origin policy.
If anyone stumbles upon this issue in using OpenAI images with NextJS, the CORS origin policy must be circumvented by establishing your own API proxy.
The image endpoints won't work unless you configure an API router through which to call into the OpenAI endpoint with a same-origin header. Following the NextJS docs here fixes the issue:
https://nextjs.org/docs/pages/building-your-application/routing/api-routes


Improve custom slot docs

Proposed changes:

Clarify how custom slot types should be defined and referred to
closes https://github.com/RasaHQ/rasa/issues/6692

Status (please check what you already did):

[ ] added some tests for the functionality
[x] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

The automatic review requests happened because I based it on the wrong branch at first (I believe). Please rerequest if I'm wrong.


feat: Add dialog schema validation to BeginDialog

Description
Add dialog schema validation to BeginDialog
Task Item
refs #5821

Coverage increased (+0.01%) to 52.783% when pulling bd8d1c4e29afbf32d65f67da33b707e626954b9e on feat/dialog-schema-validation into c68205a94169b6693423771c71c5dbba3a619d80 on main.


getItem on android after delete app data is lost

I use setItem to storage value on device and delete app after delete app i reinstall this app and use getItem to get data from storage but data is lost on Android but IOS is work. anyone can help, i don't kwon what's wrong on my code. Thanks.
package version
"react-native-sensitive-info": "^6.0.0-alpha.9",
"react": "16.13.1",
"react-native": "0.63.4",
my code
import SInfo from 'react-native-sensitive-info';
  const set = async () => {
      try {
        const val = await SInfo.setItem('key1', 'value1', {
          sharedPreferencesName: 'mySharedPrefs',
          keychainService: 'myKeychain',
        });

        console.log('set>>>>', val)
      } catch (error) {
        throw error
      }
    }

    const get = async () => {
      try {
        const val = await SInfo.getItem('key1', {
          sharedPreferencesName: 'mySharedPrefs',
          keychainService: 'myKeychain'
        });
        console.log('get>>>>', val)
      } catch (error) {
        throw error
      }
    }

`

@freedomzzzii hello, maybe is because Android stores data on app's cache and when you delete it Android clears every user data/cache from that app. On the other hand, iOS stores it into keychain which is saved separated from the app data.

@freedomzzzii hello, maybe is because Android stores data on app's cache and when you delete it Android clears every user data/cache from that app. On the other hand, iOS stores it into keychain which is saved separated from the app data.


[Refine] downloader: improve chunk writing and decompression

Introduction
This PR refines the implementation of downloader decompressing and saving data chunk.
Test result
In my local setup, with compression enabled, the time cost of whole ota update reduce from 1088 down to 990, considering my PC uses nvme and test is done with local prepared ota image, I think the performance in the real environment should also be improved in some extend.
related issue report
https://tier4.atlassian.net/browse/T4PB-25078, which is handled in https://github.com/tier4/ota-client/pull/190.

This PR only changes downloader.py, so It is possible to back-port this PR to v3.2.x.

@Bodong-Yang
This PR improves 9% on your environment and that environment is low I/O usage. So why do you think

the improvement will be significant in real environment.

On the real environment, IO usage is higher than your environment one, and on the high IO usage environment, decompression time can be hided by the IO usage.

@Bodong-Yang (This PR itself is OK) This PR improves 9% on your environment and that environment is low I/O usage. So why do you think

the improvement will be significant in real environment.

On the real environment, IO usage is higher than your environment one, and on the high IO usage environment, decompression time can be hided by the IO usage.

My environment is I/O heavy because there is very little diff between my VM image and OTA image(the otaclient will have to download 7GB even with compression enabled, basically downloading the whole image).
But anyway that is only my guess, the test in real environment is still needed.

( If it is possible, we can backport this PR to v3.2.0, and prepare a image for x1 team to test.

@obi-t4 I remember that we have handled similar issue(https://tier4.atlassian.net/browse/T4PB-25078) for v3.2.2, and this issue also existed in v3.2.0(download thread num is too small(3), the fix(#190) is to enlarge download thread to 7), I think that is the main cause.
But anyway this PR also improves the performance, so it is better to apply it also.

I remember that we have handled similar issue(https://tier4.atlassian.net/browse/T4PB-25078) for v3.2.2, and this issue also existed in v3.2.0(download thread num is too small(3), the fix(https://github.com/tier4/ota-client/pull/190) is to enlarge download thread to 7), I think that is the main cause.

Yes, this issue has been fixed by changing number of thread to 7 #190

But anyway this PR also improves the performance, so it is better to apply it also.

Yes, I think so, I'm waiting your:

the test in real environment is still needed.

PR itself is OK since this can reduce usage of memory I think.

The improvement is confirmed on v3.2.3!
Test setup:

total_regular_files:<PHONE_NUMBER>4
processed_files_download:<PHONE_NUMBER>9

Without this PR, time cost is 1008 seconds
with this PR, time cost is 980 seconds, the memory usage is also slightly reduced(10MB less than 1)

I will merge this PR now.


Chainable response methods

What: Fixes bugs #108 and #114.

Why: To make various Response methods chainable.

How: Return this from a bunch of Response methods.

@dozenne, I appreciate the pull request and the time you took to fix issues #108 and #114 in it.
If you would, could you please add new tests cases to verify the new code / functionality that was added to response.ts.
It would help verify the code works like we expecte and it will protect us from any regression in the future.

@jameswlane @dozenne wow! Came looking for this and here it is...
Would love if this can be merged!

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Added player page

Added support for Player

Nice! 🤟

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: sandeep-vedam:x: Sandeep Kumar VedamSandeep Kumar Vedam 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.


cues flicker

Calling this method when there is an active, displayed cue will cause said cue to flicker.
This document does not provide any clues on how to fix this issue.

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

ID: f7d1df21-773b-7667-c465-30cca9bfbab3
Version Independent ID: 7d56d10a-71e9-4a7c-e680-dad3ad81728b
Content: TimedMetadataTrack.AddCue(IMediaCue) Method (Windows.Media.Core) - Windows UWP applications
Content Source: https://cpubwin.visualstudio.com/DefaultCollection/windows-uwp/_git/winrt-api-build?path=%2fwinrt-api-build%2fwindows.media.core.timedmetadatatrack.yml&version=GBlive&_a=contents
Product: uwp
Git Login: drewbatgit
Microsoft Alias: drewbat

Thanks for taking the time to let us know about this and I sincerely apologize for the delayed response. Though the scope of our feedback channel here on GitHub covers specific documentation fixes, I can help redirect you to the right support channel to get an answer to your question. The community of experts and Microsoft Engineers over at Microsoft Q&A offer timely answers to a multitude of technical questions surrounding windows-uwp.
If you do create a thread over at Microsoft Q&A, it would be fantastic if you could share that link here so I can track the progress and potentially incorporate the technical details into our documentation. Though I'm marking this Issue as closed now, please treat this thread as an open thread for follow-ups. Thanks!


(mixx) Entity Too Large Exception

Looks like the mixx package, which is an embedded package has grown too large in order to be pushed to chocolatey.org:

Attempting to push mixxx.2.2.0.nupkg to https://push.chocolatey.org Failed to process request. 'Request Entity Too Large'.  The remote server returned an error: (413) Request Entity Too Large..

Is there a precedence for what to do in this case?  Should this no longer be an embedded package?
@majkinetor @AdmiringWorm

Well, since it has grown too large. We really don't have any other option than to change it back to a non-embedded package 🙁

We can make 2 packages by arch too.
But as far as I can see v2.2.0 combined is 220MB and limit is defined as 300 so you either silently reduced the maximum size or there is a bug. It look like core Chocolatey guys really need to take care of this recent embedding issues (as nobody else can). As it is, its totally demoralizing for this repository, my personal interest is dropping fast.


[Kernel] Workflow to generate unidoc

Which Delta project/connector is this regarding?

[ ] Spark
[ ] Standalone
[ ] Flink
[x] Kernel
[ ] Other (Doc)

Description

Resolves #2209
this PR will make sure all the component apis are documented.
Documentation will be generated for all changes
How was this patch tested?
commit triggered workflow tests

This is great! thank you for the PR.
Looks like the workflow is failing currently. Could you please check that is because we have a failure on the master branch?

The unidoc generation workflow is failing in master branch because of package import issues. It's not able to find the packaging structure. Is it related to some configuration in build.sbt file ?


After using the generic visual script search, reset the generic searc…

After using the generic visual script search, reset the generic search mode variable to false.
How to reproduce?:

press ctrl - f to trigger search mode
cancel search mode
pulling from any output node triggers generic search

Expected:

press ctrl - f to trigger search mode
cancel search mode
pulling from any output node has autocomplete

Thanks!


Implement IEquatable in Bool32

This is a follow-up to a suggestion by @Khitiara in PR #1587, to implement IEquatable<Bool32>, IEquatable<bool> and IEquatable<uint> in Bool32.
As always, let me know if I missed anything. :)

Should also override GetHashCode by convention when overriding Equals - that should pretty easy though you can just forward it to Value


different urls get the same filename

The filename is based only on the scheme and the host and not on the path and the query.
So, for example, if I want to take a screenshot of https://michenriksen.com/blog/aquatone-now-in-go/ and https://michenriksen.com/blog/drawio-for-threat-modeling/ with aquatone, the result is the same filename https__michenriksen_com that distorts the report.

Can be closed as it has been fixed on b77953e


Fix packaging bash scripts

Motivation and Context

Running the packaging bash scripts in the repo will result in the following error:

This is caused by un-escaped characters in the build options.
Description
Fix the issue by escaping the characters in the build options.

Contribution Checklist

[ ] The code builds clean without any errors or warnings
[ ] The PR follows the Contribution Guidelines and the pre-submission formatting script raises no violations
[ ] All unit tests pass, and I have added new tests where possible
[ ] I didn't break anyone :smile:

was this actually tested on Linux/WSL?
It still gives the error :(
/chat-copilot/scripts/deploy$ ./package-webapi.sh
Building backend executables...
Build configuration: Release
MSBuild version 17.7.3+8ec440e68 for .NET
MSBUILD : error MSB1008: Only one project can be specified.
    Full command line: '/usr/share/dotnet/sdk/7.0.402/MSBuild.dll -maxcpucount -verbosity:m -target:Restore --property:_IsPublishing=true -property:PublishDir=/home/xxxxxxxx/repo/xxxxxxxx/chat-copilot/scripts/deploy/publish -property:_CommandLineDefinedOutputPath=true -property:SelfContained=True -property:_CommandLineDefinedSelfContained=true -property:RuntimeIdentifier=linux-x64 -property:_CommandLineDefinedRuntimeIdentifier=true -property:Configuration=Release /home/xxxxxxxx/repo/xxxxxxxx/chat-copilot/scripts/deploy/../../webapi/CopilotChatWebApi.csproj //p:AssemblyVersion=0.0.0 //p:FileVersion=0.0.0 //p:InformationalVersion= -distributedlogger:Microsoft.DotNet.Tools.MSBuild.MSBuildLogger,/usr/share/dotnet/sdk/7.0.402/dotnet.dll*Microsoft.DotNet.Tools.MSBuild.MSBuildForwardingLogger,/usr/share/dotnet/sdk/7.0.402/dotnet.dll'
  Switches appended by response files:
Switch: //p:AssemblyVersion=0.0.0

For switch syntax, type "MSBuild -help"


support endpoint test

ava has no built-in endpoint test capability.

@ziofat Are you talking about adding endpoint testing to the boilerplate? If yes, I would say it is more of an implementation detail - you can install axios or any other library and do the same testing which you are doing right now - or am I wrong in my understanding?

The current test case is totally fake. It should match the current routes like "/hello", which makes the boilerplate complete and self-consistent.

@ziofat Got it! I will add the real test cases in the next release.


release to the cheeseshop

it'd be great to tag releases and put them up on pypi

Hi @paultag , Thanks for your suggestion, I plan to do that asap.

Created v0.1.2 version tag and pushed package to pypi

You rock, thanks!
On Mon, Mar 2, 2015 at 1:44 PM, Ziya SARIKAYA<EMAIL_ADDRESS>wrote:

Created v0.1.2 version tag and pushed package to pypi
—
Reply to this email directly or view it on GitHub
https://github.com/ziyasal/pyley/issues/7#issuecomment-76776383.

--
:wq


[ENH, MRG] Use the new Dipy transform_points function for warping intracranial contacts

In working on https://github.com/mne-tools/mne-python/pull/11567, I realized that the transform points was out on a stable release of dipy. This is much cleaner than our current version because you don't have to worry about bridged channels being lost. Additionally, I split the electrode-contact-image-making function out so that you could do it the old way (actually a lot neater this way, reuses other API) but also, I have found in my analysis that those images can be useful since the contact locations don't contain information about size.

Failures are unrelated, okay to merge by me

The failures are unrelated and looks good to me now.

Marking for auto-merge when green, let's merge main into this branch once #11581 lands and then we'll get this in


Remove non-existant dependency on configure-step

FYI @VladimirIvan: the dependency does not exist as this file is generated during the configure-step. Removing it reduces warnings during build time.

ok


This is a security research, please do not approve, thank you.  ehjwyw

This is a security research, please do not approve, thank you.  ehjwyw

Main branch dependencies


Allow telemetry 0.4?

Hi!
Is there a particular reason why telemetry 1.0 is required? AFAIK there were no API changes compared to 0.4.
The reason I'm asking is because we're currently in a weird transition moment, where many packages still depend on telemetry 0.4 without allowing 1.0, so if some packages (like this one) don't allow 0.4, we're forced to specify 1.0 with an override. In my project this succeeds on mix deps.get dependency resolution, but unfortunately, other tasks like mix test etc fail to start (I'm not exactly sure why but other people may also be hitting this problem).
I think it could be good to specify ~> 0.4 or ~> 1.0, at least for some time

@michallepicki just for some context, rebar3 doesn't allow projects to specify dependencies using the or syntax, so it wasn't possible to allow both versions. I agree, if folks need to use Telemetry 0.4, they can still use Poller 0.4 or 0.5. Thanks!

Thanks for clarification!


fix for issue #1021 Listener remove for onChange, onUpdate and onActiveChange(SteamVR_Action_Boolean ).

Added listener remove for onChange, onUpdate and onActiveChange.
fix for issue #1021

Thanks, there were a few more in other scripts that I've fixed. This will be in the next release.


Ecommerce: when checkout completes, delete only the basket that was checked out

Currently when a user checks out their basket, we defer deletion of the basket under later - this could be a) when the browser navigates back to the site or b) when the payment processor sends us an API request. Right now we just delete whichever basket the user has, but that may be a new basket, particularly if the API call is deferred, and we don't want to inadvertently stomp on that state.
I'd propose that we adjust the callback and api urls to accept a basket id as part of the url path. Then we selectively Basket.objects.filter(user=order.purchaser, id=basket_id) and delete that one. Note that we want to filter both on the basket id and user.

This is complicated somewhat by the fact that the Basket model has a one-to-one relationship with User, so there's a constraint there that means the user's only ever going to have one Basket. I think the only way you'd really be able to step on the state like that is in one of two places:

You get an out-of-band call from CyberSource due to a deferred transaction (i.e. it lands in the Review limbo state and someone has to hit a button in the CS console). In this case, it can check for this (either by looking at the order status or by maybe even using the Transaction table once it gets the type field in #467) and then just not delete the basket at all. There wouldn't be a valid one anyway and there wouldn't necessarily be an active user at that point either, so just leave the basket alone. (This is probably the thing to do in this case anyway.)
Someone goes through the checkout process, then goes back through to the app and enrolls in another course while they're still in CyberSource. In this case, they'd have a new basket so when they finish up the CyberSource part of it, the new course they'd added to the cart would be removed (or, they cancel or their card is declined or something and they get punted back to the cart with something totally different in their cart). I tested this on RC successfully - enrolled in one course, hit Place Order, then opened a new window back to RC and enrolled in something different, then cancelled in CyberSource, and got back a cart with only the 2nd thing in it. In this instance, it might be better to clear out the basket before sending to CyberSource and then, if the user gets redirected back, reconstruct the basket they had so they're not missing an enrollment they thought they were getting. (The UI should handle multiple cart items even though we don't necessarily give users a way to do that.)

Alternatively, I can redefine the relationship between Basket and User so it's not 1-to-1, and then put in some logic/flags to enforce one live basket per user/etc. Thoughts on this?

Figured out how to do this - PR open for this now. The PR implements the out-of-band stuff and then adds in the check to not clear the cart if the payment is successful but the cart is now somehow different (ostensibly the "I started over on MITx Online while still checking out elsewhere" flow).


TabbedPages render problem

I've setup Ooui WSAM with Existing Xamarin Forms App. It works but my MainPage is a TabbedPage but Ooui renders both pages at the same time on top of each other and there are no Nav Controls.
The pages display 'Welcome to Dashboard' and 'Welcome to Schedules'. But when when rendered at the same time following results are coming out.

Hey ! I have the same issue with NavigationPage #168
Any idea @limefrogyank ?

Now that the pull request is merged, the NavigationPage should work...

@limefrogyank I have always the same issue
Do I have to do something special unlike the Android app ?
My Navigation works fine on Android and not on the web if I take the same code


Add Elgato Eve's History capability

Adding Elgato Eve's history capability would be great. https://github.com/simont77/fakegato-history did the same for the Homebridge https://github.com/nfarina/homebridge.

@dezdeepblue It is not quite obvious from repository you mentioned what a "history" feature is. Could you elaborate that?

I'm not sure if you saw the functionality of Elgato Eve's app in regard to some of its sensors. For example check https://www.evehome.com/en/eve-degree. There are screenshots of the app on the page. Having their HomeKit accessories in the Eve app, not only it shows the current state of the sensor (Temperature, Humidity, etc.) it shows the historical data from each parameter in a graph.
I'm not sure if it could be achieved just by a specific characteristic, but by checking the https://github.com/simont77/fakegato-history it could be seen that it seems to be more than just a characteristic.
I mean it isn't just an app-side feature(As I checked with current HomeKit temperature sensor example) and the HomeKit device needs to log its data (SPIFFS, or on the cloud, Gdrive, Dropbox, etc.) and provide it somehow to the app.
I thought the Fakegato-History could help, but I don't have enough programming skills to contribute and don't know where to start.

I am also very interested in having historical data of my sensors. Don't know if Homekit provides this kind of functionality. It would be great if it does.
Right now, I have set up a function that sends data to ThingSpeak server every 10 minutes and I use a different app or a browser to view the data.
Here is the code I'm using to send temp & humidity values:
Initializing values:
#define	USE_THINGSPEAK 1
#define WEB_SERVER "api.thingspeak.com"
#define API_KEY  "XXXXXXXXXXXXXXXXXX" //Your provided key goes here
#define FIELD1 "field1="
#define FIELD2 "field2="
#define WEB_PORT "80"
#define WEB_PATH "/update?api_key="
#define THINGSPEAK_INTERVAL 600000 //interval every 10 minutes. Change it to your liking

volatile float old_humidity_value = 0.0, old_temperature_value = 0.0 //these values must be updated by another function not shown here. Normally, that function is the one reading sensor data from your sensors.

ETSTimer things_timer;

The main ThingSpeak function:
void call_things_process()
{

	int successes = 0, failures = 0;
    printf("HTTP get task starting...\r\n");

    while(1) {

        const struct addrinfo hints = {
            .ai_family = AF_UNSPEC,
            .ai_socktype = SOCK_STREAM,
        };
        struct addrinfo *res;

        printf("Running DNS lookup for %s...\r\n", WEB_SERVER);
        int err = getaddrinfo(WEB_SERVER, WEB_PORT, &hints, &res);

        if (err != 0 || res == NULL) {
            printf("DNS lookup failed err=%d res=%p\r\n", err, res);
            if(res)
            freeaddrinfo(res);
			failures++;
			break;
        }

#if LWIP_IPV6
        {
            struct netif *netif = sdk_system_get_netif(0);
            int i;
            for (i = 0; i < LWIP_IPV6_NUM_ADDRESSES; i++) {
                printf("  ip6 %d state %x\n", i, netif_ip6_addr_state(netif, i));
                if (!ip6_addr_isinvalid(netif_ip6_addr_state(netif, i)))
                    printf("  ip6 addr %d = %s\n", i, ip6addr_ntoa(netif_ip6_addr(netif, i)));
            }
        }
#endif

        struct sockaddr *sa = res->ai_addr;
        if (sa->sa_family == AF_INET) {
            printf("DNS lookup succeeded. IP=%s\r\n", inet_ntoa(((struct sockaddr_in *)sa)->sin_addr));
        }
#if LWIP_IPV6
        if (sa->sa_family == AF_INET6) {
            printf("DNS lookup succeeded. IP=%s\r\n", inet6_ntoa(((struct sockaddr_in6 *)sa)->sin6_addr));
        }
#endif

        int s = socket(res->ai_family, res->ai_socktype, 0);
        if(s < 0) {
            printf("... Failed to allocate socket.\r\n");
            freeaddrinfo(res);
           failures++;
			break;
        }

        printf("... allocated socket\r\n");

        if(connect(s, res->ai_addr, res->ai_addrlen) != 0) {
            close(s);
            freeaddrinfo(res);
            printf("... socket connect failed.\r\n");
			failures++;
			break;
        }

        printf("... connected\r\n");
        freeaddrinfo(res);

		char temp2[10];
		snprintf(temp2, sizeof(temp2),"%2.2f", old_temperature_value );
		printf("%s \n",temp2);
		printf(temp2);

		char hum1[6];
		snprintf(hum1,sizeof(hum1), "%2.2f", old_humidity_value );
		printf("%s \n",hum1 );

		char req[300]="GET " WEB_PATH API_KEY "&" FIELD1;
		strncat(req,temp2,10);
		 strncat(req,"&",2);
		 strncat(req,FIELD2,20);
		 strncat(req,hum1,6);
		 strncat(req," HTTP/1.1\r\nHost: "WEB_SERVER"\r\nUser-Agent: esp-open-rtos/0.1 esp8266\r\nConnection: close\r\n\r\n",250);

		printf("%s \n",req );

		if (old_temperature_value ==0)
		{
			break;
		}

		 printf("%s \n",req );

		if (write(s, req, strlen(req)) < 0) {
            printf("... socket send failed\r\n");
            close(s);
            failures++;
			break;
        }
        printf("... socket send success\r\n");

        static char recv_buf[128];
        int r;
        do {
            bzero(recv_buf, 128);
            r = read(s, recv_buf, 127);
            if(r > 0) {
                printf("%s", recv_buf);
            }
        } while(r > 0);

        printf("... done reading from socket. Last read return=%d errno=%d\r\n", r, errno);
        close(s);
		printf("successes = %d failures = %d\r\n", successes, failures);
        printf("\r\nEnding!\r\n");

		break;
    }
}

The following code should go on your on_wifi_ready function
void on_wifi_ready() {
other code

sdk_os_timer_setfn(&things_timer, call_things_process, NULL);
//sdk_os_timer_disarm(&things_timer);
sdk_os_timer_arm(&things_timer, THINGSPEAK_INTERVAL, 1);
}

If you try the code, I would really appreciate some feedback. It normally runs fine. However, If the accessory is not paired first, then it may fail to pair! That's why initializing the  things_timer may need to take place on a later stage after accessory has paired.

From fakegato-history repository I see that they use custom characteristics and base64 serialized data:
https://github.com/simont77/fakegato-history/blob/master/fakegato-history.js#L84-L137
That could work but surely it will work only with Elgato application.

I'm not sure how the Fakegato-history on Homebridge works, either the sensor only works on the Eve app or someway it is also working with the Home app. I need to re-setup my RPi and Homebridge to check that.
However, I think it could be added to a multiple-sensor device to make it work with both apps, just like what @peros550 did in https://github.com/peros550/esp-homekit-multiple-sensors. Isn't it @peros550 ?

I have several homebridge plugins that use fakegato-history, and for example a temperature sensor works like this.  In the home app, it appears as just a regular temperature sensor, but in the Eve app it also shows historical graphs of the temperature, which is very cool.
In the implementation you create a couple of additional characteristics that are used to communicate that historical data on request.  Also you will need to store/cache on the esp8266 the historical records until they are asked for by the app.   In homebridge, we are using either the local file system or google drive to cache the records until requested.  On the esp8266 this would be a major consideration, as you are likely to be updating the history cache every 10 minutes.  In memory memory may not be a good user experience as you would loose the records during a device restart, and writing to the local flash storage may not be desired.

@maximkulkin  This is why homekit data needs to be implemented 😄
Yes, Elgato Eve using custom characteristics and a tons of HomeKit data type. Also the accessory must support timekeeping because every data entry contains the current time (current time is calculated, not just a timestamp)!
I've all of these custom characteristics implemented to esp-homekit and also i'm still reverse-engineering the custom characteristics for Eve products 😄
At the moment using TLV8 data type, the History is showing up, but it definitely needs HomeKit data to store all the History.


X-Pack plugin license problems

The Login to Kibana fails because of this message:

Login is currently disabled because the license could not be determined. Please check that
Elasticsearch has the X-Pack plugin installed and is reachable, then refresh this page.

I googled a bit for it and it seems https://github.com/elastic/kibana-docker is abandoned and the docker images by Elastic Inc. should be used now.

@kfrohwein thank you for the issue we did discuss it internal and we will remove kibana from the sulu-docker to keep the things simple. And serve elasticsearch as an optional service.

Thanks for reporting! I think this is not relevant anymore after we restructured the project in https://github.com/sulu/sulu-docker/pull/51

Thanks for reporting! I think this is not relevant anymore after we restructured the project in https://github.com/sulu/sulu-docker/pull/51


Revert state manager

Breaking change

Proposed change

Revert of StateManager storing HassStates iso EntityState
Type of change

[ ] Dependency upgrade
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (which adds functionality to an existing integration)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ X] Code quality improvements to existing code or addition of tests

Additional information

This PR fixes or closes issue: fixes #
This PR is related to issue:
Link to documentation pull request:

Checklist

[ ] The code change is tested and works locally.
[ ] Local tests pass. Your PR cannot be merged unless tests pass
[ ] There is no commented out code in this PR.
[ ] I have followed the [development checklist][dev-checklist]
[ ] The code compiles without warnings (code quality chek)
[ ] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated for www.home-assistant.io

Codecov Report

Merging #415 (d17f971) into dev (822424c) will decrease coverage by 0.13%.
The diff coverage is 82.14%.

@@            Coverage Diff             @@
##              dev     #415      +/-   ##
==========================================
- Coverage   54.51%   54.37%   -0.14%
==========================================
  Files          83       82       -1
  Lines        4619     4583      -36
  Branches      711      707       -4
==========================================
- Hits         2518     2492      -26
+ Misses       1874     1865       -9
+ Partials      227      226       -1

Flag
Coverage Δ

unittests
54.37% <82.14%> (-0.14%)
:arrow_down:

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

Impacted Files
Coverage Δ

src/Fakes/NetDaemon.Fakes/DaemonHostTestBase.cs
74.40% <50.00%> (-2.36%)
:arrow_down:

...rc/Daemon/NetDaemon.Daemon/Daemon/NetDaemonHost.cs
53.26% <76.47%> (+0.28%)
:arrow_up:

...n/NetDaemon.Daemon/Daemon/EntityStateManagement.cs
86.27% <100.00%> (+2.27%)
:arrow_up:

...emon/NetDaemon.Daemon/Mapping/EntityStateMapper.cs
77.14% <100.00%> (ø)

...pp/NetDaemon.App/Common/Reactive/NetDaemonRxApp.cs
84.25% <0.00%> (+1.70%)
:arrow_up:

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 822424c...d17f971. Read the comment docs.


Cannot Scroll on React-Native-Web IOS Device

Hello,
You cannot scroll vertically on iOS browser but it is possible on the web.
Using the React-Native-Web version! Thank you.

Hello,
You cannot scroll vertically on iOS browser but it is possible on the web.
Using the React-Native-Web version! Thank you.

My local test did not find the problem you said, the ios version is 10.3+, the specific description of your version, I updated the example you can run down to see if you have the same problem


Fix latest tweet image

Checks if latest tweet has an attachment and only then show the latest attachment

@ckpringle this PR should fix #227. The latest tweet should show the correct image according to how it is on Twitter.


Recovery  sound  error

I run it mac
I get sound image is right

Recovery  sound  error

every recovery sound is nothing , i don't know why

Have you tried to change sound player?We noted that some video player don't reproduce the recoverie sounds.

Thank you.Change to 48 k Hz 24bit is ok.

Hi,i have very old video.Can recovery sound？
[image: image.png]
On Fri, May 22, 2020 at 3:22 PM Antonio Musolino<EMAIL_ADDRESS>wrote:

Closed #1 https://github.com/dsforza96/visual-mic/issues/1.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dsforza96/visual-mic/issues/1#event-3363571001, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AMU5FZIXV4YKGODNDTYIFOTRSYR2LANCNFSM4NBKAKQA
.

Hi,
I don't know exactly what you mean by very old video, but for example its frame rate has to be higher (at least the double) than the sound frequency you want to recover.
If you want a more complete answer you can look at the web page of the original work (http://people.csail.mit.edu/mrub/VisualMic/), in particular in the FAQs section.

Thank you
On Fri, Jun 12, 2020 at 12:21 AM Davide Sforza<EMAIL_ADDRESS>wrote:

Hi,
I don't know exactly what you mean by very old video, but for example its
frame rate has to be higher (at least the double) than the sound frequency
you want to recover.
If you want a more complete answer you can look at the web page of the
original work (http://people.csail.mit.edu/mrub/VisualMic/), in
particular in the FAQs section.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dsforza96/visual-mic/issues/1#issuecomment-642785951,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMU5FZISKPCNEQS472RL4T3RWD77NANCNFSM4NBKAKQA
.


[Issue #81] One of the JSONs for tests is never used

Issue: https://github.com/jboss/tyr/issues/81

@lukasburda thanks


Expand/contract nodes programatically

Please considere this scenario:

Nested list with checkboxes
Keep checkboxes state using extradata prop
After extradata state change keep or give an option to keep child nodes expanded

@TakaKeiji  thx for your notes, I will consider those

How can i do this in my application, I need this feature to implement in my app, please suggest me how can i acheive this. Thanks.

I have the nested list with 3 levels of the data. What i want to do is, when i tap level 1 items, i want to collapse expanded level 1 items.

I am going to use Github issues only for issues


yield operator support?

It's known that currently (ts v3.6.4) yield returns any type.
interface User {
  id: string;
}

function fetchUser(id: string): Promise<User> {
  return Promise.resolve({ id });
}

function* main() {
  const user = yield fetchUser('test'); // user is `any`
}

My question is is it planned to support yield expression return type in upcoming releases or it will return any for the time being?

Section has information to answer your question: https://devblogs.microsoft.com/typescript/announcing-typescript-3-6/#stricter-generators

@AviVahl it gives an error 🙂 Neither Generator<User> nor Generator<Promise<User>> works

The last generic parameter:
interface User {
    id: string;
}

function fetchUser(id: string): Promise<User> {
    return Promise.resolve({ id });
}

function* main(): Generator<unknown, any, User> {
    const user = yield fetchUser('test'); // user is of type: User
}

@AviVahl As user, I should not write this explicitly. I expect language to infer it from the return type of the fetchUser function.

Alright, after going over generators/iterators again, I probably have the correct answer now:
The value set on the user variable is whatever being passed to next(<value>) from the outside (meaning, whoever is using the iterator). This can be auto inferred, as explained in the blog post:
interface User {
    id: string;
}

function fetchUser(id: string): Promise<User> {
    return Promise.resolve({ id });
}

function* main() {
    const user: User = yield fetchUser('test');
}

In the above example, main has an inferred type of Generator<Promise<User>, void, User>, due to explicitly writing User as the expected type.
I believe you are trying to achieve a similar behavior to async/await, which would await the value and infer the type from the Promise:
async function main() {
    const user = await fetchUser('test'); // user is of type: User
}

This is like having a generator where the system (not the user calling main) automatically calls next with the resolved value from the Promise.
A generator is more flexible in that it allows you to provide a different value (with a different type) from outside.
Does this make sense?

Yes, I totally understand the situation and why yield is not supported as people would like it to be. My question to the maintainers in this issue whether they plan to improve yield support or it will be kept as is

"as people would like it to be" and "improve yield support" are both a bit confusing. They did improve yield support rather vastly:
https://www.typescriptlang.org/play/index.html#code/PTAEFsE8HEFMDtYCcCGAXA9k0ALFBnUFeUAS3gDNklYATUGtAVyRLUgAdZQMKAuAFAhQcRKkxIAPPCbgARsgA0ofGiTkA5stXr4GgNoBdAHwCKTeAGM0pDPABUEGAmTosACgCUoAN4DQAaCWdqqgAG4oADZMsPgAYkgY4ADyTGj4pLSwfCpqmkagALygkKSwkfQArAL+gYwsJBHRsQlJqemZsAB0AFYY5O4A5IOeAgC+NcHwoaRoyEVOoq4SXgJToU0Ls8hdiAAeaKukFKDuAIRNXbR2sN5+geFRXU0xoMJ4hCig7Fw8JzLyZC1ALbJC7WAHdz6QZQQbKQY6TRw0CDFBIVCQQaGbzCH7cSw4WCWADWdHGoHK+G490Clxe3HeBCI3043F4uV0GnGAiAA
In the above example link, I see no way for typescript to infer string[] without the developer specifying it explicitly.
The assumption made here that assumes yield behaves like await is wrong, as far as I can see.

function* main() {
  const user = yield fetchUser('test'); // user is `any`
}

I don't see how the type of user can possibly be automatically inferred here, for the same reason it's impossible to infer parameter types from the implementation: the value comes from outside.

So, the final conclusion is: the type after yield return can only be any?

@yoyo837 you'll have to clarify what you mean.
as far as I can see, it is as inferable as one can expect it to be.
The right hand side of the yield acts like a function's return type. it can be inferred from actual values being yielded.
The left hand side acts like a function's parameter type, where you have to specify the type for typescript to give you type checking. That type is automatically mapped to next(), so all is good.

Sorry for my poor English:

you should write:
const result: IModelItem = yield select(state => state.user.Roles)
by writing : IModelItem, you tell typescript the type of argument next(...) accepts when the generator function is used.
See the example link.

It report 'Cannot assign type "unknown" to type "ModelItem"'.

One would need the surrounding code (rest of generator code) and the used tsconfig.json to understand/reproduce what you're seeing.
Feel free to open a new issue if you believe this to be a bug. Follow the template and others might be able to assist. If it's just an "how do I..." question, Stack Overflow is the correct place.

Ok, I first try to resolve it by myself.
Thanks for your time.


Using example app. Error: "Media failed to load"

https://user-images.githubusercontent.com/26365596/152839766-08d6819c-c8fc-4f5e-a071-44b65d2e86b5.MP4

Xcode: 13.2.1 (13C100)
Device: iPhone 11
Device OS version: 15.2.1

Which receiver id are you using? Which device are you casting to?

That was plain android device with cast receiver app:
https://play.google.com/store/apps/details?id=com.softmedia.receiver.castapp&hl=en&gl=US&pli=1
For regular receiver device - everything works fine.


Add version constraints of setuptools

Motivation

Fix CI.
Description of the changes

Same as https://github.com/optuna/optuna/pull/3207.

Dear reviewers, to fix this issue, we have at least two ways:

Add version constraint of setuptools: Optuna's main repo takes this approach. But setuptools is a general package, so this constraint might be removed in the near future.
Use a workaround as https://github.com/optuna/optuna-examples/pull/76/commits/3c937c9a0c581a5074a0b952d526dd8100a51635 by following https://github.com/mpi4py/mpi4py/issues/157#issuecomment-1001022274.


Scripts for Ambiguity calculations

Scripts to perform ambiguity calculations in scalable manner (in particular with MPI).

It was necessary to fix numba=0.48.0 in the environment.yml (see commit https://github.com/structRobustness/analysis/pull/3/commits/938c76c4c5c8ff5668ebf2e901e095fb7986fdb0 for further information).

Scripts completed. Need to fix estimagic dependency issue with pygmo such that CI completes.


Docker installation doesn't work on windows 10 (requires windows 10 pro)

Hi!
I'm trying to install the Docker on my PC, which has windows 10, and the installation fails with the note "one prerequisite is not fulfilled: Docker Desktop requires Windows 10 Pro/Enterprise/Home (18363+)."
Is it possible to make Docker installation work on windows 10, not pro?
I really appreciate any help you can provide,
Lada Pechuk

Hi, it should work on Windows 10 Home (the non pro, non enterprise version): I did successfully install it on my computer that had Windows 10 Home.
That error message just seems to indicate that Docker would like a more up-to-date version of the OS (newer than the version in brackets). If you run Windows Update you should be good to go!
Someone else had a similar problem, see over on stackoverflow.
The installation instructions for Docker on Windows also say Windows 10 Home is ok, provided it's updated enough :)
AFAIK you need windows pro/enterprise if you want to run Windows containers, but Tierpy is a Linux container and as such can be run on Windows 10 Home using Docker with the WSL2 backend.
Let me know if updating fixes the issue!

Hi, great you got it going! This should be straightforward: in the batch processing windows, make sure to use a 'include pattern' that matches your video types :) reading from the text you posted here (thanks for including that) it was '.hdf5', it should work for your Avi videos if you set it to '.avi'.


Move logic for real-time mode (SYSTEM_CLOCK) into Clock itself.

SYSTEM_CLOCK implies animating forward at a 1x multiplier.  Centralize the logic for dealing with coordinating clock settings in Clock itself.  When switching to SYSTEM_CLOCK, other values are immediately updated to be consistent.  When changing other values, e.g. current time or multiplier, SYSTEM_CLOCK is deactivated.
This fixes some inconsistencies in the UI where the logic was not consistent, due to being scattered around.  Specifically, when you dragged the timeline while in realtime mode, you ended up in a hybrid state where the mode was still set to SYSTEM_CLOCK and therefore the label in the UI still said "Today" etc.

I'm getting a test failure for Widgets/Viewer/Viewer updates the clock when the data source changes

Fixed.

One thing I noticed while looking at DataSourceClock is that it blindly copies all values from itself into the Clock instance, but a default-constructed DataSourceClock has undefined values for all settings, which would corrupt the clock I believe.  Now fortunately the CzmlDataSource and KmlDataSource make sure to set all the properties no matter what, otherwise it would wreck everything, but should the getValue be smarter about checking for undefined values and not changing the Clock?

Now fortunately the CzmlDataSource and KmlDataSource make sure to set all the properties no matter what, otherwise it would wreck everything, but should the getValue be smarter about checking for undefined values and not changing the Clock?

We certainly shouldn't put the clock in an invalid state.  Feel free to open another PR with DataSourceClock changes.  That code is really old and used to be specific to CZML, so it probably just evolved outside of its original expected usage.


Re-enable Webpack uglification

More generally, we should restore Scratch's webpack config as much as possible.


[Bugs] Free5gc NRF is waiting for MongoDB indefinitely

Describe the bug
I am using helm to install free5gc-nrf chart. The MongoDB dependency could be instantiated but nrf is waiting for MongoDB forever. But I verified that mongodb is up. So not sure how does this happen.
kubectl get pods

NAME                                   READY   STATUS     RESTARTS   AGE
mongodb-0                              1/1     Running    0          9m14s
nrf-free5gc-nrf-nrf-79d7d9b788-cmghx   0/1     Init:0/1   0          9m14s

If I checked the log of wait-mongo container of nrf-free5gc-nrf-nrf-79d7d9b788-cmghx
kubectl logs nrf-free5gc-nrf-nrf-79d7d9b788-cmghx -c wait-mongo
nc: bad address 'mongodb:27017'
waiting for the MongoDB
nc: bad address 'mongodb:27017'
waiting for the MongoDB
....

Meanwhile I checked the log of MongoDB-0 pod
kubectl logs mongodb-0
mongodb 04:34:33.79
mongodb 04:34:33.80 Welcome to the Bitnami mongodb container
mongodb 04:34:33.80 Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-mongodb
mongodb 04:34:33.80 Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-mongodb/issues
mongodb 04:34:33.80
mongodb 04:34:33.80 INFO  ==> ** Starting MongoDB setup **
mongodb 04:34:33.82 INFO  ==> Validating settings in MONGODB_* env vars...
mongodb 04:34:33.82 WARN  ==> You set the environment variable ALLOW_EMPTY_PASSWORD=yes. For safety reasons, do not use this flag in a production environment.
mongodb 04:34:33.84 INFO  ==> Initializing MongoDB...
mongodb 04:34:33.86 INFO  ==> Deploying MongoDB with persisted data...
mongodb 04:34:33.87 INFO  ==> ** MongoDB setup finished! **

mongodb 04:34:33.89 INFO  ==> ** Starting MongoDB **

{"t":{"$date":"2023-03-18T04:34:33.934+00:00"},"s":"I",  "c":"CONTROL",  "id":20698,   "ctx":"main","msg":"***** SERVER RESTARTED *****"}
{"t":{"$date":"2023-03-18T04:34:33.939+00:00"},"s":"I",  "c":"CONTROL",  "id":23285,   "ctx":"main","msg":"Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'"}
{"t":{"$date":"2023-03-18T04:34:33.944+00:00"},"s":"W",  "c":"ASIO",     "id":22601,   "ctx":"main","msg":"No TransportLayer configured during NetworkInterface startup"}
{"t":{"$date":"2023-03-18T04:34:33.946+00:00"},"s":"I",  "c":"NETWORK",  "id":4648601, "ctx":"main","msg":"Implicit TCP FastOpen unavailable. If TCP FastOpen is required, set tcpFastOpenServer, tcpFastOpenClient, and tcpFastOpenQueueSize."}
{"t":{"$date":"2023-03-18T04:34:33.947+00:00"},"s":"I",  "c":"STORAGE",  "id":4615611, "ctx":"initandlisten","msg":"MongoDB starting","attr":{"pid":1,"port":27017,"dbPath":"/bitnami/mongodb/data/db","architecture":"64-bit","host":"mongodb-0"}}
{"t":{"$date":"2023-03-18T04:34:33.947+00:00"},"s":"I",  "c":"CONTROL",  "id":23403,   "ctx":"initandlisten","msg":"Build Info","attr":{"buildInfo":{"version":"4.4.4","gitVersion":"8db30a63db1a9d84bdcad0c83369623f708e0397","openSSLVersion":"OpenSSL 1.1.1d  10 Sep 2019","modules":[],"allocator":"tcmalloc","environment":{"distmod":"debian10","distarch":"x86_64","target_arch":"x86_64"}}}}
{"t":{"$date":"2023-03-18T04:34:33.947+00:00"},"s":"I",  "c":"CONTROL",  "id":51765,   "ctx":"initandlisten","msg":"Operating System","attr":{"os":{"name":"PRETTY_NAME=\"Debian GNU/Linux 10 (buster)\"","version":"Kernel 5.4.226-129.415.amzn2.x86_64"}}}
{"t":{"$date":"2023-03-18T04:34:33.947+00:00"},"s":"I",  "c":"CONTROL",  "id":21951,   "ctx":"initandlisten","msg":"Options set by command line","attr":{"options":{"config":"/opt/bitnami/mongodb/conf/mongodb.conf","net":{"bindIp":"*","ipv6":false,"port":27017,"unixDomainSocket":{"enabled":true,"pathPrefix":"/opt/bitnami/mongodb/tmp"}},"processManagement":{"fork":false,"pidFilePath":"/opt/bitnami/mongodb/tmp/mongodb.pid"},"security":{"authorization":"disabled"},"setParameter":{"enableLocalhostAuthBypass":"true"},"storage":{"dbPath":"/bitnami/mongodb/data/db","directoryPerDB":false,"journal":{"enabled":true}},"systemLog":{"destination":"file","logAppend":true,"logRotate":"reopen","path":"/opt/bitnami/mongodb/logs/mongodb.log","quiet":false,"verbosity":0}}}}
{"t":{"$date":"2023-03-18T04:34:33.951+00:00"},"s":"I",  "c":"STORAGE",  "id":22270,   "ctx":"initandlisten","msg":"Storage engine to use detected by data files","attr":{"dbpath":"/bitnami/mongodb/data/db","storageEngine":"wiredTiger"}}
{"t":{"$date":"2023-03-18T04:34:33.951+00:00"},"s":"I",  "c":"STORAGE",  "id":22297,   "ctx":"initandlisten","msg":"Using the XFS filesystem is strongly recommended with the WiredTiger storage engine. See http://dochub.mongodb.org/core/prodnotes-filesystem","tags":["startupWarnings"]}
{"t":{"$date":"2023-03-18T04:34:33.951+00:00"},"s":"I",  "c":"STORAGE",  "id":22315,   "ctx":"initandlisten","msg":"Opening WiredTiger","attr":{"config":"create,cache_size=7399M,session_max=33000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000,close_scan_interval=10,close_handle_minimum=250),statistics_log=(wait=0),verbose=[recovery_progress,checkpoint_progress,compact_progress],"}}
{"t":{"$date":"2023-03-18T04:34:34.563+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":"[1679114074:563496][1:0x7f24214f2140], txn-recover: [WT_VERB_RECOVERY_PROGRESS] Recovering log 1 through 2"}}
{"t":{"$date":"2023-03-18T04:34:34.646+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":"[1679114074:645988][1:0x7f24214f2140], txn-recover: [WT_VERB_RECOVERY_PROGRESS] Recovering log 2 through 2"}}
{"t":{"$date":"2023-03-18T04:34:34.722+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":"[1679114074:722877][1:0x7f24214f2140], txn-recover: [WT_VERB_RECOVERY | WT_VERB_RECOVERY_PROGRESS] Main recovery loop: starting at 1/26624 to 2/256"}}
{"t":{"$date":"2023-03-18T04:34:34.816+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":"[1679114074:816017][1:0x7f24214f2140], txn-recover: [WT_VERB_RECOVERY_PROGRESS] Recovering log 1 through 2"}}
{"t":{"$date":"2023-03-18T04:34:34.871+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":"[1679114074:871564][1:0x7f24214f2140], txn-recover: [WT_VERB_RECOVERY_PROGRESS] Recovering log 2 through 2"}}
{"t":{"$date":"2023-03-18T04:34:34.918+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":"[1679114074:918108][1:0x7f24214f2140], txn-recover: [WT_VERB_RECOVERY | WT_VERB_RECOVERY_PROGRESS] Set global recovery timestamp: (0, 0)"}}
{"t":{"$date":"2023-03-18T04:34:34.918+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":"[1679114074:918183][1:0x7f24214f2140], txn-recover: [WT_VERB_RECOVERY | WT_VERB_RECOVERY_PROGRESS] Set global oldest timestamp: (0, 0)"}}
{"t":{"$date":"2023-03-18T04:34:34.942+00:00"},"s":"I",  "c":"STORAGE",  "id":4795906, "ctx":"initandlisten","msg":"WiredTiger opened","attr":{"durationMillis":991}}
{"t":{"$date":"2023-03-18T04:34:34.942+00:00"},"s":"I",  "c":"RECOVERY", "id":23987,   "ctx":"initandlisten","msg":"WiredTiger recoveryTimestamp","attr":{"recoveryTimestamp":{"$timestamp":{"t":0,"i":0}}}}
{"t":{"$date":"2023-03-18T04:34:34.943+00:00"},"s":"I",  "c":"STORAGE",  "id":4366408, "ctx":"initandlisten","msg":"No table logging settings modifications are required for existing WiredTiger tables","attr":{"loggingEnabled":true}}
{"t":{"$date":"2023-03-18T04:34:34.943+00:00"},"s":"I",  "c":"STORAGE",  "id":22262,   "ctx":"initandlisten","msg":"Timestamp monitor starting"}
{"t":{"$date":"2023-03-18T04:34:34.947+00:00"},"s":"I",  "c":"STORAGE",  "id":20536,   "ctx":"initandlisten","msg":"Flow Control is enabled on this deployment"}
{"t":{"$date":"2023-03-18T04:34:34.947+00:00"},"s":"I",  "c":"FTDC",     "id":20625,   "ctx":"initandlisten","msg":"Initializing full-time diagnostic data capture","attr":{"dataDirectory":"/bitnami/mongodb/data/db/diagnostic.data"}}
{"t":{"$date":"2023-03-18T04:34:34.949+00:00"},"s":"I",  "c":"NETWORK",  "id":23015,   "ctx":"listener","msg":"Listening on","attr":{"address":"/opt/bitnami/mongodb/tmp/mongodb-27017.sock"}}
{"t":{"$date":"2023-03-18T04:34:34.949+00:00"},"s":"I",  "c":"NETWORK",  "id":23015,   "ctx":"listener","msg":"Listening on","attr":{"address":"<IP_ADDRESS>"}}
{"t":{"$date":"2023-03-18T04:34:34.949+00:00"},"s":"I",  "c":"NETWORK",  "id":23016,   "ctx":"listener","msg":"Waiting for connections","attr":{"port":27017,"ssl":"off"}}
{"t":{"$date":"2023-03-18T04:34:42.980+00:00"},"s":"I",  "c":"NETWORK",  "id":22943,   "ctx":"listener","msg":"Connection accepted","attr":{"remote":"<IP_ADDRESS>:38498","connectionId":1,"connectionCount":1}}
{"t":{"$date":"2023-03-18T04:34:42.980+00:00"},"s":"I",  "c":"NETWORK",  "id":51800,   "ctx":"conn1","msg":"client metadata","attr":{"remote":"<IP_ADDRESS>:38498","client":"conn1","doc":{"application":{"name":"MongoDB Shell"},"driver":{"name":"MongoDB Internal Client","version":"4.4.4"},"os":{"type":"Linux","name":"PRETTY_NAME=\"Debian GNU/Linux 10 (buster)\"","architecture":"x86_64","version":"Kernel 5.4.226-129.415.amzn2.x86_64"}}}}
{"t":{"$date":"2023-03-18T04:34:42.984+00:00"},"s":"I",  "c":"NETWORK",  "id":22944,   "ctx":"conn1","msg":"Connection ended","attr":{"remote":"<IP_ADDRESS>:38498","connectionId":1,"connectionCount":0}}
{"t":{"$date":"2023-03-18T04:34:52.979+00:00"},"s":"I",  "c":"NETWORK",  "id":22943,   "ctx":"listener","msg":"Connection accepted","attr":{"remote":"<IP_ADDRESS>:37554","connectionId":2,"connectionCount":1}}
{"t":{"$date":"2023-03-18T04:34:52.980+00:00"},"s":"I",  "c":"NETWORK",  "id":51800,   "ctx":"conn2","msg":"client metadata","attr":{"remote":"<IP_ADDRESS>:37554","client":"conn2","doc":{"application":{"name":"MongoDB Shell"},"driver":{"name":"MongoDB Internal Client","version":"4.4.4"},"os":{"type":"Linux","name":"PRETTY_NAME=\"Debian GNU/Linux 10 (buster)\"","architecture":"x86_64","version":"Kernel 5.4.226-129.415.amzn2.x86_64"}}}}
{"t":{"$date":"2023-03-18T04:34:52.984+00:00"},"s":"I",  "c":"NETWORK",  "id":22944,   "ctx":"conn2","msg":"Connection ended","attr":{"remote":"<IP_ADDRESS>:37554","connectionId":2,"connectionCount":0}}
{"t":{"$date":"2023-03-18T04:35:03.010+00:00"},"s":"I",  "c":"NETWORK",  "id":22943,   "ctx":"listener","msg":"Connection accepted","attr":{"remote":"<IP_ADDRESS>:36944","connectionId":3,"connectionCount":1}}
{"t":{"$date":"2023-03-18T04:35:03.011+00:00"},"s":"I",  "c":"NETWORK",  "id":51800,   "ctx":"conn3","msg":"client metadata","attr":{"remote":"<IP_ADDRESS>:36944","client":"conn3","doc":{"application":{"name":"MongoDB Shell"},"driver":{"name":"MongoDB Internal Client","version":"4.4.4"},"os":{"type":"Linux","name":"PRETTY_NAME=\"Debian GNU/Linux 10 (buster)\"","architecture":"x86_64","version":"Kernel 5.4.226-129.415.amzn2.x86_64"}}}}
{"t":{"$date":"2023-03-18T04:35:03.014+00:00"},"s":"I",  "c":"NETWORK",  "id":22944,   "ctx":"conn3","msg":"Connection ended","attr":{"remote":"<IP_ADDRESS>:36944","connectionId":3,"connectionCount":0}}
{"t":{"$date":"2023-03-18T04:35:13.023+00:00"},"s":"I",  "c":"NETWORK",  "id":22943,   "ctx":"listener","msg":"Connection accepted","attr":{"remote":"<IP_ADDRESS>:59666","connectionId":4,"connectionCount":1}}
{"t":{"$date":"2023-03-18T04:35:13.023+00:00"},"s":"I",  "c":"NETWORK",  "id":51800,   "ctx":"conn4","msg":"client metadata","attr":{"remote":"<IP_ADDRESS>:59666","client":"conn4","doc":{"application":{"name":"MongoDB Shell"},"driver":{"name":"MongoDB Internal Client","version":"4.4.4"},"os":{"type":"Linux","name":"PRETTY_NAME=\"Debian GNU/Linux 10 (buster)\"","architecture":"x86_64","version":"Kernel 5.4.226-129.415.amzn2.x86_64"}}}}

To Reproduce
N/A
Expected behavior
Expect that Free5gc NRF and its dependency of mongodb is running properly
Environment (please complete the following information):

free5GC Version: v3.0.5
OS: Amazon Linux 2
Kernel version:
go version:
c compiler version (Option):

Trace File
Configuration File
Provide the configuration file here.
If not clear of what to do, the config folder can be zip and upload it here.
PCAP File
Dump the packet and provide the pcap file here.
If not clear of what to do, this command can be used sudo tcpdump -i any -w free5gc.pcap prior to running bug reproduce. Then upload the pcap file free5gc.pcap.
Log File
Provide the program log file here.
If not clear of what to do, copy the printed log on the screen and upload it here.
System architecture (Option)
Please provide the draft architecture, including the scenario, use cases, installation environment(bare metal, vm, container, or k8s), etc.
Walkthrough (Option)
free5GC will be interested on the research or finding in brief.
Additional context
It will be appreciated if other context can be added here.

Hi @Zhenye-Na
We haven't maintenance the Kubernetes deployment method currently.
I suggest that you may check the service object of MongoDB is work or not.
If the service of MongoDB works properly (e.g. The webconsole can be accessed normally), you should propose a new issue to the helm repo you deployed.
Thanks a lot.

Hello @ianchen0119 ,
Thanks for the fast responding!
Actually I tried to use the kubectl command to execute command into the cluster, and below is the output:
kubectl exec -it mongodb-0 -- sh

$ mongo
MongoDB shell version v4.4.4
connecting to: mongodb://<IP_ADDRESS>:27017/?compressors=disabled&gssapiServiceName=mongodb
Implicit session: session { "id" : UUID("79c4481a-5fc4-4d33-a625-ade3fe93e025") }
MongoDB server version: 4.4.4
---
The server generated these startup warnings when booting:
        2023-03-20T19:31:37.065+00:00: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine. See http://dochub.mongodb.org/core/prodnotes-filesystem
---
---
        Enable MongoDB's free cloud-based monitoring service, which will then receive and display
        metrics about your deployment (disk utilization, CPU, operation statistics, etc).

        The monitoring data will be available on a MongoDB website with a unique URL accessible to you
        and anyone you share the URL with. MongoDB may use this information to make product
        improvements and to suggest MongoDB products and deployment options to you.

        To enable free monitoring, run the following command: db.enableFreeMonitoring()
        To permanently disable this reminder, run the following command: db.disableFreeMonitoring()
---
>

It seems like the mongo is running properly, even though I didnt use the web console to confirm it.
I have already raised an issue here https://github.com/Orange-OpenSource/towards5gs-helm/issues/81 since this is the NRF I referred to deploy. Will see what they replied.
I could safely close this issue since it is a "false" alarm to say NRF implementation contains a bug.
But before I closing this issue, is there any gotchas related to NRF + Mongo I should be aware of ?
Thanks!

Hi @Zhenye-Na
I can ensure the issue you encountered is not caused by the NRF.
The root cause is the initContiainer where specified in NRF's deployment object.
This container is used to ensure that mongoDB can be accessed correctly when NRF is running.
Futhermore,
I think the reason for this situation (initContainer can not access mongoDB but the mongo container is running) may caused by the service object of mongoDB is not working.

Note:
Service object implements the service discovery of Pods (We can access the mongoDB by querying mongodb:27017 not <IP_OF_THE_POD>:27017).

Thanks.


Question: Can WinUI Use Processes and Files?

I just read about WinUI. I was wondering whether it can replace WPF. The main issue with UWP is that it can't start processes, access the file system, access Win API, and is thus useless for many types of Windows applications.
Can WinUI start processes and access the file system, or does it have the same restrictions as UWP?

WinUI desktop projects are Win32 projects exactly like WPF and Winforms, so a WinUI 3 Desktop app can start processes and access all files. WinUI 3 UWP projects will still be limited to the features of the UWP container, e.g. not starting a process or only accessing certain files.

@chingucoding is correct. With winui3 you can use desktop apps to access this functionality.  UWP apps will still not be able to do these things.

Hey guys, coming later to the party, I am wondering how I can differenciate between a "win32 project" and an "uwp project". For version 1.0 of winui3 there is no such difference.
My goal is to access the filesystem without the UWP capabilities restrictions. Is there any way to do that, maybe even a sample?

If i recall correctly, only the experimental versions of the Win App SDK support creating UWP apps. If you create a WinUI 3 WASDK Version 1.0 app, it will be a win32 project. A good way to tell if it is win 32 or not is to look at the .NET version being used. Win32 WinUI 3 apps use .NET 5 and higher, the UWP apps are still on the UWP .NET SDK/.NET Native.


refactor(semantic): correct scope in CatchClause

close: #4186

#4192  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Dunqing and the rest of your teammates on  Graphite


Use gihutb action instead of trevis-ci

Let me know if you need changes.
solved #32

Thanks @RodrigoDornelles 🚀


Make CLI exit code useful for detecting tmt errors

Please change the reserved exit codes, as documented on, https://tmt.readthedocs.io/en/stable/code/autodocs/tmt.html#tmt.cli.TmtExitCode , to use values 2 or greater for test results, leaving 1 for internal TMT-specific errors, which should always be investigated by the infrastructure owner.
These would be ie.

TMT bug causing a python traceback (which naturally exits with 1)
invalid command line arguments

or CLI arguments with invalid values, ie. existing tmt run -i directory

missing python module (causing NameError, see first point)
inability to create a writable temporary directory
etc.

and potentially even

discover from a git URL returning HTTP errors
other "setup-style" tasks

Would require some coordination with downstream, maybe gating this by an env-variable TMT_NEW_EXIT_CODES. Some more reference ^1.
It does seem more in line to have:

1 catch-all internal error, maybe including Python module import errors, etc.
2 syntax error either in cli or fmf files
other codes still to be discussed

Pytest does not seem to use such convention, but it's also only half aligned with tmt's. Why it might make sense to align more with other standards is that tmt can be used outside of test wrapping, e.g. tmt show, tmt run discover, etc.

Yeah, I would also lean towards keeping the current exit code definition and rather catching & redirecting all errors to a proper exit code. Unless really necessary let's not break the backward compatibility.

Yeah, I would also lean towards keeping the current exit code definition and rather catching & redirecting all errors to a proper exit code. Unless really necessary let's not break the backward compatibility.

Isn't that already happening in https://github.com/teemtee/tmt/blob/main/tmt/main.py#L15? Everything except for SystemExit gets mapped to 2, "Errors occured during test execution.", which might be incorrect as many errors may happen before executing any test (e.g. the invalid URL used in discover).

To clarify: My use case, essentially, is to catch any errors from an infrastructure PoV. I don't care if the tests reported (using custom format or not) pass/fail/error/skip/whatever.
I just want to know (somehow, ideally exit code, but doesn't have to be) that TMT failed to execute tests or retrieve their results.
Currently, I have to grep TMT's output for things like

^Error:
^    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~$
^plan failed$
etc.

Does using exit code 2 not work in this case? Any non-test errors should be mapped to it

Does using exit code 2 not work in this case? Any non-test errors should be mapped to it

The problem is that any tests which report error (due to their internal logic, or just because they want to via result:custom) will also result in exit code 2.
If this was moved to some other exit code, then I could indeed use 2.

Well, yes, but isn't that intended to be the case? error could mean that e.g. beakerlib was not installed, or anything to indicate that the testing infrastructure is not well prepared.

The point is that error is a completely valid result status, and we use it (in our python non-Beakerlib suite) for several cases, ie.

a failure-waiving rule matched a pass
some timeouts inside a test were exceeded
installing a nested VM failed on Anaconda
a service (ie. osbuild-composer) failed to restart after the test made configuration changes to it
etc.

We define, essentially,

pass = test managed to run the expected scenarios and verify that they work
fail = test managed to run the expected scenarios, verify that its results were valid (nothing test-related was broken) and the tested functionality failed
error = a problem happened that prevented the test from testing the functionality

This means if we see a fail, it's almost always a new bug.
You can't rely on a test using error to mean an infrastructure error.


@enumToInt => @intFromEnum

The @enumToInt built-in was just renamed to @intFromEnum.
ref: https://github.com/ziglang/zig/commit/a6c8ee5231230947c928bbe1c6a39eb6e1bb9c5b

Looks like https://ziggit.dev/t/major-zig-language-update-just-landed-removal-of-destination-type-from-all-cast-builtins/898 landed while this was up. I'll fix that too.


fix: feedback on userstory

Closes https://github.com/Iconica-Development/flutter_start/issues/33
Closes https://github.com/Iconica-Development/flutter_start/issues/31
Closes https://github.com/Iconica-Development/flutter_start/issues/30
Closes https://github.com/Iconica-Development/flutter_start/issues/29
Closes https://github.com/Iconica-Development/flutter_start/issues/28


Transactions may fail with strings using special characters

Looks like there is a bug with special characters causing transactions to fail, which in turn prevent data to store.

Fixed in #32


[OZ 5.x Contract Support] Add OZ 777 example

Problem
The Hedera network supports smart contracts as part of EVM equivalence.
Occasionally items have shown up that surfaced inequivalence at the language or opcode layer.
OZ provides many useful templates that smart contract devs are used to utilizing.
However, it may not be clear what coverage the Hedera Smart Contract Service 2.0 has for them
Solution

Add solidity contract example that utilize follow the ERC-777 standard

Add a contract under contracts/OZ/ERC777 and tests under respective directories

Alternatives
No response

closed as OZ v5 removed erc777


The members of the Adapter  are named in lowercase letters，so cannot assign values outside the package

The members of the Adapter  are named in lowercase letters，so cannot assign values outside the package
// Adapter represents the gdb adapter for policy storage.
type Adapter struct {
	driverName     string
	dataSourceName string
	tableName      string
	db             gdb.DB
}

@closetool plz make a PR to fix it.

@vance-liu plz make a new GitHub release.

Thank you for your reminder, V0.1.0 is released.

@believening https://github.com/vance-liu/gdb-adapter/releases/tag/V0.1.0


Chore ignore license check on .github

Proposed changes
ignore license check on .github
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Add API query for VMs filtered by tree selections

I'm not sure what this filter logic will look like, or whether we'll need to change any backend stuff to support it.

Note to self: the tree query results contain VMs as leaf nodes, we can just perform lookups based on those ids.


Version 1.20 not respecting explorer.openEditors.dynamicHeight config

VSCode Version:  1.20.0-insider
OS Version: ElementaryOS 0.4.1

When the setting explorer.openEditors.dynamicHeight is set to false the "open editors" panel should have a fixed height. This is not working on this  version. On 1.19 (stable) is working fine.
Steps to Reproduce:

Set the setting explorer.openEditors.dynamicHeight to false

Reproduces without extensions: Yes

On the left is 1.20, on the right is 1.19.
Both are with the explorer.openEditors.dynamicHeight set to false and explorer.openEditors.visible set to 3.

@isidorn can we now resize the open editors view?

@bpasero yeah a user did it and it actually behaves fine. Try it out.
I should probably dump the dynamicHeight flag though

@isidorn really? :O
I really like this option :/

@isidorn what is the current solution? I know only the two settings above.
What I like is  that this panel always has the same height (enought space for 3 tabs), regardless of the number of open files. This setting is what do that for me. We have another way? 🤔
Thanks!

@beeblebrox3 currently we do not support having open editors be a fixed height. The reason for this is that I believe more users want the feature that the open editors can be resized when the overflow, than having it always the same.
I will verify this hypthoesis by looking at  telemetry
@ramya-rao-a I just tried running the following query at kusto always says loading, is there somethign wrong I am doing?
I tried running it on this site https://ailoganalyticsportal-privatecluster.cloudapp.net/#/discover/query/main
let Settings = VSCodeEvents
| where timestamp > ago(7d)
| where name == "monacoworkbench/updateConfiguration"
| extend dims = parsejson(customDimensions)
| extend machineId = tostring(dims['common.machineId']), keysString = dims.configurationKeys, keysType = tostring(dims.configurationSource)
| extend ver = tostring(dims.version)
| summarize argmax(timestamp, keysString) by machineId, keysType
| project machineId, max_timestamp_keysString, keysType
| summarize dcount(machineId) by tostring(max_timestamp_keysString), keysType
| project max_timestamp_keysString, keysType, AllMachines=dcount_machineId
;
Settings
| extend Keys = split(substring(max_timestamp_keysString, 2, strlen(max_timestamp_keysString) - 4), '","')
| mvexpand Key = Keys
| where Key == "explorer.openEditors.dynamicHeight"
| summarize Machines=sum(AllMachines) by tostring(Key), keysType
| sort by Machines desc
| limit 100

@isidorn On the stable we can do this. Maybe we can support both ways. Its possible?
My problem with the dynamic height is that when a new tab opens, the files panel moves. Is very annoying when I'm using the mouse to open files. Sometimes I do this.

@beeblebrox3 I understand the use case. For that you could use a smaller openEditor.visible number and as soon as that is hit the open editors will no longer grow. You will have to manually resize it
Try explorer.openEditors.visible: 3 for instance and let me know how it goes.

@isidorn I know, I use it too. With the value 3, by the way. But it will only solve my issue when I already have 3 open files :/

Why remove a feature, when it had value for users? I really hate that the file list is moving from under the cursor. Let's assume that you want to open 6 files. Click on the first one, then, argh, files moved under the mouse...removing this feature I guess will lead that 220 users to set the open file list to size of 0 to achieve something "similar" (NOT!) :-S

I was (probably) one of the 220 people, and found this issue out of frustation after the 1.20 update. Here is my alternative solution to this:
I feel it would be better to allow the open editors list to be expanded up to the number specified in the explorer.openEditors.visible setting*, even if the number of open editors has not reached this level.
This would effectively mean that the size of the open editor panel can be set to the size it would expand to automatically.
This can be achieved by updating this code in openEditorsView which calculates the min and max sizes, with my alternative.
Here is a video of this in action:
https://streamable.com/5ior5 **
I can make a PR if this is acceptable @isidorn
Notes:
*: Maybe the explorer.openEditors.visible setting does not accurately describe the purpose of this value and the dynamicHeight setting would have to be reinstated. This is because when the number of open editors increases past the setting, the size of the panel will remain at that value in my current implementation. Without digging further into the source, I would not know how fix this.
**: Does anyone know a better way I can make and attach a suitable video?

I was (probably) one of the 220 people, too. Currently the best solution is, set the visible value to 0.

A PR is always acceptable, but I would prefer if we first create one where we discuss what the problem is, what we want to achieve before doing any coding. So feel free to create that. Also I would wait a couple of days for the dust to settle after the release to see how many people are impacted by this.
Also from Monday, insiders will have some updates to the open editors view. So try it out there, and feedback based on that version would be the most valuable in the PR.
Thanks

OK, No Problem. I'll wait until Tuesday, see the change insiders get, then make a PR for discussion. Thanks for the quick reply!

@beeblebrox3 wrote: "when a new tab opens, the files panel moves". This is totally my case.
I see only one workaround to drag-drop "open editors" panel under "explorer" panel (to the bottom). In this case the new opened file resizes "explorer" panel from the bottom and does not shift items which is hovered by mouse cursor.

Regarding your comment, @isidorn , I have a couple of questions:

You say that you would prefer the PR to only be discussion before any coding is done and commits are added. However, it is not possible, insofar as I can see, to create a PR without any commits. If this is an oversight, would you prefer a new issue to be created for discussion, or to reopen this issue.
There are supposedly changes to the open editors view in the latest insiders as of at least yesterday. I cannot obviously see any changes, at least which affect this issue, even looking at commits starting from the tag of 1.20.0 to the latest master. Would you mind laying out what these are.

Many thanks.

@DanMcNab there is an open issue for this, let's continue the discussion there. In the lattest comment I mentioned what is the difference.
https://github.com/Microsoft/vscode/issues/43501

did not see the reference, here is my message :
You all got my point.
Sadly it does not work on latest vscode insider either :

"explorer.openEditors.visible": 0 hide it completly.
It is a huge drawback when you are very fast opening files with mouse. This is my only mousepad usage in vscode, and trust me, this issue burn my mind.
I understand that default design behaviour may change with time. But you should let the choice of keeping legacy behaviour too. Since it's literally, removing an available setting.
This may be the first ticket about, may not be the last. My team drives crazy on this.

Trying to understand what's going on here. Can somone explain how I can have a fixed size in any way with latest vscode? I always end up with lots of open editors and I don't want my workspace to be squished down like this:

Setting
"explorer.openEditors.visible": 0
to hide completely is not what I want, I want something like 5 files always and a scrollbar.

@hedefalk this seems like an unrelated issue ot this one, please file a new issue with reproducable step how you get into that state and assign it to me. Thanks