Access violation in Python 3.9

Hello,
To be quite honest, I'm not sure whether to report it here or on comtypes GitHub page, as I'm not that familiar with either of the repositories, and importing comtypes by itself works just fine.
Expected Behavior
Importing pywinauto works without issues
Actual Behavior
Importing pywinauto causes access violation issues on Windows
Steps to Reproduce the Problem

Install Python 3.9
Install pywinauto
Import pywinauto in your script

Short Example of Code to Demonstrate the Problem
import faulthandler
import pywinauto
faulthandler.enable()

which then results in the following:
Windows fatal exception: code 0x80010108

Thread 0x00002358 (most recent call first):
  File "C:\Python39\lib\site-packages\comtypes\__init__.py", line 180 in _shutdown
Windows fatal exception: code 0x80010108

Thread 0x00002358 (most recent call first):
  File "C:\Python39\lib\site-packages\comtypes\__init__.py", line 180 in _shutdown

Specifications

Pywinauto version: 0.6.8
Python version and bitness: 3.9.5 x64
Platform and OS: Win 10x64

Wow! This is interesting case. It may be comtypes' issue, but I'm not sure 100%. Anyway comtypes repo already has issue https://github.com/enthought/comtypes/issues/212 which is probably connected or a root cause of it. I have plans to look at it in June or July.
Also I'm curious why do you need C level handler instead of more pythonic module traceback?

comtypes loads UIAutomation.dll into memory while doing import pywinauto. That's why I'm thinking it's comtypes' issue anyway. Just FYI. It's OK to track this issue in pywinauto repo as well. I have admin rights in both.

Well, the faulthandler was only used to detect what actually happened.
We recently switched our automation to Python 3.9 and suddenly, even while the script ended with sys.exit(0), it would always end with<PHONE_NUMBER> which translated to 0xc0000005 which translated to windows code for Access Violation.
Thus I searched far and wide and then stumbled on faulthandler by accident, which lead me to the end of this rabbit hole.
Thanks for the info!

For the time being, I thought of a workaround of just atexit.unregister(comtypes._shutdown).
How unsafe is it?

I didn't dive into comtypes deep enough. If it works, it seems you have no other choice for now. Thanks for letting me know.

Well, the minimal reproducing script looks so:
import faulthandler
from comtypes.client import GetModule
import comtypes
UIA_dll = GetModule('UIAutomationCore.dll')
iuia = comtypes.CoCreateInstance
(
    comtypes.gen.UIAutomationClient.CUIAutomation().IPersist_GetClassID(),
    interface=comtypes.gen.UIAutomationClient.IUIAutomation, clsctx=comtypes.CLSCTX_INPROC_SERVER
)
root = iuia.GetRootElement() # this line is required for crash
faulthandler.enable()

The fix with atexit handlers also works for me. It's interesting that atexit.register(_shutdown) is called inside import comtypes (its __init__.py). The main question is why it is required to call it again.

First I suspected that faulthandler.enable() or import faulthandler resets something in atexit handlers, but when doing
atexit.unregister(comtypes._shutdown)
import faulthandler
faulthandler.enable()

it also fixes the problem. It becomes more and more interesting...

My current suggestion is that atexit handlers must be registered for every separate module (at user level). Then from comtypes point of view using one more atexit.unregister(comtypes._shutdown) looks like the right solution.

Oh, wait! comtypes calls only atexit.register(_shutdown) while atexit.unregister(_shutdown) fixes the problem. So in fact we unregister correct handler which fails. Still not good.


PBDKF2 authentication fails for password_error

Environment

OS: Alpine 3.5
Erlang/OTP: 19
EMQ: 2.3.1

Description
I hash password using pbkdf2 + hmac + sha256 in the format <algorithm>$<iterations>$<salt>$<hash> which is defacto standard from my experience. Using 36000 iterations i get something like this (password is 'password'): pbkdf2_sha256$36000$jVzOPOCIrf3C$gWdG9Xk/UeYrxEagMJRSJZhdEYil73D6aTZ4cz9nqtQ=.
In the emq_auth_pgsql.conf i configured:
## Authentication Query: select password or password, salt
auth.pgsql.auth_query = select substring(password,'^(?:pbkdf2_sha256\$36000\$)(?:.+\$)(.+)$') as password, substring(password,'^(?:pbkdf2_sha256\$36000\$)(.+)(?:\$.+)$') as salt from device_deviceauth where device_id= '%u'
auth.pgsql.password_hash = pbkdf2,sha256,36000,32

## Superuser Query
#auth.pgsql.super_query = select is_superuser from mqtt_user where username = '%u' limit 1

## ACL Query. Comment this query, the acl will be disabled.
auth.pgsql.acl_query = select allow, clientid, access, topic from device_deviceacl where device_id = '%c'

EMQ shows up with
client 123 connected, connack: 4
client 123 disconnected, reason: auth_failure
14:10:50.801 [error] Client(123@<IP_ADDRESS>:54390): Username '123' login failed for password_error

Any idea what i am doing wrong here?
I would prefer emq_auth_pgsql to read the desired information directly from a string like <algorithm>$<iterations>$<salt>$<hash>. It would be less prone to failures due to wrong plugin configuration and would allow to switch the hashing algorithm at some point in time in production.

Thanks in advance

After testing a bit i found that probably the encoding of the hash plays a role. Mine is base64 encoded. But it seem to work, when the last sign does not equal =

Hi @pritstift
The hash field of <algorithm>$<iterations>$<salt>$<hash> should be filled by  hex string of encrypted data
See:
https://github.com/emqtt/emqttd/blob/f452469bc565f3d1aa7ff1afab6fdfd918828582/src/emqttd_auth_mod.erl#L63-L67


Add example cases to components

Examples in components
### Tasks
- [x] Add example to Accordion (Figma)
- [x] Add example to Alert (Figma)
- [x] Add example to Button (Figma)
- [x] Add example to Button with only icon (Figma)
- [x] Add example to Checkbox
- [x] Add example to Chip
- [x] Add example to Card
- [x] Add example to Combobox with chips inside
- [x] Add example to Combobox with chips outside
- [x] Add example to DropdownMenu
- [x] Add example to ErrorSummary
- [x] Add example to Helptext
- [ ] Add example to Link
- [x] Add example to List
- [x] Add example to Loaders
- [ ] Add example to Modal
- [x] Add example to Pagination
- [ ] Add example to Popover
- [x] Add example to Radio
- [x] Add example to Search
- [x] Add example to SkipLink
- [ ] Add example to Switch
- [x] Add example to Table
- [ ] Add example to Tag
- [x] Add example to TextArea
- [x] Add example to TextField
- [ ] Add example to ToggleGroup
- [ ] Add example to Tooltip
- [x] Add example to Typography

Moved back to todo for when someone else has the time to continue this issue.


allows updating news_flash now, moved resolution dict to init

should solve issue #1075

@atalyaalon  check the previous failed alembic version (the old one we locally changed), seems not compatible with the online revision, maybe it's because we loaded legacy data that didn't match the schema? I leave it to you


Why Android Alarm Manager not functioning properly in Flutter on Real device?

