Add examples, tests, enable Continuous Integration

The failure on Windows seems to be a real bug.
If it is and if you don't have time to fix it I'd disable the CI on Windows till you find the time.
I've also written a blog post and recorded a video explaining this PR:
https://code-maven.com/python-automated-test-for-sssimp-simple-static-generator
Closes #5

Thank you for looking into this so quickly!
I fiddled a bit locally and even watched the whole video. Thank you for using my project to showcase how to contribute to open source to others, this is a very great way to get more people into open source!!
Now regarding the PR,

I have a few concerns regarding the extensive use of the os.path module, while the code of sssimp itself mostly use Pathlib instead, which is more in-line with modern Python. I think it'll be better to use similar patterns in both the code and tests, rather than mixing 2 different ways of doing the same things.
I believe the test files and the conftest file should go to a /tests/ folder at the root of the project, this appears to be how it's done in most popular Python projects.
I'm not too sure about the --save design choice, I think it's not very intuitive to use pytest to generate the examples. Making it its own script might be better. Someone who is willing to re-generate the examples might not think to look into tests to see how they can easily generate them all.

Those are all very easy changes, so I'll merge this PR as-is into another branch and implement them myself, then merge it once it's ready.
Regarding the bugs you noticed, good catch!
I think the order of the files when you iterate over them should always be the same, even props to you for noticing you could fix it using Jinja, however I believe future users will expect being able to always get the file in the same order without having to use sort. Even if it might not be the order they want, it's weird for the tool to generate different outputs for seemingly random reasons.
Internally it calls pathlib.Path.glob, I guess this function does not produce predictable results!
https://github.com/Tina-otoge/sssimp/blob/bdca7b6bea61933df9609e101db94d13df077668/src/sssimp/generators/html.py#L71
The Windows path one on .href is a good catch too. It happens because I'm simply returning the path of the underlying string representation of the path.Path object, which on Windows use backslashes.
I'll mark those 2 as bugs and fix them soon-ish.
Thank you again for your contribution, it is very appreciated!

I like your suggestions. As so far I avoided pathlib, this was a good opportunity to look into it.


code changes w.r.t ceph ansible cluster-name

Signed-off-by: sunilkumarn417<EMAIL_ADDRESS>

Can one of the admins verify this patch?

http://pulpito.ceph.redhat.com/sunnagar-2020-04-23_12:01:11-rgw:multisite-ansible-rh-luminous-distro-basic-clara/


⚠ Bofrost.fr has degraded performance

In df9bb56, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1461 ms

Resolved: Bofrost.fr performance has improved in 71d6131 after 11 minutes.


Windows Authentication with Kestrel + IISIntegration

Issue / Steps to reproduce the problem
Configured identity server to run on kestrel with IISIntegration and enabled WindowAuthentication in IISExpress with VS its perfectly working. Later moved it to Windows server and local IIS then its stopped working
*UnauthorizedAccessException: Attempted to perform an unauthorized operation.
for windows server i've installed DotNetCore.1.0.5_1.1.2-WindowsHosting

I'd search the Microsoft repos for this -- it's some bug in their components.

Any update on the issue? closing for now - feel free to re-open if it needs further discussion.


Click on the status bar item to restart RLS

This PR makes the status bar item indicating RLS status be clickable.
Clicking on the status bar item makes the extension restart RLS.
I checked it and it worked.
I'll try it again when I get home.
Motivation for the feature is that RLS is unstable, it may panic, it may crash.
Having a way to restart RLS is good feature.
Unresolved:

RLS doesn't respond to a shutdown request, hence doesn't exit
Add information about the feature to the documentation

I will merge the PR as soon as PR is merged.

I think the extension should detect and restart rls automatically. This would match better what @nrc envisioned here https://github.com/rust-lang-nursery/rls/issues/147

@jonasbb,
I haven't found what nrc had suggested to find whether RLS needs restart.
Any way it is good to let the user restart RLS when the user wants.

That's the part I was referring to:

Our current philosophy and plan for error handling in the RLS is that the RLS should fail easily, and recover well from being restarted.

Your motivation is that rls is unstable which is partly by design. Therefore, I think a good integration should be able to detect this and restart rls automatically when necessary. Having an option to do this manually cannot hurt though.

@jonasbb,
But what if RLS failed? Should the user reopen the project? I think not.

@KalitaAlexey No he should not. But neither should it be necessary to manually click a label. If the RLS process exited unexpectedly, just restart it. Don't wait for any user interaction.

@jonasbb,
At first manual is enough.
It is easy.

I am stuck because after restarting it doesn't hide the previous "Rust Language Server" output channel.

I got what is wrong.
It has been fixed in https://github.com/Microsoft/vscode/issues/20703

I added changes which are required in order to dispose the output channel.
When VSCode 1.10 is released, I should check whether it works.

VSCode 1.10 has been released.
The mentioned problem is partially fixed.
There is one little problem: https://github.com/Microsoft/vscode/issues/21734
The problem doesn't blocks the feature.
I am inclined to add it.

@redactedscribe,
Could you check the documentation?

@redactedscribe,
Nice.
Do you check code or only documentation?

Do you check code or only documentation?
Do you mean in general? I have no experience with TypeScript. I have moderate coding ability, reading it is easier for me. I can test stuff though if need be, but so far I have only been reviewing the documentation.

@redactedscribe,
I don't mind if you look at code for some general sense)

@KalitaAlexey Just tried to clear up a few sentences. I hope they are factual.

@redactedscribe,
Good. Thank you.


[Q] How can I log images for a run that has already finished?

Hi @TahaBinhuraib, a potential solution would be resuming your run and then upload your image artifacts once the run has been resumed.

Hi @TahaBinhuraib, since we have not heard back from you we are going to close this request. If you would like to re-open the conversation, please let us know!


iSort going crazy

Got all sorts of artifacts from the line-endings issue.
Needs to convert back from CR to CRLF.

Seems to be fixed in timothycrosley/isort#671


 Raft base tick will
be implemented in another PR.
After this PR, down peers may not be reported in time. In the worse case
PD may need more than 5 minutes to know which node is down or up
again. /cc @disksing @nolouch
What are the type of the changes? (mandatory)

New feature

How has this PR been tested? (mandatory)
unit tests
Does this PR affect documentation (docs) or release note? (mandatory)
Yes. But will be updated in the next PR.
Does this PR affect tidb-ansible update? (mandatory)
No.
Refer to a related PR or issue link (optional)
#4591, tikv/rfcs#23

PTAL

/run-all-tests

/run-all-tests


Add test resources documentation

@vlsi hope this clarifies what you pointed out in the multi-project support PR

@melix ,
I think targetProject is not documented.
However, I would prefer something that can be understood by a mere looking at the build file without searching the documentation for each and every property.

However, I would prefer something that can be understood by a mere looking at the build file without searching the documentation for each and every property.

What would you suggest? We need a way to tell which project is the test resources provider. We can't use a Configuration, because it doesn't make sense: we don't want a list of dependencies, we want a project reference. We don't want a Project instance either, because this is capturing too much state.

We can't use a Configuration, because it doesn't make sense: we don't want a list of dependencies, we want a project reference

Well, I thought configuration+dependency would be easier to understand and extend.
As far as I see you use "project reference" only for creating a dependency: https://github.com/micronaut-projects/micronaut-gradle-plugin/search?q=gettargetproject, so using the dependency looked reasonable to me.
At the same time, a regular dependency would support typesafe project accessors while targetProject=... would not support project accessors :-/

I think targetProject is not documented.
It is.

I think the only place where targetProject appears is the case when "targetProject" is used in the sample build plan.
https://github.com/search?q=org%3Amicronaut-projects+targetProject&type=code
At the same time, I do not see targetProject being added by the current PR 🤷♂ :

Would you please highlight where targetProject is mentioned?

Would you please highlight where targetProject is mentioned?

Precisely in the screenshot you pasted, with the callout :)

Well, I thought configuration+dependency would be easier to understand and extend (e.g. it would support adding dependency on several testresources projects).

Right, I think dependency on multiple test resource projects would sound a bit scary, but I can see the appeal.

Precisely in the screenshot you pasted, with the callout :)

Now I see. The name of "target" looks weird, as it feels something like "deploy test resources to a target project X"

@vlsi what about 1ffaf9a?

@melix, thank you. I think it is indeed better. However, now I'm feeling guilty for the disruption :)


Stack and queue

Stack and a Queue Implementation

[x] Node

[x] Create a Node class that has properties for the value stored in the Node, and a pointer to the next node.

[x] Stack

[x] Create a Stack class that has a top property. It creates an empty Stack when instantiated.
[x] This object should be aware of a default empty value assigned to top when the stack is created.
[x] The class should contain the following methods:

[x] push

[x] Arguments: value
[x] adds a new node with that value to the top of the stack with an O(1) Time performance.

[x] pop

[x] Arguments: none
[x] Returns: the value from node from the top of the stack
[x] Removes the node from the top of the stack
[x] Should raise exception when called on empty stack

[x] peek

[x] Arguments: none
[x] Returns: Value of the node located at the top of the stack
[x] Should raise exception when called on empty stack

[x] is empty

[x] Arguments: none
[x] Returns: Boolean indicating whether or not the stack is empty.

[x] Queue

[x] Create a Queue class that has a front property. It creates an empty Queue when instantiated.
[x] This object should be aware of a default empty value assigned to front when the queue is created.

[x] The class should contain the following methods:

[x] enqueue

[x] Arguments: value
[x] adds a new node with that value to the back of the queue with an O(1) Time performance.

[x] dequeue

[x] Arguments: none
[x] Returns: the value from node from the front of the queue
[x] Removes the node from the front of the queue
[x] Should raise exception when called on empty queue

[x] peek

[x] Arguments: none
[x] Returns: Value of the node located at the front of the queue
[x] Should raise exception when called on empty stack

[x] is empty

[x] Arguments: none
[x] Returns: Boolean indicating whether or not the queue is empty


iOS 15(iPhone OS 15.4 (19E241)) Flutter 2.8.1 got crash because of EXC_CORPSE_NOTIFY

Steps to Reproduce

For now, it is reproducible on one user's phone. (I havn't check if all the device on 15.4(19E241) can reproduce this crash)
We use InAppPurchasePlugin to handle the in-app purchase.
When InAppPurchasePlugin ask user to re-enter the password, and the user refused, the crash will reproduce on user's phone.

Expected results:
Actual results:

Code sample

// crash stacktrace
12  Runner                        	       0x10146ee4c 0x100dc0000 + 7007820
13  Runner                        	       0x10146c8c8 0x100dc0000 + 6998216
14  Runner                        	       0x10146b69c 0x100dc0000 + 6993564