My Android alarm manager,when it calls the callback function ,performs a important operation.
I have published an app on Play Store and I feel so horrible that this Android Alarm Manager actually not functioning properly on the real devices.I tried it on my Mom's and friends phone
When I ran the app on my device in the debug mode I tested it and it was really working fine.Like I tested it for 2 hours 2 times.Like I understand that 15 minutes or more is the optimum time required for the callback function to be triggered,it is only then this android alarm manager functions properly.I did make sure that the callback function is triggered no less than 15 minutes but still while running in the debug mode on my device(or u can say the emulator),there would be a difference of 10-20 seconds for the a callback function to be triggered but still on real devices it is not working properly.It is not calling the call back function only..

Hi @Chethansmash7
Can you please provide your flutter doctor -v,
your flutter run --verbose
and a minimal complete reproducible code sample.
Thank you

Hi @Chethansmash7
Can you please provide your flutter doctor -v,
your flutter run --verbose
and a minimal complete reproducible code sample.
Thank you

Sure.........for flutter doctor -v
E:\flutter_Apps\flutter_app__v2>flutter doctor -v
Warning! The 'flutter' tool you are currently running is from a different Flutter repository than the one last used by this package. The repository from which the 'flutter' tool is
currently executing will be used instead.
running Flutter tool: C:\src\flutter
previous reference  : C:\flutter\flutter\flutter
This can happen when you have multiple copies of flutter installed. Please check your system path to verify that you are running the expected version (run 'flutter --version' to see
which flutter is on your path).
[√] Flutter (Channel unknown, v1.12.13+hotfix.8, on Microsoft Windows [Version 6.3.9600], locale en-US)
• Flutter version 1.12.13+hotfix.8 at C:\src\flutter
• Framework revision 0b8abb4724 (4 months ago), 2020-02-11 11:44:36 -0800
• Engine revision e1e6ced81d
• Dart version 2.7.0
[√] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
• Android SDK at C:\Users\w8\AppData\Local\Android\Sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-29, build-tools 29.0.3
• ANDROID_HOME = C:\Users\w8\AppData\Local\Android\Sdk
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)
• All Android licenses accepted.
[√] Android Studio (version 3.6)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin version 44.0.2
• Dart plugin version 192.7761
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)
[!] Connected device
! No devices available
! Doctor found issues in 1 category.
<<<<<<<-------------------------------->>>>>>>>>>>>
For flutter run --verbose
E:\flutter_Apps\flutter_app_v2>flutter run --verbose
[  +50 ms] Warning! The 'flutter' tool you are currently running is from a different Flutter repository than the one last used by this package. The repository from which the 'flutter'
tool is
currently executing will be used instead.
running Flutter tool: C:\src\flutter
previous reference  : C:\flutter\flutter\flutter
This can happen when you have multiple copies of flutter installed. Please check your system path to verify that you are running the expected version (run 'flutter
--version' to see
which flutter is on your path).
[  +22 ms] executing: [C:\src\flutter] git -c log.showSignature=false log -n 1 --pretty=format:%H
[  +54 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] 0b8abb4724aa590dd0f429683339b1e045a1594d
[        ] executing: [C:\src\flutter] git describe --match v*.. --first-parent --long --tags
[  +37 ms] Exit code 0 from: git describe --match v*.. --first-parent --long --tags
[        ] v1.12.13+hotfix.8-0-g0b8abb472
[  +10 ms] executing: [C:\src\flutter] git rev-parse --abbrev-ref --symbolic @{u}
[  +30 ms] Exit code 128 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] fatal: HEAD does not point to a branch
[  +25 ms] executing: [C:\src\flutter] git rev-parse --abbrev-ref HEAD
[  +27 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] HEAD
[ +155 ms] executing: C:\Users\w8\AppData\Local\Android\Sdk\platform-tools\adb.exe devices -l
[  +22 ms] Exit code 0 from: C:\Users\w8\AppData\Local\Android\Sdk\platform-tools\adb.exe devices -l
[        ] List of devices attached
[  +16 ms] No supported devices connected.
[  +24 ms] "flutter run" took 241ms.
#0      throwToolExit (package:flutter_tools/src/base/common.dart:28:3)
#1      RunCommand.validateCommand (package:flutter_tools/src/commands/run.dart:289:7)

#2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:590:11)
#3      FlutterCommand.run. (package:flutter_tools/src/runner/flutter_command.dart:515:33)

#4      AppContext.run. (package:flutter_tools/src/base/context.dart:146:29)
#5      _rootRun (dart:async/zone.dart:1126:13)
#6      _CustomZone.run (dart:async/zone.dart:1023:19)
#7      _runZoned (dart:async/zone.dart:1518:10)
#8      runZoned (dart:async/zone.dart:1465:12)
#9      AppContext.run (package:flutter_tools/src/base/context.dart:145:18)
#10     FlutterCommand.run (package:flutter_tools/src/runner/flutter_command.dart:505:20)
#11     CommandRunner.runCommand (package:args/command_runner.dart:197:27)
#12     FlutterCommandRunner.runCommand. (package:flutter_tools/src/runner/flutter_command_runner.dart:413:21)

#13     AppContext.run. (package:flutter_tools/src/base/context.dart:146:29)
#14     _rootRun (dart:async/zone.dart:1126:13)
#15     _CustomZone.run (dart:async/zone.dart:1023:19)
#16     _runZoned (dart:async/zone.dart:1518:10)
#17     runZoned (dart:async/zone.dart:1465:12)
#18     AppContext.run (package:flutter_tools/src/base/context.dart:145:18)
#19     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:364:19)
#20     CommandRunner.run. (package:args/command_runner.dart:112:25)
#21     new Future.sync (dart:async/future.dart:224:31)
#22     CommandRunner.run (package:args/command_runner.dart:112:14)
#23     FlutterCommandRunner.run (package:flutter_tools/src/runner/flutter_command_runner.dart:250:18)
#24     run.. (package:flutter_tools/runner.dart:63:22)
#25     _rootRun (dart:async/zone.dart:1126:13)
#26     _CustomZone.run (dart:async/zone.dart:1023:19)
#27     _runZoned (dart:async/zone.dart:1518:10)
#28     runZoned (dart:async/zone.dart:1502:12)
#29     run. (package:flutter_tools/runner.dart:61:18)

#30     AppContext.run. (package:flutter_tools/src/base/context.dart:146:29)
#31     _rootRun (dart:async/zone.dart:1126:13)
#32     _CustomZone.run (dart:async/zone.dart:1023:19)
#33     _runZoned (dart:async/zone.dart:1518:10)
#34     runZoned (dart:async/zone.dart:1465:12)
#35     AppContext.run (package:flutter_tools/src/base/context.dart:145:18)
#36     runInContext (package:flutter_tools/src/context_runner.dart:64:24)
#37     run (package:flutter_tools/runner.dart:50:10)
#38     main (package:flutter_tools/executable.dart:65:9)
#39     main (file:///C:/src/flutter/packages/flutter_tools/bin/flutter_tools.dart:8:3)
#40     _startIsolate. (dart:isolate-patch/isolate_patch.dart:305:32)
#41     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:174:12)
E:\flutter_Apps\flutter_app_v2>
<<<<<<<<<<<<<<------------------------------->>>>>>>>>>
Code-
void callback()  {
print("I am in the isolate");
DateTime now = DateTime.now().toLocal();
print("Date time:");
print(now);
Fluttertoast.showToast(
msg:
"notification message*****",
toastLength: Toast.LENGTH_LONG,
gravity: ToastGravity.BOTTOM,
backgroundColor: Colors.black,
textColor: Colors.red,
fontSize: 16.0);
print("last line of Isolate");
}
void alarm_managing_function(int t) async {
await AndroidAlarmManager.initialize();
await AndroidAlarmManager.periodic(Duration(seconds: t), 0, callback);
}
RaisedButton(
onPressed: () {
DatePicker.showPicker(context,
showTitleActions: true,
pickerModel:
CustomPicker(currentTime: DateTime.tryParse(_selectedTime)),
onConfirm: (time) {
setState(() {
print(time);
_selectedTime = DateFormat("mm-ss").format(time);
FileUtils().saveToFile(_selectedTime);
            mm = _selectedTime.substring(0, 2);
            ss = _selectedTime.substring(3, 5);
            print(mm);
            print(ss);
            mmValue = int.parse(mm);
            ssValue = int.parse(ss);
            totalTimeInSec = mmValue * 60 + ssValue;
            print(totalTimeInSec);

            DateTime now = DateTime.now().toLocal();
            print("Start-->Date time:");
            print(now);
             alarm_managing_function(totalTimeInSec);
          });
        }, locale: LocaleType.en);

<<--------------->>>>>>
Explanation
The alarm_managing_function function is called and with totalTimeInSec indicating the time at set by the user.The alarm managing function calls the callback() function which displayes the notification in the form of a toast

Guys any can help me?I need to fix this issue asap

Hi @Chethansmash7
Could you please run flutter upgrade --force.
If the issue persists, please provide your updated flutter doctor -v,
your flutter run --verbose (making sure that is actually running on a device)
and a minimal reproducible code sample.
Thank you

flutter upgrade --force

Sure,please give me some time I will test it on 2 actual devices and let u know soon enough.Thanks for the response.....

Hi @Chethansmash7
Could you please run flutter upgrade --force.
If the issue persists, please provide your updated flutter doctor -v,
your flutter run --verbose (making sure that is actually running on a device)
and a minimal reproducible code sample
that doesn't involve 3rd party plugins
Thank you

I have tested to on Samsung and Xiaomi phones.On Samsung phone it is working fine but on Xiaomi phones it is not working properly.Any idea as to why?

Hi @Chethansmash7
could you please provide the information listed above
thank you

Hi @Chethansmash7
could you please provide the information listed above
thank you

Sure @iapicca
Here it is:
E:\flutter_Apps\flutter_app_v2>flutter doctor -v
Warning! The 'flutter' tool you are currently running is from a different Flutter repository than the one last used by this package. The repository from which the 'flutter' tool is
currently executing will be used instead.
running Flutter tool: C:\src\flutter
previous reference  : C:\flutter\flutter\flutter
This can happen when you have multiple copies of flutter installed. Please check your system path to verify that you are running the expected version (run 'flutter --version' to see
which flutter is on your path).
╔════════════════════════════════════════════════════════════════════════════╗
║ A new version of Flutter is available!                                     ║
║                                                                            ║
║ To update to the latest version, run "flutter upgrade".                    ║
╚════════════════════════════════════════════════════════════════════════════╝
[√] Flutter (Channel stable, v1.17.3, on Microsoft Windows [Version 6.3.9600], locale en-US)
• Flutter version 1.17.3 at C:\src\flutter
• Framework revision b041144f83 (2 weeks ago), 2020-06-04 09:26:11 -0700
• Engine revision ee76268252
• Dart version 2.8.4
[√] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
• Android SDK at C:\Users\w8\AppData\Local\Android\Sdk
• Platform android-29, build-tools 29.0.3
• ANDROID_HOME = C:\Users\w8\AppData\Local\Android\Sdk
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)
• All Android licenses accepted.
[√] Android Studio (version 3.6)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin version 44.0.2
• Dart plugin version 192.7761
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)
[!] Connected device
! No devices available
! Doctor found issues in 1 category
And flutter run --verbose
E:\flutter_Apps\flutter_app_v2>flutter run --verbose
[  +40 ms] Warning! The 'flutter' tool you are currently running is from a different Flutter repository than the one last used by this package. The repository from which the 'flutter'
tool is
currently executing will be used instead.
running Flutter tool: C:\src\flutter
previous reference  : C:\flutter\flutter\flutter
This can happen when you have multiple copies of flutter installed. Please check your system path to verify that you are running the expected version (run 'flutter
--version' to see
which flutter is on your path).
[  +20 ms] executing: [C:\src\flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[  +51 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] b041144f833e05cf463b8887fa12efdec9493488
[   +1 ms] executing: [C:\src\flutter/] git tag --contains HEAD
[ +298 ms] Exit code 0 from: git tag --contains HEAD
[   +1 ms] 1.17.3
[  +19 ms] executing: [C:\src\flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[  +29 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/stable
[        ] executing: [C:\src\flutter/] git ls-remote --get-url origin
[  +26 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[ +130 ms] executing: [C:\src\flutter/] git rev-parse --abbrev-ref HEAD
[  +29 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] stable
[  +52 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +6 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[  +45 ms] executing: C:\Users\w8\AppData\Local\Android\Sdk\platform-tools\adb.exe devices -l
[  +56 ms] List of devices attached
[   +4 ms] Artifact Instance of 'MaterialFonts' is not required, skipping update.
[        ] Artifact Instance of 'GradleWrapper' is not required, skipping update.
[        ] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[        ] Artifact Instance of 'FlutterSdk' is not required, skipping update.
[        ] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FontSubsetArtifacts' is not required, skipping update.
[ +101 ms] No supported devices connected.
[  +36 ms] "flutter run" took 346ms.
#0      throwToolExit (package:flutter_tools/src/base/common.dart:14:3)
#1      RunCommand.validateCommand (package:flutter_tools/src/commands/run.dart:336:7)

#2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:703:11)

#3      FlutterCommand.run. (package:flutter_tools/src/runner/flutter_command.dart:620:33)

#4      FlutterCommand.run. (package:flutter_tools/src/runner/flutter_command.dart)
#5      AppContext.run. (package:flutter_tools/src/base/context.dart:150:29)
#6      _rootRun (dart:async/zone.dart:1184:13)
#7      _CustomZone.run (dart:async/zone.dart:1077:19)
#8      _runZoned (dart:async/zone.dart:1619:10)
#9      runZoned (dart:async/zone.dart:1539:10)
#10     AppContext.run (package:flutter_tools/src/base/context.dart:149:18)
#11     FlutterCommand.run (package:flutter_tools/src/runner/flutter_command.dart:610:20)
#12     CommandRunner.runCommand (package:args/command_runner.dart:197:27)
#13     FlutterCommandRunner.runCommand. (package:flutter_tools/src/runner/flutter_command_runner.dart:339:21)

#14     FlutterCommandRunner.runCommand. (package:flutter_tools/src/runner/flutter_command_runner.dart)
#15     AppContext.run. (package:flutter_tools/src/base/context.dart:150:29)
#16     _rootRun (dart:async/zone.dart:1184:13)
#17     _CustomZone.run (dart:async/zone.dart:1077:19)
#18     _runZoned (dart:async/zone.dart:1619:10)
#19     runZoned (dart:async/zone.dart:1539:10)
#20     AppContext.run (package:flutter_tools/src/base/context.dart:149:18)
#21     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:288:19)
#22     CommandRunner.run. (package:args/command_runner.dart:112:25)
#23     new Future.sync (dart:async/future.dart:224:31)
#24     CommandRunner.run (package:args/command_runner.dart:112:14)
#25     FlutterCommandRunner.run (package:flutter_tools/src/runner/flutter_command_runner.dart:231:18)
#26     run.. (package:flutter_tools/runner.dart:63:22)
#27     _rootRun (dart:async/zone.dart:1184:13)
#28     _CustomZone.run (dart:async/zone.dart:1077:19)
#29     _runZoned (dart:async/zone.dart:1619:10)
#30     runZonedGuarded (dart:async/zone.dart:1608:12)
#31     runZoned (dart:async/zone.dart:1536:12)
#32     run. (package:flutter_tools/runner.dart:61:18)

#33     run. (package:flutter_tools/runner.dart)
#34     runInContext.runnerWrapper (package:flutter_tools/src/context_runner.dart:64:18)

#35     runInContext.runnerWrapper (package:flutter_tools/src/context_runner.dart)
#36     AppContext.run. (package:flutter_tools/src/base/context.dart:150:29)
#37     _rootRun (dart:async/zone.dart:1184:13)
#38     _CustomZone.run (dart:async/zone.dart:1077:19)
#39     _runZoned (dart:async/zone.dart:1619:10)
#40     runZoned (dart:async/zone.dart:1539:10)
#41     AppContext.run (package:flutter_tools/src/base/context.dart:149:18)
#42     runInContext (package:flutter_tools/src/context_runner.dart:67:24)
#43     run (package:flutter_tools/runner.dart:48:10)
#44     main (package:flutter_tools/executable.dart:69:9)
#45     main (file:///C:/src/flutter/packages/flutter_tools/bin/flutter_tools.dart:8:3)
#46     _startIsolate. (dart:isolate-patch/isolate_patch.dart:299:32)
#47     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:168:12)

Hi @Chethansmash7
the error you are reporting might depend from your implementation rather than flutter itself
for the issue to be workable will be needed minimal complete reproducible code sample.
Also in the log you provided the app didn't run due to lack of connected device;
could you please provide a verbose representative of the situation
Thank you

Hi @Chethansmash7
the error you are reporting might depend from your implementation rather than flutter itself
for the issue to be workable will be needed minimal complete reproducible code sample.
Also in the log you provided the app didn't run due to lack of connected device;
could you please provide a verbose representative of the situation
Thank you

@iapicca
With regards to the minimal complete reproducible code sample I have already furnished earlier.Please have a look at it.
Well the lack of connected device I feel has nothing to do with the log,because if connected it would just show the name of my mobile.Please correct me if I am wrong

Hi @Chethansmash7
for the issue to be workable it needs to be reproducible,
since the error occurs at runtime it will need a "runnable" minimal reproducible code sample,
(not production code or a snippet of a single function)
please provide the info required to investigate the issue,
without a device attached the app won't build, please provide valid logs.
Thank you

Well the problem with real device was that in the settings of the device.Under battery saver,the background process was in a restricted mode (which comes as default and recommended in most of the devices).When I ran the app after changing the settings in which the background process of an app would run without any restriction,it is working fine.
Thank u for all the help you gave me till now.

I'm glad you fixed the issue
Thank you for letting me know

I'm glad you fixed the issue
Thank you for letting me know

Welcome


how to generate input_file.json

Hey @SuvodipDey,
How should I generate the input_file.json to evaluate my model? I want to use a direct huggingface path like:  meta-llama/Llama-3.1-8B.
Maybe @yxc-cyber  got the scripts for generative LLMs?

Hi @emrecanacikgoz ,
Now I have updated my code and it should support local models now. You can take this offline_evaluate.ipynb. The only change you need is that in the client_config, you don't need to provide client or model. Instead, you provide local_model. This local model must have a function chat_completion(messages), where the input is like this:
messages = [
    {"role": "system", "content": "Some prompts."},
    {"role": "user", "content": "A user utterance."},
    {"role": "assistant", "content": "A response."},
    {"role": "user", "content": "A user utterance."},
]

And the output is of type str, which is the response to the last user utterance.
The overall idea that you can probably take as a reference is like this. First, you can inherit an LM object to implement the chat_completion(messages) function:
from transformers import LlamaForCausalLM
class customLM(LlamaForCausalLM):
    def chat_completion(self, messages):
        #Todo
        pass

Then, you can load your checkpoint from somewhere:
pretrained_model_name_or_path = "some model your want to use"
mycustomLM = customLM.from_pretrained(pretrained_model_name_or_path)

After that, you can change change the config in offline_evaluate.ipynb and run your generation:
client_config = {
    "local_model": mycustomLM,
}
offline_evaluator = evaluator(
    data,
    old_data,
    total_samples,
    prompt=eval_prompt,
    client_config=client_config,
    online=False
)

After getting the generated result, you can use eval_postprocess.py to transform the result into the format that Suvodip's eval code accepts. But currently, eval_postprocess.py contains some issues with delexicalization. So don't directly use it.

Thank you for the detailed instruction @yxc-cyber!
Isn't this the same purpose for huggingface models, see here, could you verify that?
What about this alsa, see here?


this._enabled check could be done earlier

I was wondering why the enabled check is not done earlier.
https://github.com/getsentry/raven-node/blob/master/lib/client.js#L111
Since only the ident is returned I don't see any use in performing all these other operations?

I'm pretty sure my reasoning was so that the dataCallback would be executed and basically everything gets executed as if it were to send, except bails out at the last second.
Is there an issue you're having with this behavior?

can live with that, thanks for explaining


Structured Theme, Compliant to 7+1 Architecture

Improved: Structure of the theme
Implemented: 7+1 architecture
Documented: in Jira (UIOPT-59 + UIOPT-60) + Confluence
Completed:  UIOPT-59 ; UIOPT-60
Reverted: Reduced the MandaraTheme flavors reduced to just dark and light mode. Eliminated the need to choose among other OFBiz themes
Fixed: UIOPT-60
(OFBIZ-)
Explanation:
The main task was to restructure the theme to be compliant to sass 7+1 architecture. Additional side tasks like bug fixes, etc were implemented alongside.
Thanks:
@fwagni

Review performed by FWAGNI

The ticket can be closed


Replace PowerMock with Mockito in LogLevelTest

What changes are proposed in this pull request?
Replace PowerMock with Mockito in LogLevelTest.
Why are the changes needed?
Part of #15003.
This PR intentionally limits the scope of change to a single low-impact test, so that we can first add needed dependencies and see if it works, then proceed to replace more PowerMock in other tests.
Does this PR introduce any user facing changes?
No.

What is failing?

What is failing?
The errors don't seem to be related to the part I modified. Let me have a check.

What is failing?

I think the reason is the pom.xml. When I set the inline dependency in the shell project, it works well. But when I set it in the root pom.xml, it comes the error.

2022-03-09T10:20:59.1696718Z 10:20:59.160 [ERROR] alluxio.client.file.AlluxioFileInStreamTest.readFile[0]  Time elapsed: 0.03 s  <<< ERROR!
2022-03-09T10:20:59.1697672Z org.mockito.exceptions.misusing.NotAMockException: Argument should be a mock, but is: class java.lang.Class
2022-03-09T10:20:59.1698301Z 	at alluxio.client.file.AlluxioFileInStreamTest.before(AlluxioFileInStreamTest.java:156)
2022-03-09T10:20:59.1698886Z 	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
2022-03-09T10:20:59.1699454Z 	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)

Looks like this: https://github.com/powermock/powermock/issues/992

LGTM, probably put in the description why we only apply this dependency in this project not root.

Done.

alluxio-bot, merge this please


Net disbursal Amount Feature

Description
Implements the net disbursal amount feature. It's an extract of the feature from the bulk PR based on latest apache/fineract upstream code.
Could use further testing once the equivalent UI changes get implemented.

@xurror . This should be closed in favor of the nda branch since it doesn't yet contain all the required NDA improvements which are supposed to go to Fineract-oss-release branch. Therefore, this proposal is rejected.
I have already covered the changes specified in this PR with #42 which has been merged with develop.
Please ensure checks are successful when posting to this repo.


Bundle size optimize

After replacing DOMPurify and remove deepmerge

Hi @mutoe
Are our unit tests (utils/request.spec.js) are passing after removing deepmerge?

Hi @mutoe
Are our unit tests (utils/request.spec.js) are passing after removing deepmerge?

@levchak0910 Yep, all tests were passed in the newest CI https://github.com/mutoe/vue3-realworld-example-app/actions/runs/629130533

Ok, great work!


nixos/tayga: init

Description of changes
Add module and test. Module comes from https://github.com/NixOS/nixpkgs/pull/129390

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[x] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

I'm still confused by the useNetworkd part, why can't we keep only the generic implementation.

Now I use the generic implementation. To get the most of the sandboxing, there is a check if systemd-networkd is used, because virtualOwner cannot be empty in the nixos-scripts and then uses root by defaut.

Could you move the release notes for 23.05? I am interested into getting this merged.

We're backporting this into 22.11 since it is unlikely to cause regressions.


Add estimation exactness unit tests

In this PR, new files are added :

generate_tests_results.py is the script used for the tests results generation of every estimators
test_results.npy file is storing both input and estimation results for each estimator and each combinaison of inputs
test_exactness_estimation.py file contains the exactness tests functions, it follows the same paradigm used for tolerance tests with fixtures. Those tests will execute by iterating over every row of test_results.npy, launching each corresponding tests using the stored inputs and testing that the stored results are the same as the new computed results.
constants.py file storing variables used several times in the project is added for cleanness purpose

And some existing files are modified :

In test_get_estimation.py the effects_chap function is modified to skip the errors occuring with glmnet function from rpy2 package, some imports cleaning is done as well
In mediation.py outputs of every estimator function is now a list for homogeneous purpose, some imports cleaning is done as well
In setup.py, pandas version is fixed to 1.2.1 to avoid the "DataFrame has no attribute 'iteritems'" error from simulation_based and mediation_g_estimator - pytest is added
In test_get_simulated_data.py, get_estimation.py, get_simulated_data.py, nuisances.py and utils.py some imports cleaning is done

Further improvement :

Enhance the readability of the exactness tests so that the tests outputs contain the estimator name for each failing test
Integrate what has been done in #73

Sorry for the misunderstanding, but I think that we should keep the Python default, i.e. a tuple, rather than coercing it to a list.

Sorry for the misunderstanding, but I think that we should keep the Python default, i.e. a tuple, rather than coercing it to a list.

So I should just revamp the changes or I should also return tuples where it was returning lists before ?

If there is no precise reason to return a list, we should indeed return tuples.

Requested changes are implemented
#73 is merged with develop and conflicts are solved
If it's ok for you, we can merge this PR into develop and then merge develop into main
@bthirion @judithabk6 @houssamzenati

I have made the requested changes, I merge this PR.

I have made the requested changes, I merge this PR.

I have made the requested changes, I merge this PR.


Fix line wrapping

@kokosxD : Thanks for your contribution! The author(s) have been notified to review your proposed change.


S3TC textures appear with bad artifacts

According to the current plans, Godot will require GL3.3 on desktop which doesn't mandate ETC texture support. Currently, only S3TC textures are used on desktop.
Current S3TC encoder can produce bad artifacts: (uncompressed vs VRAM for the 512x512 albedo texture, prepared in substance painter, from #8457)

Godot currently uses an old version of libsquish, with a low quality setting (kColourRangeFit). The problem persist even with the latest version of libsquish (1.15), and using the best compression kColourIterativeClusterFit.

Actually Godot uses the latest version of libsquish: https://github.com/godotengine/godot/blob/master/thirdparty/README.md#squish
But it's almost the same as the previous 1.14: https://github.com/godotengine/godot/commit/fa2d5b91dc390a11262859e5309351ba58842901

I think I got the version number from a wrong place: this is the repository link from the original author's blog, and it adds nontrivial stuff on top of what currently comes with Godot.
But using it it still doesn't solve the issue. I'm not 100% sure about this yet but it seems like the output of libsquish is fine, the problem is somewhere else in Godot.

So far I tried using squishpng (in sourceforge repo) on that texture, and it is indeed giving fair results at all quality settings. So it does seem like the problem is within Godot.

Within Godot, I confirmed that the generated S3TC is OK, so the problem is definitely somewhere else, possibly within the renderer.
This, however, led me to discover that Image::_decompress_bc isn't working. I added a image_decompress_squish function which wraps squish's decompressor, registered that and used that instead. Not sure why there is an alternative decompressor there. I'll submit a PR for that later on.

OK, found the problem: there is a typo on this line: _EXT_COMPRESSED_SRGB_S3TC_DXT1_NV should actually be _EXT_COMPRESSED_SRGB_ALPHA_S3TC_DXT1_NV.
Things work good as expected.
I'll submit another PR for that.
I'll also make sure VRAM quality settings (introduced in #8548) effect the squish quality settings.
Just as a note to myself so that I won't forget it: Image::save_png` should be const.


UBSAN error: member call on null pointer in XdsTest/FailoverTest.UpdateInitialUnavailable/FakeResolverWithLoadReporting

log snippet:
[ RUN      ] XdsTest/FailoverTest.UpdateInitialUnavailable/FakeResolverWithLoadReporting
I0116 23:14:15.061206513      19 xds_end2end_test.cc:992]    starting Backend server on port 20310
I0116 23:14:15.061585305     123 server_builder.cc:332]      Synchronous server. Num CQs: 1, Min pollers: 1, Max Pollers: 2, CQ timeout (msec): 10000
I0116 23:14:15.062416887      19 xds_end2end_test.cc:1004]   Backend server startup complete
I0116 23:14:15.062715060      19 xds_end2end_test.cc:992]    starting Backend server on port 20311
src/core/ext/filters/client_channel/xds/xds_client.cc:1276:50: runtime error: member call on null pointer of type 'grpc_core::XdsClient::ChannelState::RetryableCall<grpc_core::XdsClient::ChannelState::AdsCallState>'
I0116 23:14:15.063165616     125 server_builder.cc:332]      Synchronous server.  Num CQs: 1, Min pollers: 1, Max Pollers: 2, CQ timeout (msec): 10000
I0116 23:14:15.064947604      19 xds_end2end_test.cc:1004]   Backend server startup complete
I0116 23:14:15.065003530      19 xds_end2end_test.cc:992]    starting Backend server on port 20313
I0116 23:14:15.065246650     129 server_builder.cc:332]      Synchronous server.  Num CQs: 1, Min pollers: 1, Max Pollers: 2, CQ timeout (msec): 10000
I0116 23:14:15.066805534      19 xds_end2end_test.cc:1004]   Balancer server startup complete
I0116 23:14:15.067474772      19 xds_end2end_test.cc:1025]   Backend about to shutdown
I0116 23:14:15.067876254      19 xds_end2end_test.cc:1029]   Backend shutdown completed
I0116 23:14:15.067894713      19 xds_end2end_test.cc:1025]   Backend about to shutdown
I0116 23:14:15.068295437      19 xds_end2end_test.cc:1029]   Backend shutdown completed
I0116 23:14:15.070331449     132 subchannel.cc:1055]         New connected subchannel at 0x7f28740018f0 for subchannel 0x2cea030
I0116 23:14:15.071223486     132 xds_end2end_test.cc:593]    LRS[0x2cd1670]: StreamLoadStats starts
I0116 23:14:15.071497249     134 xds_end2end_test.cc:450]    ADS[0x2cd1528]: StreamAggregatedResources starts
I0116 23:14:15.072221842     134 xds_end2end_test.cc:425]    ADS[0x2cd1528]: received EDS request 'node {
  id: "xds_end2end_test"
  cluster: "test"
  metadata {
    fields {
      key: "foo"
      value {
        string_value: "bar"
      }
    }
  }
  locality {
    region: "corp"
    zone: "svl"
    sub_zone: "mp3"
  }
  build_version: "gRPC C-core 9.0.0 linux"
}
resource_names: "application_target_name"
type_url: "type.googleapis.com/envoy.api.v2.ClusterLoadAssignment"
'
I0116 23:14:15.072257189     134 xds_end2end_test.cc:437]    ADS[0x2cd1528]: sleeping for 0 ms...
I0116 23:14:15.072921309     134 xds_end2end_test.cc:441]    ADS[0x2cd1528]: Woke up! Sending response 'resources {
  [type.googleapis.com/envoy.api.v2.ClusterLoadAssignment] {
    cluster_name: "application_target_name"
    endpoints {
      locality {
        region: "xds_default_locality_region"
        zone: "xds_default_locality_zone"
        sub_zone: "locality0"
      }
      lb_endpoints {
        endpoint {
          address {
            socket_address {
              address: "<IP_ADDRESS>"
              port_value: 20310
            }
          }
        }
      }
      load_balancing_weight {
        value: 3
      }
    }
    endpoints {
      locality {
        region: "xds_default_locality_region"
        zone: "xds_default_locality_zone"
        sub_zone: "locality1"
      }
      lb_endpoints {
        endpoint {
          address {
            socket_address {
              address: "<IP_ADDRESS>"
              port_value: 20311
            }
          }
        }
      }
      load_balancing_weight {
        value: 3
      }
      priority: 1
    }
  }
}
type_url: "type.googleapis.com/envoy.api.v2.ClusterLoadAssignment"
'
I0116 23:14:15.073940920     130 subchannel.cc:1003]         Connect failed: {"created":"@1579216455.073877157","description":"Failed to connect to remote host: Connection refused","errno":111,"file":"src/core/lib/iomgr/tcp_client_posix.cc","file_line":200,"os_error":"Connection refused","syscall":"connect","target_address":"ipv4:<IP_ADDRESS>:20310"}
I0116 23:14:15.074023129     130 subchannel.cc:942]          Subchannel 0x7f28600039a0: Retry in 1000 milliseconds
I0116 23:14:15.074630961     135 subchannel.cc:1003]         Connect failed: {"created":"@1579216455.074562695","description":"Failed to connect to remote host: Connection refused","errno":111,"file":"src/core/lib/iomgr/tcp_client_posix.cc","file_line":200,"os_error":"Connection refused","syscall":"connect","target_address":"ipv4:<IP_ADDRESS>:20311"}
I0116 23:14:15.074665673     135 subchannel.cc:942]          Subchannel 0x7f286000cf00: Retry in 998 milliseconds
I0116 23:14:15.075014784     134 xds_end2end_test.cc:437]    ADS[0x2cd1528]: sleeping for 1000 ms...
I0116 23:14:15.568615191      19 xds_end2end_test.cc:853]    ========= WAITING FOR BACKEND 2 ==========
    #0 0x7f289ca98e8e in grpc_core::XdsClient::ChannelState::LrsCallState::MaybeStartReportingLocked() /proc/self/cwd/src/core/ext/filters/client_channel/xds/xds_client.cc:1276:50
    #1 0x7f289ca9bd5d in grpc_core::XdsClient::ChannelState::LrsCallState::Reporter::OnReportDoneLocked(void*, grpc_error*) /proc/self/cwd/src/core/ext/filters/client_channel/xds/xds_client.cc:1136:22
    #2 0x7f289aebb2f1 in grpc_combiner_continue_exec_ctx() /proc/self/cwd/src/core/lib/iomgr/combiner.cc:236:5
    #3 0x7f289af09d96 in grpc_core::ExecCtx::Flush() /proc/self/cwd/src/core/lib/iomgr/exec_ctx.cc:156:17
    #4 0x7f289aed56aa in end_worker(grpc_pollset*, grpc_pollset_worker*, grpc_pollset_worker**) /proc/self/cwd/src/core/lib/iomgr/ev_epoll1_linux.cc:991:32
    #5 0x7f289aeccf71 in pollset_work(grpc_pollset*, grpc_pollset_worker**, long) /proc/self/cwd/src/core/lib/iomgr/ev_epoll1_linux.cc:1055:3
    #6 0x7f289af08351 in pollset_work(grpc_pollset*, grpc_pollset_worker**, long) /proc/self/cwd/src/core/lib/iomgr/ev_posix.cc:324:21
    #7 0x7f289af1b5c4 in grpc_pollset_work(grpc_pollset*, grpc_pollset_worker**, long) /proc/self/cwd/src/core/lib/iomgr/pollset.cc:48:10
    #8 0x7f289c2a13b2 in run_poller(void*, grpc_error*) /proc/self/cwd/src/core/ext/filters/client_channel/backup_poller.cc:130:7
    #9 0x7f289af09fe9 in exec_ctx_run(grpc_closure*, grpc_error*) /proc/self/cwd/src/core/lib/iomgr/exec_ctx.cc:40:3
    #10 0x7f289af09d7f in grpc_core::ExecCtx::Flush() /proc/self/cwd/src/core/lib/iomgr/exec_ctx.cc:153:9
    #11 0x7f289af82d4d in run_some_timers() /proc/self/cwd/src/core/lib/iomgr/timer_manager.cc:134:30
    #12 0x7f289af82911 in timer_main_loop() /proc/self/cwd/src/core/lib/iomgr/timer_manager.cc:237:9
    #13 0x7f289af8282e in timer_thread(void*) /proc/self/cwd/src/core/lib/iomgr/timer_manager.cc:284:3
    #14 0x7f289ac48b93 in grpc_core::(anonymous namespace)::ThreadInternalsPosix::ThreadInternalsPosix(char const*, void (*)(void*), void*, bool*, grpc_core::Thread::Options const&)::'lambda'(void*)::operator()(void*) const /proc/self/cwd/src/core/lib/gprpp/thd_posix.cc:140:27
    #15 0x7f289ac48554 in grpc_core::(anonymous namespace)::ThreadInternalsPosix::ThreadInternalsPosix(char const*, void (*)(void*), void*, bool*, grpc_core::Thread::Options const&)::'lambda'(void*)::__invoke(void*) /proc/self/cwd/src/core/lib/gprpp/thd_posix.cc:110:25