-[InAppPurchasePlugin handleTransactionRestoreFailed:] (in Runner) (InAppPurchasePlugin.m:374)
__41-[InAppPurchasePlugin initWithRegistrar:]_block_invoke_2 (in Runner) (InAppPurchasePlugin.m:0)
-[FIAPaymentQueueHandler paymentQueue:restoreCompletedTransactionsFailedWithError:] (in Runner) (FIAPaymentQueueHandler.m:0)

Application Specific Information:
abort() called

Last Exception Backtrace:
0   CoreFoundation                	       0x1a384dd78 __exceptionPreprocess + 220
1   libobjc.A.dylib               	       0x1bc4b2734 objc_exception_throw + 60
2   Foundation                    	       0x1a50d31f0 _userInfoForFileAndLine + 0
3   Flutter                       	       0x10427e4f4 0x103d8c000 + 5186804
4   Flutter                       	       0x10427e6e4 0x103d8c000 + 5187300
5   Flutter                       	       0x10427e6e4 0x103d8c000 + 5187300
6   Flutter                       	       0x10427e6e4 0x103d8c000 + 5187300
7   Flutter                       	       0x10427e6e4 0x103d8c000 + 5187300
8   Flutter                       	       0x10427e6e4 0x103d8c000 + 5187300
9   Flutter                       	       0x10427e6e4 0x103d8c000 + 5187300
10  Flutter                       	       0x10427ebe8 0x103d8c000 + 5188584
11  Flutter                       	       0x10427ba68 0x103d8c000 + 5175912
12  Runner                        	       0x10146ee4c 0x100dc0000 + 7007820
13  Runner                        	       0x10146c8c8 0x100dc0000 + 6998216
14  Runner                        	       0x10146b69c 0x100dc0000 + 6993564
15  libdispatch.dylib             	       0x1a34b2e68 _dispatch_call_block_and_release + 32
16  libdispatch.dylib             	       0x1a34b4a2c _dispatch_client_callout + 20
17  libdispatch.dylib             	       0x1a34c2f48 _dispatch_main_queue_drain + 928
18  libdispatch.dylib             	       0x1a34c2b98 _dispatch_main_queue_callback_4CF + 44
19  CoreFoundation                	       0x1a38062f0 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 16
20  CoreFoundation                	       0x1a37c01f4 __CFRunLoopRun + 2532
21  CoreFoundation                	       0x1a37d36b8 CFRunLoopRunSpecific + 600
22  GraphicsServices              	       0x1bf86d374 GSEventRunModal + 164
23  UIKitCore                     	       0x1a6138e88 -[UIApplication _run] + 1100
24  UIKitCore                     	       0x1a5eba5ec UIApplicationMain + 364
25  Runner                        	       0x100dc7884 main + 112
26  dyld                          	       0x101ec9ce4 start + 520

Logs

Incident Identifier: 554D6DA9-9E7B-4793-BA48-73094019B1BF
CrashReporter Key:   8bd92585c6ef40bf52da53421768dac13e0454f5
Hardware Model:      iPhone14,3
Process:             Runner [3049]
Path:                /private/var/containers/Bundle/Application/644732C8-9F5B-4CFC-A9BF-13E5DA88A179/Runner.app/Runner
Identifier:          com.mmmm.mmmm
Version:             2.2.6 (5145)
AppStoreTools:       13A1030d
Code Type:           ARM-64 (Native)
Role:                Foreground
Parent Process:      launchd [1]
Coalition:           com.mmmm.mmmm [817]

Date/Time:           2022-03-15 14:40:39.4218 +0800
Launch Time:         2022-03-15 14:40:33.1645 +0800
OS Version:          iPhone OS 15.4 (19E241)
Release Type:        User
Baseband Version:    1.59.03
Report Version:      104

Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note:  EXC_CORPSE_NOTIFY
Triggered by Thread:  0

Application Specific Information:
abort() called

Last Exception Backtrace:
0   CoreFoundation                	       0x1a384dd78 __exceptionPreprocess + 220
1   libobjc.A.dylib               	       0x1bc4b2734 objc_exception_throw + 60
2   Foundation                    	       0x1a50d31f0 _userInfoForFileAndLine + 0
3   Flutter                       	       0x10427e4f4 0x103d8c000 + 5186804
4   Flutter                       	       0x10427e6e4 0x103d8c000 + 5187300
5   Flutter                       	       0x10427e6e4 0x103d8c000 + 5187300
6   Flutter                       	       0x10427e6e4 0x103d8c000 + 5187300
7   Flutter                       	       0x10427e6e4 0x103d8c000 + 5187300
8   Flutter                       	       0x10427e6e4 0x103d8c000 + 5187300
9   Flutter                       	       0x10427e6e4 0x103d8c000 + 5187300
10  Flutter                       	       0x10427ebe8 0x103d8c000 + 5188584
11  Flutter                       	       0x10427ba68 0x103d8c000 + 5175912
12  Runner                        	       0x10146ee4c 0x100dc0000 + 7007820
13  Runner                        	       0x10146c8c8 0x100dc0000 + 6998216
14  Runner                        	       0x10146b69c 0x100dc0000 + 6993564
15  libdispatch.dylib             	       0x1a34b2e68 _dispatch_call_block_and_release + 32
16  libdispatch.dylib             	       0x1a34b4a2c _dispatch_client_callout + 20
17  libdispatch.dylib             	       0x1a34c2f48 _dispatch_main_queue_drain + 928
18  libdispatch.dylib             	       0x1a34c2b98 _dispatch_main_queue_callback_4CF + 44
19  CoreFoundation                	       0x1a38062f0 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 16
20  CoreFoundation                	       0x1a37c01f4 __CFRunLoopRun + 2532
21  CoreFoundation                	       0x1a37d36b8 CFRunLoopRunSpecific + 600
22  GraphicsServices              	       0x1bf86d374 GSEventRunModal + 164
23  UIKitCore                     	       0x1a6138e88 -[UIApplication _run] + 1100
24  UIKitCore                     	       0x1a5eba5ec UIApplicationMain + 364
25  Runner                        	       0x100dc7884 main + 112
26  dyld                          	       0x101ec9ce4 start + 520

Thread 0 name:   Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0   libsystem_kernel.dylib        	       0x1db316b78 __pthread_kill + 8
1   libsystem_pthread.dylib       	       0x214f883bc pthread_kill + 268
2   libsystem_c.dylib             	       0x1ae93051c abort + 168
3   Runner                        	       0x10160a910 0x100dc0000 + 8694032
4   Runner                        	       0x100e0bc04 0x100dc0000 + 310276
5   Runner                        	       0x10106f5d4 0x100dc0000 + 2815444
6   FBSDKCoreKit_Basics           	       0x101e8015c FBSDKExceptionHandler + 96
7   CoreFoundation                	       0x1a38cf1b4 __handleUncaughtException + 632
8   libobjc.A.dylib               	       0x1bc4b8c7c _objc_terminate() + 132
9   Runner                        	       0x100e4aebc 0x100dc0000 + 569020
10  libc++abi.dylib               	       0x1bc5bcf18 std::__terminate(void (*)()) + 20
11  libc++abi.dylib               	       0x1bc5bceb4 std::terminate() + 64
12  libdispatch.dylib             	       0x1a34b4a40 _dispatch_client_callout + 40
13  libdispatch.dylib             	       0x1a34c2f48 _dispatch_main_queue_drain + 928
14  libdispatch.dylib             	       0x1a34c2b98 _dispatch_main_queue_callback_4CF + 44
15  CoreFoundation                	       0x1a38062f0 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 16
16  CoreFoundation                	       0x1a37c01f4 __CFRunLoopRun + 2532
17  CoreFoundation                	       0x1a37d36b8 CFRunLoopRunSpecific + 600
18  GraphicsServices              	       0x1bf86d374 GSEventRunModal + 164
19  UIKitCore                     	       0x1a6138e88 -[UIApplication _run] + 1100
20  UIKitCore                     	       0x1a5eba5ec UIApplicationMain + 364
21  Runner                        	       0x100dc7884 main + 112
22  dyld                          	       0x101ec9ce4 start + 520

[✓] Flutter (Channel stable, 2.8.1, on macOS 11.6 20G165 darwin-arm, locale
    zh-Hans-CN)
    • Flutter version 2.8.1 at /Users/blake/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 77d935af4d (2 months ago), 2021-12-16 08:37:33 -0800
    • Engine revision 890a5fca2e
    • Dart version 2.15.1