I0116 23:14:16.072536621     137 subchannel.cc:967]          Failed to connect to channel, retrying
I0116 23:14:16.073383474     137 subchannel.cc:967]          Failed to connect to channel, retrying
I0116 23:14:16.074296140     130 subchannel.cc:1003]         Connect failed: {"created":"@1579216456.074235634","description":"Failed to connect to remote host: Connection refused","errno":111,"file":"src/core/lib/iomgr/tcp_client_posix.cc","file_line":200,"os_error":"Connection refused","syscall":"connect","target_address":"ipv4:<IP_ADDRESS>:20311"}
I0116 23:14:16.074699407     130 subchannel.cc:942]          Subchannel 0x7f286000cf00: Retry in 1404 milliseconds
I0116 23:14:16.073957012     132 subchannel.cc:1003]         Connect failed: {"created":"@1579216456.073833702","description":"Failed to connect to remote host: Connection refused","errno":111,"file":"src/core/lib/iomgr/tcp_client_posix.cc","file_line":200,"os_error":"Connection refused","syscall":"connect","target_address":"ipv4:<IP_ADDRESS>:20310"}
I0116 23:14:16.075444712     130 subchannel.cc:942]          Subchannel 0x7f28600039a0: Retry in 1880 milliseconds
    #16 0x7f2898e6d6b9 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x76b9)
    #17 0x7f289858041c in clone (/lib/x86_64-linux-gnu/libc.so.6+0x10741c)

https://source.cloud.google.com/results/invocations/d8da2df6-1db0-4a8a-a91b-97126a4640e3/targets/%2F%2Ftest%2Fcpp%2Fend2end:xds_end2end_test@poller%3Depoll1/log
seen in PR: https://github.com/grpc/grpc/pull/21684

We no longer have the version of test FakeResolverWithLoadReporting, the other versions of FailoverTest.UpdateInitialUnavailable are fine with 1000 runs.
Closing this bug


[WIP] Cypress tests: init cypress testing

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


extend constant_keyword  field type usage scope

Description
Add a new parameter values in constant_keyword, support multiple fixed values.
PUT romcom_movies
{
  "mappings" : {
    "properties" : {
      "field1" : {
        "type": "constant_keyword",
        "values" : [value1, value2,value3......]
      }
    }
  }
}

It also support index and doc_values.
Related Issues
Resolves #14986

Check List

[ ] Functionality includes testing.
[ ] API changes companion pull request created, if applicable.
[ ] Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

While I think the idea of encoding multiple constant values makes sense, concepts like "indexed" or "doc values" don't really make sense for contstant_keyword fields, because they aren't actually supposed to be part of the Lucene index.
Part of the beauty of a constant_keyword field is that it exists entirely within the mapping.
I noticed that you're delegating to KeywordFieldType for some of the query logic, which I don't think works for a constant field that only lives in the mapping. Any query against a constant_keyword field should be either a MatchAllDocsQuery or a MatchNoDocsQuery, because we should be able to directly evaluate the given query against the constant value(s).
Honestly, I think it would be enough to do a for-loop over the existing logic to check each value. Yes, it grows linearly in terms of the number of values, but if we're extending the current logic that handles 1 value to N values, how big is N going to get? Since the mappings are part of the cluster state that gets propagated to every node, you don't want them to get too big.