[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
    • Android SDK at /Users/blake/Library/Android/sdk
    • Platform android-32, build-tools 32.0.0
    • ANDROID_HOME = /Users/blake/Library/Android/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.10.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2020.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[✓] VS Code (version 1.63.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.34.0

[✓] Connected device (1 available)
    • Chrome (web) • chrome • web-javascript • Google Chrome 98.0.4758.109

• No issues found!

2. We use InAppPurchasePlugin to handle the in-app purchase.

Is that in_app_purchase or flutter_inapp_purchase plugin are you referring to ?
If either plugin's example in release mode you run on iOS device and try the scenario, ie, ask user to re-enter the password, and the user refused, does it replicate for you ?

our lock file
  in_app_purchase:
    dependency: transitive
    description:
      name: in_app_purchase
      url: "https://pub.flutter-io.cn"
    source: hosted
    version: "1.0.9"
  in_app_purchase_android:
    dependency: "direct overridden"
    description:
      path: "packages/in_app_purchase/in_app_purchase_android"
      ref: master
      resolved-ref: "8d0382e0903dfe2b8a9b2ee4dd287c29399fda6b"
      url: "git@gitlab.ttyuyin.com:azeroth/app/3rd/official/plugins.git"
    source: git
    version: "0.1.6"
  in_app_purchase_ios:
    dependency: transitive
    description:
      name: in_app_purchase_ios
      url: "https://pub.flutter-io.cn"
    source: hosted
    version: "0.1.4"
  in_app_purchase_platform_interface:
    dependency: transitive
    description:
      name: in_app_purchase_platform_interface
      url: "https://pub.flutter-io.cn"
    source: hosted
    version: "1.3.1"

our lock file
  in_app_purchase:
    dependency: transitive
    description:
      name: in_app_purchase
      url: "https://pub.flutter-io.cn"
    source: hosted
    version: "1.0.9"
  in_app_purchase_ios:
    dependency: transitive
    description:
      name: in_app_purchase_ios
      url: "https://pub.flutter-io.cn"
    source: hosted
    version: "0.1.4"
  in_app_purchase_platform_interface:
    dependency: transitive
    description:
      name: in_app_purchase_platform_interface
      url: "https://pub.flutter-io.cn"
    source: hosted
    version: "1.3.1"

It replicate on my test device too.

@flutter-symbolizer-bot https://github.com/flutter/flutter/issues/100116#issue-1169341468 force flutter#v2.8.1 ios release arm64

It replicates on one of our test devices too.(iPhone OS 15.4 (19E241)(iPhone 6s plus))

Are there any specific steps to replicate that you can provide here that we can use and verify at our end too ?

https://github.com/flutter/flutter/issues/100458.    here

- (void)handleTransactionRestoreFailed:(NSError *)error {
  [self.transactionObserverCallbackChannel
      invokeMethod:@"restoreCompletedTransactionsFailed"
         arguments:[FIAObjectTranslator getMapFromNSError:error]];
}

Printing description of error:
Error Domain=SKErrorDomain Code=0 "发生未知错误" UserInfo={NSLocalizedDescription=发生未知错误, NSUnderlyingError=0x2818b5cb0 {Error Domain=ASDErrorDomain Code=500 "Unhandled exception" UserInfo={NSUnderlyingError=0x2818b7b70 {Error Domain=AMSErrorDomain Code=100 "Authentication Failed" UserInfo={NSMultipleUnderlyingErrorsKey=(
    "Error Domain=AMSErrorDomain Code=2 \"\U53d1\U751f\U672a\U77e5\U9519\U8bef\U3002\U8bf7\U518d\U8bd5\U4e00\U6b21\U3002\" UserInfo={NSLocalizedDescription=\U53d1\U751f\U672a\U77e5\U9519\U8bef\U3002\U8bf7\U518d\U8bd5\U4e00\U6b21\U3002}",
    "Error Domain=AKAuthenticationError Code=-7003 \"(null)\""
), NSLocalizedDescription=Authentication Failed, NSLocalizedFailureReason=The authentication failed.}}, NSLocalizedFailureReason=An unknown error occurred, NSLocalizedDescription=Unhandled exception}}}

I use the Objective-C code below and make this crash reproducible on (iPhone OS 15.4 (19E241))
- (void)handleTransactionRestoreFailed:(NSError *)error {
    NSError *underlyingError4 = [NSError errorWithDomain:@"AKAuthenticationError" code:-7003 userInfo:nil];
    NSError *underlyingError3 = [NSError errorWithDomain:@"AMSErrorDomain" code:2 userInfo:@{
        @"NSLocalizedDescription": @"发生未知错误。请再试一次。",
    }];
    NSError *underlyingError2 = [NSError errorWithDomain:@"AMSErrorDomain" code:100 userInfo:@{
        @"NSMultipleUnderlyingErrorsKey": @[underlyingError3, underlyingError4],
        @"NSLocalizedDescription": @"Authentication Failed",
        @"NSLocalizedFailureReason": @"The authentication failed.",
    }];
    NSError *underlyingError = [NSError errorWithDomain:@"ASDErrorDomain" code:500 userInfo:@{
        @"NSUnderlyingError": underlyingError2,
        @"NSLocalizedDescription": @"Unhandled exception",
        @"NSLocalizedFailureReason": @"An unknown error occurred",
    }];
    NSError *createdError = [NSError errorWithDomain:@"SKErrorDomain" code:0 userInfo:@{
        @"NSLocalizedDescription": @"发生未知错误",
        @"NSUnderlyingError": underlyingError,
    }];
  [self.transactionObserverCallbackChannel
      invokeMethod:@"restoreCompletedTransactionsFailed"
         arguments:[FIAObjectTranslator getMapFromNSError:createdError]];
}

what else do you need? @darshankawar

Closing as a duplicate of #100458 since there's more debugging info there.


Error: 'nfcCardScanned' is not a valid EventType

Describe the bug
When scanning an NFC card on my G4 Doorbell Pro I get the following errors in home assistant
2024-12-17 08:43:46.838 DEBUG (MainThread) [uiprotect.data.bootstrap] Validation error processing event:<PHONE_NUMBER>3d5803e40048a9. Ignoring event. Error: 'nfcCardScanned' is not a valid EventType
To Reproduce

Configure https://www.home-assistant.io/integrations/unifiprotect in home assistant. HA version 2024.11.3
Configure an NFC card in Unifi Protect.
Scan card with debug logging enabled in home assistant.

Additional context
No response
Version
6.4.0
Platform
ghcr.io/home-assistant/home-assistant:2024.11.3
Code of Conduct

[X] I agree to follow this project's Code of Conduct.

No Duplicate

[X] I have checked existing issues to avoid duplicates.

How about switching to a Home Assistant version that actually supports this? 😉 https://www.home-assistant.io/blog/2024/12/04/release-202412/#noteworthy-improvements-to-existing-integrations

Thanks I didn't see it in the release notes, I had to roll back to 2024.11.3 because of a bug in 2024.12. I'll try again once the other bug is fixed.

Out of curiosity, which bug?

This issue is causing my server to boot loop.
https://github.com/NabuCasa/hass-nabucasa/issues/761
https://github.com/home-assistant/core/issues/132586


Build nginx image failed in <IP_ADDRESS>,a new deployed environment [REPLACEMENT ISSUE]

The original issue
Id: 1187
Title: Build nginx image failed in <IP_ADDRESS>,a new deployed environment

could not be created.
This is a dummy issue, replacing the original one. It contains everything but the original issue description. In case the gitlab repository is still existing, visit the following link to show the original issue:
TODO

In GitLab by @guyingyan on Nov 8, 2019, 07:49
not deploy env issue

In GitLab by @wknet123 on Nov 8, 2019, 07:49
Network not available by that time.

In GitLab by @sokril on Nov 8, 2019, 08:20
closed

In GitLab by @sokril on Nov 8, 2019, 08:20
assigned to @cuiaq123


Client/attribute ui

This will use the global dataset but set up the initial stage for switching over and making it a smoother transition.
Fixes #437
Old Style:

New Style:

Goals:

Easier to view (List view with clicking on an attribute to edit)
Easier to stay in this mode while looking at multiple tracks/detections
Detections can be created/deleted from this panel (Click the settings icon to enter edit mode and delete, modify or create new attributes)
Streamline attributes for eventual dataset level attribute information stored in the metadata

TODO:

[x] Fix Track interface to update style (Fixed so it properly updates when type changed)
[x] ConfidencePairs needs edit capabilities as well as coloring to quickly indicate types (removing editing for now)
[x] UI Feedback on the new section
[x] Look into better separation of data between items (Did what I could do CSS for current layout, need to look into alternate layouts
[x] Refactor into composition API style for the components instead of old style.
[x] Need to prevent user from adding a new attribute with the same existing name.
[x] Suggestion for static widths with truncated hover names for attributes, will attempt to adjust for this
[ ] tests for the new interface - I think a discussion is needed about how to implement this properly with the different platforms, vuetify and other requirements.
[ ] Determination of how to handle the old UI (Remove it, leave it?  Leaning towards leaving it for right now)
[ ] Wiki update for new UI

Possible Questions and some explanations for feedback:

The Track item was modified for a single display tool for the attribute editor at the top, this was to change some behavior it had.
ConfidencePairs, adding/editing and deleting was left out of this PR, but should be added in a future PR (probably once the sorting is fixed).
I can break up the AttributesPanel.vue into a subsection component something like AttributesPanelSection.vue for tracks/attributes sections because a lot of that is repeated code except for text attribute references and the frame counting.
I know there is what seems to be unnecessary error handling for the attribute creation/saving/deletion, but this is to inform the user of any eventual permission errors in the metaData versions.  (I.E - a user tries to edit the attributes on someone else's dataset)
Suggestion on leaving in the OldAttributesSettings and items or should we just remove the Settings/Attributes panel from the global settings for now.
I don't know how you specifically want to do testing for vuetify components when we have platforms that implement vuetify themselves, or if you want to testing at the platform level.  I figured there might need to be a discussion before doing that, but once we have a template for doing it I will create tests for these components.
Finally do we want to completely remove the older attributes editor/panel or leave it.  We can leave it while we are doing the transition because it still works fine, just with renamed editors to remind myself that eventually it will be removed.

I think the first purpose is really only a result of vuetify input boxes being so obnoxiously bloated and over-engineered.  Perhaps if all these inputs were replaced with their native form equivalents, they wouldn't need to be hidden for this UI to look clean. I think the track list item is a great example of how removing the vuetify input simplified things.

The secondary reason is that you could have a list of disparate things that mean nothing to your specific track.  If there are 20 attributes that can be set and you set index 0,1, 15 to values you then have a whole lot of information that isn't relevant for viewing if you can see all unset data at the same time.  I also didn't want to resort the list of items each time based on what is set.  I think this was a decent middle ground where you have your track level data and you can edit it quickly for set values, but if you want to add more you toggle the visibility (that's why it was a edit icon before).
I do like the native HTML elements more and think they look better.  A bit more annoying to work with (especially the datalist for each text/value input) but it looks cleaner.  The only downside is that the attribute type isn't in there anymore (it used to be the hint for the vuetify input.

Oh, nice.  I like that better too.
I think the form type provides enough info about what types are accepted, but that's just me.

Not ready for review, I want to do the following before it's ready

[ ] Remove Vuetify section from AttributeInput.vue
[ ] Refactor AttributeInput.vue into composition component
[ ] AttributePanel.vue is getting too large, break it up into AttributePanelSection.vue for the Detection/Track attribute sections as well as another section for the Confidence Pairs.  I know it seems like a bit much but I believe it will make it easier to modify in the long run (I think attributes may get more complicated based on some discussions)

I feel a bit better about this system now.  I think this structure is easier to understand and to modify in the future if needed.

Swapped inputs all to native HTML elements instead of using vuetify.  (Little annoying with having multiple datalist items, but it works).
I renamed the main component because it isn't really solely an Attributes Panel.  Renamed it to TracksDetailsPanel.vue.
Refactored the attributes subsections into a single reusable component with mode Detection and Track.  Only real different is the belongsTo key and the display of the frame numbers.  I pass the core Attributes from the server through the parent object so they don't have to each make a request to the endpoint.
Added in the small trackScroll fix for the tracklist (just scrolling to the selected on mount) when switching back and forth from TrackDetailsPanel.

Bug 1
Please let me know if I am misinterpreting this bug.

Datalist is garbage in it's default behavior.  Once an item is selected it won't display the rest of the options, that is why I need to reset during onFocus the value to empty/null.  I believe it's the same reason it is done on the type selection in the trackItem.vue.  It does the same thing as well for MDN's demo implementation of the datalist.  It looks like they recognize this and have an example where you can make it work more like it properly should, but it involves creating your own controls for onClick as well as manually manipulating the css style to get to behave properly.
I can go through and using refs  and onMount bind the necessary elements and adjust css position to get it to work like the MDN demo.  I wanted to get feedback before I go about making my own component.

It does the same thing as well for MDN's demo implementation of the datalist. It looks like they recognize this and have an example where you can make it work more like it properly should, but it involves creating your own controls for onClick as well as manually manipulating the css style to get to behave properly.

Bummer.
I went back and looked again, and this works exactly like the track type dropdown.
I'd say don't worry about it for this PR. The problem is larger in scope than I thought.  Maybe we could log an issue and build our own select component sometime in the future to replace all of them (since track type should work like the mozilla demo too IMO).
Thanks for explaining that.  It isn't ideal for users, but we should maybe take a minute to think if we really want to maintain/support our own v-select

First issue was a bug in the datalist input using a copy of the prop because it needs to be set to nothing when the user clicks on the input so that way the list will properly display.  The tempVal wasn't being modified on new props being set so I added a watcher.
The second issue I feel dumb about.  It was the classic 0 TrackId and not properly checking that the TrackId !== null instead of just testing to see if the trackId is truthy.

The cog wheel issue was because I wasn't using a v-model for the dialog and was using a value check.
The issue with the display not showing up after toggling the visibility was caused by utilizing computed properties and having them update without there being any indication for the computed property to update.  Would require something like watch deep or using refs and manually updating them using functions after an attribute update is called.
There is another option and that is using the similar style to the TrackListItem.vue and the track.revision property.
https://github.com/VIAME/VIAME-Web/blob/master/client/src/components/TrackItem.vue#L58-L80
It looks like it was a created for a similar reason:  Using computed properties derived from a track but the user can edit those tracks and the computed property needs to update properly.  In TrackListItem this is when the user clicks on interpolate, delete Feature or add Feature it causes the buttons to refresh by triggering a refresh of the computed function watching the track.revision property.  I followed this pattern because the function/watching updating felt messy and why not use the system you already built.

I'll find see what I can find.  I imagine it has to do with the v-mousetrap and it's global nature.  I know we had that flag used for the global $prompt, may need to make something that prevents it from triggering if dialogs are open.  Hopefully without having to directly interact with $prompt  This is something we may run into with other areas so I'll look into fixing it.

This should prevent the escape from getting to the global mousetrap handler.

I welcome any change or suggestion to the warning text that is displayed.  That text is only displayed when the user is editing an existing Attribute.  On brand new attributes that won't be displayed.
I modified the logic so that you can overwrite or change names of the currently selected Attribute.  You aren't allowed to duplicate a name that exists when creating a new attribute or when updating a attribute.  I.E. if you have [foo, bar, buzz], you can't name a new attribute to any of them, but you are allowed to edit the current attribute to a different name as long as it isn't one of the existing items.

Sorry, I noticed discrepancies in how the Type datalist in TrackListItem behaves compared to the Attribute version.  This will make it so hitting enter after clicking will display the old value before setting it.
I also added an issue #477  about fixing whitespace inputs for both the Attributes datalist and the TrackListItem Type input.


Action : Set time selection to items without move of edit cursor

From<EMAIL_ADDRESS>on August 13, 2012 23:18:43
I badly need this action. In current behaviour when i set time selection to items it also move edit cursor to beginning of the item. Would be nice to have such action without moving of edit cursor. Im sure others can find it useful as well. For example to be able to select item and time selection at the same time and still place your cursor to any part of the item.
Thanks!
Original issue: http://code.google.com/p/sws-extension/issues/detail?id=502

@swstim This can done via custom action, or with scripting.


Feature Request: Add onChange event

Hi how are you? how to add onChange functionality to return the current second /minute/hour? it would be good because it would help trigger other events according to the current time shown.

yes.. good request.. mine too.  nice control though.  I have to use the stopwatch one until this is added.

Done, Added.


Missing server code

There's no server code to run on AppEngine.

Confirmed I can at least start appengine instance. Resolving.


ComposeUiViewController with nested scrollable column shrinks Column with UIModalPresentationFormSheet

Describe the bug
A clear and concise description of what the bug is.
When using ComposeUiViewController, and setting the modalPresentationStyle of the view controller to UIModalPresentationFormSheet, dragging the form sheet updwards/downwards causes shrinking/stretching of the nested composable scrollable column I place inside it. Also im not able to vertically scroll my column.
Affected platforms

IOS
Versions

Libraries:

Compose Multiplatform version: 1.6.10

Kotlin version: 2.0.0-RC1

To reproduce:
val bottomSheetUIViewController =
        ComposeUIViewController {
            VerticalScrollWithIndependentHorizontalRows()
        }
        bottomSheetUIViewController.modalPresentationStyle = UIModalPresentationFormSheet
        bottomSheetUIViewController.sheetPresentationController?.setDetents(
        listOf(
                    UISheetPresentationControllerDetent.mediumDetent(),
                    UISheetPresentationControllerDetent.largeDetent(),
                )
                )

                UIApplication.sharedApplication.keyWindow?.rootViewController?.presentViewController(
            viewControllerToPresent = bottomSheetUIViewController,
            animated = true,
            completion = {},
        )

 @Composable
fun VerticalScrollWithIndependentHorizontalRows() {
    Column(
        modifier =
            Modifier.fillMaxSize().verticalScroll(verticalScrollState, enabled = true),
    ) {
        repeat(10) { rowIndex ->
            val horizontalScrollState = rememberScrollState()

            Spacer(Modifier.height(30.dp).background(Color.DarkGray))
            Row(
                modifier =
                    Modifier
                        .padding(start = 16.dp, end = 16.dp)
                        .horizontalScroll(horizontalScrollState),
            ) {
                repeat(5) {
                    Box(
                        modifier =
                            Modifier
                                .size(100.dp)
                                .background(Color.Gray),
                    ) {
                        Text("Item $it in row $rowIndex")
                    }
                }
            }
        }
    }
}

Video depicting the bug :
https://github.com/JetBrains/compose-multiplatform/assets/151455263/924b9ce3-0c92-4aca-b55b-5338c5e90431
Additional Warning:
When attempting to scroll in my nested vertically scrollable column, I receive the following logs in Xcode:
DidReceiveMemoryWarning

Video depicting the bug :
https://github.com/JetBrains/compose-multiplatform/assets/151455263/924b9ce3-0c92-4aca-b55b-5338c5e90431

any updates on this issue?

I'll have a look at it soon.

The nested scrolling issue is a separate one:
https://github.com/JetBrains/compose-multiplatform/issues/3806

Not really

The memory warning issues is unrelated. If you see ever-increasing memory consumption, you have a retain-cycle somewhere inside ObjC that Kotlin can't break.

Memory warning doesn't seem related to the repro you posted. Most likely you have a retain cycle between Kotlin and ObjC with a strong reference inside ObjC API that Kotlin can't break.

@elijah-semyonov I dont really see how could that be the case as the prototype app I used to reproduce the bug uses the standard architecture of a multiplatform app where I simply use a ComposeUIViewController from swift, and to this view controller I add the sample code above

Do you mind sharing the whole solution?
"DidReceiveMemoryWarning" means something went terribly wrong.

Can you record it? I fail to reproduce this behavior.

https://github.com/JetBrains/compose-multiplatform/assets/151455263/472c9299-9d61-4987-af14-dcde8d95db49

https://github.com/nilufer32/test

@nilufer32
You've got wrong Compose Version in repro :)
compose = "1.5.11"

Reproduced memory spike though

Memory spike part of the issue should be fixed in https://github.com/JetBrains/compose-multiplatform-core/pull/1390

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Begelundmuller/fix racy runtime test

Fixes the race condition that repeatedly causes race condition tests to fail on merge to main (e.g. this one)

Replaced by https://github.com/rilldata/rill/pull/3810


kvm: fallback to cloud-init aware domain product name

This uses the previously used KVM domain product name when the provided value is null or empty. This ensure backward compatibilty and allow cloud-init to work on KVM+CloudStack setup.
Fixed #9607
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI
[ ] test (unit or integration test code)

@blueorangutan package

@rohityadavcloud a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

@rohityadavcloud sorry I missed this and created #9610. You pick changes from there

Closing in favour of https://github.com/apache/cloudstack/pull/9610#pullrequestreview-2272012279

Packaging result [SF]: ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 10884


python3Packages.pytest-flask: remove support for python 2.7

As stated in its changelog [1], python 2.7 is no longer supported.
[1] https://github.com/pytest-dev/pytest-flask/blob/master/docs/changelog.rst
ZHF: #97479
@NixOS/nixos-release-managers
Fixes https://hydra.nixos.org/build/127652828
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[X] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 100525 1


CapInputStream.java:37-40: CapInputStream should delegate all standard...

Puzzle 254-d68bc52e in src/main/java/org/takes/rq/CapInputStream.java:37-40 has to be resolved: CapInputStream should delegate all standard InputStream calls to it's origin. It's very important in context of closing stream - right code should close the stream but default InputStream implementation just throws IOException... The puzzle was created by Andrey Eliseev on 22-Jan-2016.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code.

@yegor256 milestone set to 1.0 (correct me if I am wrong)

@original-brownbear please go ahead with this task, it's yours

@davvd PR #634 created :)

@davvd PR #634 created :)

@original-brownbear thanks for that

@davvd fix merged, can you please close this ? :)

@davvd ping :)

@yegor256 Closing this issue now...

@ypshenychka please, review this issue for QA compliance, as per par.24

@davvd Quality is good.

@davvd Quality is good.

@ypshenychka thanks!

@original-brownbear paied 10 mins to @ypshenychka for QA review (payment ID is 79317218)
Thanks a lot, I just topped your account for 38 mins, transaction ID AP-5BD63918RA734602U, total time was 67 hours and 42 mins
there is a bonus for fast delivery (m=4062)
added +38 to your rating, now it is equal to +632


Cant use --clusterAuthMode with initdb in docker-compose

When running 3.4 with command --clusterAuthMode and env MONGO_INITDB_ROOT_USERNAME set it throws
BadValue: cannot have x.509 cluster authentication in allowSSL mode. It seems docker-entrypoint.sh does not remove clusterAuthMode when doing its initdb thing.
When moving clusterAuthMode to a config file it works (Not with 3.6 though, gives warning: database is not yet initialized, and "--config" is specified   the initdb database startup might fail as a result!)
This fails for example:
version: '2.1'
services:
  mongodb:
    image: mongo:3.6
    command:
     - '--sslMode'
     - 'requireSSL'
     - '--clusterAuthMode'
     - 'x509'
     - '--dbpath'
     - '/data/db'
     - '--replSet'
     - 'mongo-rs-1'
     - '--sslPEMKeyFile'
     - '/data/certs/servers/mongo/mongodb.pem'
     - '--sslCAFile'
     - '/data/certs/ca/ca.crt'
     - '--sslClusterFile'
     - '/data/certs/servers/mongo/mongodb.pem'
    volumes:
        - ./certs:/data/certs
        - ./db:/data/db
    environment:
      MONGO_INITDB_ROOT_USERNAME: admin
      MONGO_INITDB_ROOT_PASSWORD: apassword

@pelzerim did you use the client certificate to connect to mongo? I'm able to connect to mongo using generated client certificate but I get an error after executing:
db.auth({mechanism: 'MONGODB-X509'});
Error: Could not find user CN=client1,OU=MyClients,O=MongoDB-Cluster,L=Austin,ST=TX,C=US@$external
Any thoughts what could be wrong?

@cxww107 You need to use the $external library:
use \$external db.auth({mechanism: 'MONGODB-X509'});
It is also possible to do this during connection using mongo-shell:
mongo --ssl --sslPEMKeyFile /bla.pem --sslCAFile /ca.key --sslAllowInvalidHostnames --authenticationMechanism=MONGODB-X509 --authenticationDatabase='$external'

@pelzerim correct, I add a user like in documentation. Basically I follow this tutorial: https://www.mongodb.com/blog/post/secure-mongodb-with-x-509-authentication
I have the following certificates:

ca.pem -> intermediate.pem -> ca-chain (chained ca and intermediate)
server certificates x3 (1 pro replica set), clients certificate x 2
Please find my script here https://gist.github.com/cxww107/663615ae8586819d67dcb0d0dfc8a612

When I try to connect to docker container I receive following message:
2018-04-09T20:22:39.713+0200 W NETWORK  [thread1] The server certificate does not match the host name. Hostname: localhost does not match CN: server1
I think that is the problem. But I can't see what I did wrong.

You need to make sure your CN matches your hostname exactly.
The certificate you are creating use the CN=server1 (with incrementing number i assume). Your are running the mongod instance on localhost and thus the mongods hostname is "localhost". To make this development setup work, change your CN to locahost.
In a real setup all mongod instances would not run on the same machine and you would have hostnames for your mongod instances (which in turn would match your certificates CNs). If you would be using docker-compose, the service name is the hostname for example.

The host names should not be an issue as you are ignoring invalid host names both in mongod and in mongo-shell.
Where are you running this script inside the docker container? Then you would be running 3 mongod instances inside one container. What you want with a replica set is one container runnin one mongod each.
Nonetheless did you expose the mongod port to your machine? Also what are the logs for the mongod instance you are connecting to?

You are trying to connect with the client certificate (/data/certs/clients/default.pem) but you started the container with the server certificate (/data/certs/servers/server1.pem). As you did not yet initialize the replica or add any users, your client certificate has no user yet. Try connecting with the servers certificate. (--sslPEMKeyFile /data/certs/servers/server1.pem)

@pelzerim  I start container with server1.pem:

And then I get an error trying to connect with server1.pem:

It seems not working this way as well.

Well, I manage to solve the problem by workaround. Firstly I start mongodb container with authentication disabled using docker-compose, and then I connect to mongodb and run a script to create admin user with subject from its certificate (e.g. "CN=client1,OU=MyClients,O=MongoDB-Cluster,L=Austin,ST=TX,C=US").
In order to restart mongodb in x509 mode, I have to stop container, commit changes in temporary image and start from this image a new container using docker run command with ssl options.
Obviously it is ugly, but it works.

One last thing you should try: Execute into the docker container and then try connecting using mongos with the servers certificate.


Test failure: CacheTagHelper_VaryByCultureComposesWithOtherVaryByOptions

This test fails occasionally with the following error:
Assert.Equal() Failure
           ↓ (pos 1)
Expected: 10
Actual:   14
           ↑ (pos 1)
   at Microsoft.AspNetCore.Mvc.FunctionalTests.HtmlGenerationWithCultureTest.CacheTagHelper_VaryByCultureComposesWithOtherVaryByOptions() in /_/test/Microsoft.AspNetCore.Mvc.FunctionalTests/HtmlGenerationWithCultureTest.cs:line 152
--- End of stack trace from previous location where exception was thrown ---

Other tests within that build may have failed with a similar message, but they are not listed here. Check the link above for more info.
This test failed on 2.2.
CC @mkArtakMSFT
This issue was made automatically. If there is a problem contact ryanbrandenburg.

Please use this workflow to address this flaky test issue, including checking applicable checkboxes and filling in the applicable "TODO" entries:

Is this actually a flaky test?

No, this is a regular test failure, fix the test/product (TODO: Link to commit/PR)
Yes, proceed below...

Is this test failure caused by product code flakiness? (Either this product, or another product this test depends on.)

[ ] File a bug against the product (TODO: Link to other bug)
Is it possible to change the test to avoid the flakiness?

Yes? Go to the "Change the test!" section.
No?

[ ] Disable the test (TODO: Link to PR/commit)
[ ] Wait for other bug to be resolved
[ ] Wait for us to get build that has the fix
[ ] Re-enable our test (TODO: Link to PR/commit)
[ ] Close this bug

Is it that the test itself is flaky? This includes external transient problems (e.g. remote server problems, file system race condition, etc.)

Is there is a way to change our test to avoid this flakiness?

Yes? Change the test!

[ ] Change the test to avoid the flakiness, for example by using a different test strategy, or by adding retries w/ timeouts (TODO: Link to PR/commit)
[ ] Run the test 100 times locally as a sanity check.
[ ] Close this bug

No?

Is there any logging or extra information that we could add to make this more diagnosable when it happens again?

Yes?

[ ] Add the logging (TODO: Link to PR/commit)

No?

[ ] Delete the test because flaky tests are not useful (TODO: Link to PR/commit)

This comment was made automatically. If there is a problem contact ryanbrandenburg.

@NTaylorMullen, can you please look into this? Thanks!

Adding logging. @mkArtakMSFT @ryanbrandenburg how should I mark this issue while we wait for more test failures with added logging?

Personally I would say:

Label it blocked.
Wait a couple days to see if it happens again.
a. If it happens again use your new logs to figure out what's up.
b. If it doesn't close the bug for now, the bot will open a new one when it happens.

@Eilon in case he wants to countermand that workflow. We might work that into the checklist if it's unclear.

CacheTagHelper_VaryByCultureComposesWithOtherVaryByOptions failed with about the same error on master.
This comment was made automatically. If there is a problem contact ryanbrandenburg.

@NTaylorMullen is this the same failure as before? Does the new logging provide useful info?

Well it ruled out the one cause I thought possible 😲 . Now I gotta consider other possibilities.

There were 1 failures with about the same error on master:

CacheTagHelper_VaryByCultureComposesWithOtherVaryByOptions

This comment was made automatically. If there is a problem contact ryanbrandenburg.

@NTaylorMullen - I see one MVC failure on the latest run:
[17:45:45] :	 [Step 3/3]   Mvc                   |   [xUnit.net 00:00:39.36]     Microsoft.AspNetCore.Mvc.FunctionalTests.HtmlGenerationWithCultureTest.CacheTagHelper_VaryByCultureComposesWithOtherVaryByOptions [FAIL]
[17:45:45] :	 [Step 3/3]   Mvc                   |   Failed   Microsoft.AspNetCore.Mvc.FunctionalTests.HtmlGenerationWithCultureTest.CacheTagHelper_VaryByCultureComposesWithOtherVaryByOptions
[17:45:45] :	 [Step 3/3]   Mvc                   |   Error Message:
[17:45:45] :	 [Step 3/3]   Mvc                   |    Unexpected correlation Id, reading values from document:
[17:45:45] :	 [Step 3/3]   Mvc                   |
fr-FR

[17:45:45] :	 [Step 3/3]   Mvc                   |
fr-FR

[17:45:45] :	 [Step 3/3]   Mvc                   |   14
[17:45:45] :	 [Step 3/3]   Mvc                   |
[17:45:45] :	 [Step 3/3]   Mvc                   |       14
[17:45:45] :	 [Step 3/3]   Mvc                   |
[17:45:45] :	 [Step 3/3]   Mvc                   |
[17:45:45] :	 [Step 3/3]   Mvc                   |   Stack Trace:
[17:45:45] :	 [Step 3/3]   Mvc                   |      at Microsoft.AspNetCore.Mvc.FunctionalTests.HtmlGenerationWithCultureTest.CacheTagHelper_VaryByCultureComposesWithOtherVaryByOptions() in /_/test/Microsoft.AspNetCore.Mvc.FunctionalTests/HtmlGenerationWithCultureTest.cs:line 163
[17:45:45] :	 [Step 3/3]   Mvc                   |   --- End of stack trace from previous location where exception was thrown ---

...

[18:04:15] :	 [Step 3/3]   SignalR               |         Finished test ServerThrowsHubExceptionOnStreamingHubMethodArgumentCountMismatch_messagepack_LongPolling_default in 0.0258653s
[18:04:16] :	 [Step 3/3]   SignalR               |   System.Exception: Failed to bind Stream Item arguments to proper type.
[18:04:16] :	 [Step 3/3]   SignalR               |      at System.Threading.Channels.AsyncOperation`1.GetResult(Int16 token)
[18:04:16] :	 [Step 3/3]   SignalR               |      at System.Threading.Tasks.ValueTask`1.get_Result()
[18:04:16] :	 [Step 3/3]   SignalR               |      at Microsoft.AspNetCore.SignalR.Tests.MethodHub.TestTypeCastingErrors(ChannelReader`1 source) in /_/test/Microsoft.AspNetCore.SignalR.Tests/HubConnectionHandlerTestUtils/Hubs.cs:line 231
[18:04:18] :	 [Step 3/3]   SignalR               |   [xUnit.net 00:00:11.49]     Microsoft.AspNetCore.SignalR.Redis.Tests.RedisEndToEndTests.CanSendAndReceiveUserMessagesFromMultipleConnectionsWithSameUser(transportType: LongPolling, protocolName: "json") [FAIL]
[18:04:18] :	 [Step 3/3]   SignalR               |   Failed   Microsoft.AspNetCore.SignalR.Redis.Tests.RedisEndToEndTests.CanSendAndReceiveUserMessagesFromMultipleConnectionsWithSameUser(transportType: LongPolling, protocolName: "json")
[18:04:18] :	 [Step 3/3]   SignalR               |   Error Message:
[18:04:18] :	 [Step 3/3]   SignalR               |    System.TimeoutException : Operation in CanSendAndReceiveUserMessagesFromMultipleConnectionsWithSameUser timed out at /_/test/Microsoft.AspNetCore.SignalR.Redis.Tests/RedisEndToEnd.cs:118
[18:04:18] :	 [Step 3/3]   SignalR               |   Stack Trace:
[18:04:18] :	 [Step 3/3]   SignalR               |      at System.Threading.Tasks.TaskExtensions.OrTimeout[T](Task`1 task, TimeSpan timeout, String memberName, String filePath, Nullable`1 lineNumber) in /_/test/Microsoft.AspNetCore.SignalR.Tests.Utils/TaskExtensions.cs:line 67
[18:04:18] :	 [Step 3/3]   SignalR               |      at Microsoft.AspNetCore.SignalR.Redis.Tests.RedisEndToEndTests.CanSendAndReceiveUserMessagesFromMultipleConnectionsWithSameUser(HttpTransportType transportType, String protocolName) in /_/test/Microsoft.AspNetCore.SignalR.Redis.Tests/RedisEndToEnd.cs:line 118
[18:04:18] :	 [Step 3/3]   SignalR               |   --- End of stack trace from previous location where exception was thrown ---

And @anurse , I'm also seeing a bunch of these SignalR + Redis failures:
[18:05:04]E:		 [VSTest] Runner error: [xUnit.net 00:00:31.73]     Microsoft.AspNetCore.SignalR.Redis.Tests.RedisEndToEndTests.CanSendAndReceiveUserMessagesFromMultipleConnectionsWithSameUser(transportType: LongPolling, protocolName: "messagepack") [FAIL]

@anurse - any idea on that?

@Eilon Those are filed on SignalR by the bot

Ah OK so just @NTaylorMullen needs to look at the MVC stuff.


docs: remove issues.txt

Please remove the issues.txt file in the root folder as it is just a test file

done but not auto?


Add documentation

Add documentation for Address, Country, and User models.

@googlebot I signed it!

@googlebot I signed it!


add pt.json

Hello, @ViPeR5000,
Thanks a lot for your contribution! 👍 And sorry for the delay in merging it


User profile state not saved. Switching to loading / undefined state on route change.

The example works but on every route change, the user profile component's user from useUser is shortly undefined and the component shoes "...Loading" even though the session and cookie still exists.
I am using NextJS 13 with new app directory.
Is there a way keep the logged in state?

Hi @jackblackCH, thanks for raising this and apologies for the delay. The app directory introduced with Next.js 13 is currently in beta, and Vercel does not recommend using it in production. As such, this SDK does not support it yet.

@Widcket just as an fyi, the url linked to here now says

Next.js 13 and the pages directory are stable and ready for production.


Kotlin support

Hello,
I wanted to ask if it is planned Kotlin support for Spring cloud contract. Like for example autogenaring a test on the provider side that is in Kotlin? Thank you in advance!

duplicate https://github.com/spring-cloud/spring-cloud-contract/pull/561


New-DbaDbSequence - Don't use Test-Bound with defaults

Type of Change

[x] Bug fix (non-breaking change, fixes # )
[ ] New feature (non-breaking change, adds functionality, fixes # )
[ ] Breaking change (effects multiple commands or functionality, fixes # )
[ ] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[ ] Pester test is included
[ ] If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

StartWith was not set when not explicitly set by parameter.

Open issue: The command returns just the plain SMO, all the other commands add ComputerName, InstanceName and SqlInstance and have a default view. That should be added here as well.
@lancasteradam : If you like, you can just close this pull request and open your own with all the necessary changes.

The test fails because you are outputting the created object and not the object from the database. You cannot output $newSequence it has to output the sequence object found in the database (after it is created), that is how the test is written.

Test still fails and I don't have any idea. Can you please have a look @wsmelton - thanks.

The integration tests for min and max need these small changes shown below. This is because of the bugfix being made in this PR for the StartWith param in New-DbaDbSequence.ps1.
New-DbaDbSequence.Tests.ps1
Line 109:
$sequence = New-DbaDbSequence -SqlInstance $instance2 -Database $newDbName -Name "Sequence_$($randomForMinValues)" -Schema "Schema_$random" -MinValue $minValue -StartWith $minValue
and line 118:
$maxValues = @(10000, 100000)
For the New-DbaDbSequence.ps1 return object and default view this code could potentially be used:
$newSequence = $db | Get-DbaDbSequence -Name $newSequence.Name -Schema $newSequence.Schema

Add-Member -Force -InputObject $newSequence -MemberType NoteProperty -Name ComputerName -value $db.Parent.ComputerName
Add-Member -Force -InputObject $newSequence -MemberType NoteProperty -Name InstanceName -value $db.Parent.ServiceName
Add-Member -Force -InputObject $newSequence -MemberType NoteProperty -Name SqlInstance -value $db.Parent.DomainInstanceName

Select-DefaultView -InputObject $newSequence -Property ComputerName, InstanceName, SqlInstance, Name, Schema, DataType, StartValue, IncrementValue, MinValue, MaxValue, CacheSize, IsCycleEnabled

Hi Adam, thanks for the hint, that changes to the test helped. Now only unrelated test fail.
The Add-Member and Select-DefaultView is not needed, that is already handled by the Get-DbaDbSequence - that is why we use the Get- to get the object.

Thank you both! Re-running tests now 👍🏼

All tests pass, merging! 😊


production.ERROR: TypeError: Cannot read properties of undefined (reading 'url')

Hello,
Everything worked fine, but since we upgraded the NPM packages a few times, or after we migrated into a load balancer infrastructure (not sure what really affected it) it started breaking.
This happens on most requests, but there's also a fraction where it does not happen. Running last Laravel 11 and Inertia 2.0 (although it started happening before the upgrade to Inertia 2.0 so it's probably not the reason).
So I just get a hydration error on every page load on production and a backend log from Inertia:
production.ERROR: TypeError: Cannot read properties of undefined (reading 'url')

at ssrRoute (file:///home/forge/.../releases/20250101010459/bootstrap/ssr/ssr.js:5988:46)
Jan 01 03:17:50

at Footer$1 (file:///home/forge/.../releases/20250101010459/bootstrap/ssr/ssr.js:489:43)

Maybe it after started happening after an edit to some component, like the Footer here. But it's pretty simple:
import { Logo } from '@/components/logo';
import { Link } from '@inertiajs/react';
import useRoute from '@/hooks/use-route';
import { FaEnvelope } from 'react-icons/fa6';

const Footer = () => {
  const route = useRoute();
  return (

      <Logo />

        <FaEnvelope className="mr-2" />{' '}

          Contact us at <a href="mailto:contact<EMAIL_ADDRESS>

© 2024 .... All rights reserved.

          <Link href={route('privacy')} className="whitespace-nowrap">
            Privacy Policy
          </Link>
          <Link href={route('terms')} className="whitespace-nowrap">
            Terms of Service
          </Link>

  );
};

export default Footer;

HandleInertiaRequest:
'ziggy' => fn() => [
    ...(new Ziggy)->toArray(),
    'location' => $request->url(),
],

ssr.tsx:
/* eslint-disable */
      const ssrRoute = (
        name: string,
        params: Record<string, any>,
        absolute: boolean,
        config: Record<string, any>,
      ) => {
        return route(name, params, absolute, {
          ...(page.props as any).ziggy,
          location: new URL((page.props as any).ziggy.url),
          ...config,
        });
      };

      /* eslint-enable */

      return (
        <RouteContext.Provider value={ssrRoute as any}>

Using "ziggy-js": "^1.8.1", with "@types/ziggy-js": "^1.8.0", and "@inertiajs/react": "^2.0.0",
Also, this rarely happens on the local environment. Staging also does not throw it on every request (but sometimes it does). Production is almost 100/100.
Any ideas?

hmm hard to say from just looking at this, can you duplicate your prod environment so you can debug further? adding some log statements?
guessing it's this line here based on your error
location: new URL((page.props as any).ziggy.url),

can you log the page props to see whats in there and why the ziggy prop is undefined?

Hmm, that's an interesting finding. I wonder why that can happen. Before every url error there's this:
{ status: 404, auth: { user: null } }
TypeError: Cannot read properties of undefined (reading 'url')
    at ssrRoute (file:///home/forge/domain.com/releases/20250101023825/bootstrap/ssr/ssr.js:5988:46)
    at Footer$1 (file:///home/forge/domain.com/releases/20250101023825/bootstrap/ssr/ssr.js:489:43)
    at renderWithHooks (/home/forge/domain.com/releases/20250101023825/node_modules/react-dom/cjs/react-dom-server-legacy.node.development.js:5662:16)
    at renderIndeterminateComponent (/home/forge/domain.com/releases/20250101023825/node_modules/react-dom/cjs/react-dom-server-legacy.node.development.js:5736:15)
    at renderElement (/home/forge/domain.com/releases/20250101023825/node_modules/react-dom/cjs/react-dom-server-legacy.node.development.js:5961:7)
    at renderNodeDestructiveImpl (/home/forge/domain.com/releases/20250101023825/node_modules/react-dom/cjs/react-dom-server-legacy.node.development.js:6119:11)
    at renderNodeDestructive (/home/forge/domain.com/releases/20250101023825/node_modules/react-dom/cjs/react-dom-server-legacy.node.development.js:6091:14)
    at renderNode (/home/forge/domain.com/releases/20250101023825/node_modules/react-dom/cjs/react-dom-server-legacy.node.development.js:6274:12)
    at renderChildrenArray (/home/forge/domain.com/releases/20250101023825/node_modules/react-dom/cjs/react-dom-server-legacy.node.development.js:6226:7)
    at renderNodeDestructiveImpl (/home/forge/domain.com/releases/20250101023825/node_modules/react-dom/cjs/react-dom-server-legacy.node.development.js:6156:7)
    ```

I wonder what is that 404 call on every page load. Can't find it any 404 requests in the networks.


Allow permissive licenses only for PyAnsys packages

Resolves #47

This will require further iterations. The workflow is set in place but it is not working properly. There is a bug on their side. See https://github.com/actions/dependency-review-action/issues/182


Remove Edge shims

It seems that the scripts included for compatibility with Edge are unnecessary. Edge provides the browser namespace which is compatible with everything this extension uses.

Browser
chrome
browser

Chrome
API using callbacks
N/A

Firefox
API using callbacks
API using promises

Edge
Incompatible object defining only chrome.app.getDetails()
API using callbacks

Based on the above table we want to use chrome on Chrome/Firefox and browser on Edge. I've done this by checking for the existence of chrome.runtime and falling back to browser if it's unavailable.
As for the actual WebExtension API features this extension uses, I've noted the compatible version numbers listed on MDN.

Feature
Chrome
Edge
Firefox

storage.sync
Yes
15
53

storage.local
Yes
14
48*

tabs.create
Yes
14
45

runtime.sendMessage
26
14
45

runtime.lastError
Yes
Yes**
47

*45 in background scripts, 48 in content scripts.
**MDN says no, but Microsoft claims otherwise. The shims do proxy directly to runtime.lastError so I think it is supported.
This extension should perhaps fallback to local storage when sync is unavailable - I think that would make it compatible with Opera - but that's for another PR.
Tested in Edge 42.17134.1.0, Firefox 62.0 and Chrome 69.0.3497.100

Thanks @alexbarrett! I really like your PRs!
I left one minor comment, but otherwise LGTM.

Thanks @infokiller. I've addressed your feedback.


chore: re-export keyframes component from chakra

This exposes the keyframes component used in chakra ui in Northlight.

The tests have passed, not sure why github is not updating

Maybe it's the mac update or you need to restart your router.


[WIP] Agda build support

The first two commits should be pretty uncontroversial.
The third removes a wrapper shell script intended for "public use". But the generated shell scripts were not used elsewhere in nixpkgs, nor are they terribly useful for Emacs integration (as was the intention IIUC) as that was broken for other reasons.
I replaced the script with a simple environment variable that has the (resolved) agda binary "curried" with the build flags generated by the build support.
With https://github.com/NixOS/nix/issues/534 we can have tools shell out to
nix-shell --command \$wrappedAgda -- <args...>

As a proof of concept I ran
nix-shell --command '$wrappedAgda --interactive'

by hand and everything worked correctly.
Finally, making a script accessible to emacs like:
#/bin/sh
nix-shell --command '$wrappedAgda '"$@"

and having it call that also might work today. agda-mode got as far as checking and accepting the version of the binary, but then the process died for some reason.

I'll rebase if this looks good--I've done it locally but just wanted to push what I actually tested. The only "conflict" is haskell-ng -> haskell on the line below in all-packages.nix

First 2 commits OK.
The last commit I'm not sure about. For example, I used agda --latex manually many times (after running eval "$configurePhase" and that's what my Makefiles end up calling. Is there a good reason to not use a wrapper? Most tools expect that they are able to call agda.
The reason for wrapper it being in configurePhase is so we can still get at the underlying Agda binary if we want to.

Ok, now the wrapper is there for anybody that wants it. This could be improved if extras could be put in defaults without it getting built.

Ok, extras are handled more sanely now. And downstream can use them too (e.g. nix-env -p myAgdaLib.agdaWrapper). I'll need to check which specific libraries will need the wrapper or AGDA_LIBRARY_PATH, but I think the architecture here is pretty good. We could even add a latex derivation to extras too.

Did you test that it works when compiling libraries that depend on other libraries? Let's say, categories.

Yeah I need to do more testing--mainly wanted to see if you liked the design. I tested libraries that depend on stdlib for the original third commit, but only that the expressions evaluate properly with the revision. I'll build categories now and report back.

It built! [It wasn't ridiculously slow, I was just doing other things in the mean time and didn't notice it finished.]

Then it's fine with me but I'll wait a bit with merging it, I want to give it a spin myself.
If you're interested, there are few more things to do in the meantime. For example in practice I noticed that we should probably be adding the /share/agda to entries AGDA_PACKAGE_PATH. Another one was that everything in buildDepends gets added to this (and the -i in wrapper but if we address the previous issue and factor the list out, they'll be using the same paths). This means that if we put for example texLive to buildDepends, we blindly pass it to -i and put it in AGDA_PACKAGE_PATH. Two possible solutions would be to either filter out entries where {foo}/share/agda doesn't exist or to have a separate field for Agda dependencies. I know that ghcWithPackages does (or used to) filter out things which aren't Haskell libraries.
You could also look through the Travis log and see what it's upset about. It seems a library we packaged is now behind some authentication system. If Travis could come up as green for this PR that'd make me feel better.
But if you're not interested in doing that then that's perfectly fine, I don't expect it. Sit tight and I'll merge as soon as I can test.

I'm a bit busy now for the next few days (or at least today and tomorrow), but I'd be happy to work on those next few things once I have time.

Ok, I think I addressed your concerns. I also ripped some unused options, and removed "-i ." by default. Waiting on Travis now to see what libraries I need to fix.

Also propagatedUserEnvPkgs seems sketchy/extraneous.

Something is messed up, check travis.

Yeah my removing -i . failed miserably.

Hmm, it's rebuilding Agda itself for some reason, and thus the test timed out.

Replace builtins.hasAttr with ?. Also, on my machine it now no longer attempt to rebuild Agda, so hopefully travis won't try either and the tests will finish.

@Fuuzetsu It didn't say it timed out, but the log sure looks like the build was killed externally. I just ran nix-build -A AgdaSheaves -A agdaPrelude -A pretty -A TotalParserCombinators -A bitvector -A agdaBase -A AgdaStdlib '<nixpkgs>' common on my machine, and everything built just fine.

Don't know why it got killed but don't worry about it I guess. I think I should have time to test and merge all this tomorrow, thank you for your work.

Hm, I'm not sure how to use extras. Can you give an example? Let's say I'm hacking a library inside nix-shell and I want to get at the AGDA_PACKAGE_PATH var.

@Fuuzetsu Oh, I was going to point out my commit message documenting it, but it turns out it is totally wrong. The basic idea is do add the stuff from .extras to the derivation so the builder sees it. You can (actually) do that like this:
myAgdaLibrary.overrideDerivation (self: { inherit (self.extras) AGDA_PACKAGE_PATH; })

I'd be open to adding a function to automated this (give it a list of Ids to inherit for example). Also, if there was some stock subset of .extras that was generally considered useful, I could make a passthru'd .env a la Haskell NG. I only just learned about .env, hence I didn't go that route before.

.env sounds good, if you can cook something up I'd be happy to have a look

Which things do you want in it?

Just a way to get AGDA_PACKAGE_PATH and to generate the wrapper.


Requirements.txt and unreasonable results

Hey,
I was trying to use the model and some issues came up.

The first challenge I faced is that the requirements.txt file is missing, therefore the manual package installation was a little bit tricky sometimes (newest version of tensorflow does not work for instance)
The second and bigger problem is that I tried the forward test by using the pre-trained model. I followed the instructions (copied my audio into the right folder, run the inference.py), however the prediction for both fake and real recordings were really low values. I even tried out the pre-trained model with your real voice data and it still gave only a probability of 0.3% of the real clip is being real which is supposed to be close to 100%...

The only error I got is: bash: scp_spectrogram.sh: No such file or directory
Also I'm not running the Atlas for trying out the pre-trained model which I'm not sure is correct or not.

Do you have any suggestion what do I miss/should install, modify to get more reasonable probabilities?
Thanks!

Hello,
Thanks for your note:

Now you should see requirements.txt inside code/ folder. It was due to .gitignore that all the text files were ignored automatically in git push

We are still trying to improve our model as we speak. If you observe, the pre-trained model performs very well on the training and validation set (i.e. above 0.9 f1-score) but not so much good on test set or any other arbitrary audio file. This shows that the pre-trained model is overfitting on the algorithms that were used to produce fake voices in train and validation set.

We would like to encourage other users to improve upon this model by performing hyperparam search to get a more generalized model. A couple of things to try are:
a) Try to use regularization techniques
b) Try to add more audio data to train and possibly validation set
c) Try different model architectures (i.e. using conv1d on raw audio instead of spectrograms, or using LSTMs etc.)
d) Analyze the pre-trained model on different audio clips to find patterns in the spectrograms where the model seems to overfit.
c) The classes are highly imbalanced in the original dataset: 90% fake and 10% real audio clips. So, the model generally has more tendency to predict audio signals to be fake. I took some steps to overcome these by augmenting the data by using nlpaug library (see in utils.py) but it can be further improved by adding more dataset.
You should not get the  bash: scp_spectrogram.sh: No such file or directory error anymore since I removed that line. It was only there for some remote debugging processes
You can try pre-trained model without Atlas and that doesn't change anything.
Please see my suggestions in order to get a better model and let me know your thoughts.
Thanks!