@msfroh Thanks for the comment!
Each document has its own uniq value for contstant_keyword fields, We need to store each encoded value on disk for every document. When querying against a contstant_keyword, it may not necessarily hit all documents(for example the sex field, we only want to get documents containing boys), in this case, it's the same as a keyword query.
for N, I think N<128 is enough.
If we don't use KeywordFieldType, I‘m highly appreciated any additional ideas from you.

Ahh... Okay! If each document has its own value, then it's not a use-case for constant_keyword, which uses one constant value (or possibly list of values, if we want to make that change) for all documents in the index.
If you want documents to have different values, I'm wondering why a regular keyword field wouldn't work. Can you clarify what you're looking for that keyword fields can't do?

@msfroh, In some cases, we can speed up the query. For example, when the majority documents are hit, we can use the opposite documents, but it seems a limited optimization.
If you think it is useful to support multiple values (with same values in all documents), I will implement it.

@msfroh, In some cases, we can speed up the query. For example, when the majority documents are hit, we can use the opposite documents, but it seems a limited optimization.

Ahh! I considered something kind of like that for boolean fields in https://github.com/opensearch-project/OpenSearch/issues/11143.
In the end, I haven't done that, since folks could just use a numeric {0,1}, field instead. There is an optimization for that on numeric range queries -- if a range query covers more a majority of documents (and the numeric field is present in all documents), it's replaced with "NOT inverse range". You could probably achieve something similar with an "enum" type field where the distinct values get mapped to integers. (It might be nice to do that automatically.)
Anyway -- for the constant_keyword field type, I don't know how many people actively want a constant list/set of values across all documents. It's a logical extension of the existing single-valued fields, but I'd also be happy to wait until someone has a use-case that needs it before implementing it. Essentially, I would wait for someone to stand up and say, "Yes, I need that."