Hi All,
I did not have NVIDIA GPU on my local machine. I am trying to run the code on Intel GPU but did not got success.
I wanted to confirm that can I run this code on Intel GPU or not ?
Many Thanks,
Kinjal

Hi Team,
I am little skeptical about whether I can run the code on Windows 10 PRO version or not.
Please share your thoughts.
Thanks,
Kinjal

Hi Kinjal, thanks for your question. Yes you should be able to run the code on Windows 10 but you might need to modify some terminal commands as the windows commands are little bit different than Mac and Linux.

Thanks for your response.
However, I have managed to install Foundation Atlas in local, but facing
issue with this command: atlas-server start
I am sharing trace here:
(env) C:\Users\ram\Desktop\Foundation_Atlas>atlas-server start
2020-03-12 20:41:23,981 - Foundations Atlas Server - INFO - Starting
atlas-ce-tracker service...
2020-03-12 20:41:25,808 - Foundations Atlas Server - INFO - Started
atlas-ce-tracker service
2020-03-12 20:41:26,072 - Foundations Atlas Server - INFO - Starting
atlas-ce-archive-server service...
2020-03-12 20:41:27,493 - Foundations Atlas Server - INFO - Started
atlas-ce-archive-server service
2020-03-12 20:41:27,771 - Foundations Atlas Server - INFO - Starting
atlas-ce-rest-api service...
2020-03-12 20:41:29,431 - Foundations Atlas Server - INFO - Started
atlas-ce-rest-api service
2020-03-12 20:41:29,648 - Foundations Atlas Server - INFO - Starting
atlas-ce-gui service...
2020-03-12 20:41:31,629 - Foundations Atlas Server - INFO - Started
atlas-ce-gui service
2020-03-12 20:41:31,638 - Foundations Atlas Server - ERROR - Cannot start
atlas-ce-local-scheduler
2020-03-12 20:41:31,638 - Foundations Atlas Server - ERROR - Please try
re-installing Atlas Server via the installer
2020-03-12 20:41:31,639 - Foundations Atlas Server - INFO - Stopping
atlas-ce-gui service...
2020-03-12 20:41:42,677 - Foundations Atlas Server - INFO - Stopped
atlas-ce-gui service
2020-03-12 20:41:42,678 - Foundations Atlas Server - INFO - Removing
atlas-ce-gui service...
2020-03-12 20:41:42,726 - Foundations Atlas Server - INFO - Removed
atlas-ce-gui service
2020-03-12 20:41:42,727 - Foundations Atlas Server - INFO - Stopping
atlas-ce-rest-api service...
2020-03-12 20:41:44,611 - Foundations Atlas Server - INFO - Stopped
atlas-ce-rest-api service
2020-03-12 20:41:44,612 - Foundations Atlas Server - INFO - Removing
atlas-ce-rest-api service...
2020-03-12 20:41:44,656 - Foundations Atlas Server - INFO - Removed
atlas-ce-rest-api service
2020-03-12 20:41:44,657 - Foundations Atlas Server - INFO - Stopping
atlas-ce-archive-server service...
2020-03-12 20:41:46,257 - Foundations Atlas Server - INFO - Stopped
atlas-ce-archive-server service
2020-03-12 20:41:46,258 - Foundations Atlas Server - INFO - Removing
atlas-ce-archive-server service...
2020-03-12 20:41:46,312 - Foundations Atlas Server - INFO - Removed
atlas-ce-archive-server service
2020-03-12 20:41:46,313 - Foundations Atlas Server - INFO - Stopping
atlas-ce-tracker service...
2020-03-12 20:41:47,382 - Foundations Atlas Server - INFO - Stopped
atlas-ce-tracker service
2020-03-12 20:41:47,382 - Foundations Atlas Server - INFO - Removing
atlas-ce-tracker service...
2020-03-12 20:41:47,431 - Foundations Atlas Server - INFO - Removed
atlas-ce-tracker service
2020-03-12 20:41:47,432 - Foundations Atlas Server - INFO - Removing
foundations-atlas network service...
2020-03-12 20:41:47,768 - Foundations Atlas Server - INFO - Removed
foundations-atlas network service...
Please help for me to resolve this error.
Many Thanks,
Kinjal
On Fri, 13 Mar 2020 at 07:25, Sachin Rana<EMAIL_ADDRESS>wrote:

Closed #1
https://github.com/dessa-research/fake-voice-detection/issues/1.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dessa-research/fake-voice-detection/issues/1#event-3125124867,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIX5NTOYHLGLSO5BSZDDAL3RHGHAVANCNFSM4I56CS4Q
.

Hello,
I tried to install the requirements.txt file but shows an error in the line " import numpy as np" saying no module found as "numpy" .
Kindly help me resolve this issue.
Regards,
Harshit


link "https://github.com/Microsoft/ConversationLearner-WebChat" [conversationlearner-webchat] is not valid anymore

link "https://github.com/Microsoft/ConversationLearner-WebChat" [conversationlearner-webchat] is not valid anymore

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

ID: 18236fc7-32f8-e3d1-3f3c-7a2be9562d08
Version Independent ID: 28dc0d5e-315e-be81-47d5-b80e170000f4
Content: How to create a Conversation Learner model using Node.js - Microsoft Cognitive Services - Azure
Content Source: articles/cognitive-services/Labs/Conversation-Learner/quickstart.md
Service: cognitive-services
GitHub Login: @v-jaswel
Microsoft Alias: v-jaswel

@lauraRuzicka Hi, this link is valid but the moderator has set it as private, sorry for all inconveniences. Let me make sure how the repo should be.
@v-jaswel Hi, this repo which in the document is set as private. Is it in a preview period? Or just a wrong operation? Thanks.