Issue with k8s.io/docs/setup/independent/create-cluster-kubeadm/

Hi Team,
| I tried to setup master and nodes on centos using updated docs as in the below link...
kubernetes.io/docs/setup/independent/create-cluster-kubeadm
i am facing Transaction check error when i try to install  kubeadm.Transaction check error:   file /usr/bin/kubectl from install of  kubectl-1.7.1-0.x86_64 conflicts with file from package  kubernetes-client-1.5.2-0.7.git269f928.el7.x86_64...due to this unable  to install kubeadm and create cluster. Some of troubleshooting steps like DNS,Network parameters tried but still no luck.
Using:Centos 7.3
Thanks,
Surya

[root@localhost etc]# yum install -y kubelet kubeadm
Loaded plugins: fastestmirror, langpacks
base                                                                                | 3.6 kB  00:00:00
docker-ce-stable                                                                                | 2.9 kB  00:00:00
extras                                                                                | 3.4 kB  00:00:00
kubernetes/signature                                                                                |  454 B  00:00:00
kubernetes/signature                                                                                | 1.4 kB  00:00:00 !!!
updates                                                                                | 3.4 kB  00:00:00
virt7-docker-common-release                                                                                | 3.4 kB  00:00:00
Loading mirror speeds from cached hostfile

base: centos.chi.host-engine.com
extras: centos.firehosted.com
updates: centos.blazar.mx
Resolving Dependencies
--> Running transaction check
---> Package kubeadm.x86_64 0:1.7.1-0 will be installed
--> Processing Dependency: kubectl >= 1.6.0 for package: kubeadm-1.7.1-0.x86_64
--> Processing Dependency: kubernetes-cni for package: kubeadm-1.7.1-0.x86_64
---> Package kubelet.x86_64 0:1.7.1-0 will be installed
--> Running transaction check
---> Package kubectl.x86_64 0:1.7.1-0 will be installed
---> Package kubernetes-cni.x86_64 0:0.5.1-0 will be installed
--> Finished Dependency Resolution

Dependencies Resolved
=============================================================================================================================================================================================================================================
Package                                                       Arch                                                  Version                                                 Repository                                                 Size
Installing:
kubeadm                                                       x86_64                                                1.7.1-0                                                 kubernetes                                                8.6 M
kubelet                                                       x86_64                                                1.7.1-0                                                 kubernetes                                                 16 M
Installing for dependencies:
kubectl                                                       x86_64                                                1.7.1-0                                                 kubernetes                                                8.9 M
kubernetes-cni                                                x86_64                                                0.5.1-0                                                 kubernetes                                                7.4 M
Transaction Summary
Install  2 Packages (+2 Dependent packages)
Total size: 41 M
Installed size: 222 M
Downloading packages:
Running transaction check
Running transaction test
Transaction check error:
file /usr/bin/kubectl from install of kubectl-1.7.1-0.x86_64 conflicts with file from package kubernetes-client-1.5.2-0.7.git269f928.el7.x86_64
Error Summary

@SuryaPractise :wave: This issue sounds more like a request for support and less like an issue specifically for docs. I encourage you to bring your question to the #kubernetes-users channel in Kubernetes slack. You can also search resources like Stack Overflow for answers to similar questions.


Improved Readme file and Python Notebook regarding face-mask-detection model using Pytorch

Related Issuse or bug

Info about Issue or bug

Fixes: #329
Proposed Changes

Info about changes Goes here

Additional Info

Anything related Issues

Great @AshuKV


Add Ahmed AlAskalany to Contributors list

Hi  @AlAskalany, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added social share  to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.

Hi @Roshanjossey ! Thanks for the initiative, it felt good to have my name among the contributers.

I’d urge you to continue contributing to other open source projects.
We also have a slack team to help/mentor people trying to contribute to open source projects.
You can join the team by going to https://goo.gl/PM1Jdh


tensorflow 2.0 support, python 3.7

hello,
is python 3.7 supported?
are there plans for supporting tensorflow 2.0 ?
if so, (how) could we contribute?
tensorflow probability is ready for 2.0 stated here
same issue for graph_net library ontop of sonnet here

Hey flowpoint@, we're planning to make a major release of Sonnet to support TensorFlow 2 (c.f. deepmind/sonnet#117). The current plan is to make this public by the end of the month. We spoke a bit about this at the TF Dev Summit (https://www.youtube.com/watch?v=rlpQjnUvoKw).
Python 3.7 support I believe was blocked on TensorFlow supporting 3.7 which came out in TF 1.13 (https://github.com/tensorflow/tensorflow/releases/tag/v1.13.1), afaik there are no blockers from Sonnet, please let us know if that is not the case.

sry i managed to miss that


The upper/lower case of windows driver letter in GOPATH fails gucumber running

in builder.go
The check result of line 46 changes depending on the windows driver letter case (C: or c:), as a result that error is return by line 53.
line 46: if strings.HasPrefix(absPath, p) {
line 53: return fmt.Errorf("could not determine package path for %s", file)

the p is split form GO.ENV (GOPATH). and the default driver is Up letter.
So try to modify GOPATH=%GOPATH%;c:\additional_gopath <-->C:\additional_gopath, let them to be equals


⚠ Cioos National CKAN has degraded performance

In 35e96e5, Cioos National CKAN (https://catalogue.cioos.ca/) experienced degraded performance:

HTTP code: 200
Response time: 15705 ms

Resolved: Cioos National CKAN performance has improved in cee398b after 11 minutes.


Allow multi-dimensional parameter sweeps

Currently parameterSets is a list, but we only take the first item in the list. We should allow multiple sets to be defined, and apply multiple substitutions per job.

Implemented, at least up to 4D https://github.com/prominence-eosc/prominence/commit/b53f92152b5abd0e74f09a6b7e6b883100e9a147


Workflow for gene selection in scvi-tools

Hi, thanks for the scvi-tools release, I really like that everything is now neatly tied together under the model class!
I have a question about the expected workflow for performing gene selection. Since we now first prepare the adata with scvi.data.setup_anndata, should we be performing gene selection in the adata itself, before calling scvi.data.setup_anndata?
For example, in the old API I first filter genes by a minimum number of counts per batch using gene_dataset.filter_genes_by_count, then use the gene_dataset.subsample_genes method with the   poisson_zeros mode to select genes.
In the new API, should I be doing this selection directly with the adata? I saw that the poisson gene section function is still available under scvi.data.poisson_gene_selection, but I did not find the function filter_genes_by_count. Is the suggestion that this filtering be done with scanpy?
Below I'm copying a snippet showing how I'd do the gene selection and training with the old API, and how to do it with the new API which I took from the tutorial. The only part I'm not totally sure how the recommended way to do is the gene filtering and gene selection.
Thanks!
Old API
### Old API
import scvi
adata = anndata.read('my_adata.h5ad')
gene_dataset = scvi.dataset.AnnDatasetFromAnnData(adata, # make gene dataset from adata
                                    ctype_label='cluster_label', # cell type label
                                    batch_label='batch_id' # add batch labels
                                  )
vae = scvi.models.VAE('n_input':gene_dataset.nb_genes, 'n_batch':gene_dataset.n_batches ) # specify VAE parameres

#filter genes with less than 100 counts in at least one batch
gene_dataset.filter_genes_by_count(min_count = 100, per_batch=True)
# select genes using the poisson_zeros
gene_dataset.subsample_genes(3000, batch_correction= True,mode="poisson_zeros")
trainer = scvi.inference.UnsupervisedTrainer(vae, gene_dataset) # create trainer

trainer.train(frequency=1, n_epochs = 100) # train
trainer.history ## access training history

full_posterior = trainer.create_posterior( # create posterior
	trainer.model,
	gene_dataset,
	indices=np.arange(len(gene_dataset)))

latent, batch_indices, labels = full_posterior.sequential().get_latent()

New API
### New API

import scvi
adata = anndata.read('my_adata.h5ad')
adata.layers["counts"] = adata.X.copy() # preserve counts

### perform gene selection here, before setup_annata? e.g.
# scvi.data.poisson_gene_selection(adata)
# adata = adata[:,adata.var['highly_variable']]

scvi.data.setup_anndata(adata, layer="counts", batch_label='batch_id')

### or perform gene selection here, after setup_anndata?

model = scvi.model.SCVI(adata,  n_hidden=n_hidden, n_latent = n_latent)
model.train(frequency=1, n_epochs = 100)
model.trainer.history # check training history
latent = model.get_latent_representation() # get latent

Hi @Munfred ,

Since we now first prepare the adata with scvi.data.setup_anndata, should we be performing gene selection in the adata itself, before calling scvi.data.setup_anndata?

All preprocessing (and gene selection) should occur before the call to setup_anndata. In the quick start we put the following warning message as well as the info message from setup_anndata to warn against editing an already setup anndata, but perhaps we can make this more clear.

The idea of setup_anndata is that scvi-tools puts a setup dictionary into the anndata itself that is used during the vae creation and is used for data loading into the model. So editing your anndata after setup_anndata and before model creation/training will probably lead to errors, and in most cases the model will catch this and give you an informative message back.

Is the suggestion that this filtering be done with scanpy?

Yes, we removed all superfluous data preprocessing functions and refer to scanpy for these steps.  We also suggest the following workflow.
# basic filtering steps not shown
adata.layers["counts"] = adata.X.copy() # preserve counts
sc.pp.normalize_total(adata, target_sum=1e4)
sc.pp.log1p(adata)
adata.raw = adata # freeze the state in `.raw`, so subsetting genes in X will still leave .raw as all genes
# gene selection not shown.
# setup anndata using the layer

I saw that the poisson gene section function is still available under scvi.data.poisson_gene_selection

We kept this function as it uses torch and the GPU, otherwise I would have made a PR with it in scanpy. I think this gene selection is good, and so it the seurat_v3 flavor in scanpy.

Note that we found an issue with C order vs F order of the memory in the layer. F order is a lot slower. We have this fixed stage for another alpha release today or tomorrow.

Thanks for the quick response! That answers my questions!

fyi, you should update your pip install as we fixed that issue