Hi @lauraRuzicka, I have a question out to the Conversation Learner PM about this and will let you know as soon as I hear back.


Fix #217 bundle has root folder

This removes root folder which shouldn't be in the bundle. Also adds a new test to cover this.

fixed #217


Integrate dsub

Opening this PR in draft mode for now while @nisthapanda work through collaborating on documentation updates and other testing.

Some additional context: we started using dsub for All of Us

Within the Researcher Workbench, the Google Cloud Life Sciences API is the executor of dsub tasks.

However

Cloud Life Sciences is deprecated and will no longer be available on Google Cloud after July 8, 2025.

It's not yet clear what All of Us will do to support migration. I would still like to proceed with merging in this code though, but we may be okay keeping documentation light if our use case is already deprecated.
See also https://github.com/Reed-CompBio/spras/issues/130.


feat(command): Support object value type in Set Command

Make the Set Command payload to allow object value type parameters.
Closes #3753
Signed-off-by: bruce<EMAIL_ADDRESS>

If your build fails  due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[x] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I am not introducing a new dependency (add notes below if you are)
[ ] I have added unit tests for the new feature or bug fix (if not, why?) Update the unit test to reflect the change
[x] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[ ] I have opened a PR for the related docs change (if not, why?) Update the Swagger API in this PR

Testing Instructions

Clone the repo or pull the branch from:

edgex-go https://github.com/edgexfoundry/edgex-go/pull/3762
sdk-go https://github.com/edgexfoundry/device-sdk-go/pull/1038
core-contracts https://github.com/edgexfoundry/go-mod-core-contracts/pull/676

Run core-service and simple-device with specified core-contracts branch
Execute Set command
Execute Read command to inspect the result
Query event API to inspect the reading result

New Dependency Instructions (If applicable)

Resolved the conflicts.


CI: Elastix docker image build and push to docker hub

The CI now builds a docker image of every tagged elastix commit. The docker image is uploaded to dockerhub and labeled by it's tag.

Looks good! Perhaps Sebastian can review. This only triggers on the master branch?

This only triggers on tagged branches, so in the case of elastix, that will indeed only be the master branch.
@Svdvoort this is my implementation of the docker image build and push. I decided to make 1 image for both elastix and transformix. Would you mind giving feedback on the implementation?

Looks good overall! Some very minor suggestions, but everything should work as-is. Having an 'on release' action to tag the docker images automatically when a release takes place would be nice, I think most users will only use the stable tagged releases? Of course, you can also build these manually if you want to test these images more thoroughly before pushing a stable release.

Thanks a lot for the feedback @Svdvoort. An update is on it's way.


babel.config.js error

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[X] I have tried creating a repro with https://new.docusaurus.io.
[X] I have read the console error message carefully (if applicable).

Description
Hello , I want to ask what I need to solve
Uncaught ReferenceError: require is not defined
Error
So, I add code in  babel.config.js
The code is as follows, no error was reported during development, and an error was reported during construction
module.exports = {
  presets: [
    require.resolve('@docusaurus/core/lib/babel/preset'),
    '@babel/preset-env',
    ['@babel/preset-react', { runtime: 'automatic' }],
  ],
};

Error
Docusaurus Node/SSR could not render static page with path "/404.html" because of following error:

TypeError: (0 , docsClientUtils_1.getActivePlugin) is not a function
    at useActivePlugin (main:4377:548)
    at Navbar (main:5273:2821)
    at d (main:50423:498)
    at bb (main:50426:16)
    at a.b.render (main:50432:43)
    at a.b.read (main:50431:83)
    at Object.exports.renderToString (main:50442:138)
    at _callee2$ (main:4333:2450)
    at tryCatch (main:54378:40)
    at Generator.invoke [as _invoke] (main:54609:22)

Docusaurus Node/SSR could not render static page with path "/blog" because of following error:

Steps to reproduce
https://stackblitz.com/edit/github-ygdu6n?file=babel.config.js
npm run build

Expected behavior
can build no error
Actual behavior
Docusaurus Node/SSR could not render static page with path "/404.html" because of following error:

TypeError: (0 , docsClientUtils_1.getActivePlugin) is not a function
    at useActivePlugin (main:11306:548)
    at Navbar (main:12202:2821)
    at d (main:62371:498)
    at bb (main:62374:16)
    at a.b.render (main:62380:43)
    at a.b.read (main:62379:83)
    at Object.exports.renderToString (main:62390:138)
    at _callee2$ (main:11262:2450)
    at tryCatch (main:66326:40)
    at Generator.invoke [as _invoke] (main:66557:22)

Docusaurus Node/SSR could not render static page with path "/blog" because of following error:

TypeError: (0 , docsClientUtils_1.getActivePlugin) is not a function
    at useActivePlugin (main:11306:548)
    at Navbar (main:12202:2821)
    at d (main:62371:498)
    at bb (main:62374:16)
    at a.b.render (main:62380:43)
    at a.b.read (main:62379:83)
    at Object.exports.renderToString (main:62390:138)
    at _callee2$ (main:11262:2450)
    at tryCatch (main:66326:40)
    at Generator.invoke [as _invoke] (main:66557:22)

Docusaurus Node/SSR could not render static page with path "/blog/archive" because of following error:

Your environment

Public source code:
Public site URL:
Docusaurus version used:
Environment name and version (e.g. Chrome 89, Node.js 16.4):
Operating system and version (e.g. Ubuntu 20.04.2 LTS):
Mac os big sur 11.5
Chrome 89, Node.js 16.4

Reproducible demo
Thanks
Self-service

[ ] I'd be willing to fix this bug myself.

From the discussion on Discord, the OP is trying to use the React 17's automatic JSX runtime to omit the import React from 'react'; line.
I'm somewhat sure that the bug is caused by a naive TS transpilation in our own docs plugin that causes Node require() / exports to leak into client side. The default Babel configuration makes this go away unnoticed.

@mtrucc After working on the Stackblitz repro, I think the problem is not caused by the runtime: 'automatic' but rather preset-env. Our own preset already comes with preset-env that's properly configured, so there's no need to include another copy of this preset.
So what's causing the error exactly? It's Babel being unable to interpret the target of transpilation. Server-side and client-side configuration are different:
https://github.com/facebook/docusaurus/blob/713d14569edde007a00d7f9c1e23943f003a625b/packages/docusaurus/src/babel/preset.ts#L18-L38
On server-side, we have to tell preset-env that it is node and we can use Node-specific syntax (e.g. require to import functions). Therefore, just adding an option fixed the transpilation problem:
module.exports = {
  presets: [
    require.resolve('@docusaurus/core/lib/babel/preset'),
-   '@babel/preset-env',
+   ['@babel/preset-env', { target: { node: 'current' } }],
    ['@babel/preset-react', { runtime: 'automatic' }],
  ],
};

Whether that's sufficient to fix all problems I'm not sure, but it does seem to make build succeed in your repo. After all, you don't really need the preset-env because we already ship our own preset packed with this.


bot.listen throws Net::ReadTimeout

Since bot.listen uses long polling, read timeouts are to be expected when there's no activity.
In that regard, this should be hidden from the user of the library and poll request automatically restarted.
Was expecting this behaviour initially, and learned it wasn't, the hard way — bot crashed when nobody was looking at it and it stayed down for 8 hours until I woke up to see the Net::ReadTimeout got thrown from bot.listen.
To make my bot persistent, I had to update the main loop to look like this:
while true
    begin
        bot.listen do |message|
            logfrom message
            case message.text
            when /^\/pony\b/
                derpibooru_bot.pony(message)
            when /^\/(start|help)\b/
                derpibooru_bot.sendtext(message, "Hello! I'm a bot by @hmage that sends your daily fix of ponies.\r\n\r\nType /pony and I'll send you a top scoring
            end
        end
    rescue Net::ReadTimeout => e
        logerror e
    end
end

If adding automatic restart is not an option, update all examples to handle Net::ReadTimeout exception, because it will happen after a while when bot is supposed to be 24/7.

Thanks for the report. Yes, it definitely should be handled by the gem. I'll make changes a soon as possible.

Thank you, much appreciated.

Added exception handling in 0.2.6, please update your stuff.